Table Of Contents
MPLS Scalability Enhancements for the ATM LSR
Supported Standards, MIBs, and RFCs
Configuring the MPLS ATM Network
Disabling the Creation of LSPs
Efficiently Using LVC space for Cisco 12000 Series Routers
Routing Protocol Configuration
tag-switching request-tags for
MPLS Scalability Enhancements for the ATM LSR
This document describes how to prevent label-switched paths (LSPs) from being created in an MPLS network. This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Some LSPs are often unnecessary between some label-switched edge routers (LERs) in an MPLS network. Every time a new destination is created, LSPs are created from all LERs in the MPLS network to the new destination. You can use the tag-switching request-tags for command with an access list at an LER to restrict the destinations for which a downstream-on-demand request is issued. You specify the destination IP addresses that you want to enable/disable from creating LSPs.
Benefits
This command allows you to permit/deny creation of some LSPs, while preventing the creation of others. Using this command reduces the number of LSPs in an MPLS network, which reduces the VC usage in the network.
Restrictions
This section details some of the restrictions of this feature.
•
Do not use the tag-switching disable headend-vc command.
When using access lists to prevent the creation of LSPs, do not disable the router from acting as an edge router with the tag-switching disable headend-vc command, which prevents all LSPs from being established.
•
Cisco 12000 routers need special LVC configuration for efficient use of VCs.
A Cisco 12000 router (GSR) ATM interface used for MPLS cannot use the entire virtual path identifier (VPI) range configured on the subinterface. Attempts to create label switched controlled virtual circuits (LVCs) within the configured range may be rejected by the line card drivers. This can occur when you use the GSR ATM OC-3 or OC-12 interfaces running MPLS.
The following paragraphs show the commands for efficiently using LVC space. For a configuration example, see "Efficiently Using LVC space for Cisco 12000 Series Routers".
–
For the Quad OC-3 or Quad OC-12
On the main interface, use 512 VCs per VPI. Enter the following command:
atm vc-per-vp 512On the MPLS subinterface, match the hardware limit of 7 VPIs and set the control-vc to within that range by entering the following commands:
mpls atm control-vc 2 32mpls atm vpi 2-8–
For the Single-Port OC-12
On the main interface, use 1024 VCs per VPI . Enter the following command:
atm vc-per-vp 1024On the MPLS subinterface, match the hardware limit of 15 VPIs and set the control-vc to fall within that range by entering the following commands:
mpls atm control-vc 2 32mpls atm vpi 2-16You must configure the control-vc of the TDP neighbor so that it uses the same VPI and VCI.
Related Documents
For more information about standard and extended access lists, see the following documents:
•
Cisco IOS IP and IP Routing Configuration Guide, Release 12.1, Configuring IP Services
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/ipcprt1/1cdip.htm
•
Cisco IOS Security Configuration Guide, Release 12.1, Access Control Lists: Overview and Guidelines
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/secur_c/scprt3/scdacls.htm
For more information about MPLS and LSCs, see the following document:
•
MPLS Label Switch Controller and Enhancements
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/mpls_lsc.htm
For more information about configuring PVCs on the LER, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/6400/con_r2/index.htm
Supported Platforms
This feature is supported on the following platforms:
•
Cisco 7200 series
•
Cisco 7500 series
•
Cisco 12000 series (engine 0)
Supported Standards, MIBs, and RFCs
•
Standards—The MPLS LSC supports no new or modified standards.
•
MIBs—The MPLS LSC supports no new or modified MIBs.
•
RFCs—The MPLS LSC supports no new or modified RFCs.
Configuration Tasks
The following sections explain how to configure the network to prevent the creation of LSPs from specified IP addresses:
•
Configuring the MPLS ATM Network
Sample MPLS ATM Network
Figure 1 is an MPLS ATM network that consists of the following elements:
•
The PE routers in the virtual private network require LSPs to communicate with each other.
•
All the PE routers are in network 1 (198.x.x.x).
•
All the IGP IP addresses are in network 2 (192.x.x.x).
•
If numbered interfaces are required (for network management or other purposes), they are placed in network 2 (192.x.x.x).
Figure 1 Sample MPLS ATM Network
The following configuration tasks use tag-switching request-tags for commands to accomplish the following:
•
Allow the PE routers in network 1 to create LSPs and communicate with each other, but prevent creation of LSPs from the PE routers to the MPLS ATM network,
•
Prevent LSPs from being created in the MPLS ATM network (network 2) and prevent from the MPLS ATM network to the PE routers.
Performing these tasks reduces the number of LSPs in the MPLS ATM network, which reduces the VC usage in the network.
Configuring the MPLS ATM Network
In the configuration file of the routers in the MPLS ATM network, enter the following commands:
Configuring the PE Routers
In the configuration file of the PE routers, enter the following commands:
Verifying the Configuration
Use the following commands to verify the configuration:
Configuration Examples
This section contains the following configuration examples:
•
Disabling the Creation of LSPs
•
Efficiently Using LVC space for Cisco 12000 Series Routers
Disabling the Creation of LSPs
The following examples of the tag-switching request tags-for command use Figure 2 as a basis. The examples show different ways to disable the creation of LSPs from the LSC to the edge GSR, and from the edge GSRs to the LSC.
Note
In this example, the LSCs are running 12.1(5)T software. Cisco IOS Release 12.0(14ST) does not support LSCs.
Figure 2 Sample Configuration
Using a Numbered Access List
The following examples use a numbered access list to restrict creation of LSPs.
Note
With LSCs, you disable the LSC from acting as an edge router with the tag-switching disable headend-vc command, which prevents all LSPs from being established. The following examples use the tag-switching request-tags for command on the LSC. However, it is recommended that you use the tag-switching disable headend-vc command.
Preventing LSPs from the LSC to the Edge LSRs
The following example prevents LSPs from being established from the LSC to all 198.x.x.x destinations. However, transit LSPs are allowed between 198.x.x.x destinations. Add the following commands to the LSC configuration:
tag-switching request-tags for 1access-list 1 deny 198.0.0.0 0.255.255.255access-list 1 permit anyPreventing LSPs from the Edge LSRs to the LSC
The following example prevents headend LVCs from being established from edge LSR 1 and edge GSR 2 to the LSC (192.x.x.x). However, transit LSPs are allowed between 198.x.x.x destinations. Add the following commands to the edge GSR 1 and 2 configurations:
tag-switching request-tags for 1access-list 1 deny 192.0.0.0 0.255.255.255access-list 1 permit anyUsing a Named Access List
The following examples use a named access list to perform the same tasks as the previous examples.
tag-switching request-tags for nolervcsip access-list standard nolervcsdeny 198.0.0.0 0.255.255.255permit anytag-switching request-tags for nolervcsip access-list standard nolervcsdeny 192.0.0.0 0.255.255.255permit anySpecifying Exact Match IP Addresses with an Access List
The following examples use exact IP addresses to perform the same tasks as the previous examples.
tag-switching request-tags for 1access-list 1 deny 198.5.0.1 0.0.0.0access-list 1 deny 198.5.0.2 0.0.0.0access-list 1 permit anytag-switching request-tags for 1access-list 1 deny 192.6.53.1 0.0.0.0access-list 1 permit anyEfficiently Using LVC space for Cisco 12000 Series Routers
The following configuration shows how to set up the ATM interfaces so that LVC space is optimized on a Cisco 12000 series router.
Figure 1 Cisco 12000 Series Router Configuration Example
LSC1 Configuration
ip routingip ceftag-switching ip!int loopback0ip address 12.12.12.12.255.255.255.255!int atm1/0tag-control-protocol vsi slaves 18!interface XTagATM101ip unnumbered Loopback0extended-port ATM2/0 vsi 0x000A0100tag-switching atm control-vc 2 32tag-switching atm vpi 2-8tag-switching ip!interface XTagATM103ip unnumbered Loopback0extended-port ATM2/0 vsi 0x000A0300tag-switching atm control-vc 2 32tag-switching atm vpi 2-8tag-switching ipBPX1 Configuration
Port 9.1
uptrk 9.1cnfrscr 9.1 256 248207 N y 1 e 512 5000 2 15 26000 100000addshelf 9.1 VPort 10.1
uptrk 10.1cnfrscr 10.1 256 248207 N y 1 e 512 5000 2 15 26000 100000Port 10.3
uptrk 10.3cnfrscr 10.3 256 248207 N y 1 e 512 5000 2 15 26000 100000Routing Protocol Configuration
router ospf 100network 12.0.0.0.0.255.255.255.255 area 100GSR1 Configuration
ip routingip ceftag-switching ip!int loopback0ip address 10.10.10.10.255.255.255.255int atm5/0atm vc-per-vp 512!interface ATM5/0.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastno atm enable-ilmi-traptag-switching atm control-vc 2 32tag-switching atm vpi 2-8tag-switching ip!router ospf 100network 10.0.0.0.0.255.255.255.255 area 100GSR2 Configuration
ip routingip ceftag-switching ip!int loopback0ip address 11.11.11.11.255.255.255.255!int atm5/0atm vc-per-vp 512interface ATM5/0.1 tag-switchingip unnumbered Loopback0no ip directed-broadcastno atm enable-ilmi-traptag-switching atm control-vc 2 32tag-switching atm vpi 2-8tag-switching ip!router ospf 100router (config-router)# network 11.0.0.0.0.255.255.255.255 area 100Command Reference
This section describes the CLI commands that you can use to disable the creation of LSPs:
•
tag-switching request-tags for
All other commands used with this feature are documented in the Cisco IOS command reference publications.
Command Conventions
mpls ldp request-tags for
To restrict the creation of LVCs through the use of access lists on the label edge router, use the mpls ldp request-tags for global configuration command. Use the no form of this command to disable this feature.
mpls ldp request-tags for access list
no mpls ldp request-tags for access list
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The command includes the following usage guidelines:
•
You can specify either an access list number or name.
•
When creating an access list, the end of the access list contains an implicit deny statement for everything if it did not find a match before reaching the end.
•
If you omit the mask from an IP host address access list specification, 0.0.0.0 is assumed to be the mask.
Examples
In the following example, headend LVCs are prevented from being established from the core router to all 198.x.x.x destinations. The following commands are added to the core router configuration:
tag-switching request-tags for 1access-list 1 deny 198.0.0.0 0.255.255.255access-list 1 permit anyRelated Commands
tag-switching request-tags for
To restrict the creation of LVCs through the use of access lists on the label edge router, use the tag-switching request-tags for global configuration command. Use the no form of this command to disable this feature.
tag-switching request-tags for access list
no tag-switching request-tags for access list
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The command includes the following usage guidelines:
•
You can specify either an access list number or name.
•
When creating an access list, the end of the access list contains an implicit deny statement for everything if it did not find a match before reaching the end.
•
If you omit the mask from an IP host address access list specification, 0.0.0.0 is assumed to be the mask.
Examples
In the following example, headend LVCs are prevented from being established from the core router to all 198.x.x.x destinations. The following commands are added to the core router configuration:
tag-switching request-tags for 1access-list 1 deny 198.0.0.0 0.255.255.255access-list 1 permit anyRelated Commands




