Table Of Contents
MPLS Label Switch Controller
Feature Overview
Functional Description
Controlled Switch Ports Represented as Router Interfaces
LSC as Label Edge Device
Support for ATM Forum Protocols
Tag Switching/MPLS Terminology
Benefits
Supported Platforms
Supported Standards, MIBs, and RFCs
Configuration Tasks
Configuring MPLS on a LSC-Controlled BPX Port
Verifying LSC Configuration
Configuration Example
Configuring ATM-LSRs
Configuring Multi-VCs
QoS Support
Command Reference
Command Conventions
boldface font
|
Commands and keywords are in boldface.
|
italic font
|
Arguments for which you supply values are in italics. In contexts that do not allow italics, arguments are enclosed in angle
brackets < >.
|
[ ]
|
Elements in square brackets are optional.
|
{ x | y | z }
|
Required alternative keywords are grouped in braces and separated by vertical bars.
|
{ x | y | z ]
|
Required alternative keywords are grouped in brackets and separated by vertical bars.
|
extended-port
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
interface XTagATM
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
show atm vc
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Examples
show interface XTagATM
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
show controllers XTagATM
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
show controllers vsi control-interface
Syntax Description
Default
Command Mode
Command History
Examples
Related Command
show controllers vsi descriptor
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
show controllers vsi session
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Examples
Related Command
show controllers vsi status
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
show controllers vsi traffic
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Examples
show tag-switching atm-tdp bindings
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
show tag-switching atm-tdp bindwait
Syntax Description
Default
Command Mode
Command History
Examples
Related Command
show xtagatm cos-bandwidth-allocation XTagATM
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
show xtagatm cross-connect
Syntax Description
Default
Command Mode
Command History
Examples
show xtagatm vc
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Commands
tag-control-protocol vsi
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
tag-switching atm control-vc
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
tag-switching atm cos
Syntax Description
Default
Command Mode
Command History
Example
tag-switching atm vpi
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Related Command
tag-switching atm vp-tunnel
Syntax Description
Default
Command Mode
Command History
Usage Guidelines
Example
Debug Commands
debug tag-switching xtagatm cross-connect
Syntax Description
Default
Command History
Usage Guidelines
Example
Related Command
debug tag-switching xtagatm vc
Syntax Description
Default
Command History
Usage Guidelines
Example
debug tag-switching xtagatm errors
Syntax Description
Default
Command History
Usage Guidelines
Example
debug tag-switching xtagatm events
Syntax Description
Default
Command History
Usage Guidelines
Example
debug vsi api
Syntax Description
Default
Command History
Usage Guidelines
Example
debug vsi errors
Syntax Description
Default
Command History
Usage Guidelines
Example
debug vsi events
Syntax Description
Default
Command History
Usage Guidelines
Example
debug vsi packets
Syntax Description
Default
Command History
Usage Guidelines
Example
debug vsi param-groups
Syntax Description
Default
Command History
Usage Guidelines
Examples
Glossary
MPLS Label Switch Controller
This feature module describes the Cisco MPLS Label Switch Controller (LSC) feature. It includes information about the benefits of the MPLS LSC, supported platforms, configuration examples, and related commands.
Feature Overview
The label switch controller (LSC), combined with the Cisco BPX 8650 IP+ATM switch, delivers scalable integration of IP services over an ATM network.
The LSC enables the BPX 8650 to:
•
Participate in a MPLS network
•Directly peer with IP edge routers
•Support the full suite of IP features available in Cisco IOS
The LSC creates MPLS highly scalable IP+ATM integration by using a direct peer relationship between the BPX 8650 and IP edge routers. This direct peer relationship removes the limit placed on the number of IP edge routers (seen in traditional IP-over-ATM networks) allowing service providers to keep pace with the growing demand for IP services. The LSC also supports the quick and direct implementation of advanced IP services over ATM networks with BPX 8650s.
MPLS combines the performance and virtual circuit capabilities of Layer 2 (data link layer) switching with the proven scalability of Layer 3 (network layer) routing to deliver a solution to service providers that meets the challenge of managing explosive growth and providing differentiated services while leveraging their existing infrastructure.
The MPLS architecture provides the flexibility to:
•Run over any combination of Layer 2 technologies
•Support any Layer 3 protocol while scaling beyond today's current solutions.
By deploying MPLS across the Internet or large enterprise networks, customers can:
•Save money by using existing ATM and routing infrastructures
•Grow revenue with tag-enabled services
•Increase productivity with enhanced network scalability and performance
Functional Description
The label switch controller (LSC) is a label switch router (LSR) that controls the operation of a separate ATM switch. Together, the router and ATM switch function as a single ATM MPLS router (ATM-LSR). A Cisco 7200 or 7500 series router acts as the LSC, and a Cisco BPX 8600 Service Node or a partner's switch acts as the VSI-controlled ATM switch. The LSC controls the ATM switch using the Cisco Virtual Switch Interface (VSI), which runs over an ATM link connecting the two.
The combination of a LSC and the ATM switch it controls is shown in .
Figure 1 Label Switch Controller and Controlled ATM Switch
In , the dotted line represents the external interface of the LSC and controlled switch as seen in the IP routing topology. The controlled ATM switch shows one or more LC-ATM interfaces at this external interface and the LSC may include additional interfaces that may or may not be label controlled.
Controlled Switch Ports Represented as Router Interfaces
On the LSC, the LC-ATM ports on the controlled switch are represented as an IOS interface type called extended Label ATM (XTagATM). You associate XTagATM interfaces with particular physical interfaces on the controlled switch through the extended-port interface configuration command.
illustrates a configuration in which a LSC controls three ports on a BPX—6.1, 6.2, and 12.2.
These corresponding XTagATM interfaces were created on the LSC and associated with the corresponding ATM ports using the extended-port interface configuration command. Note that:
•An additional port on the BPX (12.1) acts as the switch control port
•An ATM interface (ATM1/0) on the LSC acts as the master control port
shows a typical LSC configuration in which the LSC and BPX switch function together as an ATM-LSR.
Figure 2 Typical LSC and BPX Configuration
LSC as Label Edge Device
The LSC can:
•Function simultaneously as a controller for an ATM switch and as a label edge device. Traffic can be forwarded between a router interface and a 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 can serve as the head or tail of a label-switched path tunnel. However, when the LSC acts as a label edge device the LSC is limited by the capabilities of its control link with the switch as follows:
•Total throughput between all other router interfaces and switch interfaces is limited by the bandwidth of the control link (that is, OC-3, 155 Mbps).
•Label space for LSC-terminated VCs is limited by the number of VCs supported on the control link.
Support for ATM Forum Protocols
You can connect the LSC to a network running ATM Forum protocols while the LSC simultaneously performs its LSC function. However, you must connect the ATM Forum network through a separate ATM interface (that is, not through the master control port).
Tag Switching/MPLS Terminology
The following table lists old tag switching terms and new MPLS terms used in this document.
Old Designation
|
New Designation
|
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-LSR (ATM Label Switch Router, for example,
Cisco BPX 8650 switch.)
|
TVC (Tag VC, Tag Virtual Circuit)
|
LVC (Label VC, Label Virtual Circuit)
|
TSP (Tag Switch Protocol)
|
LSP (Label Switch Protocol)
|
XTag ATM (extended Tag ATM port)
|
XmplsATM (extended MPLS ATM port)
|
Benefits
IP-ATM Integration
Enables ATM switches, including the Cisco BPX 8650 and 8680 switches to directly support advanced IP services and protocols, thereby reducing operational costs and bandwidth, and 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, integrated IP-ATM backbone, or a gigabit router backbone.
Supported Platforms
•Cisco 7500 series routers—The supported interfaces are the ATM Interface Processor (AIP), Virtual Interface Processor (VIP) and ATM port adapter (PA-A1 and PA-A3).
•Cisco 7200 series routers—The supported interface is the ATM port adapter (PA-A1 and PA-A3).
Supported Standards, MIBs, and RFCs
MIB
No new or modified MIBs are supported by this feature.
RFC
No new or modified RFCs are supported by this feature.
Standards
No new or modified standards are supported by this feature.
Configuration Tasks
This section provides an example of a configuration task for enabling MPLS on a label switch controller (LSC).
Refer to the Cisco BPX 8600 Series documentation for the BPX Service Node configuration examples.
Configuring MPLS on a LSC-Controlled BPX Port
Step
|
Command
|
Purpose
|
1
|
Router(config)# interface loopback0
Router(config-if)# ip address 192.103.210.5
|
Enable a loopback interface. A loopback interface provides stable router and LDP identifiers.
|
1
|
Router(config)# interface atm1/0
Router(config-if)# tag-control-protocol vsi
|
Enable the VSI protocol on the control interface ATM1/0.
|
2
|
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 bind it to BPX port 6.1.
|
3
|
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.
The range selected should be limited such that the total number of VPIs does not exceed 4. For example:
tag-switching atm vpi 2-5
tag-switching atm vpi 10-13
|
4
|
Router(config)# ip cef switch
|
Enable Cisco Express Forwarding (CEF) switching.
|
Note For Release 12.0(5)T, the XTagATM interfaces must be configured with the no ip route-cache cef command.
Verifying LSC Configuration
Step
|
Command
|
Purpose
|
1
|
Router# show controller vsi session
|
Displays the VSI session state.
|
2
|
Router# show tag-switching interfaces
|
Displays the MPLS-enabled interface states.
|
3
|
Router# show controllers vsi control-interface
|
Displays information about an ATM interface that controls an external ATM switch or VSI control interface.
|
4
|
Router# show interface XTagATM
|
Displays information about an extended MPLS ATM interface.
|
Configuration Example
Configuring ATM-LSRs
In , the network topology includes ATM-LSRs in a MPLS network. The network topology provides configurations for two LSCs (Cisco 7200 routers), two BPX service nodes and two edge LSRs (Cisco 7500 routers).
Figure 3 ATM-LSR Network Configuration Example
This section shows examples for the following configurations:
•LSC1
•BPX1 and BPX2
•LSC2
•Edge LSR1
•Edge LSR2
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-5
extended-port ATM3/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for BPX1 and BPX2
cnfrsrc 1.1 256 0 1 e 0 2000 1 255 0 353000
cnfrsrc 1.3 256 0 1 e 0 2000 1 255 0 353000
cnfrsrc 2.2 256 0 1 e 0 2000 1 255 0 353000
Configuration for LSC2
ip address 142.2.143.22 255.255.255.255
tag-control-protocol vsi slaves 2
extended-port ATM3/0 bpx 1.3
tag-switching atm vpi 2-5
extended-port ATM3/0 bpx 2.2
tag-switching atm vpi 2-5
Configuration for Edge LSR1
ip cef distributed switch
interface ATM2/0/0.5 tag-switching
ip address 142.6.132.2 255.255.0.0
tag-switching atm vpi 2-5
Configuration for Edge LSR2
ip cef distributed switch
interface ATM2/0/0.9 tag-switching
ip address 142.2.142.2 255.255.0.0
tag-switching atm vpi 2-5
Configuring Multi-VCs
When configuring Multi-VC support, 4 label VCs to each destination are created by default. These 4 VCs are called standard, available, premium, and control. By default class 0 and class 4 traffic take the standard VC, class 1 and class 5 take the available VC, class 2 and class 6 take the premium VC and class 3 and class 7 take the control VC.
This section shows examples for the following configurations:
•LSC1
•BPX1 and BPX2
•LSC2
•Edge LSR1
•Edge LSR2
Configuration for LSC1
ip address 192.103.210.5 255.255.255.255
extended-port ATM3/0 bpx 1.3
tag-switching atm cos available 25
tag-switching atm cos standard 25
tag-switching atm cos premium 25
tag-switching atm cos control 25
tag-switching atm vpi 2-5
extended-port ATM3/0 bpx 2.2
tag-switching atm cos available 20
tag-switching atm cos standard 30
tag-switching atm cos premium 25
tag-switching atm cos control 25
tag-switching atm vpi 2-5
Configuration for BPX1 and BPX2
cnfrsrc 1.1 256 0 1 e 0 2000 1 255 0 353000
cnfrsrc 1.3 256 0 1 e 0 2000 1 255 0 353000
cnfrsrc 2.2 256 0 1 e 0 2000 1 255 0 353000
Configuration for LSC2
ip address 142.2.143.22 255.255.255.255
tag-control-protocol vsi slaves 2
extended-port ATM3/0 bpx 1.3
tag-switching atm cos available 25
tag-switching atm cos standard 25
tag-switching atm cos premium 25
tag-switching atm cos control 25
tag-switching atm vpi 2-5
extended-port ATM3/0 bpx 2.2
tag-switching atm cos available 10
tag-switching atm cos standard 40
tag-switching atm cos premium 25
tag-switching atm cos control 25
tag-switching atm vpi 2-5
Configuration for Edge LSR1
ip cef distributed switch
interface ATM2/0/0.5 tag-switching
ip address 142.6.132.2 255.255.0.0
tag-switching atm vpi 2-5
tag-switching atm multi-vc
ip cef distributed switch
interface ATM2/0/0.9 tag-switching
ip address 142.2.142.2 255.255.0.0
tag-switching atm vpi 2-5
tag-switching atm multi-vc
QoS Support
If LSC1 supports QoS and the LSC2 does not support QoS, for example, LSC1 makes VC requests for the following default classes (control=CoS3, standard= CoS1). LSC2 will ignore the call field in the request and allocate two UBR label VCs.
If LSR1 supports QoS and the LSR2 does not support QoS, LSR2 will receive the request to create multiple label VCs, but by default, it creates class 0 only (UBR).
Command Reference
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
•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 vpi
•tag-switching atm vp-tunnel
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality helps you to sort through large amounts of output, or to exclude output that you do not need to see.
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
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
Command Conventions
boldface font
|
Commands and keywords are in boldface.
|
italic font
|
Arguments for which you supply values are in italics. In contexts that do not allow italics, arguments are enclosed in angle
brackets < >.
|
[ ]
|
Elements in square brackets are optional.
|
{ x | y | z }
|
Required alternative keywords are grouped in braces and separated by vertical bars.
|
{ x | y | z ]
|
Required alternative 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 extended-port 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 BPX interface using the native BPX syntax.
slot.port [.virtual port]
You may only use this form of the command when the controlled switch is a BPX.
|
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 logical interface number (integer).
|
Default
No default behavior or values.
Command Mode
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.
Example
The following example shows you how to create an extended MPLS ATM interface and bind it to the BPX port 2.3.
extended-port atm0/0 bpx 2.3
Related Command
Command
|
Description
|
interface XTagATM
|
Enters 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 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.
|
Default
No default behavior or values.
Command Mode
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. They are similar to ATM interfaces except that they only support LC-ATM encapsulation.
Example
The following example shows you how to create the extended MPLS ATM interface with the interface number 62:
(config)# interface XTagATM62
Related Command
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 show atm vc privileged EXEC command.
show atm vc [vcd]
Private VCs exist on the control interface of a LSC to support corresponding VCs on an extended MPLS ATM interface.
Syntax Description
vcd
|
(Optional) Specifies the virtual circuit to display information about.
|
Default
No default behavior or values.
Command Mode
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 a 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
defines the fields displayed in this example.
Table 1 Show ATM VC Command Field Descriptions
Field
|
Description
|
ATM1/0
|
Interface slot and number.
|
VCD
|
Virtual circuit descriptor (virtual circuit number).
|
VPI
|
Virtual path identifier.
|
VCI
|
Virtual channel identifier.
|
etype
|
Encapsulation type.
|
AAL5 - XTAGATM
|
Type of ATM adaptation layer (AAL) and encapsulation. A private VC has AAL5 and encapsulation XTAGATM.
|
Flags
|
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
|
PeakRate
|
Number of packets transmitted at the peak rate.
|
Average Rate
|
Number of packets transmitted at the average rate.
|
Burst Cells
|
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.
|
VCmode
|
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.
|
XTAGATM1
|
Interface of corresponding extended MPLS ATM VC.
|
VCD
|
Virtual circuit descriptor (virtual circuit number) of the corresponding extended MPLS ATM VC.
|
VPI
|
Virtual path identifier of the corresponding extended MPLS ATM VC.
|
VCI
|
Virtual channel identifier of the corresponding extended MPLS ATM VC.
|
OAM frequency
|
Seconds between OAM loopback messages or DISABLED if OAM is not in use on this VC.
|
InARP frequency
|
Minutes between InARP messages, or DISABLED if InARP is not in use on this VC.
|
InPkts
|
Total number of packets received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
OutPkts
|
Total number of packets sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
InBytes
|
Total number of bytes received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
OutBytes
|
Total number of bytes sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets.
|
InPRoc
|
Number of process-switched input packets.
|
OutPRoc
|
Number of process-switched output packets.
|
Broadcasts
|
Number of process-switched broadcast packets.
|
InFast
|
Number of fast-switched input packets.
|
OutFast
|
Number of fast-switched output packets.
|
InAS
|
Number of autonomous-switched or silicon-switched input packets.
|
OutAS
|
Number of autonomous-switched or silicon-switched output packets.
|
OAM F5 cells sent
|
Number of OAM cells sent on this virtual circuit.
|
OAM cells received
|
Number of OAM cells received on this virtual circuit.
|
Status
|
Displays the current state of the specified ATM interface.
|
show interface XTagATM
To display information about an extended MPLS ATM interface, use the show interface XTagATM EXEC command.
show interface XTagATM if-num
Syntax Description
if-num
|
Specifies the MPLS ATM interface number.
|
Default
No default behavior or values.
Command Mode
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. They are similar to ATM interfaces except that they only support LC-ATM encapsulation.
Example
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
defines the significant fields in this display.
Table 2 Show Interface XTagATM Command Field Descriptions
Field
|
Description
|
XTagATM0 is up
|
Interface is currently active.
|
line protocol is up
|
Shows line protocol is up.
|
Hardware is Tag-Controlled Switch Port
|
Specifies the hardware type.
|
Interface is unnumbered
|
Specifies that this is an unnumbered interface.
|
MTU
|
Maximum transmission unit of the extended MPLS ATM interface.
|
BW
|
Bandwidth of the interface in kilobits per second.
|
DLY
|
Delay of the interface in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255/ (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
|
load
|
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.
|
loopback not set
|
Indicates that loopback is not set.
|
Encapsulation(s)
|
Identifies the ATM adaptation layer.
|
Control interface
|
Identifies the control port switch port with which the extended MPLS ATM interface has been associated through the extended-port interface configuration command.
|
9 terminating VCs
|
Number of terminating VCs with an endpoint on this extended MPLS ATM interface. Packets are transmitted and/or received by the LSC on a terminating VC, or are forwarded between a LSC-controlled switch port and a router interface.
|
16 switch cross-connects
|
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 LSC and switch cells directly to other ports.
|
Switch port traffic
|
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.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts on noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the medium's minimum packet size.
|
giants
|
Number of packets that are discarded because they exceed the medium's maximum packet size.
|
input errors
|
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 the other counts.
|
CRC
|
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 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.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets.
|
overrun
|
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.
|
ignored
|
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.
|
abort
|
Illegal sequence of one bits on the interface. This usually indicates a clocking problem between the interface and the data link equipment.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
|
output errors
|
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, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
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.
|
interface resets
|
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.
|
output buffers copied
|
Number of packets copied from a MEMD buffer into a system buffer before being placed on the output hold queue.
|
interrupts
|
Displays the value of hwidb to tx_restarts.
|
failures
|
Number of packets discarded because no MEMD buffer was available.
|
