- Read Me First
- MPLS Traffic Engineering and Enhancements
- MPLS Traffic Engineering Configurable Path Calculation Metric for Tunnels
- MPLS Traffic Engineering--Scalability Enhancements
- MPLS Traffic Engineering--LSP Attributes
- MPLS Traffic Engineering AutoTunnel Mesh Groups
- MPLS Traffic Engineering Verbatim Path Support
- MPLS Traffic Engineering--RSVP Hello State Timer
- MPLS Traffic Engineering Forwarding Adjacency
- MPLS Traffic Engineering Class-based Tunnel Selection
- MPLS Traffic Engineering Interarea Tunnels
- MPLS Traffic Engineering Static IPv6 Routes over MPLS TE IPv4 Tunnels
- MPLS Traffic Engineering Automatic Bandwidth Adjustment for TE Tunnels
- MPLS Traffic Engineering – Bundled Interface Support
- RSVP Refresh Reduction and Reliable Messaging
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering--RSVP Hello State Timer
- Restrictions for MPLS Traffic Engineering--RSVP Hello State Timer
- Information About MPLS Traffic Engineering - Configurable Path Calculation Metric for Tunnels
- How to Configure MPLS Traffic Engineering--RSVP Hello State Timer
- Configuration Examples for MPLS Traffic Engineering--RSVP Hello State Timer
- Additional References
- Feature Information for MPLS Traffic Engineering--RSVP Hello State Timer
- Glossary
MPLS Traffic Engineering--RSVP Hello State Timer
The MPLS Traffic Engineering--RSVP Hello State Timer feature detects when a neighbor is down and quickly triggers a state timeout, which frees resources such as bandwidth that can be reused by other label switched paths (LSPs).
Resource Reservation Protocol (RSVP) hellos can be used to detect when a neighboring node is down. The hello state timer then triggers a state timeout. As a result, network convergence time is reduced, and nodes can forward traffic on alternate paths or assist in stateful switchover (SSO) operation.
- Finding Feature Information
- Prerequisites for MPLS Traffic Engineering--RSVP Hello State Timer
- Restrictions for MPLS Traffic Engineering--RSVP Hello State Timer
- Information About MPLS Traffic Engineering - Configurable Path Calculation Metric for Tunnels
- How to Configure MPLS Traffic Engineering--RSVP Hello State Timer
- Configuration Examples for MPLS Traffic Engineering--RSVP Hello State Timer
- Additional References
- Feature Information for MPLS Traffic Engineering--RSVP Hello State Timer
- Glossary
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for MPLS Traffic Engineering--RSVP Hello State Timer
Perform the following tasks on routers before configuring the MPLS Traffic Engineering--RSVP Hello State Timer feature:
Restrictions for MPLS Traffic Engineering--RSVP Hello State Timer
Information About MPLS Traffic Engineering - Configurable Path Calculation Metric for Tunnels
- Hellos for State Timeout
- Hello Instance
- Hellos for Nonfast-Reroutable TE LSP
- Hellos for Fast-Reroutable TE LSP with Backup Tunnel
- Hellos for Fast-Reroutable TE LSP Without Backup Tunnel
Hellos for State Timeout
When RSVP signals a TE LSP and there is a failure somewhere along the path, the failure can remain undetected for as long as two minutes. During this time, bandwidth is held by the nonfunctioning LSP on the nodes downstream from the point of failure along the path with the state intact. If this bandwidth is needed by headend tunnels to signal or resignal LSPs, tunnels may fail to come up for several minutes thereby negatively affecting convergence time.
Hellos enable RSVP nodes to detect when a neighboring node is not reachable. After a certain number of intervals, hellos notice that a neighbor is not responding and delete its state. This action frees the node’s resources to be reused by other LSPs.
Hellos must be configured both globally on the router and on the specific interface to be operational.
Hello Instance
A hello instance implements RSVP hellos for a given router interface address and a remote IP address. A hello instance is expensive because of the large number of hello requests that are sent and the strains they put on the router resources. Therefore, you should create a hello instance only when it is needed to time out state and delete the hello instance when it is no longer necessary.
Hellos for Nonfast-Reroutable TE LSP
The figure below shows a nonfast-reroutable TE LSP from Router 1 to Router 3 via Router 2.
Assume that the link between Router 1 and Router 2 fails. This type of problem can be detected by various means including interface failure, Interior Gateway Protocol (IGP) (Open Shortest Path First (OSPF) or Intermediate System-to-Intermediate System (IS-IS)), and RSVP hellos. However, sometimes interface failure cannot be detected; for example, when Router 1 and Router 2 are interconnected through a Layer 2 switch. The IGP may be slow detecting the failure. Or there may be no IGP running between Router 1 and Router 2; for example, between two Autonomous System Boundary Routers (ASBRs) interconnecting two autonomous systems.
If hellos were running between Router 1 and Router 2, each router would notice that communication was lost and time out the state immediately.
Router 2 sends a delayed PathTear message to Router 3 so that the state can be deleted on all nodes thereby speeding up the convergence time.
 Note | The PathTear message is delayed one second because on some platforms data is being forwarded even after the control plane is down. |
Router 1 sends a destructive PathError message upstream to Router 0 with error code ROUTING_PROBLEM and error value NO_ROUTE.
LSP1 goes from Router 0 to Router 1 to Router 2 to Router 3; LSP 2 goes from Router 0 to Router 1 to Router 4 to Router 2 to Router 3.
Hellos for Fast-Reroutable TE LSP with Backup Tunnel
The figure below shows a fast reroutable TE LSP with a backup tunnel from Router1 to Router 2 to Router 3.
This TE LSP has a backup tunnel from Router 1 to Router 3 protecting the fast reroutable TE LSP against a failure in the Router 1 to Router 2 link and node Router 2. However, assume that a failure occurs in the link connecting Router 1 to Router 2. If hellos were running between Router 1 and Router 2, the routers would notice that the link is down, but would not time out the state. Router 2 notices the failure, but cannot time out the TE LSP because Router 2 may be a merge point, or another downstream node may be a merge point. Router 1 notices the failure and switches to the backup LSP; however, Router 1 cannot time out the state either.
Note | A hello instance is not created in the preceding scenario because the neighbor is down and the hello instance cannot take action. |
Hellos for Fast-Reroutable TE LSP Without Backup Tunnel
On a fast-reroutable TE LSP with no backup tunnel, a hello instance can be created with the neighbor downstream (next hop (NHOP)). On a nonfast-reroutable TE LSP, a hello instance can be created with the neighbor downstream (NHOP) and the neighbor upstream (previous hop (PHOP)). This is in addition to the existing hellos for Fast Reroute.
Note | If both Fast Reroute and hellos for state timeout hello instances are needed on the same link, only one hello instance is created. It will have the Fast Reroute configuration including interval, missed refreshes, and differentiated services code point (DSCP). When a neighbor is down, Fast Reroute and the hello state timer take action. |
The figure below shows a fast-reroutable TE LSP. without a backup tunnel, from Router 1 (the point of local repair (PLR)), to Router 2 to Router 3.
Assume that a failure occurs in the link connecting Router 1 to Router 3. Router 1 can time out the state for the TE LSP because Router 1 knows there is no backup tunnel. However, Router 2 cannot time out the state because Router 2 does not know whether a backup tunnel exists. Also, Router 2 may be a merge point, and therefore cannot time out the state.
Note | A hello instance is not created in the preceding scenario because the neighbor is down and the hello instance cannot take action. |
How to Configure MPLS Traffic Engineering--RSVP Hello State Timer
Note | The following tasks also enable Fast Reroute; however, this section focuses on the RSVP hello state timer. |
- Enabling the Hello State Timer Globally
- Enabling the Hello State Timer on an Interface
- Setting a DSCP Value on an Interface
- Setting a Hello Request Interval on an Interface
- Setting the Number of Hello Messages that can be Missed on an Interface
- Verifying Hello for State Timer Configuration
Enabling the Hello State Timer Globally
Perform this task to enable the RSVP hello state timer globally to reduce network convergence, allow nodes to forward traffic on alternate paths, or assist in stateful switchover (SSO) operation.
1.
enable
2.
configure
terminal
3.
ip
rsvp
signalling
hello
4.
end
DETAILED STEPS
Enabling the Hello State Timer on an Interface
1.
enable
2.
configure
terminal
3.
interface
type
slot
/
subslot
/
port
[. subinterface-number]
4.
ip
rsvp
signalling
hello
5.
end
DETAILED STEPS
Setting a DSCP Value on an Interface
Perform this task to set a differentiated services code point DSCP value for hello messages on an interface.
1.
enable
2.
configure
terminal
3.
interface
type
slot
/
subslot
/
port
[. subinterface-number]
4.
ip
rsvp
signalling
hello
reroute
dscp
num
5.
end
DETAILED STEPS
Setting a Hello Request Interval on an Interface
1.
enable
2.
configure
terminal
3.
interface
type
slot
/
subslot
/
port
[. subinterface-number]
4.
ip
rsvp
signalling
hello
reroute
refresh
interval
interval-value
5.
end
DETAILED STEPS
Setting the Number of Hello Messages that can be Missed on an Interface
Perform this task to set the number of consecutive hello messages that are lost (missed) before hello declares the neighbor down.
1.
enable
2.
configure
terminal
3.
interface
type
slot
/
subslot
/
port
[. subinterface-number]
4.
ip
rsvp
signalling
hello
reroute
refresh
misses
msg-count
5.
end
DETAILED STEPS
Verifying Hello for State Timer Configuration
1.
enable
2.
show
ip
rsvp
hello
DETAILED STEPS
| Command or Action | Purpose |
|---|
Configuration Examples for MPLS Traffic Engineering--RSVP Hello State Timer
Example
In the following example, the hello state timer is enabled globally and on an interface. Related parameters, including a DSCP value, a refresh interval, and a missed refresh limit, are set on an interface.
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip rsvp signalling hello Router(config)# interface FastEthernet 0/0/0 Router(config-if)# ip rsvp signalling hello Router(config-if)# ip rsvp signalling hello reroute dscp 30 Router(config-if)# ip rsvp signalling hello reroute refresh interval 5000 Router(config-if)# ip rsvp signalling hello reroute refresh misses 5 Router(config-if)# end
The following example verifies the status of the hello state timer (reroute):
Router# show ip rsvp hello
Hello:
Fast-Reroute/Reroute:Enabled
Statistics:Enabled
Graceful Restart:Enabled (help-neighbor only)
Additional References
Related Documents
Standards
|
Standard |
Title |
|---|---|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
|
MIB |
MIBs Link |
|---|---|
|
No new or modified MIBS are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
|
RFC |
Title |
|---|---|
|
RFC 3209 |
Technical Assistance
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for MPLS Traffic Engineering--RSVP Hello State Timer
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
MPLS Traffic Engineering--RSVP Hello State Timer |
Cisco IOS XE Release 2.3 |
The MPLS Traffic Engineering--RSVP Hello State Timer feature detects when a neighbor is down and quickly triggers a state timeout, which frees resources such as bandwidth that can be reused by other label switched paths (LSPs). This feature was integrated into Cisco IOS XE Release 2.3. The following commands were introduced or modified: ip rsvp signalling hello dscp, ip rsvp signalling hello refresh interval, ip rsvp signalling hello refresh misses, ip rsvp signalling hello reroute dscp, ip rsvp signalling hello reroute refresh interval, ip rsvp signalling hello reroute refresh misses, show ip rsvp hello. |
Glossary
autonomous system --A collection of networks that share the same routing protocol and that are under the same system administration.
ASBR --autonomous system boundary router. A router that connects and exchanges information between two or more autonomous systems.
backup tunnel --A Multiprotocol Label Switching (MPLS) traffic engineering tunnel used to protect other (primary) tunnel traffic when a link or node failure occurs.
DSCP --differentiated services code point. Six bits in the IP header, as defined by the Internet Engineering Task Force (IETF). These bits determine the class of service provided to the IP packet.
FRR --Fast Reroute. A mechanism for protecting Multiprotocol Label Switching (MPLS) traffic engineering (TE) label switched paths (LSPs) from link and node failure by locally repairing the LSPs at the point of failure, allowing data to continue to flow on them while their headend routers attempt to establish end-to-end LSPs to replace them. FRR locally repairs the protected LSPs by rerouting them over backup tunnels that bypass failed links or nodes.
graceful restart --A process for helping a neighboring Route Processor (RP) restart after a node failure has occurred.
headend --The router that originates and maintains a given label switched paths (LSP). This is the first router in the LSP’s path.
IGP --Interior Gateway Protocol. Internet protocol used to exchange routing information within an autonomous system. Examples of common Internet IGPs include Internal Gateway Routing Protocol (IGRP), Open Shortest Path First (OSPF), and Routing Information Protocol (RIP).
IS-IS --Intermediate System-to-Intermediate System. Open systems Interconnection (OSI) link-state hierarchical routing protocol whereby Intermediate System (IS) routers exchange routing information based on a single metric to determine network topology.
instance --A mechanism that implements the RSVP hello extensions for a given router interface address and remote IP address. Active hello instances periodically send Hello Request messages, expecting Hello ACK messages in response. If the expected ACK message is not received, the active hello instance declares that the neighbor (remote IP address) is unreachable (that is, it is lost). This can cause LSPs crossing this neighbor to be fast rerouted.
label --A short, fixed-length data identifier that tells switching nodes how to forward data (packets or cells).
LDP --Label Distribution Protocol. The protocol that supports Multiprotocol Label Switching (MPLS) hop-by-hop forwarding by distributing bindings between labels and network prefixes. The Cisco proprietary version of this protocol is the Tag Distribution Protocol (TDP).
LSP --label switched path is a configured connection between two routers, in which Multiprotocol Label Switching (MPLS) is used to carry packets. The LSP is created by the concatenation of one or more label-switched hops, allowing a packet to be forwarded by swapping labels from one MPLS node to another MPLS node.
merge point --The backup tunnel’s tail.
MPLS --Multiprotocol Label Switching. A method for forwarding packets (frames) through a network. MPLS enables routers at the edge of a network to apply labels to packets (frames). ATM switches or existing routers in the network core can switch packets according to the labels.
OSPF --Open Shortest Path First. A link-state routing protocol used for routing.
PLR --point of local repair. The headend of the backup tunnel.
RSVP --Resource Reservation Protocol. A protocol that supports the reservation of resources across an IP network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature (bandwidth, jitter, maximum burst, and so on) of the packet streams they want to receive.
state --Information that a router must maintain about each LSP. The information is used for rerouting tunnels.
tailend --The router upon which an LSP is terminated. This is the last router in the LSP’s path.
TE --traffic engineering. The techniques and processes used to cause routed traffic to travel through the network on a path other than the one that would have been chosen if standard routing methods had been used.
topology --The physical arrangement of network nodes and media within an enterprise networking structure.
tunnel --Secure communications path between two peers, such as two routers.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. © 2004-2011 Cisco Systems, Inc. All rights reserved.
Feedback