Table of Contents
MPLS Label Switch Controller Enhancements
Feature Overview
Platforms Supported by MPLS LSC
Supported Standards, MIBs, and RFCs
Configuration Tasks
Configuration Examples
Command Reference
extended-port
interface XTagATM
show atm vc
show interface XTagATM
show controllers XTagATM
show controllers vsi control-interface
show controllers vsi descriptor
show controllers vsi session
show controllers vsi status
show controllers vsi traffic
show tag-switching atm-tdp bindings
show tag-switching atm-tdp bindwait
show xtagatm cos-bandwidth-allocation XTagATM
show xtagatm cross-connect
show xtagatm vc
tag-control-protocol vsi
tag-switching atm control-vc
tag-switching atm cos
tag-switching atm disable-headend-vc
tag-switching atm vpi
tag-switching atm vp-tunnel
Debug Commands
debug tag-switching xtagatm cross-connect
debug tag-switching xtagatm errors
debug tag-switching xtagatm events
debug tag-switching xtagatm vc
debug vsi api
debug vsi errors
debug vsi events
debug vsi packets
debug vsi param-groups
glossary
A
B
C
D
E
I
L
M
Q
R
S
T
V
W
MPLS Label Switch Controller Enhancements
This document describes the Cisco MPLS (multiprotocol label switching) Label Switch Controller (LSC). It describes the MPLS LSC, identifies the platforms supported by the MPLS LSC, provides configuration examples for MPLS LSC components, and describes related IOS command language interpreter (CLI) commands that can be used with the supported platforms.
This document includes the following major sections:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Feature Overview
The label switch controller (LSC), combined with the Cisco BPX 8650 IP+ATM switch, supports scalable integration of IP services over an ATM network. The MPLS LSC enables the Cisco BPX 8650 to:
- Participate in an MPLS network
- Directly peer with IP routers
- Support the IP features in Cisco Internetwork Operating System (IOS) software
The MPLS LSC supports highly scalable integration of MPLS (IP+ATM) services by using a direct peer relationship between the Cisco BPX 8650 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 services over ATM networks using Cisco BPX 8650 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:
- Run applications over any combination of Layer 2 technologies
- Support any Layer 3 protocol while scaling the network to meet future needs
By deploying the MPLS LSC across large enterprise networks or wide area networks, customers can:
- Save money by using existing ATM and routing infrastructures
- Grow revenue using MPLS-enabled services
- Increase productivity through enhanced network scalability and performance
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 MPLS 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
Referring to Figure 1, note that the following devices can function as an MPLS LSC:
- Cisco 7200 series router
- Cisco 7500 series router
- Cisco 6400 Universal Access Concentrator (UAC)
Note also from Figure 1 that a Cisco BPX 8600 Service Node (or a slave ATM device) can function as the controlled ATM switch.
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 outline 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 LC-ATM interfaces at this external boundary. The MPLS LSC can incorporate other label controlled or non-label controlled router interfaces.
Controlled ATM Switch Ports Used as Router Interfaces
In the LSC, the LC-ATM ports on the controlled ATM switch 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 which 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 interface configuration command.
Figure 2 Typical MPLS LSC and BPX Configuration
Observe from Figure 2 that:
- An additional port on the Cisco BPX switch (port 12.1) acts as the switch control port
- An ATM interface (ATM1/0) on the MPLS LSC acts as the master control port
Virtual Trunking
Virtual trunks provide connectivity for Cisco WAN MPLS switches through an ATM cloud, as shown in Figure 3. Since several virtual trunks can be configured across a given physical trunk, virtual trunks provide a cost effective means of connecting across an entire ATM network, because each virtual trunk typically consumes only a part of the resources of the physical trunk.
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 3 shows three Cisco WAN MPLS switching networks, each connected to an ATM network by means of a physical line. The ATM network is shown linking all three of these subnetworks to every other subnetwork with a full meshed network of virtual trunks. In this example, each physical interface is configured with two virtual trunks.
Figure 3 Typical ATM Hybrid Network Using Virtual Trunks
Benefits of Virtual Trunking
Virtual trunks provide the following benefits:
- Reduced costs—By sharing the resources of a single physical trunk among a number of virtual (logical) trunks, each of the virtual trunks provided by the public carrier needs to be assigned only as much bandwidth as needed for that interface, rather than the full T3, E3, OC3, or OC12 bandwidth of an entire physical trunk.
- Migration of MPLS services into existing networks—VSI virtual trunks allow MPLS services to be carried over part of a network that does not support MPLS services. The part of the network that does not support such services may be a public ATM network, for example, that consists of switches that are not MPLS-enabled.
MPLS Configuration
A virtual trunk number (slot number.port number.trunk number) is used to differentiate the virtual trunks found within a physical trunk port. In Figure 4, 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 4 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 tag-switching atm vp-tunnel vpi. This VPI should match the VPI in the ATM network. The LVCs are generated inside this VP, and this VP carries the LVCs and their traffic across the network.
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.
Virtual Trunk Features
The maximum number of virtual trunks that can be configured per card equals the number of virtual interfaces (VIs) on the BPX. The BXM supports 31 virtual interfaces; hence, it supports up to 31 virtual trunks. Accordingly, you can have interfaces starting from XtagATM411 to XtagATM4131 on the same physical interface.
Using the MPLS LSC as Label Edge Device
As a label edge device, you can use the MPLS LSC to:
- Function simultaneously as a controller for an ATM switch and as a label edge device. You can forward traffic between a router interface and an LC-ATM interface on the controlled switch, as well as between two LC-ATM interfaces on the controlled switch.
- Perform the imposition and removal of labels and serve as the headend or tailend of a label-switched path tunnel. However, when the MPLS LSC acts as a label edge device, it is limited by the capabilities of its control link with the switch, as noted below:
-
- Total throughput between all other router interfaces and switch interfaces is limited by the bandwidth of the control link (that is, OC-3c, 155 Mbps).
- Label space for LSC-terminated VCs is limited by the number of VCs supported on the control link.
 |
Note A Cisco 6400 UAC with an NRP configured to function as an LSC should have MPLS edge LSR functionality disabled. Refer to the "tag-switching atm disable-headend-vc" section for information about how to disable MPLS edge LSR functionality using this command. An NRP LSC should only support transit Label Switch Paths through the controlled ATM switch under VSI control. |
Cisco 6400 UAC Operating as an MPLS LSC
You can configure the Cisco 6400 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.
Cisco 6400 UAC Architectural Overview
A Cisco 6400 UAC that incorporates the following components shown can operate as an MPLS LSC in your network:
- Node Switch Processor (NSP)— The NSP incorporates an ATM switch fabric, enabling the Cisco 6400 UAC to function as an ATM label switch router (ATM LSR) in a network. The NSP manages all the external ATM interfaces for the Cisco 6400 UAC.
- Node Resource Processor (NRP)—An NRP included in a Cisco 6400 UAC chassis enables the device to function as an LSC. When used in this manner, however, you must not configure the NRP to perform any other functions.
The NRP contains internal ATM interfaces that enable it to be connected to the NSP. However, the NRP cannot directly access the external ATM interfaces of the Cisco 6400 UAC. Access to such external ATM interfaces is provided only by means of the NSP.
|
Note A Cisco 6400 UAC chassis can accommodate multiple NRPs, including one dedicated to MPLS LSC functions. Beyond this dedicated NRP, you can use additional NRPs to run MPLS and perform other networking services. However, you cannot use an additional NRP as an MPLS LSC. |
- ATM port adapter—The Cisco 6400 UAC must incorporate an ATM port adapter to provide external connectivity for the NSP.
Figure 5 shows the components that you can configure to enable the Cisco 6400 UAC to function as an MPLS LSC.
Figure 5 Cisco 6400 UAC Configured as an MPLS LSC
Configuring PVCs and PVPs in Cisco 6400 UAC NSP Used as an MPLS NRP LSC
The NRP controls the slave ATM switch by means of the Virtual Switch Interface (VSI) protocol. VSI operates over a manually configured PVC that is dedicated to the virtual circuits (VCs) used by the VSI control channel. In order for the NRP LSC to control an ATM switch through the VSI, control VCs need to be cross-connected from the BPX through the NSP to the NRP LSC. The BPX uses defined control VCs for each BXM slot of the BPX chassis, enabling the LSC to control external XTagATM interfaces through the VSI.
Table 1 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, and the NSP ATM port connected to this interface is the ATM interface that is cross-connected to ATM3/0/0. Because Figure 2 shows that the BXM slaves in BPX slots 6 and 12 are to be 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 1.
Table 1
VSI Interface Control PVCs for BPX VSI Slave Slots
| BPX VSI Slave Slot |
VSI Interface Control VC |
|
1
|
0/40
|
|
2
|
0/41
|
|
3
|
0/42
|
|
4
|
0/43
|
|
5
|
0/44
|
|
6
|
0/45
|
|
7
|
0/46
|
|
8
|
0/47
|
|
9
|
0/48
|
|
10
|
0/49
|
|
11
|
0/50
|
|
12
|
0/51
|
|
13
|
0/52
|
|
14
|
0/53
|
Figure 6 shows the functional relationships among the Cisco 6400 UAC hardware components and the PVPs that you can configure to support MPLS LSC functionality.
Figure 6 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 6). 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, several VPs must be defined. 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, four consecutive VPs must be configured. Furthermore, the selection of these VPs should be 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 "tag-switching atm vpi" for examples of how to configure edge LSRs; see the BPX command "cnfr" 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 6), the NRP is able to 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 6 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 is dependent 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 will be shown as a PVC on the LSC, as opposed to a LVC, when you execute the IOS CLI command "show xtagatm vc".
Basic MPLS LSC Operations
Figure 7 shows a Cisco 6400 UAC containing a single NRP that has been configured to perform basic MPLS LSC operations.
Figure 7 Typical Cisco 6400 UAC Configuration to Support MPLS LSC Functions
|
Note If the NRP incurs a fault that causes it to malfunction (in a single NRP configuration), the LVCs and routing paths pertaining to MPLS LSC functions are lost. |
|
Note The loopback addresses must be configured with a 32 bit mask and be included in the relevant IGP or BGP routing protocol, as shown in the following example:
ip address 192.103.210.5 255.255.255.255 |
Defining MPLS Control and IP Routing Paths
In the MPLS LSC topology shown in Figure 7, 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 7. 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 7.
Disabling Edge LVCs
By default, the NRP requests LVCs for the next hop devices (the LSRs shown in Figure 7). These LVCs, called headend LVCs, enable the NRP/ATM slave switch combination to operate as an edge label switch router (edge LSR). Because the NRP is dedicated to slave ATM switch control by default, the headend LVCs are not required.
|
Note A Cisco 6400 UAC with an NRP configured to function as an LSC should have MPLS edge LSR functionality disabled. An NRP LSC should only support transit Label Switch Paths through the controlled ATM switch under VSI control. (Refer to the command described in the section entitled "tag-switching atm disable-headend-vc" for information about how to disable MPLS edge LSR functionality. |
The tag-switching atm disable-headend-vc CLI command disables the default behavior of the NRP in setting up headend switch LVCs, thereby saving VC space over the VP between the NRP and the slave ATM switch that the NRP controls. In the absence of additional LVCs, data traffic follows the same path as that for control traffic.
Support for ATM Forum Protocols
You can connect the MPLS LSC to a network that is running ATM Forum protocols while the MPLS LSC simultaneously performs its functions. However, you must connect the ATM Forum network through a separate ATM interface (that is, not through the master control port).
Tag Switching and MPLS Terminology
Table 2 lists current tag switching terms and the equivalent MPLS terms now being used in this document.
Table 2
Equivalency Table for Tag Switching and MPLS Terms
| Old Tag Switching Terminology |
New MPLS IETF Terminology |
|
Tag Switching
|
MPLS, Multiprotocol Label Switching
|
|
Tag (short for Tag Switching)
|
MPLS
|
|
Tag (item or packet)
|
Label
|
|
TDP (Tag Distribution Protocol)
|
LDP (Label Distribution Protocol)
Cisco TDP and LDP (MPLS Label Distribution Protocol) are nearly identical in function, but use incompatible message formats and some different procedures. Cisco is changing from TDP to a fully compliant LDP.
|
|
Tag Switched
|
Label Switched
|
|
TFIB (Tag Forwarding Information Base)
|
LFIB (Label Forwarding Information Base)
|
|
TSR (Tag Switching Router)
|
LSR (Label Switching Router)
|
|
TSC (Tag Switch Controller)
|
LSC (Label Switch Controller)
|
|
ATM-TSR (ATM Tag Switch Router)
|
ATM-LSR (ATM Label Switch Router, such as the Cisco BPX 8650 switch)
|
|
TVC (Tag VC, Tag Virtual Circuit)
|
LVC (Label VC, Label Virtual Circuit)
|
|
TSP (Tag Switch Path)
|
LSP (Label Switch Path)
|
|
XTag ATM (extended Tag ATM port)
|
XmplsATM (extended MPLS ATM port)
|
MPLS LSC Benefits
By using the MPLS LSC, you can derive the following benefits:
- IP-ATM Integration—Enables ATM switches, including the Cisco BPX 8650 switch and Cisco BPX 8680 switch, to directly support advanced IP services and protocols, thereby reducing operational costs and bandwidth requirements, while at the same time decreasing time-to-market for new services.
- Explicit Routing—Provides Layer 2 VCs to gigabit router backbones and integrated IP+ATM environments, including support for explicit routing and provisioning of IP VPN services.
- Virtual Private Networks—Supports IP-based VPNs on either a Frame Relay/ATM backbone, an integrated IP-ATM backbone, or a gigabit router backbone.
Platforms Supported by MPLS LSC
You can use the following platforms in conjunction with the MPLS LSC:
- Cisco 7500 series routers—Support the following interfaces:
-
- ATM Interface Processor (AIP)
- Virtual Interface Processor (VIP)
- ATM Port Adapter (PA-A1 and PA-A3)
- Cisco 7200 series routers—Support the following interface:
-
- ATM Port Adapter (PA-A1 and PA-A3)
- Cisco 6400 Universal Access Concentrator—Supports the following interfaces:
-
- DS-3
- OC-3/STM-1
- OC-12/STM-4
Supported Standards, MIBs, and RFCs
- Standards—The MPLS LSC supports no new or modified standards.
- MIB—The MPLS LSC supports no new or modified MIBs.
- RFC—The MPLS LSC supports no new or modified RFCs.
Configuration Tasks
This section provides examples of configuration tasks for enabling MPLS LSC functionality.
Refer to the Cisco BPX 8600 Series documentation for BPX Service Node configuration examples.
Configuring MPLS on 72xx/75xx Series LSC-Controlled BPX Port
|
Command |
Purpose |
Step 1
|
Router(config)# interface loopback0 Router(config-if)# ip address 192.103.210.5 255.255.255.255 |
Enable a loopback interface. A loopback interface provides stable router and LDP identifiers.
|
Step 2
|
Router(config)# interface atm1/0 Router(config-if)# tag-control-protocol vsi |
Enable the VSI protocol on the control interface ATM1/0.
|
Step 3
|
Router(config-if)# interface XTagATM61 Router(config-if)# extended-port atm1/0 bpx 6.1 |
Configure MPLS on the extended label ATM interface by creating an extended label ATM (XTagATM) virtual interface and binding it to BPX port 6.1.
|
Step 4
|
Router(config-if)# ip unnumbered loopback0 Router(config-if)# tag-switching atm vpi 2-5 Router(config-if)# tag-switching ip |
Configure MPLS on the extended label ATM interface.
Limit the range so that the total number of VPIs does not exceed 4. For example:
tag-switching atm vpi 2-5
tag-switching atm vpi 10-13
|
Step 5
|
Router(config-if)# interface XTagATM122 Router(config-if)# extended-port atm1/0 bpx 12.2 |
Configure MPLS on the other extended label ATM interface by creating an extended label ATM (XTagATM) virtual interface and binding it to BPX port 12.2.
|
Step 6
|
Router(config-if)# ip unnumbered loopback0 Router(config-if)# tag-switching atm vpi 2-5 Router(config-if)# tag-switching ip |
Configure MPLS on the extended label ATM interface.
Limit the range so that the total number of VPIs does not exceed 4. For example:
tag-switching atm vpi 2-5
tag-switching atm vpi 10-13
|
Step 7
|
|
Enable Cisco Express Forwarding (CEF) switching.
|
|
Note If the LSC is a 75xx series router, the ip cef distributed command must be issued to configure the router. |
|
Note For Release 12.0(5)T, you must configure the XTagATM interfaces using the no ip route-cache cef command. |
Cisco 6400 UAC LSC Configuration
Configuring Cisco 6400 UAC NRP as an MPLS LSC
|
Command |
Purpose |
Step 1
|
Router(config)# interface loopback0 Router(config-if)# ip address 192.103.210.5 255.255.255.255 |
Enable a loopback interface. A loopback interface provides stable router and LDP identifiers.
|
Step 2
|
Router(config)# interface atm3/0/0 Router(config-if)# tag-control-protocol vsi |
Enable the VSI protocol on the control interface ATM3/0/0.
|
Step 3
|
Router(config-if)# interface XTagATM61 Router(config-if)# extended-port atm1/0 bpx 6.1 |
Configure MPLS on the extended label ATM interface by creating an extended label ATM (XTagATM) virtual interface and binding it to BPX port 6.1.
|
Step 4
|
Router(config-if)# ip unnumbered loopback0 Router(config-if)# tag-switching atm vpi 2-5 Router(config-if)# tag-switching ip |
Configure MPLS on the extended label ATM interface.
Limit the range so that the total number of VPIs does not exceed 4. For example:
tag-switching atm vpi 2-5
tag-switching atm vpi 10-13
|
Step 5
|
Router(config-if)# interface XTagATM122 Router(config-if)# extended-port atm1/0 bpx 12.2 |
Configure MPLS on the other extended label ATM interface by creating an extended label ATM (XTagATM) virtual interface and binding it to BPX port 12.2.
|
Step 6
|
Router(config-if)# ip unnumbered loopback0 Router(config-if)# tag-switching atm vpi 2-5 Router(config-if)# tag-switching ip |
Configure MPLS on the extended label ATM interface.
Limit the range so that the total number of VPIs does not exceed 4. For example:
tag-switching atm vpi 2-5
tag-switching atm vpi 10-13
|
Step 7
|
|
Enable Cisco Express Forwarding (CEF) switching.
|
Step 8
|
Router(config)# tag-switching atm disable-headend-vc |
Disable Headend VC label advertisement.
|
Configuring the Cisco 6400 UAC NSP for MPLS Connectivity to BPX
|
Command |
Purpose |
Step 1
|
3/0 NRP 00-0000-00 ....... |
Show the hardware connected to the Cisco 6400 UAC, inlcuding the position (3/0) of the NRP in the Cisco 6400 chassis, as shown in the sample output at the left.
|
Step 2
|
Switch(config)# interface atm3/0/0 |
Specify the ATM interface for which you want to configure PVCs and PVPs.
|
Step 3
|
atm pvc 0 40 interface ATM1/0/0 0 40
atm pvc 0 41 interface ATM1/0/0 0 41
atm pvc 0 42 interface ATM1/0/0 0 42
atm pvc 0 43 interface ATM1/0/0 0 43
atm pvc 0 44 interface ATM1/0/0 0 44
atm pvc 0 45 interface ATM1/0/0 0 45
atm pvc 0 46 interface ATM1/0/0 0 46
atm pvc 0 47 interface ATM1/0/0 0 47
atm pvc 0 48 interface ATM1/0/0 0 48
atm pvc 0 49 interface ATM1/0/0 0 49
atm pvc 0 50 interface ATM1/0/0 0 50
atm pvc 0 51 interface ATM1/0/0 0 51
atm pvc 0 52 interface ATM1/0/0 0 52
atm pvc 0 53 interface ATM1/0/0 0 53
|
Configure the PVC for the VSI control channel1, depending on which of the 14 slots in the Cisco BPX 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 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 51
Instead 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 0
|
Step 4
|
atm pvp 2 interface ATM1/0/0 2
atm pvp 3 interface ATM1/0/0 3
atm pvp 4 interface ATM1/0/0 4
atm pvp 5 interface ATM1/0/0 5
|
Configure the PVPs for the LVCs. For XtagATM interfaces, use the VPI range 2 through 5 (by issuing a tag-switching atm vpi 2-5 command). If you want to use some other VPI range, configure the PVPs accordingly.
|
1. Do not enable tag switching on this interface.
Verifying MPLS LSC Configuration
|
Command |
Purpose |
Step 1
|
Router# show controller vsi session |
Display the VSI session state.
|
Step 2
|
Router# show tag-switching interfaces |
Display the MPLS-enabled interface states.
|
Step 3
|
Router# show controllers vsi control-interface |
Display information about an ATM interface that controls an external ATM switch or VSI control interface.
|
Step 4
|
Router# show interface XTagATM |
Display information about an extended MPLS ATM interface.
|
Step 5
|
Router# show tag-switching tdp discovery |
Display information about the discovery of MPLS neighbors.
|
Step 6
|
Router# show tag-switching tdp neighbor |
Display information about the MPLS neighbor relationship.
|
Step 7
|
Router# show tag-switching atm capabilities |
Display information about negotiated of TDP or LDP control VPs.
|
Step 8
|
Router# show tag-switching atm summary |
Display summary information about the number of destination networks discovered via routing protocol and the LVCs created on each extended label ATM interface.
|
Configuration Examples
The following sections present typical network configurations for using MPLS LSC functionality.
Configuring ATM-LSRs
The network topology shown in Figure 8 incorporates two ATM-LSRs in an MPLS network. This topology includes two LSCs (Cisco 7200 routers), two BPX service nodes, and two edge LSRs (Cisco 7500 routers).
Figure 8 ATM-LSR Network Configuration Example
Based on Figure 8, the following configuration examples are provided:
Configuration for LSC1
ip address 192.103.210.5 255.255.255.255
extended-port ATM3/0 bpx 1.3
tag-switching atm vpi 2-15
extended-port ATM3/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for BPX1 and BPX2
cnfr 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 1.3 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Configuration for LSC2
ip address 142.2.143.22 255.255.255.255
extended-port ATM3/0/0 bpx 1.3
tag-switching atm vpi 2-15
extended-port ATM3/0/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for Edge LSR1
ip address 142.6.132.2 255.255.255.255
interface ATM2/0/0.5 tag-switching
tag-switching atm vpi 2-5
Configuration for Edge LSR2
ip address 142.6.142.2 255.255.255.255
interface ATM2/0.9 tag-switching
tag-switching atm vpi 2-5
Configuring Multi-VCs
When you configure multi-vc support, four label VCs for each destination are created by default. These four VCs are called:
- Standard (for class 0 and class 4 traffic)
- Available (for class 1 and class 5 traffic)
- Premium (for class 2 and class 6 traffic)
- Control (for class 3 and class 7 traffic)
This section provides examples for the following configurations, based on the sample network configuration shown earlier in Figure 8:
Configuration for LSC1
ip address 192.103.210.5 255.255.255.255
extended-port ATM3/0 bpx 1.3
tag-switching atm vpi 2-15
tag-switching atm cos available 25
tag-switching atm cos standard 25
tag-switching atm cos premium 25
tag-switching atm cos control 25
extended-port ATM3/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm cos available 20
tag-switching atm cos standard 30
tag-switching atm cos premium 25
tag-switching atm cos control 25
Configuration for BPX1 and BPX2
cnfr 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 1.3 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Configuration for LSC2
ip address 142.2.143.22 255.255.255.255
extended-port ATM3/0/0 bpx 1.3
tag-switching atm vpi 2-15
tag-switching atm cos available 25
tag-switching atm cos standard 25
tag-switching atm cos premium 25
tag-switching atm cos control 25
extended-port ATM3/0/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm cos available 20
tag-switching atm cos standard 30
tag-switching atm cos premium 25
tag-switching atm cos control 25
Configuration for Edge LSR1
ip address 142.6.132.2 255.255.255.255
interface ATM2/0/0.5 tag-switching
tag-switching atm vpi 2-5
tag-switching atm multi-vc
Configuration for Edge LSR2
ip address 142.2.142.2 255.255.255.255
interface ATM2/0.9 tag-switching
tag-switching atm vpi 2-5
tag-switching atm multi-vc
QoS Support
If LSC1 supports QoS, but LSC2 does not, LSC1 makes VC requests for the following default classes:
- Control=CoS3
- Standard=CoS1
LSC2 ignores the call field in the request and allocates two UBR label VCs.
If LSR1 supports QoS, but LSR2 does not, LSR2 receives the request to create multiple label VCs, but by default, creates class 0 only (UBR).
Configuring ATM-LSRs with a Cisco 6400 NRP Operating as LSC
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 9), 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 9 Cisco 6400 UAC NRP Operating as an LSC
Based on Figure 9, the following configuration examples are provided:
Configuration for 6400 UAC NSP
atm pvp 0 interface ATM1/0/0 0
atm pvp 2 interface ATM1/0/0 2
atm pvp 3 interface ATM1/0/0 3
atm pvp 4 interface ATM1/0/0 4
atm pvp 5 interface ATM1/0/0 5
atm pvp 6 interface ATM1/0/0 6
atm pvp 7 interface ATM1/0/0 7
atm pvp 8 interface ATM1/0/0 8
atm pvp 9 interface ATM1/0/0 9
atm pvp 10 interface ATM1/0/0 10
atm pvp 11 interface ATM1/0/0 11
atm pvp 12 interface ATM1/0/0 12
atm pvp 13 interface ATM1/0/0 13
atm pvp 14 interface ATM1/0/0 14
atm pvp 15 interface ATM1/0/0 15
|
Note Instead of configuring multiple PVCs, you can also 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 0 |
Configuration for 6400 UAC NRP LSC1
ip address 142.2.143.22 255.255.255.255
extended-port ATM0/0/0 bpx 1.3
tag-switching atm vpi 2-15
extended-port ATM0/0/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm disable-headend-vc
Configuration for BPX1 and BPX2
cnfr 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 1.3 256 252207 y 1 e 512 6144 2 15 26000 100000
cnfr 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Configuration for 6400 UAC NRP LSC2
ip address 192.103.210.5 255.255.255.255
tag-con trol-protocol vsi
extended-port ATM0/0/0 bpx 1.3
tag-switching atm vpi 2-15
extended-port ATM0/0/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm disable-headend-vc
Configuration for Edge LSR1
ip address 142.6.132.2 255.255.255.255
interface ATM2/0/0.5 tag-switching
tag-switching atm vpi 2-5
Configuration for Edge LSR2
ip address 142.6.142.2 255.255.255.255
interface ATM2/0/0.9 tag-switching
tag-switching atm vpi 2-5
Configuring ATM LSRs through ATM Network Using Cisco 7200/7500 LSCs Implementing Virtual Trunking
The network topology shown in Figure 10 incorporates two ATM-LSRs using virtual trunking to create an MPLS network through a private ATM Network. This topology includes two LSCs (Cisco 7200 and 7500 routers), two BPX Service Nodes, and two edge LSRs (Cisco 7500 and 7200 routers).
Figure 10 ATM-LSR Virtual Trunking through ATM Network
Based on Figure 10, the following configuration examples are provided:
Configuration for LSC1 Implementing Virtual Trunking
ip address 192.103.210.5 255.255.255.255
extended-port ATM3/0 bpx 1.3.2
tag-switching atm vp-tunnel 2
extended-port ATM3/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for BPX1 and BPX2
cnfr 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000
cnftrk 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 2
cnfr 1.3.2 256 252207 y 1 e 512 6144 2 2 26000 100000
cnfr 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Configuration for LSC2 Implementing Virtual Trunking
ip address 142.2.143.22 255.255.255.255
extended-port ATM3/0/0 bpx 1.3.2
tag-switching atm vp-tunnel 2
extended-port ATM3/0/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for Edge LSR1
ip address 142.6.132.2 255.255.255.255
interface ATM2/0/0.5 tag-switching
tag-switching atm vpi 2-5
Configuration for Edge LSR2
ip address 142.6.142.2 255.255.255.255
interface ATM2/0.9 tag-switching
tag-switching atm vpi 2-5
Configuring ATM LSRs through ATM Network Using Cisco 6400 NRP LSCs Implementing Virtual Trunking
The network topology shown in Figure 11 incorporates two ATM-LSRs using virtual trunking to create an MPLS network through a private ATM Network. This topology includes two LSCs (Cisco 6400 UAC NRP routers), two BPX Service Nodes, and two edge LSRs (Cisco 7500 and 7200 routers).
Figure 11 Cisco 6400 NRP Operating as LSC Implementing Virtual Trunking
Based on Figure 11, the following configuration examples are provided:
Configuration for 6400 UAC NSP
atm pvp 0 interface ATM1/0/0 0
atm pvp 2 interface ATM1/0/0 2
atm pvp 3 interface ATM1/0/0 3
atm pvp 4 interface ATM1/0/0 4
atm pvp 5 interface ATM1/0/0 5
atm pvp 6 interface ATM1/0/0 6
atm pvp 7 interface ATM1/0/0 7
atm pvp 8 interface ATM1/0/0 8
atm pvp 9 interface ATM1/0/0 9
atm pvp 10 interface ATM1/0/0 10
atm pvp 11 interface ATM1/0/0 11
atm pvp 12 interface ATM1/0/0 12
atm pvp 13 interface ATM1/0/0 13
atm pvp 14 interface ATM1/0/0 14
atm pvp 15 interface ATM1/0/0 15
|
Note Instead of configuring multiple PVCs, you can also 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 0 |
Configuration for 6400 UAC NRP LSC1 Implementing Virtual Trunking
ip address 142.2.143.22 255.255.255.255
extended-port ATM0/0/0 bpx 1.3.2
tag-switching atm vp-tunnel 2
extended-port ATM0/0/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm disable-headend-vc
Configuration for BPX1 and BPX2
cnfr 1.1 256 252207 y 1 e 512 6144 2 15 26000 100000
cnftrk 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 2
cnfr 1.3.2 256 252207 y 1 e 512 6144 2 2 26000 100000
cnfr 2.2 256 252207 y 1 e 512 4096 2 5 26000 100000
Configuration for 6400 UAC NRP LSC2 Implementing Virtual Trunking
ip address 192.103.210.5 255.255.255.255
tag-con trol-protocol vsi
extended-port ATM0/0/0 bpx 1.3.2
tag-switching atm vp-tunnel 2
extended-port ATM0/0/0 bpx 2.2
tag-switching atm vpi 2-5
tag-switching atm disable-headend-vc
Configuration for Edge LSR1
ip address 142.6.132.2 255.255.255.255
interface ATM2/0/0.5 tag-switching
tag-switching atm vpi 2-5
Configuration for Edge LSR2
ip address 142.6.142.2 255.255.255.255
interface ATM2/0/0.9 tag-switching
tag-switching atm vpi 2-5
Command Reference
This section describes the CLI commands that you can use in conjunction with the MPLS LSC:
All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
Cisco IOS Release 12.0(1)T or later enables you to search and filter the output for the show and more commands. This capability helps you to sort through large amounts of output, or to exclude output that you do not need.
To use this functionality, enter a show or more command, followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
- command | {begin | include | exclude} regular-expression
An example of a show atm vc command follows, which indicates that you want the command output to begin with the first line containing the "PeakRate" expression:
- show atm vc | begin PeakRate
For more information about the search and filter capability, refer to the Cisco IOS Release 12.0(1)T feature module entitled CLI String Search.
Command Conventions
|
boldface font
|
Commands and keywords are in boldface type.
|
|
italic font
|
Arguments for which you supply values are in italics. In a context that does not allow italics, arguments are enclosed in angle brackets < >.
|
|
[ ]
|
Elements in square brackets are optional.
|
|
{ x | y | z }
|
Alternative keywords are grouped in braces and separated by vertical bars.
|
|
[ x | y | z ]
|
Optional keywords are grouped in brackets and separated by vertical bars.
|
extended-port
To associate the currently selected extended MPLS ATM (XTagATM) interface with a particular external interface on the remotely controlled ATM switch, use the following interface configuration command.
- extended-port ctrl-if {bpx bpx-port-number | descriptor vsi-descriptor | vsi vsi-port-number }
Syntax Description
|
ctrl-if
|
Identifies the ATM interface used to control the remote ATM switch.
You must configure VSI on this interface using the tag-control-protocol interface configuration command.
|
|
bpx bpx-port-number
|
Specifies the associated Cisco BPX interface using the native BPX syntax.
slot.port [.virtual port]
You can only use this form of the command when the controlled switch is a Cisco BPX switch.
|
|
descriptor vsi-descriptor
|
Specifies the associated port by its VSI physical descriptor.
Note that the vsi-descriptor string must exactly match the corresponding VSI physical descriptor.
|
|
vsi vsi-port-number
|
Specifies the associated port by its VSI physical descriptor.
The vsi-descriptor string must exactly match the corresponding VSI physical descriptor.
|
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
The extended-port interface configuration command associates an XTagATM interface with a particular 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 example shows you how to create an extended MPLS ATM interface and bind it to BPX port 2.3.
extended-port atm0/0 bpx 2.3
Related Commands
| Command |
Description |
|
interface XTagATM
|
Enters interface configuration mode for an extended MPLS ATM (XTagATM) interface.
|
interface XTagATM
To enter interface configuration mode for the extended MPLS ATM (XTagATM) interface, use the following interface XTagATM global configuration command. The interface is created the first time this command is issued for a particular interface number.
- interface XTagATM if-num
Syntax Description
|
if-num
|
Specifies the interface number.
|
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Extended MPLS ATM interfaces are virtual interfaces that are created on first reference-like tunnel interfaces. Extended MPLS ATM interfaces are similar to ATM interfaces except that the former only supports LC-ATM encapsulation.
Examples
The following example shows how you create an extended MPLS ATM interface with interface number 62:
(config)#
interface XTagATM62Related Commands
| Command |
Description |
|
extended-port
|
Associates the currently selected extended MPLS ATM (XTagATM) interface with a remotely controlled switch.
|
show atm vc
To display information about private ATM virtual circuits (VCs), use the following show atm vc privileged EXEC command.
- show atm vc [vcd]
Private VCs exist on the control interface of an MPLS LSC to support corresponding VCs on an extended MPLS ATM interface.
Syntax Description
|
vcd
|
(Optional). Specifies the virtual circuit to display information about.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
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 which shows information only on extended MPLS ATM VCs.
Examples
In the following example, no VCD is specified and private VCs are present.
Interface VCD VPI VCI Type Encapsulation Kbps Kbps Cells Status
ATM1/0 1 0 40 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 2 0 41 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 3 0 42 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 4 0 43 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 5 0 44 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 15 1 32 PVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 17 1 34 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 26 1 43 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 28 1 45 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 29 1 46 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE
When you specify a VCD value and the VCD corresponds to that of a private VC on a control interface, the display output appears as follows:
ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0: VCD: 15, VPI: 1, VCI: 32, etype:0x8, AAL5 - XTAGATM, Flags: 0xD38
PeakRate: 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: ACTIVE
Table 3 describes the significant fields in the sample command output shown above.
Table 3
Show ATM VC Command Field Descriptions
| Field |
Description |
|
|
Interface slot and number.
|
|
|
Virtual circuit descriptor (virtual circuit number).
|
|
|
Virtual path identifier.
|
|
|
Virtual circuit identifier.
|
|
|
Ethernet type.
|
|
|
Type of ATM adaptation layer (AAL) and encapsulation. A private VC has AAL5 and encapsulation XTAGATM.
|
|
|
Bit mask describing virtual circuit information. The flag values are summed to result in the displayed value.
0x10000 ABR VC
0x20000 CES VC
0x40000 TVC
0x100 TEMP (automatically created)
0x200 MULTIPOINT
0x400 DEFAULT_RATE
0x800 DEFAULT_BURST
0x10 ACTIVE
0x20 PVC
0x40 SVC
0x0 AAL5-SNAP
0x1 AAL5-NLPID
0x2 AAL5-FRNLPID
0x3 AAL5-MUX
0x4 AAL3/4-SMDS
0x5 QSAAL
0x6 AAL5-ILMI
0x7 AAL5-LANE
0x8 AAL5-XTAGATM
0x9 CES-AAL1
0xA F4-OAM
|
|
|
|
|
Number of packets transmitted at the peak rate.
|
|
|
Number of packets transmitted at the average rate.
|
|
|
Value that, when multiplied by 32, equals the maximum number of ATM cells the virtual circuit can transmit at the peak rate of the virtual circuit.
|
|
|
AIP-specific or NPM-specific register describing the usage of the virtual circuit. Contains values such as rate queue, peak rate, and AAL mode, which are also displayed in other fields.
|
|
|
Interface of corresponding extended MPLS ATM VC.
|
|
|
Virtual circuit descriptor (virtual circuit number) of the corresponding extended MPLS ATM VC.
|
|
|
Virtual path identifier of the corresponding extended MPLS ATM VC.
|
|
|
Virtual channel identifier of the corresponding extended MPLS ATM VC.
|
|
|
Seconds between OAM loopback messages or DISABLED if OAM is not in use on this VC.
|
|
|
Minutes between InARP messages, or DISABLED if InARP is not in use on this VC.
|
|
|
Total number of packets received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
|
|
Total number of packets sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
|
|
Total number of bytes received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
|
|
Total number of bytes sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
|
|
Number of process-switched input packets.
|
|
|
Number of process-switched output packets.
|
|
|
Number of process-switched broadcast packets.
|
|
|
Number of fast-switched input packets.
|
|
|
Number of fast-switched output packets.
|
|
|
Number of autonomous-switched or silicon-switched input packets.
|
|
|
Number of autonomous-switched or silicon-switched output packets.
|
|
|
Number of OAM cells sent on this virtual circuit.
|
|
|
Number of OAM cells received on this virtual circuit.
|
|
|
Displays the current state of the specified ATM interface.
|
show interface XTagATM
To display information about an extended MPLS ATM interface, use the following show interface XTagATM EXEC command.
- show interface XTagATM if-num
Syntax Description
|
if-num
|
Specifies the MPLS ATM interface number.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Extended MPLS ATM interfaces are virtual interfaces that are created on first reference like tunnel interfaces. Extended MPLS ATM 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 XTagATM0 XTagATM0 is up, line protocol is up
Hardware is Tag-Controlled Switch Port
Interface is unnumbered. Using address of Loopback0 (12.0.0.17)
MTU 4470 bytes, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255
Encapsulation ATM Tagswitching, loopback not set
Control interface: ATM1/0, switch port: bpx 10.2
9 terminating VCs, 16 switch cross-connects
129302 cells input, 127559 cells output
Last input 00:00:04, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/0, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
61643 packets input, 4571695 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
53799 packets output, 4079127 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffers copied, 0 interrupts, 0 failures
Table 4 describes the significant fields in the sample command output shown above.
Table 4
Show Interface XTagATM Command Field Descriptions
| Field |
Description |
|
|
Interface is currently active.
|
|
|
Shows line protocol is up.
|
Hardware is Tag-Controlled Switch Port |
Specifies the hardware type.
|
|
|
Specifies that this is an unnumbered interface.
|
|
|
Maximum transmission unit of the extended MPLS ATM interface.
|
|
|
Bandwidth of the interface in kilobits per second.
|
|
|
Delay of the interface in microseconds.
|
|
|
Reliability of the interface as a fraction of 255/ (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
|
|
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation ATM Tagswitching |
Encapsulation method.
|
|
|
Indicates that loopback is not set.
|
|
|
Identifies the ATM adaptation layer.
|
|
|
Identifies the control port switch port with which the extended MPLS ATM interface has been associated through the extended-port interface configuration command.
|
|
|
Number of terminating VCs with an endpoint on this extended MPLS ATM interface. Packets are transmitted and/or received by the MPLS LSC on a terminating VC, or are forwarded between an LSC-controlled switch port and a router interface.
|
|
|
Number of switch cross-connects on the external switch with an endpoint on the switch port that corresponds to this interface. This includes cross-connects to terminating VCs that carry data to and from the LSC, as well as cross-connects that bypass the MPLS LSC and switch cells directly to other ports.
|
|
|
Number of cells received and transmitted on all cross-connects associated with this interface.
|
Terminating traffic counts |
Indicates that counters below this line apply only to packets transmitted or received on terminating VCs.
|
5-minute input rate,
5-minute output rate |
Average number of bits and packets transmitted per second in the last 5 minutes.
|
|
|
Total number of error-free packets received by the system.
|
|
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
|
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet systems and bursts of noise on serial lines are often responsible for no input buffer events.
|
|
|
Total number of broadcast or multicast packets received by the interface.
|
|
|
Number of packets that are discarded because they are smaller than the medium's minimum packet size.
|
|
|
Number of packets that are discarded because they exceed the medium's maximum packet size.
|
|
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored and abort counts. Other input-related errors can also increment the count, so that this sum may not balance with other counts.
|
|
|
Cyclic redundancy checksum generated by the originating LAN station or far end device does not match the checksum calculated from the data received.
On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus. A high number of CRCs is usually the result of traffic collisions or a station transmitting bad data.
On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
|
|
Number of packets received incorrectly having a CRC error and a non integer number of octets.
|
|
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
|
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
|
|
|
Illegal sequence of one bits on the interface. This usually indicates a clocking problem between the interface and the data link equipment.
|
|
|
Total number of messages transmitted by the system.
|
|
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
|
|
Number of times that the transmitter has been running faster than the router can handle data. This condition may never be reported on some interfaces.
|
|
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, since some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
|
|
Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only one time in output packets.
|
|
|
Number of times an interface has been completely reset. Resets occur if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
|
|
Number of packets copied from a MEMD buffer into a system buffer before being placed on the output hold queue.
|
|
|
Displays the value of hwidb to tx_restarts.
|
|
|
Number of packets discarded because no MEMD buffer was available.
|
Related Commands
| Command |
Description |
|
interface XTagATM
|
Enters configuration mode for an extended MPLS ATM (XTagATM) interface.
|
show controllers XTagATM
To display information about an extended MPLS ATM interface controlled through the VSI protocol (or, if an interface is not specified, to display information about all extended MPLS ATM interfaces controlled through the VSI protocol), use the following show controllers XTagATM EXEC command.
- show controllers XTagATM if-num
Syntax Description
|
if-num
|
Specifies the interface number.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Per-interface information includes the following:
- Interface name
- Physical descriptor
- Interface status
- Physical interface state (supplied by the switch)
- Acceptable VPI and VCI ranges
- Maximum cell rate
- Available cell rate (forward/backward)
- Available channels
Similar information appears if you enter the show controllers vsi descriptor command. However, you must specify an interface by its (switch-supplied) physical descriptor, instead of its IOS interface name. For the Cisco BPX switch, the physical descriptor has the form:
slot.port.0
Examples
In this example, the sample output is from the show controllers XTagATM command specifying interface 0.
Router#
show controllers XTagATM 0 Interface 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: 0
Table 5 describes the significant fields in the sample command output shown above.
Table 5
Show Controllers XTagATM Command Field Descriptions
| Field |
Description |
|
|
Indicates the overall status of the interface. May be "up," "down," or "administratively down."
|
Hardware is Tag-Controlled ATM Port |
Indicates the hardware type.
If the XTagATM was successfully associated with a switch port, a description of the form "(on <switch_type> switch <name)" follows this field, where <switch_type> indicates the type of switch (for example, BPX), and "name" is an identifying string learned from the switch.
If the XTagATM interface was not bound to a switch interface (with the extended-port interface configuration command), then the label "Not bound to a control interface and switch port" appears.
If the interface has been bound, but the target switch interface has not been discovered by the LSC, then the label "Bound to undiscovered switch port (id <number>)" appears, where <number> is the logical interface ID in hexadecimal notation.
|
Control interface ATM1/0 is up |
Indicates that the XTagATM interface was bound (with the extended-port interface configuration command) to the VSI master whose control interface is ATM1/0 and that this control interface is up.
|
Physical descriptor is... |
A string identifying the interface which was learned from the switch.
|
|
|
This 32-bit entity, learned from the switch, uniquely identifies the interface. It appears in both hexadecimal and dotted quad notation.
|
|
|
Operational state of the interface, according to the switch. Can be one of the following:
- ACTIVE
- FAILED_EXT (that is, an external alarm)
- FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
- REMOVED (administratively removed from the switch)
|
|
|
Administrative state of the interface, according to the switch—Either Up or Down.
|
|
|
Indicates the allowable VPI range for the interface which was configured on the switch.
|
|
|
Indicates the allowable VCI range for the interface which was configured on, or determined by, the switch.
|
LSC control VC need not be strictly in VPI or VCI range |
Indicates that the label control VC does not need to be within the range specified by VPI range, but may be on VPI 0 instead.
|
|
|
Indicates the number of channels (endpoints) which are currently free to be used for cross-connects.
|
|
|
Maximum cell rate for the interface, which was configured on the switch.
|
|
|
Cell rate which is currently available for new cross-connects on the interface.
|
|
|
Number of endpoints (channels) in use on the interface, broken down by anticipated traffic flow, as follows:
- Ingress—Endpoints carry traffic into the switch
- Egress—Endpoints carry traffic away from the switch
- Ingress/egress—Endpoints carry traffic in both directions
|
|
|
Number of cells received on the interface.
|
|
|
Number of cells received on the interface which were discarded due to traffic management actions (rx header errors).
|
|
|
Number of cells received on the interface with cell header errors.
|
rx invalid addresses (per card) |
Number of cells received with invalid addresses (that is, unexpected VPI or VCI.). On the BPX, this counter is maintained per port group (not per interface).
|
|
|
Address of the last cell received on the interface with an invalid address (for example, 0/32).
|
|
|
Number of cells transmitted from the interface.
|
|
|
Number of cells intended for transmission from the interface that were discarded due to traffic management actions.
|
Related Commands
| Command |
Description |
|
show controllers vsi descriptor
|
Displays information about a switch interface discovered by the MPLS LSC through the VSI.
|
show controllers vsi control-interface
To display information about an ATM interface configured with the tag-control-protocol vsi EXEC command to control an external switch (or if an interface is not specified, to display information about all VSI control interfaces), use the following show controllers vsi control-interface command.
- show controllers vsi control-interface [interface]
Syntax Description
|
interface
|
(Optional). Specifies the interface number.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Examples
The following is sample output from the show controllers vsi control-interface command:
Router#
show controllers vsi control-interface Interface: ATM2/0 Connections: 14
The 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
| Command |
Description |
|
tag-control-protocol vsi
|
Configures the use of VSI on a control port.
|
show controllers vsi descriptor
To display information about a switch interface discovered by the MPLS LSC through VSI, or if no descriptor is specified, about all such discovered interfaces, use the following show controllers vsi descriptor EXEC command. You 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
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Per-interface information includes the following:
- Interface name
- Physical descriptor
- Interface status
- Physical interface state (supplied by the switch)
- Acceptable VPI and VCI ranges
- Maximum cell rate
- Available cell rate (forward/backward)
- Available channels
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.0 Log intf: 0x000C0200 (0.12.2.0)
IF 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): 10000
Table 6 describes the significant fields in the sample command output shown above.
Table 6
Show Controllers VSI Descriptor Command Field Descriptions
| Field |
Description |
|
|
Physical descriptor. A string learned from the switch which identifies the interface.
|
|
|
Logical interface ID. This 32-bit entity, learned from the switch, uniquely identifies the interface.
|
|
|
The (IOS) interface name.
|
|
|
Overall interface status. Can be "up," "down," or "administratively down."
|
|
|
Minimum virtual path identifier. Indicates the low end of the VPI range configured on the switch.
|
|
|
Maximum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
|
|
Minimum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
|
|
Maximum virtual channel identifier. Indicates the high end of the VCI range configured on, or determined by, the switch.
|
|
|
Operational state of the interface, according to the switch. Can be one of the following:
- FAILED_EXT (that is, an external alarm)
- FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
- REMOVED (administratively removed from the switch)
|
|
|
Maximum cell rate for the interface, which has been configured on the switch, in cells per second.
|
|
|
Indicates the number of channels (endpoints) that are currently free to be used for cross-connects.
|
Available cell rate (forward) |
Cell rate that is currently available in the forward (that is, ingress) direction for new cross-connects on the interface.
|
Available cell rate (backward) |
Cell rate that is currently available in the backward (that is, egress) direction for new cross-connects on the interface.
|
Related Commands
| Command |
Description |
|
show controllers XTagATM
|
Displays information about an extended MPLS ATM interface.
|
show controllers vsi session
To display information about all sessions with VSI slaves, use the following show controllers vsi session EXEC command.
- show controllers vsi session [session-num [interface interface]]
-
|
Note 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 BPX, each port or trunk card assumes the role of a VSI slave. |
Syntax Description
|
session-num
|
Specifies the session number.
|
|
interface interface
|
Specifies the VSI control interface.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
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. (Only one session can contain a given number in the first release, since multiple control interfaces are not supported.)
Examples
The following is sample output from the show controllers vsi session command:
Router#
show controllers vsi session Interface Session VCD VPI/VCI Switch/Slave Ids Session State
ATM0/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 ESTABLISHED
Table 7 describes the significant fields in the sample command output shown above.
Table 7
Show Controllers VSI Session Command Field Descriptions
| Field |
Description |
|
|
Control interface name.
|
|
|
Session number (from 0 to <n-1>), where n is the number of sessions on the control interface.
|
|
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC carrying the VSI protocol between the master and the slave for this session.
|
|
|
Virtual path identifier/virtual channel identifier (for the VC used for this session).
|
|
|
Switch and slave identifiers supplied by the switch.
|
|
|
Indicates the status of the session between the master and the slave.
- ESTABLISHED is the fully operational steady state.
- UNKNOWN indicates that the slave is not responding.
Other possible states include the following:
CONFIGURING
RESYNC_STARTING
RESYNC_UNDERWAY
RESYNC_ENDING
DISCOVERY
SHUTDOWN_STARTING
SHUTDOWN_ENDING
INACTIVE
|
In the following example, session number 9 is specified with the show controllers vsi session command:
Router#
show controllers vsi session 9 Interface: ATM1/0 Session number: 9
Switch type: BPX Switch id: 0
Controller id: 1 Slave id: 10
Keepalive timer: 15 Powerup session id: 0x0000000A
Cfg/act retry timer: 8/8 Active session id: 0x0000000A
Max retries: 10 Ctrl port log intf: 0x000A0100
Trap window: 50 Max/actual cmd wndw: 21/21
Trap filter: all Max checksums: 19
Current VSI version: 1 Min/max VSI version: 1/1
Messages sent: 2502 Inter-slave timer: 4.000
Messages received: 2502 Messages outstanding: 0
Table 8 describes the significant fields in the sample command output shown above.
Table 8
Show Controllers VSI Session Command Field Descriptions
| Field |
Description |
|
|
Name of the control interface on which this session is configured.
|
|
|
A number from 0 to <n-1>, where n is the number of slaves. Configured on the MPLS LSC with the slaves option of the tag-control-protocol vsi command.
|
|
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC which carries VSI protocol messages for this session.
|
|
|
Virtual path identifier or virtual channel identifier for the VC used for this session.
|
|
|
Switch device (for example, the BPX).
|
|
|
Switch identifier (supplied by the switch).
|
|
|
Controller identifier. Configured on the LSC, as well as on the switch, with the id option of the tag-control-protocol vsi command.
|
|
|
Slave identifier (supplied by the switch).
|
|
|
VSI master keepalive timeout period, in seconds. Configured on the MPLS LSC through the keepalive option of the tag-control-protocol-vsi command. If no valid message is received by the MPLS LSC within this time period, it sends a keepalive message to the slave.
|
|
|
Session id (supplied by the slave) used at powerup time.
|
|
|
Configured and actual message retry timeout period, in seconds. If no response is received for a command sent by the master within the actual retry timeout period, the message is resent. This applies to most message transmissions. The configured retry timeout value is specified through the retry option of the tag-control-protocol vsi command. The actual retry timeout value is the larger of the configured value and the minimum retry timeout value permitted by the switch.
|
|
|
Session ID for the currently active session (supplied by the slave).
|
|
|
Maximum number of times that a particular command transmission will be retried by the master. That is, a message may be sent up to <max_retiries+1> times. Configured on the MPLS LSC through the retry option of the tag-control-protocol vsi command.
|
|
|
Logical interface identifier for the control port, as supplied by the switch.
|
|
|
Maximum number of outstanding trap messages permitted by the master. This is advertised, but not enforced, by the LSC.
|
|
|
Maximum command window is the maximum number of outstanding (that is, unacknowledged) commands that may be sent by the master before waiting for acknowledgments. This number is communicated to the master by the slave.
The command window is the maximum number of outstanding commands that are permitted by the master, before it waits for acknowledgments. This is always less than the maximum command window.
|
|
|
This is always "all" for the LSC, indicating that it wants to receive all traps from the slave. This is communicated to the slave by the master.
|
|
|
Maximum number of checksum blocks supported by the slave. (In this release, the MPLS LSC uses only one checksum block.)
|
|
|
VSI protocol version currently in use by the master for this session. (In the first release, this is always 1.)
|
|
|
Minimum and maximum VSI versions supported by the slave, as last reported by the slave. If both are zero, the slave has not yet responded to the master.
|
|
|
Number of commands sent to the slave.
|
|
|
Timeout value associated by the slave for messages it sends to other slaves.
On a VSI-controlled switch with a distributed slave implementation (such as the BPX), VSI messages may be sent between slaves to complete their processing.
For the MPLS LSC VSI implementation to function properly, the value of its retry timer is forced to be at least two times the value of the inter-slave timer. (See "Cfg/act retry timer" in this table.)
|
|
|
Number of responses and traps received by the master from the slave for this session.
|
|
|
Current number of outstanding messages (that is, commands sent by the master for which responses have not yet been received).
|
Related Commands
| Command |
Description |
|
tag-control-protocol vsi
|
Configures the use of VSI on a control port.
|
show controllers vsi status
To display a one-line summary of each VSI-controlled interface, use the following show controllers vsi status EXEC command.
- show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Related Commands
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
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 status Interface 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.0
Table 9 describes the significant fields in the sample command output shown above.
Table 9
Show Controllers VSI Status Command Field Descriptions
| Field |
Description |
|
|
The (IOS) interface name.
|
|
|
Overall interface status. Can be "up," "down," or "administratively down."
|
|
|
The operational state of the interface, according to the switch. Can be one of the following:
- FAILED_EXT (that is, an external alarm)
- FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
- REMOVED (administratively removed from the switch)
|
|
|
A string learned from the switch that identifies the interface.
|
show controllers vsi traffic
To display traffic information about VSI-controlled interfaces, VSI sessions, or VCs on VSI-controlled interfaces, use the following show controllers vsi traffic EXEC command.
- show controllers vsi traffic [{ descriptor descriptor | session session-num |vc [descriptor descriptor [vpi vci ]]}]
Syntax Description
|
descriptor descriptor
|
Specifies the interface.
|
|
session session-num
|
Specifies a session number.
|
|
vpi
|
Virtual path identifier.
|
|
vci
|
Virtual circuit identifier.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
If none of the optional command parameters is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX, the physical descriptor has the form:
slot.port. 0
If a session number is specified, VSI protocol traffic counts by message type are displayed. The VC traffic display is the same as the one produced by the show xtagatm vc cross-connect traffic descriptor command.
Examples
The following is sample output from the show controllers vsi traffic command:
Router#
show controllers vsi traffic Interface: switch control port
Rx cells: 304250 Rx cells discarded: 0
Tx cells: 361186 Tx cells discarded: 0
Rx header errors: 4294967254 Rx invalid addresses (per card): 80360
Last invalid address: 0/53
Rx cells: 202637 Rx cells discarded: 0
Tx cells: 194979 Tx cells discarded: 0
Rx header errors: 4294967258 Rx invalid addresses (per card): 80385
Last invalid address: 0/32
Rx cells: 182295 Rx cells discarded: 0
Tx cells: 136369 Tx cells discarded: 0
Rx header errors: 4294967262 Rx invalid addresses (per card): 80372
Last invalid address: 0/32
Table 10 describes the significant fields in the sample command output shown above.
Table 10
Show Controllers VSI Traffic Command Field Descriptions
| Field |
Description |
|
|
Physical descriptor of the interface.
|
|
|
The (IOS) interface name.
|
|
|
Number of cells received on the interface.
|
|
|
Number of cells transmitted on the interface.
|
|
|
Number of cells received on the interface which were discarded due to traffic management.
|
|
|
Number of cells which could not be transmitted on the interface due to traffic management and which were therefore discarded.
|
|
|
Number of cells which were discarded due to ATM header errors.
|
|
|
Number of cells received with an invalid address (that is, an unexpected VPI/VCI combination). With the Cisco BPX switch, this count is of all such cells received on all interfaces in the port group of this interface.
|
|
|
Number of cells received on this interface with ATM cell header errors.
|
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
Router#
show controllers vsi traffic session 9 Sw Get Cnfg Cmd: 3656 Sw Get Cnfg Rsp: 3656
Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0
Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1
Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1
Sw End Resync Cmd: 1 Sw End Resync Rsp: 1
Ifc Getmore Cnfg Cmd: 1 Ifc Getmore Cnfg Rsp: 1
Ifc Cnfg Trap Rsp: 4 Ifc Cnfg Trap: 4
Ifc Get Stats Cmd: 8 Ifc Get Stats Rsp: 8
Conn Cmt Cmd: 73 Conn Cmt Rsp: 73
Conn Del Cmd: 50 Conn Del Rsp: 0
Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0
Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0
Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0
Gen Err Rsp: 0 Gen Err Rsp: 0
Table 11 describes the significant fields in the sample command output shown above.
Table 11
Show Controllers VSI Traffic Session Command Field Descriptions
| Field |
Description |
|
|
Number of VSI "get switch configuration command" messages sent.
|
|
|
Number of VSI "switch configuration asynchronous trap response" messages sent.
|
|
|
Number of VSI "set switch configuration command" messages sent.
|
|
|
Number of VSI "set resynchronization start command" messages sent.
|
|
|
Number of VSI "set resynchronization end command" messages sent.
|
|
|
Number of VSI "get more interfaces configuration command" messages sent.
|
|
|
Number of VSI "interface configuration asynchronous trap response" messages sent.
|
|
|
Number of VSI "get interface statistics command" messages sent.
|
|
|
Number of VSI "set connection committed command" messages sent.
|
|
|
Number of VSI "delete connection command" messages sent.
|
|
|
Number of VSI "get connection statistics command" messages sent.
|
|
|
Number of VSI "connection configuration asynchronous trap response" messages sent.
|
|
|
Number of VSI "bulk clear connection statistics command" messages sent.
|
|
|
Number of VSI "generic error response" messages sent or received.
|
|
|
Number of VSI "get connection configuration command response" messages received.
|
|
|
Number of VSI "switch configuration asynchronous trap" messages received.
|
|
|
Number of VSI "set switch configuration response" messages received.
|
|
|
Number of VSI "set resynchronization start response" messages received.
|
|
|
Number of VSI "set resynchronization end response" messages received.
|
|
|
Number of VSI "get more interfaces configuration response" messages received.
|
|
|
Number of VSI "interface configuration asynchronous trap" messages received.
|
|
|
Number of VSI "get interface statistics response" messages received.
|
|
|
Number of VSI "set connection committed response" messages received.
|
|
|
Number of VSI "delete connection response" messages received.
|
|
|
Number of VSI "get connection statistics response" messages received.
|
|
|
Number of VSI "connection configuration asynchronous trap" messages received.
|
|
|
Number of VSI "bulk clear connection statistics response" messages received.
|
|
|
"Unused" messages are those whose function codes are recognized as being part of the VSI protocol, but which are not used by the MPLS LSC and, consequently, are not expected to be received or sent.
"Unknown" messages have function codes which the MPLS LSC does not recognize as part of the VSI protocol.
|
|
|
Total number of VSI messages sent or received.
|
show tag-switching atm-tdp bindings
To display the requested entries from the ATM LDP label bindings database, use the following show tag-switching atm-tdp bindings EXEC command.
- show tag-switching atm-tdp bindings [A.B.C.D {mask | length}]
[local-tag | remote-tag vpi vci] [neighbor atm slot/subslot/port]
[remote-tag vpi vci]
Syntax Description
|
A.B.C.D
|
Destination of prefix.
|
|
mask
|
Destination netmask prefix.
|
|
length
|
Netmask length, in the range from 1 to 32.
|
|
local-tag vpi vci
|
Matches locally assigned label values.
|
|
neighbor atm slot/subslot/port
|
Matches labels assigned by a neighbor on the specified ATM interface.
|
|
remote-tag vpi vci
|
Matches remotely assigned label values.
|
Defaults
Displays all database entries.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
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 this command.
Switch#
show tag-switching atm-tdp bindings Destination: 13.13.13.6/32
Headend Router ATM1/0.1 (2 hops) 1/33 Active, VCD=8, CoS=available
Headend Router ATM1/0.1 (2 hops) 1/34 Active, VCD=9, CoS=standard
Headend Router ATM1/0.1 (2 hops) 1/35 Active, VCD=10, CoS=premium
Headend Router ATM1/0.1 (2 hops) 1/36 Active, VCD=11, CoS=control
Headend Router ATM1/0.1 (1 hop) 1/37 Active, VCD=4, CoS=available
Headend Router ATM1/0.1 (1 hop) 1/34 Active, VCD=5, CoS=standard
Headend Router ATM1/0.1 (1 hop) 1/35 Active, VCD=6, CoS=premium
Headend Router ATM1/0.1 (1 hop) 1/36 Active, VCD=7, CoS=control
Destination: 13.0.0.18/32
Tailend Router ATM1/0.1 1/33 Active, VCD=8
Table 12 describes the significant fields in the sample command output shown above.
Table 12
Show Tag-switching Atm-tdp Bindings Field Descriptions
| Field |
Description |
|
|
Destination IP address/length of netmask
|
|
|
VC type:
- Headend—VC that originates at this router
- Tailend—VC that terminates at this router
|
|
|
ATM interface
|
|
|
VPI/VCI
|
|
|
LVC state:
- Active—Set up and working
- Bindwait—Waiting for response
|
Related Commands
| Command |
Description |
|
show tag-switching atm-tdp bindwait
|
Displays the number of bindings waiting for label assignments for a remote MPLS ATM switch.
|
show tag-switching atm-tdp bindwait
To display the number of bindings waiting for label assignments from a remote MPLS ATM switch, use the following show tag-switching atm-tdp bindwait EXEC command.
- show tag-switching atm-tdp bindwait
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Examples
The following shows a sample display using this command:
Router#
show tag-switching atm-tdp bindwaitRelated Commands
| Command |
Description |
|
show tag-switching atm-tdp bindings
|
Displays requested entries from the ATM LDP label binding database.
|
show xtagatm cos-bandwidth-allocation XTagATM
To display information about CoS bandwidth allocation on extended MPLS ATM interfaces, use the following show xtagatm cos-bandwidth-allocation XTagATM EXEC command.
- show xtagatm, cos-bandwidth-allocation XTagATM [XTagATM interface number]
Syntax Description
|
XTagATM interface number
|
Specifies the XTagATM interface number.
|
Defaults
Available 50%, control 50%.
Command Modes
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Use this command to display CoS bandwidth allocation information for the following CoS traffic categories:
- Available
- Standard
- Premium
- Control
Examples
The following example shows output from this command:
Router#
show xtagatm cos-bandwidth-allocation XTagATM 123 show xtagatm cross-connect
To display information about the LSC view of the cross-connect table on the remotely controlled ATM switch, use the following show xtagatm cross-connect EXEC command.
- show xtagatm cross-connect [traffic] [{interface interface [vpi vci] |
descriptor descriptor [vpi vci]]
Syntax Description
|
traffic
|
Displays receive and transmit cell counts for each connection.
|
|
interface interface
|
Displays only connections with an endpoint of the specified interface.
|
|
vpi vci
|
Displays only detailed information on the endpoint with the specified VPI/VCI on the specified interface.
|
|
descriptor descriptor
|
Displays only connections with an endpoint on the interface with the specified physical descriptor.
|
Defaults
No default behavior or values.
Related Commands
EXEC
Command History
| Release |
Modification |
|
12.0(5)T
|
This command was introduced.
|
Examples
Each connection is listed twice in the sample output from the show xtagatm vc cross-connect command under each interface that is linked by the connection. Connections are marked as -> (unidirectional traffic flow, into the first interface), <- (unidirectional traffic flow, away from the interface), or <-> (bidirectional).
The following is sample output from the show xtagatm cross-connect command:
Router#
show xtagatm cross-connect Phys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State
10.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 UP
Table 13 describes the significant fields in the sample command output shown above.
Table 13
Show XTagATM Cross-Connect Command Field Descriptions
| Field |
Description |
|
|
Physical descriptor. A switch-supplied string identifying the interface on which the endpoint exists.
|
|
|
Virtual path identifier and virtual channel identifier for this endpoint.
|
|
|
The notation -> indicates an ingress endpoint, where traffic is only expected to be received into the switch; <- indicates an egress endpoint, where traffic is only expected to be transmitted from the interface; <-> indicates that traffic is expected to be both transmitted and received at this endpoint.
|
|
|
Physical descriptor for the interface of the other endpoint belonging to the cross-connect.
|
|
|
Virtual path identifier and virtual channel identifier of the other endpoint belonging to the cross-connect.
|
|
|
Indicates the status of the cross-connect to which this endpoint belongs. The state is typically UP; other values, all of which are transient, include the following:
DOWN
ABOUT_TO_DOWN
ABOUT_TO_CONNECT
CONNECTING
ABOUT_TO_RECONNECT
RECONNECTING
ABOUT_TO_RESYNC
RESYNCING
NEED_RESYNC_RETRY
ABOUT_TO_RESYNC_RETRY RETRYING_RESYNC
ABOUT_TO_DISCONNECT
DISCONNECTING
|
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 42 Intf type: switch control port
X-Intf type: extended tag ATM
Cast-type: point-to-point
Rx service type: Tag COS 0
Tx service type: Tag COS 0
Table 14 describes the significant fields in the sample command output shown above.
Table 14
Show XTagATM Cross-Connect Descriptor Field Descriptions
| Field |
Description |
|
|
Physical descriptor. A switch-supplied string identifying the interface on which the endpoint exists.
|
|
|
The (IOS) interface name.
|
|
|
Interface type. Can be either extended MPLS ATM or switch control port.
|
|
|
Virtual path identifier and virtual channel identifier for this endpoint.
|
|
|
Physical descriptor for the interface of the other endpoint belonging to the cross-connect.
|
|
|
The (IOS) name for the interface of the other endpoint belonging to the cross-connect.
|
|
|
Interface type for the interface of the other endpoint belonging to the cross-connect.
|
|
|
Virtual path identifier and virtual channel identifier of the other endpoint belonging to the cross-connect.
|
|
|
Indicates the status of the cross-connect to which this endpoint belongs. The cross-connect state is typically UP; other values, all of which are transient, include the following:
DOWN ABOUT_TO_DOWN ABOUT_TO_CONNECT
CONNECTING
ABOUT_TO_RECONNECT
RECONNECTING
ABOUT_TO_RESYNC
RESYNCING
NEED_RESYNC_RETRY
ABOUT_TO_RESYNC_RETRY
RETRYING_RESYNC
ABOUT_TO_DISCONNECT
DISCONNECTING
|
|
|
Input—Indicates an ingress endpoint where traffic is only expected to be received into the switch
Output—Indicates an egress endpoint, where traffic is only expected to be transmitted from the interface
Input/output—Indicates that traffic is expected to be both transmitted and received at this endpoint
|
|
|
Indicates whether or not the cross-connect is multicast. In the first release, this is always point-to-point.
|
|
|
Class of service type for the receive, or ingress, direction. This is MPLS COS <n>, (MPLS Class of Service <n>), where n is in the range 0-7 for input and input/output endpoints; this will be n/a for output endpoints. (In the first release, this is either 0 or 7.)
|
|
|
(Guaranteed) cell rate in the receive, or ingress, direction. In the first release, this is always n/a.
|
|
|
