Configuring MPLS and RSVP-TE with CLI
This section provides information to configure MPLS and RSVP-TE using the CLI.
Topics in this section include:
MPLS Configuration Overview
MPLS enables routers to forward traffic based on a label embedded in the packet header. A router examines the label to determine the next hop for the packet, instead of router address lookups to the next node when forwarding packets.
To implement MPLS on an LSP for outer tunnel and pseudowire assignment, the following entities must be configured:
- Signaling Protocol (for RSVP-TE or LDP)
Router Interface
At least one router interface and one system interface must be defined in the config>router>interface context in order to configure MPLS on an interface.
E-LSP for Differentiated Services
An EXP-inferred LSP (E-LSP) is an LSP that can support a variety of VLLs or traffic types. Up to eight types of traffic can be multiplexed over an E-LSP.
The prioritization of mission-critical traffic is handled by the settings of the three EXP bits. The EXP bits designate the importance of a particular packet. The classification and queuing at the Provider (P) or Provider Edge (PE) nodes typically take place based on the value of the EXP bits. Refer to the 7705 SAR OS Quality of Service Guide for more information on the use of EXP bits and differentiated services on the 7705 SAR.
Paths
To configure signaled LSPs, you must first create one or more named paths on the ingress router using the config>router>mpls>path command. For each path, the transit routers (hops) in the path are specified.
LSPs
The 7705 SAR supports static and dynamic LSPs.
To configure MPLS-signaled (dynamic) LSPs, the LSP must run from an ingress LER to an egress LER. Configure the dynamic LSP only at the ingress router, and either configure the LSP to allow the router software to make the forwarding decisions or configure some or all routers in the LSP path statically. The LSP is set up by RSVP-TE signaling messages. The 7705 SAR OS automatically manages label values. Labels that are automatically assigned have values ranging from 1,024 through 1 048 575 (see Label Values).
A static LSP is a manually configured LSP where the next hop IP address and the outgoing label are explicitly specified.
To establish a static LSP, an LSP must be configured from an ingress LER to an egress LER. Labels must be manually assigned and the label values must be within the range of 32 to 1023 (see Label Values).
Pseudowires
To configure PW/VLL labels, the PW/VLL service must be configured. PW/VLL labels can be configured manually as statically allocated labels using any unused label within the static label range. Pseudowire/VLL labels can also be dynamically assigned by targeted LDP. Statically allocated labels and dynamically allocated labels are designated differently in the label information base.
PW/VLL labels are uniquely identified against a 7705 SAR, not against an interface or module.
As defined in RFC 3036, LDP Specification, and RFC 4447 Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP), label distribution is handled in the Downstream Unsolicited (DU) mode. Generic Label TLV is used for all setup and maintenance operations.
Signaling Protocol
For static LSPs, the path and the label mappings and actions configured at each hop must be specified manually. RSVP-TE or LDP is not required for static LSPs.
For dynamic LSPs, RSVP-TE or LDP must be turned on. See RSVP and RSVP-TE or Label Distribution Protocol.
To implement dynamic pseudowire/VLL labels, entities must be enabled as follows:
- MPLS must be enabled on all routers that are part of a static LSP
- LDP must be enabled on the ingress and egress LERs
When MPLS is enabled and either RSVP-TE or LDP is also enabled, MPLS uses RSVP-TE or LDP to set up the configured LSPs. For example, when you configure an LSP with both MPLS and RSVP-TE running, RSVP-TE initiates a session to create the LSP. RSVP-TE uses the local router as the RSVP-TE session sender and the LSP destination as the RSVP-TE session receiver. Once the RSVP-TE session is created, the LSP is set up on the path created by the session. If the session is not successfully created, RSVP-TE 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 gives configuration examples of common configuration tasks. To enable MPLS on a 7705 SAR router, you must configure at least one MPLS interface. The MPLS interface is configured in the config>router>mpls context. The other MPLS configuration parameters are optional.
The following example displays an MPLS configuration output.
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-TE (for RSVP-TE-signaled MPLS only)
- LDP
In order for MPLS to run, you must configure at least one MPLS interface in the config>router>mpls context.
- 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 the path 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 settings under the LSP hierarchy are optional.
Configuring MPLS Components
Use the MPLS and RSVP-TE CLI syntax shown in the following information for:
Configuring Global MPLS Parameters
Admin groups can signify link colors, such as red, yellow, or green, or some other link quality. Shared risk link groups (SRLGs) are lists of interfaces that share the same risk of failure due to shared resources. MPLS interfaces advertise the admin groups and SRLGs that they support. CSPF uses the information when paths are computed for constraint-based LSPs. CSPF must be enabled in order for admin groups and SRLGs to be relevant.
To configure global MPLS parameters, enter the following commands:
The following example displays a global MPLS configuration output.
Configuring an MPLS Interface
The interface must exist in the system before it can be configured as an MPLS interface; refer to the 7705 SAR OS Router Configuration Guide for more information.
Once the MPLS protocol instance is created, the no shutdown command is not required since MPLS is administratively enabled upon creation. Configure the label-map parameters if the interface is used in a static LSP.
Use the following CLI syntax to configure an MPLS interface on a router:
The following example displays the interface configuration output.
Configuring MPLS Paths
Configure an MPLS path for use by LSPs. When configuring an MPLS path, the IP address of each hop 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 other routers (loose).
Use the following CLI syntax to configure a path:
The following example displays a path configuration output.
Configuring an MPLS LSP
Configure an LSP 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.
The following displays an MPLS LSP configuration.
Configuring a Static LSP
An LSP can be explicitly (manually) configured. The reserved range of static LSP labels is 32 to 1023. Static LSPs are configured on every node along the LSP path. The label’s forwarding information includes the address of the next hop router.
Use the following CLI syntax to configure a static LSP:
The following example displays the static LSP configuration output.
Configuring a Fast-Retry Timer for Static LSPs
A fast-retry timer can be configured for static LSPs. When a static LSP is trying to come up, MPLS tries to resolve the ARP entry for the next hop of the LSP. This request may fail because the next hop might still be down or unavailable. In that case, MPLS starts a retry timer before making the next request. The fast-retry command allows the user to configure the retry timer so that the LSP comes up shortly after the next hop is available.
Use the following CLI syntax to configure a fast-retry timer for static LSPs:
Configuring Manual Bypass Tunnels
Consider the following network setup in Figure 10. Assume that a manual bypass tunnel must be configured on Node B.
Figure 10: Manual Bypass Tunnels
- Disable dynamic bypass tunnels on Node B.The CLI syntax for this configuration is:config>router>mpls>dynamic-bypass [disable | enable]By default, dynamic bypass tunnels are enabled.
- Configure an LSP on Node B, such as B-E-F-C, which will be used only as a bypass. Specify each hop in the path and assign its strict or loose option; in this case, the bypass LSP will have a strict path. Designate the LSP as a primary LSP.The CLI syntax for this configuration is:config>router>mpls>path path-name>hop hop-index ip-address [strict | loose]config>router>mpls>lsp lsp-name bypass-only(see also the configuration example below)Including the bypass-only keyword disables some options under the LSP configuration. See Table 6.
Table 6: Disabled and Enabled Options for Bypass-Only
Disabled Options
Enabled Options
- bandwidth
- fast-reroute
- secondary
- adaptive
- adspec
- cspf
- exclude
- hop-limit
- include
- metric
- Configure an LSP from A to D and indicate fast-reroute bypass protection by selecting facility as the FRR method.The CLI syntax for this configuration is:config>router>mpls>lsp lsp-name>fast-reroute facilityIf the LSP from A to D goes through Node B and bypass is requested, the next hop is Node C, and there is a manually configured bypass-only tunnel from B to C that excludes link BC (that is, path BEFC), then Node B uses the bypass-only tunnel.
The following example displays a bypass tunnel configuration output.
Configuring RSVP-TE Parameters
RSVP-TE is used to set up LSPs. RSVP-TE 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 config>router>rsvp context.
Initially, interfaces are configured in the config>router>mpls>interface context. Only these existing (MPLS) interfaces are available to be modified in the config>router>rsvp context. Interfaces cannot be directly added in the rsvp context.
The following example displays an RSVP-TE configuration output.
Configuring RSVP-TE Message Pacing Parameters
RSVP-TE message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full.
Use the following CLI syntax to configure RSVP-TE message pacing parameters:
The following example displays an RSVP-TE message pacing configuration output.
MPLS Configuration Management Tasks
This section discusses the following MPLS configuration management tasks:
Deleting MPLS
The no form of the mpls command typically removes an MPLS instance and all associated information. However, MPLS must be disabled (shut down) and all SDP bindings to LSPs removed before an MPLS instance can be deleted. Once MPLS is shut down, the no mpls command deletes the protocol instance and removes all configuration parameters for the MPLS instance.
If MPLS is not shut down first, when the no mpls command is executed, a warning message on the console indicates that MPLS is still administratively up.
To delete the MPLS instance:
- Disable the MPLS instance using the shutdown command.
- Remove the MPLS instance from the router using the no mpls command.
Modifying MPLS Parameters
 | Note:
You must shut down MPLS entities in order 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.
The following example displays an MPLS LSP configuration output. Refer to Configuring an MPLS Interface.
Modifying MPLS Path Parameters
In order to modify path parameters, the config>router>mpls>path context must be shut down first.
The following example displays an MPLS path configuration output. Refer to Configuring MPLS Paths.
Modifying MPLS Static LSP Parameters
Use the show>service>router>static-lsp command to display a list of LSPs.
In order to modify static LSP parameters, the config>router>mpls>static-lsp lsp-name context must be shut down.
To modify an LSP:
- Access the specific LSP by specifying the LSP name, and then shut it down.
- Enter the parameter to modify and then enter the new information.
The following example displays the static LSP configuration output.
Deleting an MPLS Interface
To delete an interface from the MPLS configuration:
- Administratively disable the interface using the shutdown command.
- Delete the interface with the no interface command.
The following example displays the configuration output when interface “to-104” has been deleted.
RSVP-TE Configuration Management Tasks
This section discusses the following RSVP-TE configuration management tasks:
Modifying RSVP-TE Parameters
Only interfaces configured in the MPLS context can be modified in the rsvp context.
The no rsvp command deletes this RSVP-TE protocol instance and removes all configuration parameters for this RSVP-TE instance. The shutdown command suspends the execution and maintains the existing configuration.
The following example displays a modified RSVP-TE configuration output.
Modifying RSVP-TE Message Pacing Parameters
RSVP-TE message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full.
The following example displays a modified RSVP-TE message pacing configuration output. Refer to Configuring RSVP-TE Message Pacing Parameters.
Deleting an Interface from RSVP-TE
Interfaces cannot be deleted directly from the RSVP-TE configuration. Because an interface is created in the mpls context and then configured in the rsvp context, it can only be deleted in the mpls context This removes the association from RSVP-TE.
Refer to Deleting an MPLS Interface.