MPLS-RSVP Configuration

Multi-protocol label switch resource reservation protocol (MPLS-RSVP) supports the distribution of MPLS labels. In addition, when transmitting the label binding message, it carries the resource reservation information, used as a signaling protocol to create, delete or modify the tunnel in the MPLS network. In this interface, you can set and query parameters related to MPLS-RSVP.

Navigation Path

In the NE Explorer, click the NE and choose Configuration > Control Plane Configuration > MPLS-RSVP Configuration from the Function Tree.

Guideline

The MPLS-RSVP is a notification mechanism of the resource reservation in the network, which realizes the bandwidth reservation on the control plane. As a label distribution protocol, it is used to set up the LSP in the MPLS network.

Parameters

**Table 1** Descriptions of the parameters for node configuration
Field	Value	Description
GR Status	Enabled, Disabled	If an LSR is restarted and the active/standby switchover is triggered on the LSR due to a fault, its RSVP adjacency to the adjacent LSR is removed because the signaling protocol times out. In this case, the tunnel is also deleted, which results in a temporary network interruption. You can configure the GR function to solve this problem. The GR function can help rebuild the adjacency between adjacent LSRs without stopping the RSVP session. NOTE: It is recommended that you set GR Status to Enabled. If you set GR Status to Disabled, Hello Loss Count in the port attributes must also be set to 100 to avoid unexpected tunnel deletion caused by frequent interruption of RSVP neighboring relationships.
GR Reconnection (s)	90 to 259200	After detecting the reset of a node, the equipment waits for the reconnection to the node. When the reconnection time expires and the reconnection to the node fails, the equipment deletes the label forwarding relationships relevant to the node.
GR Restoration (s)	60 to 259200	After the equipment is started, signaling synchronization is performed among nodes. If the recovery time expires and the signaling synchronization is not complete, the equipment deletes the forwarding relationships that are not synchronized.
Global Trail Lockout Status	Unlocked, Locked	After you lock a trail, the rerouting and global recovery functions are disabled for all dynamic TE tunnels that use the local node as the initial nodes.

**Table 2** Descriptions of the parameters for port configuration
Parameter	Value	Description
Port	Example: Slot-Board Name-Port (Port No.)	Indicates the port where the MPLS-RSVP can be configured.
Retransmission Timer Interval (ms)	500 to 3000	Specifies the timing interval for retrying creating the standby path.
Retransmission Increment (%)	0 to 100	Specifies the increment percentage of retransmission.
Status Timer Refresh Period (ms)	5000 to 2147483647	Specifies the period of refreshing the status timer.
Status Timer Timeout Multiple	3 to 255	Specifies the timeout multiples of the status timer. When consecutive times of not receiving the refresh messages exceed the timeout multiples of the status, the status is deleted.
Authentication Type	No Authentication, the Mode of MD5 Encryption	Specifies the RSVP authentication type.
Authentication Key	Example: A9j*	Specifies the authentication key. NOTE: The authentication key can be set only when the authentication type is the Mode of MD5 Encryption.
Hello Send Interval (s)	1 to 60	Specifies the interval of transmitting hello packets. Hello packets are used for detecting loss of the neighbor nodes or re-setting the RSVP status information of the neighbors.
Hello Loss Count	3 to 255	Specifies the number of the lost hello packets. NOTE: It is recommended that you set GR Status in the RSVP node attributes to Enabled. If you set GR Status to Disabled, Hello Loss Count must also be set to 100 to avoid unexpected tunnel deletion caused by frequent interruption of RSVP neighboring relationships.
RSVP Digest Refresh	Enabled, Disabled	If the entire refreshed message of the RSVP need not be transmitted, the small abstract of the refreshed message can be transmitted to maintain the RSVP status and respond to the RSVP status changes. Refreshing only the RSVP abstract reduces the number of refreshed messages and improves the reliability of the RSVP message transmission, enhancing the resource usage rate.