RSVP

Succeeded in disabling RSVP in the MPLS view.

Succeeded in enabling RSVP in the interface view.

Succeeded in enabling RSVP in the MPLS view.

The RSVP function was enabled.

The RSVP function was disabled.

Failed to obtain the MPLS MTU during the creation of interface entries.

The system works abnormally.

When the local node helped the neighbor to perform GR, the GR Aging timer expired.

When the local node helped the neighbor to perform GR and GR ended, the GR Aging timer was started.

After the local router finished GR, the status of the neighbor changed from end to normal.

The neighbor no longer helped the local node to perform GR, and the status of the local node changed to end.

When the local node performed GR and received the Support message from the neighbor, the local node changed the neighbor status from normal to supporting.

After the local node finished GR, the status of the neighbor changed from supporting to end.

When the neighbor helped the local node to perform GR and the local node finished GR, the local node changed the neighbor status from supporting to normal.

The active/standby switchover occurred.

GR normally ended.

When the local node was performing GR, no neighbor helped the local node to perform GR.

The Restart timer ended during GR.

Before the timer expired, the local node did not receive the Hello message sent from the neighbor, and thus the local node judged that the neighbor was performing GR. After receiving the Hello message sent from the neighbor, the local node changed the neighbor status.

The local node received the GR message of the neighbor and judged that the neighbor was performing GR, and then the status of the supporting node changed.

When the local node supported GR and Hello detection with the neighbor expired, the local node judged that the neighbor might be performing GR and set the flag bit.

The local node received the Hello message from the neighbor and found the neighbor performing GR.

When the neighbor was performing GR, the Hello message between the local node and the neighbor expired again.

The neighbor finished GR, and the local node changed from restarting to normal.

Failed to resolve the RSVP message.

When the authentication sequence number of the interface reached the upper limit, the sequence number was reset, and the sequence flag bit increased by 1.

An incorrect configuration caused a loop. For example, a device on a TE tunnel is configured with an IP address that is the same as the IP address of an interface along the TE tunnel.

A loop was found during the RSVP loop detection because of incorrect configuration.

During the active/standby switchover, the LSP was not backed up to the SMB after GR.

The local node was configured with self-GR. During the active/standby switchover and GR, the number of LSPs in the License was modified to a value smaller than the number of current LSPs in the SMB.

Failed to obtain the LSR ID from RRO and CSPF during the processing of the Path message.

The interface corresponded to too many neighbors.

The number of sessions reached the maximum during the creation of sessions.

The local node could help the downstream neighboring node to perform GR. When the downstream neighboring node was performing GR, the GR supporting capability or Hello detection was disabled on the local node.

The local node could help the upstream neighboring node to perform GR. When the upstream neighboring node was performing GR, the GR supporting capability or Hello detection was disabled on the local node.

1. Before the active/standby switchover, the GR capability was not configured on the device.

2. No LSP existed on the device.

3. The neighboring node did not have the RSVP GR supporting capability.

4. GR was complete.

1. RSVP GR was configured, but the undo mpls rsvp-te command was run immediately, and then the LSP was not deleted.

2. Before the active/standby switchover, the router already had the RSVP GR capability.

The PSB failed to be updated, causing the clean timer to expire. Between two directly-connected devices, if one directly-connected interface of a device fails, the device cannot send a Path Refresh message. As failing to receiving the Path Refresh message, the other device deletes the TE tunnel after the PSB cleanup timer expires.

The number of CR-LSPs created by the local device reached the maximum.

RSVP messages were not processed in time, and thus the length of the RSVP message list reached the maximum value.

The number of PSBs reached the maximum value specified in the License.

Failed to use the received GR message to reestablish PSB or RSB. Possible causes are as follows:

1. The system had insufficient memory.

2. Routing information on the SMB was lost.

3. The TTL value was smaller than 1.

4. The system detected a loop.

When the local node or the GR supporting node was performing GR, the Recovery timer expired.

When the local node or the GR supporting node was performing GR, the Recovery timer was started.

When the local node or the GR supporting node was performing GR, the Restart timer expired.

When the local node or the GR supporting node was performing GR, the Restart timer was started.

The RSB failed to be updated, causing its cleanup timer to expire. For example, between two directly-connected devices, if one directly-connected interface of a device fails, the device cannot send a Resv Refresh message. As failing to receiving the Resv Refresh message, the other device deletes the TE tunnel after the RSB cleanup timer expires.

Failed to inform the slave board that batch backup ended.