RSVP Tunnel Management

RSVP tunnels are flexibly deployed dynamic tunnels. After the source and sink nodes are manually selected, the MPLS protocol automatically calculates tunnel routes. You can specify route restrictions to route the tunnel to the desired path. To keep services secure, you can configure hot backup protection for tunnels.

Navigation Path

In the NE Explorer, choose Configuration > MPLS Management > RSVP Tunnel Management from the navigation tree.

Button Description

Button		Description
Query Switching Status		Queries the switching status of protection group.
Function	Switch to Backup LSP	Switches a service manually from the working LSP to the protection LSP. If the protection LSP is normal, the switching takes place. If the protection LSP fails or must satisfy a switching request of higher priority, the switching does not take place.
Function	Clear Switching	Clears the switching.
Re-optimize		Dynamic optimization of LSPs, namely, the periodic calculation of LSP routes. If the recalculated route is better than the current route, a new LSP is created. Traffic switches from the original LSP to the new LSP, and the original LSP is deleted. When you re-optimize a tunnel, the trails of the tunnel are recalculated. NOTICE: When you reoptimize a tunnel, the service may be interrupted. Exercise caution with this operation.

Shortcut Menu Description

Menu Item	Description
Browse Current Alarms	Displays the browse current alarms window and you can query the current alarms.
Browse History Alarms	Displays the browse historical alarms window and you can query the browse historical alarms.
Alarm Suppression	Displays the alarm suppression dialog box.
Browse Performance	Displays the performance management window where you can browse the current and historical performance data.
Performance Statistics Management	Displays the performance statistics management dialog box where you can create or view performance monitoring instances to browse the current or historical performance data.
Query Running Status	Queries the running status of the tunnel.
Query LSP Status	Queries the running status of the primary and bypass LSPs.
Query Bound PW	Queries the PWs bound to the tunnel.
Configure Hot Standby	Configures a hot standby path for the tunnel.
Cancel Hot Standby	Deletes the hot standby path configured for the tunnel. NOTICE: When you cancel the hot standby path, the service may be interrupted. Exercise caution with this operation.
Query Tunnel Fault Cause	Queries causes when the tunnel is faulty.
Query Actual Tunnel Route	Queries the actual route of the tunnel.
Query Actual Bypass LSP Route	Queries the actual route of the bypass LSP when hot standby protection is configured for the tunnel.
Ping Test	Perform the ping/traceroute test for the tunnel. You can directly use this function to learn Tunnel service connectivity and locate the fault rapidly in the Tunnel service. The only difference is that Traceroute supports detection of transit NEs between the source and sink NEs to obtain the packet loss rate and delay between the source NE and each of the transit NE and determine the fault point, while Ping can check only the connectivity between the source and sink NEs. NOTE: For a dynamic MPLS tunnel, you need to enable the IS-IS protocol for each port on the tunnel. Alternatively, for a static MPLS tunnel, you need to perform a ping or traceroute test on the local NE and configure a static route on the peer NE. Before performing a ping or traceroute test, ensure that Node Type of the tunnel is Ingress.
LSP Traceroute

Parameter Description

**Table 1** Parameters for RSVP tunnels
Parameter	Value	Description
Index	Example: 5	Indicates the unique index automatically allocated to a tunnel.
Tunnel ID	Example: 5	Indicates the unique ID manually allocated to a tunnel.
Tunnel Name	Example: Tunnel01	Indicates the name of a tunnel.
Enable Status	Enabled, Disabled	Indicates the enabling status of a tunnel.
Node Type	Ingress, Transit, Egress	Indicates whether a node is an ingress, transit, or egress. Ingress: indicates the node at which traffic enters a tunnel. Transit: indicates transit nodes on a tunnel. Egress: indicates the node at which traffic leaves a tunnel.
Direction	Unidirectional, Bidirectional	Displays the direction of tunnel.
CIR(Kbit/s)	Example: 1000	Indicates the committed information rate for a service that traverses the tunnel. The packets within this bandwidth range can be completely forwarded. If the rate of the packets entering the queue is smaller than or equal to the CIR, all the packets are forwarded. If the rate of the packets entering the queue is bigger than the CIR, the scheduling algorithm discards packets according to a certain packet loss policy.
CBS(byte)	Example: 1000	When bandwidths are insufficient, some packets cannot enter the queue immediately. A buffer is required for them. The buffer stores such packets until there are sufficient bandwidths to forward these packets. The buffer size equals the committed burst size (CBS), that is, the value of this parameter. If the size of data stored in the buffer is smaller than the CBS, the data can be fully sent without packet loss.
PIR(Kbit/s)	Example: 4000	Specifies the peak information rate for a service. The rules for setting this parameter are as follows: The value of this parameter cannot exceed the maximum bandwidth provided by the physical port. In addition, the specified PIR must contain the bandwidth for transmitting overheads. The PIR cannot be smaller than the CIR. If the PIR is excessively low, the excess traffic over the PIR is discarded. If the PIR is set to 0 for a service, the service is unavailable.
PBS(byte)	Example: 1000	Sets the maximum traffic size for the excessive burst. The maximum burst size should not be less than the extra burst buffer size.
Bandwidth Remaining(Kbit/s)	Example: 4000	Indicates the remaining tunnel bandwidth after the tunnel carries the services.
Source Node	Example: 189.9.100.171	Indicates the source node of a tunnel.
Sink Node	Example: 126.9.11.22	Indicates the sink node of a tunnel.
Protection Type	None, Hot Standby	Hot standby: A backup lsp is created immediately after a primary lsp is set up. If the primary lsp fails, services will be switched to the backup lsp. If the primary lsp restores, services will be switched back to the primary lsp. None: Backup lsp is not configured and the Bypass LSP State displays Invalid.
Rerouting Status	Enabled, Disabled	Specifies whether to enable rerouting. When rerouting is enabled, the U2000 Web LCT immediately re-calculates routes and selects a backup link to forward packets if a fault is detected at the physical or link layer.
EXP	None, 0, 1, 2, 3, 4, 5, 6, 7	Indicates the level of EXP. 7 indicates the highest level.
LSP Status	E-LSP, L-LSP	E-LSP indicates that the tunnel determines the scheduling priority and discarding priority of packets based on the EXP information. One MPLS tunnel of the E-LSP type supports a maximum of eight types of PWs. L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets based on the EXP information. In one MPLS tunnel of the L-LSP type, there is only one type of PWs.
Cos	CS7, CS6, EF, AF4, AF3, AF2, AF1, BE	The CoS parameter indicates the class of service. Eight CoS values, that is, CS7, CS6, EF, AF4, AF3, AF2, AF1, and BE, are available according to the standard. Different CoS values correspond to different queues. The equipment provides different QoS for queues of different CoS. CS6-CS7: Indicates the highest service class. The CoS is applicable to transport of signaling. EF: Indicates fast forwarding. The CoS is applicable to the service of little delay and packet loss rate, such as the audio and video services. AF1-AF4: Indicates the guaranteed forwarding. The CoS is applicable to the service that requires a certain rate, but does not limit the delay or jitter. BE: Indicates the traffic that does not need to be processed exceptionally. NOTE: This parameter can be set only when LSP Status is L-LSP.
Setup Priority	0, 1, 2, 3, 4, 5, 6, 7	Set this parameter according to network planning. When resources are insufficient, the tunnel with a higher setup priority can preempt the bandwidth resources of other tunnels during establishment. A smaller value indicates a higher priority, the value 0 indicates the highest priority.
Hold Priority	0, 1, 2, 3, 4, 5, 6, 7	After a tunnel with a higher hold priority is established, the resources of this tunnel are less likely to be preempted when the resources of other tunnels are insufficient. A smaller value indicates a higher priority, the value 0 indicates the highest priority. NOTE: The hold priority should be higher than the setup priority.
Color	Example: 0x120000AA	Indicates the color of a tunnel. RSVP tunnels are color-coded using 32-bit vectors. By comparing the 32 bits, the U2000 Web LCT can determine whether different tunnels use the same color. After a color is selected for a tunnel, the U2000 Web LCT will select a link color-coded the same in the case of tunnel rerouting.
Mask	Example: 0x440000BB
Running State	Up, Down, Fail, Partial up	Indicates the running status of the tunnel.
Primary LSP State	Up, Down	Indicates the running status of the primary LSP.
Bypass LSP State	Up, Down, Invalid	Indicates the running status of the bypass LSP. NOTE: If Protection Type is set to None, Bypass LSP State is Invalid.
Tunnel Type	Master, Bypass	Specifies whether the tunnel is a primary or backup tunnel.
Tunnel Bandwidth Limitation	Enabled, Disabled	Specifies whether bandwidth limitation is enabled for tunnels.
Re-routing Optimization	Enabled, Disabled	Specifies whether tunnels are automatically re-optimized to the optimal routes to maximize the efficiency of network resources.
Re-optimization Interval(s)	Example: 3600	Indicates the route re-optimization interval.
Tunnel Binding Policy	Bind, Unbind	Indicates the policy used for binding MPLS tunnels. If you set this parameter to Bind, the tunnel can be bound only to static services. If you set this parameter to Unbind, the tunnel can only be automatically selected by services.

**Table 2** Parameters for route restrictions
Parameter	Value	Description
Route Restriction IP	Example: 5	The interface IP address of the NE configured with route constraints
Route Restriction Type	Exclude, Include-loose, Include-strict	The mode that a tunnel uses to traverse an interface. Excluded: The tunnel does not traverse the specified Interface. Include-loose: A tunnel must traverse the Interface of the route restriction objects. In addition, the actual route of the tunnel must traverse the objects in the same sequence as the objects are listed in the route restriction table. In the Include-loose mode, the Interface of the route restriction objects can be reached through multiple hops. Include-strict: A tunnel must traverse the Interface of the route restriction objects. In addition, the actual route of the tunnel must traverse the objects in the same sequence as the objects are listed in the route restriction table. In the Include-strict mode, the Interface of the route restriction object must be reached through one hop.

**Table 3** Parameters for protection attributes
Parameter	Value	Description
Revertive Mode	Revertive, Non-Revertive	Determines whether the services are switched back to the original working tunnel after the fault is rectified. Revertive: After the fault is rectified, the services are switched back to the working tunnel. Non-Revertive: After the fault is rectified, the services are not switched back to the working tunnel.
WTR Time(s)	0 to 60	When the working tunnel is restored, the services are switched to the working tunnel after the WTR time elapses.
Switching Status	In-primary, In-secondary	Indicates the current switching status of protection group.
Switching Detailed Information	Invalid, Force, Signal fail, Wait to restore, Do not revert mode	Indicates details about switching.
Primary LSP State	Up, Down	Indicates the running status of the primary LSP.
Bypass LSP State	Up, Down, Invalid	Indicates the running status of the bypass LSP. NOTE: If Protection Type is set to None, Bypass LSP State is Invalid.

**Table 4** Parameters for query tunnel fault cause
Parameter	Value	Description
Tunnel Index	Example: 1	Indicates the unique index automatically allocated to a tunnel.
Failure Cause	String	Indicates the fault cause of a failure tunnel.
Failure Node	Example: 1.1.2.3	Indicates the fault node of a failure tunnel.
Cause of a Renegotiation Failure	String	Indicates the failure cause of recalculated route for a tunnel.
Node of a Renegotiation Failure	Example: 1.1.2.3	Indicates the fault node of recalculated route for a tunnel.

**Table 5** Descriptions of the parameters for Ping Test
Field	Value	Description
Packet Count	Example: 3	Set the count of packets.
EXP Value	0-7	Set the EXP value. The packet priority increases with the EXP value.
TTL	1-255	Sets the live of detection packets. Each time when the detection packets traverse an NE, the TTL value is decreased by 1. When the TTL value is decreased to 0, the detection packets are discarded.
Transmit Interval (10ms)	10-1000	Set the interval for transmitting detection packets.
Packet Length	65-1400	Set the length of packets (step: 4).
Wait-to-Response Timeout Time (10ms)	50-6000	After the local end sends detection packets, if the local end does not receive the respond packets from the opposite end within the set response timeout period, it indicates that the link fails. NOTE: The value range of the response timeout period varies according to the NE type. If the response timeout period is beyond the range, an error message is displayed on the NMS.
Response Mode	No Response, IPv4 UDP Response, Application Control Channel	IPv4 UDP Response: The source NE sends ping packets. The sink NE returns response packets to the source NE through the dynamic link. The source NE reports the ping test result. When you select IPv4 UDP Response, the protocol of ISIS must be enabled. No Response: The source NE sends ping packets. The sink NE does not return response packets to the source NE after receiving the ping packets. Instead, the sink NE reports the ping test result. Application Control Channel: The source NE sends ping packets. The sink NE returns response packets through the static reverse tunnel. The source NE reports the ping test result. NOTE: Set Response Mode according to the following rules: If the tunnel is a unidirectional static tunnel, setting Response Mode to No Response is recommended. If the tunnel is a bidirectional static tunnel, setting Response Mode to Application Control Channel is recommended. If the tunnel is a dynamic tunnel, setting Response Mode to IPv4 UDP Response is recommended.
Test Result	Character string	Display the test result.

NOTE:

The parameters for LSP traceroute test can refer to Ping test.