Table Of Contents
Configuring Multiprotocol Label Switching
Configuring MPLS Levels of Control
Case 1—Enable MPLS Incrementally in a Network
Case 2—Route Labeled Packets to Network A Only
Case 3—Limit Label Distribution on an MPLS Network
Configuring a Router for MPLS Forwarding
Configuring MPLS Traffic Engineering
Configuring a Device to Support Tunnels
Configuring an Interface to Support RSVP-Based Tunnel Signalling and IGP Flooding
Configuring IS-IS for MPLS Traffic Engineering
Configuring OSPF for MPLS Traffic Engineering
Configuring an MPLS Traffic Engineering Tunnel
Configuring MPLS Traffic Engineering Paths
Configuring MPLS Virtual Private Networks
Configuring BGP Routing Sessions
Configuring PE to PE Routing Sessions
Configuring BGP PE to CE Routing Sessions
Configuring RIP PE to CE Routing Sessions
Configuring Static Route PE to CE Routing Sessions
Configuring MPLS VPNs with Cable Interfaces
Defining Subinterfaces on a Physical Cable Interface and Assigning VRFs
Configuring Cable Interface Bundles
Configuring Subinterfaces and MPLS VPNs on a Bundle Master
Configuring MPLS in the P Routers in the Provider Core
Verifying the MPLS VPN Configuration
Configuring Interautonomous Systems for MPLS VPNs
Configuring EBGP Routing for the Exchange of VPN Routes Between Autonomous Systems
Displaying VPN-IPv4 LFIB Entries
Configuring MPLS QoS Backbone Support
Setting the MPLS Experimental Field Value
Importance of Prioritizing a Packet Appropriately
Configuring the Ingress MPLS Router
Using the Modular QoS CLI to Configure the Ingress Label Switching Router
Configuring a Class Map to Classify IP Packets
Configuring a Policy Map to Set the MPLS Experimental Field
Configuring the Input Interface to Attach the Service Policy
Using CAR to Configure the Ingress Label Switching Router
Configuring a Rate Limit Access List for Classifying IP Packets
Configuring a Rate-Limit on an Input Interface to Set MPLS Packets
Configuring the Output IP QoS of the Packet
Configuring PVC Mode in a Non-MPLS-Enabled Core
Configuring Multi-VC Mode in a MPLS-Enabled Core
Configuring Multi-VCs Using the Cos-Map Function
Configuring DWFQ and Changing Queue Weights on an Outgoing Interface
Configuring the MPLS Label Switch Controller
Configuring MPLS on the Cisco 7200 Series LSCs for BPX and IGX Switches
Configuring the Cisco 6400 UAC LSC
Configuring Cisco 6400 UAC NRP as an MPLS LSC
Configuring the Cisco 6400 UAC NSP for MPLS Connectivity to BPX
Verifying MPLS LSC Configuration
Configuring MPLS Egress NetFlow Accounting
Enabling MPLS Egress NetFlow Accounting
Configuring NetFlow Aggregation Cache
Troubleshooting MPLS Egress NetFlow Accounting
Verifying MPLS Egress NetFlow Accounting Configuration
Monitoring and Maintaining MPLS Egress NetFlow Accounting
Verifying Configuration of MPLS Forwarding
Enabling MPLS Incrementally in a Network Example
Enabling MPLS for a Subset of Destination Prefixes Example
Selecting the Destination Prefixes and Paths Example
Displaying MPLS LDP Binding Information Example
Displaying MPLS Forwarding Table Information Example
Displaying MPLS Interface Information Example
Displaying MPLS LDP Neighbor Information Example
Enabling LSP Tunnel Signalling Example
Configuring an LSP Tunnel Example
Displaying the LSP Tunnel Information Example
Configuring MPLS Traffic Engineering Examples
Configuring MPLS Traffic Engineering Using IS-IS Example
Configuring MPLS Traffic Engineering Using OSPF Example
Configuring an MPLS Traffic Engineering Tunnel Example
Configuring Enhanced SPF Routing over a Tunnel Example
Configuring MPLS VPNs Examples
Defining a Cable Subinterface Example
Cable Interface Bundling Example
Subinterface Definition on Bundle Master Example
Cable Interface Bundle Master Configuration Example
Configuring EBGP Routing to Exchange VPN Routes Between Autonomous Systems
Configuring EBGP Routing to Exchange VPN Routes Between Autonomous Systems in a Confederation
Running IP on Router 2 Example
Running IP on Router 1 Example
Running MPLS on Router 4 Example
Running MPLS on Router 3 Example
Running MPLS on Router 5 Example
Running MPLS on Router 6 Example
Configuring ATM Switch 2 Example
Configuring ATM Switch 1 Example
Configuring an MPLS LSC Examples
Configuring ATM-LSRs with a Cisco 6400 NRP Operating as LSC Example
Configuring ATM LSRs Through ATM Network Using Cisco 7200 LSCs Implementing Virtual Trunking Example
Configuring LSC Hot Redundancy Example
Configuring LSC Warm Standby Redundancy Example
Configuring an Interface Using Two VSI Partitions Example
Using an Access List to Control the Creation of Headend VCs
MPLS Egress NetFlow Accounting Example
Configuring Multiprotocol Label Switching
This chapter describes how to configure your network to perform Multiprotocol Label Switching (MPLS).
This chapter contains the following sections:
•
Configuring MPLS Levels of Control
•
•
•
•
•
•
•
•
For configuration examples on MPLS, see the "MPLS Configuration Examples" section.
For a complete description of the commands in this chapter, refer to the the Cisco IOS Switching Services Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the section "Identifying Supported Platforms" in the chapter "Using Cisco IOS Software."
Configuring MPLS Levels of Control
This section describes three sample cases where MPLS is configured on Cisco 7500 and 7200 series routers. These cases show the levels of control possible in selecting how MPLS is deployed in a network.
Table 28 lists the cases, including the steps to perform MPLS and their corresponding Cisco IOS CLI commands.
For more information about the Cisco IOS CLI commands, see the chapter "MPLS Commands" in the Cisco IOS Switching Services Command Reference.
Figure 51 shows a router-only MPLS network with Ethernet interfaces. The following sections outline the procedures for configuring MPLS and displaying MPLS information in a network based on the topology shown in Figure 51.
Note
Figure 51 A Router-Only MPLS Network with Ethernet Interfaces
Case 1—Enable MPLS Incrementally in a Network
In the first case, assume that you want to deploy MPLS incrementally throughout a network of routers, but that you do not want to restrict which destination prefixes are label switched. For a description of the commands listed in these cases, see the chapter "MPLS Commands" in the Cisco IOS Switching Services Command Reference.
To enable MPLS incrementally in a network, use the following commands beginning in router configuration mode (see Figure 51):
After you perform these steps, R1 applies labels to packets that are forwarded through Ethernet interface e0/1, with a next hop to R3.
You can enable MPLS throughout the rest of the network by repeating steps 1 and 2 as appropriate on other routers until all routers and interfaces are enabled for MPLS. See the example in the "Enabling MPLS Incrementally in a Network Example" section.
Case 2—Route Labeled Packets to Network A Only
In the second case, assume that you want to enable MPLS for a subset of destination prefixes. This option might be used to test MPLS across a large network. In this case, you would configure the system so that only a small number of destinations is label switched (for example, internal test networks) without the majority of traffic being affected.
To enable MPLS for a subset of destination prefixes, use the following commands at each router in the network in router configuration mode (see Figure 51):
Case 3—Limit Label Distribution on an MPLS Network
The third case demonstrates the full control available to you in determining the destination prefixes and paths for which MPLS is enabled.
Configure the routers so that packets addressed to network A are labeled, all other packets are unlabeled, and only links R1-R3, R3-R4, R4-R6, and R6-R7 carry labeled packets addressed to network A. For example, suppose the normally routed path for packets arriving at R1 addressed to network A or network B is R1, R3, R5, R6, R7. A packet addressed to network A would flow labeled on links R1-R3 and R6-R7, and unlabeled on links R3-R5 and R5-R6. A packet addressed to network B would follow the same path, but would be unlabeled on all links.
Assume that at the outset the routers are configured so that packets addressed to network A are labeled and all other packets are unlabeled (as at the completion of Case 2).
Use the tag-switching advertise-tags command and access lists to limit label distribution. Specifically, you need to configure routers R2, R5, and R8 to distribute no labels to other routers. This ensures that no other routers send labeled packets to any of those three. You also need to configure routers R1, R3, R4, R6, and R7 to distribute labels only for network A and to distribute them only to the appropriate adjacent router; that is, R3 distributes its label for network A only to R1, R4 only to R3, and so on.
To limit label distribution on a MPLS network, use the following commands in router configuration mode:
Configuring a Router for MPLS Forwarding
MPLS forwarding on routers requires that CEF be enabled. To enable CEF on a router, enter the following commands:
Router# configure terminalRouter(config)# ip cef [distributed]
Note
For more information on the CEF commands, refer to the Cisco IOS Switching Services Command Reference.
Configuring MPLS Traffic Engineering
Perform the following tasks before you enable MPLS traffic engineering:
•
•
•
To configure MPLS traffic engineering, perform the tasks described in the following sections:
•
•
•
•
•
Configuring a Device to Support Tunnels
To configure a device to support tunnels, use the following commands in global configuration mode:
Configuring an Interface to Support RSVP-Based Tunnel Signalling and IGP Flooding
To configure an interface to support RSVP-based tunnel signalling and IGP flooding, use the following commands in interface configuration mode:
Note
Configuring IS-IS for MPLS Traffic Engineering
To configure IS-IS for MPLS traffic engineering, perform the steps described below. For a description of the IS-IS commands (excluding the IS-IS traffic engineering commands), see the Cisco IOS IP and IP Routing Command Reference.
Configuring OSPF for MPLS Traffic Engineering
To configure OSPF for MPLS traffic engineering, use the following commands beginning in global configuration mode. For a description of the OSPF commands (excluding the OSPF traffic engineering commands), see the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols.
Configuring an MPLS Traffic Engineering Tunnel
To configure an MPLS traffic engineering tunnel, use the following commands in interface configuration mode. This tunnel has two path setup options: a preferred explicit path and a backup dynamic path.
Configuring MPLS Traffic Engineering Paths
To configure an MPLS traffic engineering tunnel that an IGP can use, use the following commands in interface configuration mode:
Configuring MPLS Virtual Private Networks
To configure and verify VPNs, perform the tasks described in the following sections:
•
•
•
•
•
•
•
Defining VPNs
To define VPN routing instances, use the following commands beginning in router configuration mode on the PE router:
Configuring BGP Routing Sessions
To configure BGP routing sessions in a provider network, use the following commands beginning in router configuration mode on the PE router:
Configuring PE to PE Routing Sessions
To configure PE to PE routing sessions in a provider network, use the following commands beginning in router configuration mode on the PE router:
Configuring BGP PE to CE Routing Sessions
To configure BGP PE to CE routing sessions, use the following commands beginning in router configuration mode on the PE router:
Configuring RIP PE to CE Routing Sessions
To configure RIP PE to CE routing sessions, use the following commands beginning in router configuration mode on the PE router:
Configuring Static Route PE to CE Routing Sessions
To configure static route PE to CE routing sessions, use the following commands in router configuration mode on the PE router:
Configuring MPLS VPNs with Cable Interfaces
Before configuring IP-based VPNs on Cisco uBR7200 series, perform the following tasks:
•
•
•
To configure MPLS VPNs with cable interfaces, perform the tasks described in the following sections. The first two sections are required tasks; the remaining tasks are optional:
•
•
•
•
•
•
Restrictions
The following restrictions apply to configuring MPLS VPNs with cable interfaces:
•
Note
•
•
•
–
–
–
–
–
•
•
Creating VRFs for Each VPN
To create VRFs for each VPN, use the following commands beginning in router configuration mode:
Note
Defining Subinterfaces on a Physical Cable Interface and Assigning VRFs
To create a logical cable subinterface, use the following commands beginning in global configuration mode. Create one subinterface for each VPN (one per ISP). The first subinterface created must be configured as part of the management VPN (with the lowest subinterface number). Create VRFs using the procedure described in the "Creating VRFs for Each VPN" section and apply them to the subinterface.
Configuring Cable Interface Bundles
To assign a cable interface to a bundle, use the following commands beginning in global configuration mode:
Configuring Subinterfaces and MPLS VPNs on a Bundle Master
To configure subinterfaces on a bundle master and assign each subinterface a Layer 3 configuration, configure cable interface bundles using the procedure described in the "Configuring Cable Interface Bundles" section.
Define subinterfaces on the bundle master interface and assign a Layer 3 configuration to each subinterface using the procedure described in the "Defining Subinterfaces on a Physical Cable Interface and Assigning VRFs" section. Create one subinterface for each customer VPN (one per ISP).
Configuring MPLS in the P Routers in the Provider Core
To configure MPLS in the P routers in the provider core, use the following commands beginning in router configuration mode:
Verifying the MPLS VPN Configuration
To verify MPLS VPN operations on PE routers, use the following EXEC commands:
Configuring Interautonomous Systems for MPLS VPNs
Before you configure EBGP routing between autonomous systems or subautonomous systems in an MPLS VPN, ensure that you have properly configured all MPLS VPN routing instances and sessions. The configuration tasks outlined in this section build from those configuration tasks.
Perform the following tasks before you enable configure EBGP routing between autonomous systems or subautonomous systems in an MPLS VPN:
•
•
•
•
To configure the exchange of VPN-IPv4 addresses between two or more autonomous systems or subautonomous systems in a confederation, perform the tasks described in the following sections. The tasks in the following sections are described as required or optional:
•
•
•
Configuring EBGP Routing for the Exchange of VPN Routes Between Autonomous Systems
To configure an EBGP border edge router in an autonomous system to exchange VPN routes with another autonomous system, use the following commands beginning in global configuration mode:
Note
Configuring EBGP Routing for the Exchange of VPN Routes Between Subautonomous Systems in a Confederation
In this confederation, subautonomous system IGP domains must know the addresses of CEBGP-1 and CEBGP-2. If you do not specify a next-hop-self address as part of the router configuration, ensure that the addresses of all PE routers in the subautonomous system are distributed throughout the network, not just the addresses of CEBGP-1 and CEBGP-2.
Note
To configure EBGP border edge router in a confederation to exchange VPN routes with another subautonomous system, use the following commands beginning in global configuration mode:
Displaying VPN-IPv4 LFIB Entries
To display the VPN-IPv4 Label Forwarding Information Base (LFIB) entries at the border edge routers in the autonomous systems, use the following EXEC commands:
The following is an example of how the VPN-IPv4 LFIB entries appear when you use the show tag-switching forwarding-table privileged EXEC command:
Router# show tag-switching forwarding-table
Local Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface33 33 10.120.4.0/24 0 Hs0/0 point2point35 27 100:12:10.200.0.1/32 \0 Hs0/0 point2point
Note
Verifying VPN Operation
To verify VPN operation by displaying routing information on the PE routers, use the following show commands, as needed:
Configuring MPLS QoS Backbone Support
Several different methods exist for supporting QoS across an MPLS backbone, the choice depending on whether the core has label switch routers (LSRs) or ATM-LSRs. In each case, however, the QoS building blocks are the same: CAR, WRED, and WFQ.
Three configurations are described in this section:
•
•
•
LSRs
LSRs at the core of the MPLS backbone are usually either Cisco 7200 and Cisco 7500 series routers running MPLS software. Packets are processed as follows:
1.
2.
3.
4.
5.
6.
ATM-LSRs
ATM-LSRs at the core implement the multiple label virtual circuit model (LVC). In the multiple LVC model, one label is assigned for each service class for each destination. The operation of the edge LSR is the same as that described previously for the LSR case, except that the output is an ATM interface. WRED is used to define service classes and determine discard policy during congestion.
In the multiple LVC model, however, class-based WFQ (CBWFQ) is used to define the amount of bandwidth available to each service class. Packets are scheduled by class during congestion. The ATM-LSRs participate in the differentiation of classes with WFQ and intelligently drop packets when congestion occurs. The mechanism for this discard activity is weighted early packet discard (WEPD).
ATM Switches
When the core network uses ATM switches and the edge of the network uses MPLS-enabled edge LSRs, the edge LSRs are interconnected through a mesh of ATM Forum PVCs (CBR, VBR, or UBR) over the ATM core switches. The edge LSRs invoke WFQ on a per-VC basis to provide differentiation based on the delay of each MPLS QoS multiplexed onto the ATM Forum PVC. Optionally, WRED can also be used on a per-VC basis to manage drop priority between classes when congestion occurs on the edge LSR.
Table 29 lists the MPLS QoS features supported on packet interfaces.
Table 30 lists the MPLS QoS features supported on ATM interfaces.
Table 30 MPLS QoS Features Supported on ATM Interfaces
Per-VC WRED
X1
X1
—
—
—
Per-VC WRED and
per VC, per-class WFQ—
X1
—
—
—
Per-interface WRED
X2
X2
—
—
—
Per-interface, per-class WFQ
X2
X2
—
—
—
1 This feature is only available on the PA-A3.
2 This feature is only available on the PA-A1.
Table 31 lists the MPLS QoS features supported on ATM switches.
Table 31 MPLS QoS Features Supported on ATM Switches
MPLS QoS ATM Forum PVCs
X
X
X
X
MPLS QoS Multi-VC or LBR—per-class WFQ
X
—
—
—
1 This switch can be used for the core only.
Configuring MPLS QoS
Perform the following tasks before you enable MPLS traffic engineering:
•
•
To configure MPLS QoS, perform the tasks described in the following sections. The first five sections are described as required; the remaining tasks are optional:
•
•
•
•
•
•
•
•
•
•
Configuring QoS
To configure QoS, you can configure one or more of the following features (in addition, of course, to other items not described in this document):
•
•
•
Setting the MPLS Experimental Field Value
Setting the MPLS experimental field value satisfies the requirement of service providers that do not want the value of the IP Precedence field modified within IP packets transported through their networks.
By choosing different values for the MPLS experimental field, you can mark packets based on their characteristics, such as rate or type, so that packets have the priority that they require during periods of congestion.
Figure 52 shows a MPLS network of a service provider that connects two sites of a network belonging to a customer.
Figure 52 MPLS Network Connecting Two Sites of a Customer's IP Network
To use these features in a network, set the MPLS experimental field value at PE1 (the ingress label switching router) by using the modular QoS CLI or the rate-limit interface command that CAR provides to set the QoS value in the MPLS packet. For detailed instructions, see the "Setting the MPLS Experimental Field Value" section.
Importance of Prioritizing a Packet Appropriately
During Step 1 of the configuration process (described in the "Using the Modular QoS CLI to Configure the Ingress Label Switching Router" and "Using CAR to Configure the Ingress Label Switching Router" sections) you classify IP packets according to their source address, destination address, port, protocol identification, or quality of service field. For example, packets can be identified based on one or more of the specified fields, as Voice over IP (VoIP) or a File Transfer Protocol (FTP). Packet classification/marking is important because a priority of a packet is determined by how it is classified or marked.
A priority of a packet affects how the packet is treated during periods of congestion. For example, service providers have service level agreements (SLAs) with customers. The agreement specifies how much traffic the service provider has agreed to deliver. To comply with the agreement, the customer must not send more than the agreed-upon rate. Packets are considered to be in-rate or out-of-rate. If there is congestion in the network, out-of-rate packets might be dropped more aggressively.
Configuring the Ingress MPLS Router
To classify IP packets, you configure the ingress label switching router. Packets are received at the ingress router as IP packets and sent as MPLS packets. To perform the configuration, use either of the following features:
•
•
–
–
Using the Modular QoS CLI to Configure the Ingress Label Switching Router
To use the modular QoS CLI to configure PE1 (the ingress label switching router), perform the following steps:
Step 1
Step 2
Step 3
Configuring a Class Map to Classify IP Packets
To configure a class map, use the following commands beginning in global configuration mode:
In the following example, all packets that contain IP Precedence 4 are matched by the class-map name IP_prec4:
Router(config)# class-map IP_prec4 Router(config-c-map)# match ip precedence 4 Router(config-c-map)# endConfiguring a Policy Map to Set the MPLS Experimental Field
To configure a policy map, use the following commands beginning in global configuration mode:
In the following example, the value in the MPLS experimental field of each packet that is matched by the class-map IP_prec4 is set to 5:
Router(config)# policy-map set_experimental_5 Router(config-p-map)# class IP_prec4 Router(config-p-map-c)# set mpls experimental 5 Router(config-p-map-c)# endConfiguring the Input Interface to Attach the Service Policy
To configure the input interface, use the following commands beginning in global configuration mode:
In the following example, the service policy set_experimental_5 is attached to an Ethernet input interface:
Router(config)# interface ethernet 1/0/0 Router(config-int)# service-policy input set_experimental_5 Router(config-int)# endUsing CAR to Configure the Ingress Label Switching Router
To use CAR to configure the ingress label switching router, perform the following steps:
Step 1
Step 2
These steps are explained in the following sections.
Configuring a Rate Limit Access List for Classifying IP Packets
To configure a rate limit access list, use the following commands beginning in global configuration mode:
Step 1
Specifies the criteria to be matched.
Step 2
Exits configuration mode.
In the following example, all packets that contain IP Precedence 4 are matched by the rate-limit access list 24:
Router(config)# access-list rate-limit 24 4 Router(config)# endConfiguring a Rate-Limit on an Input Interface to Set MPLS Packets
To configure a rate-limit on an input interface, use the following commands beginning in global configuration mode:
In the following example, the experimental field for the output MPLS packet is set to 4 if the input IP packets match the access list and conform to the rate. The MPLS experimental field is set to 0 if packets match access list 24 and exceed the input rate.
Router(config)# interface ethernet 1/0/0 Router(config-int)# rate-limit input access-group rate-limit 24 8000 8000 8000 conform-action set-mpls-exp-transmit 4 exceed-action set-mpls-exp-transmit 0Configuring the Output IP QoS of the Packet
The output QoS of the packet is determined by the IP header information. For configuration details, refer to the Cisco IOS Quality of Service Solutions Configuration Guide.
Configuring PVC Mode in a Non-MPLS-Enabled Core
To configure a PVC in a non-MPLS-enabled core, use the following commands beginning in router configuration mode:
Configuring Multi-VC Mode in a MPLS-Enabled Core
To configure multi-VC mode in an MPLS-enabled core, use the following commands beginning in router configuration mode:
Note
Configuring Multi-VCs Using the Cos-Map Function
If you do not choose to use the default for configuring label VCs, you can configure fewer label VCs by using the QoS map function. To use the QoS map function, use the following commands beginning in router configuration mode:
Configuring DWFQ and Changing Queue Weights on an Outgoing Interface
To configure distributed WFQ (dWFQ) and change queue weights on an interface, use the following commands in interface configuration mode after specifying the interface:
Verifying QoS Operation
To verify the operation of MPLS QoS, use the following EXEC commands:
Configuring the MPLS Label Switch Controller
To enable MPLS LSC functionality, perform the tasks described in the following sections. The first two sections are required tasks; the remaining task is optional:
•
•
•
Refer to the Cisco BPX 8600 or IGX 8400 series documentation for BPX or IGX service node configuration examples.
Configuring MPLS on the Cisco 7200 Series LSCs for BPX and IGX Switches
To configure MPLS on the Cisco 7200 Series LSCs for BPX and IGX switches, use the following commands on each LSC in the configuration beginning in router configuration mode.
Note
Configuring the Cisco 6400 UAC LSC
To configure a Cisco 6400 UAC LSC, perform the tasks in the following sections. The first section contains a required task; the remaining task is optional:
•
•
Configuring Cisco 6400 UAC NRP as an MPLS LSC
To configure a Cisco 6400 UAC NRP as an MPLS LSC, use the following commands beginning in global configuration mode:
Configuring the Cisco 6400 UAC NSP for MPLS Connectivity to BPX
To configure a Cisco 6400 UAC NSP for MPLS connectivity to BPX, use the following commands beginning in global configuration mode:
Verifying MPLS LSC Configuration
To verify your MPLS LSC configuration, use the following commands in EXEC mode:
Configuring MPLS Egress NetFlow Accounting
To configure MPLS egress NetFlow, perform the tasks described in the following sections. The first section contains a required task; the remaining tasks are optional:
•
•
•
•
•
Enabling MPLS Egress NetFlow Accounting
To enable MPLS egress NetFlow accounting, use the following command in interface configuration mode:
Router(config-if)# mpls netflow egress
Enables MPLS egress NetFlow accounting on the egress router interface.
Configuring NetFlow Aggregation Cache
To configure NetFlow aggregation cache, use the following global configuration command:
Troubleshooting MPLS Egress NetFlow Accounting
To troubleshoot the MPLS egress NetFlow accounting feature, use the following commands in EXEC mode, as needed:
Verifying MPLS Egress NetFlow Accounting Configuration
To verify MPLS egress NetFlow accounting configuration, perform the following steps:
Step 1
Note
Router# show ip cache flowIP packet size distribution (10 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 1.00 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 4456704 bytes1 active, 65535 inactive, 2 added26 ager polls, 0 flow alloc failureslast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 1 0.0 5 100 0.0 0.0 15.7Total : 1 0.0 5 100 0.0 0.0 15.7SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsEt1/1 34.0.0.2 Et1/4 180.1.1.2 01 0000 0800 5Table 32 describes the fields in the flow switching cache lines of the output.
Table 33 describes the fields in the activity-by-protocol lines of the output.
Table 34 describes the fields in the current flow lines of the output.
Step 2
Router# show ip cache flow aggRouter# show ip cache flow aggregation prefRouter# show ip cache flow aggregation prefixIP Flow Switching Cache, 278544 bytes1 active, 4095 inactive, 1 added4 ager polls, 0 flow alloc failuresSrc If Src Prefix Msk Dst If Dst Prefix Msk Flows PktsEt1/1 34.0.0.0 /8 Et1/4 180.1.1.0 /24 1 5Router#Table 35 describes the fields in the flow switching cache lines of the output.
Table 36 describes the fields in the current flow lines of the output.
The ip flow-aggregation cache command has other options, including the following:
{as | destination-prefix | prefix | protocol-port | source-prefix}
Note
Here is sample configuration output from the NetFlow aggregation cache:
Router(config)# ip flow-aggRouter(config)# ip flow-aggregation cacheRouter(config)# ip flow-aggregation cache ?as AS aggregationdestination-prefix Destination Prefix aggregationprefix Prefix aggregationprotocol-port Protocol and port aggregationsource-prefix Source Prefix aggregationRouter(config)# ip flow-aggregation cache prefixRouter(config-flow-cache)# enableHere is sample output displaying the IP aggregation cache contents:
Router# show ip cache flow aggregation ?as AS aggregation cachedestination-prefix Destination Prefix aggregation cacheprefix Source/Destination Prefix aggregation cacheprotocol-port Protocol and port aggregation cachesource-prefix Source Prefix aggregation cacheRouter# show ip cache flowIP packet size distribution (206 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .854 .000 .145 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 4292920 bytes0 active, 62977 inactive, 182 added2912 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondslast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 182 0.0 1 62 0.0 0.0 15.5Total : 182 0.0 1 62 0.0 0.0 15.5SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsRouter# show ip cache flow aggregation prefixIP Flow Switching Cache, 278544 bytes1 active, 4095 inactive, 3 added45 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondsSrc If Src Prefix Msk Dst If Dst Prefix Msk Flows PktsEt1/1 34.0.0.0 /8 PO6/0 12.12.12.12 /32 1 5Router#Monitoring and Maintaining MPLS Egress NetFlow Accounting
To monitor and maintain MPLS egress NetFlow accounting, use the following command in EXEC mode:
Verifying Configuration of MPLS Forwarding
To verify that CEF has been configured properly, enter the show ip cef summary command, which generates output similar to the following:
Router# show ip cef summaryIP CEF with switching (Table Version 49), flags=0x043 routes, 0 resolve, 0 unresolved (0 old, 0 new)43 leaves, 49 nodes, 56756 bytes, 45 inserts, 2 invalidations2 load sharing elements, 672 bytes, 2 references1 CEF resets, 4 revisions of existing leaves4 in-place modificationsrefcounts: 7241 leaf, 7218 nodeAdjacency Table has 18 adjacenciesRouter#MPLS Configuration Examples
This section provides the following MPLS configuration examples:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Enabling MPLS Incrementally in a Network Example
The following example shows how to configure MPLS incrementally throughout a network of routers. You enable MPLS first between one pair of routers (in this case, R1 and R3 shown in Figure 51) and add routers step by step until every router in the network is label switch enabled.
router-1# configuration terminal router-1(config)# ip cef distributed router-1(config)# tag-switching ip router-1(config)# interface e0/1 router-1(config-if)# tag-switching ip router-1(config-if)# exit router-1(config)#router-3# configuration terminal router-3(config)# ip cef distributed router-3(config)# tag-switching ip router-3(config)# interface e0/1 router-3(config-if)# tag-switching ip router-3(config-if)# exit router-3(config)#Enabling MPLS for a Subset of Destination Prefixes Example
The following example shows the commands you enter at each of the routers to enable MPLS for only a subset of destination prefixes (see Figure 51).
Router(config)# access-list-1 permit A Router(config)# tag-switching advertise-tags for 1Selecting the Destination Prefixes and Paths Example
The following example shows the commands you enter to configure the routers to select the destination prefixes and paths for which MPLS is enabled. When you configure R2, R5, and R8 to distribute no labels to other routers, you ensure that no routers send them labeled packets. You also need to configure routers R1, R3, R4, R6, and R7 to distribute labels only for network A and only to the applicable adjacent router. This configuration ensures that R3 distributes its label for network A only to R1, R4 only to R3, R6 only to R4, and R7 only to R6 (see Figure 51).
router-2(config)# no tag-switching advertise-tagsrouter-5(config)# no tag-switching advertise-tagsrouter-8(config)# no tag-switching advertise-tagsrouter-1(config)# access-list permit R1router-1(config)# no tag-switching advertise-tags for 1router-1(config)# tag-switching advertise-tags for 1 to 2router-1(config)# exitrouter-3# access-list 1 permit Arouter-3# access-list 2 permit R1router-3# tag-switching advertise-tags for 1 to 2router-3# exitrouter-4# access-list 1 permit Arouter-4# access-list 2 permit R3router-4# tag-switching advertise-tags for 1 to 2router-4# exitrouter-6# access-list 1 permit Arouter-6# access-list 2 permit R4router-6# tag-switching advertise-tags for 1 to 2router-6# exitrouter-7# access-list 1 permit Arouter-7# access-list 2 permit R6router-7# tag-switching advertise-tags for 1 to 2router-7# exitDisplaying MPLS LDP Binding Information Example
The following example shows how to use the show tag-switching tdp bindings EXEC command to display the contents of the Label Information Base (LIB). The display can show the entire database or can be limited to a subset of entries, based on prefix, input or output label values or ranges, or the neighbor advertising the label.
Note
Router# show tag-switching tdp bindingsMatching entries:tib entry: 10.92.0.0/16, rev 28local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.102.0.0/16, rev 29local binding: tag: 26remote binding: tsr: 172.27.32.29:0, tag: 26tib entry: 10.105.0.0/16, rev 30local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.205.0.0/16, rev 31local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.211.0.7/32, rev 32local binding: tag: 27remote binding: tsr: 172.27.32.29:0, tag: 28tib entry: 10.220.0.7/32, rev 33local binding: tag: 28remote binding: tsr: 172.27.32.29:0, tag: 29tib entry: 99.101.0.0/16, rev 35local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 100.101.0.0/16, rev 36local binding: tag: 29remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 171.69.204.0/24, rev 37local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 172.27.32.0/22, rev 38local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 210.10.0.0/16, rev 39local binding: tag: imp-null(1)tib entry: 210.10.0.8/32, rev 40remote binding: tsr: 172.27.32.29:0, tag: 27Displaying MPLS Forwarding Table Information Example
The following example shows how to use the show tag-switching forwarding-table command to display the contents of the LFIB. The LFIB lists the labels, output interface information, prefix or tunnel associated with the entry, and number of bytes received with each incoming label. A request can show the entire LFIB or can be limited to a subset of entries. A request can also be restricted to selected entries in any of the following ways:
•
•
•
•
•
Router# show tag-switching forwarding-tableLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface26 Untagged 10.253.0.0/16 0 Et4/0/0 172.27.32.428 1/33 10.15.0.0/16 0 AT0/0.1 point2point29 Pop tag 10.91.0.0/16 0 Hs5/0 point2point1/36 10.91.0.0/16 0 AT0/0.1 point2point30 32 10.250.0.97/32 0 Et4/0/2 10.92.0.732 10.250.0.97/32 0 Hs5/0 point2point34 26 10.77.0.0/24 0 Et4/0/2 10.92.0.726 10.77.0.0/24 0 Hs5/0 point2point35 Untagged [T] 10.100.100.101/32 0 Tu301 point2point36 Pop tag 168.1.0.0/16 0 Hs5/0 point2point1/37 168.1.0.0/16 0 AT0/0.1 point2point[T] Forwarding through a TSP tunnel.View additional tagging info with the 'detail' optionDisplaying MPLS Interface Information Example
The following example shows how to use the show tag-switching interfaces command to show information about the requested interface or about all interfaces on which MPLS is enabled. The per-interface information includes the interface name and indications as to whether IP MPLS is enabled and operational.
Router# show tag-switching interfacesInterface IP Tunnel OperationalHssi3/0 Yes Yes NoATM4/0.1 Yes Yes Yes (ATM tagging)Ethernet5/0/0 No Yes YesEthernet5/0/1 Yes No YesEthernet5/0/2 Yes No NoEthernet5/0/3 Yes No YesEthernet5/1/1 Yes No NoThe following shows sample output from the show tag-switching interfaces command when you specify the detail keyword:
Router# show tag-switching interfaces detailInterface Hssi3/0:IP tagging enabledTSP Tunnel tagging enabledTagging not operationalMTU = 4470Interface ATM4/0.1:IP tagging enabledTSP Tunnel tagging enabledTagging operationalMTU = 4470ATM tagging: Tag VPI = 1, Control VC = 0/32Interface Ethernet5/0/0:IP tagging not enabledTSP Tunnel tagging enabledTagging operationalMTU = 1500Interface Ethernet5/0/1:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Interface Ethernet5/0/2:IP tagging enabledTSP Tunnel tagging not enabledTagging not operationalMTU = 1500Interface Ethernet5/0/3:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Displaying MPLS LDP Neighbor Information Example
The following example shows how to use the show tag-switching tdp neighbors EXEC command to display the status of LDP sessions. The neighbor information branch can have information about all LDP neighbors or can be limited to the neighbor with a specific IP address or LDP identifier, or to LDP neighbors known to be accessible over a specific interface.
Router# show tag-switching tdp neighborsPeer TDP Ident: 10.220.0.7:1; Local TDP Ident 172.27.32.29:1TCP connection: 10.220.0.7.711 - 172.27.32.29.11029State: Oper; PIEs sent/rcvd: 17477/17487; Downstream on demandUp time: 01:03:00TDP discovery sources:ATM0/0.1Peer TDP Ident: 210.10.0.8:0; Local TDP Ident 172.27.32.29:0TCP connection: 210.10.0.8.11004 - 172.27.32.29.711State: Oper; PIEs sent/rcvd: 14656/14675; Downstream;Up time: 2d5hTDP discovery sources:Ethernet4/0/1Ethernet4/0/2POS6/0/0Addresses bound to peer TDP Ident:99.101.0.8 172.27.32.28 10.105.0.8 10.92.0.810.205.0.8 210.10.0.8Enabling LSP Tunnel Signalling Example
The following example shows how to configure support for LSP tunnel signalling along a path and on each interface crossed by one or more tunnels:
Router(config)# ip cef distributedRouter(config)# tag-switching tsp-tunnelsRouter(config)# interface e0/1Router(config-if)# tag-switching tsp-tunnelsRouter(config-if)# interface e0/2Router(config-if)# tag-switching tsp-tunnelsRouter(config-if)# exitConfiguring an LSP Tunnel Example
The following example shows how to set the encapsulation of the tunnel to MPLS and how to define hops in the path for the LSP.
Follow these steps to configure a two-hop tunnel, hop 0 being the headend router. For hops 1 and 2, you specify the IP addresses of the incoming interfaces for the tunnel. The tunnel interface number is arbitrary, but must be less than 65,535.
Router(config)# interface tunnel 2003Router(config-if)# tunnel mode tag-switchingRouter(config-if)# tunnel tsp-hop 1 10.10.0.12Router(config-if)# tunnel tsp-hop 2 10.50.0.24 lasthopRouter(config-if)# exitTo shorten the previous path, delete the hop by entering the following commands:
Router(config)# interface tunnel 2003Router(config-if)# no tunnel tsp-hop 2Router(config-if)# tunnel tsp-hop 1 10.10.0.12 lasthopRouter(config-if)# exitDisplaying the LSP Tunnel Information Example
The following example shows how to use the show tag-switching tsp-tunnels command to display information about the configuration and status of selected tunnels:
Router# show tag-switching tsp-tunnelsSignalling Summary:TSP Tunnels Process: runningRSVP Process: runningForwarding: enabledTUNNEL ID DESTINATION STATUS CONNECTION 10.106.0.6.2003 10.2.0.12 up upConfiguring MPLS Traffic Engineering Examples
This section provides the following MPLS traffic engineering configuration examples:
•
•
•
•
Figure 53 illustrates a sample MPLS topology. This example specifies point-to-point outgoing interfaces. The next sections contain sample configuration commands you enter to implement MPLS traffic engineering and the basic tunnel configuration shown in Figure 53.
Figure 53 Sample MPLS Traffic Engineering Tunnel Configuration
Configuring MPLS Traffic Engineering Using IS-IS Example
This example lists the commands you enter to configure MPLS traffic engineering with IS-IS routing enabled (see Figure 53).
Note
Router 1—MPLS Traffic Engineering Configuration
To configure MPLS traffic engineering, enter the following commands:
ip cefmpls traffic-eng tunnelsinterface loopback 0ip address 11.11.11.11 255.255.255.255ip router isisinterface s1/0ip address 131.0.0.1 255.255.0.0ip router isismpls traffic-eng tunnelsip rsvp bandwidth 1000Router 1—IS-IS Configuration
To enable IS-IS routing, enter the following commands:
router isisnetwork 47.0000.0011.0011.00is-type level-1metric-style widempls traffic-eng router-id loopback0mpls traffic-eng level-1Configuring MPLS Traffic Engineering Using OSPF Example
This example lists the commands you enter to configure MPLS traffic engineering with OSPF routing enabled (see Figure 53).
Note
Router 1—MPLS Traffic Engineering Configuration
To configure MPLS traffic engineering, enter the following commands:
ip cefmpls traffic-eng tunnelsinterface loopback 0ip address 11.11.11.11 255.255.255.255interface s1/0ip address 131.0.0.1 255.255.0.0mpls traffic-eng tunnelsip rsvp bandwidth 1000Router 1—OSPF Configuration
To enable OSPF, enter the following commands:
router ospf 0network 131.0.0.0.0.0.255.255 area 0mpls traffic-eng router-id Loopback0mpls traffic-eng area 0Configuring an MPLS Traffic Engineering Tunnel Example
This example shows you how to configure a dynamic path tunnel and an explicit path in the tunnel. Before you configure MPLS traffic engineering tunnels, you must enter the appropriate global and interface commands on the specified router (in this case, Router 1).
Router 1—Dynamic Path Tunnel Configuration
In this section, a tunnel is configured to use a dynamic path:
interface tunnel1ip unnumbered loopback 0tunnel destination 17.17.17.17tunnel mode mpls traffic-engtunnel mpls traffic-eng bandwidth 100tunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng path-option 1 dynamicRouter 1—Dynamic Path Tunnel Verification
This section includes the commands you use to verify that the tunnel is up:
show mpls traffic-eng tunnelsshow ip interface tunnel1Router 1—Explicit Path Configuration
In this section, an explicit path is configured:
ip explicit-path identifier 1next-address 131.0.0.1next-address 135.0.0.1next-address 136.0.0.1next-address 133.0.0.1Router 1—Explicit Path Tunnel Configuration
In this section, a tunnel is configured to use an explicit path:
interface tunnel2ip unnumbered loopback 0tunnel destination 17.17.17.17tunnel mode mpls traffic-engtunnel mpls traffic-eng bandwidth 100tunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng path-option 1 explicit identifier 1Router 1—Explicit Path Tunnel Verification
This section includes the commands you use to verify that the tunnel is up:
show mpls traffic-eng tunnelsshow ip interface tunnel2Configuring Enhanced SPF Routing over a Tunnel Example
This section includes the commands that cause the tunnel to be considered by the enhanced SPF calculation of the IGP, which installs routes over the tunnel for appropriate network prefixes.
Router 1—IGP Enhanced SPF Consideration Configuration
In this section, you specify that the IGP should use the tunnel (if the tunnel is up) in its enhanced SPF calculation:
interface tunnel1tunnel mpls traffic-eng autoroute announceRouter 1—Route and Traffic Verification
This section includes the commands you use to verify that the tunnel is up and that the traffic is routed through the tunnel:
show traffic-eng tunnels tunnel1 briefshow ip route 17.17.17.17show mpls traffic-eng autorouteping 17.17.17.17show interface tunnel1 accountingshow interface s1/0 accountingConfiguring MPLS VPNs Examples
This section provides the following configuration examples:
•
•
•
•
•
•
•
Configuring MPLS VPNs Example
The following example provides a sample configuration file from a PE router:
ip cef distributed ! CEF switching is pre-requisite for label Switchingframe-relay switching!ip vrf vrf1 ! Define VPN Routing instance vrf1rd 100:1route-target both 100:1 ! Configure import and export route-targets for vrf1!ip vrf vrf2 ! Define VPN Routing instance vrf2rd 100:2route-target both 100:2 ! Configure import and export route-targets for vrf2route-target import 100:1 ! Configure an additional import route-target for vrf2import map vrf2_import ! Configure import route-map for vrf2!interface lo0ip address 10.13.0.13 255.255.255.255!interface atm9/0/0 ! Backbone link to another Provider router!interface atm9/0/0.1 tag-switchingip unnumbered loopback0 no ip directed-broadcast tag-switching atm vpi 2-5tag-switching ipinterface atm5/0 no ip address no ip directed-broadcast atm clock INTERNAL no atm ilmi-keepaliveinterface Ethernet1/0 ip address 3.3.3.5 255.255.0.0 no ip directed-broadcastno ip mroute-cacheno keepaliveinterface Ethernet5/0/1 ! Set up Ethernet interface as VRF link to a CE routerip vrf forwarding vrf1ip address 10.20.0.13 255.255.255.0!interface hssi 10/1/0hssi internal-clockencaps frframe-relay intf-type dceframe-relay lmi-type ansi!interface hssi 10/1/0.16 point-to-pointip vrf forwarding vrf2ip address 10.20.1.13 255.255.255.0frame-relay interface-dlci 16 ! Set up Frame Relay PVC subinterface as link to another! ! CE routerrouter bgp 1 ! Configure BGP sessionsno synchronizationno bgp default ipv4-activate ! Deactivate default IPv4 advertisementsneighbor 10.15.0.15 remote-as 1 ! Define IBGP session with another PEneighbor 10.15.0.15 update-source lo0!address-family vpnv4 unicast ! Activate PE exchange of VPNv4 NLRIneighbor 10.15.0.15 activateexit-address-family!address-family ipv4 unicast vrf vrf1 ! Define BGP PE-CE session for vrf1redistribute static redistribute connectedneighbor 10.20.0.60 remote-as 65535neighbor 10.20.0.60 activateno auto-summaryexit-address-family!address-family ipv4 unicast vrf vrf2 ! Define BGP PE-CE session for vrf2redistribute static redistribute connectedneighbor 10.20.1.11 remote-as 65535neighbor 10.20.1.11 update-source h10/1/0.16neighbor 10.20.1.11 activateno auto-summaryexit-address-family!! Define a VRF static routeip route vrf vrf1 12.0.0.0 255.0.0.0 e5/0/1 10.20.0.60!route-map vrf2_import permit 10 ! Define import route-map for vrf2....Defining a Cable Subinterface Example
The following example shows how to define a subinterface on cable3/0:
interface cable3/0! No IP address! MAC level configuration only! first subinterfaceinterface cable3/0.1description Management Subinterfaceip address 10.255.1.1 255.255.255.0cable helper-address 10.151.129.2! second subinterfaceinterface cable3/0.2ip address 10.279.4.2 255.255.255.0cable helper-address 10.151.129.2! third subinterfaceinterface cable3/0.3ip address 10.254.5.2 255.255.255.0cable helper-address 10.151.129.2Cable Interface Bundling Example
The following example shows how to bundle a group of physical interfaces:
interface c3/0 and interface c4/0 are bundled.
interface c3/0ip address 209.165.200.225 255.255.255.0ip address 209.165.201.1 255.255.255.0 secondarycable helper-address 10.5.1.5! MAC level configurationcable bundle 1 masterint c4/0! No IP address! MAC layer configuration onlycable bundle 1Subinterface Definition on Bundle Master Example
The following example shows how to define subinterfaces on a bundle master and define Layer 3 configurations for each subinterface:
interface c3/0 and interface c4/0 are bundled.
interface c3/0! No IP address! MAC level configuration onlycable bundle 1 masterinterface c4/0! No IP address! MAC layer configurationcable bundle 1! first subinterfaceinterface c3/0.1ip address 10.22.64.0 255.255.255.0cable helper-address 10.4.1.2! second subinterfaceinterface c3/0.2ip address 10.12.39.0 255.255.255.0cable helper-address 10.4.1.2! third subinterfaceinterface c3/0.3ip address 10.96.3.0 255.255.255.0cable helper-address 10.4.1.2Cable Interface Bundle Master Configuration Example
The following examples show how to configure cable interface bundles:
Displaying the contents of the bundleRouter(config-if)# cable bundle ?<1-255> Bundle numberRouter(config-if)# cable bundle 25 ?master Bundle master<cr>Router(config-if)# cable bundle 25 master ?<cr>Router(config-if)# cable bundle 25 masterRouter(config-if)#07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down07:28:18: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to upPE Router Configuration Example
!! Identifies the version of Cisco IOS software installed.version 12.0! Defines the hostname of the Cisco uBR7246hostname region-1-ubr!! Describes where the system is getting the software image it is running. In! this configuration example, the system is loading a Cisco uBR7246 image named! AdamSpecial from slot 0.boot system flash slot0:ubr7200-p-mz.AdamSpecial!! Creates the enable secret password.enable secret xxxxenable password xxxx!! Sets QoS per modem for the cable plant.no cable qos permission createno cable qos permission updatecable qos permission modems!! Allows the system to use a full range of IP addresses, including subnet zero, for! interface addresses and routing updates.ip subnet-zero!! Enables Cisco Express Forwarding.ip cef!! Configures a Cisco IOS Dynamic Host Configuration Protocol (DHCP) server to insert the! DHCP relay agent information option in forwarded BOOTREQUEST messages.ip dhcp relay information option!! Enters the virtual routing forwarding (VRF) configuration mode and maps a VRF table to! the virtual private network (VPN) called MGMT-VPN. The VRF table contains the set of! routes that points to or gives routes to the CNR device, which provisions the cable! modem devices. Each VRF table defines a path through the MPLS cloud.ip vrf MGMT-VPN!! Creates the route distinguisher and creates the routing and forwarding table of the! router itself.rd 100:1!! Creates a list of import and/or export route target communities for the VPN.route-target export 100:2route-target export 100:3!! Maps a VRF table to the VPN called ISP1-VPN.ip vrf ISP1-VPN!! Creates the route distinguisher and creates the routing and forwarding table of the! router itself.rd 100:2!! Creates a list of import and/or export route target communities for the VPN.route-target import 100:1!! Maps a VRF table to the VPN called ISP2-VPN.ip vrf ISP2-VPN!! Creates the route distinguisher and creates the routing and forwarding table of the! router itself.rd 100:3!! Creates a list of import and/or export route target communities for the VPN.route-target import 100:1!! Maps a VRF table to the VPN called MSO-isp. Note: MSO-isp could be considered ISP-3; in! this case, the MSO is competing with other ISPs for other ISP services.ip vrf MSO-isp!! Creates the route distinguisher and creates the routing and forwarding table of the! router itself.rd 100:4!! Creates a list of import and/or export route target communities for the VPN.route-target import 100:1!! Builds a loopback interface to be used with MPLS and BGP; creating a loopback interface ! eliminates unnecessary updates (caused by physical interfaces going up and down) from! flooding the network.interface Loopback0ip address 10.0.0.0 255.255.255.0no ip directed-broadcast!! Assigns an IP address to this Fast Ethernet interface. MPLS tag-switching must be! enabled on this interface.interface FastEthernet0/0description Connection to MSO core.ip address 10.0.0.0 255.255.255.0no ip directed-broadcastfull-duplextag-switching ip!! Enters cable interface configuration mode and configures the physical aspects of the! 3/0 cable interface. Please note that no IP addresses are assigned to this interface;! they will be assigned instead to the logical subinterfaces. All other commands for! this cable interface should be configured to meet the specific needs of your cable RF! plant and cable network.interface Cable3/0no ip addressip directed-broadcastno ip mroute-cacheload-interval 30no keepalivecable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream frequency 855000000cable upstream 0 frequency 30000000cable upstream 0 power-level 0no cable upstream 0 shutdowncable upstream 1 shutdowncable upstream 2 shutdowncable upstream 3 shutdowncable upstream 4 shutdowncable upstream 5 shutdown!! Configures the physical aspects of the 3/0.1 cable subinterface. If cable modems have! not been assigned IP addresses, they will automatically come on-line using the settings! for subinterface X.1.interface Cable3/0.1description Cable Administration Network!! Associates this interface with the VRF and MPLS VPNs that connect to the MSO cable! network registrar (CNR). The CNR provides cable modems with IP addresses and other! initialization parameters.ip vrf forwarding MSO!! Defines a range of IP addresses and masks to be assigned to cable modems not yet associated with an ISP.ip address 10.0.0.0 255.255.255.0!! Disables the translation of directed broadcasts to physical broadcasts.no ip directed-broadcast!! Defines the DHCP server for cable modems whether they are associated with an ISP or! with the MSO acting as ISP.cable helper-address 10.4.1.2 cable-modem!! Defines the DHCP server for PCs that are not yet associated with an ISP.cable helper-address 10.4.1.2 host!! Disables cable proxy Address Resolution Protocol (ARP) and IP multicast echo on this! cable interface.no cable proxy-arpno cable ip-multicast-echo!! Configures the physical aspects of the 3/0.2 cable subinterface.interface Cable3/0.2description MSO as ISP Network!! Assigns this subinterface to the MPLS VPN used by the MSO to supply service to! customers—in this case, MSO-isp.ip vrf forwarding MSO-isp!! Defines a range of IP addresses and masks to be assigned to cable modems associated! with the MSO as ISP network.ip address 10.1.0.0 255.255.255.0 secondary!! Defines a range of IP addresses and masks to be assigned to host devices associated! with the MSO as ISP network.ip address 10.1.0.0 255.255.255.0!! Disables the translation of directed broadcasts to physical broadcasts.no ip directed-broadcast!! Defines the DHCP server for cable modems whether they are associated with an ISP or! with the MSO acting as ISP.cable helper-address 10.4.1.2 cable-modem!! Defines the DHCP server for PC host devices.cable helper-address 10.4.1.2 host!! Disables cable proxy Address Resolution Protocol (ARP) and IP multicast echo on this! cable interface.no cable proxy-arpno cable ip-multicast-echo!! Configures the physical aspects of the 3/0.3 cable subinterfaceinterface Cable3/0.3description ISP1's Network!! Makes this subinterface a member of the MPLS VPN.ip vrf forwarding isp1!! Defines a range of IP addresses and masks to be assigned to cable modems associated! with the MSO as ISP network.ip address 10.1.1.1 255.255.255.0 secondary!! Defines a range of IP addresses and masks to be assigned to host devices associated! with the MSO as ISP network.ip address 10.0.1.1 255.255.255.0!! Disables the translation of directed broadcasts to physical broadcasts.no ip directed-broadcast!! Disables cable proxy Address Resolution Protocol (ARP) and IP multicast echo on this! cable interface.no cable proxy-arpno cable ip-multicast-echo!! Defines the DHCP server for cable modems whether they are associated with an ISP or! with the MSO acting as ISP.cable helper-address 10.4.1.2 cable-modem!! Defines the DHCP server for PC host devices.cable helper-address 10.4.1.2 host!! Configures the physical aspects of the 3/0.4 cable subinterfaceinterface Cable3/0.4description ISP2's Network!! Makes this subinterface a member of the MPLS VPN.ip vrf forwarding isp2!! Defines a range of IP addresses and masks to be assigned to cable modems associated! with the MSO as ISP network.ip address 10.1.2.1 255.255.255.0 secondary!! Defines a range of IP addresses and masks to be assigned to host devices associated! with the MSO as ISP network.ip address 10.0.1.1 255.255.255.0!! Disables the translation of directed broadcasts to physical broadcasts.no ip directed-broadcast!! Disables cable proxy Address Resolution Protocol (ARP) and IP multicast echo on this! cable interface.no cable proxy-arpno cable ip-multicast-echo!!cable dhcp-giaddr policy!!! Defines the DHCP server for cable modems whether they are associated with an ISP or! with the MSO acting as ISP.cable helper-address 10.4.1.2 cable-modem!! Defines the DHCP server for PC host devices.cable helper-address 10.4.1.2 host!!endP Router Configuration Example
Building configuration...Current configuration:!version 12.0service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname R7460-7206-02!enable password xxxx!ip subnet-zeroip cefip host brios 223.255.254.253!interface Loopback0ip address 10.2.1.3 255.255.255.0no ip directed-broadcast!interface Loopback1no ip addressno ip directed-broadcastno ip mroute-cache!interface FastEthernet0/0ip address 1.7.108.2 255.255.255.0no ip directed-broadcastno ip mroute-cacheshutdownfull-duplexno cdp enable!interface Ethernet1/0ip address 10.0.1.2 255.255.255.0no ip directed-broadcastno ip route-cache cefno ip mroute-cachetag-switching ipno cdp enable!interface Ethernet1/1ip address 10.0.1.17 255.255.255.0no ip directed-broadcastno ip route-cache cefno ip mroute-cachetag-switching ipno cdp enable!interface Ethernet1/2ip address 10.0.2.2 255.255.255.0no ip directed-broadcastno ip route-cache cefno ip mroute-cachetag-switching ipno cdp enable!interface Ethernet1/3ip address 10.0.3.2 255.255.255.0no ip directed-broadcastno ip route-cache cefno ip mroute-cachetag-switching ipno cdp enable!interface Ethernet1/4ip address 10.0.4.2 255.255.255.0no ip directed-broadcastno ip route-cache cefno ip mroute-cachetag-switching ipno cdp enable!interface Ethernet1/5no ip addressno ip directed-broadcastno ip route-cache cefshutdownno cdp enable!interface Ethernet1/6no ip addressno ip directed-broadcastno ip route-cache cefshutdownno cdp enable!interface Ethernet1/7no ip addressno ip directed-broadcastno ip route-cache cefshutdownno cdp enable!router ospf 222network 10.0.1.0 255.255.255.0 area 0network 10.0.2.0 255.255.255.0 area 0network 10.0.3.0 255.255.255.0 area 0network 10.0.4.0 255.255.255.0 area 0network 20.2.1.3 255.255.255.0 area 0!ip classlessno ip http server!!map-list test-bno cdp run!tftp-server slot0:master/120/c7200-p-mz.120-1.4!line con 0exec-timeout 0 0password xxxxlogintransport input noneline aux 0line vty 0 4password xxxxlogin!no scheduler max-task-timeendConfiguring EBGP Routing to Exchange VPN Routes Between Autonomous Systems
The network topology in Figure 54 shows two autonomous systems, which are configured as follows:
•
•
•
•
•
•
Figure 54 Configuring Two Autonomous Systems
Autonomous System 1, CE1 Configuration
CE1: Company!interface Loopback1ip address 1.0.0.6 255.255.255.255!interface Serial1/3description Veritasno ip addressencapsulation frame-relayframe-relay intf-type dce!interface Serial1/3.1 point-to-pointdescription Veritasip address 1.6.2.1 255.255.255.252frame-relay interface-dlci 22!router ospf 1network 1.0.0.0 0.255.255.255 area 0Autonomous System 1, PE1 Configuration
PE1: Company!ip cef!ip vrf V1rd 1:105route-target export 1:100route-target import 1:100!interface Serial0/0description Burlingtonno ip addressencapsulation frame-relayno fair-queueclockrate 2000000!interface Serial0/0.3 point-to-pointdescription Burlingtonip vrf forwarding V1ip address 1.6.2.2 255.255.255.252frame-relay interface-dlci 22!interface Ethernet0/1description Vermontip address 100.2.2.5 255.255.255.0tag-switching ip!router ospf 1log-adjacency-changesnetwork 100.0.0.0 0.255.255.255 area 0!router ospf 10 vrf V1log-adjacency-changesredistribute bgp 1 metric 100 subnetsnetwork 1.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationneighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor 100.0.0.2 peer-group Rno auto-summary!address-family ipv4 vrf V1redistribute ospf 10no auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor R activateneighbor R send-community extendedneighbor 100.0.0.2 peer-group Rno auto-summaryexit-address-familyAutonomous System 1, P1 Configuration
P1: Company!ip cef!interface Loopback0ip address 100.0.0.2 255.255.255.255!interface Ethernet0/1description Ogunquitip address 100.2.1.1 255.255.255.0tag-switching ip!interface FastEthernet2/0description Veritasip address 100.2.2.1 255.255.255.0duplex autospeed autotag-switching ip!router ospf 1log-adjacency-changesnetwork 100.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationbgp log-neighbor-changesneighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor R route-reflector-clientneighbor 100.0.0.4 peer-group Rneighbor 100.0.0.5 peer-group R!address-family vpnv4neighbor R activateneighbor R route-reflector-clientneighbor R send-community extendedneighbor 100.0.0.4 peer-group Rneighbor 100.0.0.5 peer-group Rexit-address-familyAutonomous System 1, EBGP1 Configuration
EBGP1: Company!ip cef!interface Loopback0ip address 100.0.0.4 255.255.255.255!interface Ethernet0/1description Vermontip address 100.2.1.40 255.255.255.0tag-switching ip!interface ATM1/0description Lowellno ip addressno atm scrambling cell-payloadno atm ilmi-keepalive!interface ATM1/0.1 point-to-pointdescription Lowellip address 12.0.0.1 255.255.255.252pvc 1/100!router ospf 1log-adjacency-changesredistribute connected subnetsnetwork 100.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationno bgp default route-target filterbgp log-neighbor-changesneighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor 12.0.0.2 remote-as 2neighbor 100.0.0.2 peer-group Rno auto-summary!address-family vpnv4neighbor R activateneighbor R send-community extendedneighbor 12.0.0.2 activateneighbor 12.0.0.2 send-community extendedneighbor 100.0.0.2 peer-group Rno auto-summaryexit-address-familyAutonomous System 2, EBGP2 Configuration
EBGP2: Company!ip cef!ip vrf V1rd 2:103route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.3 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.3 255.255.255.255!interface Serial0/0description Littletonno ip addressencapsulation frame-relayload-interval 30no fair-queueclockrate 2000000!interface Serial0/0.2 point-to-pointdescription Littletonip unnumbered Loopback0ip router isistag-switching ipframe-relay interface-dlci 23!interface ATM1/0description Ogunquitno ip addressatm clock INTERNALno atm scrambling cell-payloadno atm ilmi-keepalive!interface ATM1/0.1 point-to-pointdescription Ogunquitip address 12.0.0.2 255.255.255.252pvc 1/100!router isisnet 49.0002.0000.0000.0003.00!router bgp 2no synchronizationno bgp default route-target filterbgp log-neighbor-changesneighbor 12.0.0.1 remote-as 1neighbor 200.0.0.8 remote-as 2neighbor 200.0.0.8 update-source Loopback0neighbor 200.0.0.8 next-hop-self!address-family ipv4 vrf V1redistribute connectedno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 12.0.0.1 activateneighbor 12.0.0.1 send-community extendedneighbor 200.0.0.8 activateneighbor 200.0.0.8 next-hop-selfneighbor 200.0.0.8 send-community extendedexit-address-familyAutonomous System 2, P2 Configuration
P2: Company!ip cef!ip vrf V1rd 2:108route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.8 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.8 255.255.255.255!interface FastEthernet0/0description Paxip address 200.9.1.2 255.255.255.0ip router isistag-switching ip!interface Serial5/0description Lowellno ip addressencapsulation frame-relayframe-relay intf-type dce!interface Serial5/0.1 point-to-pointdescription Lowellip unnumbered Loopback0ip router isistag-switching ipframe-relay interface-dlci 23!router isisnet 49.0002.0000.0000.0008.00!router bgp 2no synchronizationbgp log-neighbor-changesneighbor R peer-groupneighbor R remote-as 2neighbor R update-source Loopback0neighbor R route-reflector-clientneighbor 200.0.0.3 peer-group Rneighbor 200.0.0.9 peer-group R!address-family ipv4 vrf V1redistribute connectedno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor R activateneighbor R route-reflector-clientneighbor R send-community extendedneighbor 200.0.0.3 peer-group Rneighbor 200.0.0.9 peer-group Rexit-address-familyAutonomous System 2, PE2 Configuration
PE2: Company!ip cef!ip vrf V1rd 2:109route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.9 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.9 255.255.255.255!interface Serial0/0description Bethelno ip addressencapsulation frame-relayframe-relay intf-type dceno fair-queueclockrate 2000000!interface Serial0/0.1 point-to-pointdescription Bethelip vrf forwarding V1ip unnumbered Loopback1frame-relay interface-dlci 24!interface FastEthernet0/1description Littletonip address 200.9.1.1 255.255.255.0ip router isistag-switching ip!router ospf 10 vrf V1log-adjacency-changesredistribute bgp 2 subnetsnetwork 1.0.0.0 0.255.255.255 area 0!router isisnet 49.0002.0000.0000.0009.00!router bgp 2no synchronizationbgp log-neighbor-changesneighbor 200.0.0.8 remote-as 2neighbor 200.0.0.8 update-source Loopback0!address-family ipv4 vrf V1redistribute connectedredistribute ospf 10no auto-summaryno synchronizationexit-address-familyaddress-family vpnv4neighbor 200.0.0.8 activateneighbor 200.0.0.8 send-community extendedexit-address-familyAutonomous System 2, CE2 Configuration
CE2: Company!interface Loopback0ip address 1.0.0.11 255.255.255.255!interface Serial0description Paxno ip addressencapsulation frame-relayno fair-queueclockrate 2000000!interface Serial0.1 point-to-pointdescription Paxip unnumbered Loopback0frame-relay interface-dlci 24!router ospf 1network 1.0.0.0 0.255.255.255 area 0Configuring EBGP Routing to Exchange VPN Routes Between Autonomous Systems in a Confederation
The network topology in Figure 55 shows a single ISP that is partitioning the backbone with confederations. The AS number of the provider is 100. The two autonomous systems run their own IGPs and are configured as follows:
•
•
•
•
•
•
Figure 55 Configuring Two Autonomous Systems in a Confederation
Autonomous System 1, CE1 Configuration
CE1: Company!interface Loopback1ip address 1.0.0.6 255.255.255.255!interface Serial1/3description Veritasno ip addressencapsulation frame-relayframe-relay intf-type dce!interface Serial1/3.1 point-to-pointdescription Veritasip address 1.6.2.1 255.255.255.252frame-relay interface-dlci 22!router ospf 1network 1.0.0.0 0.255.255.255 area 0Autonomous System 1, PE1 Configuration
PE1: Company!ip cef!ip vrf V1rd 1:105route-target export 1:100route-target import 1:100!interface Serial0/0description Burlingtonno ip addressencapsulation frame-relayno fair-queueclockrate 2000000!interface Serial0/0.3 point-to-pointdescription Burlingtonip vrf forwarding V1ip address 1.6.2.2 255.255.255.252frame-relay interface-dlci 22!interface Ethernet0/1description Vermontip address 100.2.2.5 255.255.255.0tag-switching ip!router ospf 1log-adjacency-changesnetwork 100.0.0.0 0.255.255.255 area 0!router ospf 10 vrf V1log-adjacency-changesredistribute bgp 1 metric 100 subnetsnetwork 1.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationbgp confederation identifier 100bgp confederation identifier 100neighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor 100.0.0.2 peer-group Rno auto-summary!address-family ipv4 vrf V1redistribute ospf 10no auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor R activateneighbor R send-community extendedneighbor 100.0.0.2 peer-group Rno auto-summaryexit-address-familyAutonomous System 1, P1 Configuration
P1: Company!ip cef!interface Loopback0ip address 100.0.0.2 255.255.255.255!interface Ethernet0/1description Ogunquitip address 100.2.1.1 255.255.255.0tag-switching ip!interface FastEthernet2/0description Veritasip address 100.2.2.1 255.255.255.0duplex autospeed autotag-switching ip!router ospf 1log-adjacency-changesnetwork 100.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationbgp log-neighbor-changesbgp confederation identifier 100neighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor R route-reflector-clientneighbor 100.0.0.4 peer-group Rneighbor 100.0.0.5 peer-group R!address-family vpnv4neighbor R activateneighbor R route-reflector-clientneighbor R send-community extendedneighbor 100.0.0.4 peer-group Rneighbor 100.0.0.5 peer-group Rexit-address-familyAutonomous System 1, EBGP1 Configuration
EBGP1: Company!ip cef!interface Loopback0ip address 100.0.0.4 255.255.255.255!interface Ethernet0/1description Vermontip address 100.2.1.40 255.255.255.0tag-switching ip!interface ATM1/0description Lowellno ip addressno atm scrambling cell-payloadno atm ilmi-keepalive!interface ATM1/0.1 point-to-pointdescription Lowellip address 12.0.0.1 255.255.255.252pvc 1/100!router ospf 1log-adjacency-changesredistribute connected subnetsnetwork 100.0.0.0 0.255.255.255 area 0!router bgp 1no synchronizationno bgp default route-target filterbgp log-neighbor-changesbgp confederation identifier 100bgp confederation peers 1neighbor R peer-groupneighbor R remote-as 1neighbor R update-source Loopback0neighbor 12.0.0.2 remote-as 2neighbor 12.0.0.2 next-hop-selfneighbor 100.0.0.2 peer-group Rno auto-summary!address-family vpnv4neighbor R activateneighbor R send-community extendedneighbor 12.0.0.2 activateneighbor 12.0.0.2 next-hop-selfneighbor 12.0.0.2 send-community extendedneighbor 100.0.0.2 peer-group Rno auto-summaryexit-address-familyAutonomous System 2, EBGP2 Configuration
EBGP2: Company!ip cef!ip vrf V1rd 2:103route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.3 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.3 255.255.255.255!interface Serial0/0description Littletonno ip addressencapsulation frame-relayload-interval 30no fair-queueclockrate 2000000!interface Serial0/0.2 point-to-pointdescription Littletonip unnumbered Loopback0ip router isistag-switching ipframe-relay interface-dlci 23!interface ATM1/0description Ogunquitno ip addressatm clock INTERNALno atm scrambling cell-payloadno atm ilmi-keepalive!interface ATM1/0.1 point-to-pointdescription Ogunquitip address 12.0.0.2 255.255.255.252pvc 1/100!router isisnet 49.0002.0000.0000.0003.00!router bgp 2no synchronizationno bgp default route-target filterbgp log-neighbor-changesbgp confederation identifier 100bgp confederation peers 1neighbor 12.0.0.1 remote-as 1neighbor 12.0.0.1 next-hop-selfneighbor 200.0.0.8 remote-as 2neighbor 200.0.0.8 update-source Loopback0neighbor 200.0.0.8 next-hop-self!address-family ipv4 vrf V1redistribute connectedno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor 12.0.0.1 activateneighbor 12.0.0.1 next-hop-selfneighbor 12.0.0.1 send-community extendedneighbor 200.0.0.8 activateneighbor 200.0.0.8 next-hop-selfneighbor 200.0.0.8 send-community extendedexit-address-familyAutonomous System 2, P2 Configuration
P2: Company!ip cef!ip vrf V1rd 2:108route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.8 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.8 255.255.255.255!interface FastEthernet0/0description Paxip address 200.9.1.2 255.255.255.0ip router isistag-switching ip!interface Serial5/0description Lowellno ip addressencapsulation frame-relayframe-relay intf-type dce!interface Serial5/0.1 point-to-pointdescription Lowellip unnumbered Loopback0ip router isistag-switching ipframe-relay interface-dlci 23!router isisnet 49.0002.0000.0000.0008.00!router bgp 2no synchronizationbgp log-neighbor-changesbgp confederation identifier 100neighbor R peer-groupneighbor R remote-as 2neighbor R update-source Loopback0neighbor R route-reflector-clientneighbor 200.0.0.3 peer-group Rneighbor 200.0.0.9 peer-group R!address-family ipv4 vrf V1redistribute connectedno auto-summaryno synchronizationexit-address-family!address-family vpnv4neighbor R activateneighbor R route-reflector-clientneighbor R send-community extendedneighbor 200.0.0.3 peer-group Rneighbor 200.0.0.9 peer-group Rexit-address-familyAutonomous System 2, PE2 Configuration
PE2: Company!ip cef!ip vrf V1rd 2:109route-target export 1:100route-target import 1:100!interface Loopback0ip address 200.0.0.9 255.255.255.255ip router isis!interface Loopback1ip vrf forwarding V1ip address 1.0.0.9 255.255.255.255!interface Serial0/0description Bethelno ip addressencapsulation frame-relayframe-relay intf-type dceno fair-queueclockrate 2000000!interface Serial0/0.1 point-to-pointdescription Bethelip vrf forwarding V1ip unnumbered Loopback1frame-relay interface-dlci 24!interface FastEthernet0/1description Littletonip address 200.9.1.1 255.255.255.0ip router isistag-switching ip!router ospf 10 vrf V1log-adjacency-changesredistribute bgp 2 subnetsnetwork 1.0.0.0 0.255.255.255 area 0!router isisnet 49.0002.0000.0000.0009.00!router bgp 2no synchronizationbgp log-neighbor-changesbgp confederation identifier 100neighbor 200.0.0.8 remote-as 2neighbor 200.0.0.8 update-source Loopback0!address-family ipv4 vrf V1redistribute connectedredistribute ospf 10no auto-summaryno synchronizationexit-address-familyaddress-family vpnv4neighbor 200.0.0.8 activateneighbor 200.0.0.8 send-community extendedexit-address-familyAutonomous System 2, CE2 Configuration
CE2: Company!interface Loopback0ip address 1.0.0.11 255.255.255.255!interface Serial0description Paxno ip addressencapsulation frame-relayno fair-queueclockrate 2000000!interface Serial0.1 point-to-pointdescription Paxip unnumbered Loopback0frame-relay interface-dlci 24!router ospf 1network 1.0.0.0 0.255.255.255 area 0Implementing MPLS QoS Example
Figure 56 illustrates a sample MPLS topology that implements the MPLS QoS feature. The following sections contain the configuration commands entered on Routers R1 to R6 and on Switches 1 and 2 included in this figure.
Figure 56 Sample MPLS Topology Implementing QoS
Configuring CEF Example
The following configuration commands enable CEF. CEF switching is a prerequisite for the MPLS feature and must be running on all routers in the network:
ip cef distributedtag-switching ip!Running IP on Router 2 Example
The following commands enable IP routing on Router 2. All routers must have IP enabled:
Note
!ip routing!hostname R2!interface Loopback0ip address 10.10.10.10 255.255.255.255!interface POS0/3ip unnumbered Loopback0crc 16clock source internal!router ospf 100network 10.0.0.0 0.255.255.255 area 100!Running IP on Router 1 Example
The following commands enable IP routing on Router 1:
Note
ip routing!hostname R1!interface Loopback0ip address 15.15.15.15 255.255.255.255!interface POS0/3ip unnumbered Loopback0crc 16clock source internal!router ospf 100network 15.0.0.0 0.255.255.255 area 100Running MPLS on Router 4 Example
Router 4 is a label edge router. CEF and the MPLS feature must be enabled on this router. CAR is also configured on Router 4 on interface POS3/0/0 (see the following section on configuring CAR).
!hostname R4!ip routingtag-switching iptag-switching advertise-tags!ip cef distributed!interface Loopback0ip address 11.11.11.11 255.255.255.255!interface Ethernet0/1ip address 90.0.0.1 255.0.0.0tag-switching ip!Configuring CAR Example
Lines 3 and 4 of the following sample configuration contain the CAR rate policies. Line 3 sets the committed information rate (CIR) at 155,000,000 bits and the normal burst/maximum burst size at 200,000/800,000 bytes. The conform action (action to take on packets) sets the IP precedence and sends the packets that conform to the rate limit. The exceed action sets the IP precedence and sends the packets when the packets exceed the rate limit.
!interface POS3/0/0ip unnumbered Loopback0rate-limit input 155000000 2000000 8000000 conform-action set-prec-transmit 5exceed-action set-prec-transmit 1ip route-cache distributed!router ospf 100network 11.0.0.0 0.255.255.255 area 100network 90.0.0.0 0.255.255.255 area 100Running MPLS on Router 3 Example
Router 3 is running MPLS. CEF and the MPLS feature must be enabled on this router. Router 3 contains interfaces that are configured for WRED, multi-VC, per-VC WRED, WFQ, and CAR. The following sections contain these sample configurations:
!hostname R3!ip cef distributed!interface Loopback0ip address 12.12.12.12 255.255.255.255!interface Ethernet0/1ip address 90.0.0.2 255.0.0.0tag-switching ipConfiguring Point-to-Point WRED Example
The following commands configure WRED on an ATM interface. In this example, the commands refer to a PA-A1 port adapter.
!interface ATM1/1/0ip route-cache distributedatm clock INTERNALrandom-detect!Configuring an Interface for Multi-VC Mode Example
The following commands configure interface ATM1/1/0 for multi-VC mode. In this example, the commands refer to a PA-A1 port adapter.
!interface ATM1/1/0.1 tag-switchingip unnumbered Loopback0tag-switching atm multi-vctag-switching ip!Configuring WRED and Multi-VC Mode on a PA-A3 Port-Adapter Interface Example
The commands to configure a PA-A3 port adapter differ slightly from the commands to configure a PA-A1 port adapter as shown previously.
On an PA-A3 port-adapter interface, distributed WRED (DWRED) is supported only per-VC, not per-interface.
To configure a PA-A3 port adapter, enter the following commands:
!interface ATM1/1/0ip route-cache distributedatm clock INTERNAL!interface ATM 1/1/0.1 tag-switchingip unnumbered Loopback0tag-switching multi-vctag-switching random detect attach groupname!Configuring Per-VC WRED Example
The following commands configure per-VC WRED on a PA-A3 port adapter only:
Note
!interface ATM2/0/0no ip addressip route-cache distributedinterface ATM2/0/0.1 point-to-pointip unnumbered Loopback0no ip directed-broadcastpvc 10/100random-detectencapsulation aal5snapexit!tag-switching ipConfiguring WRED and WFQ Example
Lines 5 and 6 of the following sample configuration contain the commands for configuring WRED and WFQ on interface Hssi2/1/0:
!interface Hssi2/1/0ip address 91.0.0.1 255.0.0.0ip route-cache distributedtag-switching iprandom-detectfair queue toshssi internal-clock!Configuring CAR Example
Lines 3 and 4 of the following sample configuration contain the CAR rate policies. Line 3 sets the CIR at 155,000,000 bits and the normal burst/maximum burst size at 200,000/800,000 bytes. The conform action (action to take on packets) sets the IP precedence and sends the packets that conform to the rate limit. The exceed action sets the IP precedence and sends the packets when the packets exceed the rate limit.
!interface POS3/0/0ip unnumbered Loopback0rate-limit input 155000000 2000000 8000000 conform-action set-prec-transmit 2exceed-action set-prec-transmit 2ip route-cache distributed!router ospf 100network 12.0.0.0 0.255.255.255 area 100network 90.0.0.0 0.255.255.255 area 100network 91.0.0.0 0.255.255.255 area 100!ip route 93.0.0.0 255.0.0.0 Hssi2/1/0 91.0.0.2!Running MPLS on Router 5 Example
Router 5 is running the MPLS feature. CEF and MPLS must be enabled on this router. Router 5 has also been configured to create an ATM subinterface in multi-VC mode and to create a PVC on a point-to-point subinterface. The sections that follow contain these sample configurations.
!hostname R5!ip cef distributed!interface Loopback0ip address 13.13.13.13 255.255.255.255!interface Ethernet0/2ip address 92.0.0.1 255.0.0.0tag-switching ipConfiguring an ATM Interface Example
The following commands create an ATM interface:
!interface ATM1/0/0no ip addressip route-cache distributedatm clock INTERNAL!Configuring an ATM MPLS Subinterface in Multi-VC Mode Example
The following commands create an MPLS subinterface in multi-VC mode:
!interface ATM1/0/0.1 tag-switchingip unnumbered Loopback0tag-switching atm multi-vctag-switching ip!Configuring a PVC on Point-to-Point Subinterface Example
The following commands create a PVC on a point-to-point subinterface (interface ATM1/0/0.2).
!interface ATM1/0/0.2 point-to-pointip unnumbered Loopback0pvc 10/100random-detectencapsulation aal5snapexit!tag-switching ip!interface Hssi3/0ip address 91.0.0.2 255.0.0.0tag-switching iphssi internal-clock!router ospf 100network 13.0.0.0 0.255.255.255 area 100network 91.0.0.0 0.255.255.255 area 100network 92.0.0.0 0.255.255.255 area 100!Running MPLS on Router 6 Example
Router 6 is running the MPLS feature. CEF and MPLS must be enabled on this router. The following commands configure MPLS on an ethernet interface:
!hostname R6!ip cef distributed!interface Loopback0ip address 14.14.14.14 255.255.255.255!interface Ethernet0/1ip address 93.0.0.1 255.0.0.0tag-switching ip!interface Ethernet0/2ip address 92.0.0.2 255.0.0.0tag-switching ip!interface Ethernet0/3ip address 94.0.0.1 255.0.0.0tag-switching ip!router ospf 100network 14.0.0.0 0.255.255.255 area 100network 92.0.0.0 0.255.255.255 area 100network 93.0.0.0 0.255.255.255 area 100network 94.0.0.0 0.255.255.255 area 100!Configuring ATM Switch 2 Example
Switch 2 is configured for MPLS and creates an ATM Forum PVC. The following commands configure MPLS on ATM switch2:
!hostname S2!interface Loopback0ip address 16.16.16.16 255.255.255.255!interface ATM0/0/0ip unnumbered Loopback0tag-switching ip!interface ATM0/0/1ip unnumbered Loopback0tag-switching ipatm pvc 10 100 interface ATM0/0/0 10 100interface ATM0/0/2no ip addressno ip directed-broadcast!interface ATM0/0/3ip unnumbered Loopback0tag-switching ip!interface ATM1/1/0ip unnumbered Loopback0tag-switching ip!router ospf 100network 16.0.0.0 0.255.255.255 area 100!Configuring ATM Switch 1 Example
Switch 1 is configured to create an ATM Forum PVC. The following commands configure MPLS on ATM switch1:
!hostname S1!interface Loopback0ip address 17.17.17.17 255.255.255.255!interface ATM0/0/0ip unnumbered Loopback0tag-switching ip!Configuring Label VCs and an ATM Forum PVC Example
Line 3 of the following sample configuration contains the configuration command for an ATM Forum PVC:
!interface ATM0/1/1ip unnumbered Loopback0atm pvc 10 100 interface ATM0/0/0 10 100tag-switching ip!interface ATM1/1/0ip unnumbered Loopback0tag-switching ip!router ospf 100network 17.0.0.0 0.255.255.255 area 100!Configuring an MPLS LSC Examples
The following sections present the following MPLS LSC configuration examples:
•
•
•
•
•
•
•
Configuring ATM-LSRs Example
The network topology shown in Figure 57 incorporates two ATM-LSRs in an MPLS network. This topology includes two LSCs (Cisco 7200 routers), two BPX service nodes, and two edge LSRs (Cisco 7500 routers).
For the IGX, use the following commands:
extended-port atm1/0 descriptor 0.x.x.0 tag-control-protocol vsi slaves 32 id xFigure 57 ATM-LSR Network Configuration Example
Based on Figure 57, the following configuration examples are provided:
LSC1 Configuration
7200 LSC1:ip cef!interface loopback0ip address 192.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0tag-switching atm vpi 2-15tag-switching ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0tag-switching atm vpi 2-5tag-switching ipBPX1 and BPX2 Configuration
BPX1 and BPX2:uptrk 1.1addshelf 1.1 v 1 1cnfrsrc 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 1.3cnfrsrc 1.3 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 2.2cnfrsrc 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Note
LSC2 Configuration
7200 LSC2:ip cef!interface loopback0ip address 142.2.143.22 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0tag-switching atm vpi 2-15tag-switching ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0tag-switching atm vpi 2-5tag-switching ip!Edge LSR1 Configuration
7500 LSR1:ip cef distributed!interface loopback 0ip address 142.6.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.5 tag-switchingip unnumbered loopback 0tag-switching atm vpi 2-5tag-switching ipEdge LSR2 Configuration
7200 LSR2:ip cefinterface loopback 0ip address 142.6.142.2 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.9 tag-switchingip unnumbered loopback 0tag-switching atm vpi 2-5tag-switching ipConfiguring Multi-VCs Example
When you configure multi-VC support, four label VCs for each destination are created by default, as follows:
•
•
•
•
This section provides examples for the following configurations, based on the sample network configuration shown earlier in Figure 57:
Note
LSC1 Configuration
7200 LSC1:ip cef!interface loopback0ip address 192.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi!interface XTagATM13ip unnumbered loopback 0extended-port ATM3/0 bpx 1.3tag-switching atm vpi 2-15tag-switching atm cos available 25tag-switching atm cos standard 25tag-switching atm cos premium 25tag-switching atm cos control 25tag-switching ip!interface XTagATM23ip unnumbered loopback 0extended-port ATM3/0 bpx 2.2tag-switching atm vpi 2-5tag-switching atm cos available 20tag-switching atm cos standard 30tag-switching atm cos premium 25tag-switching atm cos control 25tag-switching ipBPX1 and BPX2 Configuration
BPX1 and BPX2:uptrk 1.1addshelf 1.1 v 1 1cnfrsrc 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 1.3cnfrsrc 1.3 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 2.2cnfrsrc 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000LSC2 Configuration
7200 LSC2:ip cef!interface loopback0ip address 142.2.143.22 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi!interface XTagATM13ip unnumbered loopback 0extended-port ATM3/0 bpx 1.3tag-switching atm vpi 2-15tag-switching atm cos available 25tag-switching atm cos standard 25tag-switching atm cos premium 25tag-switching atm cos control 25tag-switching ip!interface XTagATM23ip unnumbered loopback 0extended-port ATM3/0 bpx 2.2tag-switching atm vpi 2-5tag-switching atm cos available 20tag-switching atm cos standard 30tag-switching atm cos premium 25tag-switching atm cos control 25tag-switching ipEdge LSR1 Configuration
7500 LSR1:ip cef distributedinterface loopback 0ip address 142.6.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.5 tag-switchingip unnumbered loopback 0tag-switching atm vpi 2-5tag-switching atm multi-vctag-switching ipEdge LSR2 Configuration
7200 LSR2:ip cefinterface loopback 0ip address 142.2.142.2 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.9 tag-switchingip unnumbered loopback 0tag-switching atm vpi 2-5tag-switching atm multi-vctag-switching ipQoS Support
If LSC1 supports QoS, but LSC2 does not, LSC1 makes VC requests for the following default classes:
•
•
LSC2 ignores the call field in the request and allocates two UBR label VCs.
If LSR1 supports QoS, but LSR2 does not, LSR2 receives the request to create multiple label VCs, but by default, creates class 0 only (UBR).
Configuring ATM-LSRs with a Cisco 6400 NRP Operating as LSC Example
When you use the NRP as an MPLS LSC in the Cisco 6400 UAC, you must configure the NSP to provide connectivity between the NRP and the Cisco BPX switch. When configured in this way (as shown in Figure 58), the NRP is connected to the NSP by means of the internal interface ATM3/0/0, while external connectivity from the Cisco 6400 UAC to the Cisco BPX switch is provided by means of the external interface ATM1/0/0 from the NSP.
Figure 58 Cisco 6400 UAC NRP Operating As an LSC
Based on Figure 58, the following configuration examples are provided:
•
•
6400 UAC NSP Configuration
6400 NSP:!interface ATM3/0/0atm pvp 0 interface ATM1/0/0 0atm pvp 2 interface ATM1/0/0 2atm pvp 3 interface ATM1/0/0 3atm pvp 4 interface ATM1/0/0 4atm pvp 5 interface ATM1/0/0 5atm pvp 6 interface ATM1/0/0 6atm pvp 7 interface ATM1/0/0 7atm pvp 8 interface ATM1/0/0 8atm pvp 9 interface ATM1/0/0 9atm pvp 10 interface ATM1/0/0 10atm pvp 11 interface ATM1/0/0 11atm pvp 12 interface ATM1/0/0 12atm pvp 13 interface ATM1/0/0 13atm pvp 14 interface ATM1/0/0 14atm pvp 15 interface ATM1/0/0 15
Note
atm pvp 0 interface ATM1/0/0 06400 UAC NRP LSC1 Configuration
ip cef!interface Loopback0ip address 142.2.143.22 255.255.255.255!interface ATM0/0/0no ip addresstag-control-protocol vsi!interface XTagATM13ip unnumbered Loopback0extended-port ATM0/0/0 bpx 1.3tag-switching atm vpi 2-15tag-switching ip!interface XTagATM22ip unnumbered Loopback0extended-port ATM0/0/0 bpx 2.2tag-switching atm vpi 2-5tag-switching ip
