L3VPN_1.3.6.1.2.1.10.166.11.0.2 L3VPN_MIB_TRAP_VRF_DOWN

Trap Buffer Description

The interface bound to the VPN instance went Down. (VpnInstanceName=[VpnInstanceName], IfName=[IfName], IfCurRowStatus=[IfCurRowStatus], VRFOperationStatus=[VRFOperationStatus])

Of the interfaces that are bound to VPN instance, the last interface in the Up state goes Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	L3V_TRAP_VRF_DOWN
Trap OID	1.3.6.1.2.1.10.166.11.0.2
MIB	MPLS-L3VPN-STD-MIB
Alarm ID	0x09110000
Alarm Name	L3V_TRAP_VRF_DOWN
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L3VPN_1.3.6.1.2.1.10.166.11.0.1 L3VPN_MIB_TRAP_VRF_UP

Trap Buffer Parameters

Parameter	Description
VpnInstanceName	Indicates the name of the VPN.
IfName	The name of interface.
IfCurRowStatus	Indicates the row status of the interface. Including: 1: Active 2: Not in Service 3: Not Ready 4: Create and Go 5: Create and Wait 6: Destroy
VRFOperationStatus	Indicates the status of the VRF. Including: 1: Up 2: Down

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.10.166.11.1.2.1.1.5	mplsL3VpnIfConfRowStatus	mplsL3VpnVrfName mplsL3VpnIfConfIndex
1.3.6.1.2.1.10.166.11.1.2.2.1.6	mplsL3VpnVrfOperStatus	mplsL3VpnVrfName

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.2.1.1.5

mplsL3VpnIfConfRowStatus

mplsL3VpnVrfName

mplsL3VpnIfConfIndex

1.3.6.1.2.1.10.166.11.1.2.2.1.6

mplsL3VpnVrfOperStatus

mplsL3VpnVrfName

Impact on the System

No available interface is bound with the VPN instance.

Possible Causes

Cause 1: One interface was bound with the VPN instance, and the interface status changed from Up to Down.

Cause 2: Multiple interfaces were bound with the VPN instance; the status of all the interfaces changed from Up to Down; the last interface in the Up state went Down.

Cause 3: The last interface with Up state is disassociated from the VPN instance.

Procedure

1. Run the display ip vpn-instance verbose vpn-instance-name command to check which interfaces are bound with the VPN instance.

If no interface is bound with the VPN instance, search the log file and find whether there is a log message containing the keywords "undo ip binding vpn-instance" and generated with the alarm.
If so, and the VPN instance should be unbound, the problem is resolved, go to step 6. If the VPN instance cannot be unbound, run the ip binding vpn-instance vpn-instance-name command in the interface view to bound the interface with the VPN instance, and then run ip address ipv4-address command to configure IP address for the interface.
If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 L3VPN_MIB_TRAP_VRF_UP of this VPN instance appears later, the problem is resolved, go to step 6.
If not, go to step 5.
If there is not the relative log, go to step 5.
If there are some interfaces bound with the VPN instance, go to Step 2.

2. Run the display ip interface brief command to check whether there are one or more interfaces bound with the VPN instance and in Up state.

If so, go to Step 5.
If not, go to Step 3.

3. Check whether the interfaces are configured with IP addresses.

If so, go to Step 4.
If not, run ip address ipv4-address comand to configure IP addresses for the interfaces if necessary. Then,
If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 L3VPN_MIB_TRAP_VRF_UP of this VPN instance appears later, the problem is resolved, go to step 6.
If not, go to step 4.

4. Run the display this command in the interface view to check whether the interfaces are shutdown.

If so, run the undo shutdown command on the interfaces if necessary. Then,
If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 L3VPN_MIB_TRAP_VRF_UP of this VPN instance appears later, the problem is resolved, go to step 6.
If not, go to step 5.
If all the interfaces are not shut down, go to Step 5.

5. Collect alarm information and configuration information, and then contact technical support personnel.

6. End.