- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
04-TE-MIB | 77.19 KB |
TE-MIB
About this MIB
Use this MIB to manage TE tunnel interface and explicit path settings.
MIB file name
rfc3970-te.mib
Notifications
teTunnelUp
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.122.0.1 |
TE tunnel up |
Recovery |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the tunnel specified by teTunnelName transitions to the up state.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.122.1.2.1.2 (teTunnelName) |
TE tunnel name |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (1..32)) |
1.3.6.1.2.1.122.1.3.1.2 (tePathName) |
Name of the TE tunnel's path |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (0..32)) |
Recommended action
No action is required.
teTunnelDown
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.122.0.2 |
TE tunnel down |
Error |
Major |
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.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.122.1.2.1.2 (teTunnelName) |
TE tunnel name |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (1..32)) |
1.3.6.1.2.1.122.1.3.1.2 (tePathName) |
Name of the TE tunnel's path |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (0..32)) |
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 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. Collect alarm information and configuration data, and then contact Technical Support.
teTunnelChanged
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.122.0.3 |
TE tunnel path change |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the active path for the tunnel specified by teTunnelName changes or a new path becomes active. The value of tePathName is the new active path.
System impact
No negative impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable te command.
OFF
CLI: Use the undo snmp-agent trap enable te command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.122.1.2.1.2 (teTunnelName) |
TE tunnel name |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (1..32)) |
1.3.6.1.2.1.122.1.3.1.2 (tePathName) |
Name of the TE tunnel's path |
teTunnelIndex |
SnmpAdminString |
OCTET STRING (SIZE (0..32)) |
Recommended action
No action is required.