- Table of Contents
-
- 10-MPLS
- 01-HH3C-MPLSRSVP-MIB
- 02-HH3C-L2VPN-MIB
- 03-HH3C-L3VPN-MIB
- 04-HH3C-MPLS-LDP-MIB
- 05-HH3C-MPLSCRLSP-MIB
- 06-HH3C-MPLSEXT-MIB
- 07-HH3C-MPLSLSPV-MIB
- 08-HH3C-VSI-MIB
- 09-HH3C-MPLSTE-MIB
- 10-HH3C-MPLSSLSP-MIB
- 11-HH3C-MPLSPCE-MIB
- 12-MPLS-FRR-FACILITY-STD-MIB
- 13-MPLS-L3VPN-STD-MIB
- 14-MPLS-LDP-STD-MIB
- 15-MPLS-LSR-STD-MIB
- 16-PW-STD-MIB
- 17-TE-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
06-HH3C-MPLSEXT-MIB | 71.00 KB |
Contents
HH3C-MPLSEXT-MIB
About this MIB
Use this MIB to manage MPLS and LDP capabilities and MPLS BFD sessions.
MIB file name
rfc3812-mpls-te-std.mib
Notifications
mplsTunnelUp
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.166.3.0.1 |
A tunnel comes up. |
Recovery |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the operational state (indicated by the mplsTunnelOperStatus object) of a tunnel changes from down to another value (except for notPresent).
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.166.3.2.2.1.34 (mplsTunnelAdminStatus) |
Administrative state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) |
1.3.6.1.2.1.10.166.3.2.2.1.35 (mplsTunnelOperStatus) |
Actual state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7) |
Recommended action
No action is required.
mplsTunnelDown
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.166.3.0.2 |
The operation state of a tunnel becomes down. |
Error |
Major |
N/A (N/A) |
ON |
Notification triggers
For all types of tunnels, possible reasons for this notification include the following:
The interface went Down.
The configuration of the tunnel was deleted.
The link was faulty.
The tunnel was manually shut down.
Others
For RSVP-TE tunnels, possible reasons for this notification also include the following:
RSVP-TE LSP resources were preempted.
Transmission of an RSVP message timed out.
RSVP Hello mechanism detected a downstream node failure.
CSPF failed to calculate a path.
For Segment Routing TE tunnels, possible reasons for this notification also include the following:
IGP calculation or verification failed.
For static TE tunnels, possible reasons for this notification also include:
A static CR-LSP went Down.
A static SR-LSP went Down.
System impact
Service traffic carried on the tunnel will be interrupted.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.166.3.2.2.1.34 (mplsTunnelAdminStatus) |
Administrative state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) |
1.3.6.1.2.1.10.166.3.2.2.1.35 (mplsTunnelOperStatus) |
Operational state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7) |
Recommended action
To resolve this issue:
1.Check the current tunnel interface configuration, IGP configuration, and the whole tunnel path.
- If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.
If yes, clear link faults.
If no, execute step 2 or 3 according to the tunnel type.
- If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, execute step 2 or 3 according to the tunnel type.
2.For an RSVP-TE tunnel, check whether the RSVP protocol, link bandwidth, and link affinity settings are correct.
- If the settings are correct but the issue persists, go to step 4.
- If the settings are not correct, edit the related configuration.
3.For a static MPLS TE tunnel, check whether static CRLSP or SRLSP settings are correct.
- If the settings are correct but the issue persists, go to step 4.
- If the settings are not correct, edit the related configuration.
4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
mplsTunnelRerouted
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.166.3.0.3 |
A tunnel is rerouted. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when a tunnel is rerouted because of the current path used by the tunnel is unreachable. If the mplsTunnelARHopTable is used, the tunnel entry in the mplsTunnelARHopTable might contain the new path of the tunnel for a time period after the agent sends this notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.166.3.2.2.1.34 (mplsTunnelAdminStatus) |
Administrative state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) |
1.3.6.1.2.1.10.166.3.2.2.1.35 (mplsTunnelOperStatus) |
Operational state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7) |
Recommended action
No action is required..
mplsTunnelReoptimized
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.10.166.3.0.4 |
A tunnel is reoptimized. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the optimal path is selected successfully for a tunnel during tunnel reoptimization. If the mplsTunnelARHopTable is used, the tunnel entry in the mplsTunnelARHopTable might contain the new path of the tunnel for a time period after the agent sends this notification.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.10.166.3.2.2.1.34 (mplsTunnelAdminStatus) |
Administrative state of the tunnel. |
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) |
1.3.6.1.2.1.10.166.3.2.2.1.35 (mplsTunnelOperStatus) |
Operational state of the tunnel. |
mplsTunnelIndex,mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId |
INTEGER |
up(1) , down(2) , testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7) |
Recommended action
No action is required.