Downloads |
Table Of Contents
Controlled Switch Ports Represented as Router Interfaces
Support for ATM Forum Protocols
Configuring Tag Switching on a TSC-Controlled BPX Port
show controllers vsi control-interface
show controllers vsi descriptor
debug tag-switching xtagatm cross-connect
debug tag-switching xtagatm events
debug tag-switching xtagatm vc
debug tag-switching xtagatm errors
How to Read System Error Messages
Error Message Traceback Reports
Tag Switch Controller Error Messages
Tag Switch Controller
Feature Summary
The Tag Switch Controller (TSC) with Cisco's BPX 8620 wide area switch and BPX 8650 IP+ATM switch delivers scalable integration of IP services over an ATM network.
The TSC enables the BPX 8620 and 8650 to:
•
Participate in a Tag Switching network
•
•
Tag Switching's highly scalable IP+ATM integration is created by the TSC using a direct peer relationship between the BPX 8620 or 8650 and IP edge routers. This removes the limit placed on the number of IP edge routers, seen in traditional IP over ATM networks, thus allowing service providers to keep pace with the growing demand for IP services. The TSC additionally supports the easy, quick, and direct implementation of advanced IP services over an ATM network of BPX 8620s and 8650s.
Tag Switching 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 Tag Switching architecture is unique in providing the flexibility to run over any combination of Layer 2 technologies and support any Layer 3 protocol while scaling well beyond today's current solutions. Thus deploying Tag Switching across an Internet or large enterprise networks, customers can save money by using existing ATM and routing infrastructures, grow revenue with tag-enabled services, and increase productivity with enhanced network scalability and performance.
List of Terms
The following terms are defined for a Tag Switching context only, not for general situations.
ATM-TSR—A Tag Switching router with a number of TC-ATM interfaces. The router forwards the cells from these interfaces using tags carried in the VPI and/or VCI field.
ATM edge TSR—A Tag Switching router that is connected to the ATM-TSR cloud through TC-ATM interfaces. The ATM edge TSR adds tags to untagged packets and strips tags from tagged packets.
BPX—Broadband Packet Exchange (BPX). The BPX is a carrier quality switch, with trunk and CPU hot standby redundancy.
BXM—Broadband Switch Module. ATM port card for the BPX switch.
VSI—Virtual Switch Interface (VSI). The protocol that enables a TSC to control an ATM switch over an ATM link.
VSI master—In a hardware context, a device that controls a VSI switch (for example, a VSI Tag Switch Controller). In a software context, a process that implements the master side of the VSI protocol.
VSI slave—In a hardware context, a switch or a port card that implements the VSI. In a software context, a process that implements the slave side of the VSI protocol.
extended tag ATM interface—A new type of interface supported by the remote ATM switch driver and a particular switch-specific driver that supports Tag Switching over an ATM interface on a remotely controlled switch.
external ATM interface—One of the interfaces on the controlled ATM switch other than the switch control port. It is also referred to as an exposed ATM interface, because it is available for connections outside of the tag controlled switch.
master control port—A physical interface on a TSC that is connected to one end of a slave control link.
remote ATM switch driver—A set of interfaces that allow IOS software to control the operation of a remote ATM switch through a control protocol, such as VSI.
Ships in the Night (SIN)—The ability to support both Tag Switching procedures and ATM Forum protocols on the same physical interface, or on the same router or switch platform. In this mode, the two protocol stacks operate independently.
controlled ATM switch—An ATM switch that is being controlled by a TSC.
switch control port—An interface that uses a TSC to control the operation of a controlled ATM switch (for example, VSI). The protocol runs on the ATM link.
tag controlled switch—The Tag Switch Controller and controlled ATM switch that it controls, viewed together as a unit.
Tag switch controller (TSC)—An IOS platform that runs the generic Tag Switching software and is capable of controlling of the operation of an external ATM (or other type of) switch, making the interfaces of the latter appear externally as TC-ATM interfaces.
tag-switched path (TSP) tunnel—A configured connection between two routers, using Tag Switching to carry the packets.
Tag Switching router (TSR)—A Layer 3 router that forwards packets based on the value of a tag encapsulated in the packets.
TC-ATM interface—A Tag Switching interface where tags are carried in the VPI/VCI bits of ATM cells and where VC connections are established under the control of Tag Switching control software.
TFIB—Tag Forwarding Information Base (TFIB). A data structure and way of managing forwarding in which destinations and incoming tags are associated with outgoing interfaces and tags.
TVC—Tag switched controlled virtual circuit (TVC). A virtual circuit (VC) established under the control of Tag Switching. A TVC is not a PVC or an SVC. It must traverse only a single hop in a tag-switched path (TSP), but may traverse several ATM hops only if it exists within a VP tunnel.
Platforms
The TSC is supported on the following platforms:
•
•
Supported MIBs and RFCs
None.
Functional Description
The Tag Switch Controller (TSC) is a tag switch router (TSR) that controls the operation of a separate ATM switch. Together, the router and ATM switch function as a single ATM Tag Switching router (ATM-TSR). A Cisco 7200 or 7500 series router acts as the TSC, and a Cisco BPX 8600 Service Node or a partner's switch acts as the VSI-controlled ATM switch. The TSC controls the ATM switch using the Cisco Virtual Switch Interface (VSI), which runs over an ATM link connecting the two.
The combination of a TSC and the ATM switch it controls is shown in .
Figure 1 Tag Switch Controller and Controlled ATM Switch
In this figure, the dotted line represents the external interface of the TSC and controlled switch as seen in the IP routing topology. The controlled ATM switch shows one or more TC-ATM interfaces at this external interface and the TSC itself may have additional interfaces that may or may not be tag controlled.
Controlled Switch Ports Represented as Router Interfaces
On the TSC the TC-ATM ports on the controlled switch are represented as a new IOS interface type called extended Tag ATM (XTagATM). XTagATM interfaces are associated with particular physical interfaces on the controlled switch through the extended-port interface configuration command.
illustrates a configuration in which a TSC is controlling three ports on a BPX—6.1, 6.2, and 12.2. These corresponding XTagATM interfaces have been created on the TSC 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 and an ATM interface (ATM1/0) on the TSC acts as the master control port.
shows a typical TSC configuration where the TSC and BPX together function as an ATM-TSR.
Figure 2 Typical TSC/BPX Configuration
TSC as Tag Edge Device
The TSC can function simultaneously as a controller for an ATM switch and as a tag edge device. Traffic can be forwarded between a router interface and a TC-ATM interface on the controlled switch as well as between two TC-ATM interfaces on the controlled switch. The TSC can perform the imposition and removal of tags and can serve as the head or tail of a tag-switched path (TSP) tunnel. However, when acting as a tag edge device the TSC is limited by the capabilities of its control link with the switch as follows:
•
•
Support for ATM Forum Protocols
The TSC may be connected to a network running ATM Forum protocols while simultaneously performing its TSC function. However, the connection to the ATM-Forum network must be through a separate ATM interface, that is, not through the master control port.
TSC Configuration Task
This section provides an example of a configuration task for enabling Tag Switching on a Tag Switch Controller (TSC).
Refer to the Cisco BPX 8600 Series documentation for the BPX Service Node configuration examples.
Configuring Tag Switching on a TSC-Controlled BPX Port
This case shows how to configure Tag Switching on a port of the BPX that is being controlled by the TSC.
The assumption is that the BPX is connected to the TSC through ATM1/0 and the goal is to configure Tag Switching on slot 6, port 1 of the BPX (see ).
The steps to do this are as follows:
Configuration Example
In this example, the network topology includes ATM-TSRs in a Tag Switching network. It provides configurations for two TSCs (7200 routers), two BPX Service Nodes and two edge TSRs (7500 routers).
Figure 3 ATM-TSR Network Configuration Example
Configuration for TSC1
7200 TSC1:ip cef switch!interface ATM3/0no ip addresstag-control-protocol vsi!interface XTagATM13extended-port ATM3/0 bpx 1.3!ip address 142.4.133.13 255.255.0.0tag-switching ip!interface XTagATM22extended-port ATM3/0 bpx 2.2!ip address 142.6.133.22 255.255.0.0tag-switching ip!Configuration for BPX1 and BPX2
BPX1 and BPX2:uptrk 1.1cnfrsrc 1.1 256 0 1 e 0 2000 1 255 0 353000uptrk 1.3cnfrsrc 1.3 256 0 1 e 0 2000 1 255 0 353000uptrk 2.2cnfrsrc 2.2 256 0 1 e 0 2000 1 255 0 353000addshelf 1.1 v 1 1Configuration for TSC2
7200 TSC2:ip cef switch!interface ATM3/0no ip addresstag-control-protocol vsi slaves 2!interface XTagATM13extended-port ATM3/0 bpx 1.3!ip address 142.4.143.13 255.255.0.0tag-switching ip!interface XTagATM22extended-port ATM3/0 bpx 2.2!ip address 142.2.143.22 255.255.0.0tag-switching ip!Configuration for Edge TSR1
7500 TSR1:ip cef distributed switch!interface ATM2/0/0no ip address!interface ATM2/0/0.5 tag-switchingip address 142.6.132.2 255.255.0.0tag-switching ip!Configuration for Edge TSR2
7500 TSR2:ip cef distributed switch!interface ATM2/0/0no ip address!interface ATM2/0/0.9 tag-switchingip address 142.2.142.2 255.255.0.0tag-switching ip!Command Reference
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references.
•
•
extended-port
To associate the currently selected extended tag 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
Default
None
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 tag ATM interface and bind it to the BPX port 2.3.
interface XTagATM0extended-port atm0/0 bpx 2.3Related Commands
interface XTagATM
interface XTagATM
To enter interface configuration mode for the extended tag ATM (XTagATM) interface, use the interface XTagATM command. The interface is created the first time this command is issued for a particular interface number.
interface XTagATM if-num
Syntax Description
Default
None
Command Mode
Configuration
Usage Guidelines
Extended tag 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 TC-ATM encapsulation.
Example
The following example shows you how to create the extended tag ATM interface with the interface number 62:
interface XTagATM62Related Commands
extended-port
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 TSC to support corresponding VCs on an extended tag ATM interface.
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
VCs on the extended tag ATM interfaces do not show up in the show atm vc command output. Instead, the show xtagatm vc command provides a similar output which shows information only on extended tag ATM VCs.
Sample Displays
In the following example, no VCD is specified and private VCs are present.
Router# show atm vcAAL / Peak Avg. BurstInterface VCD VPI VCI Type Encapsulation Kbps Kbps Cells StatusATM1/0 1 0 40 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 2 0 41 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 3 0 42 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 4 0 43 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 5 0 44 PVC AAL5-SNAP 0 0 0 ACTIVEATM1/0 15 1 32 PVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 17 1 34 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 26 1 43 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 28 1 45 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 29 1 46 TVC AAL5-XTAGATM 0 0 0 ACTIVEATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVElists the significant fields in this display.
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:
Router# show atm vc 15ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE ATM1/0: VCD: 15, VPI: 1, VCI: 32, etype:0x8, AAL5 - XTAGATM, Flags: 0xD38PeakRate: 0, Average Rate: 0, Burst Cells: 0, VCmode: 0x0 XTagATM1, VCD: 1, VPI: 0, VCI: 32 OAM DISABLED, InARP DISABLED InPkts: 38811, OutPkts: 38813, InBytes: 2911240, OutBytes: 2968834 InPRoc: 0, OutPRoc: 0, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0 OAM F5 cells sent: 0, OAM cells received: 0 Status: ACTIVETable 1 Show ATM VC Command Field Descriptions
show interface XTagATM
To display information about an extended Tag ATM interface, use the show interface XTagATM command.
show interface XTagATM if-num
Syntax Description
Command Mode
EXEC
Usage Guidelines
Extended tag 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 TC-ATM encapsulation.
Use the show interface XTagATM command to display information about an extended tag ATM interface.
Sample Display
The following is sample output from the show interface XTagATM command:
Router# show interface XTagATM0XTagATM0 is up, line protocol is upHardware is Tag-Controlled Switch PortInterface is unnumbered. Using address of Loopback0 (12.0.0.17)MTU 4470 bytes, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255Encapsulation ATM Tagswitching, loopback not setEncapsulation(s): AAL5Control interface: ATM1/0, switch port: bpx 10.29 terminating VCs, 16 switch cross-connectsSwitch port traffic:129302 cells input, 127559 cells outputLast input 00:00:04, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/0, 0 drops; input queue 0/75, 0 dropsTerminating traffic:5 minute input rate 1000 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 1 packets/sec61643 packets input, 4571695 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort53799 packets output, 4079127 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffers copied, 0 interrupts, 0 failureslists the significant fields in this display.
Table 2 Show Interface XTagATM Command Field Descriptions
Related Commands
interface XTagATM
show controllers XTagATM
To display information about an extended tag ATM interface or, if an interface is not specified, about all extended tag ATM interfaces, that are controlled through the VSI protocol, use the show controllers XTagATM command.
show controllers XTagATM if-num
Syntax Description
Command Mode
EXEC
Usage Guidelines
Per-interface information includes the interface name, the physical descriptor, the interface status, the physical interface state (supplied by the switch), acceptable VPI/VCI ranges, maximum cell rate, available cell rate (forward/backward), and available channels.
Similar information is displayed when 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 BPX, the physical descriptor has the form:
slot.port.0
Sample Display
In this example, the sample output is from the show controllers XTagATM command specifying interface 0.
Router# show controllers XTagATM 0Interface XTagATM0 is up Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI1) Control interface ATM1/0 is up Physical descriptor is 10.2.0 Logical interface 0x000A0200 (0.10.2.0) Oper state ACTIVE, admin state UP VPI range 1-255, VCI range 32-65535 VPI is not translated at end of link Tag control VC need not be strictly in VPI/VCI range Available channels: ingress 30, egress 30 Maximum cell rate: ingress 300000, egress 300000 Available cell rate: ingress 300000, egress 300000 Endpoints in use: ingress 7, egress 8, ingress/egress 1 Rx cells 134747 rx cells discarded 0, rx header errors 0 rx invalid addresses (per card): 52994 last invalid address 0/32 Tx cells 132564 tx cells discarded: 0lists the significant fields in this display.
Table 3 Show Controllers XTagATM Command Field Descriptions
Related Commands
show controllers vsi descriptor
show controllers vsi control-interface
To display information about an ATM interface that is configured with the tag-control-protocol vsi command to control an external switch, or if an interface is not specified, about all VSI control interfaces, use the show controllers vsi control-interface command.
show controllers vsi control-interface [interface]
Syntax Description
Command Mode
EXEC
Sample Display
The following is sample output from the show controllers vsi control-interface command:
Router# show controllers vsi control-interfaceInterface: ATM2/0 Connections: 14The display shows the number of cross-connects currently on the switch that were established by the TSC through VSI over the control interface.
Related Commands
tag-control-protocol vsi
show controllers vsi descriptor
To display information about a switch interface discovered by the TSC through VSI, or if no descriptor is specified, about all such discovered interfaces, use the show controllers vsi descriptor command. You specify an interface by its (switch-supplied) physical descriptor.
show controllers vsi descriptor [descriptor]
Syntax Description
descriptor
(Optional) Physical descriptor. For the BPX, the physical descriptor has the following form:
slot.port.0
Command Mode
EXEC
Usage Guidelines
Per-interface information includes the interface name, the physical descriptor, the interface status, the physical interface state (supplied by the switch), acceptable VPI/VCI ranges, maximum cell rate, available cell rate (forward/backward), and 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.
Sample Display
The following is sample output from the show controllers vsi descriptor command:
Router# show controllers vsi descriptor 12.2.0Phys desc: 12.2.0Log intf: 0x000C0200 (0.12.2.0)Interface: XTagATM0IF status: up IFC state: ACTIVE Min VPI: 1 Maximum cell rate: 10000 Max VPI: 259 Available channels: 2000 Min VCI: 32 Available cell rate (forward): 10000 Max VCI: 65535 Available cell rate (backward): 10000lists the significant fields in this display.
Table 4 Show Controllers VSI Descriptor Command Field Description
Related Commands
show controllers XTagATM
show controllers vsi session
To display information about all sessions with VSI slaves, use the show controllers vsi session command.
Note
show controllers vsi session [session-num [interface interface]]
Syntax Description
Command Mode
EXEC
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 have a given number in the first release, as multiple control interfaces are not supported.)
Sample Display
The following is sample output from the show controllers vsi session command:
Router# show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Sesssion StateATM0/0 0 1 0/40 0/1 ESTABLISHED ATM0/0 1 2 0/41 0/2 ESTABLISHED ATM0/0 2 3 0/42 0/3 DISCOVERY ATM0/0 3 4 0/43 0/4 RESYNC-STARTING ATM0/0 4 5 0/44 0/5 RESYNC-STOPPING ATM0/0 5 6 0/45 0/6 RESYNC-UNDERWAY ATM0/0 6 7 0/46 0/7 UNKNOWN ATM0/0 7 8 0/47 0/8 UNKNOWN ATM0/0 8 9 0/48 0/9 CLOSING ATM0/0 9 10 0/49 0/10 ESTABLISHED ATM0/0 10 11 0/50 0/11 ESTABLISHED ATM0/0 11 12 0/51 0/12 ESTABLISHEDlists the significant fields in this display.
Table 5 Show Controllers VSI Session Command Field Descriptions
In this example, session number 9 is specified with the show controllers vsi session command:
Router# show controllers vsi session 9Interface: ATM1/0 Session number: 9VCD: 10 VPI/VCI: 0/49Switch type: BPX Switch id: 0Controller id: 1 Slave id: 10Keepalive timer: 15 Powerup session id: 0x0000000ACfg/act retry timer: 8/8 Active session id: 0x0000000AMax retries: 10 Ctrl port log intf: 0x000A0100Trap window: 50 Max/actual cmd wndw: 21/21Trap filter: all Max checksums: 19Current VSI version: 1 Min/max VSI version: 1/1Messages sent: 2502 Inter-slave timer: 4.000Messages received: 2502 Messages outstanding: 0lists the significant fields in this display.
Table 6 Show Controllers VSI Session (With Session Number 9 Specified) Command Field Descriptions
Related Commands
tag-control-protocol vsi
show controllers vsi status
To display a one-line summary of each VSI-controlled interface, use the show controllers vsi status command.
show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
If an interface has been discovered by the TSC, but no extended tag 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.
Sample Display
The following is sample output from the show controllers vsi status command:
Router# show controllers vsi statusInterface Name IF Status IFC State Physical Descriptor switch control port n/a ACTIVE 12.1.0 XTagATM0 up ACTIVE 12.2.0 XTagATM1 up ACTIVE 12.3.0 <unknown> n/a FAILED-EXT 12.4.0lists the significant fields in this display.
Table 7 Show Controllers VSI Status Command Field Descriptions
show controllers vsi traffic
To display traffic information about VSI-controlled interfaces, VSI sessions, or VCs on VSI-controlled interfaces, use the show controllers vsi traffic command.
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 session number.
vpi
Virtual path identifier.
vci
Virtual circuit identifier.
Command Mode
EXEC
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.
Sample Display
The following is sample output from the show controllers vsi traffic command:
Router# show controllers vsi trafficPhys desc: 10.1.0Interface: switch control portIF status: n/aRx cells: 304250 Rx cells discarded: 0Tx cells: 361186 Tx cells discarded: 0Rx header errors: 4294967254 Rx invalid addresses (per card): 80360Last invalid address: 0/53
Phys desc: 10.2.0Interface: XTagATM0IF status: upRx cells: 202637 Rx cells discarded: 0Tx cells: 194979 Tx cells discarded: 0Rx header errors: 4294967258 Rx invalid addresses (per card): 80385Last invalid address: 0/32
Phys desc: 10.3.0Interface: XTagATM1IF status: upRx cells: 182295 Rx cells discarded: 0Tx cells: 136369 Tx cells discarded: 0Rx header errors: 4294967262 Rx invalid addresses (per card): 80372Last invalid address: 0/32lists the significant fields in this display.
Table 8 Show Controllers VSI Traffic Command Field Descriptions
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
Router# show controllers vsi traffic session 9Sent ReceivedSw Get Cnfg Cmd: 3656 Sw Get Cnfg Rsp: 3656Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1Sw End Resync Cmd: 1 Sw End Resync Rsp: 1Ifc Getmore Cnfg Cmd: 1 Ifc Getmore Cnfg Rsp: 1Ifc Cnfg Trap Rsp: 4 Ifc Cnfg Trap: 4Ifc Get Stats Cmd: 8 Ifc Get Stats Rsp: 8Conn Cmt Cmd: 73 Conn Cmt Rsp: 73Conn Del Cmd: 50 Conn Del Rsp: 0Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0Gen Err Rsp: 0 Gen Err Rsp: 0unused: 0 unused: 0unknown: 0 unknown: 0TOTAL: 3795 TOTAL: 3795lists the significant fields in this display.
Table 9 Show Controllers VSI Traffic Session Command Field Descriptions
show xtagatm cross-connect
To display information about the TSC's view of the cross-connect table on the remotely controlled ATM switch, use the show xtagatm cross-connect command.
show xtagatm cross-connect [traffic] [{interface interface [vpi vci] |
descriptor descriptor [vpi vci]]Syntax Description
Command Mode
EXEC
Usage Guidelines
Sample Displays
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-connectPhys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State10.1.0 1/37 -> 10.3.0 1/35 UP 10.1.0 1/34 -> 10.3.0 1/33 UP 10.1.0 1/33 <-> 10.2.0 0/32 UP 10.1.0 1/32 <-> 10.3.0 0/32 UP 10.1.0 1/35 <- 10.3.0 1/34 UP 10.2.0 1/57 -> 10.3.0 1/49 UP 10.2.0 1/53 -> 10.3.0 1/47 UP 10.2.0 1/48 <- 10.1.0 1/50 UP 10.2.0 0/32 <-> 10.1.0 1/33 UP 10.3.0 1/34 -> 10.1.0 1/35 UP 10.3.0 1/49 <- 10.2.0 1/57 UP 10.3.0 1/47 <- 10.2.0 1/53 UP 10.3.0 1/37 <- 10.1.0 1/38 UP 10.3.0 1/35 <- 10.1.0 1/37 UP 10.3.0 1/33 <- 10.1.0 1/34 UP 10.3.0 0/32 <-> 10.1.0 1/32 UPlists the significant fields in this display.
Table 10 Show xtagatm Cross-Connect Command Field Descriptions
A sample of the detailed information provided for a single endpoint is:
Router# show xtagatm cross-connect descriptor 12.1.0 1 42Phys desc: 12.1.0Interface: n/aIntf type: switch control portVPI/VCI: 1/42X-Phys desc: 12.2.0X-Interface: XTagATM0X-Intf type: extended tag ATMX-VPI/VCI: 2/38Conn-state: UPConn-type: input/outputCast-type: point-to-pointRx service type: Tag COS 0Rx cell rate: n/aRx peak cell rate: 10000Tx service type: Tag COS 0Tx cell rate: n/aTx peak cell rate: 10000lists the significant fields in this display.
Table 11 Show xtagatm Cross-Connect Descriptor Field Descriptions
show xtagatm vc
To display information about terminating VCs on extended tag ATM (XTagATM) interfaces, use the show xtagatm vc command.
show xtagatm vc [vcd [interface]]
Syntax Description
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 input (unidirectional traffic flow, into the interface), output (unidirectional traffic flow, away from the interface) or in/out (bidirectional).
Command Mode
EXEC
Usage Guidelines
The columns marked VCD, VPI and VCI display information for the corresponding private VC on the control interface. The private VC connects the XTagATM VC to the external switch. It is termed private because its VPI and VCI are only used for communication between the TSC and the switch, and is different from the VPI and VCI seen on the XTagATM interface and the corresponding switch port.
Sample Display
The following is sample output from the show xtagatm vc command:
Router# show xtagatm vcAAL / Control Interface Interface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM0 1 0 32 PVC AAL5-SNAP 2 0 33 ACTIVEXTagATM0 2 1 33 TVC AAL5-MUX 4 0 37 ACTIVEXTagATM0 3 1 34 TVC AAL5-MUX 6 0 39 ACTIVElists the significant fields in this display.
Table 12 Show xtagatm vc Command Field Descriptions
Related Commands
show atm vc
show xtagatm cross-connecttag-control-protocol vsi
To configure the use of VSI on a particular master control port, use the tag-control-protocol vsi command. To disable VSI, use the no form of this command.
[no] tag-control-protocol vsi [id controller-id] [base-vc vpi vci] [slaves slave-count]
[keepalive timeout] [retry timeout count]Syntax Description
Command Mode
Interface configuration
Usage Guidelines
The command is only available on interfaces that can serve as a VSI master control port. It is recommended that all options to the tag-control-protocol command be entered at once.
Once VSI is active on the control interface (through an earlier tag-control-protocol vsi command), re-entering the command may cause all associated XTagATM interfaces to go down and come back up. In particular, re-entering the tag-control-protocol vsi command with any of the following options causes VSI to be shut down and re-activated on the control interface:
•
•
•
VSI remains continuously active (that is, will not be shut down and re-activated) if tag-control-protocol vsi command is re-entered with only one or more of the following options:
•
•
In either case, re-entering the tag-control-protocol vsi command causes the specified options to take on the newly specified values; the other options retain their previous values. To restore default values to all the options, enter the no tag-control-protocol command, followed by the tag-control-protocol vsi command.
Example
The following example shows you how to configure the VSI driver on the control interface:
interface atm 0/0tag-control-protocol vsi 0 51tag-switching atm control-vc
To configure the VPI and VCI values to be used for the initial link to the Tag Switching peer, use the tag-switching atm control-vc interface configuration command. This link is used to establish the TDP session and to carry non-IP traffic.
tag-switching atm control-vc vpi vci
Syntax Description
Command Mode
Interface configuration
Usage Guidelines
On an extended tag ATM (XTagATM) interface, the default VPI range to be used for tagged VCs is the configured VPI range that is learned from the switch. This default range should be sufficient for most applications. Use the tag-switching vpi command on an XTagATM interface only when it is necessary to override these defaults.
For the tag-switching atm vpi command, the VPI range specified must lie within the range that was configured on the BPX for the corresponding BPX interface.
Example
The following example shows you how to create a Tag Switching subinterface on a router and how to select VPI 1 and VCI 34 as the control VC.
interface atm4/0.1 tag-switchingtag-switching iptag-switching atm control-vc 1 34tag-switching atm vpi
To configure the range of values to use in the VPI field for tag VCs, use the tag-switching atm vpi command. To clear the interface configuration, use the no form of this command.
tag-switching atm vpi vpi [- vpi]
no tag-switching atm vpi vpi [- vpi]Syntax Description
vpi
Virtual path identifier (low end of range).
-vpi
(Optional.) Virtual path identifier (high end of range).
Default
The default is 1-1.
Command Mode
Interface configuration
Usage Guidelines
To configure ATM Tag Switching on a router interface (for example, an ATM Interface Processor), you must enable a Tag Switching subinterface.
Note
Use this command to select an alternate range of VPI values for ATM tag assignment on this interface. The two ends of the link negotiate a range defined by the intersection of the range configured at each end.
Example
The following example shows you how to create a subinterface and how to select a VPI range from VPI 1 to VPI 3:
interface atm4/0.1 tag-switchingtag-switching iptag-switching atm vpi 1-3Related Commands
tag-switching atm control-vc
tag-switching atm vp-tunnel
To specify an interface or a subinterface as a VP tunnel, use the tag-switching atm vp-tunnel command.
tag-switching atm vp-tunnel vpi
Syntax Description
Command Mode
Interface configuration
Usage Guidelines
The tag-switching atm vp-tunnel and tag-switching atm vpi commands are mutually exclusive.
This command is available on both extended tag ATM interfaces and on TC-ATM subinterfaces of ordinary router ATM interfaces. The command is not available on the 1010, where all subinterfaces are automatically VP tunnels.
On an XTagATM interface, the tunnel/non-tunnel status and the VPI value to be used in case the XTagATM interface is a tunnel, are normally learned from the switch through VSI interface discovery. Therefore, it should not be necessary to use the tag-switching atm vp-tunnel command on an XTagATM interface in most applications.
Example
The following example shows you how to specify a Tag Switching subinterface VP tunnel, with a VPI value 4.
tag-switching atm vp-tunnel 4Debug Commands
This section contains an alphabetical listing of the TSC debug commands and their descriptions. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, sample output, and a description of that output.
•
•
•
•
debug tag-switching xtagatm cross-connect
Use the debug tag-switching xtagatm cross-connect EXEC command to display requests and responses for establishing and removing cross-connects on the controlled ATM switch. The no form of this command disables debugging output.
[no] debug tag-switching xtagatm cross-connect
Usage Guidelines
You can use the debug tag-switching xtagatm cross-connect command to monitor requests to establish or remove cross-connects from XTagATM interfaces to the VSI master, and the VSI master's responses to these requests.
Note
Sample Display
The following is an example of the display you see when you enter debug tag-switching xtagatm cross-connect:
Router# debug tag-switching xtagatm cross-connectXTagATM: cross-conn request; SETUP, userdata 0x17, userbits 0x1, prec 70xC0100 (Ctl-If) 1/32 <-> 0xC0200 (XTagATM0) 0/32XTagATM: cross-conn response; DOWN, userdata 0x60CDCB5C, userbits 0x2, resultOK0xC0200 1/37 --> 0xC0300 1/37lists the significant fields shown in this display.
Table 13 Debug Tag-Switching xtagatm Cross-Connect Command Field Description
Related Commands
show xtagatm cross-connect
debug tag-switching xtagatm events
Use the debug tag-switching xtagatm events EXEC command to display information about major events that occur on XTagATM interfaces, not including events for specific XTagATM VCs and switch cross-connects. The no form of this command disables debugging output.
[no] debug tag-switching xtagatm events
Usage Guidelines
You can use the debug tag-switching xtagatm events command to monitor the major events that occur on XTagATM interfaces. The command only monitors events that pertain to XTagATM interfaces as a whole and does not include any events which pertain to individual XTagATM VCs or individual switch cross-connects. The specific events monitored when debug tag-switching xtagatm events is in effect include:
•
•
•
Sample Display
The following is an example of the display you see when you enter debug tag-switching xtagatm events:
Router# debug tag-switching xtagatm eventsXTagATM: desired cross-connect table size set to 256XTagATM: ExATM API intf event Up, port 0xA0100 (None)XTagATM: ExATM API intf event Down, port 0xA0100 (None)XTagATM: marking all VCs stale on XTagATM0lists the significant fields shown in this display.
Table 14 Debug Tag-Switching xtagatm Events Command Field Description
debug tag-switching xtagatm vc
Use the debug tag-switching xtagatm vc EXEC command to display information about events that affect individual XTagATM terminating VCs. The no form of this command disables debugging output.
[no] debug tag-switching xtagatm vc
Usage Guidelines
You can use the debug tag-switching xtagatm vc command to display detailed information about all events that affect individual XTagATM terminating VCs.
Note
Sample Display
The following is an example of the display you see when you enter debug:
Router# debug tag-switching xtagatm vcXTagATM VC: XTagATM1 18 0/32 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM1 18 0/32 (ATM1/0 88 1/32): Complete, UpPend --> UpXTagATM VC: XTagATM1 19 1/33 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM0 43 0/32 (ATM1/0 67 1/84): Teardown, Up --> DownPendlists the significant fields shown in this display.
Table 15 Debug Tag-Switching xtagatm VC Command Field Description
debug tag-switching xtagatm errors
Use the debug tag-switching xtagatm errors EXEC command to display information about error and abnormal conditions that occur on XTagATM interfaces. The no form of this command disables debugging output.
[no] debug tag-switching xtagatm errors
Usage Guidelines
You can use the debug tag-switching xtagatm errors command to display information about abnormal conditions and events that occur on XTagATM interfaces.
Sample Display
The following is an example of the display you see when you enter debug tag-switching xtagatm errors:
Router# debug tag-switching xtagatm errorsXTagATM VC: XTagATM0 1707 2/352 (ATM1/0 1769 3/915): Cross-connect setupfailed NO_RESOURCESThis message indicates that an attempt to set up a cross-connect for the a terminating VC on XTagATM0 failed, and that the reason for the failure was a lack of resources on the controlled ATM switch.
debug vsi api
Use the debug vsi api EXEC command to display information on events associated with the external ATM API interface to the VSI master. The no form of this command disables debugging output.
[no] debug vsi api
Usage Guidelines
You can use debug vsi api command to monitor the communication between the VSI master and the XTagATM component about interface changes and cross-connect requests.
Sample Displays
The following is an example of the display you see when you enter debug vsi api:
Router# debug vsi apiVSI_M: vsi_exatm_conn_req: 0x000C0200/1/35 -> 0x000C0100/1/50desired state up, status OKVSI_M: vsi_exatm_conn_resp: 0x000C0200/1/33 -> 0x000C0100/1/49curr state up, status OKlists the significant fields shown in this display.
Table 16 Debug VSI API Command Field Description
debug vsi errors
Use the debug vsi errors EXEC command to display information on errors encountered by the VSI Master. The no form of this command disables debugging output.
[no] debug vsi errors [interface interface [slave number]]
Syntax Description
Usage Guidelines
You can use the debug vsi errors command to display information on errors encountered by the VSI master when parsing received messages, as well as information on unexpected conditions encountered by the VSI Master.
If the interface parameter is specified, output is restricted to errors associated with the indicated VSI control interface. If the slave number is specified, output is further restricted to errors associated with the session with the indicated slave.
Note
Multiple uses of the form of the command which specifies slave number allows multiple slaves to be debugged at once. For example, the following commands restrict output to that for errors associated with sessions 0 and 1 on control interface atm2/0 (but for no other sessions).
Router# debug vsi errors interface atm2/0 slave 0
Router# debug vsi errors interface atm2/0 slave 1
Some errors are not associated with any particular control interface or session; messages associated with these errors are printed regardless of the interface or slave options which are in effect.
Sample Display
The following is an example of the display you see when you enter debug vsi errors:
Router# debug vsi errorsVSI Master: parse error (unexpected param-group contents) in GEN ERROR RSP rcvd on ATM2/0:0/51 (slave 0)errored section is at offset 16, for 2 bytes:01.01.00.a0 00.00.00.00 00.12.00.38 00.10.00.34*00.01*00.69 00.2c.00.00 01.01.00.80 00.00.00.0800.00.00.00 00.00.00.00 00.00.00.00 0f.a2.00.0a00.01.00.00 00.00.00.00 00.00.00.00 00.00.00.0000.00.00.00lists the significant fields shown in this display.
Table 17 Debug VSI Errors Command Field Description
debug vsi events
Use the debug vsi events EXEC command to display information on events that affect entire sessions as well as events that affect only individual connections. The no form of this command disables debugging output.
[no] debug vsi events [interface interface [slave number]]
Syntax Description
Usage Guidelines
You can use the debug vsi events command to display information on events associated with the per-session state machines of the VSI master, as well as the per-connection state machines. If the interface parameter is specified, output is restricted to events associated with the indicated VSI control interface. If the slave number is specified, output is further restricted to events associated with the session with the indicated slave.
Note
Multiple uses of the form of the command which specifies slave number allows multiple slaves to be debugged at once. For example, the following commands restrict output to that for events associated with sessions 0 and 1 on control interface atm2/0 (but for no other sessions). Output associated with all per-connection events are displayed regardless of the interface or slave options which are in effect.
Router# debug vsi events interface atm2/0 slave 0
Router# debug vsi events interface atm2/0 slave 1
Sample Display
The following is an example of the display you see when you enter debug vsi events:
Router# debug vsi eventsVSI Master: conn 0xC0200/1/37->0xC0100/1/51:CONNECTING -> UPVSI Master(session 0 on ATM2/0):event CONN_CMT_RSP, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event KEEPALIVE_TIMEOUT, state ESTABLISHED -> ESTABLISHEDVSI Master(session 0 on ATM2/0):event SW_GET_CNFG_RSP, state ESTABLISHED -> ESTABLISHEDdebug vsi packetslists the significant fields shown in this display.
Table 18 Debug VSI Events Command Field Description
debug vsi packets
Use the debug vsi packets EXEC command to display a one-line summary of each VSI message sent and received by the TSC. The no form of this command disables debugging output.
[no] debug vsi packets [interface interface [slave number]]
Syntax Description
Usage Guidelines
If the interface parameter is specified, output is restricted to messages sent and received on the indicated VSI control interface. If the slave number is specified, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple uses of the form of the command which specifies slave number allows multiple slaves to be debugged at once. For example, the following commands restrict output to that for messages received on atm2/0 for sessions 0 and 1, (but for no other sessions).
Router# debug vsi packets interface atm2/0 slave 0
Router# debug vsi packets interface atm2/0 slave 1
Sample Display
The following is an example of the display you see when you enter debug vsi packets:
Router# debug vsi packetsVSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51VSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51lists the significant fields shown in this display.
Table 19 Debug VSI Packets Command Field Description
debug vsi param-groups
Use the debug vsi param-groups EXEC command to display the first 128 bytes of each VSI message sent and received by the TSC (in hexadecimal form). The no form of this command disables debugging output.
Note
[no] debug vsi param-groups [interface interface [slave number]]
Syntax Description
Usage Guidelines
This command is most commonly used with the debug vsi packets command to monitor incoming/outgoing VSI messages. If the interface parameter is specified, output is restricted to messages sent and received on the indicated VSI control interface. If the slave number is specified, output is further restricted to messages sent and received on the session with the indicated slave.
Note
Multiple uses of the form of the command, which specifies slave number, allows multiple slaves to be debugged at once. For example, the following commands restrict output to that for messages received on atm2/0 for sessions 0 and 1, (but for no other sessions).
Router# debug vsi param-groups interface atm2/0 slave 0
Router# debug vsi param-groups interface atm2/0 slave 1Sample Display
The following is an example of the display you see when you enter debug vsi param-groups:
Router# debug vsi param-groupsOutgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c2 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c2 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31Outgoing VSI msg of 12 bytes (not including encap):01.02.00.80 00.00.95.c3 00.00.00.00Incoming VSI msg of 72 bytes (not including encap):01.02.00.81 00.00.95.c3 00.0f.00.3c 00.10.00.0800.01.00.00 00.00.00.00 01.00.00.08 00.00.00.0900.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.0000.01.0f.a0 00.13.00.15 00.0c.01.00 00.00.00.0042.50.58.2d 56.53.49.31lists the significant fields shown in this display.
Table 20 Debug VSI Param-Groups Command Field Description
System Error Messages
This section lists and describes Cisco IOS Tag Switching system error messages. The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system. Some are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software.
How to Read System Error Messages
System error messages begin with a percent sign (%) and are structured as follows:
%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-textFACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. lists the system facilities codes.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. lists the severity levels.
MNEMONIC is a code that uniquely identifies the error message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. lists the representations of variable fields and the type of information in them.
The following is a sample system error message:
%LINK-2-BADVCALL: Ints. TDR=[dec]
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the appropriate Cisco IOS configuration guide and command reference publications.
Table 23 Representation of Variable Fields in Error Messages
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860Tag Switch Controller Error Messages
This section lists the Tag Switch Controller error messages.
Error Message %VSI_M-3-INCOMPATVER:None of the VSI versions ([int]-[int) for session [dec] on [chars] can be usedExplanation The VSI master on the Tag Switch Controller, and the VSI slaves on the controlled switch, must all agree to use the same version of the VSI protocol. This error means that the slave for the indicated session on the indicated control interface does not support a VSI version which is also supported by the VSI master and all the other slaves. The sesssion cannot be established while this is the case.
Recommended Action This error indicates that the Tag Switch Controller software version is not compatible with software on the controlled switch. Determine the software versions of the TSC and the switch software/firmware, and upgrade the software/firmware which is out of date.
Error Message%VSI_M-2-XCONNFAIL:Cross-connect [chars]/[int]/[int] [chars] [chars]/[int]/[int] failed unexpectedlyExplanation One or more cross-connects previously established by the Tag Switch Controller (through VSI) have failed unexpectedly. The Tag Virtual Circuit of which this cross-connect was a part will no longer carry traffic end-to-end. The failure may be due to an unexpected condition on the switch which the TSC controls, or it may be due to an incorrect switch configuration performed while the switch was not in communication with the TSC, but before the TSC detected this lack of communication.
Recommended Action This error indicates one of more TVCs will no longer carry traffic end-to-end. Obtain the required information and contact your technical service representative.
Error Message%XTAGATM-3-CONSISTENCY: [chars]Explanation An action attempted by the XTagATM interface implementation encountered an unexpected condition
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%XTAGATM-3-CONTROLVC: [chars]; could not create the control VC; reason [chars]Explanation The tag switching control VC could not be created on the specified extended tag atm (XTagATM) interface. This prevents a TDP session from being established on this interface.
Recommended Action This message indicates that the XTagATM driver was unable to create the tag switching control VC. This failure may be the result of a configuration problem or of an unexpected condition within the XTagATM driver. To check for a configuration problem, make sure that the VPI and VCI values for the tag control VC lie within the range supported on the controlled switch interface that is associated with the XTagATM interface (through the extended-port interface configuration command). If the configuration is correct, the problem may be due to an unexpected condition within the XTagATM driver. In this case, copy the message exactly as it appears, and report it to your technical service representative.
Error Message%XTAGATM-3-CTLVCVPI:[chars]; VPI for control VC must be 0 or within configured range on switchExplanation The VPI value for the tag control VC, set through the tag-switching atm vpi interface configuration command, must either be 0 or else must lie within the range of VPI values that is configured for Tag Switching on the controlled ATM switch. If the VPI value for the tag switching control VC does not satisfy these constraints, then the tag control VC is not created, and the TDP session is not established on the XTagATM interface.
Recommended Action Either reconfigure the VPI value for the tag switching control VC using the tag-switching atm vpi... interface configuration command on the Tag Switch Controller, or else reconfigure the range of VPI values available for Tag Switching on the controlled ATM switch. Make sure that the VPI value specified for the tag control VC is either 0 or else lies within the configured range of VPI values available for Tag Switching on the controlled ATM switch
Error Message%XTAGATM-3-DUPEXTPORT:[chars]; mapped to the same switch interface as [chars]Explanation Two XTagATM interfaces have been associated with a single interface on the controlled ATM switch through the extended-port interface configuration command. This causes one of the XTagATM interfaces to remain down indefinitely.
Recommended Action Use the extended-port... interface configuration command on one of the XTagATM interfaces to remove the duplicate binding.
Error Message%XTAGATM-3-SWITCHVPI: [chars]; switch VPI range ([dec]-[dec]) outside usable range ([dec]-[dec])Explanation The VPI range that has been configured for Tag Switching on the TSC-controlled ATM switch does not overlap with the range of VPI values that the TSC can support. This prevents a TDP session from being established on this interface.
Recommended Action Reconfigure the VPI range on the controlled switch so that it overlaps the usable range of VPI values.
What to Do Next
This document describes information specific only to the Tag Switch Controller. However, you can refer to the following publications for additional hardware and software configuration not specific to Tag Switch Controller.
•
•
•
