Cisco Cisco IOS Software Release 12.2(33)SRE

In the third phase, the user can access a particular instance of a table entry. With this third phase, 
complete retrieval can be based on the SNMP context name. 

IP access lists can be configured and associated with SNMP community strings. This feature enables you 
to configure an association between VRF instances and SNMP community strings. When a VRF instance 
is associated with an SNMP community string, SNMP processes requests coming in for a particular 
community string only if they are received from the configured VRF. If the community string contained 
in the incoming packet has no VRF associated with it, it is processed only if it came in through a 
non-VRF interface. 

The MPLS-LSR-STD-MIB based on RFC 3813 provides the same basic functionality as the 
MPLS-LSR-MIB based on Version 05 of the IETF MPLS-LSR-MIB. They both provides an interface 
for managing label switching through the use of SNMP.

After the implementation of the MPLS-LSR-STD-MIB (RFC 3813) in Cisco IOS Release 12.2(33)SRB, 
the MPLS-LSR-MIB will exist for a period of time before support is completely removed. This gives 
you the chance to migrate to the MPLS-LSR-STD-MIB. Both MIBs can coexist in the same image 
because the MPLS-LSR-STD-MIB and the MPLS-LSR-MIB have different root object identifiers 
(OIDs).

The following sections contain information about the major differences between the 
MPLS-LSR-STD-MIB and the MPLS-LSR-MIB:

 shows the major difference between the MPLS-LSR-MIB objects and the 

MPLS-LSR-STD-MIB objects for each scalar object.

mplsTrafficParamIndexNext

—

Object deleted.

mplsInSegmentTrapEnable

—

Object deleted.

mplsOutSegmentTrapEnable

—

Object deleted.

—

mplsInSegmentIndexNext

New object.

mplsOutSegmentIndexNext

mplsOutSegmentIndexNext

Syntax change. Formerly 
integer 32, now is 
MplsIndexType, which is an 
octet string.

mplsXCIndexNext

mplsXCIndexNext

Syntax change. Formerly 
integer 32, now is 
MplsIndexType, which is an 
octet string.