- Table of Contents
-
- 10-MPLS
- 01-HH3C-MPLSRSVP-MIB
- 02-HH3C-MPLSLSPV-MIB
- 03-HH3C-MPLSSCRLSP-MIB
- 04-HH3C-EVC-MIB
- 05-HH3C-L2VPN-MIB
- 06-HH3C-L3VPN-MIB
- 07-HH3C-MPLS-LDP-MIB
- 08-HH3C-MPLS-VPN-BGP-MIB
- 09-HH3C-MPLSBFD-MIB
- 10-HH3C-MPLSEXT-MIB
- 11-HH3C-VSI-MIB
- 12-HH3C-MPLSTE-MIB
- 13-HH3C-MPLSSLSP-MIB
- 14-HH3C-MPLSPCE-MIB
- 15-MPLS-FRR-FACILITY-STD-MIB
- 16-MPLS-FRR-GENERAL-STD-MIB
- 17-MPLS-FTN-STD-MIB
- 18-MPLS-L3VPN-STD-MIB
- 19-MPLS-LDP-STD-MIB
- 20-MPLS-LSR-STD-MIB
- 21-MPLS-TE-STD-MIB
- 22-PW-ENET-STD-MIB
- 23-PW-MPLS-STD-MIB
- 24-PW-STD-MIB
- 25-TE-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
06-HH3C-L3VPN-MIB | 96.64 KB |
Contents
HH3C-L3VPN-MIB
About this MIB
This MIB contains L3VPN information.
MIB file name
hh3c-l3vpn.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cL3vpn (228)
Scalar objects
hh3cL3vpnVrfName
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cL3vpnVrfName (1.3.6.1.4.1.25506.2.228.1.1) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..31) |
Name of a VRF. |
As per the MIB. |
hh3cL3vpnIfName
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cL3vpnIfName (1.3.6.1.4.1.25506.2.228.1.2) |
accessible-for-notify |
DisplayString |
OCTET STRING (1..255) |
Name of an interface bound to a VRF. |
As per the MIB. |
Notifications
hh3cL3vpnVrfV6Up
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.228.0.1 |
At least one of the IPv6 interfaces bound to the VRF come up from the down state. |
Recovery |
Major |
N/A |
ON |
Notification triggers
This notification is generated when the following conditions are met:
When the VPN instance is not bound to any interfaces, an IPv6 up interface is bound to the VPN instance.
When the VPN instance is bound to only one interface, the IPv6 protocol state of the interface changes from down to up.
When the VPN instance is bound to multiple interfaces and the IPv6 protocol state of all the interfaces is down, the IPv6 protocol state of one or multiple interfaces changes from down to up.
System impact
No impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable l3vpn vrf-ipv6-up command.
Off
CLI: Use the undo snmp-agent trap enable l3vpn vrf-ipv6-up command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.228.1.1 (hh3cL3vpnVrfName) |
Name of a VRF. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
1.3.6.1.4.1.25506.2.228.1.2 (hh3cL3vpnIfName) |
Name of an interface bound to the VRF. |
N/A |
DisplayString |
OCTET STRING(1..255) |
Recommended action
No action is required.
hh3cL3vpnVrfV6Down
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.228.0.2 |
The IPv6 interfaces bound to the VRF are all down. |
Error |
Warning |
1.3.6.1.4.1.25506.2.228.0.1 (hh3cL3vpnVrfV6Up) |
ON |
Notification triggers
This notification is generated when the following conditions are met:
When the VPN instance is bound to only one interface and the IPv6 protocol state of the interface is up, the IPv6 protocol state of the interface changes from up to down or the binding between the interface and the VPN instance is removed.
When the VPN instance is bound to multiple interfaces and the IPv6 protocol state of all the interfaces is down, the IPv6 protocol state of one or multiple interfaces changes from down to up.
System impact
The VPN instance does not have any interfaces for forwarding IPv6 traffic.
Status control
ON
CLI: Use the snmp-agent trap enable l3vpn vrf-ipv6-down command.
Off
CLI: Use the undo snmp-agent trap enable l3vpn vrf-ipv6-down command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.228.1.1 (hh3cL3vpnVrfName) |
Name of a VRF. |
N/A |
OCTET STRING |
OCTET STRING(0..31) |
1.3.6.1.4.1.25506.2.228.1.2 (hh3cL3vpnIfName) |
Name of an interface bound to the VRF. |
N/A |
DisplayString |
OCTET STRING(1..255) |
Recommended action
To resolve this issue:
1. Identify whether the VPN instance is in use. If it is not in use, no action is required. If it is use, execute the display ip vpn-instance instance-name vpn-instance-name command to check the Interfaces field in the output from the command:
¡ If this field does not exist, no interfaces bound to the VPN instance exist. You must execute the ip binding vpn-instance command bind the interface to the VPN instance on the interface that belongs to the VPN instance, and then execute the ipv6 address command to specify an IPv6 address for the interface.
¡ If the value for the field is an interface or multiple interfaces, execute the display ipv6 interface command to view the status of the interfaces.
- If the current state of the interface is down, check for and troubleshoot physical link failure.
- If the current state of the interface is Administratively DOWN, execute the undo shutdown command on the interface to bring up the interface.
- If no IPv6 address exists on the interface, execute the ipv6 address command on the interface to specify an IP address for the interface.
2. Collect alarm information and configuration data, and then contact Technical Support for help.