Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

MX Series Router Cloud CPE SNMP Monitoring Services Overview

When you migrate subscribers to cCPE services, you can provide them with read-only access to systems (SNMP MIB-2 System), interfaces (SNMP MIB-2 Interfaces), and some environment-monitoring MIBs. Because the Layer 3 CPE functionality moves from the CPE device to the MX Series router, only the interfaces MIB is relevant to cCPE services. However, you can also provide read-only access to the systems MIB, which enables subscribers to retrieve the location or contact information of the cCPE context. Traps for system-wide events for a specific subscriber are not relevant, because the router hosting the cCPE context is shared by many customers (one cCPE context per subscriber).

The SNMP service supports routing instances in the following ways:

• You can bind an SNMP community to a specific routing instance by using the edit snmp community community routing-instance routing-instance configuration statement.
• If an SNMP request is received on a nondefault routing instance and the routing instance is not bound to the specified community, the request is denied.
• SNMP requests received by a nondefault routing instance through one of its access links must use community in the format of routing-instance@community, where the routing-instance must be one of the routing instances bound to the community. In addition, the routing instance used in community must be the routing instance where the request is received. Such requests return only MIB objects pertaining to the specified routing instance. For example, an SNMP walk command issued on the interfaces table (RFC 2863) with community “acme@public” returns only interfaces defined in the routing instance “acme.” To learn more about the MIB objects that are segregated by routing instances, see Support Classes for MIB Objects.
• SNMP read requests received on the default routing instance can also use community in the format of routing-instance@community. The Junos OS SNMP agent returns only MIB objects pertaining to the specified routing instance. If you want to provide MIB information through an NMS system that connects to the default routing instance, you can use the format routing-instance@community to provide the necessary MIB object isolation for a subscriber’s routing instance.

Note: For security purposes, after you configure cCPE services, subscribers cannot retrieve the global router configuration. The only information customers can retrieve pertains to their cCPE context, which includes the interfaces used for implementing the IP VPN services. You can retrieve the status of VPN services by getting the usage counters of the interfaces.