Table Of Contents
show controllers vsi control-interface
show controllers vsi descriptor
show controllers vsi session
show controllers vsi status
show controllers vsi traffic
show controllers xtagatm
show interface stats
show interface xtagatm
show interfaces switching
show ip bgp labels
show ip bgp vpnv4
show ip cache
show ip cache flow
show ip cache flow aggregation
show ip cache verbose flow
show controllers vsi control-interface
To display information about an ATM interface configured with the tag-control-protocol vsi command to control an external switch (or if an interface is not specified, to display information about all Virtual Switch Interface [VSI] control interfaces), use the show controllers vsi control-interface command in user EXEC or privileged EXEC mode.
show controllers vsi control-interface [interface]
Syntax Description
interface
|
(Optional) Specifies the interface number.
|
Command Modes
User EXEC
Privileged 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 Multiprotocol Label Switching (MPLS) Label Switch Controller (LSC) through a Virtual Switch Interface (VSI), or if no descriptor is specified, about all such discovered interfaces, use the show controllers vsi descriptor command in user EXEC or privileged EXEC mode.
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
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Specify an interface by its (switch-supplied) physical descriptor.
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 privileged EXEC command. However, you must specify a Cisco 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 12 describes the significant fields in the display.
Table 12 show controllers vsi descriptor Field Descriptions
Field
|
Description
|
Phys desc
|
Physical descriptor. A string learned from the switch that identifies the interface.
|
Log intf
|
Logical interface ID. This 32-bit entity, learned from the switch, uniquely identifies the interface.
|
Interface
|
The (Cisco IOS) interface name.
|
IF status
|
Overall interface status. Can be "up," "down," or "administratively down."
|
Min VPI
|
Minimum virtual path identifier. Indicates the low end of the VPI range configured on the switch.
|
Max VPI
|
Maximum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
Min VCI
|
Minimum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
Max VCI
|
Maximum virtual channel identifier. Indicates the high end of the VCI range configured on, or determined by, the switch.
|
IFC state
|
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
|
Maximum cell rate for the interface, which has been configured on the switch (in cells per second).
|
Available channels
|
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
show controllers vsi session
To display information about all sessions with Virtual Switch Interface (VSI) slaves, use the show controllers vsi session command in user EXEC or privileged EXEC mode.
show controllers vsi session [session-number [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-number
|
(Optional) Specifies the session number.
|
interface interface
|
(Optional) Specifies the VSI control interface.
|
Command Modes
User EXEC
Privileged 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, because 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 13 describes the significant fields in the display.
Table 13 show controllers vsi session Field Descriptions
Field
|
Description
|
Interface
|
Control interface name.
|
Session
|
Session number (from 0 to <n-1>), where n is the number of sessions on the control interface.
|
VCD
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC carrying the VSI protocol between the master and the slave for this session.
|
VPI/VCI
|
Virtual path identifier or virtual channel identifier (for the VC used for this session).
|
Switch/Slave Ids
|
Switch and slave identifiers supplied by the switch.
|
Session State
|
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 14 describes the significant fields in the display.
Table 14 show controllers vsi session Field Descriptions
Field
|
Description
|
Interface
|
Name of the control interface on which this session is configured.
|
Session number
|
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.
|
VCD
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC that carries VSI protocol messages for this session.
|
VPI/VCI
|
Virtual path identifier or virtual channel identifier for the VC used for this session.
|
Switch type
|
Switch device (for example, the BPX).
|
Switch id
|
Switch identifier (supplied by the switch).
|
Controller id
|
Controller identifier. Configured on the LSC, and on the switch, with the id option of the tag-control-protocol vsi command.
|
Slave id
|
Slave identifier (supplied by the switch).
|
Keepalive timer
|
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.
|
Powerup session id
|
Session ID (supplied by the slave) used at powerup time.
|
Cfg/act retry timer
|
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.
|
Active session id
|
Session ID (supplied by the slave) for the currently active session.
|
Max retries
|
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_retries+1> times. Configured on the MPLS LSC through the retry option of the tag-control-protocol vsi command.
|
Ctrl port log intf
|
Logical interface identifier for the control port, as supplied by the switch.
|
Trap window
|
Maximum number of outstanding trap messages permitted by the master. This is advertised, but not enforced, by the LSC.
|
Max/actual cmd wndw
|
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.
|
Trap filter
|
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.
|
Max checksums
|
Maximum number of checksum blocks supported by the slave.
|
Current VSI version
|
VSI protocol version currently in use by the master for this session.
|
Min/max VSI version
|
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.
|
Messages sent
|
Number of commands sent to the slave.
|
Inter-slave timer
|
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 interslave timer. (See "Cfg/act retry timer" in this table.)
|
Messages received
|
Number of responses and traps received by the master from the slave for this session.
|
Messages outstanding
|
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 Virtual Switch Interface (VSI)-controlled interface, use the show controllers vsi status command in user EXEC or privileged EXEC mode.
show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
If an interface is discovered by the LSC, but no extended Multiprotocol Label Switching (MPLS) ATM interface is associated with it through the extended-port 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 15 describes the significant fields in the display.
Table 15 show controllers vsi status Field Descriptions
Field
|
Description
|
Interface Name
|
The (Cisco IOS) interface name.
|
IF Status
|
Overall interface status. Can be "up," "down," or "administratively down."
|
IFC State
|
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)
|
Physical Descriptor
|
A string learned from the switch that identifies the interface.
|
show controllers vsi traffic
To display traffic information about Virtual Switch Interface (VSI)-controlled interfaces, VSI sessions, or virtual circuits (VCs) on VSI-controlled interfaces, use the show controllers vsi traffic command in user EXEC or privileged EXEC mode.
show controllers vsi traffic {descriptor descriptor | session session-number | vc [descriptor
descriptor [vpi vci]]}
Syntax Description
descriptor descriptor
|
Specifies the interface.
|
session session-number
|
Specifies a session number.
|
vpi
|
Virtual path identifier (0 to 4095).
|
vci
|
Virtual circuit identifier (0 to 65535).
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(4)T
|
The VPI range of values was extended to 4095.
|
Usage Guidelines
If none of the keywords is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX switch, the physical descriptor has the form
slot.port. 0
If a session number is specified, the output displays VSI protocol traffic by message type. The VC traffic display is also displayed by the show xmplsatm 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 16 describes the significant fields shown in the display.
Table 16 show controllers vsi traffic Field Descriptions
Field
|
Description
|
Phys desc
|
Physical descriptor of the interface.
|
Interface
|
The Cisco (IOS) interface name.
|
Rx cells
|
Number of cells received on the interface.
|
Tx cells
|
Number of cells transmitted on the interface.
|
Rx cells discarded
|
Number of cells received on the interface that were discarded due to traffic management.
|
Tx cells discarded
|
Number of cells that could not be transmitted on the interface due to traffic management and which were therefore discarded.
|
Rx header errors
|
Number of cells that were discarded due to ATM header errors.
|
Rx invalid addresses
|
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.
|
Last invalid address
|
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 17 describes the significant fields shown in the display.
Table 17 show controllers vsi traffic session Field Descriptions
Field
|
Description
|
Sw Get Cnfg Cmd
|
Number of VSI "get switch configuration command" messages sent.
|
Sw Cnfg Trap Rsp
|
Number of VSI "switch configuration asynchronous trap response" messages sent.
|
Sw Set Cnfg Cmd
|
Number of VSI "set switch configuration command" messages sent.
|
Sw Start Resync Cmd
|
Number of VSI "set resynchronization start command" messages sent.
|
Sw End Resync Cmd
|
Number of VSI "set resynchronization end command" messages sent.
|
Ifc Getmore Cnfg Cmd
|
Number of VSI "get more interfaces configuration command" messages sent.
|
Ifc Cnfg Trap Rsp
|
Number of VSI "interface configuration asynchronous trap response" messages sent.
|
Ifc Get Stats Cmd
|
Number of VSI "get interface statistics command" messages sent.
|
Conn Cmt Cmd
|
Number of VSI "set connection committed command" messages sent.
|
Conn Del Cmd
|
Number of VSI "delete connection command" messages sent.
|
Conn Get Stats Cmd
|
Number of VSI "get connection statistics command" messages sent.
|
Conn Cnfg Trap Rsp
|
Number of VSI "connection configuration asynchronous trap response" messages sent.
|
Conn Bulk Clr Stats Cmd
|
Number of VSI "bulk clear connection statistics command" messages sent.
|
Gen Err Rsp
|
Number of VSI "generic error response" messages sent or received.
|
Sw Get Cnfg Rsp
|
Number of VSI "get connection configuration command response" messages received.
|
Sw Cnfg Trap
|
Number of VSI "switch configuration asynchronous trap" messages received.
|
Sw Set Cnfg Rsp
|
Number of VSI "set switch configuration response" messages received.
|
Sw Start Resync Rsp
|
Number of VSI "set resynchronization start response" messages received.
|
Sw End Resync Rsp
|
Number of VSI "set resynchronization end response" messages received.
|
Ifc Getmore Cnfg Rsp
|
Number of VSI "get more interfaces configuration response" messages received.
|
Ifc Cnfg Trap
|
Number of VSI "interface configuration asynchronous trap" messages received.
|
Ifc Get Stats Rsp
|
Number of VSI "get interface statistics response" messages received.
|
Conn Cmt Rsp
|
Number of VSI "set connection committed response" messages received.
|
Conn Del Rsp
|
Number of VSI "delete connection response" messages received.
|
Conn Get Stats Rsp
|
Number of VSI "get connection statistics response" messages received.
|
Conn Cnfg Trap
|
Number of VSI "connection configuration asynchronous trap" messages received.
|
Conn Bulk Clr Stats Rsp
|
Number of VSI "bulk clear connection statistics response" messages received.
|
unused, unknown
|
"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 that the MPLS LSC does not recognize as part of the VSI protocol.
|
TOTAL
|
Total number of VSI messages sent or received.
|
show controllers xtagatm
To display information about an extended Multiprotocol Label Switching (MPLS) ATM interface controlled through the Virtual Switch Interface (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 show controllers xtagatm command in user EXEC or privileged EXEC mode.
show controllers xtagatm if-number
Syntax Description
if-number
|
Specifies the interface number.
|
Command Modes
User EXEC
Privileged 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 Cisco 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 18 describes the significant fields in the display.
Table 18 show controllers xtagatm Field Descriptions
Field
|
Description
|
Interface XTagATM0 is up
|
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 the 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 that was learned from the switch.
|
Logical interface
|
This 32-bit entity, learned from the switch, uniquely identifies the interface. It appears in both hexadecimal and dotted quad notation.
|
Oper state
|
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)
|
admin state
|
Administrative state of the interface, according to the switch—either "Up" or "Down."
|
VPI range 1 to 255
|
Indicates the allowable VPI range for the interface that was configured on the switch.
|
VCI range 32 to 65535
|
Indicates the allowable VCI range for the interface that 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.
|
Available channels
|
Indicates the number of channels (endpoints) that are currently free to be used for cross-connects.
|
Maximum cell rate
|
Maximum cell rate for the interface, which was configured on the switch.
|
Available cell rate
|
Cell rate that is currently available for new cross-connects on the interface.
|
Endpoints in use
|
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
|
Rx cells
|
Number of cells received on the interface.
|
rx cells discarded
|
Number of cells received on the interface that were discarded due to traffic management actions (rx header errors).
|
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).
|
last invalid address
|
Address of the last cell received on the interface with an invalid address (for example, 0/32).
|
Tx cells
|
Number of cells sent from the interface.
|
tx cells discarded
|
Number of cells intended for transmission from the interface that were discarded due to traffic management actions.
|
Related Commands
show interface stats
To display numbers of packets that were process switched, fast switched, and distributed switched, use the show interface stats command in user EXEC or privileged EXEC mode.
show interface type number stats
Syntax Description
type number
|
Interface type and number about which to display statistics.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Usage Guidelines
Use this command on the RP.
Note When fast switching is configured on the outbound interface, and RSP optimum, RSP flow, and VIP DFS switching modes are all specified on the incoming interface, the interface on which RSP optimum, RSP flow, and VIP DFS switching modes is not enabled can still show packets switched out via those switching paths when packets are received from other interfaces with RSP optimum, RSP flow, and VIP DES switching modes enabled.
Examples
The following is sample output from the show interface stats command:
Router# show interface fddi 3/0/0 stats
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 3459994 1770812197 4141096 1982257456
Route cache 10372326 3693920448 439872 103743545
Distributed cache 19257912 1286172104 86887377 1184358085
Total 33090232 2455937453 91468345 3270359086
Table 19 describes the significant fields in the display.
Table 19 show interface stats Field Descriptions
Field
|
Description
|
Fddi3/0/0
|
Interface for which information is shown.
|
Switching path
|
Column heading for the various switching paths below it.
|
Pkts In
|
Number of packets received in each switching mechanism.
|
Chars In
|
Number of characters received in each switching mechanism.
|
Pkts Out
|
Number of packets sent out each switching mechanism.
|
Chars Out
|
Number of characters sent out each switching mechanism.
|
show interface xtagatm
To display information about an extended Multiprotocol Label Switching (MPLS) ATM interface, use the show interface xtagatm command in user EXEC or privileged EXEC mode.
show interface xtagatm if-number
Syntax Description
if-number
|
Specifies the MPLS ATM interface number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.3T
|
Sample command output was added for when an interface is down.
|
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 command output when an interface is down:
Router# show interface xt92
XTagATM92 is down, line protocol is down
Hardware is Tag-Controlled Switch Port
Interface is unnumbered. Using address of Loopback1 (15.15.15.15)
MTU 4470 bytes, BW 4240 Kbit, DLY 80 used,
reliability 186/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Keepalive set (10 sec) [00:00:08/4]
Control interface: not configured
? cells input, ? cells output
Last input 00:00:10, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
138 packets input, 9193 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 i
00:05:46: %SYS-5-CONFIG_I: Configured from console by consolegnored, 0 abort
142 packets output, 19686 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
The following is sample command output when an interface is up:
Router# show interface xt92
XTagATM92 is up, line protocol is up
Hardware is Tag-Controlled Switch Port
Interface is unnumbered. Using address of Loopback1 (15.15.15.15)
MTU 4470 bytes, BW 4240 Kbit, DLY 80 used,
reliability 174/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Control interface: ATM3/0, switch port: bpx 9.2
3 terminating VCs, 7 switch cross-connects
275 cells input, 273 cells output
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
127 packets input, 8537 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
131 packets output, 18350 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 20 describes the significant fields shown in the displays.
Table 20 show interface xtagatm Field Descriptions
Field
|
Description
|
XTagATM0 is up
XTagATM0 is down
|
Interface is currently active (up) or inactive (down).
|
line protocol is up
line protocol is down
|
Displays the line protocol as up or down.
|
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 kBps).
|
DLY
|
Delay of the interface in microseconds.
|
reliability
|
Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
|
Encapsulation ATM
|
Encapsulation method.
|
loopback not set
|
Indicates that loopback is not set.
|
Keepalive set (10 sec) [00:00:08/4]
|
Indicates why the Xtag line is down. Valid values are:
1—Internal usage.
2—Administratively down.
3—Internal usage.
4—No extended port is configured.
5—Some cross-connects from an old session have been left operational.
6—No extended port or a wrong extended port was configured.
7—No control port was configured.
8—Internal usage.
9—Internal usage.
10—Internal usage.
11—Internal usage.
12—External port. The XTag is mapped to an invalid port on the switch.
13—External port. The XTag is mapped to a port that is down.
14—External port is mapped to the control panel on the switch.
15—OAM is being used to track the link state. The neighbor may be down or it is not responding to the OAM calls.
|
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.
|
n terminating VCs
|
Number of terminating VCs with an endpoint on this extended MPLS ATM interface. Packets are sent or received by the MPLS LSC on a terminating VC, or are forwarded between an LSC-controlled switch port and a router interface.
|
7 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, and cross-connects that bypass the MPLS LSC and switch cells directly to other ports.
|
Switch port traffic
|
Number of cells received and sent on all cross-connects associated with this interface.
|
Terminating traffic
|
Indicates that counters below this line apply only to packets sent or received on terminating VCs.
|
5-minute input rate,
5-minute output rate
|
Average number of bits and packets sent 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 Ethernet systems and bursts of 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 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 traffic collisions or a station sending 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 sent by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, sent by the system.
|
underruns
|
Number of times that the sender has been running faster than the router can handle data. This condition 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, because 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 re-sent 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.
|
Related Commands
Command
|
Description
|
interface xtagatm
|
Enters configuration mode for an extended MPLS ATM (XTagATM) interface.
|
show interfaces switching
To display the number of packets sent and received on an interface classified by the switching path, use the show interfaces switching command in user EXEC and privileged EXEC mode.
show interfaces [type number] switching
Syntax Description
type number
|
Interface type and number about which to display packet switching path information.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3
|
This command was introduced.
|
Usage Guidelines
Use the show interfaces switching command to show which path the router uses and how the traffic is switched. This command is also useful for troubleshooting CPU utilization.
Statistics for packets in, bytes in, packets out, and bytes out are displayed for the available protocols. The statistics are arranged by process, cache misses, fast-path and autonomous path. All values displayed by the show interfaces switching command are absolute. The clear interface counters command has no effect on these values.
You must enter at least seven characters of the switching keyword (switchi) when you use the show interfaces switching command.
Examples
The following shows sample output from the show interfaces switching command:
