Contents

HH3C-MPLSRSVP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

hh3cRsvpNeighborLost 1

hh3cMplsRsvpNeighborLostRecovery· 2

hh3cMplsRsvpAuthFail 3

hh3cMplsRsvpAuthFailRecovery· 4

hh3cMplsRsvpFrrProtAval 5

hh3cMplsRsvpFrrProtNotAval 6

hh3cMplsRsvpFrrSwitch· 7

hh3cMplsRsvpFrrResume· 8

 

 

HH3C-MPLSRSVP-MIB

About this MIB

Use this MIB to notify RSVP traps.

MIB file name

hh3c-mplsrsvp.mib

Notifications

hh3cRsvpNeighborLost

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.1	The device was disconnected from an RSVP neighbor, and the hello state of the RSVP neighbor changed from up state to init or idle state.	Error	Major	1.3.6.1.4.1.25506.2.229.0.2 (hh3cMplsRsvpNeighborLostRecovery)	ON

 

Notification triggers

This notification might be generated when the following events occur:

RSVP hello timer expires.

RSVP hello is disabled.

RSVP neighbor link or node failure.

Others.

System impact

The loss of a neighbor will cause the RSVP-TE path established between neighbors to be disconnected. If the GR capability is enabled, there will be no negative impact on services. If the GR capability is not enabled, it will lead to the LSP entering the Down state or an FRR switchover.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-nbr-lost command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-nbr-lost command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.1 (hh3cMplsRsvpNbrAddr)	RSVP neighbor address	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Check whether there is a fault on the physical link or the peer node.

  - If yes, repair the physical link or restart the peer node.

  - If not, proceed to step 2.

2.Execute the display ip routing-table command to check if a route to the peer node exists.

  - If yes, proceed to step 3.

  - If no, configure the IGP protocol to advertise the route.

3.Check whether the RSVP settings are correct.

  - If yes, proceed to step 4.

  - If not, correct the related settings.

4.If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsRsvpNeighborLostRecovery

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.2	The RSVP neighbor recovered, the device received a hello from the RSVP neighbor, and the hello state of the RSVP neighbor changed from init to up.	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an RSVP neighbor recovers and the device receives hello messages from the RSVP neighbor again.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-nbr-lost command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-nbr-lost command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.1 (hh3cMplsRsvpNbrAddr)	RSVP neighbor address	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.

hh3cMplsRsvpAuthFail

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.3	RSVP authentication failed. The device cannot receive RSVP packets from the RSVP neighbor.	Error	Major	1.3.6.1.4.1.25506.2.229.0.4 (hh3cMplsRsvpAuthFailRecovery)	ON

 

Notification triggers

This notification might be generated when the following events occur:

The RSVP authentication configuration is consistent on the two ends of the RSVP session.

Others.

System impact

The device cannot receive all RSVP packets from the RSVP neighbor, resulting in RSVP service failure.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-auth-fail command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-auth-fail command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.1 (hh3cMplsRsvpNbrAddr)	RSVP neighbor address	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Check whether the RSVP authentication related configuration is consistent on the two ends of the RSVP session.

  - If yes, proceed to step 2.

  - If not, correct the related settings.

2.If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsRsvpAuthFailRecovery

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.4	The device received correct RSVP authentication packets from the RSVP neighbor. The RSVP authentication failure recovers.	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the device receives correct RSVP authentication packets from an authentication-failed RSVP neighbor.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-auth-fail  command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-auth-fail  command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.1 (hh3cMplsRsvpNbrAddr)	RSVP neighbor address	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.

hh3cMplsRsvpFrrProtAval

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.5	The main tunnel was bound to the bypass tunnel. The bypass tunnel then can protect the main tunnel. When the main tunnel fails, the bypass tunnel takes over to avoid traffic forwarding failure.	Informational	Major	1.3.6.1.4.1.25506.2.229.0.6 (hh3cMplsRsvpFrrProtNotAval)	ON

 

Notification triggers

This notification is generated when a main tunnel is bound to a bypass tunnel and FRR is available.

System impact

The bypass tunnel is ready to provide protection. No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-frr-protect command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-frr-protect command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.2  (hh3cMplsRsvpFrrMainInfo)	Information of the protected tunnel (main tunnel)	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.229.1.1.3 (hh3cMplsRsvpFrrByPassInfo)	Information of the protection tunnel (bypass tunnel)	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.

hh3cMplsRsvpFrrProtNotAval

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.6	The main tunnel was unbound from the bypass tunnel. The bypass tunnel then cannot protect the main tunnel. When the main tunnel fails, traffic forwarding fails.	Informational	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a main tunnel is unbound from its bypass tunnel.

System impact

FRR becomes unavailable. When a link fails, the RSVP-TE tunnel cannot perform link switchover quickly, resulting in traffic interruption on the main tunnel.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-frr-protect command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-frr-protect command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.2  (hh3cMplsRsvpFrrMainInfo)	Information of the protected tunnel (main tunnel)	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.229.1.1.3 (hh3cMplsRsvpFrrByPassInfo)	Information of the protection tunnel (bypass tunnel)	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Verify that the bypass tunnel is established.

2.Verify that the bypass tunnel uses a different path than the main tunnel.

3.Verify that RSVP-TE FRR related settings are correct.

4.If the issue persists, contact Technical Support for help.

hh3cMplsRsvpFrrSwitch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.7	The main tunnel fails and traffic is switched from the main tunnel to the bypass tunnel.	Error	Major	1.3.6.1.4.1.25506.2.229.0.8 (hh3cMplsRsvpFrrResume)	ON

 

Notification triggers

This notification is generated when the interface or link protected by a bypass tunnel goes down and the service traffic is switched to the bypass tunnel.

System impact

The tunnel service is switched to the bypass tunnel. The service traversed path is not the expected main tunnel, thus risks might increase for the service.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-frr-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-frr-switch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.2  (hh3cMplsRsvpFrrMainInfo)	Information of the protected tunnel (main tunnel)	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.229.1.1.3 (hh3cMplsRsvpFrrByPassInfo)	Information of the protection tunnel (bypass tunnel)	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, proceed to step 2.

If not, proceed to step 3.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 3.

2.Clear link faults.

3.Collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsRsvpFrrResume

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.229.0.8	The main tunnel recovers, and traffic is switched back from the bypass tunnel to the main tunnel.	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of the interface or link protected by a bypass tunnel changes from down to up and the service traffic is switched from the bypass tunnel back to the main tunnel.

System impact

The service traffic is switched from the bypass tunnel back to the main tunnel. No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te-private rsvp-frr-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private rsvp-frr-switch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.229.1.1.2  (hh3cMplsRsvpFrrMainInfo)	Information of the protected tunnel (main tunnel)	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.229.1.1.3 (hh3cMplsRsvpFrrByPassInfo)	Information of the protection tunnel (bypass tunnel)	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.