Contents

MPLS-L3VPN-STD-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

mplsL3VpnVrfUp· 1

mplsL3VpnVrfDown· 2

mplsL3VpnVrfRouteMidThreshExceeded· 3

mplsL3VpnVrfNumVrfRouteMaxThreshExceeded· 4

mplsL3VpnNumVrfRouteMaxThreshCleared· 5

 

 

MPLS-L3VPN-STD-MIB

About this MIB

Use this MIB to obtain MPLS VPN information.

MIB file name

rfc4382-mpls-l3vpn-std.mib

Notifications

mplsL3VpnVrfUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.11.0.1	An interface associated with a VRF comes up.	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated for a VPN instance (VRF) in the following conditions:

When the VPN instance is not bound to any interface, bind the VPN instance with an interface whose state (ifOperStatus) is up.

The VPN instance is bound to only one interface, and the bound interface's state (ifOperStatus) changes from down to up.

The VPN instance is bound to multiple interfaces. When all the interfaces are in down state (ifOperStatus), one of the interfaces changes from down state to up state.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable l3vpn command.

OFF

CLI: Use the undo snmp-agent trap enable l3vpn command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.11.1.2.1.1.5 (mplsL3VpnIfConfRowStatus)	Row status used to create, modify, and delete a row in this table.	mplsL3VpnVrfName mplsL3VpnIfConfIndex	INTEGER	active(1)
1.3.6.1.2.1.10.166.11.1.2.2.1.6 (mplsL3VpnVrfOperStatus)	Operational state of the VPN.	mplsL3VpnVrfName	INTEGER	up(1), down(2)

 

Recommended action

No action is required.

mplsL3VpnVrfDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.11.0.2	An interface associated with a VRF goes down.	Error	Major	1.3.6.1.2.1.10.166.11.0.1 (mplsL3VpnVrfUp)	ON

 

Notification triggers

This notification is generated for a VPN instance (VRF) in the following conditions:

The VPN instance is bound to only one interface and the interface’s state (ifOperStatus) is up. The interface state changes from up to down or the interface is unbound from the VPN instance.

The VPN instance is bound to multiple interfaces. The ifOperStatus state of the last bound interface changes from up to down, or the last up interface is unbound from the VPN instance.

System impact

The VPN instance does not have an interface to forward IPv4 traffic.

Status control

ON

CLI: Use the snmp-agent trap enable l3vpn command.

OFF

CLI: Use the undo snmp-agent trap enable l3vpn command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.11.1.2.1.1.5 (mplsL3VpnIfConfRowStatus)	Row status used to create, modify, and delete a row in this table.	mplsL3VpnVrfName mplsL3VpnIfConfIndex	INTEGER	active(1)
1.3.6.1.2.1.10.166.11.1.2.2.1.6 (mplsL3VpnVrfOperStatus)	Operational state of the VPN.	mplsL3VpnVrfName	INTEGER	up(1), down(2)

 

Recommended action

To resolve this issue, perform the following tasks:

Identify whether the VPN instance is in use. If the VPN instance is not in use, unbinding the VPN instance from interfaces is normal and no action is required. If the VPN instance is in use, execute the display ip vpn-instance instance-name vpn-instance-name command to view the Interfaces field in the output.

● If the Interfaces field is not displayed, it indicates that no interface is bound to the VPN instance. In this case, identify the interface for the VPN instance, execute the ip binding vpn-instance command to bind the interface to the VPN instance, and then execute the ip address command to configure an IPv4 address for the interface.

● If the value of the Interfaces field is an interface or multiple interfaces, execute the display ip interface command to view interface state.

  - If the interface physical state (current state) is down, troubleshoot the physical link faults.

  - If the interface physical state (current state) is Administratively DOWN, execute the undo shutdown command to bring up the interface.

  - If the interface does not have an IPv4 address, execute the iP address command to assign an IPv4 address to the interface.

If the issue persists, collect log messages, configuration data, and alarm information, and then contact Technical Support.

1.

mplsL3VpnVrfRouteMidThreshExceeded

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.11.0.3	The number of routes in a VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the number of route prefixes in the routing table of the VPN instance exceeds the warning threshold.

System impact

The number of routes in the routing table of the VPN instance has reached the warning threshold. New routes can still be added to the VPN routing table and no route loss or traffic disruption will occur currently.

Status control

ON

CLI: Use the snmp-agent trap enable l3vpn command.

OFF

CLI: Use the undo snmp-agent trap enable l3vpn command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.11.1.3.1.1.3 (mplsL3VpnVrfPerfCurrNumRoutes)	Total number of active IPv4 and IPv6 routes.	mplsL3VpnVrfName	Gauge32	INTEGER(0..4294967295)
1.3.6.1.2.1.10.166.11.1.2.2.1.9 (mplsL3VpnVrfConfMidRteThresh)	Mid-level water marker for the number of routes that this VRF supports.	mplsL3VpnVrfName	Unsigned32	Standard MIB values.

 

Recommended action

To resolve this issue, perform the following tasks:

1.Execute the display ip routing-table vpn-instance vpn-instance-name summary command to view the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields to identify whether the VPN instance route limit has reached the MidRoute warning threshold.

2.Execute the display ip routing-table vpn-instance vpn-instance-name statistics command to view the number of routes of each protocol in the VPN instance. Identify whether the route counts satisfy the expected size.

  - If yes, enter VPN instance view, edit the routing-table limit configuration with a bigger warning threshold value.

  - If no, check the routing protocol whose route count exceeds the expected size and adjust the configuration to remove the exceeding routes. Then, execute the command in step 1 to identify whether the number of route prefixes has dropped below the warning threshold.

3.If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support.

mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.11.0.4	The number of routes in a VRF exceeds or about to exceed the maximum allowed value as indicated by mplsL3VpnVrfMaxRouteThreshold.	Error	Warning	1.3.6.1.2.1.10.166.11.0.6 (mplsL3VpnNumVrfRouteMaxThreshCleared)	ON

 

Notification triggers

This notification is generated when the number of prefixes in the routing table of a VPN instance exceeds the maximum allowed.

System impact

No new routes can be added to the routing table of the VPN instance, and thus some traffic might be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable l3vpn command.

OFF

CLI: Use the undo snmp-agent trap enable l3vpn command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.11.1.3.1.1.3 (mplsL3VpnVrfPerfCurrNumRoutes)	Total number of active IPv4 and IPv6 routes.	mplsL3VpnVrfName	Gauge32	INTEGER(0..4294967295)
1.3.6.1.2.1.10.166.11.1.2.2.1.10 (mplsL3VpnVrfConfHighRteThresh)	High-level water marker for the number of routes that the VRF supports.	mplsL3VpnVrfName	Unsigned32	Standard MIB values.

 

Recommended action

1.Execute the display ip routing-table vpn-instance vpn-instance-name summary command to view the values for the Max Active Route, Remain Active Route, and Threshold value percentage fields to identify whether the number of route prefixes in the VPN instance has reached the maximum.

2.Execute the display ip routing-table vpn-instance vpn-instance-name statistics command to view the number of routes of each protocol in the VPN instance. Identify whether the route counts satisfy the expected size.

  - If yes, enter VPN instance view, edit the routing-table limit configuration with a bigger maximum value.

  - If no, check the routing protocol whose route count exceeds the expected size and adjust the configuration to remove the exceeding routes. Then, execute the command in step 1 to identify whether the number of route prefixes has dropped below the warning threshold.

3.If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support.

mplsL3VpnNumVrfRouteMaxThreshCleared

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.11.0.6	The number of routes in a VRF falls below the value of the mplsVrfMaxRouteThreshold object.	Recovery	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the number of route prefixes in the routing table of a VPN instance drops below the maximum value.

System impact

The number of routes in the routing table of the VPN instance has dropped below the maximum value. New routes can be added to the VPN instance’s routing table again

Status control

ON

CLI: Use the snmp-agent trap enable l3vpn command.

OFF

CLI: Use the undo snmp-agent trap enable l3vpn command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.11.1.3.1.1.3 (mplsL3VpnVrfPerfCurrNumRoutes)	Total number of active IPv4 and IPv6 routes.	mplsL3VpnVrfName	Gauge32	INTEGER(0..4294967295)
1.3.6.1.2.1.10.166.11.1.2.2.1.10 (mplsL3VpnVrfConfHighRteThresh)	High-level water marker for the number of routes that the VRF supports.	mplsL3VpnVrfName	Unsigned32	Standard MIB values.

 

Recommended action

No action is required.