Table Of Contents
MPLS Label Switch Controller and Enhancements
Changing from Tag-Switching to MPLS Terminology
MPLS LSC Functional Description
Using Controlled ATM Switch Ports as Router Interfaces
How the LSC, ATM Switch, and VSI Work Together
Platforms Supported by MPLS LSC
Supported Routing Protocols on LC-ATM and MPLS LSC
Supported Standards, MIBs, and RFCs
Configuring the 7200 Series LSCs for BPX and IGX Switches
Verifying the MPLS LSC Configuration
Configuration Example: MPLS LSC
Configuring the Cisco MGX 8850 Switch and RPM-PR as an MPLS LSC
Cisco MGX 8850 RPM-PR Overview
Comparing Cisco 7200 LSC Configuration with Cisco RPM-PR LSC Configuration
Comparing Edge Label Switch Router Configurations
Configuring the Cisco MGX RPM-PR
Configuring the Cisco MGX 8850 Switch with RPM-PR to Perform Basic LSC Operations
Configuration Steps: Adding an MPLS Controller to the PXM-45
Configuration Steps: Mapping an AXSM Port to an XtagATM Interface on the LSC
Configuration Steps: Configuring an RPM as an Edge Label Switch Router
MGX ATM MPLS Configuration Examples
PVP-Based ATM MPLS Network Configuration
Simple PVC-Based Packet MPLS Network Configuration
Configuring the Cisco 6400 Universal Access Concentrator as an MPLS LSC
Cisco 6400 UAC Architectural Overview
Configuring Permanent Virtual Circuits and Permanent Virtual Paths
Control VC Setup for MPLS LSC Functions
Configuring the Cisco 6400 UAC to Perform Basic MPLS LSC Operations
Configuration Steps: Configuring Cisco 6400 UAC NRP as an MPLS LSC
Configuration Steps: Configuring the Cisco 6400 UAC NSP for MPLS Connectivity to the BPX Switch
Configuration Example: Configuring a Cisco 6400 NRP as an LSC
Configuring the Cisco IGX 8400 Switch with a Universal Router Module as an MPLS ATM-LSR
Cisco IGX 8400 Switch with a Universal Router Module Overview
Configuration Example: Configuring a Cisco IGX 8400 Switch with a URM as an MPLS ATM-LSR
Disabling the LSC from Acting as an Edge LSR
Feature 1: Creating Virtual Trunks
Typical ATM Hybrid Network with Virtual Trunks
Configuration Example: Configuring Virtual Trunks with Cisco 7200 LSCs
Configuration for LSC1 Implementing Virtual Trunking
Configuration for BPX1 and BPX2
Configuration for LSC2 Implementing Virtual Trunking
Configuration Example: Configuring Virtual Trunking on Cisco 6400 NRP LSCs
Configuration for Cisco 6400 UAC NSP
Configuration for Cisco 6400 UAC NRP LSC1 Implementing Virtual Trunking
Configuration for BPX1 and BPX2
Configuration for 6400 UAC NRP LSC2 Implementing Virtual Trunking
Feature 2: Using LSC Redundancy
Differences Between Hot and Warm LSC Redundancy
General Redundancy Operational Modes
How LSC Redundancy Differs from Router and Switch Redundancy
ATM, Frame Relay, and Circuit Switch Redundancy
General Hot/Warm Standby Redundancy in Switches
Partitioning the Resources of the ATM Switch
Implementing the Parallel VSI Model
Configuration Example: Configuring LSC Hot Redundancy
Configuration for BPX-1 and BPX-2
Configuration for Edge LSR 7200-1
Configuration for Edge LSR 7200-2
Configuration Example: Configuring LSC Warm Standby Redundancy
Configuration Example: Configuring an Interface Using Two VSI Partitions
Feature 3: Reducing the Number of Label Switch Paths Created in an MPLS Network
Using an Access List to Disable Creation of LSPs to Destination IP Addresses
Specifying Exact Match IP Addresses with an Access List
Configuration Example: Using an Access List to Limit Headend VCs
Configuration for BPX 1 and BPX 2
Feature 4: Differentiated Services and MPLS QoS Multi-VCs
Differentiated Services and Quality of Service
DiffServ Classes and Cisco IP+ATM Switches
Requirements for Differential Services Approach to QoS
Optionally Setting the MPLS Experimental Field Value
Configuring MPLS QoS in the Core of an ATM Network
Configuring Queuing Functions on Router Output Interfaces
Setting the ATM-CLP Bit on Enhanced ATM Port Adapter Interfaces
VC Merge Hardware and Software Requirements
Feature 6: MPLS Diff-Serv-Aware Traffic Engineering over ATM
Guaranteed Bandwidth Service Configuration
Feature 7: MPLS: OAM Insertion and Loop Detection on LC-ATM
Prerequisites for MPLS: OAM Insertion and Loop Detection on LC-ATM
Restrictions for MPLS: OAM Insertion and Loop Detection on LC-ATM
How to Configure MPLS: OAM Insertion and Loop Detection on LC-ATM
Configuration Examples for MPLS: OAM Insertion and Loop Detection on LC-ATM
OAM Management with MPLS Subinterfaces Example
OAM Management with Switch Subinterfaces on Route Processor Modules Example
OAM Management with XtagATM Subinterfaces on Label Switch Controllers Example
Feature 8: Troubleshooting the MPLS LSC Network with the LVC Path Trace Feature
Prerequisites for the LVC Path Trace Feature
Restriction for the LVC Path Trace Feature
Starting Up the Cisco MGX 8850 PXM-45 and Cisco MGX AXSM
File and Directory Names Are Case Sensitive
Flash Command vs. Bootflash Command
Upgrade Cisco MGX 8850 PXM-45 Card First
Set Boot IP Address in Every Switch
Copying the Images from the TFTP Server
Upgrading the PXM-45 and AXSM Images
Verifying the IOS Files on the PXM-45 E:Drive
debug mpls xtagatm cross-connect
show controllers vsi control-interface
show controllers vsi descriptor
show xtagatm cos-bandwidth-allocation xtagatm
MPLS Label Switch Controller and Enhancements
This document describes the Cisco Multiprotocol Label Switching (MPLS) Label Switch Controller (LSC). It describes the MPLS LSC feature, identifies the platforms supported by the MPLS LSC, provides configuration examples for MPLS LSC components, and describes related IOS commands that can be used with the supported platforms.
Feature History for MPLS Label Switch Controller and Enhancements
This document was introduced as the Tag Switch Controller.
Added references to the Cisco IOS switching services documentation.
Added support for multi-VCs.
Added support for the Cisco 6400 UAC.
Added support for virtual trunking/tunneling.
Added support for dedicated LSC with the command
mpls atm disable-headend-vc.Added support for LSC redundancy.
Added access list support for controlling the creation of label switch paths with the command mpls request-labels for.
Added support for Cisco IGX 8410, 8420, and 8430 switches.
Removed support for the 7500 router as an MPLS LSC.
Changed tag-switching commands and terminology to MPLS format.
Added support for Cisco MGX 8850 switch with the Cisco MGX RPM-PR card as an MPLS LSC.
Added DiffServ with MPLS QoS multi-VC feature support.
Added the vci-range keyword to the mpls atm vpi and mpls atm vp-tunnel commands.
Extended the VPI range from 256 to 4095.
Added support for the Cisco 8400 IGX Switch with a Universal Router Module as an MPLS ATM-LSR.
Added support for the VC merge and MPLS Diff-Serv-aware features.
Added support for the MPLS OAM Insertion and Loop Detection on LC-ATM feature.
Added the LVC Path Trace feature.
Added the path keyword to the show mpls atm-ldp bindings command.
This feature was integrated into 12.3(9).
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Document Organization
This document is organized as follows. The following sections describe MPLS LSC in general:
•
Platforms Supported by MPLS LSC
•
The following sections describe MPLS LSC features. Each section contains its own configuration steps and examples:
•
•
•
•
•
•
•
The following section provides additional information for the Cisco MGX 8850 RPM-PR:
•
The following sections describe commands used throughout the book:
Changing from Tag-Switching to MPLS Terminology
Cisco is moving from tag-switching to MPLS, because MPLS is compliant with the IETF standard. This change necessitates terminology and command changes. Table 1 lists the old tag-switching terms and the equivalent MPLS terms used in this document. Table 8 lists the changes made to commands.
Feature Overview
The MPLS label switch controller (LSC), combined with the slave ATM switch, supports scalable integration of IP services over an ATM network. The MPLS LSC enables the slave ATM switch to:
•
•
•
The MPLS LSC supports highly scalable integration of MPLS (IP+ATM) services by using a direct peer relationship between the ATM switch and MPLS routers. This direct peer relationship removes the limitation on the number of IP edge routers (typical of traditional IP-over-ATM networks), allowing service providers to meet growing demands for IP services. The MPLS LSC also supports direct and rapid implementation of advanced IP and MPLS services over ATM networks using ATM switches.
MPLS combines the performance and virtual circuit capabilities of Layer 2 (data link layer) switching with the scalability of Layer 3 (network layer) routing capabilities. This combination enables service providers to deliver solutions for managing growth, providing differentiated services, and leveraging existing networking infrastructures.
The MPLS LSC architecture provides the flexibility to:
•
•
By deploying the MPLS LSC across large enterprise networks or wide area networks, customers can:
•
•
•
MPLS LSC Functional Description
The MPLS LSC is a label switch router (LSR) that is configured to control the operation of a separate ATM switch. Together, the MPLS LSC and the controlled ATM switch function as a single ATM label switch router (ATM-LSR).
Figure 1 shows the functional relationship between the MPLS LSC and the ATM switch that it controls.
Figure 1 MPLS Label Switch Controller and Controlled ATM Switch
The following routers can function as an MPLS LSC:
•
•
The following ATM switches can function with the Cisco 7200 series router as the controlled ATM switch:
•
•
Also, the Cisco MGX 8850 switch with a Cisco MGX 8850 Route Processor Module (RPM-PR) can function as an MPLS ATM-LSR.
The MPLS LSC controls the ATM switch by means of the Virtual Switch Interface (VSI), which runs over an ATM link connecting the two devices.
The dotted line in Figure 1 represents the logical boundaries of the external interfaces of the MPLS LSC and the controlled ATM switch, as discovered by the IP routing topology. The controlled ATM switch provides one or more XTagATM interfaces at this external boundary. The MPLS LSC can incorporate other label-controlled or nonlabel-controlled router interfaces.
Using Controlled ATM Switch Ports as Router Interfaces
The XTagATM ports on the LSC are used as an IOS interface type called extended Label ATM (XTagATM). To associate these XTagATM interfaces with particular physical interfaces on the controlled ATM switch, use the interface configuration command extended-port.
Figure 2 shows a typical MPLS LSC configuration that controls three ATM ports on a Cisco BPX switch: ports 6.1, 6.2, and 12.2. These corresponding XTagATM interfaces were created on the MPLS LSC and associated with the corresponding ATM ports on the Cisco BPX switch by means of the extended-port command.
Figure 2 Typical MPLS LSC and BPX Switch Configuration
Observe from Figure 2 that:
•
•
How the LSC, ATM Switch, and VSI Work Together
The LSC and slave ATM switch have the following characteristics:
•
•
•
•
If a component on the LSC fails, the ATM switch's IP switching function is disabled. The standalone LSC is the single point of failure.
The VSI implementation includes the following characteristics:
•
•
•
•
MPLS LSC Benefits
Using the MPLS LSC provides the following benefits:
•
•
•
–
–
–
–
MPLS LSC Restrictions
•
•
•
ip route destination-prefix destination-mask forwarding-router's-address
Note
•
Related Documents
The following documents provide more information about MPLS features:
•
•
•
The following documents provide more information about platform-specific features:
Cisco 6400 UAC
•
Cisco BPX 8600 Series Switches
•
Cisco IGX 8400 Series Switches
•
•
Cisco MGX 8850 Route Processor Module
•
Cisco IGX 8400 Series Switches with a URM
•
•
Platforms Supported by MPLS LSC
Routers
You can use the following routers to configure an ATM-LSR:
•
–
•
–
–
–
•
Switches
You can use the following ATM switches to configure an ATM-LSR:
•
•
Switches with Router Modules
You can also use the following switches with router modules as ATM-LSRs:
•
•
Supported Routing Protocols on LC-ATM and MPLS LSC
The followng protocols are supported on the LC-ATM and MPLS LSC:
•
•
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs:
•
•
Configuration Tasks
See the following for examples of basic configuration tasks for enabling MPLS LSC functionality:
•
•
•
•
•
Refer to the Cisco BPX 8600 or IGX 8400 series switch documentation for BPX/IGX switch configuration examples.
Configuring the 7200 Series LSCs for BPX and IGX Switches
To enable MPLS functionality on the Cisco 7200 series routers connected to BPX and IGX switches, perform the following steps on each LSC in the configuration.
Note
.
Verifying the MPLS LSC Configuration
The following sections explain some of the commands you can use to ensure that you have configured MPLS correctly.
Check that the Switch Control Port Is Active
Enter the show controllers vsi status command to show the switch control port is active. If an interface has been discovered by the LSC, but an XTagATM interface has not been associated with it through the extended-port configuration command, then the interface name is marked <unknown>, and interface status is marked n/a.
The following is sample output from the show controllers vsi status command:
Router# show controllers vsi statusInterface Name IF Status IFC State Physical Descriptorswitch control port n/a ACTIVE 12.1.0XTagATM0 up ACTIVE 12.2.0XTagATM1 up ACTIVE 12.3.0<unknown> n/a FAILED-EXT 12.4.0Check that VSI Sessions Are Established
Make sure that every VSI session has been established. A session consists of an exchange of VSI messages between the VSI master (the LSC) and a VSI slave (an entity on the switch). There can be multiple VSI slaves for a switch. On the ATM switch, each port or trunk card assumes the role of a VSI slave.
The following is sample output from the show controllers vsi session command. Session State indicates the status of the session between the master and the slave.
•
•
Router# show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Session StateATM0/0 0 1 0/40 0/1 ESTABLISHEDATM0/0 1 2 0/41 0/2 ESTABLISHEDATM0/0 2 3 0/42 0/3 DISCOVERYATM0/0 3 4 0/43 0/4 RESYNC-STARTINGATM0/0 4 5 0/44 0/5 RESYNC-STOPPINGATM0/0 5 6 0/45 0/6 RESYNC-UNDERWAYATM0/0 6 7 0/46 0/7 UNKNOWNATM0/0 7 8 0/47 0/8 UNKNOWNATM0/0 8 9 0/48 0/9 CLOSINGATM0/0 9 10 0/49 0/10 ESTABLISHEDATM0/0 10 11 0/50 0/11 ESTABLISHEDATM0/0 11 12 0/51 0/12 ESTABLISHEDCheck that the VSI Is Operational
To display information about the switch interface discovered by the MPLS LSC through VSI, use the show controllers vsi descriptor EXEC command. The field called IFC state shows the operational state of the interface, according to the switch. It should be ACTIVE.
Router# show controllers vsi descriptor 12.2.0Phys desc: 12.2.0Log intf: 0x000C0200 (0.12.2.0)Interface: XTagATM0IF status: up IFC state: ACTIVEMin VPI: 1 Maximum cell rate: 10000Max VPI: 259 Available channels: 2000Min VCI: 32 Available cell rate (forward): 10000Max VCI: 65535 Available cell rate (backward): 10000Check XTagATM Interfaces
Ensure that the control VC 0/32 has been created to carry non-IP traffic (LDP) on every XTagATM interface. The columns marked VCD, VPI, and VCI display information for the corresponding private VC on the control interface. The private VC connects the XTagATM VC to the external switch. It is termed private because its VPI and VCI are only used for communication between the MPLS LSC and the switch, and it is different from the VPI and VCI seen on the XTagATM interface and the corresponding switch port.
Router# show XTagatm vcAAL / Control InterfaceInterface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM0 1 0 32 PVC AAL5-SNAP 2 0 33 ACTIVEXTagATM0 2 1 33 TVC AAL5-MUX 4 0 37 ACTIVEXTagATM0 3 1 34 TVC AAL5-MUX 6 0 39 ACTIVETo gather more information about the XTagATM interface, enter the show interface XTagATM command:
Router# show interface XTagATM0XTagATM0 is up, line protocol is upHardware is TAG-Controlled Switch PortInterface is unnumbered. Using address of Loopback0 (10.0.0.17)MTU 4470 bytes, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255Encapsulation ATM Labelswitching, loopback not setEncapsulation(s): AAL5Control interface: ATM1/0, switch port: bpx 10.29 terminating VCs, 16 switch cross-connectsSwitch port traffic:129302 cells input, 127559 cells outputLast input 00:00:04, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/0, 0 drops; input queue 0/75, 0 dropsTerminating traffic:5 minute input rate 1000 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 1 packets/sec61643 packets input, 4571695 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort53799 packets output, 4079127 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffers copied, 0 interrupts, 0 failuresCheck that LDP Is Operational
The show mpls ldp discovery privileged EXEC command displays the interfaces over which the LDP discovery process is running. Each interface should display a status of "xmit/recv", which means the LSC is sending and receiving LDP messages.
Router# show mpls ldp discoveryLocal LDP Identifier:8.1.1.1:0Discovery Sources:Interfaces:Ethernet1/1/3 (ldp): xmit/recvLDP Id: 172.73.0.77:0LDP Id: 172.16.0.44:0LDP Id: 172.22.0.55:0ATM3/0.1 (ldp): xmit/recvLDP Id: 192.168.7.7:2ATM0/0.2 (tdp): xmit/recvTDP Id: 192.168.0.1:1Targeted Hellos:10.1.1.1 -> 172.44.0.33 (ldp): active, xmit/recvLDP Id: 172.44.0.33:010.1.1.1 -> 192.168.0.16 (tdp): passive, xmit/recvTDP Id: 192.168.0.33:0To display the status of LDP sessions, issue the show mpls ldp neighbor privileged EXEC command. The output should show that the LDP sessions are operational and sending and receiving messages.
Router# show mpls ldp neighborPeer LDP Ident: 192.1680.7.7:2; Local LDP Ident 8.1.1.1:1TCP connection: 192.168.7.7.11032 - 8.1.1.1.646State: Oper; Msgs sent/rcvd: 5855/6371; Downstream on demandUp time: 13:15:09LDP discovery sources:ATM3/0.1Peer LDP Ident: 10.1.1.1:0; Local LDP Ident 10.1.1.1:0TCP connection: 10.1.1.1.646 - 10.1.1.1.11006State: Oper; Msgs sent/rcvd: 4/411; DownstreamUp time: 00:00:52LDP discovery sources:Ethernet1/0/0Addresses bound to peer LDP Ident:10.0.0.29 10.1.1.1 109.0.0.199 172.102.1.110.205.0.9Check that MPLS and LDP Are Operational
Make sure that MPLS is globally enabled and that a label distribution protocol is running on the requested interfaces by issuing the show mpls interfaces command.
Router# show mpls interfacesInterface IP Tunnel Operational(...)Serial0/1.1 Yes (ldp) Yes YesSerial0/1.2 Yes Yes NoSerial0/1.3 Yes (ldp) Yes Yes(...)The IP field shows that MPLS IP is configured for an interface. The Label Distribution Protocol (LDP) appears in parentheses to the right of the IP status.
The Tunnel field indicates the capacity of traffic engineering on the interface.
The Operational field shows the status of the LDP. The interfaceSerial0/1.2 is down in the example; therefore, the Operational field shows that LDP is not operational on that interface.
Configuration Example: MPLS LSC
The network topology shown in Figure 3 incorporates two ATM-LSRs in an MPLS network. This topology includes two LSCs (Cisco 7200 routers), two BPX switches, and two Edge LSRs (Cisco 7200 routers).
Figure 3 ATM-LSR Network Configuration Example
Configuration for LSC1
7200 LSC1:
ip cef!mpls atm disable-headend vc!interface loopback0ip address 172.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0mpls atm vpi 2-15mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for BPX1 and BPX2
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
Configuration for LSC2
7200 LSC2:
ip cef!mpls atm disable-headend vc!interface loopback0ip address 172.18.143.22 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0mpls atm vpi 2-15mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR1
LSR1:
ip cef distributed!interface loopback 0ip address 172.22.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.5 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR2
7200 LSR2:
ip cefinterface loopback 0ip address 172.22.172.18 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.9 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguring the Cisco MGX 8850 Switch and RPM-PR as an MPLS LSC
You can configure the Cisco MGX 8850 switch with the Cisco 8850 Router Processor Module (RPM-PR) as an MPLS LSC in an MPLS network.
The RPM-PR provides integrated IP in an ATM platform, enabling services such as integrated Point-to-Point Protocol (PPP), Frame Relay termination, and IP virtual private networks (VPNs) using MPLS technology. It provides Cisco IOS-based multiprotocol routing over ATM, Frame Relay and ATM Interface Layer 3 Termination, Local Server Interconnect over High-Speed LANs, access concentration, and switching between Ethernet LANs and the WAN facilities of the MGX 8850. The RPM-PR runs Cisco IOS software.
The hardware that supports MPLS LSC functionality on the Cisco MGX 8850 switch is described in the following sections.
Cisco MGX 8850 RPM-PR Overview
The RPM-PR is a router module based on an NPE-400 processor, modified to fit into any full-height module slot on a Cisco MGX 8850 32-slot chassis. It connects to the PXM-45 back card, the 4E/B back card, and other service modules through the midplane. The RPM-PR receives power from the midplane and communicates over the midplane with the PXM-45 using IPC over ATM.
The RPM-PR has an integrated ATM interface—a permanently attached ATM port adapter/back card based on the Cisco ATM Deluxe module—and the RPM-PR can support up to two optional back cards to provide LAN connectivity.
The MGX 8850 shelf can be completely populated with 12 RPM-PRs. This allows you to use multiple RPM-PRs to achieve load sharing. Load sharing is achieved by manually distributing connections across multiple embedded RPM-PR router blades.
Note
In a 16-slot configuration, you can add RPM-PRs in any of slots 1 through 6 and 9 through 14. RPM-PRs must not be added to slots 7, 8, 15, or 16 in the MGX 8850 switch.The RPM-PR fits into the Cisco MGX 8850 and MGX 8850 midplane architecture so that the front card provides Cisco IOS router services, and the back cards provide physical network connectivity. The RPM-PR front card also provides ATM connectivity to the Cisco MGX 8850 cellbus at full-duplex OC-3.
Figure 4 shows a Cisco MGX 8850 RPM-PR connected to the Cisco MGX 8850 midplane and the back cards.
Figure 4 PRM-PR Connected to the MGX 8850 Midplane and to Back Cards
The RPM-PR back cards are connected to the front card by a dual PCI bus (see Figure 4). Each RPM-PR card can be equipped with up to two single-height back cards.
Note
Note
MGX 8850 Cellbus
The MGX 8850 cellbus in the MGX 8850 midplane communicates between the RPM-PR, service modules (cellbus slaves) and the PXM-45 (cellbus master) (see Figure 4). Each cellbus is connected to a set of PXM-45 cards. Only one cellbus can be active at a time.
Communication from master to slaves consists of a broadcast to all slaves. The first byte of the cell header contains addressing information. Each slave will monitor data traffic and "pick up" cells that are destined to its slot. Also, a multicast bit allows all slaves to receive a cell simultaneously.
Communication from the slaves to the master is more complicated. Because many slaves might attempt to transmit simultaneously, arbitration among slaves is required. At the start of a given cell period, the master will poll all slaves to see if they have anything to send. By the end of the current cell, the master will grant, or allow, one of the slaves to transmit. Polling and data transmission occur simultaneously.
If two RPM-PRs in adjacent slots share the same cellbus, you need to configure a clock rate of 42 MHz on the PXM-45.
Use the dspcbclk command to display the clock rate:
PXM> dspcbclkCellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 21 1, 2 21, 42CB2 21 3, 4 21, 42CB3 21 5, 6 21, 42CB4 21 17 - 22 21CB5 21 9, 10 21, 42CB6 21 11, 12 21, 42CB7 21 13, 14 21, 42CB8 21 25 - 30 21Use the cnfcbclk cbn 42 command to change the clock rate, where n is the number of the cellbus:
PXM> cnfcbclk cb1 42CellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 42 1, 2 21, 42CB2 21 3, 4 21, 42CB3 21 5, 6 21, 42CB4 21 17 - 22 21CB5 21 9, 10 21, 42CB6 21 11, 12 21, 42CB7 21 13, 14 21, 42CB8 21 25 - 30 21ATM Deluxe Integrated Port Adapter
The ATM deluxe port adapter provides a single ATM interface to the MGX 8850 cellbus interface (CBI). The ATM port adapter is a permanent, internal ATM interface. As such, it has no cabling to install and does not support interface types. It connects internally and directly to the MGX 8850 midplane.
Comparing Cisco 7200 LSC Configuration with Cisco RPM-PR LSC Configuration
This section compares the configuration of the Cisco 7200 LSC controlling Cisco BPX or Cisco IGX switches with the configuration of the Cisco MGX 8850 RPM-PR LSC controlling the Cisco MGX 8850 switch.
Table 2 compares the configuration of switch partitions and partition resources for the Cisco 7200 LSC controlling the Cisco BPX or Cisco IGX switch with the configuration of the Cisco MGX 8850 RPM-PR LSC controlling the Cisco MGX 8850 switch.
Note
Table 3 compares the configuration of interfaces and virtual paths and identifiers of the Cisco 7200 LSC controlling the Cisco BPX or Cisco IGX switch with the configuration of the Cisco MGX 8850 RPM-PR LSC controlling the Cisco MGX 8850 switch.
Comparing Edge Label Switch Router Configurations
This section compares the configuration of the Cisco 7200 routers, and the Cisco 12000 Internet routers as an Edge Label Switch Router (Edge LSR) with the configuration of the Cisco MGX8850 RPM-PR as an Edge LSR.
Table 4 compares the Edge LSR configuration of the Cisco 7200 routers, and the Cisco 12000 Internet routers with the Cisco MGX 8850 RPM-PR when connected to another RPM-PR and when connected to other routers, such as the Cisco 7200 router.
Configuring the Cisco MGX RPM-PR
This section provides the following configuration information for the Cisco MGX RPM-PR:
•
•
Accessing the RPM-PR Command Line Interface
To configure the RPM-PR, you must access the command line interface (CLI) of the RPM-PR.
You can access the RPM-PR CLI using any of the following methods:
•
•
•
Booting the RPM-PR
When the RPM-PR is booted, the boot image must be the first file in the bootflash. (See the section "RPM-PR Bootflash Precautions" to make sure that the first file on the bootflash is a valid boot image.) If the bootflash does not have a valid boot image as a first file, the card may not be able to boot and can result in bootflash corruption. If the bootflash is corrupted, you need to send the card back for an external burn with a valid boot image.
You can reboot the RPM-PR from the PXM by entering the resetcd <card_number> command from the switch CLI, where card_number is the slot number of the RPM-PR that is being rebooted.
Caution
Also, you can reboot the RPM-PR from the RPM-PR using the RPM-PR console port and entering the reload command.
Note
In addition, you can use the regular TFTP boot procedures to boot the RPM-PR. Make sure you have the network connection to the tftpboot server first.
RPM-PR Bootflash Precautions
The RPM-PR bootflash is used to store boot image, and possibly configuration and run-time files. The bootflash stores and accesses data sequentially, and the RPM-PR boot image must be the first file stored to successfully boot the card.
The RPM's boot image, which comes loaded on the bootflash, will work for all RPM IOS images, and therefore, no reason exists to delete or move the factory-installed boot image.
Caution
To avoid unnecessary failures, requiring card servicing, you should:
•
•
•
As long as the boot file remains intact in the first position on the bootflash, the RPM will successfully boot.
Note
Configuring the Cisco MGX 8850 Switch with RPM-PR to Perform Basic LSC Operations
To support MPLS on the Cisco 8850 switch, you need to configure MPLS support on the RPM-PR, the PXM-45, and the AXSM cards.
Figure 5 shows a Cisco MGX 8850 switch with a Cisco MGX 8850 RPM-PR set up to perform basic MPLS LSC functions. The following sections contain configuration steps and examples that show the setup of MPLS support on the Cisco MGX 8850 switch with a Cisco MGX RPM-PR.
Figure 5 Typical Cisco MGX 8850 Configuration to Support MPLS LSC Functions
Note
Configuration Steps: Adding an MPLS Controller to the PXM-45
To add an MPLS controller to the PXM-45 card, follow these steps:
When you use the Cisco MGX 8850 RPM-PR as an MPLS LSC, you also need to add and partition an AXSM NNI port for MPLS.
Configuration Example: Adding and Partitioning an AXSM NNI Port for MPLS
The following example shows adding and then partitioning an NNI port on an AXSM card for MPLS.
cc 1cnfcdsct 4upln 1.1addport 1 1.1 353207 353207 4 2addpart 1 2 8 500000 500000 500000 500000 0 15 32 65535 4000 4000dsppartsWhere:
•
•
addport ifNum bay.line guaranteedRate maxRate sctID ifType [vpiNum]
where:
ifNum = a number between 1 and 60 bay.line = the Line number guaranteedRate = the virtual rate in cells/sec MaxRate = OC48 rate—between 50 and 5651320 (maxRate for OC12 is between 50 and 1412830 maxRate for OC3 is between 50 and 353207 maxRate for T3 is between 50 and 96000 (PLCP), 104268 (ADM) maxRate for E3 is between 50 and 80000) sctID = the Port SCT ID between 0 and 255, for default file use 0 ifType = 1 for uni; 2 for nni; 3 for vnni (optional) vpiNum = between a number 1 and 4095, used for configuring the interface as a virtual trunkThe guaranteedRate argument must equal the maxRate argument.
•
addpart ifNum partID cntlrID egrminbw egrmaxbw ingrminbw ingrmaxbw minVpi maxVpi minVci maxVci minConns maxConns
Where:
ifNum = a number between 1 and 60 partId = the Partition Identifier between 1 and 20 cntrlrID = the Controller Identifier between 1 and 20 egrminbw = the Egress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth egrmaxbw = the Egress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth ingrminbw = the Ingress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth ingrmaxbw = the Ingress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth minVpi = the minimum VPI value, which is a number between 0 and 4095 (0 to 255 for UNI interface) maxVpi = the maximum VPI value, which is number between 0 and 4095 (0 to 255 for UNI interface) minVci = the minimum VCI value, which is a number between 32 and 65535 maxVci = the maximum VCI value, which is a number between 32 and 65535 minConns = the guaranteed number of connections, which is a number between 0 and the maximum number of connections in portgroup maxConns = the maximum number of connections, which is a number between 0 and the maximum number of connections in portgroup•
Configuration Steps: Mapping an AXSM Port to an XtagATM Interface on the LSC
Enter the following commands into the RPM-PR to map AXSM ports to the LSC:
When you use the Cisco MGX 8850 RPM-PR as an MPLS LSC, you also need to create the VNNI port on the AXSM card and add an XtagATM interface on the LSC for the VNNI port.
Configuration Example: Creating the VNNI Port on the AXSM Card
The following example shows the creation of a VNNI port on the AXSM card residing on the PXM-45 shelf.
cc 1cnfcdsct 4upln 1.2addport 12 1.2 353207 353207 4 2 11addpart 12 2 8 250000 250000 250000 250000 11 11 32 65535 10000 10000dsppart 2Where:
•
addport ifNum bay.line guaranteedRate maxRate sctID ifType [vpiNum]
Where:
ifNum = a number between 1 and 60 bay.line = the Line number guaranteedRate = the virtual rate in cells/sec MaxRate = OC48 rate—between 50 and 5651320 (maxRate for OC12 is between 50 and 1412830 maxRate for OC3 is between 50 and 353207 maxRate for T3 is between 50 and 96000 (PLCP), 104268 (ADM) maxRate for E3 is between 50 and 80000) sctID = the Port SCT ID between 0 and 255, for default file use 0 ifType = 1 for uni; 2 for nni; 3 for vnni (optional) vpiNum = VPI between 1 and 4095, used for configuring the interface as a virtual trunkThe guaranteedRate argument must equal the maxRate argument.
•
addpart ifNum partID cntlrID egrminbw egrmaxbw ingrminbw ingrmaxbw minVpi maxVpi minVci maxVci minConns maxConns
Where:
ifNum = a number between 1 and 60 partId = the Partition Identifier between 1 and 20 cntrlrID = the Controller Identifier between 1 and 20 egrminbw = the Egress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth egrmaxbw = the Egress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth ingrminbw = the Ingress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth ingrmaxbw = the Ingress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth minVpi = the minimum VPI value, which is a number between 0 and 4095 (0 to 255 for UNI interface) maxVpi = the maximum VPI value, which is number between 0 and 4095 (0 to 255 for UNI interface) minVci = the minimum VCI value, which is a number between 32 and 65535 maxVci = the maximum VCI value, which is a number between 32 and 65535 minConns = the guaranteed number of connections, which is a number between 0 and the maximum number of connections in portgroup maxConns = the maximum number of connections, which is a number between 0 and the maximum number of connections in portgroup•
Configuration Example: Adding an XtagATM Interface on the LSC for the VNNI Port
The following example shows the addition of an XtagATM interface on the Label Switch Controller (LSC) for the VNNI port.
cc 5enablePassword:config terminalEnter configuration commands, one per line. End with CNTL/Z.!interface XtagATM11212ip unnumbered Loopback0extended-port Switch1 descriptor "1:1.2:12"mpls ipConfiguration Steps: Configuring an RPM as an Edge Label Switch Router
To configure the RPM-PR as an Edge Label Switch Router (Edge LSR) on the MGX 8850 Release 2 shelf, follow these steps:
Configuring an XTag Interface in the LSC Connecting to the RPM-PR Edge LSR
To configure an XTag interface on the LSC connecting to the Cisco MGX 8850 RPM-PR Edge LSR, follow these steps:
MGX ATM MPLS Configuration Examples
This section contains the following sample Cisco MGX 8850 ATM MPLS configurations:
•
Simple Cisco MGX 8850 RPM-PR LSC Network Configuration (VCC Switch Partition)
Figure 6 represents the sample RPM-PR LSC network configuration for a VCC switch partition for the configuration examples that follow.
•
•
Figure 6 Sample RPM-PR LSC Network Configuration
Note
RPM-PR Edge LSR1 Configuration
Following is an example of an RPM-PR Edge LSR(1) configuration. This example uses the switch partition vcc command and therefore, only VCI ranges can be used; you cannot use VPI ranges or VP tunnels. In this example, only one label (tag) switching interface is used, so you can use the default VPI = 0 and the VCI range = 32 to 3808.
Note
ip cef!interface Loopback0ip address 10.9.9.9 255.255.255.255!interface Switch1switch partition vcc 2 8ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface Switch1.1 mplsip unnumbered Loopback0mpls atm vpi 0 vci 33 3000mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
PXM LSC Configuration
The following command adds the LSC controller in the PXM-45. Use the addcontroller <cntrlrtid> <i | o> <cntrlrType> <slot> [cntrlrName] command:
addcontroller 8 i 3 10 LSCWhere:
•
•
•
•
•
RPM-PR LSC Configuration
Following is an example of an RPM-PR LSC configuration. This example uses the switch partition vcc command and therefore, you can use only VPI = 0 and VCI ranges; you cannot use VPI ranges or VP tunnels.
ip cef!mpls atm disable-headend-vc!interface Loopback0ip address 10.20.20.20 255.255.255.255!interface Switch1tag-control-protocol vsi id 8ip route-cache cefswitch partition vcc 2 8ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface XTagATM91ip unnumbered Loopback0extended-port Switch1 descriptor 9.1mpls ip!interface XTagATM111ip unnumbered Loopback0extended-port Switch1 descriptor 11.1mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
•
•
RPM-PR Edge LSR2 Configuration
Following is an example of an RPM-PR Edge LSR(2) configuration. This example uses the switch partition vcc command and therefore, only VPI = 0 and any VCI in the allowed range can be used; you cannot use VPI ranges or VP tunnels.
ip cef!interface Loopback0ip address 10.10.10.10 255.255.255.255!interface Switch1switch partition vcc 2 8ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface Switch1.1 mplsip unnumbered Loopback0mpls atm vpi 0 vci 33 3000mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
Cisco MGX 8850 RPM-PR LSC Network Configuration with Cisco MGX 8850 and Cisco BPX Switches (VCC Switch Partition)
Figure 7 represents a sample RPM-PR LSC network configuration with the MGX 8850 and the BPX switches for the configuration examples that follow.
•
•
•
•
•
Figure 7 Sample RPM-PR LSC Network with Cisco MGX 8850 and Cisco BPX Switches
Note
RPM-PR Edge LSR1 Configuration
Following is an example of a PRM-PR Edge LSR(1) configuration. This example uses the switch partition vcc command and therefore, you can use only VCI ranges; you cannot use VPI ranges or VP tunnels. In this example, only one label (tag) switching interface is used, so you use the default VPI = 0 and the VCI range = 33 to 3808.
Note
In the Cisco MGX 8850 switch, the partition resources of the switch ports are configured at the RPM-PR. In the Cisco BPX or IGX switches, all resources are configured in the switch.ip cef!interface Loopback0ip address 10.9.9.9 255.255.255.255!interface Switch1switch partition vcc 2 8ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface Switch1.1 mplsip unnumbered Loopback0mpls atm vpi 0 vci 33 3000mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
PXM LSC Configuration
The following command adds the LSC controller in the PXM-45. Use the addcontroller <cntrlrtid> <i | 0> <cntrlrType> <slot> [cntrlrName] command:
addcontroller 8 i 3 10 LSCWhere:
•
•
•
•
•
RPM-PR LSC Configuration
Following is an example of an RPM-PR LSC configuration. This example uses the switch partition vcc command and therefore, you can use only VPI = 0 and VCI ranges: you cannot use VPI ranges or VP tunnels.
ip cef!mpls atm disable-headend vc!interface Loopback0ip address 10.20.20.20 255.255.255.255!interface Switch1tag-control-protocol vsi id 8ip route-cache cefswitch partition vcc 2 8controller ID is 8.ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface XTagATM91ip unnumbered Loopback0extended-port Switch1 descriptor 9.1mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
•
•
Mapping a Cisco MGX 8850 AXSM Port to an XtagATM Interface on the Cisco MGX 8850 RPM-PR LSC
The following example shows a sample configuration for mapping an AXSM port to an XtagATM interface on the RPM-PR LSC:
interface XTagATM1111ip unnumbered Loopback0extended-port Switch1 descriptor 1:1.1:1mpls atm vpi 0-15mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
–
–
–
•
AXSM Configuration for the Xtag Interfaces
This configuration example shows adding and partitioning an NNI port on an AXSM card for MPLS. Enter the cc command to change to an AXSM card, then enter the cnfcdsct command to configure the AXSM card service class template (SCT) for PNNI and MPLS:
At the PXM-45 SWITCH.7PXM.a> prompt:
cc 1At the AXM SWITCH.1.AXSM.a> prompt:
cnfcdsct 4upln 1.1addport 1 1.1 353207 353207 4 2addpart 1 2 5 500000 500000 500000 500000 0 15 32 65535 4000 4000dsppartsif part Ctlr egr egr ingr ingr min max min max min maxNum ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn(.0001%)(.0001%)(.0001%)(.0001%)-----------------------------------------------------------------------------1 2 5 500000 500000 500000 500000 0 15 32 65535 4000 4000Where:
•
•
•
addport ifNum bay.line guaranteedRate maxRate sctID ifType [vpiNum]
Where:
ifNum is a number between 1 and 60 bay.line is the format for the Line Number guaranteedRate is the virtual rates in cells/sec maxRate for OC48 = between 50 and 5651320 for OC12 = between 50 and 1412830 for OC3 = between 50 and 353207 for T3 = between 50 and 96000(PLCP),104268(ADM) for E3 = between 50 and 80000 sctID is the Port SCT ID between 0 and 255, for the default file use 0 ifType is 1 for UNI; 2 for NNI; 3 for VNNI vpiNum is between 1 and 4095, used for configuring the interface as virtual trunkThe guaranteedRate argument must equal the maxRate argument.
•
addpart ifNum partID cntlrID egrminbw egrmaxbw ingrminbw ingrmaxbw minVpi maxVpi minVci maxVci minConns maxConns
Where:
ifNum is a number between 1 and 60 partID is the partition identifier between 1 and 20 cntrlrID is the controller identifier between 1 and 20 egrminbw is the Egress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth egrmaxbw is the Egress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth ingrminbw is the Ingress guaranteed percentage of bandwidth in units of 0.0001% of interface bandwidth ingrmaxbw is the Ingress maximum percentage of bandwidth in units of 0.0001% of interface bandwidth minVpi is the minimum VPI value, which is a number between 0 and 4095 (0 to 255 for the UNI interface) maxVpi is the maximum VPI value, which is number between 0 and 4095 (0 to 255 for the UNI interface) minVci is the minimum VCI value, which is a number between 32 and 65535 maxVci is the maximum VCI value, which is a number between 32 and 65535 minConns is the guaranteed number of connections, which is a number between 0 and the maximum number of connections in portgroup (see dspcd for portgroup info) maxConns is the maximum number of connections, which is a number between 0 and the maximum number of connections in portgroup (see dspcd for portgroup info)•
Configuration for BXP
BPX:
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 100000Configuration for Cisco 7200 LSC
7200 LSC:
ip cef!mpls atm disable-headend-vc!interface loopback0ip address 40.40.40.40 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0mpls atm vpi 2-15mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ip!router ospf 100network 40.0.0.0 0.255.255.255 area 0Configuration for Cisco 7200 Edge LSR2
7200 LSR2:
ip cef!interface loopback 0ip address 30.30.30.30 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.5 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ip!router ospf 100network 30.0.0.0 0.255.255.255 area 0PVP-Based ATM MPLS Network Configuration
This section contains sample configurations for the following PVP-based ATM MPLS network configurations:
•
•
Edge LSR to Edge LSR SPVP LC-ATM Interface Configuration
Figure 8 represents a sample permanent virtual path (PVP) configuration with devices in the same Cisco MGX 8850 switch for the ATM MPLS network configuration examples that follow.
•
•
•
Figure 8 PVP Configuration with Devices in Same Cisco MGX 8850 Switch
Note
RPM-PR Edge LSR1 Configuration with VPC Switch Partition
This example uses the switch partition vpc command and therefore, you can use VPI ranges or VP tunnels. If you create a VP tunnel between two routers, you need to configure VPC partitioning and PNNI signaling to bring up the PVP. Then you can run the LC-ATM interface on the PVP.
Note
Following is a sample configuration for the RPM-PR Edge LSR1:
ip cef!interface Loopback0ip address 10.9.9.9 255.255.255.255!interface Switch1atm pvp 2 10000switch partition vpc 1 2ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 1 255vci 0 65535!interface Switch1.2 mplsip unnumbered Loopback0pvc 2/0mpls atm control-vc 2 32mpls atm vpi 2 vci 33-65518mpls ipswitch connection vpc 2 master remote!router ospf 100network 10.0.0.0 0.255.255.255 area 0Where:
•
•
•
•
•
Note
PXM-45 Configuration with VPC Switch Partition
This illustrates the PXM configuration for VPC switch partitioning for a PVP when all devices exist on the same Cisco MGX 8850 switch.
At the PXM-45 SWITCH.7.PXM.a> prompt:
addcontroller 2 i 2 7 PNNIdnpnport 9.2cnfpnportsig 9.2 -univer noneuppnport 9.2dspcon 9.2 2Port Vpi Vci Owner State-------------------------------------------------------------------------Local 9:-1.2:-1 2.0 SLAVE FAILAddress: 47.009181000000000142265fb2.000001074b02.00Node name: SWITCHRemote Routed 0.0 MASTER --Address: 00.000000000000000000000000.000000000000.00Node name:-------------------- Provisioning Parameters --------------------Connection Type: VPC Cast Type: Point-to-PointService Category: UBR Conformance: UBR.1Bearer Class: BCOB-VPLast Fail Cause: N/A Attempts: 0Continuity Check: Disabled Frame Discard: DisabledL-Utils: 0 R-Utils: 0 Max Cost: 0 Routing Cost: 0OAM Segment Ep: Enabled---------- Traffic Parameters ----------Tx PCR: 353208 Rx PCR: 353208Tx CDV: N/A Rx CDV: N/ATx CTD: N/A Rx CTD: N/AWhere:
•
Note
•
•
•
RPM -PR Edge LSR2 Configuration with VPC Switch Partition
This example uses the switch partition vpc command and therefore, you can use VPI ranges or VP tunnels. If you create a VP tunnel between two routers, you need to configure VPC partitioning and PNNI signaling to bring up the PVP. Then you can run the LC-ATM interface on the PVP.
Note
Following is a sample configuration for the RPM-PR Edge LSR2:
ip cef!interface Loopback0ip address 12.12.12.12 255.255.255.255!interface Switch1atm pvp 2 10000switch partition vpc 1 2ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 1 255vci 0 65535!interface Switch1.2 mplsip unnumbered Loopback0pvc 2/0mpls atm control-vc 2 32mpls atm vpi 2 vci 33-65518mpls ipswitch connection vpc 2 master local raddr 47.0091.8100.0000.0001.4226.5fb2.0000.0107.4b02.00 2!!router ospf 100network 12.0.0.0 0.255.255.255 area 0!dspcon 9.2 2Port Vpi Vci Owner State-------------------------------------------------------------------------Local 9:-1.2:-1 2.0 SLAVE OKAddress: 47.009181000000000142265fb2.000001074b02.00Node name: SWITCHRemote Routed 0.0 MASTER OKAddress: 47.009181000000000142265fb2.000001076302.00Node name:-------------------- Provisioning Parameters --------------------Connection Type: VPC Cast Type: Point-to-PointService Category: UBR Conformance: UBR.1Bearer Class: BCOB-VPLast Fail Cause: No Fail Attempts: 0Continuity Check: Disabled Frame Discard: DisabledL-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0OAM Segment Ep: Enabled---------- Traffic Parameters ----------Tx PCR: 353208 Rx PCR: 353208Tx CDV: N/A Rx CDV: N/ATx CTD: N/A Rx CTD: N/AWhere:
•
•
•
PXM-45 Configuration with VPC Switch Partition
This illustrates the PXM configuration for VPC switch partitioning for a PVP when all devices exist on the same Cisco MGX 8850 switch.
At the PXM-45 SWITCH.7.PXM.a> prompt:
dnpnport 12.2cnfpnportsig 12.2 -univer noneuppnport 12.2Where:
•
Note
•
•
Cisco MGX 8850 RPM-PR Connected to an External Device
These sample configurations illustrate a permanent virtual path (PVP) ATM MPLS network with the Cisco MGX 8850 RPM-PR in the Cisco MGX 8850 switch connected to an external device (a Cisco 7200 router, for example). Figure 9 illustrates a PVP configuration with the RPM-PR in the Cisco MGX 8850 switch connected to a Cisco 7200 Edge LSR for the configuration examples that follow.
•
•
•
Figure 9 RPM-PR in Cisco MGX 8850 Switch Connected to Cisco 7200 Edge LSR
Note
These examples use the switch partition vpc command and therefore, you can use VPI ranges or VP tunnels. If you create a VP tunnel between two routers, you need to configure VPC partitioning and PNNI signaling to bring up the PVP. Then you can run the LC-ATM interface on the PVP.
Between Cisco MGX 8850 RPM-PRs, you can use signaled connections, soft permanent virtual circuit (SPVC) and soft permanent virtual path (SPVP) connections, using PNNI. For this type of connection with VPC partitions, you can use any VPI = 1 to 256. You can run MPLS on SPVCs or SPVPs. With MPLS, you can configure the following:
•
•
If you are connecting the Cisco RPM-PR Edge LSR with other routers, such as the Cisco 7200 router, the Cisco 12000 router, or the Cisco BPX or Cisco IGX switch with the Cisco 7200 router, then you need to connect these routers through AXSM or AXSM-E cards. The Cisco 7200, and Cisco 12000 routers, and the Cisco BPX or Cisco IGX switch with the Cisco 7200 router cannot use PNNI signaling. You need to do the following:
•
•
RPM-PR Edge LSR1 Configuration (VPC Switch Partition)
ip cef!interface Loopback0ip address 10.12.12.12 255.255.255.255!interface Switch1atm pvp 12 100000switch partition vpc 1 2ingress-percentage-bandwidth 20 100egress-percentage-bandwidth 20 100vpi 1 100vci 0 65535!interface Switch1.12 mplsip unnumbered Loopback0pvc 12/0ubr 100000mpls atm vp-tunnel 12 vci-range 33-65518mpls ipswitch connection vpc 12 master remote!router ospf 100network 12.0.0.0 0.255.255.255 area 0Where:
•
•
•
PXM-45 Configuration (Switch Partition VPC)
The following examples show PVP-based ATM MPLS network configurations for the AXSM and PXM-45 cards.
At the AXSM SWITCH.11.AXSM.a> prompt:
upln 1.2addport 2 1.2 40000 40000 4 2addpart 2 1 2 235900 235900 235900 235900 1 100 32 65535 10 100At the PXM-45 SWITCH.7.PXM.a> prompt:
addcontroller 2 i 27 PNNIdnport 9.2cnfpnportsig 9.2 -univer noneuppnport 9.2!dspportsifNum Line Admin Oper. Guaranteed Maximum Port SCT Id ifType VPIState State Rate Rate VNNI only)----- ---- ----- ----- ---------- -------- ------------- ------ ------1 1.1 Up Down 353207 353207 5 UNI 02 1.2 Up Up 40000 40000 4 NNI 0At the AXSM SWITCH.11.AXSM.a> prompt:
dspport 2Interface Number : 2Line Number : 1.2Admin State : Up Operational State : UpGuaranteed bandwidth(cells/sec): 40000 Number of partitions: 1Maximum bandwidth(cells/sec) : 40000 Number of SPVC : 0ifType : NNI Number of SPVP : 0Port SCT Id : 4VPI number(VNNI only) : 0 Number of SVC : 0dspport 1Interface Number : 1Line Number : 1.1Admin State : Up Operational State : DownGuaranteed bandwidth(cells/sec): 353207 Number of partitions: 1Maximum bandwidth(cells/sec) : 353207 Number of SPVC : 0ifType : UNI Number of SPVP : 0Port SCT Id : 5VPI number(VNNI only) : 0 Number of SVC : 0dsppart 2 1Interface Number : 2Partition Id : 1 Number of SPVC: 0Controller Id : 2 Number of SPVP: 0egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0egr Maximum bw(.0001percent) : 1000000ing Guaranteed bw(.0001percent): 1000000ing Maximum bw(.0001percent) : 1000000min vpi : 1max vpi : 100min vci : 32max vci : 65535guaranteed connections : 10maximum connections : 100At the PXM-45 SWITCH.7.PXM.a> prompt:
dspconsLocal Port Vpi.Vci remote Port Vpi.Vci State Owner----------------------------+-----------------------------+-------+------9.1 0 2000 12.1 0 2000 OK SLAVELocal Addr: 47.009181000000000142265fb2.000001074b01.00Remote Addr: 47.009181000000000142265fb2.000001076301.0012.1 0 2000 9.1 0 2000 OK MASTERLocal Addr: 47.009181000000000142265fb2.000001076301.00Remote Addr: 47.009181000000000142265fb2.000001074b01.0012.2 12 0 Routed 0 0 FAIL SLAVELocal Addr: 47.009181000000000142265fb2.000001076302.00Remote Addr: 00.000000000000000000000000.000000000000.00At the AXSM SWITCH.11.AXSM.a> prompt:
addcon 2 12 0 8 1 -slave 47009181000000000142265fb200000107630200.12.0 -lpcr8000 -rpcr 8000master endpoint added successfullymaster endpoint id : 47009181000000000142265FB20000010B180200.12.0At the PXM-45 SWITCH.7.PXM.a> prompt:
dspconsLocal Port Vpi.Vci Remote Port Vpi.Vci State Owner----------------------------+-----------------------------+-------+------9.1 0 2000 12.1 0 2000 OK SLAVELocal Addr: 47.009181000000000142265fb2.000001074b01.00Remote Addr: 47.009181000000000142265fb2.000001076301.0012.1 0 2000 9.1 0 2000 OK MASTERLocal Addr: 47.009181000000000142265fb2.000001076301.00Remote Addr: 47.009181000000000142265fb2.000001074b01.0012.2 12 0 11:1.2:2 12 0 OK SLAVELocal Addr: 47.009181000000000142265fb2.000001076302.00Remote Addr: 47.009181000000000142265fb2.0000010b1802.0011:1.2:2 12 0 12.2 12 0 OK MASTERLocal Addr: 47.009181000000000142265fb2.0000010b1802.00Remote Addr: 47.009181000000000142265fb2.000001076302.00master endpoint id : 47009181000000000142265FB20000010B180200.12.0Where:
•
Configuration for Cisco 7200 Edge LSR2
ip cef!interface loopback 0ip address 10.9.9.9 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.9 mplsip unnumbered loopback 0mpls atm vpi 12mpls ip!router ospf 100network 10.0.0.0 0.255.255.255 area 0PXM-45 Configuration with VPC Switch Partition
At the PXM-45 SWITCH.7.PXM.a> prompt:
dnport 11:1.2:2cnfpnportsig 11:1.2:2 -univer noneuppnport 11:1.2:2Where:
•
Simple PVC-Based Packet MPLS Network Configuration
This section contains configuration examples for a simple permanent virtual circuit (PVC) packet MPLS network. For this example all devices are in the same Cisco MGX 8850 switch. Figure 10 illustrates a PVC packet MPLS network with all devices in the same Cisco MGX 8850 switch.
•
•
•
Figure 10 PVC Packet MPLS Network with All Devices in the Same Cisco MGX 8850 Switch
Note
RPM-PR Edge LSR1 Configuration (Switch Partition VCC)
This example uses the switch partition vcc command and therefore, you can use only VCI ranges; you cannot use VPI ranges or VP tunnels. To create and bring up a PVC between two routers, you need to configure VCC partitioning and PNNI signaling. Then you can run packet-based MPLS for the PVC.
Note
ip cef!interface Loopback0ip address 9.9.9.9 255.255.255.255!interface Switch1switch partition vcc 1 2ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 32 3808!interface Switch1.2 point-to-pointip unnumbered Loopback0pvc 0/2000oam-pvc manageencapsulation aal5snap!mpls ipswitch connection vcc 0 2000 master remote!router ospf 100network 9.0.0.0 0.255.255.255 area 0Where:
•
•
•
•
•
PXM-45 Configuration (Switch Partition VCC)
This example shows commands to configure the PXM-45 for a simple PVC packet MPLS network.
At the PXM-45 SWITCH.7.PXM.a> prompt:
addcontroller 2 i 2 7 PNNIdnpnport 9.1cnfpnportsig 9.1 -univer noneuppnport 9.1dspcon 9.2 1Where:
•
•
•
•
•
RPM-PR Edge LSR2 Configuration (Switch Partition VCC)
This example uses the switch partition vcc command and therefore, you can use only VCI ranges; you cannot use VPI ranges or VP tunnels. To create and bring up a PVC between two routers, you need to configure VCC partitioning and PNNI signaling. Then you can run packet-based MPLS for the PVC.
ip cef!interface Loopback0ip address 12.12.12.12 255.255.255.255!interface Switch1switch partition vcc 1 2ingress-percentage-bandwidth 1 100egress-percentage-bandwidth 1 100vpi 0 0vci 1501 3808!interface Switch1.2 point-to-pointip unnumbered Loopback0pvc 0/2000oam-pvc manageencapsulation aal5snap!mpls ipswitch connection vcc 0 2000 master local raddr 47.0091.8100.0000.0001.4226.5fb2.0000.0107.4b01.00 0 2000!router ospf 100network 12.0.0.0 0.255.255.255 area 0Where:
•
•
•
•
PXM-45 Configuration (Switch Partition VCC)
This example shows commands to configure the PXM-45 for a simple PVC packet MPLS network.
At the PXM-45 SWITCH.7.PXM.a> prompt:
addcontroller 2 i 2 7 PNNIdnpnport 12.1cnfpnportsig 12.1 -univer noneuppnport 12.1Where:
•
•
•
Configuring the Cisco 6400 Universal Access Concentrator as an MPLS LSC
You can configure the Cisco 6400 Universal Access Concentrator (UAC) to operate as an MPLS LSC in an MPLS network. The hardware that supports MPLS LSC functionality on the Cisco 6400 UAC is described in the following sections.
Note
Cisco 6400 UAC Architectural Overview
A Cisco 6400 UAC can operate as an MPLS LSC if it incorporates the following components:
•
•
The NRP contains internal ATM interfaces that enable it to be connected to the NSP. However, the NRP cannot access the external ATM interfaces of the Cisco 6400 UAC. Only the NSP can access the external ATM interfaces.
Note
•
Figure 11 shows the components that you can configure to enable the Cisco 6400 UAC to function as an MPLS LSC.
Figure 11 Cisco 6400 UAC Configured as an MPLS LSC
Configuring Permanent Virtual Circuits and Permanent Virtual Paths
The NRP controls the slave ATM switch through the Virtual Switch Interface (VSI) protocol. The VSI protocol operates over a permanent virtual circuit (PVC) that you configure. The PVC is dedicated to the virtual circuits (VCs) that the VSI control channel uses.
For the NRP to control an ATM switch through the VSI, cross-connect the control VCs from the ATM switch through the NSP to the NRP. The ATM switch uses defined control VCs for each BXM slot of the BPX chassis, enabling the LSC to control external XTagATM interfaces through the VSI.
Table 5 defines the PVCs that must be configured on the NSP interface connected to the BPX VSI shelf. These PVCs are cross-connected via the NSP to the NRP VSI master control port, which is running the VSI protocol.
For an NRP that is installed in slot 3 of a Cisco 6400 UAC chassis, the master control port would be ATM3/0/0 on the NSP. As shown in Figure 2, the BPX switch control interface is 12.1. The NSP ATM port connected to interface 12.1 is the ATM interface that is cross-connected to ATM3/0/0. Figure 2 shows that the BXM slaves in BPX slots 6 and 12 are configured as external XTagATM ports. The PVCs that must be cross-connected through the NSP are 0/45 for slot 6 and 0/51 for slot 12, respectively, as outlined in Table 5.
.
Figure 12 shows the functional relationships among the Cisco 6400 UAC hardware components and the permanent virtual paths (PVPs) that you can configure to support MPLS LSC functionality.
Figure 12 Cisco 6400 UAC PVP Configuration for MPLS LSC Functions
All other MPLS LSC functions, such as routing, terminating LVCs, and LDP control VCs (default 0/32), can be accomplished by means of a separate, manually configured PVP (see the upper shaded area in Figure 12). The value of "n" for this manually configured PVP must be the same among all the associated devices (the NRP, the NSP, and the slave ATM switch). Because the NSP uses VP=0 for ATM Forum signaling and the BPX uses VP=1 for autoroute, the value of "n" for this PVP for MPLS LSC functions must be greater than or equal to 2, while not exceeding an upper bound.
Note that some Edge LSRs have ATM interfaces with limited VC space per virtual path (VP). For these interface types, you define several VPs. For example, the Cisco ATM Port Adapter (PA-A1) and the AIP interface are limited to VC range 33 through 1018. To use the full capacity of the ATM interface, configure four consecutive VPs. Make sure the VPs are within the configured range of the BPX.
For internodal BPX connections, it is suggested that you configure VPs 2 through 15; for Edge LSRs, it is suggested that you configure VPs 2 through 5. (See the IOS CLI command mpls atm vpi for examples of how to configure Edge LSRs; see the BPX command "cnfrsrc" described in the Cisco BPX 8600 Series documentation for examples of how to configure BPX service nodes.)
Control VC Setup for MPLS LSC Functions
After you connect the NRP, the NSP, and the slave ATM switch by means of manually configured PVPs (as shown in Figure 12), the NRP can control the slave ATM switch as though it is directly connected to the NRP. The NRP discovers the interfaces of the slave ATM switch and establishes the default control VC to be used in creating MPLS VCs.
The slave ATM switch shown in Figure 12 incorporates two external ATM interfaces (labeled 1 and 2) that are known to the NRP as XTagATM61 and XTagATM122, respectively. On interface 6.1 of the slave ATM switch, VC 0/32 is connected to VC 2/35 by the VSI protocol. On the NRP, VC 2/35 is terminated on interface XTagATM61 and mapped to VC 0/32, also by means of the VSI protocol. This mapping enables the LDP to discover MPLS LSC neighbors by means of the default control VC 0/32 on the physical interface. On interface 12.2 of the slave ATM switch, VC 0/32 is connected to VC 2/83 by the VSI protocol. On the NRP, VC 2/83 is terminated on interface XTagATM122 and mapped to VC 0/32.
Note that the selection of these VCs depends on the availability of VC space. Hence it is not predictable what physical VC will be mapped to the external default control VC 0/32 on the XTagATM interface. The control VC is shown as a PVC on the LSC, as opposed to a LVC, when you execute the IOS CLI command show xtagatm vc.
Configuring the Cisco 6400 UAC to Perform Basic MPLS LSC Operations
Figure 13 shows a Cisco 6400 UAC containing a single NRP that has been configured to perform basic MPLS LSC operations.
Figure 13 Typical Cisco 6400 UAC Configuration to Support MPLS LSC Functions
Note
Note
ip address 172.103.210.5 255.255.255.255
Defining the MPLS Control and IP Routing Paths
In the MPLS LSC topology shown in Figure 13, the devices labeled LSR1 and LSR2 are external to the Cisco 6400 UAC. These devices, with loopback addresses as their respective LDP identifiers, are connected to two separate interfaces labeled 6.1 and 12.2 on the slave ATM switch. Both LSR1 and LSR2 learn about each other's routes from the NRP by means of the data path represented as the thick dashed line in Figure 13. Subsequently, LVCs are established by means of LDP operations to create the data paths between LSR1 and LSR2 through the ATM slave switch.
Both LSR1 and LSR2 learn of the loopback address of the NRP and create a data path (LVCs) from each other that terminates in the NRP. These LVCs, called tailend LVCs, are not shown in Figure 13.
Disabling Edge LVCs
By default, the NRP requests LVCs for the next hop devices (the LSRs shown in Figure 13). The headend LVCs enable the LSC to operate as an edge LSR. Using the LSC as an edge LSR is not supported. Further, the NRP is dedicated to control the slave ATM switch. Therefore, the headend LVCs are not required.
If a Cisco 6400 UAC with an NRP is configured to function as an LSC, disable the edge LSR functionality. An NRP LSC should support transit label switch paths only through the ATM switch using the VSI protocol. To disable the LSC from acting as an edge LSR, see "Disabling the LSC from Acting as an Edge LSR" section.
Configuration Steps: Configuring Cisco 6400 UAC NRP as an MPLS LSC
To configure the Cisco 6400 UAC NRP as an MPLS LSC, perform the following steps:
Configuration Steps: Configuring the Cisco 6400 UAC NSP for MPLS Connectivity to the BPX Switch
To configure the Cisco 6400 UAC NSP for MPLS connectivity to the BXP switch, perform the following steps:
Step 1
Router# show hardware3/0 NRP 00-0000-00 .......Shows the hardware connected to the Cisco 6400 UAC, including the position (3/0) of the NRP in the Cisco 6400 chassis, as shown in the sample output at the left.
Step 2
Router(config)# interface atm3/0/0Specifies the ATM interface for which you want to configure PVCs and PVPs.
Step 3
Configures the PVC for the VSI control channel1 , depending on which of the 14 slots in the Cisco BPX switch is occupied by a Cisco Broadband Switch Module (BXM). If you do not know the BPX slots containing a BXM, configure all 14 PVCs (as shown opposite) to ensure that the NSP functions properly.
However, if you know that Cisco BPX switch slots 10 and 12, for example, contain a BXM, you only need to configure PVCs corresponding to those slots, as shown below:
atm pvc 0 49 interface ATM1/0/0 0 49 atm pvc 0 51 interface ATM1/0/0 0 51Instead of configuring multiple PVCs, as shown opposite in this step, you can configure PVP 0 by deleting all well-known VCs. For example, you can use the command atm manual-well-known-vc delete on both interfaces and then configure PVP 0, as indicated below:
atm pvp 0 interface ATM1/0/0 0Step 4
atm 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 5Configures the PVPs for the LVCs. For XTagATM interfaces, use the VPI range 2 through 5 (by issuing an mpls atm vpi 2-5 command). To use a different VPI range, configure the PVPs accordingly.
1 Do not enable MPLS on this interface.
Configuration Example: Configuring a Cisco 6400 NRP as an LSC
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 14), 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 14 Cisco 6400 UAC NRP Operating as an LSC
Configuration for Cisco 6400 UAC NSP
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 0
Configuration for Cisco 6400 UAC NRP LSC1
ip cef!interface Loopback0ip address 172.18.143.22 255.255.255.255!interface ATM0/0/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13ip unnumbered Loopback0extended-port ATM0/0/0 bpx 1.3mpls atm vpi 2-15mpls ip!interface XTagATM22ip unnumbered Loopback0extended-port ATM0/0/0 bpx 2.2mpls atm vpi 2-5mpls ip!mpls atm disable-headend-vcConfiguration for BPX1 and BPX2
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
Configuration for Cisco 6400 UAC NRP LSC2
ip cef!interface Loopback0ip address 172.103.210.5 255.255.255.255!interface ATM0/0/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13ip unnumbered Loopback0extended-port ATM0/0/0 bpx 1.3mpls atm vpi 2-15mpls ip!interface XTagATM22ip unnumbered Loopback0extended-port ATM0/0/0 bpx 2.2mpls atm vpi 2-5mpls ip!mpls atm disable-headend-vcConfiguration for Edge LSR1
LSR1:
ip cef distributed!interface loopback 0ip address 172.22.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR2
LSR2:
ip cef distributed!interface loopback 0ip address 172.22.172.18 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsunnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguring the Cisco IGX 8400 Switch with a Universal Router Module as an MPLS ATM-LSR
Cisco offers the Universal Router Module (URM) for the Cisco IGX 8400 series switches. The Universal Router Module is a blade for the IGX switch. The IGX switch with the URM supports MPLS and can function as an MPLS ATM-LSR. The following sections explain how to configure the IGX switch with the URM as an MPLS ATM-LSR.
Running the URM on the IGX requires Switch Software 9.3.20 or higher.
VSI
The Virtual Switch Interface (VSI) allows MPLS controllers to control the switch. Each URM in an IGX can be a VSI master or slave. The embedded router in the URM can be configured as a router. The embedded universal switching module (UXM) is always a VSI slave. The embedded router on the URM can act as a master to communicate with the slaves on the IGX and control switch resources.
ATM-LSR
The URM supports MPLS, enabling it to function as an ATM-LSR. The interfaces have the following functions:
•
•
Note
Cisco IGX 8400 Switch with a Universal Router Module Overview
The URM consists of a logically partitioned front card connected to a universal router interface (URI) back card. The front card contains an embedded UXM-E running an Administration firmware image, and an embedded router (based on the Cisco 3660 router) running a Cisco IOS image. The embedded UXM-E and the embedded router connect through a logical internal ATM interface, with capability equivalent to an OC-3 ATM port.
Note
Unlike the Cisco 3660 router, which has one slot for the motherboard and six slots for network modules, the embedded router has three virtual slots with built-in interfaces (see Table 6).
Because the URM front card contains both an embedded UXM-E and an embedded Cisco router, the front card runs two separate software images with two different download procedures. For the embedded UXM-E, the Administration firmware image (Version XAA) is downloaded and saved to the embedded UXM-E Flash memory through SWSW command-line interface (CLI) commands, which are documented in Cisco IGX 8400 Series Installation and Configuration.
The embedded router runs Cisco IOS software. You can download and save the Cisco IOS image using standard Cisco IOS procedures as outlined in any documentation supporting Cisco IOS Release 12.1(5)YA or later (see the Cisco IOS Configuration Fundamentals Configuration Guide).
The embedded UXM-E hardware is based on the UXM-E card for the Cisco IGX series and features 16-MB asynchronous DRAM, 8-MB Flash memory, and 8-KB BRAM. The embedded router hardware is based on the Cisco 3660 modular-access router and features 8-MB boot Flash SIMM, 32-MB Cisco IOS Flash SIMM, and 128-KB NVRAM.
The back card (BC-URI-2FE2VT1 or BC-URI-2FE2VE1) contains an installed voice and WAN interface card (VWIC) with a generic dual-port T1 or E1 digital voice interface.
URM Connections
The Cisco IGX backplane is a cell bus composed of four parallel data buses that transmit up to four cells at a time. This bus bandwidth is organized into allocated units called universal bandwidth units (UBUs), each capable of transmitting 4000 cells per second or 2000 fast packets per second. The Cisco IGX has a total of 584 UBUs, giving the Cisco IGX the capacity to transmit about 2 million cells or 1 million fast packets per second.
Each URM receives a default bandwidth from the Cisco IGX at power on. You can configure this default bandwidth by using the SWSW CLI cnfbusbw command. For more information on this and other SWSW commands, refer to the Cisco WAN Switching Command Reference.
Note
Connections terminating on the URM can be virtual path connections (VPCs) or virtual channel connections (VCCs).
The Cisco IOS router in the URM connects to Cisco IGX WAN through an internal ATM interface on the URM card. Because the URM supports voice connections using either standard VoIP or Cisco proprietary VoATM configurations (using ATM PVCs on the internal ATM interface), the remote end of these connections is either an ATM PVC endpoint or a Frame Relay PVC endpoint.
Note
Configuration Example: Configuring a Cisco IGX 8400 Switch with a URM as an MPLS ATM-LSR
The following example configures MPLS on ATM-LSRs and Edge LSRs. The examples use the appropriate ATM interfaces that are directly connected to IGX.
Figure 15 Cisco IGX 8400 Switch with a Universal Router Module
Configuration for Edge LSR 1
LSR1:
ip cef distributedinterface loopback 0ip address 172.22.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for ATM-LSR1
URM LSC1:
ip cefmpls atm disable-headend-vc!interface loopback0ip address 2.2.2.2 255.255.255.0!interface atm0/0no shuttag-control-protocol vsi id 1ip route-cache cef!interface XTagATM132extended-port atm0/0 igx 1.3.2ip unnumbered loopback0mpls atm vp-tunnel 2mpls ip!interface XTagATM22extended-port atm0/0 igx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for ATM-LSR2
URM LSC2
ip cefmpls atm disable-headend-vcinterface loopback0ip address 3.3.3.3 255.255.255.255!interface atm0/0no shuttag-control-protocol vsi id 2ip route-cache cef!interface XTagATM132ip unnumbered loopback0extended-port atm0/0 igx 1.3.2mpls atm vp-tunnel 2mpls ipinterface XTagATM22ip unnumbered loopback0extended-port atm0/0 igx 2.2mpls atm vpi 2-5mpls ipConfiguration for IGX1 and IGX2
IGX1 and IGX2:
uptrk 1.1addshelf 1.1 v 1 1cnfrsrc 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 1.3.2cnftrk 1.3.2 100000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 2cnfrsrc 1.3.2 256 252207 y 1 e 512 6144 2 2 26000 100000uptrk 2.2cnfrsrc 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Note
Configuration for Edge LSR2
7200 LSR2:
ip cefinterface loopback 0ip address 172.22.172.18 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipDisabling the LSC from Acting as an Edge LSR
Using the MPLS LSC as a label edge device is not supported. Using the MPLS LSC as a label edge device introduces unnecessary complexity to the configuration. See the command mpls atm disable-headend-vc to disable edge LSR functionality on the LSC.
Disabling the LSC from acting as an edge LSR causes the LSC to stop initiating LSPs to any destination. Therefore, the number of LVCs used in the network is reduced. The LSC can still terminate tailend LVCs, if required.
You can prevent the terminating tailend LVCs from being created between the edge LSRs and LSCs. This helps prevent the unnecessary use of LVC resources in a slave ATM switch. You use the mpls request-labels for command with an access list to disable the creation of the LSPs. You can create an access list at an edge LSR to restrict the destinations for which a downstream-on-demand request is issued.
With downstream on demand, LVCs are depleted with the addition of each new node. These commands save resources by disabling the LSC from setting up unwanted LSPs. The absence of those LSPs allows traffic to follow the same path as control traffic.
The following example uses the mpls atm disable-headend-vc command to disable the LSC from functioning as an edge LSR. The following line is added to the LSC configuration:
mpls atm disable-headend-vc
Note
Feature 1: Creating Virtual Trunks
Virtual trunks provide connectivity for Cisco WAN MPLS switches through an ATM cloud, as shown in Figure 16. Because several virtual trunks can be configured across a given private/public physical trunk, virtual trunks provide a cost-effective means of connecting across an entire ATM network.
The ATM equipment in the cloud must support virtual path switching and transmission of ATM cells based solely on the VPI in the ATM cell header. The virtual path identifier (VPI) is provided by the ATM cloud administrator (that is, by the service provider).
Typical ATM Hybrid Network with Virtual Trunks
Figure 16 shows three Cisco WAN MPLS switching networks, each connected to an ATM network by a physical line. The ATM network links all three of these subnetworks to every other subnetwork with a fully meshed network of virtual trunks. In this example, each physical interface is configured with two virtual trunks.
Figure 16 Typical ATM Hybrid Network Using Virtual Trunks
A virtual trunk number (slot number.port number.trunk number) differentiates the virtual trunks found within a physical trunk port. In Figure 17, three virtual trunks (4.1.1, 4.1.2, and 4.1.3) are configured on a physical trunk that connects to the port 4.1 interface of a BXM.
Figure 17 Virtual Trunks Configured on a Physical Trunk
These virtual trunks are mapped to the XTagATM interfaces on the LSC. On the XTagATM interface, you configure the respective VPI value using the command mpls atm vp-tunnel vpi. This VPI should match the VPI in the ATM network. The label virtual circuits (LVCs) are generated inside this VP, and this VP carries the LVCs and their traffic across the network.
Virtual Trunking Benefits
Virtual trunks provide the following benefits:
•
•
Virtual Trunking Restrictions
Virtual Trunk Bandwidth—The total bandwidth of all the virtual trunks on one port cannot exceed the maximum bandwidth of the port. Trunk loading (units of load) is maintained per virtual trunk, but the cumulative loading of all virtual trunks on a port is restricted by the transmit and receive rates for the port.
Maximum Virtual Trunks—The maximum number of virtual trunks that can be configured per card equals the number of virtual interfaces (VIs) on the BPX/IGX switch.
•
•
Configuration Example: Configuring Virtual Trunks with Cisco 7200 LSCs
The network topology shown in Figure 18 incorporates two ATM-LSRs using virtual trunking to create an MPLS network through a private ATM Network. This topology includes:
•
•
•
Note
extended-port atm1/0 descriptor 0.x.x.0
tag-control-protocol vsi slaves 32 id x
ip route-cache cefFigure 18 ATM-LSR Virtual Trunking through ATM Network
Based on Figure 19, the following configuration examples are provided:
•
•
•
Configuration for LSC1 Implementing Virtual Trunking
7200 LSC1:
ip cef!interface loopback0ip address 172.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM132extended-port ATM3/0 bpx 1.3.2ip unnumbered loopback0mpls atm vp-tunnel 2mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for BPX1 and BPX2
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.3.2cnftrk 1.3.2 100000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 2cnfrsrc 1.3.2 256 252207 y 1 e 512 6144 2 2 26000 100000uptrk 2.2cnfrsrc 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Note
Configuration for LSC2 Implementing Virtual Trunking
7200 LSC2:
ip cef!interface loopback0ip address 172.18.143.22 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM132extended-port ATM3/0 bpx 1.3.2ip unnumbered loopback0mpls atm vp-tunnel 2mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR1
LSR1:
ip cef distributedinterface loopback 0ip address 172.22.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR2
7200 LSR2:
ip cefinterface loopback 0ip address 172.22.172.18 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration Example: Configuring Virtual Trunking on Cisco 6400 NRP LSCs
The network topology shown in Figure 19 incorporates two ATM-LSRs using virtual trunking to create an MPLS network through a private ATM Network. This topology includes:
•
•
•
Figure 19 Cisco 6400 NRP Operating as LSC Implementing Virtual Trunking
Configuration for Cisco 6400 UAC NSP
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 0
Configuration for Cisco 6400 UAC NRP LSC1 Implementing Virtual Trunking
ip cef!interface Loopback0ip address 172.18.143.22 255.255.255.255!interface ATM0/0/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM132ip unnumbered Loopback0extended-port ATM0/0/0 bpx 1.3.2mpls atm vp-tunnel 2mpls ip!interface XTagATM22ip unnumbered Loopback0extended-port ATM0/0/0 bpx 2.2mpls atm vpi 2-5mpls ip!mpls atm disable-headend-vcConfiguration for BPX1 and BPX2
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.3.2cnftrk 1.3.2 100000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 2cnfrsrc 1.3.2 256 252207 y 1 e 512 6144 2 2 26000 100000uptrk 2.2cnfrsrc 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Note
Configuration for 6400 UAC NRP LSC2 Implementing Virtual Trunking
ip cef!interface Loopback0ip address 172.103.210.5 255.255.255.255!!interface ATM0/0/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM132ip unnumbered Loopback0extended-port ATM0/0/0 bpx 1.3.2mpls atm vp-tunnel 2mpls ip!interface XTagATM22ip unnumbered Loopback0extended-port ATM0/0/0 bpx 2.2mpls atm vpi 2-5mpls ip!mpls atm disable-headend-vcConfiguration for Edge LSR1
LSR1:
ip cef distributed!interface loopback 0ip address 172.22.132.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR2
LSR2:
ip cef distributed!interface loopback 0ip address 172.22.172.18 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsunnumbered loopback 0mpls atm vpi 2-5mpls ipFeature 2: Using LSC Redundancy
LSC redundancy allows you to create a highly reliable IP network, one whose reliability is nearly equivalent to that provided by hot standby routing. Instead of using hot standby routing processes to create redundancy, this method uses a combination of LSCs, the Virtual Switch Interface (VSI), and IP routing paths with the same cost path for hot redundancy, or different costs for warm redundancy. The VSI allows multiple control planes (MPLS, PNNI, and voice) to control the same switch. Each control plane controls a different partition of the switch.
In the LSC redundancy model, two independent LSCs control the different partitions of the switch. Thus, two separate MPLS control planes set up connections on different partitions of the same switch. This is where LSC redundancy differs from hot standby redundancy. The LSCs do not need copies of each other's internal state to create redundancy. The LSCs control the partitions of the switch independently.
A single IP network consists of switches with one LSC (or a hot standby pair of LSCs) and MPLS edge label switch routers (LSRs).
If you change that network configuration by assigning two LSCs per switch, you form two separate MPLS control planes for the network. You logically create two independent parallel IP subnetworks linked at the edge.
If the two LSCs on each switch are assigned identical shares of the switch's resources and links, the two subnetworks are identical. You have two identical parallel IP subnetworks on virtually the same equipment, which would otherwise support only one network.
For example, Figure 20 shows a network of switches that each have two LSCs. MPLS Edge LSRs are located at the edge of the network, to form a single IP network. The LSCs on each switch have identical shares of the switch's resources and links, which makes the networks identical. In other words, there are two identical parallel IP subnetworks.
Figure 20 LSC Redundancy Model
Part of the redundancy model includes Edge LSRs, which link the two networks at the edge.
If the network uses Open Shortest Path First (OSPF) or a similar IP routing protocol with an equal cost on each path, then there are at least two equally viable paths from every Edge LSR to every other Edge LSR. The OSPF equal cost multipath distributes traffic evenly on both paths. Therefore, MPLS sets up two identical sets of connections for the two MPLS control planes. IP traffic travels equally across the two sets of connections.
Note
With the LSC redundancy model, if one LSC on a switch fails, IP traffic uses the other path, without having to establish new links. LSC redundancy does not require the network to set up new connections when a controller fails. Because the connections to the other paths have already been established, the interruption to the traffic flow is negligible. The LSC redundancy model is as reliable as networks that use hot standby controllers. LSC redundancy requires hardware like that used by hot standby controllers. However, the controllers act independently, rather than in hot standby mode. For LSC redundancy to work, the hardware must have connection capacity for doubled-up connections.
If an LSC fails and LSC redundancy is not present, IP traffic halts until other switches break their present connections and reroute traffic around the failed controller. The stopped IP traffic results in undesirable unreliability.
Hot LSC Redundancy
Hot redundancy provides near-instant failover to the other path when an LSC fails. When you set up hot redundancy, both LSCs are active and have the same routing costs on both paths. To ensure that the routing costs are the same, run the same routing protocols on the redundant LSCs.
In hot redundancy, the LSCs run parallel and independent Label Distribution Protocols (LDPs). At the Edge LSRs, when the LDP has multiple routes for the same destination, it requests multiple labels. It also requests multiple labels when it needs to support class of service (CoS). When one LSC fails, the labels distributed by that LSC are removed.
To achieve hot redundancy, you can implement the following redundant components:
•
•
•
•
•
Figure 21 shows one example of how hot LSC redundancy can be implemented.
Figure 21 Hot LSC Redundancy
Warm LSC Redundancy
To achieve warm redundancy, you need only redundant LSCs. You do not necessarily need to run the same routing protocols or distribution protocols on the LSCs.
Note
If you run the same routing protocols, you specify a higher cost for the interfaces on the backup LSC. This causes the data to use only the lower-cost path. This also saves resources on the ATM switch, because the Edge LSR requests LVCs only through the lower-cost LSC. When the primary LSC fails, the Edge LSR uses the backup LSC and creates new paths to the destination. Creating new paths requires reroute time and LDP negotiation time.
Figure 22 shows one example of how warm LSC redundancy can be implemented.
Figure 22 Warm LSC Redundancy
Differences Between Hot and Warm LSC Redundancy
Virtually any configuration of switches and LSCs that provides hot redundancy can also provide warm redundancy. You can also switch from warm to hot redundancy with little or no change to the links, switch configurations, or partitions.
Hot and warm redundancy differ in the following ways:
•
•
General Redundancy Operational Modes
The LSC redundancy model allows you to use the following four operational models. Most other redundancy models cannot accommodate all of these redundancy models.
•
•
•
•
How LSC Redundancy Differs from Router and Switch Redundancy
In traditional IP router networks, network managers ensure reliability by creating multiple paths through the network from every source to every destination. If a device or link on one path fails, IP traffic uses an alternate path to reach its destination.
LSC Redundancy
Connecting two independent LSCs to each switch by the Virtual Switch Interface (VSI) creates two identical subnetworks. Multipath IP routing uses both subnetworks equally. Thus, both subnetworks have identical connections. If a controller in one subnetwork fails, the multipath IP routing diverts traffic to the other path. Because the connections already exist in the alternate path, the reroute time is very fast. The LSC redundancy model matches the reliability of networks with hot standby controllers, without the difficulty of implementing hot standby redundancy.
Router Redundancy
Because routers do not need to establish a virtual circuit to transfer data, they are inherently connectionless. When a router discovers a failed device or link, it requires approximately less than a second to reroute traffic from one path to another.
Routers can incorporate a warm or hot standby routing process to increase reliability. The routing processes share information about the routes to direct different streams of IP traffic. They do not need to keep or share connection information. Routers can also include redundant switch fabrics, backplanes, power supplies, and other components to decrease the chances of node failures.
ATM, Frame Relay, and Circuit Switch Redundancy
Circuit switch, ATM, and Frame Relay networks transfer data by establishing circuits or virtual circuits. To ensure the transfer of data in switches, network managers incorporate redundant switch components. If any component fails, a spare component takes over. Switches can have redundant line cards, power supplies, fans, backplanes, switch fabrics, line cards, and control cards.
•
•
•
A software application usually monitors the state of the switches and their components. If a problem arises, the software sets an alarm to bring attention to the faulty component.
The redundant switch hardware and software are required, because switches take some time to reroute traffic when a failure occurs. Switches can have connection routing software, such as Cisco automatic connection routing, PNNI, or MPLS. However, rerouting the connections in a switch takes much more time than rerouting traffic in a router network. Rerouting connections in a switch requires calculating routes and reprogramming some hardware for each connection. In router networks, large aggregates of traffic can be rerouted simultaneously, with little or no hardware programming. Therefore, router networks can reroute traffic more quickly and easily than connection-oriented networks. Router networks rely on rerouting techniques to ensure reliability. Connection-oriented networks use rerouting only as a last resort.
General Hot/Warm Standby Redundancy in Switches
Network managers can install redundant copies of the connection routing software for ATM and Frame Relay switches on a redundant pair of control processors.
With hot standby redundancy, the active process sends its state to the spare process to keep the spare process up to date in case it needs to take over. The active process sends the state information to the spare process or writes the state to a disk, where both processes can access the information. In either case, the state information is shared between controllers. Because the state of the network routing tables changes frequently, the software must perform much work to maintain consistent routing states between redundant pairs of controllers.
With warm standby redundancy, the state information is not shared between the active and spare processes. If a failure occurs, the spare process resets all of the connections and re-establishes them. Reliability decreases when the spare resets the connections. The chance of losing data increases.
LSC Redundancy Benefits
By implementing the LSC redundancy model, you eliminate the single point of failure between the LSC and the ATM switch it controls. If one LSC fails, the other LSC takes over and routes the data on the other path. The following sections explain the other benefits of LSC redundancy.
LSC Redundancy Does Not Use Shared States or Databases
In the LSC redundancy model, the LSCs do not share states or databases, which increases reliability. Sometimes, when states and databases are shared, an error in the state or database information can cause both controllers to fail simultaneously.
Also, new software features and enhancements do not affect LSC redundancy. Because the LSCs do not share states or database information, you do not have to worry about ensuring redundancy during every step of the update.
LSC Redundancy Allows Different Software Versions
The LSCs work independently and there is no interaction between the controllers. They do not share the controller's state or database, as other redundancy models require. Therefore, you can run different versions of the IOS software on the LSCs, which provides the following advantages:
•
•
Note
LSC Redundancy Allows You to Use Different Router Models
You can use different models of routers in this LSC redundancy model. Using different hardware in the redundancy model reduces the chance that a hardware fault would interrupt network traffic.
LSC Redundancy Allows You to Switch from Hot to Warm Redundancy on the Fly
You can implement hot or warm redundancy and switch from one model to the other. Hot redundancy can use redundant physical interfaces, slave ATM switches with Y redundancy, and redundant LSCs. This enables parallel paths and near-instant failover. If your resources are limited, you can implement warm redundancy, which uses only redundant LSCs. When one controller fails, the backup controller requires some reroute time. As your network grows, you can switch from hot to warm redundancy and back, without bringing down the entire network.
Other redundancy models require complex hardware and software configurations, which are difficult to alter when you change the network configuration. You must manually change the connection routing software from hot standby mode to warm standby mode.
LSC Redundancy Provides an Easy Migration from Standalone LSCs to Redundant LSCs
You can migrate from a standalone LSC to a redundant LSC and back again without affecting network operations. Because the LSCs work independently, you can add a redundant LSC without interrupting the other LSC.
LSC Redundancy Allows Configuration Changes in a Live Network
The hot LSC redundancy model provides two parallel, independent networks. Therefore, you can disable one LSC without affecting the other LSC. This feature has the following benefits:
•
•
LSC Redundancy Provides Fast Reroute in IP+ATM Networks
The hot LSC redundancy model offers redundant paths for every destination. Therefore, reroute recovery is very fast. Other rerouting processes in IP+ATM networks require many steps and take more time.
In normal IP+ATM networks, the reroute process consists of the following steps:
•
•
•
•
After this reroute process, the new path is ready to transfer data. Rerouting data using this process takes time.
The hot LSC redundancy method allows you to quickly reroute data in IP+ATM networks without using the normal reroute process. When you incorporate hot LSC redundancy, you create parallel paths. Every destination has at least one alternative path. If a device or link along the path fails, the data uses the other path to reach its destination. The hot LSC redundancy model provides the fastest reroute recovery time for IP+ATM networks.
LSC Redundancy Restrictions
Hot LSC Redundancy Restrictions
The following list explains the items you need to consider when implementing hot LSC redundancy:
•
•
•
•
Warm LSC Redundancy Restrictions
The following list explains the items you need to consider when implementing warm LSC redundancy:
•
•
•
Note
Configuring LSC Redundancy
To make an LSC redundant, you can partition the resources of the slave ATM switch, implement a parallel VSI model, assign redundant LSCs to each switch, and create redundant LSRs. The following sections explain each of these steps.
Partitioning the Resources of the ATM Switch
In the LSC redundancy model, two LSCs control different partitions of the ATM switch. When you partition the ATM switch for LSC redundancy, use the following guidelines:
•
•
–
–
•
•
See the documentation on the Cisco BPX 8600 series or Cisco IGX 8400 series switches for more information about configuring the slave ATM switch.
Implementing the Parallel VSI Model
The parallel VSI model means that the physical interfaces on the ATM switch are shared by more than one LSC. For instance, LSC1 maps VSI slave interfaces 1 to N to the ATM switch's physical interfaces 1 to N. LSC2 maps VSI slave interfaces to the ATM switch's physical interfaces 1 to N. LSC1 and LSC2 share the same physical interfaces on the ATM switch. With this mapping, you achieve fully meshed independent masters.
Figure 23 shows four ATM physical interfaces mapped as four XTagATM interfaces at LSC1 and LSC2. Each LSC is not aware that the other LSC is mapped to the same interfaces. Both LSCs are active all the time. The ATM switch runs the same VSI protocol on both partitions.
Figure 23 XTagATM Interfaces
Adding Interface Redundancy
To ensure reliability throughout the LSC redundant network, you can also implement:
•
•
Figure 24 Interface Redundancy
Configuration Example: Configuring LSC Hot Redundancy
The network topology shown in Figure 25 incorporates two ATM-LSRs in an MPLS network. This topology includes two LSCs on each BPX node and four Edge LSRs.
Figure 25 ATM-LSR Network Configuration Example
The following configuration examples show the label-switching configuration for both standard downstream-on-demand interfaces and downstream-on-demand over a VP-tunnel. The difference between these two types of configurations is:
•
•
The following configuration examples are provided in this section.
Note
extended-port atm1/0 descriptor 0.x.x.0
tag-control-protocol vsi slaves 32 id x
ip route-cache cef
Note
Configuration for LSC 1A
7200 LSC 1A:
ip cef!mpls atm disable-headend-vc!interface loopback0ip address 172.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi id 1ip route-cache cef!interface XTagATM12ip unnumbered loopback0extended-port ATM3/0 bpx 1.2mpls atm vpi 2-5mpls ip!interface XTagATM15ip unnumbered loopback0extended-port ATM3/0 bpx 1.5mpls atm vpi 2-15mpls ip!interface XTagATM1612ip unnumbered loopback0extended-port ATM3/0 bpx 1.6.12mpls atm vp-tunnel 12mpls ip!interface XTagATM2612ip unnumbered loopback0extended-port ATM3/0 bpx 2.6.12mpls atm vp-tunnel 12mpls ipConfiguration for LSC 1B
7200 LSC 1B:
ip cef!mpls atm disable-headend-vc!!interface loopback0ip address 172.103.210.6 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi id 2ip route-cache cef!interface XTagATM22ip unnumbered loopback0extended-port ATM3/0 bpx 2.2mpls atm vpi 2-5mpls ip!interface XTagATM25ip unnumbered loopback0extended-port ATM3/0 bpx 2.5mpls atm vpi 2-15mpls ip!interface XTagATM1622ip unnumbered loopback0extended-port ATM3/0 bpx 1.6.22mpls atm vp-tunnel 22mpls ip!interface XTagATM2622ip unnumbered loopback0extended-port ATM3/0 bpx 2.6.22mpls atm vp-tunnel 22mpls ipConfiguration for LSC 2A
7200 LSC 2A:
ip cef!mpls atm disable-headend-vc!interface loopback0ip address 172.103.210.7 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi id 1ip route-cache cef!interface XTagATM12ip unnumbered loopback0extended-port ATM3/0 bpx 1.2mpls atm vpi 2-5mpls ip!interface XTagATM15ip unnumbered loopback0extended-port ATM3/0 bpx 1.5mpls atm vpi 2-15mpls ip!interface XTagATM1612ip unnumbered loopback0extended-port ATM3/0 bpx 1.6.12mpls atm vp-tunnel 12mpls ip!interface XTagATM2612ip unnumbered loopback0extended-port ATM3/0 bpx 2.6.12mpls atm vp-tunnel 12mpls ipConfiguration for LSC 2B
7200 LSC 2B:
ip cef!mpls atm disable-headend-vc!interface loopback0ip address 172.103.210.8 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsi id 2ip route-cache cef!interface XTagATM22ip unnumbered loopback0extended-port ATM3/0 bpx 2.2mpls atm vpi 2-5mpls ip!interface XTagATM25ip unnumbered loopback0extended-port ATM3/0 bpx 2.5mpls atm vpi 2-15mpls ip!interface XTagATM1622ip unnumbered loopback0extended-port ATM3/0 bpx 1.6.22mpls atm vp-tunnel 22mpls ip!interface XTagATM2622ip unnumbered loopback0extended-port ATM3/0 bpx 2.6.22mpls atm vp-tunnel 22mpls ipConfiguration for BPX-1 and BPX-2
BPX-1 and BPX-2:
uptrk 1.1addshelf 1.1 vsi 1 1cnfrsrc 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000upln 1.2upport 1.2cnfrsrc 1.2 256 252207 y 1 e 512 6144 2 5 26000 100000uptrk 1.5cnfrsrc 1.5 256 252207 y 1 e 512 6144 2 15 26000 100000uptrk 1.6.12cnftrk 1.6.12 110000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 12cnfrsrc 1.6.12 256 252207 y 1 e 512 6144 12 12 26000 100000uptrk 1.6.22cnftrk 1.6.22 110000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 22cnfrsrc 1.6.22 256 252207 y 2 e 512 6144 22 22 26000 100000uptrk 2.1addshelf 2.1 vsi 2 2cnfrsrc 2.1 256 252207 y 2 e 512 6144 2 15 26000 100000upln 2.2upport 2.2cnfrsrc 2.2 256 252207 y 2 e 512 4096 2 5 26000 100000uptrk 2.5cnfrsrc 2.5 256 252207 y 2 e 512 6144 2 15 26000 100000uptrk 2.6.12cnftrk 2.6.12 110000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 12cnfrsrc 2.6.12 256 252207 y 1 e 512 6144 12 12 26000 100000uptrk 2.6.22cnftrk 2.6.22 110000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 N N Y Y Y CBR 22cnfrsrc 2.6.22 256 252207 y 2 e 512 6144 22 22 26000 100000
Note
Configuration for Edge LSR 7200-1
7200-1 Edge LSR:
ip cef!interface loopback0ip address 172.103.210.1 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.12 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ip!interface ATM3/0no ip addressinterface ATM3/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR-1
Edge LSR:
ip cef distributed!interface loopback0ip address 172.103.210.2 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.1612 mplsip unnumbered loopback0mpls atm vp-tunnel 12mpls ip!interface ATM2/0/0.1622 mplsip unnumbered loopback0mpls atm vp-tunnel 22mpls ipConfiguration for Edge LSR-2
Edge LSR:
ip cef distributed!interface loopback0ip address 172.103.210.3 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.12 mplsip unnumbered loopback0mpls atm vpi 2-5mpls ip!!interface ATM3/0/0no ip address!interface ATM3/0/0.22 mplsip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR 7200-2
7200-2 Edge LSR:
ip cef!interface loopback0ip address 172.103.210.4 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.1612 mplsip unnumbered loopback0mpls atm vp-tunnel 12mpls ip!interface ATM2/0.1622 mplsip unnumbered loopback0mpls atm vp-tunnel 22mpls ipConfiguration Example: Configuring LSC Warm Standby Redundancy
You can implement the configuration of LSC warm standby redundancy by configuring the redundant link for either a higher routing cost than the primary link or configuring a bandwidth allocation that is less desirable. You need to perform this only at the Edge LSR nodes, because the LSCs are configured to disable the creation of headend VCs, which reduces the LVC overhead.
Configuration Example: Configuring an Interface Using Two VSI Partitions
A special case may arise where a network topology can only support a neighbor relationship between peers using a single trunk or line interface. To configure the network, use the following procedure:
Step 1
uptrk 2.8cnfrsrc 2.8 256 252207 y 1 e 512 6144 2 15 26000 100000cnfrsrc 2.8 256 252207 y 2 e 512 6144 16 29 26000 100000Thus partition 1 will create LVCs using VPIs 2-15 and partition 2 will create LVCs using VPIs 16-29.
Step 2
mpls atm control-vc <vpi> <vci>Therefore, LSC 1 XTagATM28 can use the default control-vc 0/32 (but it is suggested that you use 2/32 to reduce configuration confusion) and the LSC 2 XTagATM28 should use control-vc 16/32.
Note
extended-port atm1/0 descriptor 0.x.x.0
tag-control-protocol tag-control-protocol vsi slaves 32 id x
ip route-cache cefThe following example shows the configuration steps:
LSC1:
interface XTagATM2801ip unnumbered loopback0extended-port ATM3/0 bpx 2.8mpls atm vpi 2-15mpls atm control-vc 2 32mpls ipLSC2:
interface XTagATM2802ip unnumbered loopback0extended-port ATM3/0 bpx 2.8mpls atm vpi 16-29mpls atm control-vc 16 32mpls ipFeature 3: Reducing the Number of Label Switch Paths Created in an MPLS Network
You can reduce the number of LSPs created in an MPLS networkby Disabling LSPs from being created from a edge LSR or LSC to a destination IP address. Use the mpls request-labels for command. Specify the destination IP addresses that you want to disable from creating LSPs. This command allows you to permit creation of some LSPs, while preventing the creation of others.
Using an Access List to Disable Creation of LSPs to Destination IP Addresses
You can prevent LSPs from being created between Edge LSRs and LSCs. This helps prevent the unnecessary use of LVC resources in a slave ATM switch. You use the mpls request-labels for command with an access list to disable the creation of the LSPs.
Some LSPs are often unnecessary between some Edge LSRs in an MPLS network. Every time a new destination is created, LSPs are created from all Edge LSRs in the MPLS network to the new destination. You can create an access list at an Edge LSR or LSC to restrict the destinations for which a downstream-on-demand request is issued.
For example, Figure 26 is an MPLS ATM network that consists of the following elements:
•
•
•
•
Use mpls request-labels for commands to accomplish the following tasks:
•
•
Performing these tasks reduces the number of LSPs in the MPLS ATM cloud, which reduces the VC usage in the cloud.
Figure 26 Sample MPLS ATM Network
Note
The following examples of the mpls request-labels for command use Figure 27 as a basis. The examples show different ways to disable the creation of LSPs from the LSC to the Edge LSR, and from the Edge LSRs to the LSC.
Figure 27 Sample Configuration for mpls request-labels for Command
Using a Numbered Access List
The following examples use a numbered access list to restrict creation of LSPs.
Preventing LSPs from the LSC to the Edge LSRs
The following example prevents LSPs from being established from the LSC to all 192.x.x.x destinations. However, transit LSPs are allowed between 192.x.x.x destinations. Add the following commands to the LSC configuration:
mpls request-labels for 1access-list 1 deny 192.168.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 LSR 2 to the LSC (172.16.x.x). However, transit LSPs are allowed between 192.168.x.x destinations. Add the following commands to the Edge LSR 1 and 2 configurations:
mpls request-labels for 1access-list 1 deny 172.16.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:
mpls request-labels for nolervcsip access-list standard nolervcsdeny 192.168.0.0 0.255.255.255permit anympls request-labels for nolervcsip access-list standard nolervcsdeny 172.16.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:
mpls request-labels for 1access-list 1 deny 192.168.0.1 0.0.0.0access-list 1 deny 192.168.0.2 0.0.0.0access-list 1 permit anympls request-labels for 1access-list 1 deny 172.16.53.1 0.0.0.0access-list 1 permit anyConfiguration Example: Using an Access List to Limit Headend VCs
The following example shows how to use an access list to control the creation of headend VCs in an MPLS network, which allows the network to support more destinations.
Figure 28 shows two Edge LSRs and two ATM-LSRs. In the configuration, only LSPs between Edge LSRs are required to provide label switched paths. Other LSPs are not essential. The LSPs between LSCs and between the LSCs and the Edge LSRs are often unused and required only for monitoring and maintaining the network. In such cases the IP forwarding path is sufficient.
Figure 28 Sample MPLS Network
In networks that require connections only between Edge LSRs, you can use the access list to eliminate the creation of unnecessary LSPs. This allows LVC resources to be conserved so that more Edge LSR connections can be supported.
To prevent creation of LSPs between LSCs, create an access list that denies all 172.16.0.0/24 addresses. Then, to prevent creation of LVCs from the LSCs to the Edge LSRs, create an access list that denies all 192.168.0.0/24 addresses. The configuration examples for LSC 1 and 2 show the commands for performing these tasks.
To prevent creation of LVCs from the Edge LSRs to LSCs, create an access list at the Edge LSRs that denies all 172.16.0.0/24 addresses. The configuration examples for Edge LSR 1 and 2 show the commands for performing this task.
Configuration for LSC 1
7200 LSC 1:
ip cef!mpls request-labels for acl_lscip access-list standard acl_lscdeny 172.16.0.0 0.255.255.255deny 192.168.0.0 0.255.255.255permit any!interface loopback0ip address 172.16.0.1 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0mpls atm vpi 2-15mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ipConfiguration for BPX 1 and BPX 2
BPX 1 and BPX 2:
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
Configuration for LSC 2
7200 LSC 2:
ip cef!mpls request-labels for acl_lscip access-list standard acl_lscdeny 172.16.0.0 0.255.255.255deny 192.168.0.0 0.255.255.255permit any!interface loopback0ip address 172.16.0.2 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13extended-port ATM3/0 bpx 1.3ip unnumbered loopback0mpls atm vpi 2-15mpls ip!interface XTagATM22extended-port ATM3/0 bpx 2.2ip unnumbered loopback0mpls atm vpi 2-5mpls ip!Configuration for Edge LSR 1
LSR 1:
ip cef distributed!mpls request-labels for acl_lerip access-list standard acl_lerdeny 172.16.0.0 0.255.255.255permit any!interface loopback 0ip address 192.168.0.1 255.255.255.255!interface ATM2/0/0no ip address!interface ATM2/0/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipConfiguration for Edge LSR 2
7200 LSR 2:
ip cef!mpls request-labels for acl_lerip access-list standard acl_lerdeny 172.16.0.0 0.255.255.255permit any!interface loopback 0ip address 192.168.0.2 255.255.255.255!interface ATM2/0no ip address!interface ATM2/0.22 mplsip unnumbered loopback 0mpls atm vpi 2-5mpls ipFeature 4: Differentiated Services and MPLS QoS Multi-VCs
Quality of service (QoS) refers to the ability of a network to provide better service to selected network traffic over various underlying technologies including Frame Relay, ATM, Ethernet and 802.1 networks, SONET, and IP-routed networks. In particular, QoS features provide better and more predictable network service by supporting dedicated bandwidth, improving loss characteristics, avoiding and managing network congestion, shaping network traffic, and setting traffic priorities across the network.
A service model, also called a level of service, describes a set of end-to-end QoS capabilities. End-to-end QoS is the ability of the network to deliver service required by specific network traffic from one end of the network to another. Differentiated services is a service model supported by Cisco IOS QoS software that can provide end-to-end QoS.
The Multiprotocol Label Switching quality of service (MPLS QoS) mechanism is a feature for performing differentiated services over ATM. The MPLS QoS Multi-VC mode enhances general MPLS QoS features by enabling users to map the experimental (EXP) field value of an MPLS label to an ATM virtual circuit (VC) to create sets of labeled virtual circuits (LVCs). Each set consists of multiple LVCs, and each LVC is treated as a member of the set.
Differentiated Services and Quality of Service
Differentiated service (DiffServ) is a multiple service model that can satisfy differing QoS requirements. However, unlike the integrated service model, an application using differentiated service does not explicitly signal the router before sending data.
Two different acronyms are used for differentiated services and both are commonly used in other documents. "DiffServ" is used most commonly, and refers to differentiated services in general. "DS" is the name given specifically to the bits in the IP headers used by DiffServ.
For differentiated service, the network tries to deliver a particular kind of service based on the QoS specified by each packet. This specification can occur in different ways, for example, using the IP Precedence bit settings in IP packets. The network uses the QoS specification to classify, mark, shape, and police traffic, and to perform intelligent queuing.
The differentiated service model is used for several mission-critical applications and for providing end-to-end QoS. Typically, this service model is appropriate for aggregate flows because it performs a relatively coarse level of traffic classification.
Cisco IOS QoS includes the following features that support the differentiated service model:
•
•
The DiffServ approach to QoS divides network traffic into a small number of classes and allocates resources on a per-class basis. DiffServ can be viewed as an incremental approach to QoS.
DiffServ Per-Hop Behaviors
DiffServ networks use queuing technologies such as weighted fair queuing (WFQ) to provide differential service to the different classes of service (CoS). Link-by-link engineering of WFQ parameters is the approach suggested by the IETF DiffServ Working Group.
The treatment of a particular CoS on a particular link (or "hop"), using technologies such as weighted fair queuing, is referred to as a per-hop behavior (PHB). Cisco supports engineering of per-hop behaviors on links in both ATM MPLS and packet-based MPLS networks, as well as ordinary IP networks. The principles are the same in all network types, although there are differences in the way CoS information is carried in packets for different networks.
DiffServ Classes and Cisco IP+ATM Switches
Engineering of DiffServ networks leads to specifications of required bandwidths for various classes of service on various links of the network. This is quite different from traditional per-VC bandwidth management in ATM networks.
As shown in Figure 29, class-based queuing involves a separate queue in the ATM switch for each CoS. Cells from all LVCs of each CoS are queued in a single queue for that CoS. The bandwidth parameters of a CoS on a link are set directly on the CoS queue. The only parameter signalled for each LVC is the CoS for the LVC. This means that the ATM MPLS control component is used unchanged, except that multiple LVCs are set up for each destination: one LVC per destination per CoS.
Figure 29 Per-VC Service and CoS in Cisco IP + ATM Switches
Cisco IP+ATM switches support DiffServ for MPLS traffic, alongside ATM Forum Traffic Management types for PVCs and SVCs. Each DiffServ or ATM Forum Traffic Management type gets is own "class of service buffer." Per-VC queuing can be used in addition to the class of "class of service buffers" and this is done for ATM Forum Traffic Management types. Weighted fair queuing is used to assign bandwidths to the IP class of service buffers. This means that the IP classes share bandwidth.
Using class-based queuing instead of per-VC queuing for the IP traffic has several advantages:
•
•
•
•
•
For these reasons, Cisco strongly recommends that networks supporting IP services are engineered using class-based queuing.
Requirements for Differential Services Approach to QoS
Good quality of service can be provided to connectionless IP traffic, on MPLS networks in particular. The process involves the following:
•
•
•
•
•
•
Configuring Multi-VCs
The Multiprotocol Label Switching quality of service (MPLS QoS) mechanism is a feature for performing differentiated services over ATM. It allows the ATM network to treat different packets based on the EXP (experimental) field (also called CoS) of the MPLS header which has the same properties, and which can be mapped to IP precedence. You can configure multiple VCs that have different QoS characteristics between any pair of ATM-connected routers.
Every label switch router (LSR) has a corresponding number of virtual circuits (VCs)—from one to four—for the same destination, hence the term "multi-VC." These parallel label virtual circuits (LVCs) are set up automatically by the upstream edge router using the Label Distribution Protocol. Each set consists of multiple LVCs, and each LVC is treated as a member of the set.
For more detailed information on configuring multi-VCs, refer to the following document:
MPLS QoS Multi-VC Mode for PA-A3
Setting Up LVCs
When you configure multi-VC support, four LVCs for each destination are created by default that map to MPLS QoS. Table 7 shows the LVC to MPLS QoS mapping.
Table 7 LVC to MPLS QoS Mapping
Available
0
0,4
Standard
1
1,5
Premium
2
2,6
Control
3
3, 7
To set up four default LVCs (with default mapping), you add the following instruction to the ATM subinterface configuration of the Edge LSRs:
mpls atm multi-vcThe parallel LVCs are set up automatically on the ATM switches.
Optionally Setting the MPLS Experimental Field Value
The ability to optionally set the MPLS EXP field of the label header upon entry of a customer IP packet into an MPLS network has no direct connection to the MPLS QoS multi-VC mode feature per se. However, the ability to manipulate the EXP field provides flexibility to preserve the IP precedence value in the IP type-of-service (ToS) byte in the header of an incoming IP packet. The service provider can manage queues or select LVCs based on the value of the EXP field.
You can set the MPLS experimental field (EXP) value in customer IP packets arriving at the provider edge router by means of modular QoS CLI commands or CAR commands executed on that edge router.
Using Modular QoS CLI to Configure Ingress Label Switching Router
To use the modular QoS CLI to configure the ingress LSR appropriately for multi-VC mode functionality, perform the following steps:
Step 1
Step 2
Step 3
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)# endIn the following example, the MPLS EXP field of each IP packet that matches class-map IP_prec4 is set to a value of 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)# endIn the following example, the service policy set_experimental_5 is attached to the specified Ethernet input interface (et 1/0/0):
Router(config)# interface et 1/0/0 Router(config-if)# service-policy input set_experimental_5 Router(config-if)# endUsing CAR to Configure an Ingress Label Switching Router
To classify the packets on the ingress Edge LSR, you can use MPLS QoS committed access rate (CAR) service to set the EXP field of the MPLS header to the desired value. To use CAR to configure the ingress LSR for multi-VC mode functionality, perform the following steps:
Step 1
Step 2
In the following example, all packets containing IP precedence value 4 are matched by the rate-limit access list 24:
Router(config)# access-list rate-limit 24 4 Router(config)# endIn the following example, the MPLS EXP field is set to 4 on output of packets if input IP packets match the access-list and conform to the packet rate. The MPLS EXP field is set to 0 if packets match access list 24 and exceed the input rate.
Router(config)# interface et 1/0/0 Router(config-if)# rate-limit input access-group rate-limit 24 8000 8000 8000 conform-action set-mpls-exp-transmit 4 exceed-action set-mpls-exp-transmit 0 Router(config-if)# end
Note
You need to configure ip cef (ip cef distributed on a Cisco 7200) on the general configuration of the routers before you configure CAR.
Configuring MPLS QoS in the Core of an ATM Network
To configure MPLS QoS in the core of an ATM network, perform the following steps:
Step 1
Step 2
The default for the multi-VC mode creates four LVCs (available, standard, premium, and control) for each MPLS destination.
If you do not choose to use the default for configuring LVCs, you can configure fewer LVCs by using the QoS map function.
Configuring Queuing Functions on Router Output Interfaces
To configure class-based weighted fair queuing (CBWFQ) and weighted random early detection (WRED) functionality on a Cisco 7200 series router interface or a Cisco MGX 8850 switch with the Cisco RPM-PR card interface, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Setting the ATM-CLP Bit on Enhanced ATM Port Adapter Interfaces
To set the ATM-CLP bit in ATM cells exiting from an enhanced ATM port adapter interface incorporated into a Cisco 7200 router or a Cisco MGX RPM-PR (in a Cisco MGX 8850 or 8890 switch), perform the following steps:
Step 1
Step 2
Step 3
Step 4
Verifying MPLS QoS Operation
To verify the operation of MPLS QoS, issue the following commands to view information about the switching interfaces, the specified QoS map used to assign a quantity of VCs, and the prefix map used to assign a QoS map to network prefixes that match a standard IP access list.
Router# show mpls interfaces interfacesRouter# show mpls cos-map cos-mapRouter# show mpls prefix-mapConfiguration Examples
This section provides examples for the following configurations, based on the sample ATM LSR network configuration shown in Figure 30:
•
•
•
•
•
•
Note
Figure 30 Sample ATM LSR Network Configuration (CE1 to be added with connection to Edge LSR1)
Configuration for CE1
2600 or 3600 CE1:
interface Loopback0ip address 7.7.7.7 255.255.255.0!interface FastEthernet0/1ip address 150.150.0.2 255.255.255.0duplex autospeed auto!router ospf 1network 7.7.7.7 0.0.0.0 area 0network 150.150.0.0 0.0.0.255 area 0Configuration for Edge LSR1
8850 with RPM-PR LSR1:
ip cef distributed!class-map match-all exp0match mpls experimental 0 4class-map match-all exp1match mpls experimental 1 5class-map match-all exp2match mpls experimental 2 6class-map match-all exp3match mpls experimental 3 7class-map match-all acl101match access-group 101class-map match-all acl102match access-group 102!policy-map atm_outputclass exp0bandwidth percent 10class exp1bandwidth percent 25class exp2bandwidth percent 20class exp3bandwidth percent 20!policy-map input_intclass acl101police cir 64000 bc 2000 conform-action set-mpls-exp-transmit 2 exceed-action set-mpls-exp-transmit 1class acl102police cir 32000 bc 1500 conform-action set-mpls-exp-transmit 3 exceed-action drop!interface loopback 0ip address 142.6.132.2 255.255.255.255!interface Ethernet1/1ip address 150.150.0.1 255.255.255.0service-policy input input_int!interface ATM2/0/0no ip address!interface ATM2/0/0.5 mplsip unnumbered loopback 0service-policy output atm_outputmpls atm vpi 2-5mpls atm multi-vcmpls ip!access-list 101 permit ip host 7.7.7.7 anyaccess-list 102 permit ip host 150.150.0.2 anyConfiguration for LSC1
7200 or 8850 with PRM-PR LSC1:
ip cef!interface loopback0ip address 192.103.210.5 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13ip unnumbered loopback 0extended-port ATM3/0 bpx 1.3mpls atm vpi 2-15mpls atm cos available 20mpls atm cos standard 30mpls atm cos premium 25mpls atm cos control 25mpls ip!interface XTagATM23ip unnumbered loopback 0extended-port ATM3/0 bpx 2.2mpls atm vpi 2-5mpls atm cos available 20mpls atm cos standard 30mpls atm cos premium 25mpls atm cos control 25mpls ipConfiguration for BPX1 and BPX2
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 100000Configuration for LSC2
7200 or 8850 with RPM-PR LSC2:
ip cef!interface loopback0ip address 142.2.143.22 255.255.255.255!interface ATM3/0no ip addresstag-control-protocol vsiip route-cache cef!interface XTagATM13ip unnumbered loopback 0extended-port ATM3/0 bpx 1.3mpls atm vpi 2-15mpls atm cos available 20mpls atm cos standard 30mpls atm cos premium 25mpls atm cos control 25mpls ip!interface XTagATM23ip unnumbered loopback 0extended-port ATM3/0 bpx 2.2mpls atm vpi 2-5mpls atm cos available 20mpls atm cos standard 30mpls atm cos premium 25mpls atm cos control 25mpls ipConfiguration for Edge LSR2
7200 or 8850 with RPM-PR LSR2:
ip cef!class-map match-all exp0match mpls experimental 0 4class-map match-all exp1match mpls experimental 1 5class-map match-all exp2match mpls experimental 2 6class-map match-all exp3match mpls experimental 3 7class-map match-all acl101match access-group 101class-map match-all acl102match access-group 102!policy-map atm_outputclass exp0bandwidth percent 10class exp1bandwidth percent 25class exp2bandwidth percent 20class exp3bandwidth percent 20!policy-map input_intclass acl101police cir 64000 bc 2000 conform-action set-mpls-exp-transmit 2 exceed-action set-mpls-exp-transmit 1class acl102police cir 32000 bc 1500 conform-action set-mpls-exp-transmit 3 exceed-action drop!interface loopback 0ip address 142.2.142.2 255.255.255.255!interface Ethernet1/1ip address 160.160.0.1 255.255.255.0service-policy input input_int!interface ATM2/0no ip address!interface ATM2/0.9 mplsip unnumbered loopback 0service-policy output atm_outputmpls atm vpi 2-5mpls atm multi-vcmpls ip!access-list 101 permit ip host 8.8.8.8 anyaccess-list 102 permit ip host 160.160.0.1 anyConfiguration for CE2
2600 or 3600 CE2:
interface Loopback0ip address 8.8.8.8 255.255.255.0!interface FastEthernet0/1ip address 160.160.0.1 255.255.255.0duplex autospeed auto!router ospf 1network 8.8.8.8 0.0.0.0 area 0network 160.160.0.0 0.0.0.255 area 0QoS 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).
Feature 5: MPLS VC Merge
The VC merge feature allows multiple incoming VCs to be merged into a single outgoing VC. This feature is only available on hardware that supports VC Merge functionality. See VC Merge Hardware and Software Requirements for more information. VC Merge helps scale MPLS networks, because it allocates only one VC to each destination on a link. Figure 31 shows how VC merge streamlines the flow of frames in a network.
Figure 31 How VC Merge Improves the Flow of Information
Feature Overview
VC merge maps several incoming labels to one single outgoing label. Cells from different virtual channel identifiers (VCIs) traveling to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections.
VC merge allows the switch to transmit cells coming from different VCIs over the same outgoing VCI to the same destination. In other words, VC merge queues AAL5 frames in input buffers until the switch receives the last frame. Then the switch transmits the cells from that AAL5 frame before it sends any cells from other frames. VC merge requires the switch to provide buffering, but no more buffering than is required in IP networks. VC merge slightly delays the transfer of frames; however, VC merge is for IP traffic and not for traffic that requires speed. IP traffic tolerates delays better than other traffic on the ATM network.
In Figure 32, routers A and B send traffic to router C (prefix 171.69.0.0/16). The ATM switch in the middle is configured with a single outbound VCI 50, which is bound to prefix 171.69.0.0/16. Data that flows from routers A and B congregates in the ATM switch and shares the same outgoing VC. The ATM switch buffers the cells from VCIs 40 and 90 until it receives all the AAL5 frames. Then, the switch forwards the complete frame router C on VCI 50.
Figure 32 How VC Merge Works
VC merge is enabled by default. To disable VC merge, enter the no mpls ldp atm vc-merge command in global configuration mode.
VC Merge Benefits
The VC merge feature makes MPLS networks highly scalable. Without VC merge, an IGX 8400 network can scale to about 22-64 Edge LSRs. The VC merge feature can expand the number of Edge LSRs 2 to 10 times that amount.
Note
This sharing of labels reduces the total number of virtual circuits required for label switching. Without VC merge, each source-destination prefix pair consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination.
VC Merge Restrictions
•
•
•
•
•
VC Merge Hardware and Software Requirements
You need the following hardware, software, and firmware to enable the VC merge feature.
Hardware:
Cisco IGX 8400 switches with a UXM-E card
Cisco BPX 8600 series switches with a BXM-E card
Cisco MGX 8850 switches with an AXSM or AXSM-E card
Cisco IGX and BPX Switch Software
Release 9.3.10 or higher
IOS Software
12.2(8)T or higher
Related VC Merge Docs
Designing MPLS for ATM: Dimensioning MPLS Label VC Space
Configuration
The VC merge feature is enabled by default on devices that support the feature. To disable the VC merge feature, use the no mpls ldp atm vc-merge command.
Feature 6: MPLS Diff-Serv-Aware Traffic Engineering over ATM
Multiprotocol Label Switching Traffic Engineering (MPLS TE) supports the Diff-Serv-aware over ATM feature. MPLS TE allows constraint-based routing of IP traffic. One of the constraints satisfied by constraint-based routing is the availability of required bandwidth over a selected path. Diff-Serv-aware Traffic Engineering (DS-TE) extends MPLS traffic engineering to enable you to perform constraint-based routing of "guaranteed" traffic, which satisfies a more restrictive bandwidth constraint than that satisfied by constraint-based routing for regular traffic. The more restrictive bandwidth is termed a sub-pool, while the regular TE tunnel bandwidth is called the global pool. (The sub-pool is a portion of the global pool.) Tunnels using the sub-pool bandwidth can be used in conjunction with MPLS quality of service (QoS) mechanisms to deliver guaranteed bandwidth services end-to-end across the network. The ability to satisfy a more restrictive bandwidth constraint translates into an ability to achieve higher QoS performance (in terms of delay, jitter, or loss) for the guaranteed traffic.
Guaranteed Bandwidth Service Configuration
You can configure two bandwidth pools for tunnel head-end, mid-point, and tail-end devices. (See MPLS Diff-Serv-aware Traffic Engineering (DS-TE) over ATM for configuration information.) Once these pools are configured, you can:
•
•
Having a separate pool for traffic requiring strict guarantees allows you to limit the amount of such traffic admitted on any given link. Often, you can achieve strict QoS guarantees only if the amount of guaranteed traffic is limited to a portion of the total link bandwidth.
Having a separate pool for other traffic (best-effort or Diff-Serv traffic) allows you to have a separate limit for the amount of such traffic admitted on any given link. This is useful because it allows you to fill up links with best-effort or Diff-Serv traffic, thereby achieving a greater utilization of those links.
Providing Strict QoS Guarantees Using DS-TE Sub-pool Tunnels
A tunnel using sub-pool bandwidth can satisfy the stricter requirements if you do all of the following:
1.
For delay/jitter guarantees, use the Diff-Serv Expedited Forwarding PHB (EF PHB). On the Cisco 7200 it is the "priority" queue. You must configure the bandwidth of the queue to be at least equal to the bandwidth of the sub-pool.
For bandwidth guarantees, use the Diff-Serv Assured Forwarding PHB (AF PHB). On the Cisco 7200 you use one of the existing class-based weighted fair queuing (CBWFQ) queues.
2.
You do this by marking the traffic that enters the tunnel with a unique value in the mpls exp bits field, and steering only traffic with that marking into the GB queue.
3.
You do this by rate-limiting the guaranteed traffic before it enters the sub-pool tunnel. The aggregate rate of all traffic entering the sub-pool tunnel should be less than or equal to the bandwidth capacity of the sub-pool tunnel. Excess traffic can be dropped (for delay/jitter guarantees) or can be marked differently for preferential discard (for bandwidth guarantees).
4.
You do this by setting the sub-pool bandwidth of each outbound link to the appropriate percentage of the total link bandwidth (that is, by adjusting the subpool kbps parameter of the ip rsvp bandwidth command).
Providing Differentiated Service Using DS-TE Global Pool Tunnels
You can configure a tunnel using global pool bandwidth to carry best-effort as well as several other classes of traffic. Traffic from each class can receive differentiated service if you do all of the following:
1.
2.
3.
To control the amount of Diff-Serv tunnel traffic you intend to support on a given link, adjust the size of the global pool on that link.
Providing Strict Guarantees and Differentiated Service in the Same Network
Because DS-TE allows simultaneous constraint-based routing of sub-pool and global pool tunnels, strict guarantees and Diff-Serv can be supported simultaneously in a given network.
For More Information about MPLS Diff-Serv-aware over ATM
For more information on the MPLS Diff-Serv-aware over ATM feature and its configuration, see the following document:
MPLS Diff-Serv-aware Traffic Engineering (DS-TE) over ATM
Feature 7: MPLS: OAM Insertion and Loop Detection on LC-ATM
This feature allows you to use ATM OAM cells to detect a failure between cell-mode MPLS interfaces. If two Cisco routers are connected using an LC-ATM link or a logical link (VP tunnel interface), OAM cells are inserted at regular intervals and looped back on the remote end. When one side of the link goes down or if the logical link fails, the OAM cells cannot reach their destination, causing the interface to change to the down state. OAM management allows the status of LC-ATM interfaces to be identified. Using OAM management reduces the amount of time required to accurately reflect the status of the link.
Without OAM management, when one side of an LC-ATM link breaks, the other side of the link cannot detect the failure. The interface and the line protocol of the broken link are still in the up state.
You can configure the OAM management parameters and tune them to your network needs.
OAM management is enabled by default. If one Cisco router does not have same release of software (and thus does not have OAM management), the other router that has OAM management can detect the broken link.
This feature allows you to configure OAM management on the following types of interfaces:
•
•
•
Prerequisites for MPLS: OAM Insertion and Loop Detection on LC-ATM
This feature has the following prerequisites:
•
Restrictions for MPLS: OAM Insertion and Loop Detection on LC-ATM
This feature has the following restrictions:
•
•
•
How to Configure MPLS: OAM Insertion and Loop Detection on LC-ATM
Note
This procedure explains how to configure OAM management on the interface. You can also use this procedure to configure OAM management on an MPLS ATM or switch subinterface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface xtagatm{if-number}
Example:Router(config)# interface xtagatm61
Specifies the XtagATM interface.
Step 4
mpls atm control-vc vpi vci
Example:Router(config-subif)# mpls atm control-vc 0 32
Configures the control VC VPI and VCI values for the link to the MPLS peer.
This command also enables you to enter control-VC configuration mode.
Step 5
oam-pvc manage [seconds]
Example:Router(cfg-mpls-atm-cvc)# oam-pvc manage 25(Optional) Specifies how often OAM cells should be sent. See the oam-pvc command for the default values.
Step 6
oam retry [up-count down-count retry-frequency]
Example:Router(cfg-mpls-atm-cvc)# oam retry 2 3 4(Optional) Specifies the OAM retry count before declaring a VC is up or down, and its polling frequency. See the oam retry command for the default values.
Troubleshooting Tips
Use the following commands to help troubleshoot:
•
•
Configuration Examples for MPLS: OAM Insertion and Loop Detection on LC-ATM
This section provides the following configuration examples:
•
•
•
OAM Management with MPLS Subinterfaces Example
The following example show how to configure OAM management on an MPLS subinterface.
interface ATM3/0.100 mplsip unnumbered Loopback0mpls atm control-vc 0 32oam-pvc manage 1mpls ipOAM Management with Switch Subinterfaces on Route Processor Modules Example
The following example shows how to configure OAM management on a switch subinterface on an route processor module.
interface Switch1.10 mplsip unnumbered Loopback0mpls atm control-vc 0 32oam retry 1 5 1oam-pvc manage 2mpls ipOAM Management with XtagATM Subinterfaces on Label Switch Controllers Example
The following example shows how to configure OAM management on an XtagATM subinterface.
interface xtagatm113ip unnumbered Loopback0extended-port Switch1 descriptor "11:1.3:3"mpls atm control-vc 0 32oam retry 1 5 1mpls ipFeature 8: Troubleshooting the MPLS LSC Network with the LVC Path Trace Feature
This section describes the LVC Path Trace feature, which enables you to display the path of an established LVC. The show mpls atm-ldp bindings command has been updated with the path keyword. By displaying the path of an LVC, it is easier to troubleshoot outages in an MPLS LSC network.
Prerequisites for the LVC Path Trace Feature
Before issuing the show mpls atm-ldp bindings command with the path keyword, ensure that LDP loop detection is enabled throughout the LC-ATM network. The LDP loop detection mechanism is used with the Downstream on Demand (DoD) method of label distribution, supplementing the DoD hop count mechanism to detect looping label switched paths (LSPs) that might occur during transient routing events. You enable LDP loop detection with the mpls ldp loop-detection global configuration command.
If LDP loop detection is not enabled, the following error message is displayed when you issue the show mpls atm-ldp bindings command with the path keyword:
%Cannot trace the path of LVCs, because LDP loop detection is not enabled for this LDP sessionEnsure that LDP loop detection is configured before LDP sessions are configured. Issuing the mpls ldp loop-detection command on already existing LDP sessions has no effect. The following error message is displayed:
%Enabling loop detection has no effect on existing LDP sessions.To determine if loop detection is enabled on DoD LDP sessions, you can issue the show mpls ldp neighbor detail command. In the following example, the last two lines of output show that LDP loop detection is on and the path vector limit of the LDP session is 20/20. (The path vector limit is configured with the mpls ldp maxhops command.)
Router# show mpls ldp neighbor detailPeer LDP Ident: 10.0.3.42:1; Local LDP Ident 10.0.2.102:1TCP connection: 10.0.3.42.11028 - 10.0.2.102.646State: Oper; Msgs sent/rcvd: 46/46; Downstream on demandUp time: 00:33:38; UID: 1; Peer Id 0;LDP discovery sources:Switch1.1; Src IP addr: 10.0.3.42holdtime: 15000 ms, hello interval: 5000 msPeer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estabClients: TC ATMLoop Detection Peer/Local: on/onPath vector Limit Peer/Local: 20/20Restriction for the LVC Path Trace Feature
The LVC Path Trace feature cannot completely trace the path of an LVC if VC merge capability is enabled. If VC Merge is enabled on some nodes, show mpls atm-ldp bindings command with the path keyword displays the path only up to the merging point.
Tracing the Path of an LVC
When you issue the show mpls atm-ldp bindings command with the path keyword, the command displays the path of the LVC, from the source to its destination. The asterisk (*) next to the prefix indicates the address from where the command was issued. The path output is limited to four router IDs per line. If more than four routers exist in the path, the command output wraps to the next line. For more information about the command output, see the show mpls atm-ldp bindings command with the path keyword. The following example is a sample LVC path trace:
Router# show mpls atm-ldp bindings 10.0.2.115 32 pathDestination: 10.0.2.115/32Headend Router Switch1.1 (2 hops) 0/39 Active, VCD=9, CoS=availablePath: 10.0.2.102* 10.0.3.42 10.0.2.115Headend Router Switch1.1 (2 hops) 0/41 Active, VCD=8, CoS=premiumPath: 10.0.2.102* 10.0.3.42 10.0.2.115Headend Router Switch1.1 (2 hops) 0/43 Active, VCD=7, CoS=controlPath: 10.0.2.102* 10.0.3.42 10.0.2.115The path is always displayed from headend to tailend. If you display the path of a transit node, the prefix with the asterisk appears in the middle of the output. If you display the path of a tailend device, the prefix with the asterisk is at the end.
The following example shows the path of a transit node:
Destination: 10.0.0.13/32Headend Switch XTagATM1301 (1 hop) 0/87 Active, VCD=604, CoS=availablePath: 10.0.0.10* 10.0.0.13Transit XTagATM4010202 0/3538 Active -> XTagATM1301 0/417 Active, CoS=availablePath: 10.0.0.2 10.0.0.10* 10.0.0.13Transit XTagATM4010202 0/3594 Active -> XTagATM1301 0/477 Active, CoS=availablePath: 10.0.0.11 10.0.0.2 10.0.0.10* 10.0.0.13Transit XTagATM10010202 0/2042 Active -> XTagATM1301 0/523 Active, CoS=availablePath: 10.0.0.100 10.0.0.10* 10.0.0.13Transit XTagATM4010505 1/262 Active -> XTagATM1301 0/717 Active, CoS=availablePath: 10.0.0.72 10.0.0.10* 10.0.0.13Transit XTagATM4010505 1/264 Active -> XTagATM1301 0/719 Active, CoS=standardPath: 10.0.0.72 10.0.0.10* 10.0.0.13Transit XTagATM4010505 1/266 Active -> XTagATM1301 0/721 Active, CoS=premiumPath: 10.0.0.72 10.0.0.10* 10.0.0.13Transit XTagATM4010505 1/268 Active -> XTagATM1301 0/723 Active, CoS=controlPath: 10.0.0.72 10.0.0.10* 10.0.0.13The following example shows the path of a tailend device:
Destination: 10.0.2.142/32Tailend Router Switch1.1 0/5464 Active, VCD=10432, CoS=availablePath: 10.0.2.112 10.0.3.25 10.0.2.142*Tailend Router Switch1.1 0/5466 Active, VCD=10433, CoS=premiumPath: 10.0.2.112 10.0.3.25 10.0.2.142*Tailend Router Switch1.1 0/5468 Active, VCD=10434, CoS=controlPath: 10.0.2.112 10.0.3.25 10.0.2.142*Tailend Router Switch1.1 0/8110 Active, VCD=11759, CoS=availablePath: 10.0.2.92 10.0.3.42 10.0.3.25 10.0.2.142*Tailend Router Switch1.1 0/8112 Active, VCD=11760, CoS=premiumPath: 10.0.2.92 10.0.3.42 10.0.3.25 10.0.2.142*Tailend Router Switch1.1 0/8114 Active, VCD=11761, CoS=controlPath: 10.0.2.92 10.0.3.42 10.0.3.25 10.0.2.142*Starting Up the Cisco MGX 8850 PXM-45 and Cisco MGX AXSM
The Cisco MGX 8850 AXSM Broadband ATM Switching Module is a high-density, high-speed module used in the Cisco MGX 8850 combined with the high-capacity PXM-45 processor switching module to deliver connectivity from T3/E3 to OC-48c/STM-16.
This section contains the following topics:
•
•
•
Before Startup
This section contains information about the following:
•
•
•
•
Access Privileges
The default username and password for access to the switch is cisco. In this mode, a limited set of commands are available for troubleshooting. If you log in during stage 1 and the card progresses to the "active" or "standby" state, the card logs out the stage 1 user and prompts you to log in again. At this point, you must log in as a user with configuration privileges and the corresponding password. The stage 1 username and password are not supported on active and standby cards.
To perform some startup procedures, you need to log in as a user with SUPER_GP privileges (default username and password: superuser, superuser).
To display detailed command lists, you must establish a session using a username with SERVICE_GP privileges or higher.
For more information on access privileges on the Cisco MGX 8850 switch, see the Cisco MGX 8850 Routing Switch Command Reference, Release 2.1.
Booting Order and Cautions
Make sure that you boot the Cisco 8850 PXM-45 Processor Switch Module properly with the correct PXM image. If the PXM-45 is not fully booted properly, you cannot reach any cards in the Cisco 8850 MGX switch. With a proper boot, you should get the "unknown.7.PXM.a>" prompt, or if you have already given the card a name, you should get a "name.7.PXM.a>" prompt. With either prompt, you can reach other cards.
The PXM-45 needs to be booted before you bring up the Cisco MGX 8850 RPM-PRs. Make sure that all RPM-PRs are booted properly with the correct image. Otherwise, the PXM does not recognize the RPM-PRs.
File and Directory Names Are Case Sensitive
You must use a capital E when referencing the E: drive in switch commands. File and directory names in the switch file system are case sensitive.
Flash Command vs. Bootflash Command
Although you can display directory contents with the dir bootflash: command, the show flash: command provides more detail. The terms bootflash and flash refer to the same entity on the RPM-PR; on other Cisco routers, bootflash and flash are separate entities.
Upgrade Cisco MGX 8850 PXM-45 Card First
Pay attention to the following if you plan to upgrade PXM-45 and AXSM cards:
•
•
•
•
Set Boot IP Address in Every Switch
Because the LAN IP address is stored on the PXM-45 hard disk and is not used until after the run-time software loads, Cisco recommends that the boot IP address be set in every switch. This enables switch management over Ethernet when the boot software has loaded.
Image File Formats
Figure 33 illustrates the filename format for released software.
Figure 33 Filename Format for Release Software
Figure 34 illustrates the filename format for prereleased firmware.
Figure 34 Filename Format for Prereleased Software
Copying the Images from the TFTP Server
To copy the software images for the Cisco MGX 8850 PXM-45 and Cisco MGX 8850 AXSM from the TFTP server to the Cisco MGX 8850 switch, perform the following steps:
Step 1
unknown.7.PXM.a > cnfname <node name>Enter up to 32 characters for the node name. The Cisco MGX 8850 switch node name is case sensitive. Be sure to enter the name correctly. For example:
unknown.7.PXM.a > cnfname SwitchThis node name will be changed to Switch. Please Confirmcnfname: Do you want to proceed (Yes/No)? ycnfname: Configured this node name to Switch Successfully.SWITCH.7.PXM.a >The new node name appears immediately in the next CLI prompt.
Step 2
Note
For example:
SWITCH.7.PXM.a > dspipif lnPci0SWITCH System Rev: 02.01 Sep. 13, 2001 16:19:43 GMTMGX8850 Node Alarm: MAJORIP INTERFACE CONFIGURATIONlnPci (unit number 0):Flags: (0x63) UP BROADCAST ARP RUNNINGInternet address: 10.0.6.105Broadcast address: 0.255.255.255Netmask 0xff000000 Subnetmask 0xffff0000Ethernet address is 00:01:42:26:5f:b2Metric is 0Maximum Transfer Unit size is 150020 packets received; 0 packets sent0 input errors; 0 output errors0 collisionsDISK IP address: 10.0.6.105SWITCH.7.PXM.a >If the IP address is not configured, then you can configure the IP address, using the following command:
ipifconfig <interface> [ <ip_address> ] [ netmask <mask> ] [ broadcast <broad_addr> ][ up | down ] [arp | noarp] [svc | nosvc] [pvc | nopvc][ default | nodefault] [clrstats]Where:
•
•
•
•
For example:
SWITCH.7.PXM.a > ipifconfig lnPci0 10.0.6.105 netmask 255.255.0.0 upYou can verify the IP address of the Ethernet interface, using the dspipif lnPci0 command.
Step 3
SWITCH.7.PXM.a > saveallcnfThe 'saveallcnf' command can be time-consuming. The shelfmust not provision new circuits while this command is running.Do not run this command unless the shelf configuration is stableor you risk corrupting the saved configuration file.Do you want to proceed (Yes/No)? ysaveallcnf: shelf configuration saved in C:/CNF/Switch_01_200109151550.zip.
Caution
Step 4
Workstation> ls002.001.060.008-P2.tar pxm1_001.001.060.008-P1_bt002.001.060.008-P2.tar.txt pxm1_001.001.060.008-P1_bt.fw2.01.60.8-P2.catcs pxm1_001.001.060.008-P1_bt.hexCWM_UPGRD pxm1_001.001.060.008-P1_bt.mapaxsm_002.001.060.008-A_bt pxm1_001.001.060.008-P1_sesaxsm_002.001.060.008-A_bt.fw pxm1_001.001.060.008-P1_ses.fwaxsm_002.001.060.008-A_bt.hex pxm1_001.001.060.008-P1_ses.mapaxsm_002.001.060.008-A_bt.map pxm45_002.001.060.008-P1_btaxsm_002.001.060.008-P2 pxm45_002.001.060.008-P1_bt.fwaxsm_002.001.060.008-P2.fw pxm45_002.001.060.008-P1_bt.hexaxsm_002.001.060.008-P2.map pxm45_002.001.060.008-P1_bt.mapaxsme_002.001.060.008-A_bt pxm45_002.001.060.008-P1_mgxaxsme_002.001.060.008-A_bt.fw pxm45_002.001.060.008-P1_mgx.fwaxsme_002.001.060.008-A_bt.hex pxm45_002.001.060.008-P1_mgx.mapaxsme_002.001.060.008-A_bt.map release.notesaxsme_002.001.060.008-P1 rpm-boot-mz.122-3.4.Taxsme_002.001.060.008-P1.fw rpm-js-mz.122-3.4.Taxsme_002.001.060.008-P1.mapStep 5
Note
Workstation> ftp 10.0.6.105Connected to 10.0.6.105.220 VxWorks FTP server (VxWorks 5.3.1) ready.Name (10.0.6.105:username): cisco331 Password requiredPassword:230 User logged inftp> bin200 Type set to I, binary modeftp> cd FW250 Changed directory to "C:FW"ftp> put pxm45_002.001.060.008-P1_bt.fw200 Port set okay150 Opening BINARY mode data connection226 Transfer completelocal: pxm45_002.001.060.008-P1_bt.fw remote: pxm45_002.001.060.008-P1_bt.fw897616 bytes sent in 9.2 seconds (96 Kbytes/s)Hash mark printing on (8192 bytes/hash mark).ftp> put pxm45_002.001.060.008-P1_mgx.fw200 Port set okay150 Opening BINARY mode data connection226 Transfer completelocal: pxm45_002.001.060.008-P1_mgx.fw remote: pxm45_002.001.060.008-P1_mgx.fw4889196 bytes sent in 49 seconds (97 Kbytes/s)ftp> put axsm_002.001.060.008-P2.fw200 Port set okay150 Opening BINARY mode data connection226 Transfer completelocal: axsm_002.001.060.008-P2.fw remote: axsm_002.001.060.008-P2.fw2651752 bytes sent in 27 seconds (97 Kbytes/s)ftp> put axsm_002.001.060.008-A_bt.fw200 Port set okay150 Opening BINARY mode data connection226 Transfer completelocal: axsm_002.001.060.008-A_bt.fw remote: axsm_002.001.060.008-A_bt.fw634528 bytes sent in 6.5 seconds (96 Kbytes/s)ftp> bye221 Bye...see you laterWorkstation>Step 6
SWITCH.7.PXM.a > cd FWThen, you can list the files on this directory using the ls or dir command.
SWITCH.7.PXM.a > ls...pxm45_002.000.002.000_mgx.fwpxm45_002.000.002.000_bt.fwaxsm_002.000.002.000.fwaxsm_002.000.002.000_bt.fwpxm45_002.001.000.235-A_bt.fwrpm-boot-mz_002.001.000.040rpm-js-mz_002.001.000.040axsm_002.001.000.040-A.fwaxsm_002.001.000.210-A_bt.fwpxm45_002.001.000.040-P1_mgx.fwpxm45_002.001.060.008-P1_bt.fwpxm45_002.001.060.008-P1_mgx.fwaxsm_002.001.060.008-P2.fwaxsm_002.001.060.008-A_bt.fwIn the file system :total space : 819200 K bytesfree space : 755677 K bytesThe files copied from the server are highlighted in the example.
Note
Upgrading the PXM-45 and AXSM Images
To upgrade the software images for the Cisco MGX 8850 PXM-45 and Cisco MGX 8850 AXSM cards, perform the following steps:
Step 1
Note
SWITCH.7.PXM.a > cd ..SWITCH.7.PXM.a > shWait until the display is complete before continuing to the next step.
Step 2
pxm45>sysBackupBootpxm45bkup> sysFlashBootBurn "C:FW/pxm45_002.001.060.008-P1_bt.fw"Burning backup boot from file=C:FW/pxm45_002.001.060.008-P1_bt.fwPlease confirm:[y/n yImgHdr: image_type=2,shelf_type=5,card_type=3000Checksum size is 897616 ...Simulating PXM Card removal.Downloading C:FW/pxm45_002.001.060.008-P1_bt.fw into the flash ...QUERY TABLE: flash_size=8388608 block_size=131072 write_buf_size=32buf_wr_time=2048 write_time=2048 erase_time=16384000burning 0xbfc00000 verify ... okburning 0xbfc20000 verify ... okburning 0xbfc40000 verify ... okburning 0xbfc60000 verify ... okburning 0xbfc80000 verify ... okburning 0xbfca0000 verify ... okburning 0xbfcc0000 verify ... okVerify checksum: addr=0xbfc00000 chksum=0x91ce90e3 size=(0xdb250,897616)...okFlash download completed ...value = 0 = 0x0pxm45bkup>rebootLogin: Entering rvtAct...BertCtcAppEventHandlerAttaching network interface sl0... done.Login: Ciscopassword:Step 3
SWITCH.7.PXM.a > dspcd 7SWITCH System Rev: 02.01 Sep. 13, 2001 16:48:18 GMTMGX8850 Node Alarm: MAJORSlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45 UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active-U Active ActiveSerial Number: SBK0447009D SBK044200XM SBK043600GVPrim SW Rev: 2.1(0.40)P1 --- ---Sec SW Rev: 2.1(0.40)P1 --- ---Cur SW Rev: 2.1(0.40)P1 --- ---Boot FW Rev: 2.1(60.8)P1 --- ---800-level Rev: B0 A0 A0800-level Part#: 800-06147-07 800-05787-02 800-05052-04CLEI Code: BAA5KMZCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop: qThe new boot firmware is highlighted in the example.
Step 4
Note
SWITCH.7.PXM.a > loadrev 7 2.1(60.8)P1one or more card(s) in the logical slot may be reset.loadrev: Do you want to proceed (Yes/No)? yStep 5
SWITCH.7.PXM.a > dspcd 7SWITCH System Rev: 02.01 Sep. 13, 2001 18:24:20 GMTMGX8850 Node Alarm: MAJORSlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45 UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active-U Active ActiveSerial Number: SBK0447009D SBK044200XM SBK043600GVPrim SW Rev: 2.1(0.40)P1 --- ---Sec SW Rev: 2.1(60.8)P1 --- ---Cur SW Rev: 2.1(0.40)P1 --- ---Boot FW Rev: 2.1(60.8)P1 --- ---800-level Rev: B0 A0 A0800-level Part#: 800-06147-07 800-05787-02 800-05052-04CLEI Code: BAA5KMZCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop: qThe new firmware and software images are highlighted in this example.
Step 6
SWITCH.7.PXM.a > runrev 7 2.1(60.8)P1one or more card(s) in the logical slot may be reset.runrev: Do you want to proceed (Yes/No)? yStep 7
SWITCH.7.PXM.a > burnboot 11 2.1(60.8)AThe card in slot 11 will be reset.burnboot: Do you want to proceed (Yes/No)? yStep 8
SWITCH.7.PXM.a > loadrev 11 2.1(60.8)Aone or more card(s) in the logical slot may be reset.loadrev: Do you want to proceed (Yes/No)? ySWITCH.7.PXM.a > runrev 11 2.1(60.8)P2one or more card(s) in the logical slot may be reset.runrev: Do you want to proceed (Yes/No)? yThe card goes through many states, but should settle in the Active-U state.
Step 9
Note
SWITCH.7.PXM.a > dspcd 11SWITCH System Rev: 02.01 Sep. 13, 2001 18:40:26 GMTMGX8850 Node Alarm: MAJORSlot Number: 11 Redundant Slot: NONEFront Card Upper Card Lower Card---------- ---------- ----------Inserted Card: AXSM_16OC3 MMF_8_OC3_MT ---Reserved Card: UnReserved UnReserved UnReservedState: Active-U Active EmptySerial Number: SBK044200H5 SBK044301MQ ---Prim SW Rev: 2.1(60.8)P2 --- ---Sec SW Rev: --- --- ---Cur SW Rev: 2.1(60.8)P2 --- ---Boot FW Rev: 2.1(60.8)A --- ---800-level Rev: ---800-level Part#: 800-05776-06 800-04819-01 ---CLEI Code: BAA5HLXCAA BAA5Z8UCAA ---Reset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop:Switch System Rev: 02.01 Sep. 13, 2001 18:40:26 GMTMGX8850 Node Alarm: MAJORCrossbar Slot Status: PresentAlarm Causes------------NO ALARMS
Note
Verifying the IOS Files on the PXM-45 E:Drive
The IOS image can be stored on the PXM-45 hard drive. To confirm this, make sure you are in the E:RPM directory and enter the ll command to list the contents of the directory. You should see a file named rpm-js-mz_002.001.000.057, or with a similar name beginning with rpm-js-mz, which is the IOS image.
Tip
The following screen displays the PXM E:RPM content listing:
SWITCH.7.PXM.a > cd E:RPMSWITCH.7.PXM.a >size date time name-------- ------ ------ --------512 FEB-23-2001 17:59:54 . <DIR>512 FEB-23-2001 17:59:54 .. <DIR>2452288 FEB-23-2001 11:13:10 rpm-boot-mz_002.001.000.0577934768 FEB-23-2001 11:15:24 rpm-js-mz_002.001.000.057744 FEB-27-2001 10:24:22 auto_config_slot11In the file system :total space : 102400 K bytesfree space : 91984 K bytesCommand Reference
This section describes the CLI commands that you can use with the MPLS LSC. All other commands used with this feature are documented in the Cisco IOS Release 12.3 command reference publications.
Modified Commands for Cisco IOS Release 12.3(9):
Modified Commands for Cisco IOS Release 12.3(9)
Commands Related to MPLS LSC
•
•
•
•
All other commands used with this feature are documented in the command reference publications.
Command Conventions
CLI Command Summary
Table 8 summarizes the MPLS commands that evolved from existing tag-switching commands.
debug mpls xtagatm cross-connect
To display requests and responses for establishing and removing cross-connects on the controlled ATM switch, use the debug mpls xtagatm cross-connect command. To disable debugging output, use the no form of this command.
debug mpls xtagatm cross-connect
no debug mpls xtagatm cross-connect
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
This command monitors requests to establish or remove cross-connects from XtagATM interfaces to the VSI master, as well as the VSI master's responses to these requests.
Note
Examples
The following is sample output from the debug mpls xtagatm cross-connect command:
Router# debug mpls xtagatm cross-connectXTagATM: cross-conn request; SETUP, userdata 0x17, userbits 0x1, prec 70xC0100 (Ctl-If) 1/32 <-> 0xC0200 (XTagATM0) 0/32XTagATM: cross-conn response; DOWN, userdata 0x60CDCB5C, userbits 0x2, resultOK0xC0200 1/37 --> 0xC0300 1/37Table 9 describes the significant fields in the sample command output shown above.
Related Commands
debug mpls xtagatm errors
To display information about error and abnormal conditions that occur on extended MPLS ATM (XtagATM) interfaces, use the debug mpls xtagatm errors command. To disable debugging output, use the no form of this command.
debug mpls xtagatm errors
no debug mpls xtagatm errors
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
Use the debug mpls xtagatm errors command to display information about abnormal conditions and events that occur on XtagATM interfaces.
Examples
The following is sample output from the debug mpls xtagatm errors command:
Router# debug mpls xtagatm errorsXTagATM VC: XTagATM0 1707 2/352 (ATM1/0 1769 3/915): Cross-connect setupfailed NO_RESOURCESThis message indicates a failed attempt to set up a cross-connect for a terminating VC on XtagATM0. The reason for the failure was a lack of resources on the controlled ATM switch.
debug mpls xtagatm events
To display information about major events that occur on extended MPLS ATM (XtagATM) interfaces, not including events for specific XtagATM VCs and switch cross-connects, use the debug mpls xtagatm events command. To disable debugging output, use the no form of this command.
debug mpls xtagatm events
no debug mpls xtagatm events
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
Use the debug mpls xtagatm events command to monitor major events that occur on XtagATM interfaces. This command monitors events that pertain only to XtagATM interfaces as a whole and does not include any events that pertain to individual XtagATM VCs or individual switch cross-connects. The specific events that are monitored when the debug mpls xtagatm events command is in effect include the following:
•
•
•
Examples
The following is sample output from the debug mpls xtagatm events command:
Router# debug mpls xtagatm eventsXTagATM: desired cross-connect table size set to 256XTagATM: ExATM API intf event Up, port 0xA0100 (None)XTagATM: ExATM API intf event Down, port 0xA0100 (None)XTagATM: marking all VCs stale on XTagATM0Table 10 describes the significant fields in the sample command output shown above.
debug mpls xtagatm vc
To display information about events that affect individual extended MPLS ATM (XtagATM) terminating VCs, use the debug mpls xtagatm vc command. To disable debugging output, use the no form of this command.
debug mpls xtagatm vc
no debug mpls xtagatm vc
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
Use the debug mpls xtagatm vc command to display detailed information about all events that affect individual XtagATM terminating VCs.
Note
Examples
The following is sample output from the debug mpls xtagatm vc command:
Router# debug mpls xtagatm vcXTagATM VC: XTagATM1 18 0/32 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM1 18 0/32 (ATM1/0 88 1/32): Complete, UpPend --> UpXTagATM VC: XTagATM1 19 1/33 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM0 43 0/32 (ATM1/0 67 1/84): Teardown, Up --> DownPendTable 11 describes the significant fields in the sample command output shown above.
debug vsi api
To display information on events associated with the external ATM API interface to the VSI master, use the debug vsi api command. To disable debugging output, use the no form of this command.
debug vsi api
no debug vsi api
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command History
Usage Guidelines
Use the debug vsi api command to monitor the communication between the VSI master and the XtagATM component regarding interface changes and cross-connect requests.
Examples
The following is sample output from the debug vsi api command:
Router# debug vsi apiVSI_M: vsi_exatm_conn_req: 0x000C0200/1/35 -> 0x000C0100/1/50desired state up, status OKVSI_M: vsi_exatm_conn_resp: 0x000C0200/1/33 -> 0x000C0100/1/49curr state up, status OKTable 12 describes the significant fields in the sample command output shown above.
debug vsi errors
To display information about errors encountered by the VSI master, use the debug vsi errors command. To disable debugging output, use the no form of this command.
debug vsi errors [interface interface [slave number]]
no debug vsi errors [interface interface [slave number]]
Syntax Description
Defaults
This command has no default behavior or values.
Command History
Usage Guidelines
Use the debug vsi errors command to display information about errors encountered by the VSI master when parsing received messages, as well as information about unexpected conditions encountered by the VSI master.
If the interface parameter is specified, output is restricted to errors associated with the indicated VSI control interface. If the slave number is specified, output is further restricted to errors associated with the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged immediately. For example, the following commands display errors associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions.
Router# debug vsi errors interface atm2/0 slave 0Router# debug vsi errors interface atm2/0 slave 1Some errors are not associated with any particular control interface or session. Messages associated with these errors are printed, regardless of the interface or slave options currently in effect.
Examples
The following is sample output from the debug vsi errors command:
Router# debug vsi errorsVSI Master: parse error (unexpected param-group contents) in GEN ERROR RSP rcvd on ATM2/0:0/51 (slave 0)errored section is at offset 16, for 2 bytes:01.01.00.a0 00.00.00.00 00.12.00.38 00.10.00.34*00.01*00.69 00.2c.00.00 01.01.00.80 00.00.00.0800.00.00.00 00.00.00.00 00.00.00.00 0f.a2.00.0a00.01.00.00 00.00.00.00 00.00.00.00 00.00.00.0000.00.00.00Table 13 describes the significant fields in the sample command output shown above.
debug vsi events
To display information about events that affect entire sessions, as well as events that affect only individual connections, use the debug vsi events command. To disable debugging output, use the no form of this command.
debug vsi events [interface interface [slave number]]
no debug vsi events [interface interface [slave number]]
Syntax Description
Defaults
This command has no default behavior or values.
Command History
Usage Guidelines
Use the debug vsi events command to display information about events associated with the per-session state machines of the VSI master, as well as the per-connection state machines. If you specify an interface, the output is restricted to events associated with the indicated VSI control interface. If you specify the slave number, output is further restricted to events associated with the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to events associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions. Output associated with all per-connection events are displayed, regardless of the interface or slave options currently in effect.
Router# debug vsi events interface atm2/0 slave 0Router# debug vsi events interface atm2/0 slave 1Examples
The following is sample output from the debug vsi events command:
Router# debug vsi eventsVSI Master: conn 0xC0200/1/37->0xC0100/1/51:CONNECTING -> UPVSI Master(session 0 on ATM2/0):event CONN_CMT_RSP, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event KEEPALIVE_TIMEOUT, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event SW_GET_CNFG_RSP, state ESTABLISHED -> ESTABLISHEDdebug vsi packetsTable 14 describes the significant fields in the sample command output shown above.
debug vsi packets
To display a one-line summary of each VSI message sent and received by the label switch controller (LSC), use the debug vsi packets command. To disable debugging output, use the no form of this command
debug vsi packets [interface interface [slave number]]
no debug vsi packets [interface interface [slave number]]
Syntax Description
Defaults
This command has no default behavior or values.
Command History
Usage Guidelines
If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface. If you specify a slave number, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to messages received on atm2/0 for sessions 0 and 1, but for no other sessions.
Router# debug vsi packets interface atm2/0 slave 0Router# debug vsi packets interface atm2/0 slave 1Examples
The following is sample output from the debug vsi packets command:
Router# debug vsi packetsVSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51VSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51Table 15 describes the significant fields in the sample command output shown above.
debug vsi param-groups
To display the first 128 bytes of each VSI message sent and received by the MPLS LSC (in hexadecimal form), use the debug vsi param-groups command. To disable debugging output, use the no form of this command.
debug vsi param-groups [interface interface [slave number]]
no debug vsi param-groups [interface interface [slave number]]
Note
Syntax Description
Defaults
This command has no default behavior or values.
Command History
Usage Guidelines
This command is most commonly used with the debug vsi packets command to monitor incoming and outgoing VSI messages.
If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface.
If you specify a slave, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple commands that specify a slave numbers allows multiple slaves to be debugged at once. For example, the following commands restrict output for messages received on atm2/0 for sessions 0 and 1, but for no other sessions.
Router# debug vsi param-groups interface atm2/0 slave 0 Router# debug vsi param-groups interface atm2/0 slave 1Examples
The following is sample output from the debug vsi param-groups command:
Router# debug vsi param-groupsOutgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c2 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c2 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31Outgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c3 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c3 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31Table 16 describes the significant fields in the sample command output shown above.
extended-port
To associate an extended MPLS ATM (XtagATM) interface with an external interface on the remotely controlled ATM switch, use the extended-port command in interface configuration mode. To remove the association, use the no form of this command.
extended-port ctrl-if {bpx bpx-port-number | igx igx-port-number | descriptor vsi-descriptor | vsi vsi-port-number}
no extended-port ctrl-if {bpx bpx-port-number | igx igx-port-number | descriptor vsi-descriptor | vsi vsi-port-number}
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The extended-port interface configuration command associates an XtagATM interface with an external interface on the remotely controlled ATM switch. The three alternate forms of the command permit the external interface on the controlled ATM switch to be specified in three different ways.
Examples
The following examples create an XtagATM interface, using different command qualifiers.
The following example creates an XtagATM interface and binds it to BPX switch port 2.3:
Router(config)# interface xtagatm23Router(config-if)# extended-port atm0/0 bpx 2.3The following example creates an XtagATM interface and binds it to port 2.4:
Router(config)# interface xtagatm24Router(config-if)# extended-port atm0/0 descriptor 0.2.4.0The following example creates an XtagATM interface and binds it to port 1622:
Router(config)# interface xtagatm1622Router(config-if)# extended-port atm0/0 vsi 0x00010614Related Commands
Creates an XtagATM interface.
Displays a summary of each VSI-controlled interface.
interface xtagatm
To create an extended MPLS ATM (XtagATM) interface, use the interface xtagatm command in global configuration mode. The interface is created the first time this command is issued for a particular interface number. To disable the XtagATM interface, use the no form of this command.
interface xtagatm if-num
no interface xtagatm if-num
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Global configuration
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
XtagATM interfaces are virtual interfaces that are created on reference-like tunnel interfaces. XtagATM interfaces are similar to ATM interfaces, except that the former only supports LC-ATM encapsulation.
Examples
In the following example, an XtagATM interface is created with interface number 62:
Router(config)# interface xtagatm62Related Commands
Associates the currently selected extended XTagATM interface with a remotely controlled switch.
mpls atm control-vc
To configure the control virtual circuit (VC) virtual path identifier (VPI) and virtual circuit identifier (VCI) values for the initial link to the MPLS peer, use the mpls atm control-vc command in interface configuration mode. Use this command to establish the LDP session and to carry non-IP traffic. To return the VPI and VCI to their default value, use the no form of this command.
mpls atm control-vc vpi vci
no mpls atm control-vc vpi vci
Syntax Description
vpi
Virtual path identifier, in the range from 0 to 4095.
vci
Virtual circuit identifier, in the range from 0 to 65535.
Defaults
0/32
Command Modes
Interface configuration
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
The VPI range of values was extended to 4095.
Usage Guidelines
The default VPI VCI for the control VC is (3, 32). If you need a different control VC, use the mpls atm control-vc command to configure a VPI VCI allowed by the vpi vci arguments for the control VC.
Examples
The following example creates an MPLS subinterface on a router and selects VPI 1 and VCI 34 as the control VC.
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm control-vc 1 34Related Commands
mpls atm cos
To change the configured bandwidth allocation for class of service (CoS), use the mpls atm cos command in xtagatm interface configuration mode.
mpls atm cos {available | standard | premium | control} weight
Syntax Description
Defaults
Available 50%, control 50%
Command Modes
xtagatm interface configuration
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Examples
In the following example, the XtagATM interface is configured for CoS traffic.
Router(config)# interface Xtagatm12Router(config-if)# extended-port atm1/0 descriptor 1.2Router(config-if)# mpls ipRouter(config-if)# mpls atm cos available 49Router(config-if)# mpls atm cos standard 50Router(config-if)# mpls atm cos premium 0Router(config-if)# mpls atm cos control 1mpls atm disable-headend-vc
To remove all headend virtual circuit (VCs) from the MPLS label switch controller (LSC) and disable its ability to function as an Edge LSR, use the mpls atm disable-headend-vc command in global configuration mode. To restore the headend VCs of the MPLS LSC and restores full Edge LSR functionality, use the no form of the command.
mpls atm disable-headend-vc
no mpls atm disable-headend-vc
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command Modes
Global configuration
Command History
12.0(7)DC
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
This command prevents the LSC from initiating headend LVCs, and thus reduces the number of LVCs used in the network.
Examples
In the following example, the MPLS LSC is disabled from acting like an Edge LSR and therefore cannot create headend LVCs.
Router(config)# mpls atm disable-headend-vcmpls ldp atm vc-merge
To enable the virtual circuit (VC) merge (multipoint to point VCs) feature for unicast label VCs, use the mpls ldp atm vc-merge command in global configuration mode. To disable the VC merge capability, use the no form of this command.
mpls ldp atm vc-merge
no mpls ldp atm vc-merge
Syntax Description
This command has no arguments or keywords.
Defaults
If the hardware supports ATM VC merge capabilities, this command is enabled by default; otherwise, the feature is disabled.
Command Modes
Global configuration
Command History
11.1CT
This command was introduced.
12.2(8)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
By default VC merge is enabled. Therefore it is not necessary to use this command to initialize the feature. However, if you disable the VC merge feature, you can use this command to enable it.
Use of VC merge helps conserve ATM labels by allowing incoming LSPs from different sources for the same destination to be merged onto a single outgoing VC.
Examples
In the following example, the ATM-VC merge capability is disabled:
Router# no mpls ldp atm vc-mergeRelated Commands
mpls atm vpi
To configure the range of values to use in the virtual path identifier (VPI) field for label virtual circuits (VCs), use the mpls atm vpi command in interface configuration mode. To clear the range of values, use the no form of this command.
mpls atm vpi vpi [- vpi] [vci-range low - high]
no mpls atm vpi vpi [- vpi] [vci-range low - high]
Syntax Description
Defaults
The default VPI range is 1 to 1.
The default VCI range is 33 to 65535.
Command Modes
Interface configuration
Command History
Usage Guidelines
You might need to change the default label VPI range on the switch if:
•
•
To configure ATM MPLS on a router interface (for example, an ATM Interface Processor), you must enable an MPLS subinterface.
Note
Use this command to select an alternate range of VPI values for ATM label assignment on this interface. The two ends of the link negotiate a range defined by the intersection of the range configured at each end.
•
•
•
If you use the vci-range keyword, you must specify a VPI value.
Examples
The following example creates a subinterface and selects a VPI range from VPI 1 to VPI 3:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 1-3The following example creates a subinterface with a VPI of 240 and a VCI range between 33 and 4090:
Router(config)# interface atm4/0.1 mplsRouter(config-if)# mpls ipRouter(config-if)# mpls atm vpi 240 vci-range 33-4090Related Commands
mpls atm vp-tunnel
To specify an interface or a subinterface as a VP tunnel, use the mpls atm vp-tunnel command in interface configuration mode. To remove the VP tunnel from an interface or subinterface, use the no form of this command.
mpls atm vp-tunnel vpi [vci-range low - high]
no mpls atm vp-tunnel vpi [vci-range low - high]
Syntax Description
vpi
The VPI value for the local end of the tunnel (0 to 4095).
vci-range low - high
Range of VCI values the VP tunnel can use.
Defaults
If you do not specify a VCI range for the VP tunnel, the tunnel uses the default VCI range of 33 to 65535.
Command Modes
Interface configuration
Command History
Usage Guidelines
The mpls atm vp-tunnel and mpls atm vpi commands are mutually exclusive.
This command is available on both extended MPLS ATM (XtagATM) interfaces and on LC-ATM subinterfaces of router ATM interfaces. The command is not available on the LS1010, where all subinterfaces are automatically VP tunnels.
It is not necessary to use the mpls atm vp-tunnel command on an XtagATM interface in most applications. The switch learns (through VSI interface discovery) whether the XtagATM interface is a tunnel, the VPI value of the tunnel, and tunnel status.
Examples
The following example creates an MPLS subinterface VP tunnel with a VPI value of 4:
Router(config-if)# mpls atm vp-tunnel 4The following example creates a VP tunnel with a value of 240 and a VCI range of 33 to 4090:
Router(config-if)# mpls atm vp-tunnel 240 vci-range 33-4090mpls request-labels for
To restrict the creation of label virtual circuits (LVCs) through the use of access lists on the label switch controller (LSC) or label edge router, use the mpls request-labels for command in global configuration mode. To disable this feature, use the no form of this command.
mpls request-labels for access list
no mpls request-labels for
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Global configuration
Command History
12.1(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
The command includes the following usage guidelines:
•
•
•
Examples
In the following example, headend LVCs are prevented from being established from the LSC to all 192.168.x.x destinations. The following commands are added to the LSC configuration:
Router(config)# mpls request-labels for 1Router(config)# access-list 1 deny 192.168.0.0 0.255.255.255Router(config)# access-list 1 permit anyRelated Commands
access list
Creates access lists.
ip access-list
Permits or denies access to IP addresses.
oam-pvc
To enable end-to-end F5 Operation, Administration, and Maintenance (OAM) loopback cell generation and OAM management for an ATM permanent virtual circuit (PVC), virtual circuit (VC) class, or control VC, use the oam-pvc command in the appropriate command mode. To disable generation of OAM loopback cells and OAM management, use the no form of this command.
For an ATM VC or VC class:
oam-pvc [manage] [frequency]
no oam-pvc [manage] [frequency]
For an LC-ATM VC:
oam-pvc manage [frequency]
no oam-pvc manage [frequency]
Syntax Description
Defaults
For ATM VCS or VC Classes:
10 seconds
For control VCs
OAM is enabled by default. The default frequency is 5 seconds.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC)
VC-class configuration (for a VC class)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for enabling OAM management on an LC-ATM VC)
Command History
Usage Guidelines
If OAM management is enabled, further control of OAM management is configured using the oam retry command.
For ATM VCS or VC Classes:
If the oam-pvc command is not explicitly configured on an ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an ATM PVC with a transmission frequency of 3 seconds:
Router(cfg-mpls-atm-cvc)# oam-pvc manage 3The following example shows how to enable end-to-end F5 OAM loopback cell transmission and OAM management on an LC-ATM interface with a transmission frequency of 2 seconds:
Router(config)# interface Switch1.10 mplsRouter(config-subif)# ip unnumbered Loopback0Router(config-subif)# mpls atm control-vc 0 32Router(cfg-mpls-atm-cvc)# oam-pvc manage 2Related Commands
Configures parameters related to OAM management for an ATM PVC, SVC, VC class or LC-ATM VC.
oam retry
To configure parameters related to Operation, Administration, and Maintenance (OAM) management for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), VC class, or VC bundle, or control VC, use the oam retry command in the appropriate command mode. To remove OAM management parameters, use the no form of this command.
oam retry up-count down-count retry-frequency
no oam retry
Syntax Description
Defaults
For ATM PVCs and SVCs:
up-count = 3
down-count = 5
retry-frequency = 1 second
For control VCs:
up-count = 2
down-count = 2
retry-frequency = 2 seconds
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle configuration mode (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Control-VC configuration (for an LC-ATM VC)
Command History
Usage Guidelines
These following guidelines apply to PVCs, SVCs, and VC classes. They do not apply to control VCs.
•
–
–
–
–
•
•
–
–
–
Examples
The following example shows how to configure the OAM management parameters with up-count 3, down-count 3, and the retry-frequency at 10 seconds:
Router(cfg-mpls-atm-cvc)# oam retry 3 3 10Related Commands
oam-bundle
Enables end-to-end F5 OAM loopback cell generation and OAM management for a virtual circuit class that can be applied to a virtual circuit bundle.
oam-pvc
Enables end-to-end F5 OAM loopback cell generation and OAM management for an ATM PVC or virtual circuit class.
oam-svc
Enables end-to-end F5 OAM loopback cell generation and OAM management for an ATM SVC or virtual circuit class.
1 Not all commands are supported for all types of VCs.
show atm vc
To display information about private ATM virtual circuits (VCs), use the show atm vc command in privileged EXEC mode.
show atm vc [vcd]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Private VCs exist on the control interface of an MPLS LSC to support corresponding VCs on an extended MPLS ATM interface.
VCs on the extended MPLS ATM interfaces do not appear in the show atm vc command output. Instead, the show xtagatm vc command provides similar output that shows information only on extended MPLS ATM VCs.
Examples
In the following example, no VCD is specified and private VCs are present:
Router# show atm vcAAL / Peak Avg. BurstInterface VCD VPI VCI Type Encapsulation Kbps Kbps Cells StatusATM1/0 1 0 40 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 2 0 41 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 3 0 42 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 4 0 43 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 5 0 44 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 15 1 32 PVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 17 1 34 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 26 1 43 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 28 1 45 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 29 1 46 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVEWhen you specify a VCD that corresponds to that of a private VC on a control interface, the display output appears as follows:
Router# show atm vc 15ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE ATM1/0: VCD: 15, VPI: 1, VCI: 32, etype:0x8, AAL5 - XTAGATM, Flags: 0xD38PeakRate: 0, Average Rate: 0, Burst Cells: 0, VCmode: 0x0 XTagATM1, VCD: 1, VPI: 0, VCI: 32 OAM DISABLED, InARP DISABLED InPkts: 38811, OutPkts: 38813, InBytes: 2911240, OutBytes: 2968834 InPRoc: 0, OutPRoc: 0, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0 OAM F5 cells sent: 0, OAM cells received: 0 Status: ACTIVETable 17 describes the significant fields in the sample output.
show controllers vsi control-interface
To display information about an ATM interface that controls an external switch, use the show controllers vsi control-interface command in EXEC mode.
show controllers vsi control-interface [interface]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show controllers vsi control-interface command:
Router# show controllers vsi control-interfaceInterface: ATM2/0 Connections: 14The display shows the number of cross-connects currently on the switch that were established by the MPLS LSC through the VSI over the control interface.
Related Commands
show controllers vsi descriptor
To display information about a switch interface discovered by the MPLS label switch controller (LSC) through the Virtual Switch Interface (VSI), use the show controllers vsi descriptor command in EXEC mode. You can specify an interface by its (switch-supplied) physical descriptor.
show controllers vsi descriptor [descriptor]
Syntax Description
descriptor
(Optional) Physical descriptor. For the Cisco BPX switch, the physical descriptor has the following form: slot.port.0
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Per-interface information includes the following:
•
•
•
•
•
•
•
•
Similar information is displayed when you enter the show controllers xtagatm command. However, you must specify an IOS interface name instead of a physical descriptor.
Examples
The following is sample output from the show controllers vsi descriptor command:
Router# show controllers vsi descriptor 12.2.0Phys desc: 12.2.0Log intf: 0x000C0200 (0.12.2.0)Interface: XTagATM0IF status: up IFC state: ACTIVE Min VPI: 1 Maximum cell rate: 10000 Max VPI: 259 Available channels: 2000 Min VCI: 32 Available cell rate (forward): 10000 Max VCI: 65535 Available cell rate (backward): 10000Table 18 describes the significant fields in the sample command output shown above.
Related Commands
show controllers vsi session
To display information about all sessions with Virtual Switch Interface (VSI) slaves, use the show controllers vsi session command in EXEC mode.
show controllers vsi session [session-num [interface interface]]
Note
Syntax Description
session-num
(Optional) The session number.
interface interface
(Optional) The VSI control interface.
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
If a session number and an interface are specified, detailed information on the individual session is presented. If the session number is specified, but the interface is omitted, detailed information on all sessions with that number is presented.
Examples
The following is sample output from the show controllers vsi session command:
Router# show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Session StateATM0/0 0 1 0/40 0/1 ESTABLISHED ATM0/0 1 2 0/41 0/2 ESTABLISHED ATM0/0 2 3 0/42 0/3 DISCOVERY ATM0/0 3 4 0/43 0/4 RESYNC-STARTING ATM0/0 4 5 0/44 0/5 RESYNC-STOPPING ATM0/0 5 6 0/45 0/6 RESYNC-UNDERWAY ATM0/0 6 7 0/46 0/7 UNKNOWN ATM0/0 7 8 0/47 0/8 UNKNOWN ATM0/0 8 9 0/48 0/9 CLOSING ATM0/0 9 10 0/49 0/10 ESTABLISHED ATM0/0 10 11 0/50 0/11 ESTABLISHED ATM0/0 11 12 0/51 0/12 ESTABLISHEDTable 19 describes the significant fields in the sample command output shown above.
In the following example, session number 9 is specified with the show controllers vsi session command:
Router# show controllers vsi session 9Interface: ATM1/0 Session number: 9VCD: 10 VPI/VCI: 0/49Switch type: BPX Switch id: 0Controller id: 1 Slave id: 10Keepalive timer: 15 Powerup session id: 0x0000000ACfg/act retry timer: 8/8 Active session id: 0x0000000AMax retries: 10 Ctrl port log intf: 0x000A0100Trap window: 50 Max/actual cmd wndw: 21/21Trap filter: all Max checksums: 19Current VSI version: 1 Min/max VSI version: 1/1Messages sent: 2502 Inter-slave timer: 4.000Messages received: 2502 Messages outstanding: 0Table 20 describes the significant fields in the sample command output shown above.
Related Commands
show controllers vsi status
To display a one-line summary of each VSI-controlled interface, use the show controllers vsi status command in EXEC mode.
show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Related Commands
EXEC
Command History
Usage Guidelines
If an interface has been discovered by the LSC, but no extended MPLS ATM interface has been associated with it through the extended-port interface configuration command, then the interface name is marked <unknown>, and interface status is marked n/a.
Examples
The following is sample output from the show controllers vsi status command:
Router# show controllers vsi statusInterface Name IF Status IFC State Physical Descriptor switch control port n/a ACTIVE 12.1.0 XTagATM0 up ACTIVE 12.2.0 XTagATM1 up ACTIVE 12.3.0 <unknown> n/a FAILED-EXT 12.4.0Table 21 describes the significant fields in the sample command output shown above.
show controllers vsi traffic
To display traffic information about VSI-controlled interfaces, VSI sessions, or VCs on VSI-controlled interfaces, use the show controllers vsi traffic command in EXEC mode.
show controllers vsi traffic [{descriptor descriptor | session session-num | vc [descriptor descriptor [vpi vci ]]}]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
The VPI range of values was extended to 4095.
Usage Guidelines
If none of the keywords is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX switch, the physical descriptor has the form:
slot.port. 0
If a session number is specified, the output displays VSI protocol traffic by message type. The VC traffic display is also displayed by the show xtagatm cross-connect traffic descriptor command.
Examples
The following is sample output from the show controllers vsi traffic command:
Router# show controllers vsi trafficPhys desc: 10.1.0Interface: switch control portIF status: n/aRx cells: 304250 Rx cells discarded: 0Tx cells: 361186 Tx cells discarded: 0Rx header errors: 4294967254 Rx invalid addresses (per card): 80360Last invalid address: 0/53Phys desc: 10.2.0Interface: XTagATM0IF status: upRx cells: 202637 Rx cells discarded: 0Tx cells: 194979 Tx cells discarded: 0Rx header errors: 4294967258 Rx invalid addresses (per card): 80385Last invalid address: 0/32Phys desc: 10.3.0Interface: XTagATM1IF status: upRx cells: 182295 Rx cells discarded: 0Tx cells: 136369 Tx cells discarded: 0Rx header errors: 4294967262 Rx invalid addresses (per card): 80372Last invalid address: 0/32Table 22 describes the significant fields in the sample command output shown above.
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
Router# show controllers vsi traffic session 9Sent ReceivedSw Get Cnfg Cmd: 3656 Sw Get Cnfg Rsp: 3656Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1Sw End Resync Cmd: 1 Sw End Resync Rsp: 1Ifc Getmore Cnfg Cmd: 1 Ifc Getmore Cnfg Rsp: 1Ifc Cnfg Trap Rsp: 4 Ifc Cnfg Trap: 4Ifc Get Stats Cmd: 8 Ifc Get Stats Rsp: 8Conn Cmt Cmd: 73 Conn Cmt Rsp: 73Conn Del Cmd: 50 Conn Del Rsp: 0Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0Gen Err Rsp: 0 Gen Err Rsp: 0unused: 0 unused: 0unknown: 0 unknown: 0TOTAL: 3795 TOTAL: 3795Table 23 describes the significant fields in the sample command output shown above.
show controllers xtagatm
To display information about an extended MPLS ATM (XtagATM) interface controlled through the Virtual Switch Interface (VSI) protocol, use the show controllers xtagatm command in EXEC mode.
show controllers xtagatm if-num
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
Per-interface information includes the following:
•
•
•
•
•
•
•
•
Examples
In this example, the sample output is from the show controllers xtagatm command specifying interface 0.
Router# show controllers xtagatm 0Interface XTagATM0 is up Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI1) Control interface ATM1/0 is up Physical descriptor is 10.2.0 Logical interface 0x000A0200 (0.10.2.0) Oper state ACTIVE, admin state UP VPI range 1-255, VCI range 32-65535 VPI is not translated at end of link Tag control VC need not be strictly in VPI/VCI range Available channels: ingress 30, egress 30 Maximum cell rate: ingress 300000, egress 300000 Available cell rate: ingress 300000, egress 300000 Endpoints in use: ingress 7, egress 8, ingress/egress 1 Rx cells 134747 rx cells discarded 0, rx header errors 0 rx invalid addresses (per card): 52994 last invalid address 0/32 Tx cells 132564 tx cells discarded: 0Table 24 describes the significant fields in the sample command output shown above.
Related Commands
Displays information about a switch interface discovered by the MPLS LSC through the VSI.
show interface xtagatm
To display information about an extended MPLS ATM (XtagATM) interface, use the show interface xtagatm command in EXEC mode.
show interface xtagatm if-num
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
XtagATM interfaces are virtual interfaces that are created on first reference like tunnel interfaces. XtagATM interfaces are similar to ATM interfaces, except that the former only supports LC-ATM encapsulation.
Examples
The following is sample output from the show interface xtagatm command:
Router# show interface xtagatm0XTagATM0 is up, line protocol is upHardware is Tag-Controlled Switch PortInterface is unnumbered. Using address of Loopback0 (12.0.0.17)MTU 4470 bytes, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255Encapsulation ATM Tagswitching, loopback not setEncapsulation(s): AAL5Control interface: ATM1/0, switch port: bpx 10.29 terminating VCs, 16 switch cross-connectsSwitch port traffic:129302 cells input, 127559 cells outputLast input 00:00:04, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/0, 0 drops; input queue 0/75, 0 dropsTerminating traffic:5 minute input rate 1000 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 1 packets/sec61643 packets input, 4571695 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort53799 packets output, 4079127 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffers copied, 0 interrupts, 0 failuresTable 25 describes the significant fields in the sample command output shown above.
Related Commands
show mpls atm-ldp bindings
To display the requested entries from the ATM label distribution protocol (LDP) label bindings database, use the show mpls atm-ldp bindings command in EXEC mode.
show mpls atm-ldp bindings [A.B.C.D {mask | length}]
[local-label vpi vci] [remote-label vpi vci] [neighbor atm slot/subslot/port] [vc-merged] [path]Syntax Description
Defaults
Displays all database entries.
Command Modes
EXEC
Command History
Usage Guidelines
The display output can show the entire database or a subset of entries based on the prefix, the VC label value, or an assigning interface.
Examples
The following is sample output from the show mpls atm-ldp bindings command:
Router# show mpls atm-ldp bindingsDestination: 10.13.13.6/32Headend Router ATM1/0.1 (2 hops) 1/33 Active, VCD=8, CoS=availableHeadend Router ATM1/0.1 (2 hops) 1/34 Active, VCD=9, CoS=standardHeadend Router ATM1/0.1 (2 hops) 1/35 Active, VCD=10, CoS=premiumHeadend Router ATM1/0.1 (2 hops) 1/36 Active, VCD=11, CoS=controlDestination: 192.168.0.0/8Headend Router ATM1/0.1 (1 hop) 1/37 Active, VCD=4, CoS=availableHeadend Router ATM1/0.1 (1 hop) 1/34 Active, VCD=5, CoS=standardHeadend Router ATM1/0.1 (1 hop) 1/35 Active, VCD=6, CoS=premiumHeadend Router ATM1/0.1 (1 hop) 1/36 Active, VCD=7, CoS=controlDestination: 10.0.0.18/32Tailend Router ATM1/0.1 1/33 Active, VCD=8The following is sample output from the show mpls atm-ldp bindings command with the path keyword:
Router# show mpls atm-ldp bindings 10.0.2.115 32 pathDestination: 10.0.2.115/32Headend Router Switch1.1 (2 hops) 0/39 Active, VCD=9, CoS=availablePath: 10.0.2.102* 10.0.3.42 10.0.2.115Headend Router Switch1.1 (2 hops) 0/41 Active, VCD=8, CoS=premiumPath: 10.0.2.102* 10.0.3.42 10.0.2.115Headend Router Switch1.1 (2 hops) 0/43 Active, VCD=7, CoS=controlPath: 10.0.2.102* 10.0.3.42 10.0.2.115Table 26 describes the significant fields shown in the display.
Related Commands
Displays the number of bindings waiting for label assignments for a remote MPLS ATM switch.
show mpls atm-ldp bindwait
To display the number of bindings waiting for label assignments from a remote MPLS ATM switch, use the show mpls atm-ldp bindwait command in EXEC mode.
show mpls atm-ldp bindwait
Syntax Description
This command has no keywords or arguments.
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Examples
The following shows a sample display using this command:
Router# show mpls atm-ldp bindwaitIf everything is working properly, this command does not display any output.
Related Commands
show mpls atm-ldp capability
To display the Multiprotocol Label Switching (MPLS) ATM capabilities negotiated with Label Distribution Protocol (LDP) neighbors for label-controlled ATM (LC-ATM) interfaces, use the show mpls atm-ldp capability command in privileged EXEC mode.
show mpls atm-ldp capability
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When two label switch routers (LSRs) establish an LDP session, they negotiate parameters for the session, such as the range of virtual path identifiers (VPIs) and virtual channel identifiers (VCIs) that will be used as labels.
This command displays the MPLS ATM capabilities negotiated by LDP or the Tag Distribution Protocol (TDP).
Examples
The following is sample output from the show mpls atm-ldp capability command:
Router# show mpls atm-ldp capabilityVPI VCI Alloc Odd/Even VC MergeATM0/1/0 Range Range Scheme Scheme IN OUTNegotiated [100 - 101] [33 - 1023] UNIDIR - -Local [100 - 101] [33 - 16383] UNIDIR EN ENPeer [100 - 101] [33 - 1023] UNIDIR - -VPI VCI Alloc Odd/Even VC MergeATM0/1/1 Range Range Scheme Scheme IN OUTNegotiated [201 - 202] [33 - 1023] BIDIR - -Local [201 - 202] [33 - 16383] UNIDIR ODD NO NOPeer [201 - 202] [33 - 1023] BIDIR EVEN - -Table 27 describes the fields shown in the display.
Related Commands
mpls ldp atm vc-merge
Controls whether ATM-virtual circuit merge (multipoint-to-point) is supported for unicast label virtual circuits.
show mpls atm-ldp summary
To display summary information about all the entries in the ATM label binding database, use the show mpls atm-ldp summary command in privileged EXEC mode.
show mpls atm-ldp summary
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display dynamic ATM accounting information.
Examples
The following shows sample output from the show mpls atm-ldp summary command:
Router# show mpls atm-ldp summaryTotal number of destinations: 406ATM label bindings summaryinterface total active local remote Bwait Rwait IFwaitATM0/0/0 406 406 404 2 0 0 0ATM0/0/1 406 406 3 403 0 0 0Table 28 describes the significant fields shown in the display.
Related Commands
show mpls atm-ldp bindings
Displays the requested entries from the ATM LDP label binding database.
show xtagatm cos-bandwidth-allocation xtagatm
To display information about class of service (CoS) bandwidth allocation on extended MPLS ATM (XtagATM) interfaces, use the show xtagatm cos-bandwidth-allocation xtagatm command in EXEC mode.
show xtagatm cos-bandwidth-allocation xtagatm [interface number]
Syntax Description
Defaults
Available 50%, control 50%.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
Use this command to display CoS bandwidth allocation information for the following CoS traffic categories:
•
•
•
•
Examples
The following example shows output from this command:
Router# show xtagatm cos-bandwidth-allocation xtagatm 123CoS Bandwidth allocationavailable 25%standard 25%premium 25%control 25%show xtagatm cross-connect
To display information about the label switch controller (LSC) view of the cross-connect table on the remotely controlled ATM switch, use the show xtagatm cross-connect command in EXEC mode.
show xtagatm cross-connect [traffic] [{interface interface [vpi vci] |
descriptor descriptor [vpi vci]]Syntax Description
Defaults
This command has no default behavior or values.
Related Commands
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Examples
Each connection is listed twice in the output from the show xtagatm cross-connect command, because it shows each interface that is linked by the connection.
The following is sample output from the show xtagatm cross-connect command:
Router# show xtagatm cross-connectPhys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State10.1.0 1/37 -> 10.3.0 1/35 UP 10.1.0 1/34 -> 10.3.0 1/33 UP 10.1.0 1/33 <-> 10.2.0 0/32 UP 10.1.0 1/32 <-> 10.3.0 0/32 UP 10.1.0 1/35 <- 10.3.0 1/34 UP 10.2.0 1/57 -> 10.3.0 1/49 UP 10.2.0 1/53 -> 10.3.0 1/47 UP 10.2.0 1/48 <- 10.1.0 1/50 UP 10.2.0 0/32 <-> 10.1.0 1/33 UP 10.3.0 1/34 -> 10.1.0 1/35 UP 10.3.0 1/49 <- 10.2.0 1/57 UP 10.3.0 1/47 <- 10.2.0 1/53 UP 10.3.0 1/37 <- 10.1.0 1/38 UP 10.3.0 1/35 <- 10.1.0 1/37 UP 10.3.0 1/33 <- 10.1.0 1/34 UP 10.3.0 0/32 <-> 10.1.0 1/32 UPTable 29 describes the significant fields in the sample command output shown above.
A sample of the detailed command output provided for a single endpoint is shown below.
Router# show xtagatm cross-connect descriptor 12.1.0 1 42Phys desc: 12.1.0Interface: n/aIntf type: switch control portVPI/VCI: 1/42X-Phys desc: 12.2.0X-Interface: XTagATM0X-Intf type: extended tag ATMX-VPI/VCI: 2/38Conn-state: UPConn-type: input/outputCast-type: point-to-pointRx service type: MPLS COS 0Rx cell rate: n/aRx peak cell rate: 10000Tx service type: MPLS COS 0Tx cell rate: n/aTx peak cell rate: 10000Table 30 describes the significant fields in the sample command output shown above.
show xtagatm vc
To display information about terminating virtual circuits (VCs) on extended MPLS ATM (XtagATM) interfaces, use the show xtagatm vc command in EXEC mode.
show xtagatm vc [vcd [interface]]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the MPLS IETF terminology.
Usage Guidelines
The columns marked VCD, VPI, and VCI display information for the corresponding private VC on the control interface. The private VC connects the XtagATM VC to the external switch. It is termed private because its VPI and VCI are only used for communication between the MPLS LSC and the switch, and it is different from the VPI and VCI seen on the XtagATM interface and the corresponding switch port.
Examples
The following is sample output from the show xtagatm vc command.
Router# show xtagatm vcAAL / Control Interface Interface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM0 1 0 32 PVC AAL5-SNAP 2 0 33 ACTIVEXTagATM0 2 1 33 TVC AAL5-MUX 4 0 37 ACTIVEXTagATM0 3 1 34 TVC AAL5-MUX 6 0 39 ACTIVETable 31 describes the significant fields in the sample command output shown above.
Related Commands
Displays information about private ATM VCs.
Displays information about remotely connected ATM switches.
tag-control-protocol vsi
To configure the use of Virtual Switch Interface (VSI) on a particular master control port, use the tag-control-protocol vsi command in interface configuration mode. To disable VSI, use the no form of this command.
tag-control-protocol vsi [base-vc vpi vci] [delay seconds] [id controller-id] [keepalive timeout] [nak [basic | extended]] [retry timeout-count] [slaves slave-count]
no tag-control-protocol vsi [base-vc vpi vci] [delay seconds] [id controller-id] [keepalive timeout] [nak [basic | extended]] [retry timeout-count] [slaves slave-count]
Syntax Description
Defaults
VSI is disabled.
Command Modes
Interface configuration
Command History
12.0(5)T
This command was introduced.
12.2(15)T
The delay keyword was added.
12.3(2)T
The nak keyword was added.
Usage Guidelines
•
•
–
–
–
The VSI remains continuously active (that is, the VSI does not shut down and then reactivate) if you reenter the tag-control-protocol vsi command with only one or both of the following options:
–
–
–
In either case, if you reenter the tag-control-protocol vsi command, this causes the specified options to take on the newly specified values; the other options retain their previous values. To restore default values to all the options, enter the no tag-control-protocol command, followed by the tag-control-protocol vsi command.
Examples
The following example shows how to configure the VSI driver on the control interface:
Router(config)# interface atm 0/0Router(config-if)# tag-control-protocol vsi base-vc 0 51The following example enables extended NAK support:
Router(config-if)# tag-control-protocol vsi nak extended
The following example shows that extended NAK support is enabled, as shown by the bold output:
Router# show running-config interface atm0/0Building configuration...Current configuration : 113 bytesinterface ATM0/0no ip addressshutdownlabel-control-protocol vsi nak extendedno atm ilmi-keepaliveendThe show controllers vsi session command also indicates that extended NAK support is enabled, as shown by the bold output:
Router# show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Session StateATM0/0 0 1 0/40 0/0 UNKNOWNATM0/0 1 2 0/41 0/0 UNKNOWNATM0/0 2 3 0/42 0/0 UNKNOWNATM0/0 3 4 0/43 0/0 UNKNOWNATM0/0 4 5 0/44 0/0 UNKNOWNATM0/0 5 6 0/45 0/0 UNKNOWNATM0/0 6 7 0/46 0/0 UNKNOWNATM0/0 7 8 0/47 0/0 UNKNOWNATM0/0 8 9 0/48 0/0 UNKNOWNATM0/0 9 10 0/49 0/0 UNKNOWNATM0/0 10 11 0/50 0/0 UNKNOWNATM0/0 11 12 0/51 0/0 UNKNOWNATM0/0 12 13 0/52 0/0 UNKNOWNATM0/0 13 14 0/53 0/0 UNKNOWNExtended NAK support is enabled on LSCGlossary
The terms in this glossary are defined in an MPLS context, rather than a general usage context.
AIP—ATM Interface Processor. An ATM interface for Cisco 7000 series routers designed to minimize performance bottlenecks at the user-network interface (UNI).
Alien Port Adapter—A dual-wide port adapter for the Cisco 7200 router. The Alien Port Adapter is ABR-ready and supports traffic shaping.
ATM Edge LSR—A router that is connected to the ATM-LSR cloud through LSC-ATM interfaces. The ATM Edge LSR adds labels to unlabeled packets and strips labels from labeled packets.
ATM Lite—Entry-level port adapter (higher performance than the AIP) for 7200 routers. The ATM Lite does not support traffic shaping or ABR.
ATM-LSR—A label switch router with several LSC-ATM interfaces. The router forwards the cells among these interfaces using labels carried in the VPI/VCI field of the cells.
BPX—Broadband Packet Exchange. A carrier-quality switch with trunk and CPU hot standby redundancy.
BXM—Broadband Switch Module. An ATM port card for the Cisco BPX switch.
CAR—committed access rate. CAR is the main feature supporting packet classification. CAR uses the type of service (ToS) bits in the IP header to classify packets. You can use the CAR classification commands to classify and reclassify a packet.
Controlled ATM Switch—An ATM switch that is controlled by an LSC.
CoS—class of service. A feature that provides scalable, differentiated types of service across an MPLS network.
downstream on demand—Indicates that the downstream-on-demand method of label distribution is being used for this LDP session. When the downstream-on-demand method is used, an LSR advertises its locally assigned (incoming) labels to its LDP peer device only when the peer device asks for them.
DWFQ—VIP-Distributed WFQ (weighted fair queuing).
DWRED—VIP-Distributed WRED (weighted random early detection).
extended label ATM interface—A type of interface supported by the remote ATM switch driver and a particular switch-specific driver that supports MPLS over an ATM interface on a remotely controlled switch.
external ATM interface—One of the interfaces on the controlled ATM switch other than the switch control port. It is also referred to as an exposed ATM interface, because it is available for connections outside of the label-controlled switch.
IP Precedence—A 3-bit value in the type of service (ToS) byte used for assigning precedence to IP packets.
label—A short fixed-length label that tells switching nodes how the data (packets or cells) should be forwarded.
label controlled switch—The label switch controller and the controlled ATM switch that it controls, viewed together as a unit.
label imposition—The act of putting the first label on a packet.
label switch—A node that forwards units of data (packets or cells) on the basis of labels.
LBR—label bit rate. Service category defined by this document for label-VC traffic. Link and per-VC bandwidth sharing may be controlled by relative bandwidth configuration at the edge and each switch along a label-VC. No ATM traffic-related parameters specified.
LC-ATM (label-controlled ATM) interface—An MPLS interface in which labels are carried in the VPI or VCI fields of the ATM cells and in which VC connections are established under the control of MPLS software.
LFIB—Label forwarding information base. A data structure and way of managing forwarding in which destinations and incoming labels are associated with outgoing interfaces and labels.
LSC—label switch controller. A Cisco IOS platform that runs the generic MPLS software and that can control the operation of an external ATM (or other type of) switch, making the interfaces of the latter appear externally as XtagATM interfaces.
LSP—label switched path. A configured connection between two routers, using MPLS to carry the packets.
LSR—label switching router. A Layer 3 router that forwards a packet based on the value of a label encapsulated in the packet.
LVC—label virtual circuit. A virtual circuit (VC) established under the control of MPLS. An LVC is neither a PVC nor an SVC. The LVC must traverse only a single hop in a label-switched path (LSP), but the LVC may traverse several ATM hops only if the LVC exists within a VP tunnel.
master control port—A physical interface on an MPLS LSC that is connected to one end of a slave control link.
MPLS—Multiprotocol Label Switching. An emerging industry standard on which label switching is based.
PNNI—Private Network-Network Interface.
PVC—permanent virtual circuit (or connection). A virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and tear down in situations where certain virtual circuits must exist all the time. In ATM terminology, called a permanent virtual connection. Compare with SVC. See also virtual circuit.
PVP—permanent virtual path. A virtual path that consists of PVCs. See also PVC and virtual path.
QoS—quality of service. A measurement of performance for a transmission system that reflects its transmission quality and service availability.
RED—random early detection. Congestion avoidance algorithm in which a small percentage of packets are dropped when congestion is detected and before the queue in question overflows completely.
remote ATM switch driver—A set of interfaces that allows Cisco IOS software to control the operation of a remote ATM switch through a control protocol, such VSI.
ships in the night mode—The ability to support both MPLS functions and ATM forum protocols on the same physical interface, or on the same router or switch platform. In this mode, the two protocol stacks operate independently.
Switch control port—An interface that uses an MPLS LSC to control the operation of a controlled ATM switch (for example, VSI). The protocol runs on an ATM link.
SVC—switched virtual circuit. Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in situations where data transmission is sporadic. See also virtual circuit. Called a switched virtual connection in ATM terminology. Compare with PVC.
ToS—type of service. A byte in the IPv4 header.
VCC—virtual channel connection. Logical circuit, made up of VCLs, that carries data between two end points in an ATM network. Sometimes called a virtual circuit connection. See also VCL and VPI.
VCI—virtual channel identifier. 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. ATM switches use the VPI/VCI fields to identify the next network VCL that a cell needs to transit on its way to its final destination. The function of the VCI is similar to that of the DLCI in Frame Relay. Compare with DLCI.
VCL—virtual channel link. A connection between two ATM devices.
virtual circuit—Logical circuit created to ensure reliable communication between two network devices. A virtual circuit is defined by a VPI/VCI pair, and can be either permanent (PVC) or switched (SVC). Virtual circuits are used in Frame Relay and X.25. In ATM, a virtual circuit is called a virtual channel. Sometimes abbreviated VC.
VNNI—Virtual Network-Network Interface.
VPC—virtual path connection. Grouping of VCCs that share one or more contiguous VPL. See also VCC and VPL.
VPI—virtual path identifier. An 8-bit field in the header of an ATM cell. The VPI, together with the VCI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. ATM switches use the VPI/VCI fields to identify the next VCL that a cell needs to transit on its way to its final destination. The function of the VPI is similar to that of the DLCI in Frame Relay.
VPN—virtual private network. A network that enables IP traffic to use tunneling to travel securely over a public TCP/IP network.
VSI—Virtual Switch Interface. The protocol that enables an MPLS LSC to control an ATM switch over an ATM link.
VSI master—A VSI master process implementing the master side of the VSI protocol in a VSI controller. Sometimes the whole VSI controller is referred to as a "VSI Master," but this is not strictly correct.
1. A device that controls a VSI switch, for example, a VSI Label Switch Controller.
2. A process implementing the master side of the VSI protocol.
VSI slave—A VSI slave is either of the following definitions:
1. A switch (in the "Single Slave model") or a port card (in the "Multiple Slave Model") that implements the VSI.
2. A process implementing the slave side of the VSI protocol.
WEPD—Weighted Early Packet Discard. A variant of EPD used by some ATM switches for discarding a complete AAL5 frame when a threshold condition, such as imminent congestion, is met. EPD prevents congestion that would otherwise jeopardize the ability of the switch to properly support existing connections with a guaranteed service.
WRED—weighted random early detection. A variant of RED in which the probability of a packet being dropped depends on its IP Precedence, CAR marking, or MPLS CoS (as well as other factors in the RED algorithm).
WFQ—weighted fair queuing. A queue management algorithm that provides a certain fraction of link bandwidth to each of several queues, based on relative bandwidth applied to each of the queues.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)
