MPLS and RSVP
This chapter provides information to configure MPLS and RSVP.
MPLS
Multiprotocol Label Switching (MPLS) is a label switching technology that provides the ability to set up connection-oriented paths over a connectionless IP network. MPLS facilitates network traffic flow and provides a mechanism to engineer network traffic patterns independently from routing tables. MPLS sets up a specific path for a sequence of packets. The packets are identified by a label inserted into each packet. MPLS is not enabled by default and must be explicitly enabled.
MPLS is independent of any routing protocol but is considered multiprotocol because it works with the Internet Protocol (IP) and frame relay network protocols.
The 7210 SAS routers enable service providers to deliver virtual private networks (VPNs) and Internet access using MPLS tunnels, with Ethernet interfaces.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, is designed to fit into a network using the principles of seamless MPLS architecture which enable access devices with smaller IP routing scale (both control-plane RIB and FIB) and smaller MPLS scale (both control-plane and FIB) to be used to deploy MPLS end-to-end and benefit from the traffic engineering and resiliency mechanism that MPLS provides. The MPLS features and capabilities available on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C are described in this user guide.
MPLS label stack
MPLS requires a set of procedures to enhance network layer packets with label stacks, which turns them into labeled packets. Routers that support MPLS are called Label Switching Routers (LSRs). To transmit a labeled packet on a specific data link, an LSR must support the encoding technique which, when given a label stack and a network layer packet, produces a labeled packet.
In MPLS, packets can carry not just one label, but a set of labels in a stack. An LSR can swap the label at the top of the stack, pop the stack, or swap the label and push one or more labels into the stack. The processing of a labeled packet is completely independent of the level of hierarchy. The processing is always based on the top label, without regard for the possibility that some number of other labels may have been above it in the past, or that some number of other labels may be below it at present.
As described in RFC 3032, MPLS Label Stack Encoding, the label stack is represented as a sequence of label stack entries. Each label stack entry is represented by 4 octets. The following figure shows the label placement in a packet. Packet/label field description describes the fields.
Field |
Description |
|---|---|
Label |
This 20-bit field carries the actual value (unstructured) of the label. |
Exp |
This 3-bit field is reserved for experimental use. It is currently used for Class of Service (CoS). |
S |
This bit is set to 1 for the last entry (bottom) in the label stack, and 0 for all other label stack entries. |
TTL |
This 8-bit field is used to encode a TTL value. |
A stack can carry several labels, organized in a last in/first out order. The top of the label stack appears first in the packet and the bottom of the stack appears last (as shown in the following figure).
The label value at the top of the stack is looked up when a labeled packet is received. A successful lookup reveals the following:
the next hop where the packet is to be forwarded
the operation to be performed on the label stack before forwarding
In addition, the lookup may reveal outgoing data link encapsulation and other information needed to properly forward the packet.
An empty label stack can be thought of as an unlabeled packet. An empty label stack has zero (0) depth. The label at the bottom of the stack is referred to as the Level 1 label. The label above it (if it exists) is the Level 2 label, and so on. The label at the top of the stack is referred to as the Level m label.
Labeled packet processing is independent of the level of hierarchy. Processing is always based on the top label in the stack which includes information about the operations to perform on the packet's label stack.
Label values
Packets travelling along an LSP (see Label Switching Routers) are identified by its label, the 20-bit, unsigned integer. The range is 0 through 1,048,575. Label values 0-15 are reserved and are defined below as follows:
A value of 0 represents the IPv4 Explicit NULL Label. This Label value is legal only at the bottom of the Label stack. It indicates that the Label stack must be popped, and the packet forwarding must be based on the IPv4 header.
A value of 1 represents the router alert Label. This Label value is legal anywhere in the Label stack except at the bottom. When a received packet contains this Label value at the top of the Label stack, it is delivered to a local software module for processing. The actual packet forwarding is determined by the Label beneath it in the stack. However, if the packet is further forwarded, the router alert Label should be pushed back onto the Label stack before forwarding. The use of this Label is analogous to the use of the router alert option in IP packets. Because this Label cannot occur at the bottom of the stack, it is not associated with a particular network layer protocol.
A value of 3 represents the Implicit NULL Label. This is a Label that a Label Switching Router (LSR) can assign and distribute, but which never actually appears in the encapsulation. When an LSR would otherwise replace the Label at the top of the stack with a new Label, but the new Label is Implicit NULL, the LSR pops the stack instead of doing the replacement. Although this value may never appear in the encapsulation, it needs to be specified in the RSVP, so a value is reserved.
Values 4-15 are reserved for future use.
7210 SAS devices use labels for MPLS, RSVP-TE, and LDP, as well as packet-based services such as VLL and VPLS.
Label values 16 through 1,048,575 are defined as follows:
Label values 16 through 31 are reserved for future use.
Label values 32 through 1,023 are available for static assignment.
Label values 1,024 through 2,047 are reserved for future use.
Label values 2,048 through 18,431 are statically assigned for services.
Label values 32768through 131,071 are dynamically assigned for both MPLS and services.
Label values 131,072 through 1,048,575 are reserved for future use.
Label Switching Routers
LSRs perform the label switching function. LSRs perform different functions based on it's position in an LSP. Routers in an LSP do one of the following:
The router at the beginning of an LSP is the ingress label edge router (ILER). The ingress router can encapsulate packets with an MPLS header and forward it to the next router along the path. An LSP can only have one ingress router.
A Label Switching Router (LSR) can be any intermediate router in the LSP between the ingress and egress routers. An LSR swaps the incoming label with the outgoing MPLS label and forwards the MPLS packets it receives to the next router in the MPLS path (LSP). An LSP can have 0-253 transit routers.
The router at the end of an LSP is the egress label edge router (ELER). The egress router strips the MPLS encapsulation which changes it from an MPLS packet to a data packet, and then forwards the packet to its final destination using information in the forwarding table. Each LSP can have only one egress router. The ingress and egress routers in an LSP cannot be the same router.
A router in your network can act as an ingress, egress, or transit router for one or more LSPs, depending on your network design.
An LSP is confined to one IGP area for LSPs using constrained-path. They cannot cross an autonomous system (AS) boundary.
Static LSPs can cross AS boundaries. The intermediate hops are manually configured so the LSP has no dependence on the IGP topology or a local forwarding table.
LSP types
The following are LSP types:
static LSPs
A static LSP specifies a static path. All routers that the LSP traverses must be configured manually with labels. No signaling such as RSVP or LDP is required.
signaled LSP
LSPs are set up using a signaling protocol such as RSVP-TE or LDP. The signaling protocol allows labels to be assigned from an ingress router to the egress router. Signaling is triggered by the ingress routers. Configuration is required only on the ingress router and is not required on intermediate routers. Signaling also facilitates path selection.
There are two signaled LSP types:
explicit-path LSPs
MPLS uses RSVP-TE to set up explicit path LSPs. The hops within the LSP are configured manually. The intermediate hops must be configured as either strict or loose meaning that the LSP must take either a direct path from the previous hop router to this router (strict) or can traverse through other routers (loose). You can control how the path is set up. They are similar to static LSPs but require less configuration. See RSVP.
constrained-path LSPs
The intermediate hops of the LSP are dynamically assigned. A constrained path LSP relies on the Constrained Shortest Path First (CSPF) routing algorithm to find a path which satisfies the constraints for the LSP. In turn, CSPF relies on the topology database provided by the extended IGP such as OSPF or IS-IS.
When the path is found by CSPF, RSVP uses the path to request the LSP set up. CSPF calculates the shortest path based on the constraints provided such as bandwidth, class of service, and specified hops.
If fast reroute is configured, the ingress router signals the routers downstream. Each downstream router sets up a detour for the LSP. If a downstream router does not support fast reroute, the request is ignored and the router continues to support the LSP. This can cause some of the detours to fail, but otherwise the LSP is not impacted.
No bandwidth is reserved for the rerouted path. If the user enters a value in the bandwidth parameter in the config>router>mpls>lsp>fast-reroute context, it has no effect on the LSP backup LSP establishment.
Hop-limit parameters specifies the maximum number of hops that an LSP can traverse, including the ingress and egress routers. An LSP is not set up if the hop limit is exceeded. The hop count is set to 255 by default for the primary and secondary paths. It is set to 16 by default for a bypass or detour LSP path.
The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C support the following functionality:
MPLS LSR functionality.
MPLS LER functionality with the following support:
Static LSPs.
RSVP signaled LSPs with support for both explicit-path LSP and constrained-path LSPs.
Support for FRR one-to-one and FRR facility bypass for RSVP signaled LSPs.
MPLS pseudowire hash label support
The MPLS pseudowire hash label allows LSR nodes in a network to load balance labeled packets in a more granular manner than by hashing on the standard label stack. Using the hash label also removes the need to have an LSR inspect the payload below the label stack to check for an IPv4 or IPv6 header.
In packets forwarded over an LSP, an MPLS hash label is inserted by the ingress LER at the bottom of the label stack. The label value is the result of the hash of the packet headers (the packet header fields that are used depend on the capability of the ingress LER node). The ingress LER hash routine guarantees that the spraying of packets by an LSR hashing on the extended label stack, which includes the hash label, maintains packet ordering within a conversation. LSR hashing pertains to multiple LDP ECMP paths or multiple paths over a LAG network port.
-
On 7210 SAS devices, the ingress node does not use the pseudowire hash label for ECMP hashing and LAG hashing. It is available for use by the transit MPLS LSR nodes. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Interface Configuration Guide for a description of the fields used by the ingress LER for ECMP and LAG hashing.
The pseudowire hash label is supported for VLL services with spoke-SDP, VPLS services with spoke-SDP and mesh SDP, and RVPLS services with spoke-SDP.
When a hash label is added at the ingress LER, it is marked with an LSP EXP value of 0.
- The pseudowire hash label is not accounted for the in the total number of MPLS transport and service labels that the node pushes and pops.
MPLS facility bypass method of MPLS Fast Re-Route (FRR)
The MPLS facility bypass method of MPLS Fast Re-Route (FRR) functionality is extended to the ingress node.
The behavior of an LSP at an ingress LER with both fast reroute and a standby LSP path configured is as follows:
when a down stream detour becomes active at a point of local repair (PLR)
The ingress LER switches to the standby LSP path. If the primary LSP path is repaired subsequently at the PLR, the LSP switches back to the primary path. If the standby goes down, the LSP is switched back to the primary, even though it is still on the detour at the PLR. If the primary goes down at the ingress while the LSP is on the standby, the detour at the ingress is cleaned up and for one-to-one detours a "path tear" is sent for the detour path. In other words, the detour at the ingress does not protect the standby. If and when the primary LSP is again successfully re-signaled, the ingress detour state machine is restarted.
when the primary fails at the ingress
The LSP switches to the detour path. If a standby is available then LSP would switch to standby on expiration of hold-timer. If hold-timer is disabled then switchover to standby would happen immediately. On successful global revert of primary path, the LSP would switch back to the primary path.
Admin groups are not taken into account when creating detours for LSPs.
Manual bypass LSP
The 7210 SAS supports Manual bypass tunnels, on implementation of the Manual bypass feature a LSP can be preconfigured from a PLR which is used exclusively for bypass protection. If a path message for a new LSP requests for bypass protection, the node checks if a manual bypass tunnel satisfying the path constraints exists. If a tunnel is found, it is selected. If no such tunnel exists by default, the 7210 SAS dynamically signals a bypass LSP.
Users can disable the dynamic bypass creation on a per node basis using the CLI.
A maximum of 1000 associations of primary LSP paths can be made with a single manual bypass at the PLR node. If dynamic bypass creation is disabled on the node, it is recommended to configure additional manual bypass LSPs to handle the required number of associations.
PLR bypass LSP selection rules
The following figure shows the bypass tunnel nodes.
The PLR uses the following rules to select a bypass LSP among multiple manual and dynamic bypass LSPs at the time of establishment of the primary LSP path or when searching for a bypass for a protected LSP which does not have an association with a bypass tunnel:
The MPLS/RSVP task in the PLR node checks if an existing manual bypass satisfies the constraints. If the path message for the primary LSP path indicated node protection is needed, which is the default LSP FRR setting at the head end node, MPLS/RSVP task searches for a node-protect' bypass LSP. If the path message for the primary LSP path indicated link protection is needed, then it searches for a link-protect bypass LSP.
If multiple manual bypass LSPs satisfying the path constraints exist, it prefers a manual-bypass terminating closer to the PLR over a manual bypass terminating further away. If multiple manual bypass LSPs satisfying the path constraints terminate on the same downstream node, it selects one with the lowest IGP path cost or if in a tie, picks the first one available.
If none satisfies the constraints and dynamic bypass tunnels have not been disabled on PLR node, then the MPLS/RSVP task in the PLR checks if any of the already established dynamic bypasses of the requested type satisfies the constraints.
If none do, then the MPLS/RSVP task asks CSPF to check if a new dynamic bypass of the requested type, node-protect or link-protect, can be established.
If the path message for the primary LSP path indicated node protection is needed, and no manual bypass was found after Step 1, or no dynamic bypass LSP was found after 3 attempts of performing Step 3, the MPLS/RSVP task repeats Steps 1-3 looking for a suitable link-protect bypass LSP. If none are found, the primary LSP has no protection and the PLR node must clear the "local protection available" flag in the IPv4 address sub-object of the RRO starting in the next Resv refresh message it sends upstream.
If the path message for the primary LSP path indicated link protection is needed, and no manual bypass was found after step 1, or no dynamic bypass LSP was found after performing Step 3, the primary LSP has no protection and the PLR node must clear the "local protection available" flag in the IPv4 address sub-object of the RRO starting in the next RESV refresh message it sends upstream. The PLR does not search for a node-protect' bypass LSP in this case.
If the PLR node successfully makes an association, it must set the "local protection available" flag in the IPv4 address sub-object of the RRO starting in the next RESV refresh message it sends upstream.
For all primary LSP that requested FRR protection but are not currently associated with a bypass tunnel, the PLR node on reception of RESV refresh on the primary LSP path repeats Steps 1-7.
If the user disables dynamic-bypass tunnels on a node while dynamic bypass tunnels were activated and were passing traffic, traffic loss occurs on the protected LSP. Furthermore, if no manual bypass exist that satisfy the constraints of the protected LSP, the LSP remains without protection.
If the user configures a bypass tunnel on node B and dynamic bypass tunnels have been disabled, LSPs which have been previously signaled and which were not associated with any manual bypass tunnel, for example, none existed, are associated with the manual bypass tunnel if suitable. The node checks for the availability of a suitable bypass tunnel for each of the outstanding LSPs every time a RESV message is received for these LSPs.
If the user configures a bypass tunnel on node B and dynamic bypass tunnels have not been disabled, LSPs which have been previously signaled over dynamic bypass tunnels are not automatically switched into the manual bypass tunnel even if the manual bypass is a more optimized path. The user has to perform a make before break at the head end of these LSPs.
If the manual bypass goes into the down state in node B and dynamic bypass tunnels have been disabled, node B (PLR) clears the "protection available" flag in the RRO IPv4 sub-object in the next RESV refresh message for each affected LSP. It then tries to associate each of these LSPs with one of the manual bypass tunnels that are still up. If it finds one, it makes the association and sets the "protection available" flag again in the next RESV refresh message for each of these LSPs. If it could not find one, it keeps checking for one every time a RESV message is received for each of the remaining LSPs. When the manual bypass tunnel is back UP, the LSPs which did not find a match are associated back to this tunnel and the protection available flag is set starting in the next RESV refresh message.
If the manual bypass goes into the down state in node B and dynamic bypass tunnels have not been disabled, node B automatically signals a dynamic bypass to protect the LSPs if a suitable one does not exist. Similarly, if an LSP is signaled while the manual bypass is in the down state, the node only signals a dynamic bypass tunnel if the user has not disabled dynamic tunnels. When the manual bypass tunnel is back into the UP state, the node does not switch the protected LSPs from the dynamic bypass tunnel into the manual bypass tunnel.
FRR node-protection (facility)
The MPLS Fast Re-Route (FRR) functionality enables PLRs to be aware of the missing node protection and allows them to regularly probe for a node-bypass. The following figure describes an LSP scenario.
Where:
LSP 1 - between PE_1 to PE_2, with CSPF, FRR facility node-protect enabled
P_1 protects P_2 with bypass-nodes P_1 -P_3 - P_4 - PE_4 -PE_2
If P_4 fails, P_1 tries to establish the bypass-node three times
When the bypass-node creation fails, P_1 protects link P_1-P_2
P_1 protects the link to P_2 through P_1 - P_5 - P_2
P_4 returns online
As LSP 1 had requested node protection, but because of a lack of any available path, it could only obtain link protection. Therefore, every 60 seconds the PLR for LSP 1 searches for a new path that may be able to provide node protection. When P_4 is back online and such a path is available, a new bypass tunnel is signaled and LSP 1 is associated with this new bypass tunnel.
Uniform FRR failover time
The failover time during FRR consists of a detection time and a switchover time. The detection time corresponds to the time it takes for the RSVP control plane protocol to detect that a network IP interface is down or that a neighbor/next-hop over a network IP interface is down. The control plane can be informed of an interface down event when the event is because of a failure in a lower layer such in the physical layer. The control plane can also detect the failure of a neighbor/next-hop on its own by running a protocol such as Hello, Keep-Alive, or BFD.
The switchover time is measured from the time the control plane detected the failure of the interface or neighbor/next-hop to the time the IOM completed the reprogramming of all the impacted ILM or service records in the datapath. This includes the time it takes for the control plane to send a down notification to all IOMs to request a switch to the backup NHLFE.
Uniform Fast-Reroute (FRR) failover enables the switchover of MPLS and service packets from the outgoing interface of the primary LSP path to that of the FRR backup LSP within the same amount of time regardless of the number of LSPs or service records. This is achieved by updating Ingress Label Map (ILM) records and service records to point to the backup Next-Hop Label to Forwarding Entry (NHLFE) in a single operation.
RSVP
The Resource Reservation Protocol (RSVP) is a network control protocol used by a host to request specific qualities of service from the network for particular application data streams or flows. RSVP is also used by routers to deliver quality of service (QoS) requests to all nodes along the paths of the flows and to establish and maintain state to provide the requested service. RSVP requests generally result in resources reserved in each node along the datapath. MPLS leverages this RSVP mechanism to set up traffic engineered LSPs. RSVP is not enabled by default and must be explicitly enabled.
RSVP requests resources for simplex flows. It requests resources only in one direction (unidirectional). Therefore, RSVP treats a sender as logically distinct from a receiver, although the same application process may act as both a sender and a receiver at the same time. Duplex flows require two LSPs, to carry traffic in each direction.
RSVP is not a routing protocol. RSVP operates with unicast and multicast routing protocols. Routing protocols determine where packets are forwarded. RSVP consults local routing tables to relay RSVP messages.
RSVP uses two message types to set up LSPs, PATH and RESV. Establishing LSPs shows the process to establish an LSP as follows:
The sender (the ingress LER (ILER)), sends PATH messages toward the receiver, (the egress LER (ELER)) to indicate the FEC for which label bindings are needed. PATH messages are used to signal and request label bindings required to establish the LSP from ingress to egress. Each router along the path observes the traffic type.
PATH messages facilitate the routers along the path to make the necessary bandwidth reservations and distribute the label binding to the router upstream.
The ELER sends label binding information in the RESV messages in response to PATH messages received.
The LSP is considered operational when the ILER receives the label binding information.
Figure 5. Establishing LSPs 
The following figure shows an example of an LSP path set up using RSVP. The ingress label edge router (ILER 1) transmits an RSVP path message (path: 30.30.30.1) downstream to the egress label edge router (ELER 4). The path message contains a label request object that requests intermediate LSRs and the ELER to provide a label binding for this path.
Figure 6. LSP using RSVP path set up 
In addition to the label request object, an RSVP PATH message can also contain a number of optional objects:
explicit route object (ERO)
When the ERO is present, the RSVP path message is forced to follow the path specified by the ERO (independent of the IGP shortest path).
record route object (RRO)
Allows the ILER to receive a listing of the LSRs that the LSP tunnel actually traverses.
A session attribute object controls the path set up priority, holding priority, and local-rerouting features.
Upon receiving a path message containing a label request object, the ELER transmits a RESV message that contains a label object. The label object contains the label binding that the downstream LSR communicates to its upstream neighbor. The RESV message is sent upstream toward the ILER, in a direction opposite to that followed by the path message. Each LSR that processes the RESV message carrying a label object uses the received label for outgoing traffic associated with the specific LSP. When the RESV message arrives at the ingress LSR, the LSP is established.
Using RSVP for MPLS
Hosts and routers that support both MPLS and RSVP can associate labels with RSVP flows. When MPLS and RSVP are combined, the definition of a flow can be made more flexible. When an LSP is established, the traffic through the path is defined by the label applied at the ingress node of the LSP. The mapping of label to traffic can be accomplished using a variety of criteria. The set of packets that are assigned the same label value by a specific node are considered to belong to the same FEC which defines the RSVP flow.
For use with MPLS, RSVP already has the resource reservation component built-in which makes it ideal to reserve resources for LSPs.
RSVP Traffic Engineering extensions for MPLS
RSVP has been extended for MPLS to support automatic signaling of LSPs. To enhance the scalability, latency, and reliability of RSVP signaling, several extensions have been defined. Refresh messages are still transmitted but the volume of traffic, the amount of CPU utilization, and response latency are reduced while reliability is supported. None of these extensions result in backward compatibility problems with traditional RSVP implementations.
Hello protocol
The Hello protocol detects the loss of a neighbor node or the reset of a neighbor’s RSVP state information. In standard RSVP, neighbor monitoring occurs as part of the RSVP soft-state model. The reservation state is maintained as cached information that is first installed and then periodically refreshed by the ingress and egress LSRs. If the state is not refreshed within a specified time interval, the LSR discards the state because it assumes that either the neighbor node has been lost or its RSVP state information has been reset.
The Hello protocol extension is composed of a hello message, a hello request object and a hello ACK object. Hello processing between two neighbors supports independent selection of failure detection intervals. Each neighbor can automatically issue hello request objects. Each hello request object is answered by a hello ACK object.
MD5 authentication of RSVP interface
When enabled on an RSVP interface, authentication of RSVP messages operates in both directions of the interface.
A node maintains a security association with its neighbors for each authentication key. The following items are stored in the context of this security association:
the HMAC-MD5 authentication algorithm
key used with the authentication algorithm
lifetime of the key. A key is user-generated key using a third party software/hardware and enters the value as static string into CLI configuration of the RSVP interface. The key continues to be valid until it is removed from that RSVP interface.
source address of the sending system
latest sending sequence number used with this key identifier
The RSVP sender transmits an authenticating digest of the RSVP message, computed using the shared authentication key and a keyed-hash algorithm. The message digest is included in an Integrity object which also contains a Flags field, a Key Identifier field, and a Sequence Number field. The RSVP sender complies to the procedures for RSVP message generation in RFC 2747, RSVP Cryptographic Authentication.
An RSVP receiver uses the key together with the authentication algorithm to process received RSVP messages.
When a PLR node switches the path of the LSP to a bypass LSP, it does not send the integrity object in the RSVP messages over the bypass tunnel. If an integrity object is received from the MP node, then the message is discarded because there is no security association with the next-next-hop MP node.
The MD5 implementation does not support the authentication challenge procedures in RFC 2747.
Reservation styles
LSPs can be signaled with explicit reservation styles. A reservation style is a set of control options that specify a number of supported parameters. The style information is part of the LSP configuration. SR OS supports two reservation styles:
Note that if FRR option is enabled for the LSP and selects the facility FRR method at the head-end node, only the SE reservation style is allowed. Furthermore, if a PLR node receives a path message with fast-reroute requested with facility method and the FF reservation style, it rejects the reservation. The one-to-one detour method supports both FF and SE styles.
RSVP message pacing
When a flood of signaling messages arrive because of topology changes in the network, signaling messages can be dropped which results in longer set up times for LSPs. RSVP message pacing controls the transmission rate for RSVP messages, allowing the messages to be sent in timed intervals. Pacing reduces the number of dropped messages that can occur from bursts of signaling messages in large networks.
RSVP overhead refresh reduction
The RSVP refresh reduction feature consists of the following capabilities implemented in accordance to RFC 2961, RSVP Refresh Overhead Reduction Extensions:
RSVP message bundling
This capability is intended to reduce overall message handling load. The 7210 SAS supports receipt and processing of bundled message only, but no transmission of bundled messages.
reliable message delivery
This capability consists of sending a message-id and returning a message-ack for each RSVP message. It can be used to detect message loss and support reliable RSVP message delivery on a per hop basis. It also helps reduce the refresh rate because the delivery becomes more reliable.
summary refresh
This capability consists of refreshing multiples states with a single message-id list and sending negative ACKs (NACKs) for a message_id which could not be matched. The summary refresh capability reduces the amount of messaging exchanged and the corresponding message processing between peers. It does not, however, reduce the amount of soft state to be stored in the node.
These capabilities can be enabled on a per-RSVP-interface basis are referred to collectively as "refresh overhead reduction extensions". When the refresh-reduction is enabled on an RSVP interface, the node indicates this to its peer by setting a refresh-reduction- capable bit in the flags field of the common RSVP header. If both peers of an RSVP interface set this bit, all the above three capabilities can be used. Furthermore, the node monitors the settings of this bit in received RSVP messages from the peer on the interface. As soon as this bit is cleared, the node stops sending summary refresh messages. If a peer did not set the "refresh-reduction-capable" bit, the node does not attempt to send summary refresh messages.
Configuring implicit null
The implicit null label option allows a router egress LER to receive MPLS packets from the previous hop without the outer LSP label. The operation of the previous hop is referred to as Penultimate Hop Popping (PHP).
This option is signaled by the egress LER to the previous hop during the LSP signaling with RSVP control protocol. In addition, the egress LER can be configured to receive MPLS packet with the implicit null label on a static LSP.
The user can configure your router to signal the implicit null label value over all RSVP interfaces and for all RSVP LSPs for which this node is the egress LER using the implicit-null-label command in the config>router>rsvp context. The user must shutdown RSVP before being able to change the implicit null configuration option.
All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface signals the implicit null label. This means that if the egress LER is also the merge-point (MP) node, then the incoming interface for the path refresh message over the bypass dictates if the packet uses the implicit null label or not. The same applies for a 1-to-1 detour LSP.
The implicit null label option is also supported on a static label LSP. The following commands can be used to cause the node to push or to swap to an implicit null label on the MPLS packet:
config>router>mpls>static-lsp>push implicit-null-label nexthop ip-address
config>router>mpls>if>label-map>swap implicit-null-label nexthop ip-address
Using unnumbered Point-to-Point interface in RSVP
This feature introduces the use of unnumbered IP interface as a Traffic Engineering (TE) link for the signaling of RSVP P2P LSP.
An unnumbered IP interface is identified uniquely on a router in the network by the tuple {router-id, ifIndex}. Each side of the link assigns a system-wide unique interface index to the unnumbered interface. IS-IS, OSPF, RSVP, and OAM modules use this tuple to advertise the link information, signal LSP paths over this unnumbered interface, or send and respond to an MPLS echo request message over an unnumbered interface.
The interface-borrowed IP address is used exclusively as the source address for IP packets that originates from the interface and needs to be configured to an address different from system interface for the FRR bypass LSP to come up at the ingress LER.
The borrowed IP address for an unnumbered interface is configured using the following CLI command, with a default value set to the system interface address:
configure>router>interface>unnumbered [ip-int-name | ip-address].
The support of unnumbered TE link in IS-IS consists of adding a new sub-TLV of the extended IS as per RFC 5307 reachability TLV, which encodes the Link Local and Link Remote Identifiers as defined in RFC 5307.
The support of unnumbered TE link in OSPF consists of adding a new sub-TLV, which encodes the same Link Local and Link Remote Identifiers in the Link TLV of the TE area opaque LSA and sends the local Identifier in the Link Local Identifier TLV in the TE link local opaque LSA as per RFC 4203.
The support of unnumbered TE link in RSVP implements the signaling of unnumbered interfaces in ERO/RRO as per RFC 3477 and the support of IF_ID RSVP_HOP object with a new C-Type as per Section 8.1.1 of RFC 3473. The IPv4 Next/Previous Hop Address field is set to the borrowed IP interface address.
The unnumbered IP is advertised by IS-IS TE and OSPF TE, and CSPF can include them in the computation of a path for a P2P LSP. This feature does not, however, support defining an unnumbered interface as a hop in the path definition of an LSP.
A router creates an RSVP neighbor over an unnumbered interface using the tuple {router-id, ifIndex}. The router-id of the router which advertised a specific unnumbered interface index is obtained from the TE database. As as result, if traffic engineering is disabled in IS-IS or OSPF, a non-CSPF LSP with the next-hop for its path is over an unnumbered interface does not come up at the ingress LER because the router-id of the neighbor which has the next-hop of the path message cannot be looked up. In this case, the LSP path remains in the operationally down state with the reason "noRouteToDestination". If a PATH message is received at the LSR in which traffic engineering was disabled and the next-hop for the LSP path is over an unnumbered interface, a PathErr message is sent back to the ingress LER with the Routing Problem error code 24 and an error value of 5 "No route available toward destination".
This feature supports all of the MPLS features available for numbered IP interfaces, with the following exceptions:
configuring a router-id with a value other than system
signaling an LSP path with an ERO based loose/strict hop using an unnumbered TE link in the path hop definition
signaling of one-to-one detour LSP over unnumbered interface
soft preemption of LSP path using unnumbered interface
inter-area LSP
unnumbered RSVP interface registration with BFD
RSVP Hello and all Hello-related capabilities, such as Graceful-restart helper
user SRLG database feature. The user-srlg-db option under MPLS allows the user to manually enter the SRLG membership of any link in the network in a local database at the ingress LER. An unnumbered interface cannot be entered in this database and, therefore, all unnumbered interfaces are treated as having no SRLG membership if the user-srlg-db option is enabled.
This feature also extends the support of lsp-ping, lsp-trace, and P2P LSPs that have unnumbered TE links in their path.
Operation of RSVP FRR facility backup over unnumbered interface
When the Point-of-Local Repair (PLR) node activates the bypass LSP by sending a PATH message to refresh the path state of protected LSP at the Merge-Point (MP) node, it must use an IPv4 tunnel sender address in the sender template object which is different than the one used by the ingress LER in the PATH message. These are the procedures specified in RFC 4090 and which are followed in the node implementation.
The node uses the address of the outgoing interface of the bypass LSP as the IPv4 tunnel sender address in the sender template object. This address will be different from the system interface address used in the sender template of the protected LSP by the ingress LER and therefore there are no conflicts when the ingress LER acts as a PLR.
When the PLR is the ingress LER node and the outgoing interface of the bypass LSP is unnumbered, it is required that the user assigns to the interface a borrowed IP address which is different from the system interface. If not, the bypass LSP will not come up.
In addition, the PLR node will include the IPv4 RSVP_HOP object (C-Type=1) or the IF_ID RSVP_HOP object (C-Type=3) in the PATH message if the outgoing interface of the bypass LSP is numbered or unnumbered respectively.
When the MP node receives the PATH message over the bypass LSP, it will create the merge-point context for the protected LSP and associate it with the existing state if any of the following is satisfied:
change in C-Type of the RSVP_HOP object
C-Type is IF_ID RSVP_HOP and did not change but IF_ID TLV is different
change in IPv4 Next/Previous Hop Address in RSVP_HOP object regardless of the C-Type value
These procedures at PLR and MP nodes are followed in both link-protect and node-protect FRR.
If the MP node is running a pre-R9.0 R4 implementation, it will reject the new IF_ID C-Type and drop the PATH over bypass. This will result in the protected LSP state expiring at the MP node, which will tear down the path. This would be the case in general when node-protect FRR is enabled and the MP node does not support unnumbered RSVP interface.
PCEP support for RSVP-TE LSPs
The Path Computation Element Communication Protocol (PCEP) is one of several protocols used for communication between a wide area network (WAN) software-defined network (SDN) controller and network elements.
The 7210 SAS operates as a PCE Client (PCC) only, supporting PCC capabilities for RSVP-TE LSPs.
The following MPLS-level and LSP-level CLI commands are used to configure RSVP-TE LSPs in a router acting as a PCC.
config>router>mpls>
pce-report rsvp-te {enable | disable}
config>router>mpls>lsp>
path-profile profile-id [path-group group-id]
pce-computation
pce-control
pce-report {enable | disable | inherit}
MPLS Traffic Engineering
Without traffic engineering, routers route traffic according to the SPF algorithm, disregarding congestion or packet types.
With traffic engineering, network traffic is routed efficiently to maximize throughput and minimize delay. Traffic engineering facilitates the mapping of traffic flows to the destination through a different (less congested) path other than the one selected by the SPF algorithm.
MPLS directs a flow of IP packets along a label switched path (LSP). LSPs are simplex, meaning that the traffic flows in one direction (unidirectional) from an ingress router to an egress router. Two LSPs are required for duplex traffic. Each LSP carries traffic in a specific direction, forwarding packets from one router to the next across the MPLS domain.
When an ingress router receives a packet, it adds an MPLS header to the packet and forwards it to the next hop in the LSP. The labeled packet is forwarded along the LSP path until it reaches the destination point. The MPLS header is removed and the packet is forwarded based on Layer 3 information such as the IP destination address. The physical path of the LSP is not constrained to the shortest path that the IGP would choose to reach the destination IP address.
TE metric (IS-IS and OSPF)
When the use of the TE metric is selected for an LSP, the shortest path computation after the TE constraints are applied will select an LSP path based on the TE metric instead of the IGP metric. The user configures the TE metric under the MPLS interface. Both the TE and IGP metrics are advertised by OSPF and IS-IS for each link in the network. The TE metric is part of the traffic engineering extensions of both IGP protocols.
A typical application of the TE metric is to allow CSPF to represent a dual TE topology for the purpose of computing LSP paths.
An LSP dedicated for real-time and delay sensitive user and control traffic has its path computed by CSPF using the TE metric. The user configures the TE metric to represent the delay figure, or a combined delay/jitter figure, of the link. In this case, the shortest path satisfying the constraints of the LSP path will effectively represent the shortest delay path.
An LSP dedicated for non delay sensitive user and control traffic has its path computed by CSPF using the IGP metric. The IGP metric could represent the link bandwidth or some other figure as required.
When the use of the TE metric is enabled for an LSP, CSPF will first prune all links in the network topology that do not meet the constraints specified for the LSP path. These constraints include bandwidth, admin-groups, and hop limit. CSPF will then run an SPF on the remaining links. The shortest path among the all SPF paths will be selected based on the TE metric instead of the IGP metric used by default. The TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability.
Advanced MPLS/RSVP features
LSP path change
The tools perform router mpls update-path {lsp lsp-name path current-pathname new-path new-path-name} command instructs MPLS to replace the path of the primary or secondary LSP.
The primary or secondary LSP path is indirectly identified via the current-path-name value. In existing implementation, the same path name cannot be used more than once in a given LSP name.
This command is also supported on an SNMP interface.
This command applies to both CSPF LSP and to a non-CSPF LSP. However, it will only be honored when the specified current-path-name has the adaptive option enabled. The adaptive option can be enabled the LSP level or at the path level.
The new path must be first configured in CLI or provided via SNMP. The config router mpls path path-name CLI command is used to enter the path.
The command fails if any of the following conditions are satisfied:
The specified current-path-name of this LSP does not have the adaptive option enabled.
The specified new-path-name value does not correspond to a previously defined path.
The specified new-path-name value exists but is being used by any path of the same LSP, including this one.
When the command is executed, MPLS performs the following procedures:
MPLS performs a single MBB attempt to move the LSP path to the new path.
If the MBB is successful, MPLS updates the new path.
MPLS writes the corresponding NHLFE in the datapath if this path is the current backup path for the primary.
If the current path is the active LSP path, it will update the path, write the new NHLFE in the datapath, which will cause traffic to switch to the new path.
If the MBB is not successful, the path retains it current value.
The update-path MBB has the same priority as the manual re-signal MBB.
Manual LSP path switch
This feature provides a new command to move the path of an LSP from a standby secondary to another standby secondary.
The base version of the command allows the path of the LSP to move from a standby (or an active secondary) to another standby of the same priority. If a new standby path with a higher priority or a primary path comes up after the tools perform command is executed, the path re-evaluation command runs and the path is moved to the path specified by the outcome of the re-evaluation.
The CLI command for the base version is:
tools perform router mpls switch-path lsp lsp-name path path-name
The sticky version of the command can be used to move from a standby path to any other standby path regardless of priority. The LSP remains in the specified path until this path goes down or the user performs the no form of the tools perform command.
The CLI commands for the sticky version are:
tools perform router mpls force-switch-path lsp lsp-name path path-name
tools perform router mpls no force-switch-path lsp lsp-name
Make-Before-Break (MBB) procedures for LSP/Path parameter configuration change
When an LSP is switched from an existing working path to a new path, it is desirable to perform this in a hitless fashion. The Make-Before-Break (MBB) procedure consist of first signaling the new path when it is up, and having the ingress LER move the traffic to the new path. Only then the ingress LER tears down the original path.
MBB procedure is raised during the following operations:
timer based and manual re-signal of an LSP path
Fast-ReRoute (FRR) global revertive procedures
Traffic-Engineering (TE) graceful shutdown procedures
Shared Risk Link Groups
Shared Risk Link Groups (SRLGs) is a feature that allows the user to establish a backup secondary LSP path or a FRR LSP path which is disjoint from the path of the primary LSP. Links that are members of the same SRLG represent resources sharing the same risk, for example, fiber links sharing the same conduit or multiple wavelengths sharing the same fiber.
When the SRLG option is enabled on a secondary path, CSPF includes the SRLG constraint in the computation of the secondary LSP path. This requires that the primary LSP already be established and up since the head-end LER needs the most current ERO computed by CSPF for the primary path. CSPF would return the list of SRLG groups along with the ERO during primary path CSPF computation. At a subsequent establishment of a secondary path with the SRLG constraint, the MPLS/RSVP task will query again CSPF providing the list of SLRG group numbers to be avoided. CSPF prunes all links with interfaces which belong to the same SRLGs as the interfaces included in the ERO of the primary path. If CSPF finds a path, the secondary is setup. If not, MPLS/RSVP will keep retrying the requests to CSPF.
When the SRLG option is enabled on FRR, CSPF includes the SRLG constraint in the computation of a FRR detour or bypass for protecting the primary LSP path. CSPF prunes all links with interfaces which belong to the same SRLG as the interface which is being protected, for example, the outgoing interface at the PLR the primary path is using. If one or more paths are found, the MPLS/RSVP task will select one based on best cost and will signal the bypass/detour. If not and the user included the strict option, the bypass/detour is not setup and the MPLS/RSVP task will keep retrying the request to CSPF. Otherwise, if a path exists which meets the other TE constraints, other than the SRLG one, the bypass/detour is setup.
A bypass or a detour LSP path is not guaranteed to be SRLG disjoint from the primary path. This is because only the SRLG constraint of the outgoing interface at the PLR that the primary path is using is avoided.
Disjoint backup paths
This section provides information about the steps necessary to create shared risk link groups for primary/standby SRLG disjoint configuration and for FRR detours/bypass SRLG disjoint configuration. Non-CSPF manual bypass is not considered.
A typical application of the SRLG feature is to provide for an automatic placement of secondary backup LSPs or FRR bypass/detour LSPs that minimizes the probability of fate sharing with the path of the primary LSP (shown in the following figure).
This feature is supported on OSPF and IS-IS interfaces on which RSVP is enabled.
Enabling disjoint backup paths for primary and standby SRLG disjoint configuration
The following details the steps necessary to create shared risk link groups for primary/standby SRLG disjoint configuration.
- Create an SRLG-group similar to admin groups.
- Link the SRLG-group to MPLS interfaces.
- Configure primary and secondary LSP paths and enable SRLG on the secondary LSP path. Note that the SRLG secondary LSP paths will always perform a strict CSPF query. The srlg-frr command is irrelevant in this case (For more information, see srlg-frr).
Enabling disjoint backup paths for FRR detours and bypass SRLG disjoint configuration
The following details the steps necessary to create shared risk link groups for FRR detours/bypass SRLG disjoint configuration.
- Create an SRLG group, similar to admin groups.
- Link the SRLG group to MPLS interfaces.
- Enable the srlg-frr (strict/non-strict) option, which is a system-wide parameter, and it forces every LSP path CSPF calculation, to take the configured SRLG memberships (and propagated through the IGP opaque-te-database) into account.
-
Configure primary FRR (one-to-one/facility) LSP paths. Consider that each PLR
will create a detour/bypass that will only avoid the SRLG memberships configured
on the primary LSP path egress interface. In a one-to-one case, detour-detour
merging is out of the control of the PLR, therefore the latter will not ensure
that its detour will be prohibited to merge with a colliding one. For facility
bypass, with the presence of several bypass types to bind to, the following
priority rules will be followed:
- manual bypass disjoint
- manual bypass non-disjoint (eligible only if srlg-frr is non-strict)
- dynamic disjoint
- dynamic non-disjoint (eligible only if srlg-frr is non-strict)
Static configurations of SRLG memberships
This feature provides operations with the ability to enter manually the link members of SRLG groups for the entire network at any 7210 SAS node which will need to signal LSP paths (for example, a head-end node).
The operator may explicitly enables the use by CSPF of the SRLG database. In that case, CSPF will not query the TE database for IGP advertised interface SRLG information.
Note, however, that the SRLG secondary path computation and FRR bypass/detour path computation remains unchanged.
There are deployments where the 7210 SAS will interpret with routers that do not implement the SRLG membership advertisement through IGP SRLG TLV or sub-TLV.
In these situations, the user is provided with the ability to enter manually the link members of SRLG groups for the entire network at any 7210 SAS node which will need to signal LSP paths, for example, a head-end node.
The user enters the SRLG membership information for any link in the network by using the interface ip-int-name srlg-group group-name command in the config>router>mpls> srlg-database>router-id context. An interface can be associated with up to 5 SRLG groups for each execution of this command. The user can associate an interface with up to 64 SRLG groups by executing the command multiple times. The user must also use this command to enter the local interface SRLG membership into the user SRLG database. The user deletes a specific interface entry in this database by executing the no form of this command.
The group-name must have been previously defined in the SRLG srlg-group group-name value group-value command in the config>router>mpls context. The maximum number of distinct SRLG groups the user can configure on the system is 1024.
The parameter value for router-id must correspond to the router ID configured under the base router instance, the base OSPF instance or the base IS-IS instance of a specific node. Note however, that a single user SLRG database is maintained per node regardless if the listed interfaces participate in static routing, OSPF, IS-IS, or both routing protocols. The user can temporarily disable the use by CSPF of all interface membership information of a specific router ID by executing the shutdown command in the config>router>mpls>srlg-database>router-id context. In this case, CSPF will assume these interfaces have no SRLG membership association. The operator can delete all interface entries of a specific router ID entry in this database by executing the no router-id router-address command in the config>router>mpls>srlg-database context.
CSPF will not use entered SRLG membership if an interface is not listed as part of a router ID in the TE database. If an interface was not entered into the user SRLG database, it will be assumed that it does not have any SRLG membership. CSPF will not query the TE database for IGP advertised interface SRLG information.
The operator enables the use by CSPF of the user SRLG database by entering the user-srlg-db enable command in the config>router>mpls context. When the MPLS module makes a request to CSPF for the computation of an SRLG secondary path, CSPF will query the local SRLG and computes a path after pruning links which are members of the SRLG IDs of the associated primary path. Similarly, when MPLS makes a request to CSPF for a FRR bypass or detour path to associate with the primary path, CSPF queries the user SRLG database and computes a path after pruning links which are members of the SRLG IDs of the PLR outgoing interface.
The operator can disable the use of the user SRLG database by entering the user-srlg-db disable in command in the config>router>mpls context. CSPF will then resumes queries into the TE database for SRLG membership information. However, the user SRLG database is maintained
The operator can delete the entire SRLG database by entering the no srlg-database command in the config>router>mpls context. In this case, CSPF will assume all interfaces have no SRLG membership association if the user has not disabled the use of this database.
TE graceful shutdown
Graceful shutdown provides a method to bulk re-route transit LSPs away from the node during software upgrade of a node. A solution is described in RFC 5817, Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks. This is achieved in this draft by using a PathErr message with a specific error code Local Maintenance on TE link required flag. When a LER gets this message, it performs a make-before-break on the LSP path to move the LSP away from the links/nodes which IP addresses were indicated in the PathErr message.
Graceful shutdown can flag the affected link/node resources in the TE database so other routers will signal LSPs using the affected resources only as a last resort. This is achieved by flooding an IGP TE LSA/LSP containing link TLV for the links under graceful shutdown with the traffic engineering metric set to 0xffffffff and 0 as unreserved bandwidth.
MPLS/RSVP configuration process overview
The following figure shows the process to configure MPLS and RSVP parameters.
Configuration notes
This following information describes MPLS and RSVP guidelines and restrictions:
Interfaces must already be configured in the config>router>interface context before they can be specified in MPLS and RSVP.
A router interface must be specified in the config>router>mpls context to apply it or modify parameters in the config>router>rsvp context.
A system interface must be configured and specified in the config>router>mpls context.
Paths must be created before they can be applied to an LSP.
Configuring MPLS and RSVP with CLI
This section provides information to configure MPLS and RSVP using the command line interface.
MPLS configuration overview
Multiprotocol Label Switching (MPLS) enables routers to forward traffic based on a simple label embedded into the packet header. A router examines the label to determine the next hop for the packet, saving time for router address lookups to the next node when forwarding packets. MPLS is not enabled by default and must be explicitly enabled.
LSPs
To configure MPLS-signaled label switched paths (LSPs), an LSP must run from an ingress router to an egress router. Configure only the ingress router and configure LSPs to allow the software to make the forwarding decisions or statically configure some or all routers in the path. The LSP is set up by Resource Reservation Protocol (RSVP), through RSVP signaling messages. The automatically manages label values. Labels that are automatically assigned have values ranging from 1,024 through 1,048,575. See section Label values for more information.
A static LSP is a manually set up LSP where the next hop IP address and the outgoing label are explicitly specified.
Paths
To configure signaled LSPs, you must first create one or more named paths on the ingress router. For each path, the transit routers (hops) in the path are specified.
Router interface
At least one router interface and one system interface must be defined in the config>router>interface context to configure MPLS on an interface.
Choosing the signaling protocol
If only static label switched paths are used in your configurations, then you must manually define the paths through the MPLS network. Label mappings and actions configured at each hop must be specified. You do not need to enable RSVP if you are configuring static LSPs.
If dynamic LSP signaling is implemented in your network, then RSVP must be specified. Enable signaling protocols only on the links where the functionality is required.
To implement MPLS, the following entities must be enabled:
MPLS must be enabled on all routers that are part of an LSP.
RSVP must be enabled on the same routers.
When MPLS is enabled and either RSVP is also enabled, MPLS uses RSVP to set up the configured LSPs. For example, when you configure an LSP with both MPLS and RSVP running, RSVP initiates a session for the LSP. RSVP uses the local router as the RSVP session sender and the LSP destination as the RSVP session receiver. When the RSVP session is created, the LSP is set up on the path created by the session. If the session is not successfully created, RSVP notifies MPLS, MPLS can then either initiate backup paths or retry the initial path.
Basic MPLS configuration
This section provides information to configure MPLS and configuration examples of common configuration tasks. To enable MPLS on routers, you must configure at least one MPLS interface. The other MPLS configuration parameters are optional.
MPLS configuration output
A:ALA-1>config>router>mpls# info
------------------------------------------
admin-group "green" 15
admin-group "yellow" 20
admin-group "red" 25
interface "system"
exit
interface "StaticLabelPop"
admin-group "green"
label-map 50
pop
no shutdown
exit
exit
interface "StaticLabelPop"
label-map 35
swap 36 nexthop 10.10.10.91
no shutdown
exit
exit
path "secondary-path"
no shutdown
exit
path "to-NYC"
hop 1 10.10.10.104 strict
no shutdown
exit
lsp "lsp-to-eastcoast"
to 10.10.10.104
from 10.10.10.103
fast-reroute one-to-one
exit
primary "to-NYC"
exit
secondary "secondary-path"
exit
no shutdown
exit
static-lsp "StaticLabelPush"
to 10.10.11.105
push 60 nexthop 10.10.11.105
no shutdown
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>mpls#
Common configuration tasks
This section provides a brief overview of the tasks to configure MPLS and provides the CLI commands.
The following protocols must be enabled on each participating router:
MPLS
RSVP (for RSVP-signaled MPLS only)
LDP
In order for MPLS to run, you must configure at least one MPLS interface in the config>router>mpls context as follows:
An interface must be created in the config>router>interface context before it can be applied to MPLS.
In the config>router>mpls context, configure path parameters for configuring LSP parameters. A path specifies some or all hops from ingress to egress. A path can be used by multiple LSPs.
When an LSP is created, the egress router must be specified in the to command and at least one primary or secondary path must be specified. All other statements under the LSP hierarchy are optional.
Configuring global MPLS parameters
Admin groups can signify link colors, such as red, yellow, or green. MPLS interfaces advertise the link colors it supports. CSPF uses the information when paths are computed for constrained-based LSPs. CSPF must be enabled in order for admin groups to be relevant.
Use the following syntax to configure MPLS admin-group parameters.
mpls
admin-group group-name group-value
frr-object
resignal-timer minutes
Admin group configuration output
A:ALA-1>config>router>mpls# info
----------------------------------------------
resignal-timer 500
admin-group "green" 15
admin-group "yellow" 20
admin-group "red" 25
...
----------------------------------------------
A:ALA-1>config>router>mpls#
Configuring an MPLS interface
Configure the label-map parameters if the interface is used in a static LSP. Use the following syntax to configure an MPLS interface on a router.
config>router>mpls
interface
no shutdown
admin-group group-name [group-name...(up to 32 max)]
label-map
pop
swap
no shutdown
srlg-group group-name [group-name...(up to 5 max)]
te-metric value
MPLS interface configuration output
A:ALA-1>config>router>mpls# info
----------------------------------------------
...
interface "to-104"
admin-group "green"
admin-group "red"
admin-group "yellow"
label-map 35
swap 36 nexthop 10.10.10.91
no shutdown
exit
exit
no shutdown
...
----------------------------------------------
A:ALA-1>config>router>mpls#
Configuring MPLS paths
Configure an LSP path to use in MPLS. When configuring an LSP, the IP address of the hops that the LSP should traverse on its way to the egress router must be specified. The intermediate hops must be configured as either strict or loose meaning that the LSP must take either a direct path from the previous hop router to this router (strict) or can traverse through other routers (loose).
Use the following syntax to configure a path.
config>router> mpls
path path-name
hop hop-index ip-address {strict|loose}
no shutdown
Path configuration output
A:ALA-1>config>router>mpls# info
------------------------------------------
interface "system"
exit
path "secondary-path"
hop 1 10.10.0.121 strict
hop 2 10.10.0.145 strict
hop 3 10.10.0.1 strict
no shutdown
exit
path "to-NYC"
hop 1 10.10.10.103 strict
hop 2 10.10.0.210 strict
hop 3 10.10.0.215 loose
exit
------------------------------------------
A:ALA-1>config>router>mpls#
Configuring an MPLS LSP
Configure an LSP path for MPLS. When configuring an LSP, you must specify the IP address of the egress router in the to statement. Specify the primary path to be used. Secondary paths can be explicitly configured or signaled upon the failure of the primary path. All other statements are optional.
MPLS LSP configuration output
A:ALA-1>config>router>mplp# info
----------------------------------------------
...
lsp "lsp-to-eastcoast"
to 192.168.200.41
rsvp-resv-style ff
cspf
include "red"
exclude "green"
adspec
fast-reroute one-to-one
exit
primary "to-NYC"
hop-limit 10
exit
secondary "secondary-path"
bandwidth 50000
exit
no shutdown
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>mpls#
Configuring a static LSP
An LSP can be explicitly (statically) configured. Static LSPs are configured on every node along the path. The label’s forwarding information includes the address of the next hop router.
Use the following syntax to configure a static LSP.
config>router>mpls
static-lsp lsp-name
to ip-address
push out-label nexthop ip-addr
no shutdownStatic LSP configuration output
A:ALA-1>config>router>mpls# info
----------------------------------------------
...
static-lsp "static-LSP"
to 10.10.10.124
push 60 nexthop 10.10.42.3
no shutdown
exit
...
----------------------------------------------
A:ALA-1>config>router>mpls#
Configuring manual bypass tunnels
Consider the network setup in the following figure that shows nodes A through F.
The user first configures the option to disable the dynamic bypass tunnels.
Listed below are the steps to configure the manual bypass tunnels.
- Configure the option to disable the dynamic bypass tunnels on the 7210 SAS node B (if required). The CLI for this configuration is: config>router>mpls>dynamic-bypass [disable | enable] The dynamic bypass tunnels are enabled by default.
-
Configure an LSP on node B, such as B-E-F-C which is used only as bypass. The
user specifies each hop in the path, for example, the bypass LSP has a strict
path.
Note that including the bypass-only keyword disables the following options under the LSP configuration:
-
bandwidth
-
fast-reroute
-
secondary
-
adaptive
-
adspec
-
cspf
-
exclude
-
hop-limit
-
include
-
metric
Bypass tunnel configuration outputA:7210 SAS>config>router>mpls>path# info ------------------------------------------- ... path "BEFC" hop 10 10.10.10.11 strict hop 20 10.10.10.12 strict hop 30 10.10.10.13 strict no shutdown exit lsp "bypass-BC" to 10.10.10.15 primary "BEFC" exit no shutdown ... ------------------------------------------- A:7210 SAS >config>router>mpls>path# -
-
Configure an LSP from A to D and indicate fast-reroute bypass protection,
select the facility as "FRR method"
(config>router>mpls>lsp>fast-reroute
facility).
Observe if the following criteria apply:
-
if the LSP passes through B
-
a bypass is requested
-
the next hop is C
-
a manually configured bypass-only tunnel exists from B to C (excluding link B to C)
Node B uses the manually configured bypass-only tunnel from B to C. -
Configuring RSVP parameters
RSVP is used to set up LSPs. RSVP must be enabled on the router interfaces that are participating in signaled LSPs. The keep-multiplier and refresh-time default values can be modified in the RSVP context.
Initially, interfaces are configured in the config>router>mpls>interface context. Only these existing (MPLS) interfaces are available to modify in the config>router> rsvp context. Interfaces cannot be directly added in the RSVP context.
RSVP configuration output
A:ALA-1>config>router>rsvp# info
----------------------------------------------
interface "system"
no shutdown
exit
interface to-104
hello-interval 4000
no shutdown
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>rsvp#
Configuring RSVP message pacing parameters
RSVP message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full.
Use the following syntax to configure RSVP parameters.
config>router>rsvp
no shutdown
msg-pacing
period milli-seconds
max-burst number
RSVP message pacing configuration output
A:ALA-1>config>router>rsvp# info
----------------------------------------------
keep-multiplier 5
refresh-time 60
msg-pacing
period 400
max-burst 400
exit
interface "system"
no shutdown
exit
interface to-104
hello-interval 4000
no shutdown
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>rsvp#
Configuring graceful shutdown
Enable TE graceful shutdown on the maintenance interface using the config>router>rsvp>interface>graceful-shutdown command.
Disable graceful shutdown by executing the no form of the command at the RSVP interface level or at the RSVP level. This restores the user-configured TE parameters of the maintenance links, and the 7210 SAS maintenance node floods them.
MPLS configuration management tasks
This section discusses the MPLS configuration management tasks.
Modifying MPLS parameters
You must shut down MPLS entities to modify parameters. Re-enable (no shutdown) the entity for the change to take effect.
Modifying an MPLS LSP
Some MPLS LSP parameters, such as primary and secondary, must be shut down before they can be edited or deleted from the configuration.
MPLS LSP configuration output
A:ALA-1>>config>router>mpls>lsp# info
----------------------------------------------
shutdown
to 10.10.10.104
from 10.10.10.103
rsvp-resv-style ff
include "red"
exclude "green"
fast-reroute one-to-one
exit
primary "to-NYC"
hop-limit 50
exit
secondary "secondary-path"
exit
----------------------------------------------
A:ALA-1>config>router>mpls#
Modifying MPLS path parameters
To modify path parameters, the config>router>mpls>path context must be shut down first.
Path configuration output
A:ALA-1>config>router>mpls# info
#------------------------------------------
echo "MPLS"
#------------------------------------------
...
path "secondary-path"
hop 1 10.10.0.111 strict
hop 2 10.10.0.222 strict
hop 3 10.10.0.123 strict
no shutdown
exit
path "to-NYC"
hop 1 10.10.10.104 strict
hop 2 10.10.0.210 strict
no shutdown
exit
...
----------------------------------------------
A:ALA-1>config>router>mpls#
Modifying MPLS static LSP parameters
To modify static LSP parameters, the config>router>mpls>path context must be shut down first.
Static LSP configuration
A:ALA-1>config>router>mpls# info
----------------------------------------------
...
static-lsp "static-LSP"
to 10.10.10.234
push 102704 nexthop 10.10.8.114
no shutdown
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>mpls#
Deleting an MPLS interface
To delete an interface from the MPLS configuration, the interface must be shut down first.
Use the following syntax to delete an interface from the MPLS configuration output.
mpls
[no] interface ip-int-name
shutdown
MPLS configuration output
A:ALA-1>config>router>mpls# info
----------------------------------------------
...
admin-group "green" 15
admin-group "red" 25
admin-group "yellow" 20
interface "system"
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>mpls#RSVP configuration management tasks
This section describes the RSVP configuration management tasks.
Modifying RSVP parameters
Only interfaces configured in the MPLS context can be modified in the RSVP context.
The no rsvp command deletes this RSVP protocol instance and removes all configuration parameters for this RSVP instance.
The shutdown command suspends the execution and maintains the existing configuration.
Modified RSVP configuration output
A:ALA-1>config>router>rsvp# info
----------------------------------------------
keep-multiplier 5
refresh-time 60
msg-pacing
period 400
max-burst 400
exit
interface "system"
exit
interface "test1"
hello-interval 5000
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>rsvp#
Modifying RSVP message pacing parameters
RSVP message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full.
Modified RSVP message pacing configuration output
A:ALA-1>config>router>rsvp# info
----------------------------------------------
keep-multiplier 5
refresh-time 60
msg-pacing
period 200
max-burst 200
exit
interface "system"
exit
interface "to-104"
exit
no shutdown
----------------------------------------------
A:ALA-1>config>router>rsvp#
Deleting an interface from RSVP
Interfaces cannot be deleted directly from the RSVP configuration. An interface must have been configured in the MPLS context and then the RSVP context. The interface must first be deleted from the MPLS context. This removes the association from RSVP.
See Deleting an MPLS interface for information about deleting an MPLS interface.
MPLS/RSVP command reference
Command hierarchies
Configuration commands
MPLS commands
config
- router
- [no] mpls
- dynamic-bypass [enable | disable]
- [no] frr-object
- hold-timer seconds
- no hold-timer
- [no] interface ip-int-name
- [no] admin-group group-name [group-name...(up to 5 max)]
- label-map in-label
- no label-map in-label
- no pop
- pop
- no shutdown
- shutdown
- swap out-label nexthop ip-address
- swap implicit-null-label nexthop ip-address
- no swap
- no shutdown
- shutdown
- [no] srlg-group group-name [group-name...(up to 5 max)]
- te-metric metric
- no te-metric
- pce-report rsvp-te {enable | disable}
- resignal-timer minutes
- no resignal-timer
- [no] shutdown
- [no] srlg-database
- [no] router-id router-addr
- [no] interface ip-addr srlg-group group-name [group-name...(up to 5 max)]
- [no] shutdown
- [no] srlg-frr [strict]
- [no] static-lsp lsp-name
- no push label
- push label nexthop ip-address
- [no] shutdown
- to ip-address
- [no] static-lsp-fast-retry seconds
- user-srlg-db [enable | disable]
MPLS LSP commands
config
- router
- [no] mpls
- [no] lsp lsp-name [bypass-only]
- [no] adaptive
- [no] adspec
- bgp-transport-tunnel {include | exclude}
- [no] cspf [use-te-metric]
- [no] exclude group-name [group-name...(up to 5 max)]
- fast-reroute frr-method
- no fast-reroute
- bandwidth rate-in-mbps
- no bandwidth
- hop-limit number
- no hop-limit
- [no] node-protect
- from ip-address
- hop-limit number
- no hop-limit
- [no] include group-name [group-name...(up to 5 max)]
- path-profile profile-id [path-group group-id]
- no path-profile profile-id
- [no] pce-computation
- [no] pce-control
- pce-report {enable | disable | inherit}
- [no] primary path-namex
- [no] adaptive
- bandwidth rate-in-mpbs
- no bandwidth
- [no] exclude group-name [group-name...(up to 5 max)]
- hop-limit number
- no hop-limit
- [no] include group-name [group-name...(up to 5 max)]
- [no] record
- [no] record-label
- [no] shutdown
- retry-limit number
- no retry-limit
- retry-timer seconds
- no retry-timer
- rsvp-resv-style [se | ff]
- [no] secondary path-name
- [no] adaptive
- bandwidth rate-in-mbps
- no bandwidth
- [no] exclude group-name [group-name...(up to 5 max)]
- hop-limit number
- no hop-limit
- [no] include group-name [group-name...(up to 5 max)]
- [no] path-preference
- [no] record
- [no] record-label
- [no] shutdown
- [no] srlg
- [no] standby
- [no] shutdown
- to ip-address
MPLS Path commands
RSVP commands
config
- router
- [no] rsvp
- [no] implicit-null-label
- [no] interface ip-int-name
- authentication-key [authentication-key | hash-key] [hash | hash2]
- no authentication-key
- [no] bfd-enable
- hello-interval milli-seconds
- no hello-interval
- [no] refresh-reduction
- [no] reliable-delivery
- [no] shutdown
- subscription percentage
- no subscription
- keep-multiplier number
- no keep-multiplier
- [no] msg-pacing
- max-burst number
- no max-burst
- period milli-seconds
- no period
- rapid-retransmit-time hundred-milliseconds
- no rapid-retransmit-time
- rapid-retry-limit number
- no rapid-retry-limit
- refresh-time seconds
- no refresh-time
- [no] shutdown
Show commands
show
- router
- mpls
- bypass-tunnel [to ip-address] [protected-lsp name] [dynamic | manual] [detail]
- interface [ip-int-name|ip-address] [label-map label]
- interface [ip-int-name|ip-address]
- label start-label [end-label | in-use | label-owner]
- label-range
- lsp [lsp-name] [status {up|down}] [from ip-address| to ip-address] [detail]
- lsp {transit | terminate} [status {up|down}] [from ip-address | to ip-address | lsp-name name] [detail]
- lsp count
- lsp lsp-name activepath
- lsp [lsp-name] path [path-name] [status {up | down}] [detail]
- srlg-database [router-id ip-address] [interface ip-address]
- static-lsp [lsp-name]
- static-lsp {transit | terminate}
- static-lsp count
- status
show
- router
- rsvp
- interface [interface [ip-int-name]] statistics [detail]
- neighbor [ip-address] [detail]
- session [session-type] [from ip-address| to ip-address| lsp-name name] [status {up|down}][detail]
- statistics
- status
Tools commands
tools
- perform
- router
- mpls
- cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap bitmap] [exclude-bitmap bitmap] [hop-limit limit] [exclude-address excl-addr [excl-addr...(up to 8 max)]] [use-te-metric] [strict-srlg] [srlggroup
grp-id...(up to 8 max)] [skip-interface interface-name]
- resignal {lsp lsp-name path path-name | delay minutes}
- switch-path [lsp lsp-name] [path path-name]
Clear commands
clear
- router
- mpls
- interface [ip-int-name]
- lsp lsp-name
- rsvp
- interface [ip-int-name] [statistics]
- statistics
Debug commands
debug
- router
- mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id]
- no mpls
- [no] event
- all [detail]
- no all
- frr [detail]
- no frr
- iom [detail]
- no iom
- lsp-setup [detail]
- no lsp-setup
- mbb [detail]
- no mbb
- misc [detail]
- no misc
- xc [detail]
- no xc
- rsvp [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id] [interface ip-int-name]
- no rsvp
- [no] event
- all [detail]
- no all
- auth
- no auth
- misc [detail]
- no misc
- nbr [detail]
- no nbr
- path [detail]
- no path
- resv [detail]
- no resv
- rr
- no rr
- [no] packet
- all [detail]
- no all
- ack
- bundle [detail]
- no bundle
- hello [detail]
- no hello
- path [detail]
- no path
- patherr [detail]
- no patherr
- pathtear [detail]
- no pathtear
- resv [detail]
- no resv
- resverr [detail]
- no resverr
- resvtear [detail]
- no resvtear
- srefresh [detail]
- no srefresh
Command descriptions
MPLS configuration commands
Generic commands
shutdown
Syntax
[no] shutdown
Context
config>router>mpls
config>router>mpls>interface
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
MPLS is not enabled by default and must be explicitly enabled (no shutdown).
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
The no form of this command places the entity into an administratively enabled state.
Default
no shutdown
MPLS commands
mpls
Syntax
[no] mpls
Context
config>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
Commands in this context configure MPLS parameters. MPLS is not enabled by default and must be explicitly enabled (no shutdown). The shutdown command administratively disables MPLS.
MPLS must be shut down before the MPLS instance can be deleted. If MPLS is not shut down, when the no mpls command is executed, a warning message on the console displays indicating that MPLS is still administratively up.
The no form of this command deletes this MPLS protocol instance, which removes all configuration parameters for this MPLS instance.
dynamic-bypass
Syntax
dynamic-bypass [enable | disable]
no dynamic-bypass
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command disables the creation of dynamic bypass LSPs in FRR. One or more manual bypass LSPs must be configured to protect the primary LSP path at the PLR nodes.
Implicit NULL must be enabled for the use of Manual Bypass or Dynamic Bypass (FRR facility) if the 7210 SAS is used as an egress LER or is a merge point.
Default
dynamic bypass
frr-object
Syntax
[no] frr-object
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies whether fast reroute for LSPs using the facility bypass method is signaled with or without the fast reroute object using the one-to-one keyword. The value is ignored if fast reroute is disabled for the LSP or if the LSP is using one-to-one backup.
By default, the value is inherited by all LSPs.
Default
frr-object
hold-timer
Syntax
hold-timer seconds
no hold-timer
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the amount of time that the ingress node waits before programming its data plane and declaring to the service module that the LSP is up.
The no form of this command disables the hold timer.
Default
1 second
Parameters
- seconds
Specifies the hold time, in seconds.
pce-report
Syntax
pce-report rsvp-te {enable | disable}
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the reporting mode for RSVP-TE LSPs.
The PCC LSP database is synchronized with the PCE LSP database using the PCEP PCRpt (PCE report) message for PCC-controlled, PCE-computed, and PCE-controlled LSPs.
The global MPLS-level pce-report command enables or disables PCE reporting for all RSVP-TE LSPs during PCE LSP database synchronization. The PCC reports both CSPF and non-CSPF LSPs.
The LSP-level pce-report command (in the config>router>mpls>lsp>pce-report context) overrides the global configuration for reporting an LSP to the PCE. The default configuration, which inherits the global MPLS-level configuration, is disabled (using the pce-report rsvp-te disable command).
The default configuration controls the introduction of a PCE into an existing network and allows the user to decide whether all RSVP-TE LSPs should be reported. If PCE reporting for an LSP is disabled, either because of the inheritance of the global MPLS configuration or because of LSP-level configuration, enabling the pce-control option for the LSP has no effect.
Default
pce-report rsvp-te disable
Parameters
- rsvp-te
Specifies PCE reporting for all RSVP-TE LSPs.
enable — Keyword to enable PCE reporting.
disable — Keyword to disable PCE reporting.
resignal-timer
Syntax
resignal-timer minutes
no resignal-timer
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the value for the LSP resignal timer. The resignal timer is the wait time, in minutes, before the software attempts to resignal the LSPs.
When the resignal timer expires, if the new computed path for an LSP has a better metric than the current recorded hop list, an attempt is made to resignal that LSP using the make-before-break mechanism. If the attempt to resignal an LSP fails, the LSP continues to use the existing path and a resignal is attempted the next time the timer expires.
The no form of this command disables timer-based LSP resignaling.
Default
no resignal-timer
Parameters
- minutes
Specifies the time the software waits before attempting to resignal the LSPs.
srlg-frr
Syntax
srlg-frr [strict]
no srlg-frr
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables or disables the use of the Shared Risk Link Group (SRLG) constraint in the computation of an FRR bypass or detour LSP for any primary LSP path on the system.
When this command is enabled, CSPF includes the SRLG constraint in the computation of an FRR detour or bypass for protecting the primary LSP path.
CSPF prunes all links with interfaces that belong to the same SRLG as the interface being protected, where the interface being protected is the outgoing interface at the PLR used by the primary path. If one or more paths are found, the MPLS/RSVP task selects one path based on best cost and signals the setup of the FRR bypass or detour LSP. If no path is found and the user included the strict option, the FRR bypass or detour LSP is not set up and the MPLS/RSVP task keeps retrying the request to CSPF. If a path exists that meets the other TE constraints, other than the SRLG one, the bypass or detour LSP is set up.
An FRR bypass or detour LSP is not guaranteed to be SRLG disjoint from the primary path. This is because only the SRLG constraint of the outgoing interface at the PLR that the primary path is using is checked.
When the MPLS/RSVP task is searching for a SRLG bypass tunnel to associate with the primary path of the protected LSP, the task performs the following steps:
First, the task checks for any configured manual bypass LSP that has CSPF enabled and that satisfies the SLRG constraints.
The task then skips any non-CSPF bypass LSP in the search because there is no ERO returned with which to check the SLRG constraint.
If no path is found, the task checks for an existing dynamic bypass LSP that satisfies the SLRG and other primary path constraints.
If no bypass path is found, the task makes a request to CSPF to create one.
When the primary path of the LSP is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface that the primary path is using will not be considered by the MPLS/RSVP task at the PLR for bypass or detour LSP association until the next opportunity that the primary path is resignaled. The path may be resignaled because of a failure or a make-before-break (MBB) operation. An MBB operation occurs as a result of a global revertive operation, a reoptimization of the LSP path (timer-based or manual), or a user change to any of the path constraints.
When the bypass or detour path is set up and is operationally up, subsequent changes to the SRLG group membership of an interface that the bypass or detour LSP path is using would not be considered by the MPLS/RSVP task at the PLR until the next opportunity that the association with the primary LSP path is rechecked. The association is rechecked if the bypass path is reoptimized. Detour paths are not reoptimized and are resignaled if the primary path is down.
Enabling or disabling the srlg-frr command takes effect only after LSP paths are resignaled, which is done by shutting down and reenabling MPLS. Another option is using the tools perform router mpls resignal command. While using the tools command may have less service impact, only originating LSPs can be resignaled using the tools command. If local transit and bypass LSPs must also be resignaled, the tools command must be executed on all ingress nodes in the network. The same may be locally achieved by disabling and enabling using the configure router mpls dynamic-bypass command, but this can trigger the LSP to go down and traffic loss to occur when the detour or bypass LSP is in use.
An RSVP interface can belong to a maximum of 64 SRLG groups. Configure the SRLG groups using the config router mpls srlg-group command. Configure the SRLG groups that an RSVP interface belongs to using the srlg-group command in the config>router>mpls>interface context.
The no form of this command reverts to the default value.
Default
no srlg-frr
Parameters
- strict
Specifies the name of the SRLG group within a virtual router instance.
user-srlg-db
Syntax
user-srlg-db [enable | disable]
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of CSPF by the user SRLG database. When the MPLS module makes a request to CSPF for the computation of an SRLG secondary path, CSPF queries the local SRLG and computes a path after pruning links that are members of the SRLG IDs of the associated primary path. When MPLS makes a request to CSPF for an FRR bypass or detour path to associate with the primary path, CSPF queries the user SRLG database and computes a path after pruning links that are members of the SRLG IDs of the PLR outgoing interface.
If an interface was not entered into the user SRLG database, it is assumed that it does not have any SRLG membership. CSPF will not query the TE database for IGP advertised interface SRLG information.
The disable keyword disables the use of the user SRLG database. CSPF then resumes queries into the TE database for SRLG membership information. The user SRLG database is maintained.
Default
user-srlg-db disable
Parameters
- enable
Keyword to enable the use of the user SRLG database.
- disable
Keyword to disable the use of the user SRLG database.
srlg-database
Syntax
[no] srlg-database
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
Commands in this context manually enter the link members of SRLG groups for the entire network at any node that needs to signal LSP paths (for example, a head-end node).
The no form of this command deletes the entire SRLG database. CSPF assumes all interfaces have no SRLG membership association if the database was not disabled using the config router mpls user-srlg-db disable command.
router-id
Syntax
[no] router-id ip-address
Context
config>router>mpls>srlg-database
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command manually enters the link members of SRLG groups for a specific router in the network. The user must also use this command to enter the local interface SRLG membership into the user SRLG database. Use by CSPF of all interface SRLG membership information of a specific router ID may be temporarily disabled by shutting down the node. If this occurs, CSPF assumes these interfaces have no SRLG membership association.
The no form of this command deletes all interface entries under the router ID.
Parameters
- ip-address
Specifies the router ID for this system. This must be the router ID configured under the base router instance, the base OSPF instance or the base IS-IS instance.
interface
Syntax
interface ip-address srlg-group group-name [group-name...(up to 5 max)]
no interface ip-address [srlg-group group-name...(up to 5 max)]
Context
config>router>mpls>srlg-database>router-id
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enable the user to manually enter the SRLG membership information for any link in the network, including links on this node, into the user SRLG database.
An interface can be associated with up to five SRLG groups for each execution of this command. The user can associate an interface with up to 64 SRLG groups by executing the command multiple times.
CSPF does not use entered SRLG membership if an interface is not validated as part of a router ID in the routing table.
The no form of this command deletes a specific interface entry in this user SRLG database. The group-name must already exist in the config>router>mpls>srlg-group context.
Parameters
- ip-int-name
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address.
- srlg-group group-name
Specifies the SRLG group name. Up to 1024 group names can be defined in the config>router>mpls context. The SRLG group names must be identical across all routers in a single domain.
label-map
Syntax
[no] label-map in-label
Context
config>router>mpls>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command is used on transit routers when a static LSP is defined. The static LSP on the ingress router is initiated using the config router mpls static-lsp lsp-name command. An in-label can be associated with either a pop or swap action, but not both. If both actions are specified, the last action specified takes effect.
The no form of this command deletes the static LSP configuration associated with the in-label.
Parameters
- in-label
Specifies the incoming MPLS label on which to match.
pop
Syntax
[no] pop
Context
config>router>mpls>if>label-map
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies that the incoming label must be popped (removed). No label stacking is supported for a static LSP. The service header follows the top label. After the label is popped, the packet is forwarded based on the service header.
The no form of this command removes the pop action for the in-label.
shutdown
Syntax
[no] shutdown
Context
config>router>mpls>if>label-map
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command disables the label map definition. This drops all packets that match the in-label specified in the label-map command.
The no form of this command administratively enables the defined label map action.
Default
no shutdown
swap
Syntax
swap out-label nexthop ip-address
swap implicit-null-label nexthop ip-address
no swap
Context
config>router>mpls>interface>label-map
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command swaps the incoming label and specifies the outgoing label and next-hop IP address on an LSR for a static LSP.
The no form of this command removes the swap action associated with the in-label.
Parameters
- implicit-null-label
Keyword to specify the use of the implicit label value for the outgoing label of the swap operation.
- out-label
Specifies the label value to be swapped with the in-label. Label values 16 through 1,048,575 are defined as follows.
Label values16 through 31 are reserved.
Label values 32 through 1,023 are available for static assignment.
Label values 1,024 through 2,047 are reserved for future use.
Label values 2,048 through 18,431 are statically assigned for services.
Label values 28,672 through 131,071 are dynamically assigned for both MPLS and services.
Label values 131,072 through 1,048,575 are reserved for future use.
- nexthop ip-address
Specifies the IP address to forward to. If an ARP entry for the next hop exists, the static LSP is marked operational. If an ARP entry does not exist, the operational status of the static LSP is set to down and the software continuously tries to ARP for the configured next hop at fixed intervals.
static-lsp
Syntax
[no] static-lsp lsp-name
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures a static LSP on the ingress router. The static LSP is a manually set up LSP where the next-hop IP address and the outgoing label (push) must be specified.
The no form of this command deletes this static LSP and associated information.
The LSP must be shut down first to delete it. If the LSP is not shut down, the no static-lsp lsp-name command generates a warning message on the console indicating that the LSP is administratively up.
Parameters
- lsp-name
Specifies a name that identifies the LSP, up to 32 alphanumeric characters.
push
Syntax
no push label
push label nexthop ip-address
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies the label to be pushed on the label stack and the next-hop IP address for the static LSP.
The no form of this command removes the association of the label to push for the static LSP.
Parameters
- label
Specifies the label to push on the label stack. Label values 16 through 1048575 are defined as follows.
Label values16 through 31 are reserved.
Label values 32 through 1023 are available for static assignment.
Label values 1024 through 2047 are reserved for future use.
Label values 2048 through 18431 are statically assigned for services.
Label values 28672 through 131071 are dynamically assigned for both MPLS and services.
Label values 131072 through 1048575 are reserved for future use.
- nexthop ip-address
Specifies the IP address of the next hop toward the LSP egress router. If an ARP entry for the next hop exists, the static LSP is marked operational.
If ARP entry does not exist, software sets the operational status of the static LSP to down and continuously tries to ARP for the configured next hop at a fixed interval.
shutdown
Syntax
[no] shutdown
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command administratively disables the static LSP.
The no form of this command administratively enables the static LSP.
Default
shutdown
to
Syntax
to ip-address
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the system IP address of the egress router for the static LSP. This command is required while creating an LSP. For LSPs that are used as transport tunnels for services, the to IP address must be the system IP address. If the to address does not match the SDP address, the LSP is not included in the SDP definition.
Parameters
- ip-address
Specifies the system IP address of the egress router.
static-lsp-fast-retry
Syntax
static-lsp-fast-retry seconds
[no] static-lsp-fast-retry
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the value used as the fast retry timer for a static LSP.
When a static LSP is trying to come up, the MPLS request for the ARP entry of the LSP next hop may fail when it is made while the next hop is still down or unavailable. In that case, MPLS starts a retry timer before making the next request. This functionality allows the user to configure the retry timer, so that the LSP comes up as soon as the next hop is up.
The no form of this command reverts to the default value.
Default
no static-fast-retry-timer
Parameters
- seconds
Specifies the value, in seconds, used as the fast retry timer for a static LSP.
MPLS interface commands
interface
Syntax
[no] interface ip-int-name
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures MPLS protocol support on an IP interface. No MPLS commands are executed on an IP interface where MPLS is not enabled. An MPLS interface must be explicitly enabled (no shutdown).
The no form of this command deletes all MPLS commands, such as label-map, that are defined under the interface. The MPLS interface must be shut down first to delete the interface definition. If the interface is not shut down, the no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
Default
shutdown
Parameters
- ip-int-name
Specifies the name of the network IP interface, up to 32 alphanumeric characters. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
admin-group
Syntax
[no] admin-group group-name [group-name...(up to 5 max)]
Context
config>router>mpls>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command associates admin groups with the interface.
The user can apply admin groups to an IES, VPRN, network IP, or MPLS interface. Each single operation of the admin-group command allows a maximum of five groups to be specified at a time. However, a maximum of 32 groups can be added to a specific interface through multiple operations.
After an admin group is bound to one or more interfaces, its value cannot be changed until all bindings are removed. The configured admin-group membership is applied in all levels and areas the interface is participating in. The same interface cannot have different memberships in different levels or areas.
Only the admin groups bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.
The user can also delete all memberships of an interface by not specifying a group name.
The no form of this command deletes the association of this interface with one or more of the admin groups.
Default
no admin-group
Parameters
- group-name
Specifies the name of the group, up to 32 characters. The association of group name and value should be unique within an IP/MPLS domain.
srlg-group
Syntax
[no] srlg-group group-name [group-name...(up to 5 max)]
Context
config>router>mpls>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command defines the association of RSVP interface to an SRLG group. An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of five groups to be specified at a time.
The no form of this command deletes the association of the interface to the SRLG group.
Parameters
- group-name
Specifies the name of the SRLG group within a virtual router instance, up to 32 characters.
te-metric
Syntax
te-metric value
no te-metric
Context
config>router>mpls>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the traffic engineering metric used on the interface. This metric is in addition to the interface metric used by IGP for the shortest path computation.
This metric is flooded as part of the TE parameters for the interface using an opaque LSA or an LSP. The IS-IS TE metric is encoded as sub-TLV 18 as part of the extended IS reachability TLV. The metric value is encoded as a 24-bit unsigned integer. The OSPF TE metric is encoded as a sub-TLV Type 5 in the link TLV. The metric value is encoded as a 32-bit unsigned integer.
When the use of the TE metric is enabled for an LSP, CSPF first prunes all links in the network topology that do not meet the constraints specified for the LSP path. Such constraints include bandwidth, admin-groups, and hop limit. Then, CSPF runs an SPF on the remaining links. The shortest path among the all SPF paths is selected based on the TE metric instead of the IGP metric, which is used by default.
The TE metric in CSPF LSP path computation can be configured by entering the config router mpls lsp cspf use-te-metric command.
The TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability. The value of the IGP metric is advertised in the TE metric sub-TLV by IS-IS and OSPF.
The no form of this command reverts to the default value.
Default
no te-metric
Parameters
- value
Specifies the metric value.
LSP commands
lsp
Syntax
[no] lsp lsp-name [bypass-only]
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command creates an LSP that is signaled dynamically by the 7210 SAS.
When the LSP is created, the egress router must be specified using the to command and at least one primary or secondary path must be specified. All other statements under the LSP hierarchy are optional. Notre that the maximum number of static configurable LSPs is 4.
LSPs are created in the administratively down (shutdown) state.
The no form of this command deletes the LSP. All configuration information associated with this LSP is lost. The LSP must be administratively shutdown before it can be deleted.
Parameters
- lsp-name
Specifies a name that identifies the LSP. The LSP name can be up to 32 characters and must be unique.
- bypass-only
Keyword to specify an LSP as a manual bypass LSP exclusively. When a path message for a new LSP requests bypass protection, the PLR first checks if a manual bypass tunnel satisfying the path constraints exists. If one is found, the 7210 SAS selects it. If no manual bypass tunnel is found, the 7210 SAS dynamically signals a bypass LSP in the default behavior. The CLI for this feature includes a command that provides the option to disable dynamic bypass creation on a per-node basis.
adaptive
Syntax
[no] adaptive
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the make-before-break (MBB) functionality for an LSP or LSP path. When enabled for the LSP, MBB is performed for the primary path and all the secondary paths of the LSP.
Default
adaptive
adspec
Syntax
[no] adspec
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies that the advertised data (ADSPEC) object is included in RSVP messages for this LSP. The ADSPEC object is used by the ingress LER to discover the minimum value of the MTU for links in the path of the LSP. By default, the ingress LER derives the LSP MTU from that of the outgoing interface of the LSP path.
A bypass LSP always signals the ADSPEC object because it protects both primary paths that signal the ADSPEC object and primary paths that do not. The MTU of LSP at ingress LER may change to a different value from that derived from the outgoing interface, even if the primary path has ADSPEC disabled.
Default
no adspec
bgp-transport-tunnel
Syntax
bgp-transport-tunnel {include | exclude}
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables or disables RSVP-TE LSP to be used as a transport LSP for BGP tunnel routes.
Default
bgp-transport-tunnel exclude
Parameters
- include
Keyword that enables RSVP-TE LSP to be used as transport LSP from ingress PE to ASBR in the local AS.
- exclude
Keyword that disables RSVP-TE LSP to be used as transport LSP from ingress PE to ASBR in the local AS.
cspf
Syntax
[no] cspf [use-te-metric]
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures Constrained Shortest Path First (CSPF) computation for constrained-path LSPs. Constrained-path LSPs are the ones that take configuration constraints into account. CSPF is also used to calculate the detour routes when the fast-reroute command is enabled.
Explicitly configured LSPs where each hop from ingress to egress is specified do not use CSPF. The LSP will be set up using RSVP signaling from ingress to egress.
If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, neither global revertive nor local revertive is available for the LSP to recover.
Default
no cspf
Parameters
- use-te-metric
Keyword to specify the use of the TE metric for the purpose of the LSP path computation by CSPF.
exclude
Syntax
[no] exclude group-name [group-name...(up to 5 max)]
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the admin groups to be excluded when an LSP is set up in the primary or secondary contexts.
Each single operation of the exclude command allows a maximum of five groups to be specified at a time. However, a maximum of 32 groups can be specified per LSP by using multiple operations. The admin groups are defined in the config>router>mpls>admin-group context.
The no form of this command removes the exclude command.
Default
no exclude
Parameters
- group-name
Specifies the existing group-name to be excluded when an LSP is set up.
fast-reroute
Syntax
fast-reroute frr-method
no fast-reroute
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures a precomputed detour LSP from each node in the path of the LSP. In case of failure of a link or LSP between two nodes, traffic is immediately rerouted on the precomputed detour LSP, which avoids packet loss.
When the fast-reroute command is enabled, each node along the path of the LSP tries to establish a detour LSP, as follows.
Each upstream node sets up a detour LSP that avoids only the immediate downstream node and merges back on to the actual path of the LSP as soon as possible.
If it is not possible to set up a detour LSP that avoids the immediate downstream node, a detour can be set up to the downstream node on a different interface.
The detour LSP may take one or more hops (see hop-limit) before merging back to the main LSP path.
When the upstream node detects a downstream link or node failure, the ingress router switches traffic to a standby path, if one was set up for the LSP.
Fast reroute is available only for the primary path. No configuration is required on the transit hops of the LSP. The ingress router signals all intermediate routers using RSVP to set up their detours. TE must be enabled for fast-reroute to work.
CSPF must be enabled for fast rerouter to work. If an LSP is configured with fast-reroute frr-method specified but without CSPF enabled, neither global revertive nor local revertive is available for the LSP to recover.
The no form of this fast-reroute command removes the detour LSP from each node on the primary path. This command also removes configuration information about the hop-limit and the bandwidth for the detour routes.
The no form of fast-reroute hop-limit command reverts to the default value.
Default
no fast-reroute
Parameters
- ffr-method
Specifies the fast reroute method to use.
bandwidth
Syntax
bandwidth rate-in-mbps
no bandwidth
Context
config>router>mpls>lsp>fast-reroute
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures reserved bandwidth on the detour path. When configuring an LSP, specify the traffic rate associated with the LSP.
When configuring the fast-reroute command, allocate bandwidth for the rerouted path. The bandwidth rate does not need to be the same as the bandwidth allocated for the LSP.
Default
no bandwidth
Parameters
- rate-in-mbps
Specifies the amount of bandwidth, in Mb/s, to be reserved for the LSP path.
hop-limit
Syntax
hop-limit limit
no hop-limit
Context
config>router>mpls>lsp>fast-reroute
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures how many more routers a detour can traverse compared to the LSP itself on a fast reroute. For example, if an LSP traverses four routers, any detour for the LSP can be no more than ten router hops, including the ingress and egress routers.
The no form of this command reverts to the default value.
Default
16
Parameters
- limit
Specifies the maximum number of hops.
node-protect
Syntax
[no] node-protect
Context
config>router>mpls>lsp>fast-reroute
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables or disables node and link protection on the specified LSP. Node protection ensures that traffic from an LSP traversing a neighboring router reaches its destination even if the neighboring router fails.
Default
node-protect
from
Syntax
from ip-address
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This optional command specifies the IP address of the ingress router for the LSP. When this command is not specified, the system IP address is used. IP addresses that are not defined in the system are allowed. If an invalid IP address is entered, LSP bring-up fails and an error is logged.
If an interface IP address is specified as the from address, and the egress interface of the next-hop IP address is a different interface, the LSP is not signaled. As the egress interface changes because of changes in the routing topology, an LSP recovers if the from IP address is the system IP address and not a specific interface IP address.
Only one from address can be configured.
Default
system IP address
Parameters
- ip-address
Specifies the IP address of the ingress router. This can be either the interface or the system IP address. If the IP address is local, the LSP must egress through that local interface, which ensures local strictness.
hop-limit
Syntax
hop-limit number
no hop-limit
Context
config>router>mpls>lsp
config>router>mpls>lsp>fast-reroute
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the maximum number of hops that an LSP can traverse, including the ingress and egress routers. An LSP is not set up if the hop limit is exceeded. This value can be changed dynamically for an LSP that is already set up with the following implications.
If the new value is less than the current number of hops of the established LSP, the LSP is brought down. The 7210 SAS then tries to re-establish the LSP within the new hop-limit number.
If the new value is equal to or greater than the current number hops of the established LSP, the LSP is not affected.
The no form of this command reverts to the default value.
Default
255
Parameters
- number
Specifies the number of hops the LSP can traverse, expressed as an integer.
include
Syntax
[no] include group-name [group-name...(up to 5 max)]
Context
config>router>mpls>lsp
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the admin groups to be included when an LSP is set up. Up to five groups per operation can be specified, up to 32 maximum.
The no form of this command deletes the specified groups in the specified context.
Default
no include
Parameters
- group-name
Specifies admin groups to be included when an LSP is set up.
metric
Syntax
metric metric
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the metric for this LSP, which is used to select an LSP among a set of LSPs that are destined for the same egress router. The LSP with the lowest metric is selected.
Default
1
Parameters
- metric
Specifies the metric for this LSP.
path-profile
Syntax
path-profile profile-id [path-group group-id]
no path-profile profile-id
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the PCE path profile and path group ID.
The PCE supports the computation of disjoint paths for two LSPs originating or terminating on the same or different PE routers. To indicate this constraint to the PCE, the user configures the PCE path profile ID and path group ID to which the PCE-computed or PCE-controlled LSP belongs. Because the PCC passes these parameters transparently to the PCE, the parameters are opaque data to the router.
The association of the optional path group ID allows the PCE to determine the profile ID to use with this path group ID. Although one path group ID is allowed for each profile ID, you can execute the path-profile command multiple times and enter the same path group ID with multiple profile IDs. A maximum of five path-profile profile-id [path-group group-id] entries can be associated with the same LSP.
Parameters
- profile-id
Specifies the profile ID.
- group-id
Specifies the path group ID.
pce-computation
Syntax
[no] pce-computation
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the PCE-computed LSP mode of operation for an RSVP-TE LSP.
The user can grant only path computation requests (PCE-computed) or both path computation requests and path updates (PCE-controlled) to a PCE for a specific LSP.
The pce-computation command sends the path computation request to the PCE instead of the local CSPF. Enabling this option allows the PCE to perform path computations for the LSP at the request of the PCC router only. This is used in cases where the user wants to use the PCE-specific path computation algorithm instead of the local router CSPF algorithm.
The enabling of the pce-computation requires that the cspf option first be enabled; otherwise, this configuration is rejected. Conversely, an attempt to disable the cspf option on an RSVP-TE LSP that has the pce-computation command or pce-control command enabled is rejected.
Default
no pce-computation
pce-control
Syntax
[no] pce-control
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the PCE-controlled LSP mode of operation for an RSVP-TE LSP.
Using the pce-control command, the PCC router delegates full control of the LSP to the PCE (PCE-controlled). As a result, PCE acts in an active stateful mode for this LSP. The PCE can reroute the path following a failure or reoptimize the path and update the router without an update request from the PCC router.
The user can delegate CSPF and non-CSPF LSPs, or LSPs that have the pce-computation option enabled or disabled. The LSP maintains the latest active path computed by the PCE or the PCC router at the time it is delegated. The PCE only updates the path at the next network event or reoptimization.
The enabling of the pce-control command requires that the cspf option first be enabled; otherwise, this configuration is rejected. Conversely, an attempt to disable the cspf option on an RSVP-TE LSP that has the pce-control command or pce-computation command enabled is rejected.
If PCE reporting is disabled for the LSP, either because of inheritance from the MPLS-level configuration or because of LSP-level configuration, enabling the pce-control option for the LSP has no effect.
Default
no pce-control
pce-report
Syntax
pce-report {enable | disable | inherit}
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the reporting mode to a PCE for an RSVP-TE LSP.
The PCC LSP database is synchronized with the PCE LSP database using the PCEP PCRpt (PCE Report) message for PCC-controlled, PCE-computed, and PCE-controlled LSPs.
Use the global MPLS-level pce-report command (config>router>mpls>pce-report) to enable or disable PCE reporting for all RSVP-TE LSPs during PCE LSP database synchronization.
The LSP-level pce-report command overrides the global configuration for reporting an LSP to the PCE. The default configuration is to inherit the global MPLS-level configuration. The inherit option reconfigures the LSP to inherit the global configuration.
Default
pce-report inherit
Parameters
- enable
Keyword to enable PCE reporting.
- disable
Keyword to disable PCE reporting.
- inherit
Keyword to inherit the global configuration for PCE reporting.
to
Syntax
to ip-address
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the system IP address of the egress router for the LSP. This command is mandatory to create an LSP.
An IP address for which a route does not exist is allowed in the configuration. If the LSP signaling fails because the destination is not reachable, an error is logged and the LSP operational status is set to down.
Parameters
- ip-address
Specifies the system IP address of the egress router.
retry-limit
Syntax
retry-limit number
no retry-limit
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This optional command specifies the number of attempts software should make to re-establish the LSP after it has failed LSP. After each successful attempt, the counter is reset to zero.
When the specified number is reached, no more attempts are made, and the LSP path is put into the shutdown state.
Use the config router mpls lsp lsp-name no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts to the default value.
Default
0
Parameters
- number
Specifies the number of times the 7210 SAS attempts to re-establish the LSP after it has failed. Allowed values are integers; 0 indicates to retry forever.
retry-timer
Syntax
retry-timer seconds
no retry-timer
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the time, in seconds, for LSP re-establishment attempts after the LSP has failed.
The no form of this command reverts to the default value.
Default
30
Parameters
- seconds
Specifies the amount of time, in seconds, between attempts to re-establish the LSP after it has failed.
rsvp-resv-style
Syntax
rsvp-resv-style [se | ff]
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the RSVP reservation style, shared explicit (se) or fixed filter (ff). A reservation style is a set of control options that specify a number of supported parameters. The style information is part of the LSP configuration.
Default
se
Parameters
- ff
Fixed filter is single reservation with an explicit scope. This reservation style specifies an explicit list of senders and a distinct reservation for each of them. A specific reservation request is created for data packets from a particular sender. The reservation scope is determined by an explicit list of senders.
- se
Shared explicit is shared reservation with a limited scope. This reservation style specifies a shared reservation environment with an explicit reservation scope. This reservation style creates a single reservation over a link that is shared by an explicit list of senders. Because each sender is explicitly listed in the RESV message, different labels can be assigned to different sender-receiver pairs, thereby creating separate LSPs.
shutdown
Syntax
[no] shutdown
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command disables the existing LSP including the primary and any standby secondary paths.
To shut down only the primary path, enter the config router mpls lsp lsp-name primary path-name shutdown command.
To shut down a specific standby secondary path, enter the config router mpls lsp lsp-name secondary path-name shutdown command. The existing configuration of the LSP is preserved.
The no form of this command restarts the LSP. LSPs are created in a shutdown state. Use this command to administratively bring up the LSP.
Default
shutdown
Primary and secondary path commands
primary
Syntax
primary path-name
no primary
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures a preferred path for the LSP. This command is optional only if the secondary path-name is included in the LSP definition. Only one primary path can be defined for an LSP.
Some of the attributes of the LSP, such as the bandwidth and hop-limit, can be optionally specified as the attributes of the primary path. The attributes specified in the primary path-name command override the LSP attributes.
The no form of this command deletes the association of this path-name from the LSP lsp-name. All configurations specific to this primary path, such as record, bandwidth, and hop limit, are deleted. The primary path must be first shut down to delete it.
The no form of this command results in no action except a warning message on the console indicating that the primary path is administratively up.
Parameters
- path-name
Specifies the case-sensitive alphanumeric name label for the LSP path, up to 32 characters.
secondary
Syntax
[no] secondary path-name
Context
config>router>mpls>lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures an alternative path that the LSP uses if the primary path is not available. This command is optional and is not required if the config router mpls lsp lsp-name primary path-name command is specified. After the switch over from the primary to the secondary, the 7210 SAS software continuously tries to revert to the primary path. The switch back to the primary path is based on the retry-timer interval.
Up to eight secondary paths can be specified. All the secondary paths are considered equal and the first available path is used. The 7210 SAS software does not switch back between secondary paths.
The 7210 SAS software starts the signaling of all non-standby secondary paths at the same time. Retry counters are maintained for each unsuccessful attempt. When the retry limit is reached on a path, the 7210 SAS software does not attempt to signal the path and administratively shuts down the path. The first successfully established path is made the active path for the LSP.
The no form of this command removes the association between this path-name and lsp-name. All specific configurations for this association are deleted. The secondary path must be shutdown first to delete it.
The no secondary path-name command results in no action except a warning message on the console indicating that the secondary path is administratively up.
Parameters
- path-name
Specifies the case-sensitive alphanumeric name label for the LSP path, up to 32 characters.
adaptive
Syntax
[no] adaptive
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the MBB functionality for an LSP or a primary or secondary LSP path. When enabled for the LSP, an MBB operation is performed for primary path and all the secondary paths of the LSP.
Default
adaptive
bandwidth
Syntax
bandwidth rate-in-mbps
no bandwidth
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies the amount of bandwidth to be reserved for the LSP path.
The no form of this command resets bandwidth parameters (no bandwidth is reserved).
Default
no bandwidth
Parameters
- rate-in-mbps
Specfies the amount of bandwidth reserved for the LSP path in Mb/s.
exclude
Syntax
[no] exclude group-name [group-name...(up to 5 max)]
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies the admin groups to be excluded when an LSP is set up. Up to 5 groups per operation can be specified, up to 32 maximum. The admin groups are defined in the config>router>mpls>admin-group context.
The no form of this command removes the exclude command.
Default
no exclude
Parameters
- group-name
Specifies the existing group name to be excluded when an LSP is set up.
hop-limit
Syntax
hop-limit number
no hop-limit
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command overrides the config router mpls lsp hop-limit command. This command specifies the total number of hops that an LSP traverses, including the ingress and egress routers.
This value can be changed dynamically for an LSP that is already set up with the following implications:
If the new value is less than the current hops of the established LSP, the LSP is brought down. MPLS then tries to re-establish the LSP within the new hop-limit number.
If the new value is equal or more than the current hops of the established LSP, the LSP is unaffected.
The no form of this command reverts to the values defined under the LSP definition using the config router mpls lsp lsp-name hop-limit command.
Default
no hop-limit
Parameters
- number
Specifies the number of hops the LSP can traverse, expressed as an integer.
path-preference
Syntax
[no] path-preference value
Context
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of path preference among configured standby secondary paths per LSP.
If all standby secondary paths have a default path-preference value, a non-standby secondary path remains an active path, while a standby secondary is available. A standby secondary path configured with highest priority (lowest path-preference value) must be made the active path when the primary is not in use. Path preference can be configured on standby secondary path.
The no form of this command reverts to the default value.
Default
255
Parameters
- value
Specifies an alternate path for the LSP if the primary path is not available.
record
Syntax
[no] record
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables recording of all the hops that an LSP path traverses. Enabling record increases the size of the PATH and RESV refresh messages for the LSP, because this information is carried end-to-end along the path of the LSP. The increase in control traffic per LSP may impact scalability.
The no form of this command disables the recording of all the hops for the specified LSP. There are no restrictions as to when the no command can be used.
The no form of this command also disables the record-label command.
Default
record
record-label
Syntax
[no] record-label
Context
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables recording of all the labels at each node that an LSP path traverses. Enabling the record-label command also enables the record command, if it is not already enabled.
The no form of this command disables the recording of the hops that an LSP path traverses.
Default
record-label
srlg
Syntax
[no] srlg
Context
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of the SRLG constraint in the computation of a secondary path for an LSP at the head-end LER.
When this feature is enabled, CSPF includes the SRLG constraint in the computation of the secondary LSP path. CSPF requires that the primary LSP already be established and in the up state, because the head-end LER needs the most current ERO computed by CSPF for the primary path. CSPF would return the list of SRLG groups along with the ERO during primary path CSPF computation. At a subsequent establishment of a secondary path with the SRLG constraint, the MPLS/RSVP task queries CSPF again, which provides the list of SLRG group numbers to be avoided. CSPF prunes all links with interfaces that belong to the same SRLGs as the interfaces included in the ERO of the primary path. If CSPF finds a path, the secondary is set up. If CSPF does not find a path, MPLS/RSVP keeps retrying the requests to CSPF.
If CSPF is not enabled on the LSP, a secondary path of that LSP that includes the SRLG constraint is shut down and a specific failure code indicates the exact reason for the failure in the show router mpls lsp path detail command output.
At initial primary LSP path establishment, if primary does not come up or primary is not configured, SRLG secondary is not signaled and is put in the down state. A specific failure code indicates the exact reason for the failure in show router mpls lsp path detail command output. However, if a non-SRLG secondary path was configured, such as a secondary path with the SRLG option disabled, the MPLS/RSVP task signals it and the LSP use it.
As soon as the primary path is configured and successfully established, MPLS/RSVP moves the LSP to the primary and signals all SRLG secondary paths.
Any time the primary path is reoptimized, has undergone MBB, or has come back up after being down, the MPLS/RSVP task checks with CSPF if the SRLG secondary should be resignaled. If MPLS/RSVP finds that the current secondary path is no longer SRLG disjoint, for example, it became ineligible and puts it on a delayed MBB immediately after the expiry of the retry timer. If MBB fails at the first try, the secondary path is torn down and the path is put on retry.
At the next opportunity that the primary path goes down, the LSP uses the path of an eligible SRLG secondary if it is in the up state. If all secondary eligible SLRG paths are in the down state, MPLS/RSVP uses a non SRLG secondary if configured and in the up state. If while the LSP is using a non SRLG secondary, an eligible SRLG secondary came back up, MPLS/RSVP does not switch the path of the LSP to it. As soon as primary is resignaled and comes up with a new SLRG list, MPLS/RSVP resignals the secondary using the new SRLG list.
A secondary path that becomes ineligible as a result of an update to the SRLG membership list of the primary path has the ineligibility status removed when any of the following occurs.
A successful MBB of the standby SRLG path, which makes it eligible again.
The standby path goes down. MPLS/RSVP puts the standby on retry at the expiry of the retry timer. If successful, it becomes eligible. If not successful after the retry-timer expires or the number of retries reaches the number configured under the retry-limit parameter, it is left down.
The primary path goes down. In this case, the ineligible secondary path is immediately torn down and is resignaled only when the primary comes back up with a new SRLG list.
When primary path of the LSP is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface the primary path is using would not be considered until the next opportunity the primary path is resignaled. The primary path may be resignaled because of a failure or an MBB operation. MBB occurs as a result of a global revertive operation, a timer-based or manual reoptimization of the LSP path, or an operator change to any of the path constraints.
When an SRLG secondary path is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface the secondary path is using would not be considered until the next opportunity the secondary path is resignaled. The secondary path is resignaled because of a failure, a resignaling of the primary path, or an MBB operation. MBB occurs as a result of a timer-based or manual reoptimization of the secondary path, or an operator change to any of the path constraints of the secondary path, including enabling or disabling the SRLG constraint.
Also, the user-configured include or exclude admin group statements for this secondary path are also checked together with the SRLG constraints by CSPF.
The no form of this command reverts to the default value.
Default
no srlg
standby
Syntax
[no] standby
Context
config>router>mpls>lsp>secondary
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
The secondary path LSP is normally signaled when the primary path LSP fails. The standby command ensures that the secondary path LSP is signaled and maintained indefinitely in a hot-standby state. When the primary path is re-established, the traffic is switched back to the primary path LSP.
The no form of this command specifies that the secondary LSP is signaled when the primary path LSP fails.
LSP path commands
hop
Syntax
hop hop-index ip-address {strict | loose}
no hop hop-index
Context
config>router>mpls>path
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the IP address of the hops that the LSP should traverse on its way to the egress router. The IP address can be the interface IP address or the system IP address. If the system IP address is specified, the LSP can choose the best available interface.
Optionally, the LSP ingress and egress IP address can be included as the first and the last hop. A hop list can include the ingress interface IP address, the system IP address, and the egress IP address of any of the hops being specified.
The no form of this command deletes hop list entries for the path. All the LSPs currently using this path are affected. Additionally, all services actively using these LSPs are affected. The path must be shut down first to delete the hop from the hop list. The no hop hop-index command results in no action except a warning message on the console indicating that the path is administratively up.
Parameters
- hop-index
Specifies the hop index, which is used to order the specified hops. The LSP always traverses from the lowest hop index to the highest. The hop index does not need to be sequential.
- ip-address
Specifies the system or network interface IP address of the transit router. The IP address can be the interface IP address or the system IP address. If the system IP address is specified, the LSP can choose the best available interface. A hop list can also include the ingress interface IP address, the system IP address, and the egress IP address of any of the specified hops.
- loose
Keyword that specifies the route taken by the LSP from the previous hop to this hop can traverse through other routers. Multiple hop entries with the same IP address are flagged as errors. Either the loose or strict keyword must be specified.
- strict
Keyword that specifies the LSP must take a direct path from the previous hop router to this router. No transit routers between the previous router and this router are allowed. If the IP address specified is the interface address, that is the interface the LSP must use. If there are direct parallel links between the previous router and this router and if system IP address is specified, any one of the available interfaces can be used by the LSP. The user must ensure that the previous router and this router have a direct link. Multiple hop entries with the same IP address are flagged as errors. Either the loose or strict keyword must be specified.
p2p-active-path-fast-retry
Syntax
p2p-active-path-fast-retry seconds
no p2p-active-path-fast-retry
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures a global parameter to apply a shorter retry timer for the first try after an active LSP path went down because of a local failure or the receipt of a RESVTear. This timer is used only on the first try. Subsequent retries continue to be governed by the existing LSP level retry timer.
Default
0 (disabled)
Parameters
- seconds
Specifies the retry timer, in seconds.
path
Syntax
[no] path path-name
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the path to be used for an LSP. A path can be used by multiple LSPs. A path can specify some or all hops from ingress to egress, and they can be either strict or loose. A path can also be empty (no path-name specified) in which case the LSP is set up based on IGP (best effort) calculated shortest path to the egress router. Paths are created in a shutdown state. A path must be shut down before making any changes (adding or deleting hops) to the path. When a path is shut down, any LSP using the path becomes operationally down.
To create a strict path from the ingress to the egress router, the ingress and egress routers must be included in the path statement.
The no form of this command deletes the path and all its associated configuration information. All the LSPs that are currently using this path are affected. All the services that are actively using these LSPs are also affected. A path must be shutdown and unbound from all LSPs using the path before it can be deleted. The no path path-name command results in no action except a warning message on the console indicating that the path may be in use.
Parameters
- path-name
Specifies a unique case-sensitive alphanumeric name label for the LSP path, up to 32 characters.
shutdown
Syntax
[no] shutdown
Context
config>router>mpls>path
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command disables the existing LSPs using this path. All services using these LSPs are affected. Binding information, however, is retained in those LSPs. Paths are created in the shutdown state.
The no form of this command administratively enables the path. All LSPs where this path is defined as primary or as standby secondary are established or re-established.
Default
shutdown
Static LSP commands
static-lsp
Syntax
[no] static-lsp lsp-name
Context
config>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures a static LSP on the ingress router. The static LSP is a manually set up LSP where the next-hop IP address and the outgoing label (push) must be specified.
The LSP must be shut down first to delete it. If the LSP is not shut down, the no static-lsp lsp-name command does nothing except generate a warning message on the console indicating that the LSP is administratively up.
The no form of this command deletes this static LSP and associated information.
Parameters
- lsp-name
Specifies the name that identifies the LSP, up to 32 alphanumeric characters.
push
Syntax
push label nexthop ip-address
no push label
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies the label to be pushed onto the label stack and the next-hop IP address for the static LSP.
The no form of this command removes the association of the label to push for the static LSP.
Parameters
- label
Specifies the label to push on the label stack. Label values 16 through 1,048,575 are defined as follows.
Label values16 through 31 are reserved.
Label values 32 through 1023 are available for static assignment.
Label values 1024 through 2047 are reserved for future use.
Label values 2048 through 18431 are statically assigned for services.
Label values 28672 through 131071 are dynamically assigned for both MPLS and services.
Label values 131072 through 1048575 are reserved for future use.
- nexthop ip-address
Specifies the IP address of the next hop toward the LSP egress router. If an ARP entry for the next hop exists, the static LSP is marked operational. If an ARP entry does not exist, the software sets the operational status of the static LSP to down and continues to send an ARP request for the configured next hop at fixed intervals.
shutdown
Syntax
[no] shutdown
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command administratively disables the static LSP.
The no form of this command administratively enables the static LSP.
Default
shutdown
to
Syntax
to ip-address
Context
config>router>mpls>static-lsp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the system IP address of the egress router for the static LSP. This command is required when creating an LSP. For LSPs that are used as transport tunnels for services, the to IP address must be the system IP address.
Parameters
- ip-address
Specifies the system IP address of the egress router.
RSVP configuration commands
Generic commands
shutdown
Syntax
[no] shutdown
Context
config>router>rsvp
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command disables the RSVP protocol instance or the RSVP-related functions for the interface. The RSVP configuration information associated with this interface is retained. When RSVP is administratively disabled, all the RSVP sessions are torn down. The existing configuration is retained.
The no form of this command administratively enables RSVP on the interface.
Default
shutdown
RSVP commands
rsvp
Syntax
[no] rsvp
Context
config>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
Commands in this context configure RSVP protocol parameters. RSVP is not enabled by default and must be explicitly enabled (no shutdown).
RSVP is used to set up LSPs. RSVP should be enabled on all router interfaces that participate in signaled LSPs.
The no form of this command deletes this RSVP protocol instance and removes all configuration parameters for this RSVP instance. To suspend the execution and maintain the existing configuration, use the shutdown command. RSVP must be shut down before the RSVP instance can be deleted. If RSVP is not shut down, the no rsvp command does nothing except issue a warning message on the console indicating that RSVP is still administratively enabled.
Default
no shutdown
bfd-enable
Syntax
[no] bfd-enable
Context
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of bidirectional forwarding (BFD) to control the state of the associated RSVP interface. This causes RSVP to register the interface with the BFD session on that interface.
Configure the BFD session parameters, such as transmit-interval, receive-interval, and multiplier, under the IP interface in the config>router>interface>bfd context.
It is possible that the BFD session on the interface was started because of a prior registration with another protocol, for example, OSPF or IS-IS.
The registration of an RSVP interface with BFD is performed at the time the neighbor gets its first session, which is when this node sends or receives a new Path message over the interface. However, if the session does not come up, because of not receiving a Resv for a new path message sent after the maximum number of retries, the LSP is shut down and the node deregisters with BFD. In general, the registration of RSVP with BFD is removed as soon as the last RSVP session is cleared.
The registration of an RSVP interface with BFD is performed independent of whether an RSVP hello is enabled on the interface. However, hello timeout clears all sessions toward the neighbor and RSVP deregisters with BFD at the clearing of the last session.
An RSVP session is associated with a neighbor based on the interface address the path message is sent to. If multiple interfaces exist to the same node, each interface is treated as a separate RSVP neighbor. The user must enable BFD on each interface, and RSVP registers with the BFD session running with each of those neighbors independently.
Similarly, the disabling of BFD on the interface results in removing registration of the interface with BFD.
When a BFD session transitions to the down state, the following actions are triggered:
for RSVP signaled LSPs, activation of FRR bypass/detour backup (PLR role), global revertive (head-end role), and switchover to secondary, if any (head-end role), for affected LSPs with FRR enabled
switchover to secondary, if any, and scheduling of retries for signaling the primary path of the non-FRR-affected LSPs (head-end role).
For more information about the list of protocols that support BFD, see the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
The no form of this command removes BFD from the associated RSVP protocol adjacency.
Default
no bfd-enable
graceful-shutdown
Syntax
[no] graceful-shutdown
Context
config>router>rsvp
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command initiates a graceful shutdown of the specified RSVP interface (maintenance interface) or all RSVP interfaces on the node (maintenance node), if applied at the RSVP level.
To initiate a graceful shutdown, the maintenance node generates a PathErr message with a specific error sub-code of Local Maintenance on TE Link required for each LSP that is exiting the maintenance interface.
The node performs a single MBB attempt for all adaptive CSPF LSPs it originates and LSP paths using the maintenance interfaces. If an alternative path for an affected LSP is not found, the LSP is maintained on its current path. The maintenance node also tears down and resignals any detour LSP path using listed maintenance interfaces as soon as they are not active.
The maintenance node floods an IGP TE LSA/LSP containing Link TLV for the links under graceful shutdown with the TE metric set to 0xffffffff and the unreserved bandwidth parameter set to zero.
A head-end LER node, upon receipt of the PathErr message, performs a single MBB attempt on the affected adaptive CSPF LSP. If an alternative path is not found, the LSP is maintained on its current path.
A node does not take any action on the paths of the following originating LSPs after receiving the PathErr message:
an adaptive CSPF LSP for which the PathErr indicates a node address in the address list and the node corresponds to the destination of the LSP. In this case, there are no alternative paths that can be found.
an adaptive CSPF LSP whose path has explicit hops defined using the listed maintenance interfaces or nodes.
a CSPF LSP with the adaptive option disabled and where the current path is over the listed maintenance interfaces in the PathErr message. These are not subject to MBB.
a non-CSPF LSP where the current path is over the listed maintenance interfaces in the PathErr message
The head-end LER node, upon receipt of the updates IPG TE LSA/LSP for the maintenance interfaces, updates the TE database. This information is used at the next scheduled CSPF computation for any LSP with a path that traverses any of the maintenance interfaces.
The no form of this command disables the graceful shutdown operation at the RSVP interface level or the RSVP level. The configured TE parameters of the maintenance links are restored and the maintenance node floods the links.
keep-multiplier
Syntax
keep-multiplier number
no keep-multiplier
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies an integer used by RSVP to declare that a reservation is down or the neighbor is down.
The no form of this command reverts to the default value.
Default
3
Parameters
- number
Specifies the keep-multiplier value.
refresh-reduction-over-bypass
Syntax
refresh-reduction-over-bypass [enable | disable]
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the refresh reduction capabilities over all bypass tunnels originating on this 7210 SAS PLR node or terminating on this 7210 SAS Merge Point (MP) node.
By default, this command is disabled. Because a bypass tunnel may merge with the primary LSP path in a node downstream of the next hop, there is no direct interface between the PLR and the MP node, and it is possible the latter will not accept summary refresh messages received over the bypass.
When disabled, the node as a PLR or MP will not set the "Refresh-Reduction-Capable" bit on RSVP messages pertaining to LSP paths tunneled over the bypass. The node will also not send Message-ID in RSVP messages. This effectively disables summary refresh.
Default
disable
rapid-retransmit-time
Syntax
rapid-retransmit-time hundred-milliseconds
no rapid-retransmit-time
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the value of the rapid retransmission interval. This is used in the retransmission mechanism based on an exponential backoff timer to handle unacknowledged message_id objects.
The RSVP-TE message with the same message-id is retransmitted every 2 × rapid-retransmit-time interval.
The node stops the retransmission of unacknowledged RSVP messages in the following cases when the updated backoff interval exceeds the value of the regular refresh interval or when the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.
The rapid retransmission Interval must be smaller than the regular refresh interval configured using the config router rsvp refresh-time command.
The no form of this command reverts to the default value.
Default
5
Parameters
- hundred-milliseconds
Specifies the rapid retransmission interval.
rapid-retry-limit
Syntax
rapid-retry-limit limit
no rapid-retry-limit
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the value of the rapid retry limit. This is used in the retransmission mechanism based on an exponential backoff timer to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 × rapid-retransmit-time interval.
The node stops the retransmission of unacknowledged RSVP messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit command, whichever comes first.
The no form of this command reverts to the default value.
Default
3
Parameters
- limit
Specifies the value of the rapid retry limit.
refresh-time
Syntax
refresh-time seconds
no refresh-time
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the interval between the successive Path and Resv refresh messages. RSVP declares the session down after it misses the consecutive refresh messages value configured in the keep-multiplier command.
The no form of this command reverts to the default value.
Default
30 seconds
Parameters
- seconds
Specifies the refresh time, in seconds.
Interface commands
interface
Syntax
[no] interface ip-int-name
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables RSVP protocol support on an IP interface. No RSVP commands are executed on an IP interface where RSVP is not enabled.
The no form of this command deletes all RSVP commands, such as hello-interval and subscription, that are defined for the interface. The RSVP interface must be shutdown before it can be deleted. If the interface is not shut down, the no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
Default
shutdown
Parameters
- ip-int-name
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
Context
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the authentication key used between RSVP neighbors to authenticate RSVP messages. Authentication uses the MD-5 message-based digest.
When enabled on an RSVP interface, authentication of RSVP messages operates in both directions of the interface.
A node maintains a security association using one authentication key for each interface to a neighbor. The following items are stored in the context of this security association:
HMAC-MD5 authentication algorithm
key used with the authentication algorithm
lifetime of the key; the user-entered key is valid until the user deletes it from the interface
source address of the sending system
latest sending sequence number used with this key identifier
An RSVP sender transmits an authenticating digest of the RSVP message, computed using the shared authentication key and a keyed-hash algorithm. The message digest is included in an integrity object that also contains a flags field, a key identifier field, and a sequence number field. The RSVP sender complies with the procedures for RSVP message generation in RFC 2747, RSVP Cryptographic Authentication.
An RSVP receiver uses the key together with the authentication algorithm to process received RSVP messages.
The MD5 implementation does not support the authentication challenge procedures in RFC 2747.
The no form of this command disables authentication.
Default
no authentication-key
Parameters
- authentication-key
Specifies the authentication key. The key can be any combination of ASCII characters up to 16 characters in length (unencrypted). If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- hash-key
Specifies the hash key. The key can be any combination of up 33 alphanumeric characters. If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but for security purposes the actual unencrypted key value is not provided.
- hash
Keyword to specify the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
- hash2
Keyword to specify the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
hello-interval
Syntax
hello-interval milli-seconds
no hello-interval
Context
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the time interval between RSVP hello messages.
RSVP hello packets detect loss of RSVP connectivity with the neighboring node. Hello packets detect the loss of the neighbor more quickly than it would take for the RSVP session to time out based on the refresh interval. After the loss of the of keep-multiplier number consecutive hello packets, the neighbor is declared to be in a down state.
The no form of this command reverts to the default value. To disable sending hello messages, set the value to zero.
Default
3000 milliseconds
Parameters
- milli-seconds
Specifies the RSVP hello interval in milliseconds, in multiples of 1000. A 0 (zero) value disables the sending of RSVP hello messages.
implicit-null-label
Syntax
implicit-null-label [enable | disable]
no implicit-null-label
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of the implicit null label for all LSPs signaled by RSVP on the node.
All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface signals the implicit null label. If the egress LER is also the merge-point (MP) node, the incoming interface for the path refresh message over the bypass dictates whether the packet uses the implicit null label. The same is true for a 1-to-1 detour LSP.
The RSVP interface must be shut down before changing the implicit-null-label command.
The no form of this command reverts the RSVP interface to using the RSVP level configuration value.
Default
disable
Parameters
- enable
Keyword to enable the implicit null label.
- disable
Keyword to disable the implicit null label.
refresh-reduction
Syntax
[no] refresh-reduction
Context
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables the use of the RSVP overhead refresh reduction capabilities on this RSVP interface.
The no form of this command reverts to the default value.
Default
no refresh-reduction
reliable-delivery
Syntax
[no] reliable-delivery
Context
config>router>rsvp>interface>refresh-reduction
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures reliable delivery of RSVP messages over the RSVP interface. When the refresh-reduction command is enabled on an interface and the reliable-delivery command is disabled, the router sends a message_id and not set ACK desired in the RSVP messages over the interface. The router does not expect an ACK but accepts it if received. The node also accepts message IDs and replies with an ACK when requested. In this case, if the neighbor set the "refresh-reduction-capable" bit in the flags field of the common RSVP header, the node enters summary refresh for a specific message_id it sent regardless of whether it received an ACK to this message from the neighbor.
Finally, when the reliable-delivery command is enabled on any interface, RSVP message pacing is disabled on all RSVP interfaces on the system; for example, the user cannot enable the msg-pacing option in the config>router>rsvp context, and an error message is returned in the CLI. When the msg-pacing option is enabled, the user cannot enable the reliable delivery option on any interface on this system. An error message is also generated in the CLI after such an attempt.
The no form of this command reverts to the default value.
Default
no reliable-delivery
subscription
Syntax
subscription percentage
no subscription
Context
config>router>rsvp>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the percentage of the link bandwidth that RSVP can use for reservation and sets a limit for the amount of over-subscription or under-subscription allowed on the interface.
When the subscription is set to zero, no new sessions are permitted on this interface. If the percentage value is exceeded, the reservation is rejected and a log message is generated.
The no form of this command reverts to the default value.
Default
100
Parameters
- percentage
Specifies the percentage of the interface bandwidth that RSVP allows to be used for reservations.
Message pacing commands
msg-pacing
Syntax
[no] msg-pacing
Context
config>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures RSVP message pacing, in which the specified number of RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the period command. A count is kept of the messages that are dropped because the output queue for the interface used for message pacing is full.
Default
no msg-pacing
max-burst
Syntax
max-burst number
no max-burst
Context
config>router>rsvp>msg-pacing
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the maximum number of RSVP messages that are sent in the specified period under normal operating conditions.
Default
650
Parameters
- number
Specifies the maximum number of RSVP messages.
period
Syntax
period milli-seconds
no period
Context
config>router>rsvp>msg-pacing
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the time interval, in milliseconds, during which the router can send the specified number of RSVP messages, as specified in the max-burst command.
Default
100
Parameters
- milli-seconds
Specifies the time period during which the router can send RSVP messages.
Show commands
Show MPLS commands
bypass-tunnel
Syntax
bypass-tunnel [to ip-address] [protected-lsp [lsp-name]] [dynamic | manual] [detail]
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
If fast reroute is enabled on an LSP and the facility method is selected, instead of creating a separate LSP for every LSP that is to be backed up, a single LSP is created that serves as a backup for a set of LSPs. Such an LSP tunnel is called a bypass tunnel.
Parameters
- ip-address
Specifies the IP address of the egress router.
- lsp-name
Specifies the name of the LSP protected by the bypass tunnel.
- dynamic
Displays dynamically assigned labels for bypass protection.
- manual
Displays manually assigned labels for bypass protection.
- detail
Displays detailed information.
Output
The following output is an example of MPLS bypass tunnel information, and Output fields: MPLS bypass tunnel describes the output fields.
Sample output*A:Dut-A>show>router>mpls# bypass-tunnel
===============================================================================
MPLS Bypass Tunnels
===============================================================================
Legend : m - Manual d - Dynamic
===============================================================================
To State Out I/F Out Label Reserved Protected Type
BW (Kbps) LSP Count
-------------------------------------------------------------------------------
10.10.36.3 Up lag-1:10 131066 0 2 d
10.10.23.2 Up lag-1:10 130454 0 4 d
10.10.46.4 Up lag-2 130592 0 4 d
10.10.36.6 Up lag-2 130591 0 2 d
-------------------------------------------------------------------------------
Bypass Tunnels : 4
===============================================================================
*A:Dut-A>show>router>mpls#
Label |
Description |
|---|---|
To |
The system IP address of the egress router |
State |
The LSP administrative state |
Out I/F |
Specifies the name of the network IP interface |
Out Label |
Specifies the incoming MPLS label on which to match |
Reserved BW (Kbps) |
Specifies the amount of bandwidth in kilobytes per second (Kb/s) reserved for the LSP |
interface
Syntax
interface [ip-int-name | ip-address] [label-map label]
interface [ip-int-name | ip-address]
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS interface information.
Parameters
- ip-int-name
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- ip-address
Specifies the system or network interface IP address.
- label
Specifies the MPLS label on which to match.
Output
The following output is an example of MPLS interface information, and Output fields: MPLS interface describes the output fields.
Sample outputA:7210SAS# show router mpls interface
===============================================================================
MPLS Interfaces
===============================================================================
Interface Port-id Adm Opr TE-metric
-------------------------------------------------------------------------------
system system Up Up None
Admin Groups None
Srlg Groups None
ip-10.10.2.3 1/1/15 Up Up None
Admin Groups None
Srlg Groups None
ip-10.10.5.3 1/1/1 Up Up None
Admin Groups None
Srlg Groups None
ip-10.10.11.3 1/1/3 Up Up None
Admin Groups None
Srlg Groups None
ip-10.10.12.3 lag-1 Up Up None
Admin Groups None
Srlg Groups None
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
*A:7210SAS#
Label |
Description |
|---|---|
Interface |
The interface name |
Port-id |
The port ID displayed in slot/mda/port format |
Adm |
Specifies the administrative state of the interface |
Opr |
Specifies the operational state of the interface |
Srlg Groups |
Specifies the shared risk link group (SRLG) names |
Te-metric |
Specifies the traffic engineering metric used on the interface |
Interfaces |
The total number of interfaces |
Transmitted |
Displays the number of packets and octets transmitted from the interface |
Received |
Displays the number of packets and octets received |
In Label |
Specifies the ingress label |
In I/F |
Specifies the ingress interface |
Out Label |
Specifies the egress label |
Out I/F |
Specifies the egress interface |
Next Hop |
Specifies the next hop IP address for the static LSP |
Type |
Specifies whether the label value is statically or dynamically assigned |
label
Syntax
label start-label [end-label | in-use | label-owner]
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS labels exchanged.
Parameters
- start-label
Specifies the label value assigned at the ingress router.
- end-label
Specifies the label value assigned for the egress router.
- in-use
Specifies the number of in-use labels displayed.
- label-owner
Specifies the owner of the label.
Output
The following output is an example of MPLS label information, and Output fields: MPLS label describes the output fields.
Sample output*A:SRU4>config>router>mpls# show router mpls label 202
=================================================================
MPLS Label 202
=================================================================
Label Label Type Label Owner
-----------------------------------------------------------------
202 static-lsp STATIC
-----------------------------------------------------------------
In-use labels in entire range : 5057
=================================================================
*A:SRU4>config>router>mpls#
Label |
Description |
|---|---|
Label |
Displays the value of the label |
Label Type |
Specifies whether the label value is statically or dynamically assigned |
Label Owner |
The label owner |
In-use labels in entire range |
The total number of labels being used by RSVP |
label-range
Syntax
label-range
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays the MPLS label range.
Output
The following output is an example of MPLS label range information, and Output fields: MPLS label describes the output fields.
Sample output*A:Dut-A# show router mpls-labels label-range
============================================================================
Label Ranges
============================================================================
Label Type Start Label End Label Aging Available Total
----------------------------------------------------------------------------
Static 32 18431 - 18399 18400
Dynamic 18432 131071 0 112635 112640
Seg-Route 0 0 - 0 112640
============================================================================
*A:Dut-A#
Label |
Description |
|---|---|
Label Type |
Displays the information about static-lsp, static-svc, and dynamic label types |
Start Label |
The label value assigned at the ingress router |
End Label |
The label value assigned for the egress router |
Aging |
The number of labels released from a service that are transitioning back to the label pool. Labels are aged 15 seconds. |
Total Available |
The number of label values available |
lsp
Syntax
lsp lsp-name [status {up | down}] [from ip-address | to ip-address] [detail]
lsp {transit | terminate} [status {up | down}] [from ip-address | to ip-address | lsp-name name] [detail]
lsp count
lsp lsp-name activepath
lsp lsp-name path [path-name] [status {up | down}] [detail]
lsp [lsp-name] path [path-name] mbb
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays LSP details.
Parameters
- lsp lsp-name
Specifies the name of the LSP used in the path.
- status up
Displays an LSP that is operationally up.
- status down
Displays an LSP that is operationally down.
- from ip-address
Displays the IP address of the ingress router for the LSP.
- to ip-address
Displays the IP address of the egress router for the LSP.
- transit
Displays the number of static LSPs that transit through the router.
- terminate
Displays the number of static LSPs that terminate at the router.
- name
Specifies the IP address of the named LSP.
- lsp count
Displays the total number of LSPs.
- activepath
Displays the present path being used to forward traffic.
- path-name
Specifies the name of the path carrying the LSP.
- mbb
Displays make-before-break (MBB) information.
- detail
Displays detailed information.
Output
The following output is an example of MPLS LSP information, and Output fields: MPLS LSP describes the output fields.
Sample output*A:SRU4>config>router>mpls# show router mpls lsp "to_10_20_1_1_cspf"
===============================================================================
MPLS LSPs (Originating)
===============================================================================
LSP Name To Fastfail Adm Opr
Config
-------------------------------------------------------------------------------
to_10_20_1_1_cspf 10.20.1.1 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
*A:SRU4>config>router>mpls#
===============================================================================
*A:7210-SAS>show>router>mpls# lsp A detail
===============================================================================
MPLS LSPs (Originating) (Detail)
===============================================================================
-------------------------------------------------------------------------------
Type : Originating
-------------------------------------------------------------------------------
LSP Name : A LSP Tunnel ID : 1
From : 2.2.2.2 To : 10.100.100.100
Adm State : Up Oper State : Down
LSP Up Time : 0d 00:00:00 LSP Down Time : 0d 00:05:42
Transitions : 2 Path Changes : 2
Retry Limit : 0 Retry Timer : 30 sec
Signaling : RSVP Resv. Style : SE
Hop Limit : 255 Negotiated MTU : 0
Adaptive : Enabled ClassType : 0
FastReroute : Disabled Oper FR : Disabled
CSPF : Disabled ADSPEC : Disabled
Metric : 0
Include Grps: Exclude Grps :
None None
Type : RegularLsp Least Fill : Disabled
LdpOverRsvp : Enabled VprnAutoBind : Enabled
Oper Metric : 65535
Primary : A Down Time : 0d 00:05:42
Bandwidth : 0 Mbps
===============================================================================
*A:7210-SAS>show>router>mpls# lsp 2 detail
Label |
Description |
|---|---|
LSP Name |
The name of the LSP used in the path |
To |
The system IP address of the egress router for the LS. |
Adm State |
Down — The path is administratively disabled |
Up — The path is administratively enabled |
|
Oper State |
Down — The path is operationally down |
Up — The path is operationally up |
|
Oper State |
Down — The path is operationally down |
Up — The path is operationally up |
|
LSPs |
The total number of LSPs configured |
From |
The IP address of the ingress router for the LSP |
LSP Up Time |
The length of time the LSP has been operational |
Transitions |
The number of transitions that have occurred for the LSP |
Retry Limit |
The number of attempts that the software should make to re-establish the LSP after it has failed |
Signaling |
Specifies the signaling style |
Hop Limit |
The maximum number of hops that an LSP can traverse, including the ingress and egress routers |
Fast Reroute/FastFail Config |
enabled — Fast reroute is enabled. In the event of a failure, traffic is immediately rerouted on the precomputed detour LSP, which minimizes packet loss. |
disabled — There is no detour LSP from each node on the primary path |
|
ADSPEC |
enabled — The LSP includes advertising data (ADSPEC) objects in RSVP messages |
disabled — The LSP does not include advertising data (ADSPEC) objects in RSVP messages |
|
Primary |
The preferred path for the LSP |
Secondary |
The alternate path that the LSP uses if the primary path is not available. |
Bandwidth |
The amount of bandwidth in megabits per second (Mbps) reserved for the LSP path. |
LSP Up Time |
The total time in increments that the LSP path has been operational |
LSP Tunnel ID |
The value that identifies the label switched path that is signaled for this entry |
To |
The IP address of the egress router for the LSP |
LSP Down Time |
The total time, in increments, that the LSP path has not been operational |
Path Changes |
The number of path changes this LSP has had. For every path change (path down, path up, path change), a corresponding syslog/trap (if enabled) is generated. |
Retry Timer |
The time, in seconds, for LSP re-establishment attempts after an LSP failure |
Resv Style |
se — Specifies a shared reservation environment with a limited reservation scope. This reservation style creates a single reservation over a link that is shared by an explicit list of senders. |
ff — Specifies a shared reservation environment with an explicit reservation scope. Specifies an explicit list of senders and a distinct reservation for each of them. |
|
Negotiated MTU |
The size of the maximum transmission unit (MTU) that is negotiated during establishment of the LSP |
FR Hop Limit |
The total number of hops a detour LSP can take before merging back onto the main LSP path |
LastResignalAttempt |
Displays the system up time when the last attempt to resignal this LSP was made |
VprnAutoBind |
Displays the status on the VPRN auto-bind feature as enabled or disabled |
srlg-database
Syntax
srlg-database [router-id ip-address] [interface ip-address]
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS SRLG database information.
Parameters
- router-id ip-address
Specifies a 32-bit integer that uniquely identifies the router in the AS. To ensure uniqueness, this may default to the value of one of the router's IPv4 host addresses, represented as a 32-bit unsigned integer, if IPv4 is configured on the router. The router ID can be either the local one or a remote router.
- interface ip-address
Specifies the IP address of the interface.
path
Syntax
path [path-name] [lsp-binding]
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS paths.
Parameters
- path-name
Specifies the unique name label for the LSP path.
- lsp-binding
Displays binding information.
Output
The following output is an example of MPLS path information, and Output fields: MPLS path describes the output fields.
Sample output*A:SRU4>config>router>mpls# show router mpls path
===============================================================================
MPLS Path:
===============================================================================
Path Name Adm Hop Index IP Address Strict/Loose
-------------------------------------------------------------------------------
to_110_20_1_1 Up no hops n/a n/a
to_110_20_1_2 Up no hops n/a n/a
to_110_20_1_3 Up no hops n/a n/a
to_110_20_1_4 Up no hops n/a n/a
to_110_20_1_5 Up no hops n/a n/a
to_110_20_1_6 Up no hops n/a n/a
to_110_20_1_110 Up no hops n/a n/a
to_10_8_100_15 Up no hops n/a n/a
to_10_20_1_20 Up no hops n/a n/a
to_10_20_1_22 Up no hops n/a n/a
to_10_100_1_1 Up no hops n/a n/a
------------------------------------------------------------------------------
Paths : 11
===============================================================================
*A:SRU4>config>router>mpls#
Label |
Description |
|---|---|
Path Name |
The unique name label for the LSP path |
Adm |
Down — the path is administratively disabled Up — the path is administratively enabled |
Hop Index |
The value used to order the hops in a path |
IP Address |
The IP address of the hop that the LSP should traverse on the way to the egress router |
Strict/Loose |
Strict — the LSP must take a direct path from the previous hop router to the next router Loose — the route taken by the LSP from the previous hop to the next hop can traverse through other routers |
LSP Name |
The name of the LSP used in the path |
Binding |
Primary — the preferred path for the LSP Secondary — the standby path for the LSP |
Paths |
Total number of paths configured |
static-lsp
Syntax
static-lsp [lsp-name]
static-lsp [lsp-type {transit | terminate}]
static-lsp count
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS static LSP information.
Parameters
- lsp-name
Specifies a name that identifies the LSP.
- lsp-type
Specifies the type that identifies the LSP.
transit — Displays the number of static LSPs that transit the router.
terminate — Displays the number of static LSPs that terminate at the router.
- count
Displays the number of static LSPs that originate and terminate at the router.
Output
The following output is an example of MPLS static LSP information, and Output fields: MPLS static LSP describes the output fields.
Sample outputA:ALA-12# show router mpls static-lsp
===============================================================================
MPLS Static LSPs (Originating)
===============================================================================
Lsp Name To Next Hop Out Label Out I/F Adm Opr
-------------------------------------------------------------------------------
NYC_SJC_customer2 10.20.1.10 10.10.1.4 1020 1/1/1 Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
A:ALA-12#
*A:SRU4>config>router>mpls# show router mpls static-lsp transit
===============================================================================
MPLS Static LSPs (Transit)
===============================================================================
In Label In Port Out Label Out Port Next Hop Adm Opr
-------------------------------------------------------------------------------
240 aps-1 440 1/1/10 10.22.11.3 Up Up
241 aps-1 441 1/1/10 10.22.11.3 Up Up
242 aps-1 442 1/1/10 10.22.11.3 Up Up
243 aps-1 443 1/1/10 10.22.11.3 Up Up
244 aps-1 444 1/1/10 10.22.11.3 Up Up
245 aps-1 445 1/1/10 10.22.11.3 Up Up
246 aps-1 446 1/1/10 10.22.11.3 Up Up
247 aps-1 447 1/1/10 10.22.11.3 Up Up
248 aps-1 448 1/1/10 10.22.11.3 Up Up
249 aps-1 449 1/1/10 10.22.11.3 Up Up
250 aps-1 450 1/1/10 10.22.11.3 Up Up
251 aps-1 451 1/1/10 10.22.11.3 Up Up
252 aps-1 452 1/1/10 10.22.11.3 Up Up
253 aps-1 453 1/1/10 10.22.11.3 Up Up
...
207 3/2/8 407 1/1/9 10.22.10.3 Up Up
208 3/2/8 408 1/1/9 10.22.10.3 Up Up
209 3/2/8 409 1/1/9 10.22.10.3 Up Up
-------------------------------------------------------------------------------
LSPs : 256
===============================================================================
*A:SRU4>config>router>mpls#
A:ALA-12# show router mpls static-lsp terminate
===============================================================================
MPLS Static LSPs (Terminate)
===============================================================================
In Label In I/F Out Label Out I/F Next Hop Adm Opr
-------------------------------------------------------------------------------
1021 1/1/1 n/a n/a n/a Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
A:ALA-12#
Label |
Description |
|---|---|
Lsp Name |
The name of the LSP used in the path |
To |
The system IP address of the egress router for the LSP |
Next Hop |
The system IP address of the next hop in the LSP path |
In I/F |
The ingress interface |
Out Label |
The egress label |
Out I/F |
The egress interface |
Adm |
Down — the path is administratively disabled Up — the path is administratively enabled |
Opr |
Down — the path is operationally down Up — the path is operationally up |
LSPs |
The total number of static LSPs |
status
Syntax
status
Context
show>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays MPLS operation information.
Output
The following output is an example of MPLS status information, and Output fields: MPLS status describes the output fields.
Sample output*A:7210SAS# show router mpls status
===============================================================================
MPLS Status
===============================================================================
Admin Status : Up Oper Status : Up
Oper Down Reason : n/a
FR Object : Enabled Resignal Timer : Disabled
Hold Timer : 1 seconds Next Resignal : N/A
Srlg Frr : Disabled Srlg Frr Strict : Disabled
Dynamic Bypass : Enabled User Srlg Database : Disabled
Least Fill Min Thd.: 5 percent LeastFill ReoptiThd: 10 percent
Short. TTL Prop Lo*: Enabled Short. TTL Prop Tr*: Enabled
AB Sample Multipli*: 1 AB Adjust Multipli*: 288
Exp Backoff Retry : Disabled CSPF On Loose Hop : Disabled
Lsp Init RetryTime*: 30 seconds
Logger Event Bundl*: Disabled
Sec FastRetryTimer : Disabled Static LSP FR Timer: 30 seconds
P2P Max Bypass Ass*: 1000
P2PActPathFastRetry: Disabled
In Maintenance Mode: No
LSP Counts Originate Transit Terminate
-------------------------------------------------------------------------------
Static LSPs 0 0 0
Dynamic LSPs 0 0 1
Detour LSPs 0 0 0
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:7210SAS#
Label |
Description |
|---|---|
Admin Status |
Down — MPLS is administratively disabled Up — MPLS is administratively enabled |
Oper Status |
Down — MPLS is operationally down Up — MPLS is operationally up |
LSP Counts |
Static LSPs — Displays the count of static LSPs that originate, transit, and terminate on or through the router. Dynamic LSPs — Displays the count of dynamic LSPs that originate, transit, and terminate on or through the router Detour LSPs — Displays the count of detour LSPs that originate, transit, and terminate on or through the router |
FR Object |
Enabled — Specifies that Fast reroute object is signaled for the LSP Disabled — Specifies that Fast reroute object is not signaled for the LSP |
Resignal Timer |
Enabled — Specifies that the resignal timer is enabled for the LSP Disabled — Specifies that the resignal timer is disabled for the LSP |
Hold Timer |
Displays the amount of time that the ingress node holds before programming its data plane and declaring the LSP up to the service module |
Show RSVP commands
interface
Syntax
interface [ip-int-name | ip-address] statistics [detail]
Context
show>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command shows RSVP interfaces.
Parameters
- ip-int-name
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- ip-address
Specifies the system or network interface IP address.
- statistics
Displays IP address and the number of packets sent and received on an interface-basis.
- detail
Displays detailed information.
Output
The following output is an example of RSVP interface information, and Output fields: RSVP interface describes the fields.
Sample output*A:A:ALA-1>show>router>rsvp# interface detail
===============================================================================
RSVP Interfaces (Detailed)
===============================================================================
-------------------------------------------------------------------------------
Interface : system
-------------------------------------------------------------------------------
Interface : system
Port ID : system
Admin State : Up Oper State : Up
Active Sessions : 0 Active Resvs : 0
Total Sessions : 0
Subscription : 100 % Port Speed : 0 Mbps
Total BW : 0 Mbps Aggregate : Dsabl
Hello Interval : 3000 ms Hello Timeouts : 0
Authentication : Disabled
Auth Rx Seq Num : n/a Auth Key Id : n/a
Auth Tx Seq Num : n/a Auth Win Size : n/a
Refresh Reduc. : Disabled Reliable Deli. : Disabled
Bfd Enabled : No Graceful Shut. : Disabled
Percent Link Bandwidth for Class Types
Link Bw CT0 : 100 Link Bw CT4 : 0
Link Bw CT1 : 0 Link Bw CT5 : 0
Link Bw CT2 : 0 Link Bw CT6 : 0
Link Bw CT3 : 0 Link Bw CT7 : 0
Bandwidth Constraints for Class Types (Kbps)
BC0 : 0 BC4 : 0
BC1 : 0 BC5 : 0
BC2 : 0 BC6 : 0
BC3 : 0 BC7 : 0
Bandwidth for TE Class Types (Kbps)
TE0-> Resv. Bw : 0 Unresv. Bw : 0
TE1-> Resv. Bw : 0 Unresv. Bw : 0
TE2-> Resv. Bw : 0 Unresv. Bw : 0
TE3-> Resv. Bw : 0 Unresv. Bw : 0
TE4-> Resv. Bw : 0 Unresv. Bw : 0
TE5-> Resv. Bw : 0 Unresv. Bw : 0
TE6-> Resv. Bw : 0 Unresv. Bw : 0
TE7-> Resv. Bw : 0 Unresv. Bw : 0
No Neighbors.
-------------------------------------------------------------------------------
Interface : ip-10.10.12.3
-------------------------------------------------------------------------------
Interface : ip-10.10.12.3
Port ID : 1/1/9
Admin State : Up Oper State : Up
Active Sessions : 1 Active Resvs : 0
Total Sessions : 1
Subscription : 100 % Port Speed : 1000 Mbps
Total BW : 1000 Mbps Aggregate : Dsabl
Hello Interval : 3000 ms Hello Timeouts : 0
Authentication : Disabled
Auth Rx Seq Num : n/a Auth Key Id : n/a
Auth Tx Seq Num : n/a Auth Win Size : n/a
Refresh Reduc. : Disabled Reliable Deli. : Disabled
Bfd Enabled : No Graceful Shut. : Disabled
Percent Link Bandwidth for Class Types
Link Bw CT0 : 100 Link Bw CT4 : 0
Link Bw CT1 : 0 Link Bw CT5 : 0
Link Bw CT2 : 0 Link Bw CT6 : 0
Link Bw CT3 : 0 Link Bw CT7 : 0
Bandwidth Constraints for Class Types (Kbps)
BC0 : 1000000 BC4 : 0
BC1 : 0 BC5 : 0
BC2 : 0 BC6 : 0
BC3 : 0 BC7 : 0
Bandwidth for TE Class Types (Kbps)
TE0-> Resv. Bw : 0 Unresv. Bw : 1000000
TE1-> Resv. Bw : 0 Unresv. Bw : 1000000
TE2-> Resv. Bw : 0 Unresv. Bw : 1000000
TE3-> Resv. Bw : 0 Unresv. Bw : 1000000
TE4-> Resv. Bw : 0 Unresv. Bw : 1000000
TE5-> Resv. Bw : 0 Unresv. Bw : 1000000
TE6-> Resv. Bw : 0 Unresv. Bw : 1000000
TE7-> Resv. Bw : 0 Unresv. Bw : 1000000
Neighbors : 10.10.12.2
-------------------------------------------------------------------------------
Interface : ip-10.10.4.3
-------------------------------------------------------------------------------
Interface : ip-10.10.4.3
Port ID : 1/1/8
Admin State : Up Oper State : Up
Active Sessions : 1 Active Resvs : 0
Total Sessions : 1
Subscription : 100 % Port Speed : 1000 Mbps
Total BW : 1000 Mbps Aggregate : Dsabl
Hello Interval : 3000 ms Hello Timeouts : 0
Authentication : Disabled
Auth Rx Seq Num : n/a Auth Key Id : n/a
Auth Tx Seq Num : n/a Auth Win Size : n/a
Refresh Reduc. : Disabled Reliable Deli. : Disabled
Bfd Enabled : No Graceful Shut. : Disabled
Percent Link Bandwidth for Class Types
Link Bw CT0 : 100 Link Bw CT4 : 0
Link Bw CT1 : 0 Link Bw CT5 : 0
Link Bw CT2 : 0 Link Bw CT6 : 0
Link Bw CT3 : 0 Link Bw CT7 : 0
Bandwidth Constraints for Class Types (Kbps)
BC0 : 1000000 BC4 : 0
BC1 : 0 BC5 : 0
BC2 : 0 BC6 : 0
BC3 : 0 BC7 : 0
Bandwidth for TE Class Types (Kbps)
TE0-> Resv. Bw : 0 Unresv. Bw : 1000000
TE1-> Resv. Bw : 0 Unresv. Bw : 1000000
TE2-> Resv. Bw : 0 Unresv. Bw : 1000000
TE3-> Resv. Bw : 0 Unresv. Bw : 1000000
TE4-> Resv. Bw : 0 Unresv. Bw : 1000000
TE5-> Resv. Bw : 0 Unresv. Bw : 1000000
TE6-> Resv. Bw : 0 Unresv. Bw : 1000000
TE7-> Resv. Bw : 0 Unresv. Bw : 1000000
Neighbors : 10.10.4.2
-------------------------------------------------------------------------------
Interface : ip-10.10.2.3
-------------------------------------------------------------------------------
Interface : ip-10.10.2.3
Port ID : 1/1/4
Admin State : Up Oper State : Down
Active Sessions : 0 Active Resvs : 0
Total Sessions : 0
Subscription : 100 % Port Speed : 0 Mbps
Total BW : 0 Mbps Aggregate : Dsabl
Hello Interval : 3000 ms Hello Timeouts : 0
Authentication : Disabled
Auth Rx Seq Num : n/a Auth Key Id : n/a
Auth Tx Seq Num : n/a Auth Win Size : n/a
Refresh Reduc. : Disabled Reliable Deli. : Disabled
Bfd Enabled : No Graceful Shut. : Disabled
Percent Link Bandwidth for Class Types
Link Bw CT0 : 100 Link Bw CT4 : 0
Link Bw CT1 : 0 Link Bw CT5 : 0
Link Bw CT2 : 0 Link Bw CT6 : 0
Link Bw CT3 : 0 Link Bw CT7 : 0
Bandwidth Constraints for Class Types (Kbps)
BC0 : 0 BC4 : 0
BC1 : 0 BC5 : 0
BC2 : 0 BC6 : 0
BC3 : 0 BC7 : 0
Bandwidth for TE Class Types (Kbps)
TE0-> Resv. Bw : 0 Unresv. Bw : 0
TE1-> Resv. Bw : 0 Unresv. Bw : 0
TE2-> Resv. Bw : 0 Unresv. Bw : 0
TE3-> Resv. Bw : 0 Unresv. Bw : 0
TE4-> Resv. Bw : 0 Unresv. Bw : 0
TE5-> Resv. Bw : 0 Unresv. Bw : 0
TE6-> Resv. Bw : 0 Unresv. Bw : 0
TE7-> Resv. Bw : 0 Unresv. Bw : 0
No Neighbors.
===============================================================================
Label |
Description |
|---|---|
Interface |
The name of the IP interface |
Total Sessions |
The total number of RSVP sessions on this interface This count includes sessions that are active, as well as sessions that have been signaled but a response has not yet been received. |
Active Sessions |
The total number of active RSVP sessions on this interface |
Total BW |
The amount of bandwidth in megabits per second (mbps) available to be reserved for the RSVP protocol on the interface |
Resv BW |
The amount of bandwidth in mega-bits per seconds (mbps) reserved on this interface A value of zero indicates that no bandwidth is reserved. |
Adm |
Down — The RSVP interface is administratively disabled Up — The RSVP interface is administratively enabled |
Opr |
Down — The RSVP interface is operationally down Up — The RSVP interface is operationally up |
Port ID |
Specifies the physical port bound to the interface |
Active Resvs |
The total number of active RSVP sessions that have reserved bandwidth |
Subscription |
Specifies the percentage of the link bandwidth that RSVP can use for reservation When the value is zero, no new sessions are permitted on this interface. |
Port Speed |
Specifies the speed for the interface |
Unreserved BW |
Specifies the amount of unreserved bandwidth |
Reserved BW |
Specifies the amount of bandwidth in megabits per second (mbps) reserved by the RSVP session on this interface A value of zero indicates that no bandwidth is reserved. |
Total BW |
Specifies the amount of bandwidth in megabits per second (mbps) available to be reserved for the RSVP protocol on this interface |
Hello Interval |
Specifies the length of time, in seconds, between the hello packets that the router sends on the interface This value must be the same for all routers attached to a common network. When the value is zero, the sending of hello messages is disabled. |
Refresh Time |
Specifies the interval between the successive path and resv refresh messages RSVP declares the session down after it misses ((keep-multiplier + 0.5) ✕ 1.5 ✕ refresh-time)) consecutive refresh messages. |
Hello Timeouts |
The total number of hello messages that timed out on this RSVP interface |
Neighbors |
The IP address of the RSVP neighbor |
Sent |
The total number of error free RSVP packets that have been transmitted on the RSVP interface |
Recd |
The total number of error free RSVP packets received on the RSVP interface |
Total Packets |
The total number of RSVP packets, including errors, received on the RSVP interface |
Bad Packets |
The total number of RSVP packets with errors transmitted on the RSVP interface |
Paths |
The total number of RSVP PATH messages received on the RSVP interface |
Path Errors |
The total number of RSVP PATH ERROR messages transmitted on the RSVP interface |
Path Tears |
The total number of RSVP PATH TEAR messages received on the RSVP interface |
Resvs |
The total number of RSVP RESV messages received on the RSVP interface |
Resv Confirms |
The total number of RSVP RESV CONFIRM messages received on the RSVP interface |
Resv Errors |
Total RSVP RESV ERROR messages received on RSVP interface |
Resv Tears |
Total RSVP RESV TEAR messages received on RSVP interface |
Refresh Summaries |
Total RSVP RESV summary refresh messages received on interface |
Refresh Acks |
Total RSVP RESV acknowledgment messages received when refresh reduction is enabled on the RSVP interface |
Hellos |
Total RSVP RESV HELLO REQ messages received on the interface |
Bfd Enabled |
Yes — BFD is enabled on the RSVP interface No — BFD is disabled on the RSVP interface |
neighbor
Syntax
neighbor [ip-address] [detail]
Context
show>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command shows neighbor information.
Parameters
- ip-address
Displays RSVP information about the specified IP address.
- detail
Displays detailed information.
session
Syntax
session session-type [from ip-address | to ip-address| lsp-name name] [status {up | down}] [detail]
Context
show>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command shows RSVP session information.
Parameters
- session session-type
Specifies the session type.
- from ip-address
Specifies the IP address of the originating router.
- to ip-address
Specifies the IP address of the egress router.
- lsp-name name
Specifies the name of the LSP used in the path.
- status up
Displays a session that is operationally up.
- status down
Displays a session that is operationally down.
- detail
Displays detailed information.
Output
The following output is an example of RSVP session information, and Output fields: RSVP session describes the output fields.
Sample output*A:SRU4>show>router>rsvp# session
===============================================================================
RSVP Sessions
===============================================================================
From To Tunnel LSP Name State
ID ID
-------------------------------------------------------------------------------
10.20.1.5 10.20.1.4 18 27648 b4-1::b4-1 Up
10.20.1.5 10.20.1.4 1 37902 gsr::gsr Up
10.20.1.5 10.20.1.22 11 53760 to_10_20_1_22_cspf::to_10_2* Up
10.20.1.4 10.20.1.20 146 17920 to_10_20_1_20_cspf_3::to_10* Up
10.20.1.4 10.20.1.20 145 34816 to_10_20_1_20_cspf_2::to_10* Up
10.20.1.4 10.20.1.20 147 45056 to_10_20_1_20_cspf_4::to_10* Up
10.20.1.4 10.20.1.20 148 6656 to_10_20_1_20_cspf_5::to_10* Up
10.20.1.4 10.20.1.20 149 58880 to_10_20_1_20_cspf_6::to_10* Up
10.20.1.4 10.20.1.20 150 13312 to_10_20_1_20_cspf_7::to_10* Up
10.20.1.4 10.20.1.20 152 40448 to_10_20_1_20_cspf_9::to_10* Up
10.20.1.4 10.20.1.20 154 27648 to_10_20_1_20_cspf_11::to_1* Up
10.20.1.4 10.20.1.20 155 12288 to_10_20_1_20_cspf_12::to_1* Up
10.20.1.4 10.20.1.20 151 46080 to_10_20_1_20_cspf_8::to_10* Up
10.20.1.4 10.20.1.20 153 512 to_10_20_1_20_cspf_10::to_1* Up
10.20.1.4 10.20.1.22 164 62464 to_10_20_1_22_cspf_2::to_10* Up
10.20.1.4 10.20.1.20 156 37888 to_10_20_1_20_cspf_13::to_1* Up
10.20.1.4 10.20.1.20 157 24064 to_10_20_1_20_cspf_14::to_1* Up
10.20.1.4 10.20.1.20 158 19968 to_10_20_1_20_cspf_15::to_1* Up
10.20.1.4 10.20.1.20 161 59904 to_10_20_1_20_cspf_18::to_1* Up
...
10.20.1.3 10.20.1.4 54 23088 to_110_20_1_4_cspf_4::to_11* Up
-------------------------------------------------------------------------------
Sessions : 1976
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:SRU4>show>router>rsvp#
A:ALA-12# show router rsvp session lsp-name A_C_2::A_C_2 status up
===============================================================================
RSVP Sessions
===============================================================================
From To Tunnel LSP Name State
ID ID
-------------------------------------------------------------------------------
10.20.1.1 10.20.1.3 2 40 A_C_2::A_C_2 Up
-------------------------------------------------------------------------------
Sessions : 1
===============================================================================
A:ALA-12#
Label |
Description |
|---|---|
From |
The IP address of the originating router |
To |
The IP address of the egress router |
Tunnel ID |
The IP address of the tunnel’s ingress node supporting this RSVP session |
LSP ID |
The ID assigned by the agent to this RSVP session |
Name |
The administrative name assigned to the RSVP session by the agent |
State |
Down — the operational state of this RSVP session is down Up — the operational state of this RSVP session is up |
statistics
Syntax
statistics
Context
show>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays global statistics in the RSVP instance.
Output
The following output is an example of RSVP statistics information, and Output fields: RSVP statistics describes the output fields.
Sample output*A:SRU4>show>router>rsvp# statistics
===============================================================================
RSVP Global Statistics
===============================================================================
PATH Timeouts : 1026 RESV Timeouts : 182
===============================================================================
*A:SRU4>show>router>rsvp#
Label |
Description |
|---|---|
PATH Timeouts |
The total number of path timeouts |
RESV Timeouts |
The total number of RESV timeouts |
status
Syntax
rsvp status
Context
show>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays RSVP status.
Output
The following output is an example of RSVP status information, and Output fields: RSVP status describes the output fields.
Sample output*A:SRU4>show>router>rsvp# status
===============================================================================
RSVP Status
===============================================================================
Admin Status : Up Oper Status : Up
Keep Multiplier : 3 Refresh Time : 30 sec
Message Pacing : Disabled Pacing Period : 100 msec
Max Packet Burst : 650 msgs Refresh Bypass : Disabled
===============================================================================
*A:SRU4>show>router>rsvp#
Label |
Description |
|---|---|
Admin Status |
Down — RSVP is administratively disabled Up — RSVP is administratively enabled |
Oper Status |
Down — RSVP is operationally down Up — RSVP is operationally up |
Keep Multiplier |
Displays the keep-multiplier number used by RSVP to declare that a reservation is down or the neighbor is down |
Refresh Time |
Displays the refresh-time interval, in seconds, between the successive Path and Resv refresh messages |
Message Pacing |
Enabled — RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the period command Disabled — Message pacing is disabled. RSVP message transmission is not regulated |
Pacing Period |
Displays the time interval, in milliseconds, when the router can send the specified number of RSVP messages specified in the rsvp max-burst command |
Max Packet Burst |
Displays the maximum number of RSVP messages that are sent in the specified period under normal operating conditions |
Tools commands
cspf
Syntax
cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap bitmap] [exclude-bitmap bitmap] [hop-limit limit] [exclude-address excl-addr [excl-addr...(up to 8 max)]] [use-te-metric] [strict-srlg] [srlg-group grp-id...(up to 8 max)] [skip-interface interface-name]
Context
tools>perform>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command computes a CSPF path with specified user constraints.
Parameters
- to ip-addr
Specifies the destination IP address.
- from ip-addr
Specifies the originating IP address.
- bandwidth bandwidth
Specifies the amount of bandwidth in mega-bits per second (Mbps) to be reserved.
- include-bitmap bitmap
Specifies to include a bit-map that specifies a list of admin groups that should be included during setup.
- exclude-bitmap bitmap
Specifies to exclude a bit-map that specifies a list of admin groups that should be included during setup.
- hop-limit limit
Specifies the total number of hops a detour LSP can take before merging back onto the main LSP path.
- exclude-address ip-addr
Specifies IP addresses, up to 8, that should be included during setup.
- use-te-metric
Specifies the use of the traffic engineering metric used on the interface.
- strict-srlg
Specifies whether to associate the LSP with a bypass or signal a detour if a bypass or detour satisfies all other constraints except the SRLG constraints.
- srlg-group grp-id
Specifies up to 8 Shared Risk Link Groups (SRLGs). An SRLG group represents a set of interfaces which could be subject to the same failures or defects and therefore, share the same risk of failing.
- skip-interface interface-name
Specifies an interface name that should be skipped during setup.
Output
The following output is an example of MPLS CSPF information.
Sample output*A:Dut-C# tools perform router mpls cspf to 10.20.1.6
Req CSPF for all ECMP paths
from: this node to: 10.20.1.6 w(no Diffserv) class: 0 , setup Priority 7, Hold
Priority 0 TE Class: 7
CSPF Path
To : 10.20.1.6
Path 1 : (cost 2000)
Src: 10.20.1.3 (= Rtr)
Egr: unnumbered lnkId 4 -
> Ingr: unnumbered lnkId 2 Rtr: 10.20.1.5 (met 1000)
Egr: unnumbered lnkId 3 -
> Ingr: unnumbered lnkId 3 Rtr: 10.20.1.6 (met 1000)
Dst: 10.20.1.6 (= Rtr)
Path 2 : (cost 2000)
Src: 10.20.1.3 (= Rtr)
Egr: unnumbered lnkId 5 -
> Ingr: unnumbered lnkId 5 Rtr: 10.20.1.4 (met 1000)
Egr: unnumbered lnkId 3 -
> Ingr: unnumbered lnkId 2 Rtr: 10.20.1.6 (met 1000)
Dst: 10.20.1.6 (= Rtr)
*A:Dut-C#
resignal
Syntax
resignal {lsp lsp-name path path-name | delay minutes}
Context
tools>perform>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command resignals a specific LSP path. The minutes parameter configures the global timer of all LSPs for resignal. If only lsp-name and path-name are provided, the LSP is resignaled immediately.
Parameters
- lsp-name
Specifies an existing LSP name to resignal.
- path-name
Specifies an existing path name to resignal.
- delay minutes
Sets the global timer of all LSPs to resignal.
switch-path
Syntax
switch-path [lsp lsp-name] [path path-name]
Context
tools>perform>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command moves a standby (or an active secondary) path to another standby path of the same priority. If a new standby path with a higher priority or a primary path comes up after the tools perform command is executed, the path re-evaluation command runs and the path is moved to the path specified by the outcome of the re-evaluation.
Parameters
- lsp-name
Specifies the name of an existing LSP to move.
- path-name
Specifies the path name to which to move the specified LSP.
Clear commands
interface
Syntax
interface ip-int-name
Context
clear>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command resets or clears statistics for MPLS interfaces.
Parameters
- ip-int-name
Specifies the name of an existing IP interface. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
lsp
Syntax
lsp lsp-name
Context
clear>router>mpls
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command resets and restarts an LSP.
Parameters
- lsp-name
Specifies the name of the LSP to clear, up to 64 characters.
statistics
Syntax
statistics
Context
clear>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command clears global statistics for the RSVP instance; for example, the command clears path and resv timeout counters.
Debug commands
mpls
Syntax
mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id]
no mpls
Context
debug>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables and configures debugging for MPLS.
Parameters
- lsp-name
Specifies the name that identifies the LSP, which can be up to 32 characters and must be unique.
- source-address
Specifies the system IP address of the sender.
- endpoint-address
Specifies the far-end system IP address.
- tunnel-id
Specifies the MPLS SDP ID.
- lsp-id
Specifies the LSP ID.
- ip-int-name
Specifies th name that identifies the interface. The interface name can be up to 32 characters and must be unique. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
event
Syntax
[no] event
Context
debug>router>mpls
debug>router>rsvp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables debugging for specific events.
The no form of this command disables the debugging.
all
Syntax
all [detail]
no all
Context
debug>router>mpls>event
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs all events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about all events.
auth
Syntax
auth
no auth
Context
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs authentication events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about authentication events.
frr
Syntax
frr [detail]
no frr
Context
debug>router>mpls>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs fast reroute events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about reroute events.
iom
Syntax
iom [detail]
no iom
Context
debug>router>mpls>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs MPLS IOM events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about MPLS IOM events.
lsp-setup
Syntax
lsp-setup [detail]
no lsp-setup
Context
debug>router>mpls>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs LSP setup events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about LSP setup events.
mbb
Syntax
mbb [detail]
no mbb
Context
debug>router>mpls>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs the state of the most recent invocation of the make-before-break (MBB) functionality.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about MBB events.
misc
Syntax
misc [detail]
no misc
Context
debug>router>mpls>event
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs miscellaneous events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about miscellaneous events.
xc
Syntax
xc [detail]
no xc
Context
debug>router>mpls>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs cross connect events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about cross connect events.
rsvp
Syntax
[lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id] [interface ip-int-name]
no rsvp
Context
debug>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables and configures debugging for RSVP.
Parameters
- lsp-name
Specifies the name that identifies the LSP, which can be up to 32 characters and must be unique.
- source-address
Specifies the system IP address of the sender.
- endpoint-address
Specifies the far-end system IP address.
- tunnel-id
Specifies the RSVP tunnel ID.
- lsp-id
Specifies the LSP ID.
- ip-int-name
Specifies the interface name. The interface name can be up to 32 characters and must be unique. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
nbr
Syntax
nbr [detail]
no nbr
Context
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs neighbor events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about neighbor events.
path
Syntax
path [detail]
no path
Context
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs path-related events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about path-related events.
resv
Syntax
resv [detail]
no resv
Context
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs RSVP reservation events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about RSVP reservation events.
rr
Syntax
rr
no rr
Context
debug>router>rsvp>event
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs refresh reduction events.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about refresh reduction events.
packet
Syntax
[no] packet
Context
debug>router>rsvp>
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs packets.
The no form of this command disables the debugging.
ack
Syntax
ack [detail]
no ack
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs ACK packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about RSVP ACK packets.
bundle
Syntax
bundle [detail]
no bundle
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs bundle packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about RSVP bundle packets.
all
Syntax
all [detail]
no all
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs all packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about all RSVP packets.
hello
Syntax
hello [detail]
no hello
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs hello packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about hello packets.
path
Syntax
path [detail]
no path
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables debugging for RSVP path packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about path-related events.
patherr
Syntax
patherr [detail]
no patherr
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs path error packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about path error packets.
pathtear
Syntax
pathtear [detail]
no pathtear
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs path tear packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about path tear packets.
resv
Syntax
resv [detail]
no resv
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables debugging for RSVP RESV packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about RSVP RESV events.
resverr
Syntax
resverr [detail]
no resverr
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs ResvErr packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about ResvErr packets.
resvtear
Syntax
resvtear [detail]
no resvtear
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs ResvTear packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about ResvTear packets.
srefresh
Syntax
srefresh [detail]
no srefresh
Context
debug>router>rsvp>packet
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command debugs srefresh packets.
The no form of this command disables the debugging.
Parameters
- detail
Displays detailed information about RSVP srefresh packets.