Table Of Contents
SIP and SPA Command Reference
bert errors
bert pattern
card type (T1/E1)
card type (T3/E3)
framing (T1/E1 controller)
framing (T3 controller)
framing (T3/E3 interface)
hw-module subslot reload
hw-module subslot shutdown
hw-module subslot srp
interface
loopback (T3/E3 interface)
mdl
show controllers pos
show controllers serial
show diag
show hw-module all fpd
show hw-module subslot fpd
show hw-module subslot oir
show interface sdcc
show interfaces gigabitethernet
show interfaces pos
show interfaces serial
show upgrade fpd file
show upgrade fpd package default
show upgrade fpd progress
show upgrade fpd table
speed
t1 framing
ttb
upgrade fpd auto
upgrade fpd path
upgrade hw-module slot
upgrade hw-module subslot
SIP and SPA Command Reference
This chapter documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference and master index publications.
Note
Some of the commands in this chapter apply to multiple Cisco products and are supported
on different platforms. The documentation for these commands describes differences in syntax and usage for certain platform or product variations. Therefore, when you see multiple forms of syntax, examples, or usage guidelines for a command in this guide, be sure to locate the heading within the command reference page that corresponds to the related SPA (or SIP) for your platform.
The following list shows the new and modified commands contained in this chapter:
•
bert errors
•
bert pattern
•
card type (T1/E1)
•
card type (T3/E3)
•
framing (T1/E1 controller)
•
framing (T3 controller)
•
framing (T3/E3 interface)
•
hw-module subslot reload
•
hw-module subslot shutdown
•
hw-module subslot srp
•
interface
•
loopback (T3/E3 interface)
•
mdl
•
show controllers pos
•
show controllers serial
•
show diag
•
show hw-module all fpd
•
show hw-module subslot fpd
•
show hw-module subslot oir
•
show interface sdcc
•
show hw-module subslot oir
•
show interfaces pos
•
show interfaces serial
•
show upgrade fpd file
•
show upgrade fpd package default
•
show upgrade fpd progress
•
show upgrade fpd table
•
speed
•
t1 framing
•
ttb
•
upgrade fpd auto
•
upgrade fpd path
•
upgrade hw-module slot
•
upgrade hw-module subslot
bert errors
To transmit bert errors while running any bert pattern, use the bert error command in interface configuration mode.
bert errors [number]
Syntax Description
number
|
(Optional) Range of 1-255 bert errors that may be introduced in a bert pattern.
|
Defaults
Default is 1
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.1(12c)EX1
|
This command was introduced for Cisco 7304 routers.
|
12.2(18)S
|
This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2 S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS release 12.2(18)SXE to support SPAs on the Cisco 7600 series router.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use this command to test link availability by injecting a fixed number of bert errors when a pattern is running and check that the same number of errors were received on the remote end.
Examples
This example injects 200 bit errors in a running bit pattern on slot 5, bay 2.
Router# configure terminal
Router(config)#int serial 5/0/0
Router(config-if)#bert errors 200
Related Commands
Command
|
Description
|
bert pattern
|
Start a BERT pattern on a port.
|
show controller serial
|
Displays serial line statistics.
|
bert pattern
To start a BERT pattern on a port, use the bert pattern command in interface configuration mode. Use the no bert pattern command to stop the sequence.
bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1 | qrss} interval minutes}
no bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1 | qrss} interval minutes}
Syntax Description
0s
|
Repeating pattern of zeros (...000...).
|
1s
|
Repeating pattern of ones (...111...).
|
2^15
|
Pseudorandom 0.151 test pattern that is 32,768 bits in length.
|
2^20
|
Pseudo-andom 0.153 test pattern that is 1,048,575 bits in length.
|
2^23
|
Pseudorandom 0.151 test pattern that is 8,388,607 bits in length.
|
alt-0-1
|
Repeating pattern of alternating zeros and ones (...01010...).
|
qrss
|
Pseudorandom quasi-random signal sequence (QRSS) 0.151 test pattern that is 1,048,575 bits in length.
|
interval minutes
|
Specifies the length of the BERT test in minutes.
|
Defaults
Bert is disabled by default.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.1CC
|
The command was introduced.
|
12.0(5)XE
|
The command was enhanced as an ATM interface configuration command
|
12.0(7)XE1
|
Support for Cisco 7100 series routers was added.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.1(12c)EX1
|
Support for Cisco 7304 routers was added.
|
12.2(18)S
|
Support for Cisco 7304 routers was added.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series router.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the bert pattern commamd to start or stop a specific bit pattern. To test link availability, start a pattern on one end and put the remote end in network loopback and verify that there are no bert errors.
Examples
This example starts a bert pattern on slot 5, bay 0.
Router# configure terminal
Router(config)#int serial 5/0/0
Router(config-if)#bert pattern 0s
Related Commands
Command
|
Description
|
bert errors
|
Transmit bert errors while running any bert pattern.
|
show controller serial
|
Displays serial line statistics.
|
loopback
|
Loopback at various points in the transmit and receive path.
|
card type (T1/E1)
To configure the ports on SPA in T1 or E1 mode, use the card type command in global configuration mode. To deselect the card type, use the no form of this command.
Note
The no form of this command is not supported on the Cisco 12000 router family.
card type {t1 | e1} slot subslot
no card type {t1 | e1} slot subslot
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
t1
|
Clear-channel T1 with integrated data service units (DSUs).
|
e1
|
Clear-channel E1 with integrated data service units (DSUs).
|
Defaults
No default behavior or values. There is no card type when the SPA is inserted for the first time. The user must configure this command before they can configure individual ports.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(5)XE
|
This command was introduced.
|
12.0(7)T
|
This command was integrated into Cisco IOS Release 12.0(7)T.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.
|
Usage Guidelines
To change all the SPA ports from T1 or T3 to E1 or E3 (or E3 to T3), you must deselect the card type and then configure the card with the new type of interface.
Examples
The following example configures all ports of a T3/E3 SPA, seated in slot 5, bay 2, in T3 mode:
Router# configure terminal
Router(config)# card type t3 5 2
Related Commands
Command
|
Description
|
show interface serial
|
Displays the serial interface type and other information.
|
card type (T3/E3)
To configure the ports on SPA in T3 or E3 mode, use the card type command in global configuration mode. To deselect the card type, use the no form of this comand.
Note
The no form of this command is not supported on the Cisco 12000 router family.
card type {t3 | e3} slot subslot
no card type {t3 | e3} slot subslot
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
t3
|
Clear-channel T3 with integrated data service units (DSUs).
|
e3
|
Clear-channel E3 with integrated data service units (DSUs).
|
Defaults
No default behavior or values. There is no card type when the SPA is inserted for first time. The user must configure this command before they can configure individual ports.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(5)XE
|
This command was introduced.
|
12.0(7)T
|
This command was integrated into Cisco IOS Release 12.0(7)T.
|
12.1(1)T
|
This command was introduced.
|
12.2(11)YT
|
This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms: Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.3(1)
|
This command was integrated into Cisco IOS Release 12.3(1) and support was added for Cisco 2610XM, Cisco 2611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 platforms.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
To change all the SPA ports from T3 to E3, you must deselect the card type and then configure the card with the new type of interface.
Once a card type is issued, the user can enter the no card type command and then another card type command to configure a new card type. The user must save the configuration to NVRAM and reboot the router in order for the new configuration to take effect.
When the router comes up, the software comes up with the new card type. Note that the software will reject the configuration associated with the old controller and old interface. The user will now have to configure the new controller and serial interface and save it.
Examples
The following example configures all ports of a T3/E3 SPA, seated in slot 5, bay 2, in T3 mode:
Router# configure terminal
Router(config)# card type t3 5 2
Related Commands
Command
|
Description
|
show interface serial
|
Displays the serial interface type and other information.
|
framing (T1/E1 controller)
To select the frame type for the T1 or E1 data line, use the framing command in controller configuration mode.
T1 Lines
framing {sf | esf}
E1 Lines
framing {crc4 | no-crc4} [australia]
T1 Shared Port Adapter
framing {sf | esf}
no framing {sf | esf}
E1 Shared Port Adapter
framing {crc4 | no-crc4 | unframed}
no framing {crc4 | no-crc4 | unframed}
Syntax Description
sf
|
Specifies super frame as the T1 frame type. This is the default for T1.
|
esf
|
Specifies extended super frame as the T1 frame type.
|
crc4
|
Specifies CRC4 frame as the E1 frame type. This is the default for E1.
|
no-crc4
|
Specifies no CRC4 frame as the E1 frame type.
|
australia
|
(Optional) Specifies the E1 frame type used in Australia.
|
Defaults
sf (for a T1 line)
crc4 (for an E1 line)
Command Modes
Controller configuration
Command History
Release
|
Modification
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use this command in configurations in which the router or access server is intended to communicate with T1 or E1 fractional data lines. The service provider determines the framing type required for your T1/E1 circuit.
To return to the default mode on a T1/E1 SPA, use the no form of this command. This command does not have a no form for other T1/E1 lines.
Examples
The following example selects extended super frame as the T1 frame type:
Router(config-controller)# framing esf
Related Commands
Command
|
Description
|
cablelength
|
Specifies the distance of the cable from the routers to the network equipment.
|
linecode
|
Selects the linecode type for T1 or E1 line.
|
framing (T3 controller)
To choose framing mode on a T3 port, use the framing command in controller configuration mode. To return to the default mode, use the no form of this command.
T3 Controllers
framing {c-bit | m23}
no framing
T3/E3 Shared Port Adapters and the Cisco 7500 Series Routers with CT3IP Port Adapter
framing {c-bit | m23 | auto-detect}
no framing
Syntax Description
auto-detect
|
Specifies detection of the framing type that it receives from the far-end equipment.
|
c-bit
|
Specifies that C-bit framing is used as the T3 framing type.
|
m23
|
Specifies that M23 framing is used as the T3 framing type.
|
Defaults
c-bit (for T3 and most T3 controllers)
auto-detect (for the CT3IP in a Cisco 7500 series router)
Command Modes
Controller configuration
Command History
Release
|
Modification
|
11.1CA
|
This command was introduced.
|
12.2(11)YT
|
This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms for T3: Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the framing command to set the framing mode on the T3/E3 port.
Examples
The following example sets the framing mode on a T3 interface.
Router# configure terminal
Router(config)# controller t1 6/0/0
Router(config-controller)# framing m23
The following example sets the framing for the CT3IP to C-bit:
Router(config)# controller t3 9/0/0
Router(config-controller)# framing c-bit
Related Commands
Command
|
Description
|
controller
|
Configures a T1, E1, or T3 controller and enters controller configuration mode.
|
show controller
|
Displays controller configuration.
|
framing (T3/E3 interface)
To choose framing mode on a T3 port, use the framing command in interface configuration mode. To return to the default mode, use the no form of this command.
framing {bypass | c-bit | m13}
no framing {bypass | c-bit | m13}
To choose framing mode on an E3 port, use the framing command in interface configuration mode. To return to the default mode, use the no form of this command.
framing {bypass | g751 | g832}
no framing {bypass | g751 | g832}
Syntax Description
bypass
|
Bypasses DS3 framing mode.
|
c-bit
|
Enables DS3 C-bit framing mode.
|
m13
|
Enables DS3 M13 framing mode.
|
g751
|
Enables E3 G.751 framing mode.
|
g832
|
Enables E3 G.832 framing mode.
|
Defaults
T3: C-bit framing
E3: g751 framing
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers. The g832 keyword option was added to the command.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the framing command to set the framing mode on the T3 port.
Examples
The following example sets the framing mode on the first port on slot 5.
Router# configure terminal
Router(config)# interface serial 5/0/0
Router(config-if)# framing bypass
Related Commands
Command
|
Description
|
show controller serial
|
Displays serial line statistics.
|
hw-module subslot reload
To restart a shared port adapter (SPA) and its interfaces, use the hw-module subslot reload command in privileged EXEC configuration mode. The command does not have a no form.
hw-module subslot slot/subslot reload
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S3
|
This command was introduced.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 12000 Series Routers.
|
12.0(31)S
|
This command was integrted into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.
|
Usage Guidelines
The hw-module subslot reload command stops and starts power to the SPA. This command is useful when you want to restart all interfaces on a SPA.
The command is recommended to restart a SPA under some of the following conditions:
•
To restart a SPA after it has been powered off because of a failure.
•
To recover from corrupted messaging between the RouteProcessor (RP) and the SIP.
Examples
The following command power cycles the SPA in subslot 2 of the SIP installed in chassis slot 13:
Router# hw-module subslot 13/2 reload
Note
The hw-module subslot reload command does not produce a message on the router console to indicate the status of the command action. However, some interface configurations might produce console output related to the action of reloading the SPA.
Related Commands
Command
|
Description
|
show hw-module subslot oir
|
Displays the operational status of a SPA.
|
hw-module subslot shutdown
To shut down a shared port adapter (SPA) with or without power and ensure that the SPA remains shut down, use the hw-module subslot shutdown command in global configuration mode. To reenable the SPA, use the no form of this command.
hw-module subslot slot/subslot shutdown [powered | unpowered]
no hw-module subslot slot/subslot shutdown [powered | unpowered]
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
powered
|
(Optional) Shuts down the SPA and all of its interfaces, and leaves them in an administratively down state with power enabled. This is the default state.
|
unpowered
|
(Optional) Shuts down the SPA and all of its interfaces, and leaves them in an administratively down state wihout power. As of 12.0(31)S the unpowered CLI option for the hw-module shutdown command is no longer supported.
|
Defaults
If this command is not used, no hw-module subslot shutdown is the default behavior. The SPA will not be shutdown unless specified by the user.
If this command is entered but both powered and unpowered are not specified in the CLI, powered is the default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(25)S3
|
This command was introduced.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
When you shut down a SPA, you can choose to put it into one of two states:
•
Powered state—(Default) Shuts down the SPA, but the SPA remains powered on. Use this option when you plan to leave the SPA physically installed and cabled in the router. You might choose to do this if you want to install a SPA and configure it, but do not want it online or to start communicating with the remote end of the connection.
•
Unpowered state—Shuts down the SPA and removes power from the SPA. Use this option when you plan to remove the SPA from the chassis.
This command is useful when a user wants all the interfaces on a SPA disabled but does not or cannot remove the SPA. Unlike the hw-module subslot stop EXEC command on the Cisco 7304 router, this command is saved in the configuration file and will keep the SPA disabled when other router events (such as a router reload or OIR) attempt to restart the SPA. All other settings and configurations of the SPA will be maintained even if the SPA itself is shutdown using this command.
As a general rule, you do not need to shut down a SPA if you are removing it and replacing it with the same exact model of SPA in an online insertion and removal (OIR) operation. However, you should shut down a SPA whenever you are replacing a SPA with a different model of SPA.
When you shut down a SPA using the hw-module subslot shutdown command, it remains shut down even if you reset the router or install a new SPA in that subslot. You must manually reenable the card, using the no hw-module subslot shutdown command, so you can begin using the card again.
Examples
The following example shows how to disable the SPA in subslot 4/1 while leaving the SPA in the router chassis. This command will be saved to the configuration file and no actions, outside of changing this configuration, will reenable the SPA:
Router(config)# hw-module subslot 4/1 shutdown unpowered
The following example shows how to configure the SPA to resume normal operation after the unpowered option has been used to disable the SPA:
Router(config)# hw-module subslot 4/1 shutdown powered
No messages are provided on the console when you shut down or reenable a SPA.
Related Commands
Command
|
Description
|
show hw-module subslot oir
|
Displays the operational status of a SPA.
|
hw-module slot1
|
Deactivates or reactivates a carrier card that is installed in a router slot. This command is entered in EXEC mode and is not saved to the configuration file.
|
hw-module subslot srp
To change from Packet over SONET (POS) mode to Spatial Reuse Protocol (SRP) mode for all interfaces on a POS/Resilient Packet Ring (RPR) SPA, use the hw-module subslot srp command in global configuration mode.
hw-module subslot slot/subslot srp {mate slot/subslot}
no hw-module subslot slot/subslot srp {mate slot/subslot}
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
mate slot/subslot
|
(Not required for the 2-Port OC-48c/STM-16 POS SPA) Specifies the location of the SPA that is the SRP mate.
|
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(32)SY
|
This command was introduced.
|
Usage Guidelines
When enabling SRP mode using the hw-module subslot srp command, consider the following guidelines:
•
For proper configuration of SRP for SPAs installed in the same SIP, you should enable SRP using the hw-module subslot srp command on the POS SPA that is installed in the lower-numbered slot/subslot combination. This SPA is considered the host SRP interface.
•
You only need to configure the hw-module subslot srp command on the host SRP interface—not on the mate SRP interface.
•
The host SRP interface becomes "Side A" of the SRP interface. The slot number of the side-A interface must be lower than the slot location of the SRP mate (side B) interface. Also, you must specify the side-A interface location for configuration of any SRP options.
•
The mate keyword does not apply to the 2-Port OC-48c/STM-16 POS SPA. For a single 2-Port OC-48c/STM-16 POS SPA, mating is done internally between the two SONET ports, and no mate cabling is required.
•
The SIP reads the information it receives from the hardware cable mating to validate the mate cable connectivity with your software configuration.
•
You must shut down the POS interface before enabling SRP.
•
When you change the SPA mode, the SPA automatically reloads.
•
The entire SPA operates either in POS mode or SRP mode—you cannot have some interfaces configured for POS mode, and other interfaces configured for SRP mode.
Examples
The following example shows how to enable SRP on a 1-Port OC-192c/STM-64 POS/RPR SPA:
Router(config)# interface pos 1/0/0
Router(config-if)# shutdown
Router(config))# hw-module subslot 1/0 srp mate 1/1
Router(config)# interface srp 1/0/0
Related Commands
Command
|
Description
|
interface srp
|
Configures a POS/RPR SPA interface as an SRP interface.
|
interface
To configure an interface type and enter interface configuration mode, use the interface command in global configuration mode.
Standard Syntax
interface type number [name-tag]
Analysis Module Network Module
interface analysis-module slot/unit
Content Engine Network Module
interface content-engine slot/unit
Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor
interface type slot/port
Cisco 7200 VXR Router used as a Router Shelf in a Cisco AS5800 Universal Access Server
interface type router-shelf/slot/port
Cisco 7500 Series with Channelized T1 or E1
interface serial slot/port:channel-group
Cisco 7500 Series with Ports on VIP Cards
interface type slot/port-adapter/port
To configure a subinterface, use this form of the interface global configuration command.
Cisco 7200 Series
interface type slot/port.subinterface-number [multipoint | point-to-point]
Cisco 7500 Series
interface type slot/port-adapter.subinterface-number [multipoint | point-to-point]
Cisco 7500 Series with Ports on VIP Cards
interface type slot/port-adapter/port.subinterface-number [multipoint | point-to-point]
Shared Port Adapters
interface type slot/subslot/port[.subinterface-number]
Syntax Description
type
|
Type of interface to be configured. See Table 19-1.
|
number
|
Port, connector, or interface card number. On Cisco 4700 series routers, specifies the network interface module (NIM) or network processor module (NPM) number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command.
|
name-tag
|
(Optional) Specifies the logic name to identify the server configuration so that multiple server configurations can be entered.
This optional argument is for use with the Redundant Link Manager (RLM) feature.
|
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SIP where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
/unit
|
Number of the daughter card on the network module. For analysis module and content engine (CE) network modules, always use 0.
|
/port
|
Port or interface number.
Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.
|
router-shelf
|
Router shelf number in a Cisco AS5800 universal access server. Refer to the appropriate hardware manual for router shelf information.
|
:channel-group
|
Channel group number. Cisco 7500 series routers specify the channel group number in the range of 0 to 4 defined with the channel-group controller configuration command.
|
/port-adapter
|
Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
.subinterface-number
|
Subinterface number in the range 1 to 4294967293. The number that precedes the period (.) must match the number to which this subinterface belongs.
|
multipoint | point-to-point
|
(Optional) Specifies a multipoint or point-to-point subinterface. There is no default.
|
Defaults
No interface types are configured.
Command Modes
Global configuration
Note
To use this command with the RLM feature, you must be in interface configuration mode.
Command History
Release
|
Modification
|
10.0
|
This command was introduced for the Cisco 7000 series routers.
|
11.0
|
This command was implemented on the Cisco 4000 series routers.
|
12.0(3)T
|
The optional name-tag argument was added for the RLM feature.
|
12.2(13)T
|
The content-engine keyword was added.
|
12.2(15)T
|
The lex keyword was removed because the LAN Extension feature is no longer available in Cisco IOS software.
|
12.3(7)T
|
The analysis-module keyword was added.
|
12.2(20)S2
|
This command was implemented for SPAs on the Cisco 7304 router.
|
12.2(18)SXE
|
This command was implemented for SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was implemented for SPAs on the Cisco 12000 series routers.
|
Usage Guidelines
This command does not have a no form.
Subinterfaces can be configured to support partially meshed Frame Relay networks. Refer to the "Configuring Serial Interfaces" chapter in the Cisco IOS Interface and Hardware Component Configuration Guide.
Table 19-1 displays the keywords that represent the types of interfaces that can be configured with the interface command. Replace the type argument with the appropriate keyword from the table.
Table 19-1 Interface Type Keywords
Keyword
|
Interface Type
|
analysis-module
|
Analysis module interface. The analysis module interface is a Fast Ethernet interface on the router that connects to the internal interface on the Network Analysis Module (NAM). This interface cannot be configured for subinterfaces or for speed, duplex mode, and similar parameters. See the command-line interface (CLI) help for a list of valid parameters.
|
async
|
Port line used as an asynchronous interface.
|
atm
|
ATM interface.
|
bri
|
ISDN BRI. This interface configuration is propagated to each of the B channels. B channels cannot be individually configured. The interface must be configured with dial-on-demand commands in order for calls to be placed on that interface.
|
content-engine
|
Content engine (CE) network module interface. The CE network module interface cannot be configured for subinterfaces or for speed, duplex mode, and similar parameters. See the command-line interface (CLI) help for a list of valid parameters. The content-engine keyword was formerly documented as the interface content-engine command.
|
dialer
|
Dialer interface.
|
ethernet
|
Ethernet IEEE 802.3 interface.
|
fastethernet
|
100-Mbps Ethernet interface. The fastethernet keyword was formerly documented as the interface fastethernet command.
|
fddi
|
FDDI interface.
|
gigabitethernet
|
1000-Mbps Ethernet interface. The gigabitethernet keyword was formerly documented as the interface gigabitethernet command.
|
group-async
|
Master asynchronous interface. The group-async keyword was formerly documented as the interface group-async command.
|
hssi
|
High-Speed Serial Interface (HSSI).
|
loopback
|
Software-only loopback interface that emulates an interface that is always up. It is a virtual interface supported on all platforms. The number argument is the number of the loopback interface that you want to create or configure. There is no limit on the number of loopback interfaces that you can create.
|
null
|
Null interface.
|
port-channel
|
Port channel interface. The port-channel keyword was formerly documented as the interface port-channel command.
|
pos
|
Packet OC-3 interface on the Packet-over-SONET (POS) interface processor. The pos keyword was formerly documented as the interface pos command.
|
sdcc
|
Section data communications channel interface.
|
serial
|
Serial interface.
|
switch
|
Switch interface.
|
tokenring
|
Token Ring interface.
|
tunnel
|
Tunnel interface; a virtual interface. The number argument is the number of the tunnel interface that you want to create or configure. There is no limit on the number of tunnel interfaces that you can create.
|
vg-anylan
|
100VG-AnyLAN port adapter. The vg-anylan keyword was formerly documented as the interface vg-anylan command.
|
Using the analysis-module Keyword
The analysis module interface is used to access the NAM console for the initial configuration. After the NAM IP parameters are configured, the analysis module interface is typically used only during NAM software upgrades and while troubleshooting if the NAM Traffic Analyzer is inaccessible.
Visible only to the Cisco IOS software on the router, the analysis module interface is an internal Fast Ethernet interface on the router that connects to the internal NAM interface. The analysis module interface is connected to the router's Peripheral Component Interconnect (PCI) backplane, and all configuration and management of the analysis module interface must be performed from the Cisco IOS CLI.
Using the group-async Keyword
Using the group-async keyword, you create a single asynchronous interface with which other interfaces are associated as members using the group-range command. This one-to-many configuration allows you to configure all associated member interfaces by entering one command on the group master interface, rather than entering this command on each individual interface. You can create multiple group masters on a device; however, each member interface can be associated only with one group.
Using the port-channel Keyword
The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. You can configure the port-channel interface as you would any Fast Ethernet interface.
After you create a port-channel interface, you assign Fast Ethernet interfaces (up to four) to it. For information on how to assign a Fast Ethernet interface to a port-channel interface, refer to the channel-group interface configuration command.
Caution 
The port-channel interface is the routed interface. Do not enable Layer 3 addresses on the physical
Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces
because it creates loops. Also, you must disable spanning tree.

Caution 
With Release 11.1(20)CC, the Fast EtherChannel supports Cisco Express Forwarding (CEF) and distributed Cisco Express Forwarding (dCEF). We recommend that you clear all explicit
ip route-cache distributed commands from the Fast Ethernet interfaces before enabling dCEF on
the port-channel interface. Clearing the route cache gives the port-channel interface proper control
of its physical Fast Ethernet links. When you enable CEF/dCEF globally, all interfaces that support CEF/dCEF are enabled. When CEF/dCEF is enabled on the port-channel interface, it is automatically enabled on each of the Fast Ethernet interfaces in the channel group. However, if you have
previously disabled CEF/dCEF on the Fast Ethernet interface, CEF/dCEF is not automatically
enabled. In this case, you must enable CEF/dCEF on the Fast Ethernet interface.
As you work with the port-channel keyword, consider the following points:
•
Currently, if you want to use the Cisco Discovery Protocol (CDP), you must configure it only on the port-channel interface and not on the physical Fast Ethernet interface.
•
If you do not assign a static MAC address on the port-channel interface, the Cisco IOS software automatically assigns a MAC address. If you assign a static MAC address and then later remove it, Cisco IOS software automatically assigns a MAC address.
Using the vg-anylan Keyword
The 100VG-AnyLAN port adapter provides a single interface port that is compatible with and specified by IEEE 802.12. The 100VG-AnyLAN port adapter provides 100 Mbps over Category 3 or Category 5 unshielded twisted-pair (UTP) cable with RJ-45 terminators, and supports IEEE 802.3 Ethernet packets.
You configure the 100VG-AnyLAN port adapter as you would any Ethernet or Fast Ethernet interface. The 100VG-AnyLAN port adapter can be monitored with the IEEE 802.12 Interface MIB.
Examples
Serial Interface Example
The following example shows how to configure serial interface 0 with PPP encapsulation:
Router(config)# interface serial 0
Router(config-if)# encapsulation ppp
Loopback Interace Example
The following example shows how to enable loopback mode and assigns an IP network address and network mask to the interface. The loopback interface established here will always appear to be up.
Router(config)# interface loopback 0
Router(config-if)# ip address 10.108.1.1 255.255.255.0
Cisco 7500 Series Router Ethernet Interface Processor Example
The following example shows how to configure Ethernet port 4 on the Ethernet Interface Processor (EIP) in slot 2 on the Cisco 7500 series router:
Router(config)# interface ethernet 2/4
Cisco 7500 Series Router Token Ring Interface Example
The following example shows how to configure the Token Ring interface processor in slot 1 on port 0 of a Cisco 7500 series router:
Router(config)# interface tokenring 1/0
Network Analysis Module Interface Example
The following example configures an analysis module interface when the NAM router is in router slot 1:
Router(config)# interface analysis-module 1/0
Content Engine Network Module Interface Example
The following example configures an interface for a content engine network module in slot 1:
Router(config)# interface content-engine 1/0
Cisco 4700 Series Router Fast Ethernet Interface Example
The following example shows how to configure Fast Ethernet interface 0 for standard ARPA encapsulation (the default setting) on a Cisco 4700 series router:
Router(config)# interface fastethernet 0
Gigabit Ethernet Interface Example
The following example shows how to configure the Gigabit Ethernet interface for slot 0, port 0:
Router(config)# interface gigabitethernet 0/0
Asynchronous Group Master Interface Example
The following example shows how to define asynchronous group master interface 0:
Router(config)# interface group-async 0
Port Channel Interface Example
The following example shows how to create a port-channel interface with a channel group number of 1 and adds two Fast Ethernet interfaces to port-channel 1:
Router(config)# interface port-channel 1
Router(config-if)# ip address 10.1.1.10 255.255.255.0
Router(config)# interface fastethernet 1/0/0
Router(config-if)# channel-group 1
Router(config)# interface fastethernet 4/0/0
Router(config-if)# channel-group 1
Packet over SONET Interface Example
The following example shows how to specify the single Packet OC-3 interface on port 0 of the POS OC-3 port adapter in slot 2:
Router(config)# interface pos 2/0
100VG-AnyLAN Interface Example
The following example shows how to specify the 100VG-AnyLAN port adapter in the first port adapter in slot 1:
Router(config)# interface vg-anylan 1/0/0
Frame Relay Subinterface Example
The following example shows how to configure a partially meshed Frame Relay network. In this example, subinterface serial 0.1 is configured as a multipoint subinterface with two associated Frame Relay permanent virtual connections (PVCs), and subinterface serial 0.2 is configured as a point-to-point subinterface.
Router(config)# interface serial 0
Router(config-if)# encapsulation frame-relay
Router(config)# interface serial 0/0.1 multipoint
Router(config-if)# ip address 10.108.10.1 255.255.255.0
Router(config-if)# frame-relay interface-dlci 42 broadcast
Router(config-if)# frame-relay interface-dlci 53 broadcast
Router(config)# interface serial 0/0.2 point-to-point
Router(config-if)# ip address 10.108.11.1 255.255.255.0
Router(config-if)# frame-relay interface-dlci 59 broadcast
T1 Serial Interface Example
The following example shows how to configure circuit 0 of a T1 link for PPP encapsulation:
Router(config)# controller t1 4/1
Router(config-controller)# circuit 0 1
Router(config-controller)# exit
Router(config)# interface serial 4/1:0
Router(config-if)# ip address 10.108.13.1 255.255.255.0
Router(config-if)# encapsulation ppp
SDCC Interface on a POS Shared Port Adapter Example
The following example configures the first interface (port 0) as a section data communications channel (SDCC) interface on a POS SPA, where the SPA is installed in the top subslot (0) of the MSC, and the MSC is installed in slot 4 of the Cisco 7304 router:
Router(config)# interface sdcc 4/3/0
Router(config-if)# ip address 10.1.9.2 255.255.255.0
Router(config-if)# logging event link-status
Router(config-if)# load-interval 30
Router(config-if)# no keepalive
Router(config-if)# no fair-queue
Router(config-if)# no cdp enable
Shared Port Adapter Interface Example
The following example configures the second interface (port 1) on a 4-Port 10/100 Fast Ethernet SPA for standard ARPA encapsulation (the default setting), where the SPA is installed in the bottom subslot (1) of the MSC, and the MSC is installed in slot 2 of the Cisco 7304 router:
Router(config)# interface fastethernet 2/1/1
Related Commands
Command
|
Description
|
channel-group
|
Defines the timeslots that belong to each T1 or E1 circuit.
|
channel-group (Fast EtherChannel)
|
Assigns a Fast Ethernet interface to a Fast EtherChannel group.
|
clear interface
|
Resets the hardware logic on an interface.
|
controller
|
Configures an E1, J1, T1, or T3 controller and enters controller configuration mode.
|
group-range
|
Creates a list of asynchronous interfaces that are associated with a group interface on the same device.
|
mac-address
|
Sets the MAC layer address.
|
ppp
|
Starts an asynchronous connection using PPP.
|
show controllers content-engine
|
Displays controller information for CE network modules.
|
show interfaces
|
Displays information about interfaces.
|
show interfaces content-engine
|
Displays basic interface configuration information for a CE network module.
|
shutdown (RLM)
|
Shuts down all of the links under the RLM group.
|
slip
|
Starts a serial connection to a remote host using SLIP.
|
loopback (T3/E3 interface)
To loopback at various points in the transmit and receive path, use the loopback command in interface configuration mode. To stop the loopback, use the no form of this command.
PA-T3 Port Adapter
loopback {dte | local | network {line | payload} | remote}
no loopback
PA-E3 Port Adapter
loopback {dte | local | network {line | payload}}
no loopback
T3/E3 Shared Port Adapters
loopback {dte | local | dual | network {line | payload} | remote}
no loopback {dte | local | dual | network {line | payload} | remote}
Syntax Description
dte
|
Loopback after the line interface unit (LIU) towards the terminal.
|
local
|
Loopback after going through the framer toward the terminal.
|
dual
|
Sets both local loopback and network line loopback.
|
network {line | payload}
|
Sets the loopback toward the network before going through the framer (line) or after going through the framer (payload).
|
remote
|
Sends FEAC to set remote in loopback.
|
Defaults
No loopback by default.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
11.3
|
This command was introduced.
|
12.2(11)YT
|
This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms for E3: Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers. The dual keyword was added.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the loopback command to diagnose problems on the local port, between the framer and the line interface unit (LIU) level.
Examples
The following example creates a loopback on slot 5, bay 0 after the LIU towards the terminal.
Router# configure terminal
Router(config)# interface serial 5/0/0
Router(config-if)# loopback dte
mdl
To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification, use the mdl command in controller configuration mode.
mdl [string {eic | fic | generator | lic | pfi | port | unit}string] | [transmit {idle-signal | path |
test-signal}]
no mdl [string {eic | fic | generator | lic | pfi | port | unit}string] | [transmit {idle-signal | path |
test-signal}]
Syntax Description
string eic string
|
Specifies the Equipment Identification Code; can be up to 10 characters.
|
string fic string
|
Specifies the Frame Identification Code; can be up to 10 characters.
|
string generator string
|
Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters.
|
string lic string
|
Specifies the Location Identification Code; can be up to 11 characters.
|
string pfi string
|
Specifies the Path Facility Identification Code sent in the MDL Path message; can be up to 38 characters.
|
string port string
|
Specifies the Port number string sent in the MDL Idle Signal message; can be up to 38 characters.
|
string unit string
|
Specifies the Unit Identification Code; can be up to 6 characters.
|
transmit idle-signal
|
Enables MDL Idle-Signal message transmission.
|
transmit path
|
Enables MDL Path message transmission.
|
transmit test-signal
|
Enables MDL Test-Signal message transmission.
|
Defaults
No default behavior or values
Command Modes
Controller configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
12.1(13)EX
|
This command was introduced on the Cisco 7304 router.
|
12.2(11)YT
|
This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms: Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2 S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the mdl command to send msgs in maintainance data link in T3 c-bit framing mode.
Examples
The following example sends a test signal on the maintenance data link.
Router# configure terminal
Router(config)#controller t3 5/0/0
Router(config-controller)#mdl transmit test-signal
Related Commands
Command
|
Description
|
controller
|
Configures a T1, E1, or T3 controller and enters controller configuration mode.
|
show controllers serial
|
Displays serial line statistics.
|
show controllers pos
To display information about a Packet over SONET (POS) interface, use the show controllers pos command in privileged EXEC mode. The command does not have a no form.
Cisco 7500 Series Routers
show controllers pos [slot/port-adapter/port] [details | pm [time-interval]]
Cisco 12000 Series Routers
show controllers pos [slot/port] [details | pm [time-interval]]
POS Shared Port Adapters
show controllers pos [slot/subslot/port[/sub_int]] [alarm | details | pm [time-interval]]
Syntax Description
slot
|
(Optional) Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/port-adapter
|
(Optional) Port adapter number.
Refer to the appropriate hardware manual for information about port adapter compatibility.
|
/subslot
|
(Optional) Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
/port
|
(Optional) Port or interface number.
Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.
|
/sub_int
|
(Optional) Subinterface number.
|
alarm
|
(Optional) SONET/SDH alarm event counters.
|
details
|
(Optional) In addition to the normal information displayed by the show controllers pos command, the details keyword provides a hexadecimal and ASCII "dump" of the path trace buffer.
|
pm
|
(Optional) Displays SONET performance monitoring statistics accumulated for a 24-hour period in 15-minute intervals.
|
time-interval
|
(Optional) Number of the SONET MIB 15-minute time interval in the range from 1 to 96. If the time-interval argument is not specified, the performance monitoring statistics for the current time interval are displayed.
|
Defaults
If you do not specify any slot addressing, information for all installed POS interfaces is displayed.
The show controllers pos command with the pm keyword displays SONET performance monitoring statistics accumulated at 15-minute intervals, and these statistics can be queried using Simple Network Management Protocol (SNMP) tools. The performance monitoring statistics are collected according to the RFC 1595 specification.
The information that this command displays is generally useful only for diagnostic tasks performed by Cisco Systems technical support personnel.
If no interface is specified, the command displays information for all POS interfaces.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1CC
|
This command was introduced.
|
12.2 S
|
This command was integrated into Cisco IOS Release 12.2 S.
|
12.2(25)S3
|
This command was integrated into Cisco IOS Release 12.2(25)S3 to support SPAs on the Cisco 7304 router. The command was modified to support a new addressing format for SPAs on the Cisco 7304 router.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.
|
Examples
Example of the show controllers pos Command on the Cisco 7500 Series Router
The following is sample output from the show controllers pos command on a Cisco 7500 series router:
Router# show controllers pos
LOF = 0 LOS = 2335 BIP(B1) = 77937133
AIS = 2335 RDI = 20 FEBE = 3387950089 BIP(B2) = 1622825387
AIS = 2340 RDI = 66090 FEBE = 248886263 BIP(B3) = 103862953
LOP = 246806 NEWPTR = 11428072 PSE = 5067357 NSE = 4645
Active Defects: B2-TCA B3-TCA
Alarm reporting enabled for: B1-TCA
COAPS = 12612784 PSBF = 8339
State: PSBF_state = False
Rx(K1/K2): 00/CC Tx(K1/K2): 00/00
State: RDOOL_state = True
PATH TRACE BUFFER: UNSTABLE
Remote Rx(K1/K2): ../.. Tx(K1/K2): ../..
BER thresholds: SF = 10e-3 SD = 10e-8
TCA thresholds: B1 = 10e-7 B2 = 10e-3 B3 = 10e-6
Table 19-2 describes the fields shown in this display.
Table 19-2 show controllers pos Field Descriptions
Field
|
Description
|
POSx/y/z
|
Slot number of the POS interface.
|
LOF
|
Section loss of frame is detected when a severely error framing (SEF) defect on the incoming SONET signal persist for 3 milliseconds.
|
LOS
|
Section loss of signal is detected when an all-zeros pattern on the incoming SONET signal lasts 19 plus or minus 3 microseconds or longer. This defect might also be reported if the received signal level drops below the specified threshold.
|
BIP(B1)/BIP(B2)/BIP(B3)
|
Bit interleaved parity (BIP).
For B1, the BIP error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section-level bit errors have occurred.
For B2, the BIP error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line-level bit errors have occurred.
For B3, the BIP error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path-level bit errors have occurred.
|
AIS
|
Alarm indication signal.
A line alarm indication signal is sent by the section terminating equipment (STE) to alert the downstream line terminating equipment (LTE) that a loss of signal (LOS) or loss of frame (LOF) defect has been detected on the incoming SONET section.
A path alarm indication signal is sent by the LTE to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
|
RDI
|
Remote defect indication.
A line remote defect indication is reported by the downstream LTE when it detects LOF, LOS, or AIS.
A path remote defect indication is reported by the downstream PTE when it detects a defect on the incoming signal.
|
FEBE
|
Far end block errors.
Line FEBE (accumulated from the M0 or M1 byte) is reported when the downstream LTE detects BIP(B2) errors.
Path FEBE (accumulated from the G1 byte) is reported when the downstream PTE detects BIP(B3) errors.
|
LOP
|
Path loss of pointer is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF)-enabled indications.
|
NEWPTR
|
Inexact count of the number of times that the SONET framer has validated a new SONET pointer value (H1, H2).
|
PSE
|
Inexact count of the number of times that the SONET framer has detected a positive stuff event in the received pointer (H1, H2).
|
NSE
|
Inexact count of the number of times that the SONET framer has detected a negative stuff event in the received pointer (H1, H2).
|
Active Defects
|
List of all currently active SONET defects.
|
Active Alarms
|
List of current alarms as enforced by Sonet Alarm Hierarchy.
|
Alarm reporting enabled for
|
List of alarms for which you enabled reporting with the pos report interface command.
|
APS
|
Automatic protection switching.
|
COAPS
|
An inexact count of the number of times that a new APS value has been detected in the K1, K2 bytes.
|
PSBF
|
An inexact count of the number of times that a protection switching byte failure has been detected (no three consecutive SONET frames contain identical K1 bytes).
|
PSBF_state
|
Protection switching byte failure state.
|
Rx(K1/K2)/Tx(K1/K2)
|
Contents of the received and transmitted K1 and K2 bytes.
|
S1S0
|
The two S bits received in the last H1 byte.
|
C2
|
The value extracted from the SONET path signal label byte (C2).
|
CLOCK RECOVERY
|
The SONET clock is recovered using information in the SONET overhead. RDOOL is an inexact count of the number of times that Receive Data Out Of Lock has been detected, which indicates that the clock recovery phased lock loop is unable to lock to the receive stream.
|
PATH TRACE BUFFER
|
SONET path trace buffer is used to communicate information regarding the remote host name, interface name and number, and IP address. This is a Cisco-proprietary use of the J1 (path trace) byte.
|
BER thresholds
|
List of the bit error rate (BER) thresholds that you configured with the pos threshold interface command.
|
TCA thresholds
|
List of the threshold crossing alarms (TCAs) that you configured with the pos threshold interface command.
|
Example of the show controllers pos Command on a POS Shared Port Adapter
The following is sample output from the show controllers pos command on a Cisco 7600 series router for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot 4):
Router# show controllers pos 4/3/0
LOF = 0 LOS = 0 BIP(B1) = 65535
AIS = 0 RDI = 0 FEBE = 65535 BIP(B2) = 16777215
AIS = 0 RDI = 0 FEBE = 65535 BIP(B3) = 65535
PLM = 0 UNEQ = 0 TIM = 0 TIU = 0
LOP = 0 NEWPTR = 3 PSE = 0 NSE = 0
Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
State: PSBF_state = False
Rx(K1/K2): 00/00 Tx(K1/K2): 00/00
Rx Synchronization Status S1 = 00
Remote aps status (none); Reflected local aps status (none)
State: RDOOL_state = False
PATH TRACE BUFFER: STABLE
Remote hostname : woodson
Remote interface: POS3/0/0
Remote Rx(K1/K2): 00/00 Tx(K1/K2): 00/00
BER thresholds: SF = 10e-3 SD = 10e-6
TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6
Table 19-2 describes the fields shown in this display.
Example of the show controllers pos alarm Command on the Cisco 7600 Series Router
The following is sample output from the show controllers pos alarm command that displays SONET/SDH alarm event counters on a Cisco 7600 series router:
Router# show controllers pos3/2/0 alarm
LOF = 0 LOS = 0 B1-TCA = 0
AIS = 0 RDI = 0 RDOOL = 0
AIS = 0 RDI = 0 LOP = 0 B3-TCA = 0
Example of the show controllers pos pm Command on the Cisco 12000 Series Router
The following is sample output from the show controllers pos pm command that displays performance monitoring statistics on a Cisco 12000 series router:
Router# show controllers pos 1/0 pm
Line coding is RZ, Line type is LONG SM
Data in current interval (516 seconds elapsed)
515 Errored Secs, 515 Severely Err Secs
0 Coding Violations, 515 Sev Err Framing Secs
0 Errored Secs, 0 Severely Err Secs
0 Coding Violations, 0 Unavailable Secs
0 Errored Secs, 0 Severely Err Secs
0 Coding Violations, 0 Unavailable Secs
0 Errored Secs, 0 Severely Err Secs
0 Coding Violations, 0 Unavailable Secs
0 Errored Secs, 0 Severely Err Secs
0 Coding Violations, 0 Unavailable Secs
Table 19-3 describes the fields shown in the display.
Table 19-3 show controllers pos pm Field Descriptions
Field
|
Description
|
POSx/y
|
Slot number of the POS interface.
|
Line coding
|
Shows the current line encoding type, either return to zero (RZ) or nonreturn to zero (NRZ).
|
Line type
|
Line type for this interface. Optical line types can be either long range (LONG) or short range (SHORT), and either single mode (SM) or multimode (MM).
|
Data in current interval
|
Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. Accumulation period is from 1 to 900 seconds. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer.
|
Errored Secs
|
An errored second is a second in which one of the following is detected:
• One or more coding violations.
• One or more incoming defects (for example, a severely errored frame (SEF) defect, an LOS defect, an AIS defect, or an LOP defect).
|
Severely Err Secs
|
A severely errored second (SES) is a second with one of the following errors:
• A certain number of coding violations. The number is dependent on the line rate and the BER.
• A certain number of incoming defects.
|
Coding Violations
|
Number of coding violations for the current interval. Coding violations are defined as BIP errors that are detected in the incoming signal. The coding violations counter is incremented for each BIP error detected.
|
Sev Err Framing Secs
|
Severely errored framing seconds (SEFS) are seconds with one or more SEF defects.
|
Unavailable Secs
|
Total number of seconds for which the interface is unavailable. The interface is considered to be unavailable after a series of ten consecutive SESs.
|
Related Commands
Command
|
Description
|
pos report
|
Permits selected SONET alarms to be logged to the console for a POS interface.
|
pos threshold
|
Sets the BER threshold values of specified alarms for a POS interface.
|
show controllers serial
To display serial controller statistics, use the show controllers serial command in privileged EXEC mode.
Standard Syntax
show controllers serial [slot/port]
Cisco 7000 Series Routers with the RSP7000 and RSP7000CI and Cisco 7500 Series Routers
show controllers serial [slot/port-adapter/port]
T3/E3 Shared Port Adapters and 2-Port and 4-Port Channelized T3 SPA in Unchannelized Mode
show controllers serial [slot/subslot/port]
Channelized T3 Shared Port Adapters
show controllers serial [slot/subslot/port/t1-number]
Syntax Description
slot
|
(Optional) Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
port-adapter
|
(Optional) On Cisco 7500 series routers and Cisco 7000 series routers with the RSP7000 and RSP7000CI, the location of the port adapter on a Versatile Interface Processor (VIP). The value can be 0 or 1.
|
/subslot
|
(Optional) Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
port
|
(Optional) Port or interface number.
Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.
|
t1-number
|
(Optional) Logical T1 number in channelized mode.
For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.1CA
|
This command was modified to include support for the PA-E3 and PA-T3 port adapters.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE and introduced a new output for interfaces on the serial SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
The output from the show controllers serial command provides error and alarm information that is useful in troubleshooting line problems.
The information displayed is generally useful for diagnostic tasks performed by Cisco Systems technical support personnel only. For the PA-E3 or PA-T3 port adapters, the show controllers serial command also displays configuration information such as the framing, clock source, bandwidth limit, whether scrambling is enabled, the national bit, the international bits, and DSU mode configured on the interface. Also displayed are the performance statistics for the current interval and last 15-minute interval and whether any alarms exist.
Examples
Example of the show controllers serial Command on the Cisco 4000 Series Router
The following is sample output from the show controllers serial command on the Cisco 4000:
Router# show controllers serial
MK5 unit 0, NIM slot 1, NIM type code 7, NIM version 1
idb = 0x6150, driver structure at 0x34A878, regaddr = 0x8100300
IB at 0x6045500: mode=0x0108, local_addr=0, remote_addr=0
N1=1524, N2=1, scaler=100, T1=1000, T3=2000, TP=1
DTE V.35 serial cable attached
RX ring with 32 entries at 0x45560 : RLEN=5, Rxhead 0
00 pak=0x6044D78 ds=0x6044ED4 status=80 max_size=1524 pak_size=0
01 pak=0x60445F0 ds=0x604474C status=80 max_size=1524 pak_size=0
02 pak=0x6043E68 ds=0x6043FC4 status=80 max_size=1524 pak_size=0
03 pak=0x60436E0 ds=0x604383C status=80 max_size=1524 pak_size=0
04 pak=0x6042F58 ds=0x60430B4 status=80 max_size=1524 pak_size=0
05 pak=0x60427D0 ds=0x604292C status=80 max_size=1524 pak_size=0
06 pak=0x6042048 ds=0x60421A4 status=80 max_size=1524 pak_size=0
07 pak=0x60418C0 ds=0x6041A1C status=80 max_size=1524 pak_size=0
08 pak=0x6041138 ds=0x6041294 status=80 max_size=1524 pak_size=0
09 pak=0x60409B0 ds=0x6040B0C status=80 max_size=1524 pak_size=0
10 pak=0x6040228 ds=0x6040384 status=80 max_size=1524 pak_size=0
11 pak=0x603FAA0 ds=0x603FBFC status=80 max_size=1524 pak_size=0
12 pak=0x603F318 ds=0x603F474 status=80 max_size=1524 pak_size=0
13 pak=0x603EB90 ds=0x603ECEC status=80 max_size=1524 pak_size=0
14 pak=0x603E408 ds=0x603E564 status=80 max_size=1524 pak_size=0
15 pak=0x603DC80 ds=0x603DDDC status=80 max_size=1524 pak_size=0
16 pak=0x603D4F8 ds=0x603D654 status=80 max_size=1524 pak_size=0
17 pak=0x603CD70 ds=0x603CECC status=80 max_size=1524 pak_size=0
18 pak=0x603C5E8 ds=0x603C744 status=80 max_size=1524 pak_size=0
19 pak=0x603BE60 ds=0x603BFBC status=80 max_size=1524 pak_size=0
20 pak=0x603B6D8 ds=0x603B834 status=80 max_size=1524 pak_size=0
21 pak=0x603AF50 ds=0x603B0AC status=80 max_size=1524 pak_size=0
22 pak=0x603A7C8 ds=0x603A924 status=80 max_size=1524 pak_size=0
23 pak=0x603A040 ds=0x603A19C status=80 max_size=1524 pak_size=0
24 pak=0x60398B8 ds=0x6039A14 status=80 max_size=1524 pak_size=0
25 pak=0x6039130 ds=0x603928C status=80 max_size=1524 pak_size=0
26 pak=0x60389A8 ds=0x6038B04 status=80 max_size=1524 pak_size=0
27 pak=0x6038220 ds=0x603837C status=80 max_size=1524 pak_size=0
28 pak=0x6037A98 ds=0x6037BF4 status=80 max_size=1524 pak_size=0
29 pak=0x6037310 ds=0x603746C status=80 max_size=1524 pak_size=0
30 pak=0x6036B88 ds=0x6036CE4 status=80 max_size=1524 pak_size=0
31 pak=0x6036400 ds=0x603655C status=80 max_size=1524 pak_size=0
TX ring with 8 entries at 0x45790 : TLEN=3, TWD=7
tx_count = 0, tx_head = 7, tx_tail = 7
00 pak=0x000000 ds=0x600D70C status=0x38 max_size=1524 pak_size=22
01 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
02 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
03 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
04 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
05 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
06 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2
07 pak=0x000000 ds=0x6000000 status=0x38 max_size=1524 pak_size=0
XID/Test TX desc at 0xFFFFFF, status=0x30, max_buffer_size=0, packet_size=0
XID/Test RX desc at 0xFFFFFF, status=0x0, max_buffer_size=0, packet_size=0
Status Buffer at 0x60459C8: rcv=0, tcv=0, local_state=0, remote_state=0
phase=0, tac=0, currd=0x00000, curxd=0x00000
bad_frames=0, frmrs=0, T1_timeouts=0, rej_rxs=0, runts=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 user primitive errors
0 provider primitives lost, 0 unexpected provider primitives
0 spurious primitive interrupts, 0 memory errors, 0 tr
%LINEPROTO-5-UPDOWN: Linansmitter underruns
mk5025 registers: csr0 = 0x0E00, csr1 = 0x0302, csr2 = 0x0704
csr3 = 0x5500, csr4 = 0x0214, csr5 = 0x0008
Example of the show controllers serial Command for a PA-E3 Serial Port Adapter
The following is sample output from the show controllers serial command for a PA-E3 serial port adapter installed in slot 2:
Router# show controllers serial 2/0
M1T-E3 pa: show controller:
PAS unit 0, subunit 0, f/w version 2-55, rev ID 0x2800001, version 2
idb = 0x6080D54C, ds = 0x6080F304, ssb=0x6080F4F4
Clock mux=0x30, ucmd_ctrl=0x0, port_status=0x1
Serial config=0x8, line config=0x1B0202
maxdgram=4474, bufpool=128Kb, 256 particles
rxLOS inactive, rxLOF inactive, rxAIS inactive
txAIS inactive, rxRAI inactive, txRAI inactive
E3 DTE cable, received clockrate 50071882
base0 registers=0x3D000000, base1 registers=0x3D002000
mxt_ds=0x608BA654, rx ring entries=128, tx ring entries=256
rxring=0x4B01F480, rxr shadow=0x6081081C, rx_head=26
txring=0x4B01F960, txr shadow=0x60810E48, tx_head=192, tx_tail=192, tx_count=0
throttled=0, enabled=0, disabled=0
rx_no_eop_err=0, rx_no_stp_err=0, rx_no_eop_stp_err=0
rx_no_buf=0, rx_soft_overrun_err=0, dump_err= 1
tx_underrun_err=0, tx_soft_underrun_err=0, tx_limited=0
tx_fullring=0, tx_started=11504
Framing is g751, Clock Source is Line, Bandwidth limit is 34010.
National Bit is 0, International Bits are: 0 0
Data in current interval (213 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 P-bit Err Secs, 0 P-bit Severely Err Secs
0 Severely Err Framing Secs, 0 Unavailable Secs
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 P-bit Coding Violation,
0 C-bit Coding Violation,
0 P-bit Err Secs, 0 P-bit Severely Err Secs,
0 Severely Err Framing Secs, 0 Unavailable Secs,
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Example of the show controllers serial Command for a PA-T3 Serial Port Adapter
The following is sample output from the show controllers serial command that shows serial port 1/0/0 on a 1-port PA-T3 serial port adapter installed on a VIP2 in chassis slot 1:
Router# show controllers serial 2/0/1
Mx T3(1) HW Revision 0x3, FW Revision 2.55
Framing is c-bit, Clock Source is Line
Bandwidth limit is 35000, DSU mode 1, Cable length is 50
Data in current interval (325 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 P-bit Err Secs, 0 P-bit Sev Err Secs
0 Sev Err Framing Secs, 0 Unavailable Secs
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 P-bit Coding Violation,
0 C-bit Coding Violation,
0 P-bit Err Secs, 0 P-bit Sev Err Secs,
0 Sev Err Framing Secs, 0 Unavailable Secs,
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs
Example of the show controllers serial Command for a Channelized T3 SPA
The following is sample output from the show controllers serial command for a 2 or 4-Port CT3 SPA located in slot 3 of a Cisco 7304 router:
Router# show controllers serial
Framing is c-bit, Clock Source is Internal
Bandwidth limit is 44210, DSU mode 0, Cable length is 10
rx FEBE since last clear counter 0, since reset 0
Data in current interval (0 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 P-bit Err Secs, 0 P-bit Sev Err Secs
0 Sev Err Framing Secs, 0 Unavailable Secs
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs
0 Severely Errored Line Secs
0 Far-End Errored Secs, 0 Far-End Severely Errored Secs
0 CP-bit Far-end Unavailable Secs
0 Near-end path failures, 0 Far-end path failures
0 Far-end code violations, 0 FERF Defect Secs
0 AIS Defect Secs, 0 LOS Defect Secs
Transmitter is sending AIS.
Receiver has loss of signal.
Framing is c-bit, Clock Source is Line
Bandwidth limit is 44210, DSU mode 0, Cable length is 10
rx FEBE since last clear counter 0, since reset 0
Data in current interval (757 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 P-bit Err Secs, 0 P-bit Sev Err Secs
0 Sev Err Framing Secs, 0 Unavailable Secs
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs
0 Severely Errored Line Secs
0 Far-End Errored Secs, 0 Far-End Severely Errored Secs
0 CP-bit Far-end Unavailable Secs
0 Near-end path failures, 0 Far-end path failures
0 Far-end code violations, 0 FERF Defect Secs
0 AIS Defect Secs, 0 LOS Defect Secs
Table 19-4 describes the fields shown in the show controllers serial output.
Note
The fields appearing in the ouput will vary depending on card type, controller configuration, and the status of the controller line.
Table 19-4 show controllers serial Field Descriptions
Field
|
Description
|
Serial
|
Name of the serial controller.
|
Framing
|
Framing type.
|
Clock source
|
Source of the synchronization signal (clock).
|
Bandwidth limit
|
The allowable bandwidth for the controller.
|
DSU mode
|
The Data Service Unit (DSU) interoperability mode.
|
Cable length
|
The distance to the first repeater.
|
rx FEBE since last clear counter
|
Number of received far-end block errors.
Note Line far-end block error (accumulated from the M0 or M1 byte) is reported when the downstream LTE detects BIP(B2) errors. Path far-end block error (accumulated from the G1 byte) is reported when the downstream PTE detects BIP(B3) errors.
|
rx FEBE since last reset
|
Number of received far-end block errors.
|
Line Code Violations
|
Number of Bipolar Violation (BPV) errors or Excessive Zeros (EXZ) errors.
|
P-bit Coding Violations
|
Number of P-bit errors encountered between source and destination.
|
C-bit coding violations
|
Number of C-bit errors encountered between source and destination.
|
P-bit Err Secs (PES)
|
Number of seconds with P-bit errors.
Note A PES is a second with one or more PCVs or one or more Out of Frame defects or a detected incoming AIS. This gauge is not incremented when UASs are counted.
|
P-bit Sev Err Secs (PSES)
|
Number of seconds with P-bit severe errors.
Note A PSES is a second with 44 or more PCVs or one or more Out of Frame defects or a detected incoming AIS. This gauge is not incremented when UASs are counted.
|
Sev Err Framing Secs
|
The number of 1-second intervals in which either a Remote Alarm Indication was received or a Loss Of Frame condition occurred.
|
Unavailable Secs
|
The number of 1-second intervals in which the controller was down.
|
Line Errored Secs
|
The number of 1-second intervals in which a Line Code Violation occurred.
|
C-bit Errored Secs (CES)
|
Number of seconds with C-bit errors.
Note A CES is a second with one or more CCVs or one or more Out of Frame defects or a detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3 applications. This gauge is not incremented when UASs are counted.
|
C-bit Sev Err Secs (CSES)
|
Number of seconds with severe C-bit errors.
Note A CSES is a second with 44 or more CCVs or one or more Out of Frame defects or a detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3 applications. This gauge is not incremented when UASs are counted.
|
Severely Errored Line Secs
|
For ESF signals, this is a second in which one of the following defects is detected:
• 320 or more Path Code Violation errors.
• One or more Out of Frame defects.
• An AIS defect.
For E1-CRC signals, this is a second with one of the following errors:
• 832 or more Path Code Violation errors.
• One or more Out of Frame defects.
For E1-nonCRC signals, this is a second with 2048 or more Line Code Violations.
|
Far-End Errored Secs
|
Number of seconds of far-end failures.
|
Far-End Severely Errored Secs
|
The number of 1-second intervals in which either a Remote Alarm Indication was received or a Loss Of Frame condition occurred.
|
P-bit Unavailable Secs
|
Number of seconds the interface is unavailable because of P-bit errors.
|
CP-bit Unavailable Secs
|
Number of seconds the interface is unavailable because of CP-bit errors.
|
CP-bit Far-end Unavailable Secs
|
Number of seconds the interface is unavailable because of CP-bit errors from the far-end device.
|
Near-end path failures
|
|
Far-end path failures
|
|
Far-end code violations
|
|
FERF Defect Secs
|
Number of far-end receive failures detected per second.
|
AIS Defect Secs
|
Number of alarm indication signals per second.
|
LOS Defect Secs
|
Number of loss of signal alarms per second.
|
Path Code Violations
|
Indicates a frame synchronization bit error in the D4 and E1-no CRC formats, or a CRC error in the Extended Superframe (ESF) and E1-CRC formats.
|
Slip Secs
|
Indicates the replication or deletion of the payload bits of a domestic trunk interface (DS1) frame. A slip might happen when there is a difference between the timing of a synchronous receiving terminal and the received signal.
|
Fr Loss Secs
|
Indicates the number of seconds an Out of Frame (OOF) error is detected.
|
Line Err Secs
|
Line Errored Seconds (LES) is a second in which one or more Line Code Violation errors are detected.
|
Degraded Mins
|
A degraded minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3.
|
Errored Secs
|
In ESF and E1-CRC links, an errored second is a second in which one of the following defects is detected:
• One or more Path Code Violations.
• One or more Controlled Slip events.
Note For SF and E1 no-CRC links, the presence of Bipolar Violations also triggers an errored second.
|
Bursty Err Secs
|
A second with more than one but fewer than 320 Path Coding Violation errors, no Severely Errored Frame defects, and no detected incoming AIS defects. Controlled slips are not included in this parameter.
|
show diag
To display diagnostic information about the controller, interface processor, and port adapters for a networking device, use the show diag command in privileged EXEC mode.
show diag [slot-number | subslot slot/subslot] [details | summary]
Syntax Description
slot-number
|
(Optional) Slot number of the interface. If a slot number is not specified, diagnostic information for all slots is displayed.
|
subslot slot/subslot
|
(Optional) Specifies the display of diagnostic information about the shared port adapter (SPA), where:
• slot—Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
• subslot—Secondary slot number on a SIP where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
details
|
(Optional) Displays more details than the normal show diag output.
|
summary
|
(Optional) Displays a summary (one line per slot) of the chassis.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
11.2 GS
|
This command was implemented on the Cisco 12000 series.
|
12.0
|
This command was implemented on the Cisco AS5300.
|
12.0(7)T
|
This command was implemented on the Cisco 1750 router.
|
12.2(8)T
|
This command was implemented for AIC and WIC cards on the Cisco 2600 series and the Cisco 3600 series.
|
12.2(13)T
|
This command was implemented for the AIM-VPN/EPII and AIM-VPN/HPII cards on the following platforms: Cisco 2691, Cisco 3660, Cisco 3725, and Cisco 3745.
|
12.2(15)ZJ
|
This command was implemented for the AIM-VPN/BPII card on the following platforms: Cisco 2610XM, Cisco 2611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM, and Cisco 2651XM.
|
12.3(4)T
|
Support for the AIM-VPN/BPII card on the Cisco 2600XM series was integrated into Cisco IOS Release 12.3(4)T.
|
12.0(31)S
|
This command was modified in Cisco IOS Release 12.0(31)S. The subslot keyword is added to support slot/subslot addressing for SIPs and SPAs on the Cisco 12000 series routers.
|
Usage Guidelines
Use this command to determine the type of hardware installed in your networking device. This command displays information for the EEPROM, motherboard, WAN interface cards (WICs), voice interface cards (VICs), ATM interface cards (AICs), and advanced integration modules (AIMs).
Examples
Example for a 1-Port T3 Serial Port Adapter
The following is sample output from the show diag command for a 1-port T3 serial port adapter in chassis slot 1 on a Cisco 7200 series router:
Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0
Master Enable, LED, WCS Loaded
VIP2 controller, HW rev 2.4, board revision D0
Serial number: 04372053 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
0x20: 01 15 02 04 00 42 B6 55 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x14A8 (5d02h ago)
Controller Memory Size: 16 MBytes DRAM, 1024 KBytes SRAM
HW rev FF.FF, Board revision UNKNOWN
Serial number: 4294967295 Part number: 255-65535-255
Examples for a Cisco 12000 Series Internet Router
The following is sample output from the show diag command on a Cisco 12000 series Internet router:
SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi Mode
MAIN: type 33, 00-0000-00 rev 70 dev 0
HW config: 0x01 SW key: 00-00-00
PCA: 73-2147-02 rev 94 ver 2
HW version 1.0 S/N 04499695
MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0
HW version 1.1 S/N 04494882
Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
DIAG: Test count: 0x05000001 Test results: 0x00000000
MBUS Agent Software version 01.27 (RAM) using CAN Bus A
ROM Monitor version 00.0D
Fabric Downloader version used 00.0D (ROM version is 00.0D)
Board State is Line Card Enabled (IOS RUN )
Insertion time: 00:00:10 (00:04:51 ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 67108864 bytes
ToFab SDRAM size: 16777216 bytes
The following is sample output from the show diag command with the summary keyword:
Router# show diag summary
SLOT 0 (RP/LC 0 ): Route Processor
SLOT 2 (RP/LC 2 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 4 (RP/LC 4 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 7 (RP/LC 7 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 9 (RP/LC 9 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 11 (RP/LC 11): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 16 (CSC 0 ): Clock Scheduler Card
SLOT 17 (CSC 1 ): Clock Scheduler Card
SLOT 18 (SFC 0 ): Switch Fabric Card
SLOT 19 (SFC 1 ): Switch Fabric Card
SLOT 20 (SFC 2 ): Switch Fabric Card
SLOT 24 (PS A1 ): AC Power Supply
SLOT 26 (PS B1 ): AC Power Supply
SLOT 28 (TOP FAN ): Blower Module
SLOT 29 (BOT FAN ): Blower Module
The following is sample output from the show diag command with the details keyword:
Router# show diag 4 details
SLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
MAIN: type 33, 800-2389-01 rev 71 dev 16777215
HW config: 0x00 SW key: FF-FF-FF
PCA: 73-2275-03 rev 75 ver 3
HW version 1.1 S/N 04529465
MBUS: MBUS Agent (1) 73-2146-06 rev 73 dev 0
HW version 1.1 S/N 04541395
Test hist: 0xFF RMA#: FF-FF-FF RMA hist: 0xFF
DIAG: Test count: 0x05000001 Test results: 0x00000000
00: 01 00 01 00 49 00 08 62 06 03 00 00 00 FF FF FF
10: 30 34 35 34 31 33 39 35 FF FF FF FF FF FF FF FF
20: 01 01 00 00 00 00 00 FF FF FF FF FF FF FF FF FF
30: A5 FF A5 A5 A5 A5 FF A5 A5 A5 A5 A5 A5 A5 A5 A5
40: 00 21 01 01 00 49 00 08 E3 03 05 03 00 01 FF FF
50: 03 20 00 09 55 01 01 FF FF FF 00 FF FF FF FF FF
60: 30 34 35 32 39 34 36 35 FF FF FF FF FF FF FF FF
70: FF FF FF FF FF FF FF FF 05 00 00 01 00 00 00 00
MBUS Agent Software version 01.24 (RAM)
Fabric Downloader version 00.0D
Board State is Line Card Enabled (IOS RUN)
Insertion time: 00:00:10 (00:04:51 ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 67108864 bytes
ToFab SDRAM size: 16777216 bytes
Example for an ATM SAR AIM in a Cisco 3660
The following is sample output from the show diag command for one ATM Segmentation and Reassembly (SAR) AIM in a Cisco 3660 router:
3660 Chassis type: ENTERPRISE
Top Assy. Part Number : 800-04740-02
ATM AIM module with SAR only (no DSPs)
Top Assy. Part Number : 800-03700-01
PCB Serial Number : JAB9801ABCD
Example for an NM-AIC-64 Installed in a Cisco 2611
The following is sample output from the show diag command for a Cisco 2611 router with the NM-AIC-64 installed.
Slot 0:
C2611 2E Mainboard Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 2.3
PCB Serial Number : JAD044808SG (1090473337)
Part Number : 73-2840-13
RMA History : 00
RMA Number : 0-0-0-0
Board Revision : C0
Deviation Number : 0-0
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 92 41 02 03 C1 18 4A 41 44 30 34 34
0x10: 38 30 38 53 47 20 28 31 30 39 30 34 37 33 33 33
0x20: 37 29 82 49 0B 18 0D 04 00 81 00 00 00 00 42 43
0x30: 30 80 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Slot 1:
NM_AIC_64 Port adapter, 3 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 1.0
Part Number : 74-1923-01
Board Revision : 02
PCB Serial Number : DAN05060012
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 02 55 41 01 00 82 4A 07 83 01 42 30 32
0x10: C1 8B 44 41 4E 30 35 30 36 30 30 31 32 FF FF FF
0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Table 19-5 describes significant fields shown in the display.
Table 19-5 show diag (AIC) Field Descriptions
Field
|
Description
|
C2611 2E Mainboard Port adapter, 2 ports
|
Line card type; number of ports available.
|
Port adapter is analyzed
|
The system has identified the port adapter.
|
Port adapter insertion time
|
Elapsed time since insertion.
|
Hardware Revision
|
Version number of the port adapter.
|
PCB Serial Number
|
Serial number of the printed circuit board.
|
Part Number
|
Part number of the port adapter.
|
RMA History
|
Counter that indicates how many times the port adapter has been returned and repaired.
|
RMA Number
|
Return material authorization number, which is an administrative number assigned if the port adapter needs to be returned for repair.
|
Board Revision
|
Revision number (signifying a minor revision) of the port adapter.
|
Deviation Number
|
Revision number (signifying a minor deviation) of the port adapter.
|
EEPROM format version
|
Version number of the EEPROM format.
|
EEPROM contents (hex)
|
Dumps of EEPROM programmed data.
|
Example for an AIM-VPN in a Cisco 2611XM
The following example shows how to obtain hardware information about an installed AIM-VPN on the Cisco 2611XM router.
Router# show diag 0
Encryption AIM 1:
Hardware Revision :1.0
Top Assy. Part Number :800-03700-01
Board Revision :A0
Deviation Number :0-0
Fab Version :02
PCB Serial Number :JAB9801ABCD
RMA Test History :00
RMA Number :0-0-0-0
RMA History :00
EEPROM format version 4
EEPROM contents (hex):
0x00:04 FF 40 03 0B 41 01 00 C0 46 03 20 00 0E 74 01
0x10:42 41 30 80 00 00 00 00 02 02 C1 8B 4A 41 42 39
0x20:38 30 31 41 42 43 44 03 00 81 00 00 00 00 04 00
0x30:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Table 19-6 describes significant fields shown in the display.
Table 19-6 show diag (AIM-VPN) Field Descriptions
Field
|
Description
|
Hardware Revision
|
Version number of the port adapter.
|
Top Assy. Part Number
|
Part number of the port adapter.
|
Board Revision
|
Revision number (signifying a minor revision) of the port adapter.
|
Deviation Number
|
Revision number (signifying a minor deviation) of the port adapter.
|
PCB Serial Number
|
Serial number of the printed circuit board.
|
RMA Number
|
Return material authorization number, which is an administrative number assigned if the port adapter needs to be returned for repair.
|
RMA History
|
Counter that indicates how many times the port adapter has been returned and repaired.
|
EEPROM format version
|
Version number of the EEPROM format.
|
EEPROM contents (hex)
|
Dumps of EEPROM programmed data.
|
Examples for a Shared Port Adapter on a Cisco 12000 Series Router
The following is sample output from the show diag subslot command for the 1-Port OC-192c/STM-64 POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1
SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter
Product Identifier (PID) : SPA-OC192POS-XFP
Version Identifier (VID) : V01
PCB Serial Number : PRTA1304061
Top Assy. Part Number : 68-2190-01
Insertion Time : 00:00:10 (13:14:17 ago)
Table 19-6 describes the significant fields shown in the display.
Table 19-7 show diag subslot Field Descriptions
Field
|
Description
|
Product Identifier (PID)
|
Product number of the SPA.
|
Version Identifier (VID)
|
Version number of the SPA.
|
PCB Serial Number
|
Serial number of the printed circuit board.
|
Top Assy. Part Number
|
Part number of the SPA.
|
Top Assy. Revision
|
Revision number (signifying a minor revision) of the SPA.
|
Hardware Revision
|
Revision number (signifying a minor revision) of the SPA hardware.
|
CLEI Code
|
Common Language Equipment Identification number.
|
Insertion Time
|
Time when the SPA was installed, and elapsed time between that insertion time and the current time.
|
Operational Status
|
Current status of the SPA. For more information about the status field descriptions, refer to the show hw-module subslot oir command.
|
The following is sample output from the show diag subslot details command for the 1-Port OC-192c/STM-64 POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1 details
SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter
PCB Serial Number : PRTA1304061
PCB Part Number : 73-8546-01
PCB Revision : A0 Fab Version : 01
Product Identifier (PID) : SPA-OC192POS-XFP
Version Identifier (VID) : V01
Top Assy. Part Number : 68-2190-01
Top Assy. Revision : A0 IDPROM Format Revision : 36
System Clock Frequency : 00 00 00 00 00 00 00 00
Base MAC Address : 00 00 00 00 00 00
MAC Address block size : 0
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data : 00 00 00 00 00 00 00 00
Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmV
Power Consumption : 11000 mWatts (Maximum)
Environment Monitor Data : 03 30 04 B0 46 32 07 08
Processor Label : 00 00 00 00 00 00 00
Platform features : 00 00 00 00 00 00 00 00
Insertion Time : 00:00:10 (13:14:24 ago)
Example for a SPA Interface Processor on a Cisco 12000 Series Router
The following is sample output from the show diag command for a SIP located in chassis slot 2 on a Cisco 12000 series router:
SLOT 2 (RP/LC 2 ): Modular 10G SPA Interface Card
MAIN: type 149, 800-26270-01 rev 84
HW config: 0x00 SW key: 00-00-00
PCA: 73-9607-01 rev 91 ver 1
Design Release 1.0 S/N SAD08460678
Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
DIAG: Test count: 0x00000000 Test results: 0x00000000
FRU: Linecard/Module: 12000-SIP-650
FRU: Linecard/Module: 12000-SIP-650
Processor Memory: MEM-LC5-1024=(Non-Replaceable)
Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)
L3 Engine: 5 - ISE OC192 (10 Gbps)
MBUS Agent Software version 1.114 (RAM) (ROM version is 3.4)
ROM Monitor version 255.255
Fabric Downloader version used 3.7 (ROM version is 255.255)
Board State is Line Card Enabled (IOS RUN )
Insertion time: 1d00h (2d08h ago)
Processor Memory size: 1073741824 bytes
TX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
RX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
subslot 2/0: SPA-OC192POS-XFP (0x44C), status is ok
Related Commands
Command
|
Description
|
dsl operating-mode (ADSL)
|
Modifies the operating mode of the digital subscriber line for an ATM interface.
|
show dsl interface atm
|
Shows all of the ADSL-specific information for a specified ATM interface.
|
show hw-module all fpd
To display the current versions of all field-programmable devices (FPDs) for all of the supported card types on a router, enter the show hw-module all fpd command in privileged EXEC configuration mode.
show hw-module all fpd
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(18)SXE
|
This command was introduced.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Other than the FPD version information, the output for this command may also contain useful FPD-related notes.
Examples
This example shows FPD image file versions for all SIPs and SPAs in the Cisco 7600 series router:
Router# show hw-module all fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Type Ver. Device: "ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
4 7600-SIP-200 0.132 1-I/O FPGA 0.19 0.18
3-PEGASUS TX FPGA 0.121 0.121
4-PEGASUS RX FPGA 0.13 0.13
---- ---------------------- ------ ------------------ ----------- --------------
4/0 SPA-4XOC3-ATM 1.0 1-I/O FPGA 0.121 0.121
---- ---------------------- ------ ------------------ ----------- --------------
4/1 SPA-8XCHT1/E1 0.117 1-ROMMON 2.12 2.12
---- ---------------------- ------ ------------------ ----------- --------------
4/3 SPA-4XCT3/DS0 0.253 1-ROMMON 2.12 2.12
3-T3 SUBRATE FPGA 0.15 0.15
==== ====================== ====== =============================================
This example shows FPD image file versions that require an upgrade (indicated by the asterisk) for two SIPs in the Cisco 7600 series router. The SIPs are disabled due to the version mismatch:
Router# show hw-module all fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Type Ver. Device: "ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
1 7600-SIP... <DISABLED> 0.550 1-I/O FPGA 1.1 1.1
3-PEGASUS TX FPGA 1.129 1.129
4-PEGASUS RX FPGA 1.3 1.3
---- ---------------------- ------ ------------------ ----------- --------------
4 7600-SIP... <DISABLED> 0.550 1-I/O FPGA 1.1 1.1
3-PEGASUS TX FPGA 1.129 1.129
4-PEGASUS RX FPGA 1.3 1.3
==== ====================== ====== =============================================
- FPD images that are required to be upgraded are indicated with a '*'
character in the "Minimal Required Version" field.
- The following FPD image package file is required for the upgrade:
"c7600-fpd-pkg.122-18.SXE.pkg"
Related Commands
Command
|
Description
|
show hw-module slot fpd
|
Displays the current versions of all FPDs for a SIP in the specified slot location and for all of the SPAs installed in that SIP.
|
show hw-module subslot fpd
|
Displays the current versions of all FPDs for a particular SPA or all of the active SPAs on a router.
|
show hw-module subslot fpd
To display the current versions of all field-programmable devices (FPDs) for a particular SPA or all of the active SPAs on a router, enter the show hw-module subslot fpd command in privileged EXEC configuration mode.
Cisco 7304 Router
show hw-module subslot [slot/subslot] fpd
Cisco 7600 and Cisco 12000 Series Routers
show hw-module subslot {slot/subslot | all} fpd
Syntax Description
slot
|
Chassis slot number.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address" topic in the platform-specific SPA software configuration guide for subslot information.
|
all
|
Specifies display of FPD information for all SPAs in the system.
Note The all keyword is not supported for SPAs on the Cisco 7304 router.
|
Defaults
For the Cisco 7304 router, if no location is specified, the output for this command will show information for all supported card types on the router.
For the Cisco 7600 and Cisco 12000 series routers, there is no default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(20)S2
|
This command was introduced.
|
12.2(18)SXE
|
The all keyword was added in Cisco IOS Release 12.2(18)SXE on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S and introduced on Cisco 12000 series routers.
|
Usage Guidelines
Other than the FPD version information, the output for this command may also contain useful FPD-related notes.
Cisco 7304 Router
The all keyword is not supported on the Cisco 7304 router. The slot/subslot arguments are optional, and if you do not specify them, the command displays FPD information for all supported card types on the router.
Cisco 7600 and 12000 Series Routers
If you do not use the all keyword, then you must specify the slot/subslot arguments to select the location of a particular card. There is no default behavior for this command on the Cisco 7600 series routers.
Examples
Displaying FPD Information for a Particular SPA Example
This example shows the output when using the slot/subslot arguments to identify a particular SPA. This SPA meets the minimum FPD requirements with that particular Cisco IOS Release:
Router# show hw-module subslot 4/0 fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Description Ver. Device: "ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
4/0 SPA-4XOC3-ATM 1.0 1-I/O FPGA 0.121 0.121
==== ====================== ====== =============================================
Displaying FPD Information for all SPAs in the System Example
This example shows FPD image file versions for all SPAs in the system:
Router# show hw-module subslot all fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Type Ver. Device: "ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
4/0 SPA-4XOC3-ATM 1.0 1-I/O FPGA 0.121 0.121
---- ---------------------- ------ ------------------ ----------- --------------
4/1 SPA-8XT1/E1 0.143 1-ROMMON 2.12 2.12
---- ---------------------- ------ ------------------ ----------- --------------
4/3 SPA-4XOC3-POS 0.100 1-I/O FPGA 3.4 3.4
---- ---------------------- ------ ------------------ ----------- --------------
7/0 SPA-8XCHT1/E1 0.117 1-ROMMON 2.12 2.12
---- ---------------------- ------ ------------------ ----------- --------------
7/1 SPA-4XOC3-ATM 0.205 1-I/O FPGA 0.121 0.121
==== ====================== ====== =============================================
Displaying Information for all SPAs in the System Example (Cisco 7304 only)
The all keyword is not supported on the Cisco 7304 router.
To display all FPD image file versions for all SPAs on a Cisco 7304 router, enter the show hw-module subslot fpd command without specifying a slot and subslot. The following example shows all FPD image file versions on a Cisco 7304 router:
Router# show hw-module subslot fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Description Ver. Device:"ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
2/0 SPA-4FE-7304 0.32 1-Data & I/O FPGA 4.13 4.13
---- ---------------------- ------ ------------------ ----------- --------------
2/1 SPA-2GE-7304 0.15 1-Data & I/O FPGA 4.13 4.13
==== ====================== ====== =============================================
Related Commands
Command
|
Description
|
show hw-module all fpd
|
Displays the current versions of all FPDs for all of the supported card types on a router.
|
show hw-module slot fpd
|
Displays the current versions of all FPDs for a SIP in the specified slot location on a router, and for all of the SPAs installed in that SIP.
|
show hw-module subslot oir
To display the operational status of a shared port adapter (SPA), use the show hw-module subslot oir command in privileged EXEC configuration mode. The command does not have a no form.
show hw-module subslot {slot/subslot | all} oir [internal]
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
all
|
Displays OIR status for all supported card types in the system.
|
internal
|
(Optional) Displays detailed diagnostic information. This option is intended for internal diagnostic use with Cisco Systems technical support personnel.
|
Defaults
No default behavior or values
If no location is specified, the output for this command will show information for all SPAs in the router.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S3
|
This command was introduced.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Use the show hw-module subslot oir command to obtain operational status information about one or all SPAs. To display information for a specific SPA, specify the slot number of the SIP and the subslot number of the SPA about which you want information. To display information for all SPAs in the router, do not specify the slot/subslot arguments and use the all keyword.
The optional internal keyword displays detailed diagnostic information that is recommended only for use with Cisco Systems technical support personnel.
Note
The following status descriptions are not applicable to every SPA and can be platform-specific.
Examples
The following example shows the operational status of all of the SPAs installed in a router where two of the SPAs are in an out-of-service condition:
Router# show hw-module subslot all oir
Module Model Operational Status
-------------- ------------------ -------------------------
subslot 4/0 SPA-4XOC3-POS booting
subslot 4/1 SPA-4XOC3-ATM out of service(FPD upgrade failed)
subslot 4/2 SPA-4XOC3-POS ok
subslot 4/3 SPA-1XTENGE-XFP out of service(SPA unrecognized)
Table 19-8 describes the possible values for the Operational Status field in the output.
Table 19-8 Operational Status Field Descriptions
Operational Status
|
Description
|
admin down
|
SPA is administratively disabled by the hw-module subslot shutdown global configuration command.
|
booting
|
SPA is initializing.
|
missing
|
SPA is not present in the SIP subslot.
|
ok
|
SPA is operational.
|
out of service (reason)
|
The SPA is out of service for one of the following reasons:
Note The following reasons are not applicable to every SPA and can be platform-specific.
• Analyze failed—Failed to create a SPA data structure, most likely due to a memory allocation problem.
• Authentication failed—SPA has failed hardware validation.
• Data structure create error—Failed to create a SPA data structure, most likely due to a memory allocation problem.
• Event corrupt—A SPA online insertion and removal (OIR) event has been corrupted. This could be caused by a corrupted message between the SIP and the route processor (RP) or some other software or hardware problem.
• Event sequence error—A SPA OIR event was received out of sequence. This could be caused by a corrupted message between the SIP and the route processor (RP) or some other software or hardware problem.
• Fail code not set—Failure code could not be read from a SPA OIR event message. This could be caused by a corrupted message between the SIP and the RP or some other software or hardware problem.
• Failed too many times—SPA is disabled because it has failed more than the allowable limit on the platform.
• FPD upgrade failed—A field-programmable device, such as the Field-Programmable Gate Array (FPGA), failed to automatically upgrade.
• H/W signal deasserted—The SPA_OK or PWR_OK hardware signal indicating that the SPA is accessible are no longer asserted.
• Heartbeat failed—Occurs when intelligent SPAs encounter heartbeat failures.
• Incompatible FPD—An FPGA version mismatch with the Cisco IOS software has been detected for the SPA.
|
out of service (reason)—CONTINUED
|
• Init timeout—Time limit has been reached during initialization of a SPA.
• Read SPA type failed—A read from the hardware for the SPA type failed.
• Reload request—SPA reload is in progress from the hw-module subslot reload command.
• SPA h/w error—The SPA software driver has detected a hardware error.
• SPA ready timeout—A timeout ocurred on the RP while waiting for the SPA to become operational.
• SPA type mismatch—Occurs when you have pre-configured a SPA of one type, but have inserted a SPA of a different type.
Note This reason code only applies to those platforms that support pre-configuration. This is not applicable to a Cisco 12000 Series Router.
• SPA unrecognized—SPA is not supported by the Cisco IOS software release.
• Start failed—Failed to start interfaces on SPA.
• Unexpected inserted event—The SPA OIR software has received a SPA insertion event when the OIR software considered the SPA already present.
• Wait h/w ok timeout—A timeout occurred while waiting for the SPA_OK and PWR_OK hardware signals to be asserted.
• Wait start timeout—A timeout occurred on the SIP while waiting for permission from the RP to bring up the SPA.
|
stopped
|
SPA has been gracefully deactivated using the hw-module subslot stop privileged EXEC command on the Cisco 7304 router.
|
The following example shows the operational status of all of the SPAs installed in a router where all SPAs are running successfully:
Router# show hw-module subslot all oir
Module Model Operational Status
------------- -------------------- ------------------------
subslot 1/1 SPA-2XOC3-ATM ok
subslot 4/0 SPA-2XT3/E3 ok
subslot 4/1 SPA-4XOC3-POS ok
subslot 4/2 SPA-8XCHT1/E1 ok
The following example shows sample output when using the optional internal keyword:
Router# show hw-module subslot 4/0 oir internal
WARNING: This command is not intended for production use
and should only be used under the supervision of
Cisco Systems technical support personnel.
sm(spa_oir_tsm subslot 4/0 TSM), running yes, state ready
Admin Status: admin enabled, Operational Status: ok(1)
Last reset Reason: manual
configured_spa_type 0x483
soft remove fail code 0x0(none)
last_fail_code 0x110E(SPA unrecognized)
timed_fail_count 0, failed_spa_type 0x483
associated_fail_code 0x110E(SPA unrecognized)
sequence numbers: next from tsm 4, last to tsm 2
spa type 0x483, active spa type 0x483
subslot flags 0x0, plugin flags 0x0
wait_psm_ready_timeout 360000 ms, init_timeout 240000 ms
short_recovery_delay 5000 ms, long_recovery_delay 120000 ms
ok_up_time 1200000 ms, bad_fail_count 10
fail_time_period 600000 ms, max_fail_count 5
does not support pre-configuration
SPA OIR state machine audit statistics
In-sync poll-count qry-fail resp-fail restarts fail-count
subslot 4/0 yes 1 0 0 0 0
Related Commands
Command
|
Description
|
hw-module subslot reload
|
Restarts a SPA and its interfaces.
|
hw-module subslot shutdown
|
Shuts down a SPA with or without power.
|
show interface sdcc
To display configuration information and statistics for a sections data communications channel (SDCC) interface, use the show interface sdcc command in privileged EXEC mode. The command does not have a no form.
show interface sdcc slot/subslot/port
Syntax Description
slot
|
Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
/port
|
(Optional) Port or interface number.
Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address on a SPA" topics in the platform-specific SPA software configuration guide.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(11)BC3
|
This command was introduced.
|
12.2(25)S3
|
This command was integrated into Cisco IOS Release 12.2(25)S3 to support POS SPAs on the Cisco 7304 router.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support POS SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S to support POS SPAs on the Cisco 12000 series routers.
|
Examples
Cisco 7600 Series Router Example
The following command displays configuration information and statistics for SDCC interface 7/0/0:
Router# show interface sdcc 7/0/0
SDCC7/0/0 is up, line protocol is up
Internet address is 10.11.11.10/8
MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set
Last input 00:00:38, output 00:00:38, output hang never
Last clearing of "show interface" counters 00:00:48
Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0
Output queue:0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5 packets input, 520 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5 packets output, 520 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco 12000 Series Router Example
The following is sample output from the show interface sdcc command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):
Router# show interface sdcc 1/1/0
SDCC1/1/0 is administratively down, line protocol is down
MTU 1500 bytes, BW 192 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, crc 32, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters 00:01:55
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 19-9 describes the significant fields shown in these displays.
Table 19-9 show interface sdcc Field Descriptions
Field
|
Description
|
SDCCx/y/z is up, line protocol is up
|
Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.
|
Hardware is. . .
|
Hardware type:
• SDCC— Section Data Communications Channel
|
Internet address is
|
Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
crc
|
Cyclic redundancy check size (16 or 32 bits).
|
Loopback
|
Indicates whether loopback is set.
|
Keepalive
|
Indicates whether keepalives are set.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
|
Output queue, drops input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
|
5 minute input rate 5 minute output rate
|
Average number of bits and packets received or transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes (input)
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts 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 minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
throttles
|
Not supported for POS interfaces.
|
parity
|
Report of the parity errors on the interface.
|
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 might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
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 than 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.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes (output)
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Not supported for POS interfaces.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an 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 unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
|
output buffer failures
|
Not supported for POS interfaces.
|
output buffers swapped out
|
Not supported for POS interfaces.
|
carrier transitions
|
Number of times the carrier detect signal of the interface has changed state.
|
show interfaces gigabitethernet
To display information about the Gigabit Ethernet interfaces, use the show interfaces gigabitethernet command in privileged EXEC configuration mode.
show interfaces gigabitethernet slot/subslot/port
Syntax Description
slot
|
Number of the slot where the jacket card that contains the SPA is installed.
|
subslot
|
Number of the secondary slot on the jacket card where the SPA that you want to select is installed. For double-height SPAs, the subslot is 0.
|
port
|
Number of the interface that you want to select.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1 CC
|
This command was introduced.
|
12.1(3a)E
|
Support for the Cisco 7200-I/O-GE+E controller was introduced.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(20)S2
|
This command was integrated into Cisco IOS Release 12.2(20)S2 and introduced a new address format and output for interfaces on the 2-Port 10/100/1000 Gigabit Ethernet SPA on the Cisco 7304 router.
|
12.0(31)S
|
This command was introduced for the Gigabit Ethernet SPAs on the Cisco 12000 series routers. Since SPAs need to be specified using the subslot option, the subslot option was introduced.
|
Examples
The following is sample output from the show interfaces gigabitethernet command for the first interface (port 0) in a 2-Port 10/100/1000 Gigabit Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show interfaces gigabitethernet 4/0/0
GigabitEthernet4/0/0 is up, line protocol is down
Hardware is SPA-2GE-7304, address is 00b0.64ff.5a80 (bia 00b0.64ff.5a80)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Half-duplex, 1000Mb/s, link type is auto, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:09, 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/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
109 packets output, 6540 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Note
There are variations in the output for the show interfaces commands on Cisco Systems routers depending on the platform, type of interface, and also other features that you might have configured, such as Quality of Service (QoS). Therefore, some additional output fields might appear in your show command output. For more information about these fields, see the show interfaces command description in the Cisco IOS Interface Command Reference, Release 12.2.
Table 19-10 describes the fields shown in the display.
Table 19-10 show interfaces gigabitethernet Field Descriptions—Gigabit Ethernet SPA
Field
|
Description
|
GigabitEthernet...is up ...is administratively down
|
Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.
|
line protocol is
|
Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.
|
Hardware
|
Hardware type (for example, SPA-2GE-7304) and MAC address.
|
Description
|
Alphanumeric string identifying the interface. This only appears if the description interface configuration command has been configured on the interface.
|
Internet address
|
Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface. The default is 1500 bytes for the 2-Port 10/100/1000 Gigabit Ethernet SPA.
|
BW
|
Bandwidth of the interface in kilobits per second.
|
DLY
|
Delay of the interface in microseconds.
|
reliability
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
txload, rxload
|
Load on the interface (in the transmit "tx" and receive "rx" directions) as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to the interface.
|
loopback
|
Indicates whether or not loopback is set.
|
Keepalive
|
Indicates whether or not keepalives are set, and the time interval.
|
Half-duplex, Full-duplex
|
Indicates the duplex mode for the interface.
|
1000Mb/s, 100Mb/s, 10Mb/s
|
Speed of the interface in megabits per second.
|
link type
|
Specifies whether or not autonegotiation is being used on the link.
|
media type
|
Interface port media type: RJ45, SX, LX, or ZX.
|
100BaseTX/FX
|
Media protocol standard.
|
ARP type:
|
Type of Address Resolution Protocol (ARP) assigned and the timeout period.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed.
This field is not updated by fast-switched traffic.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is displayed. If that field overflows, asterisks are printed.
Note This field does not apply to SPA interfaces.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
A series of asterisks (***) indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Input queue (size/max/drops/flushes)
|
Packet statistics on the input queue reported as:
• Size—Number of packets in the input queue.
• Max—Maximum size of the queue.
• Drops—Number of packets dropped because of a full input queue.
• Flushes—Number of packets dropped as part of selective packet discard (SPD). SPD implements a selective packet drop policy on the router's IP process queue. Therefore, it only applies to process-switched traffic.
|
Total output drops
|
Total number of packets dropped because of a full output queue.
|
Queueing strategy
|
Type of Layer 3 queueing active on this interface. The default is first-in, first-out (FIFO).
|
Output queue (size/max)
|
Number of packets in the output queue (size), and the maximum size of the queue (max).
|
5 minute input rate, 5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
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.
|
Received...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 minimum packet size of the medium. For instance, any Ethernet packet that is smaller than 64 bytes is considered a runt.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is larger than 1536 bytes is considered a giant.
Note For the 2-Port 10/100/1000 Gigabit Ethernet SPA, the default is that a giant is any packet greater than 1536 bytes. However, if you modify the maximum transmission unit (MTU) for the interface, this counter increments when you exceed the specified MTU for the interface.
|
throttles
|
Number of times the receiver on the port was disabled, possibly because of buffer or processor overload.
|
input errors
|
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
|
CRC
|
Cyclic redundancy check 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 itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
|
overrun
|
Number of times the 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 than the system buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
watchdog
|
Number of times the watchdog receive timer expired. Expiration happens when receiving a packet with a length greater than 2048 bytes.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented for informational purposes only; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of 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 once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. Interface resets can occur when an interface is looped back or shut down.
|
babbles
|
Transmit jabber timer expired.
|
late collision
|
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble.
|
deferred
|
Number of times that the interface had to defer while ready to transmit a frame because the carrier was asserted.
|
lost carrier
|
Number of times the carrier was lost during transmission.
|
no carrier
|
Number of times the carrier was not present during the transmission.
Note This field does not apply to SPA interfaces.
|
output buffer failures, output buffers swapped out
|
These counters are not used by the 2-Port 10/100/1000 Gigabit Ethernet SPA on the Cisco 7304 router.
|
Related Commands
Command
|
Description
|
show interfaces1
|
Displays statistics for the interfaces configured on a router or access server.
|
show controllers gigabitethernet
|
Displays Gigabit Ethernet interface information, transmission statistics and errors, and applicable MAC destination address and VLAN filtering tables.
|
show interfaces pos
To display configuration information and statistics for a Packet over SONET (POS) interface, use the show interfaces pos command in user EXEC or privileged EXEC configuration mode.
Cisco 7000 and Cisco 7500 Series with VIPs
show interfaces pos [slot/port-adapter/port]
POS Shared Port Adapters
show interfaces pos slot/subslot/port[/sub_int]
Syntax Description
slot
|
Chassis slot number. Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/port-adapter
|
Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
/subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed. Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
/port
|
Port or interface number. Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding "Specifying the Interface Address" topics in the platform-specific SPA software configuration guide.
|
/sub_int
|
(Optional) Subinterface number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
The show interface posi command was introduced.
|
11.3
|
The name of the command was modified from show interface posi to show interfaces pos, and the sample output was updated.
|
12.2(25)S3
|
This command was integrated into Cisco IOS Release 12.2(25)S3 to support SPAs on the Cisco 7304 router. The command was modified to support a new addressing format for SPAs.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.
|
Examples
Cisco 7513 Example
The following is sample output from the show interfaces pos command on a Cisco 7513 router with one Packet OC-3 Interface Processor (POSIP):
Router# show interfaces pos 2/0/0
POS2/0/0 is up, line protocol is up
Hardware is cyBus Packet over Sonet
Description: PRI-T1 net to zippy (4K) to Pac-Bell
Internet address is 10.1.1.1/27
MTU 4470 bytes, BW 1000 Kbit, DLY 40000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (3 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:23:09
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
1046 packets input, 54437 bytes, 0 no buffer
Received 485 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4013 packets output, 1357412 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco 7600 Series Router POS Shared Port Adapter Example
The following is sample output from the show interfaces pos command on a Cisco 7600 series router for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot 4):
Router# show interfaces pos 4/3/0
POS4/3/0 is up, line protocol is up (APS working - active)
Hardware is Packet over SONET
Internet address is 10.0.0.1/8
MTU 4470 bytes, BW 622000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation HDLC, crc 16, loopback not set
Last input 00:00:34, output 04:09:06, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Available Bandwidth 622000 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
782 packets input, 226563 bytes, 0 no buffer
Received 0 broadcasts, 1 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
271 packets output, 28140 bytes, 0 underruns
0 output errors, 0 applique, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
Cisco 12000 Series Router POS Shared Port Adapter Example
The following is sample output from the show interfaces pos command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):
Router# show interfaces pos 1/1/0
POS1/1/0 is up, line protocol is up
Hardware is Packet over SONET
Internet address is 10.41.41.2/24
MTU 4470 bytes, BW 9952000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation HDLC, crc 32, loopback not set
Last input 00:00:59, output 00:00:11, output hang never
Last clearing of "show interface" counters 00:00:14
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Available Bandwidth 9582482 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
1 packets output, 314 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 19-9 describes the significant fields shown in these displays.
Table 19-11 show interfaces pos Field Descriptions
Field
|
Description
|
POSx/y/z is up, line protocol is up
|
Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.
|
Hardware is. . .
|
Hardware type:
• For POSIP— cyBus Packet over Sonet
• For POS SPAs—Packet over SONET
|
Internet address is
|
Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
Loopback
|
Indicates whether loopbacks are set.
|
Keepalive
|
Indicates whether keepalives are set.
|
Scramble
|
Indicates whether or not SONET payload scrambling is enabled. SONET scrambling is disabled by default. For the POS SPAs on the Cisco 12000 series routers, scrambling is enabled by default.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
|
Output queue, drops input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
|
5 minute input rate 5 minute output rate
|
Average number of bits and packets received or transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes (input)
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts 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 minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
throttles
|
Not supported for POS interfaces.
|
parity
|
Report of the parity errors on the interface.
|
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 might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
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 than 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.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes (output)
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
applique
|
Indicates an unrecoverable error has occurred on the POSIP applique. The system then invokes an interface reset.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an 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 unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
|
output buffer failures
|
Not supported for POS interfaces.
|
output buffers swapped out
|
Not supported for POS interfaces.
|
carrier transitions
|
Number of times the carrier detect signal of the interface has changed state.
|
Related Commands
Command
|
Description
|
interface
|
Configures an interface type and enters interface configuration mode.
|
show interfaces serial
To display information about a serial interface, use the show interfaces serial command in privileged EXEC mode. When using Frame Relay encapsulation, use the show interfaces serial command in user EXEC or privileged EXEC mode to display information about the multicast data-link connection identifier (DLCI), the DLCIs used on the interface, and the DLCI used for the Local Management Interface (LMI).
Cisco 4000 Series
show interfaces serial [number[:channel-group]] [accounting]
Cisco 7000 and Cisco 7500 Series with the RSP7000, RSP7000CI, or Ports on VIPs
show interfaces serial [slot/port-adapter/port]
Cisco 7500 Series
show interfaces serial [slot/port[:channel-group]] [accounting]
Cisco 7500 Series with a CT3IP
show interfaces serial [slot/port-adapter/port][:t1-channel] [accounting | crb]
Cisco AS5350 and Cisco AS5400 Universal Gateways
show interfaces serial slot/port
Cisco AS5800 Access Servers
show interfaces serial dial-shelf/slot/t3-port:t1-num:chan-group
T3/E3 Shared Port Adapters and 2-Port and 4-Port Channelized T3 SPA in Unchannelized Mode
show interfaces serial [slot/subslot/port]
Channelized T3 Shared Port Adapters
show interfaces serial [slot/subslot/port/t1-num:channel-group]
Syntax Description
number
|
(Optional) Number of the port being displayed.
|
:channel-group
|
(Optional) On the Cisco 4000 series with a Network Management Processor (NPM) or the Cisco 7500 series routers with a MultiChannel Interface Processor (MIP), specifies the T1 channel-group number in the range of 0 to 23 defined with the channel-group controller configuration command.
For channelized T3 SPAs, number 0-23 of the DS0 link on the T1 channel.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Chassis slot number.
Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
port
|
(Optional) Number of the port being displayed. Refer to the appropriate hardware manual for slot and port information.
|
port-adapter
|
(Optional) Number of the port adapter being displayed. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
subslot
|
Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.
Refer to the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on a SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
:t1-channel
|
(Optional) T1 channel number. For the CT3IP, the T1 channel is a number between 1 and 28.
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This scheme ensures consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
|
crb
|
(Optional) Displays interface routing and bridging information.
|
dial-shelf
|
Dial-shelf chassis in the Cisco AS5800 access server that contains the CT3 interface card.
|
slot
|
Location of the CT3 interface card in the dial shelf chassis.
|
t3-port
|
T3 port number. The only valid value is 0.
|
:t1-num
|
T1 time slot in the T3 line. The value can be from 1 to 28.
|
:chan-group
|
Channel group identifier.
|
Defaults
No default behavior or values
Command Modes
User EXEC when Frame Relay encapsulation is used
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced on the Cisco 4000 series routers.
|
11.0
|
This command was implemented on the Cisco 7000 series routers.
|
11.1CA
|
This command was modified to include sample output for the PA-2JT2, PA-E3, and PA-T3 serial port adapters.
|
11.3
|
This command was modified to include the CT3IP.
|
12.0(3)T
|
This command was implemented on the Cisco AS5800 access servers. This command was modified to include support for flow-based WRED.
|
12.0(4)T
|
This command was modified to include enhanced display information for dialer bound interfaces.
|
12.0(7)T
|
This command was modified to include dialer as an interface type, and to reflect the default behavior.
|
12.2(11)T
|
This command was implemented on the Cisco AS5350 and Cisco AS5400.
|
12.2(13)T
|
This command was modified to display information about Frame Relay interface queueing and fragmentation.
|
12.2S
|
This command was integrated into Cisco IOS Release 12.2S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.
|
12.0(31)S
|
This command was integrated into Cisco IOS Release 12.0(31)S.
|
Usage Guidelines
Frame Relay
Use this command to determine the status of the Frame Relay link. This display also indicates Layer 2 status if switched virtual circuits (SVCs) are configured.
Channel Groups as Virtual Serial Interfaces
To find out about channel groups configured as virtual serial interfaces, to verify that the router has High-Level Data Link Control (HDLC) encapsulation on the interface, and to verify that the interface sees the loopback, use the show interfaces serial command in privileged EXEC mode.
Examples
Example of Synchronous Serial Interface
The following is sample output from the show interfaces serial command for a synchronous serial interface:
Router# show interfaces serial
Serial 0 is up, line protocol is up
Internet address is 192.168.10.203, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:07, output 0:00:00, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
16263 packets input, 1347238 bytes, 0 no buffer
Received 13983 broadcasts, 0 runts, 0 giants
2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
22146 packets output, 2383680 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
Table 19-12 describes significant fields shown in the display.
Table 19-12 show interfaces serial Field Descriptions—Synchronous Serial Interface
Field
|
Description
|
Serial ... is {up | down} ... is administratively down
|
Indicates whether the interface hardware is currently active (whether carrier detect is present), is currently inactive, or has been taken down by an administrator.
|
line protocol is {up | down}
|
Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful) or whether the line has been taken down by an administrator.
|
Hardware is
|
Specifies the hardware type.
|
Internet address is
|
Specifies the Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Indicates the value of the bandwidth parameter that has been configured for the interface (in kbps). If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 kbps for T1 and 56 kbps for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether or not loopback is set.
|
keepalive
|
Indicates whether or not keepalives are set.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Output queue, drops input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate 5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
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 networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received... 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 minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
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 might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. 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. On a serial line, this is usually the result of noise or other transmission problems.
|
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. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
|
carrier transitions
|
Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes output
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface from being examined. Note that this might not balance with the sum of the enumerated output errors because some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. Some collisions are normal. However, if your collision rate climbs to around 4 or 5 percent, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds' time. 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.
|
restarts
|
Number of times the controller was restarted because of errors.
|
alarm indications, remote alarms, rx LOF, rx LOS
|
Number of CSU/DSU alarms and number of occurrences of receive loss of frame and receive loss of signal.
|
BER inactive, NELR inactive, FELR inactive
|
Status of G.703-E1 counters for bit -error rate (BER) alarm, near-end loop remote (NELR), and far-end loop remote (FELR). Note that you cannot set the NELR or FELR.
|
Example of PA-2JT2 Serial Interface
The following is sample output from the show interfaces serial command for a PA-2JT2 serial interface:
Router# show interfaces serial 3/0/0
Serial3/0/0 is up, line protocol is up
Internet address is 10.0.0.1/8
MTU 1500 bytes, BW 6312 Kbit, DLY 20000 usec, rely 255/255, load 26/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 00:04:31, output 00:04:31, output hang never
Last clearing of "show interface" counters 00:06:07
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 162000 bits/sec, 8 packets/sec
5 minute output rate 162000 bits/sec, 8 packets/sec
20005 packets input, 20080520 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
20005 packets output, 20080520 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 cv errors, 0 crc5 errors, 0 frame errors
rxLOS inactive, rxLOF inactive, rxPAIS inactive
rxAIS inactive, rxRAI inactive, rxHBER inactive
Table 19-13 describes significant fields shown in the display that are different from the fields described in Table 19-12.
Table 19-13 show interfaces serial Field Descriptions—PA-2JT2 Serial Interface
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
carrier transitions
|
Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.
|
cv errors
|
B8ZS/B6ZS (zero suppression) coding violation counter.
|
crc5 errors
|
CRC-5 error counter.
|
frame errors
|
Framing error counter.
|
rxLOS
|
Receive loss of signal alarm. Values are active or inactive.
|
rxLOF
|
Receive loss of frame alarm. Values are active or inactive.
|
rxPAIS
|
Receive loss of payload alarm indication signal (AIS). Values are active or inactive.
|
rxAIS
|
Receive loss of physical AIS. Values are active or inactive.
|
rxRAI
|
Receive remote AIS. Values are active or inactive.
|
rxHBER
|
Receive high bit-error rate alarm. Values are active or inactive.
|
Example of PA-E3 Serial Port Adapter
The following is sample output from the show interfaces serial command for a PA-E3 serial port adapter installed in chassis slot 2:
Router# show interfaces serial 2/0
Serial2/0 is up, line protocol is up
Internet address is 172.17.1.1/24
MTU 4470 bytes, BW 34010 Kbit, DLY 200 usec, rely 128/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 1w0d, output 00:00:48, output hang never
Last clearing of "show interface" counters 1w0d
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
20 packets input, 2080 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
11472 packets output, 3824748 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
rxLOS inactive, rxLOF inactive, rxAIS inactive
txAIS inactive, rxRAI inactive, txRAI inactive
Table 19-14 describes significant fields shown in the display that are different from the fields described in Table 19-12.
Table 19-14 show interfaces serial Field Descriptions—PA-E3
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
parity
|
Number of the parity errors on the interface.
|
applique
|
Indicates that an unrecoverable error has occurred on the E3 applique. The router then invokes an interface reset.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
rxLOS, rxLOF, rxAIS
|
Receive loss of signal, loss of frame, and alarm indication signal status. Values are inactive or active.
|
txAIS, rxRAI, txRAI
|
Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active. When the router receives an LOS, LOF, or AIS, the txRAI is active. When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.
|
Example of 1-Port PA-T3 Serial Port Adapter Installed in a VIP2
The following is sample output from the show interfaces serial command for a 1-port PA-T3 serial port adapter installed in a VIP2 in chassis slot 1, in port adapter slot 0:
Router# show interfaces serial 1/0/0
Serial1/0/0 is up, line protocol is up
Hardware is cyBus PODS3 Serial
Internet address is 172.18.1.1/24
MTU 4470 bytes, BW 44736 Kbit, DLY 200 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 00:00:05, output 00:00:02, output hang never
Last clearing of "show interface" counters 5d02h
Output queue 0/40, 0 drops; input queue 0/75, 27269 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
79039 packets input, 14195344 bytes, 0 no buffer
Received 84506 broadcasts, 0 runts, 0 giants
9574 input errors, 6714 CRC, 0 frame, 1 overrun, 0 ignored, 2859 abort
62472 packets output, 13751644 bytes, 0 underruns
0 output errors, 0 applique, 10 interface resets
0 output buffer failures, 0 output buffers swapped out
rxLOS inactive, rxLOF inactive, rxAIS inactive
txAIS inactive, rxRAI inactive, txRAI inactive
Table 19-15 describes significant fields shown in the display that are different from the fields described in Table 19-12.
Table 19-15 show interfaces serial Field Descriptions—PA-T3
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
parity
|
Number of the parity errors on the interface.
|
applique
|
Indicates that an unrecoverable error has occurred on the T3 applique. The router then invokes an interface reset.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
rxLOS, rxLOF, rxAIS
|
Receive loss of signal, loss of frame, and alarm indication signal status. Values are inactive or active.
|
txAIS, rxRAI, txRAI
|
Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active. When the router receives an LOS, LOF, or AIS, the txRAI is active. When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.
|
Example of CT3IP Serial Interface
The following is sample output from the show interfaces serial command for the CT3IP serial interface:
Router# show interfaces serial 3/0/0:25
Serial3/0/0:25 is up, line protocol is up
Internet address is 10.25.25.2/24
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 12/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 00:19:01, output 00:11:49, output hang never
Last clearing of "show interface" counters 00:19:39
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 69000 bits/sec, 90 packets/sec
5 minute output rate 71000 bits/sec, 90 packets/sec
762350 packets input, 79284400 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
150 input errors, 0 CRC, 0 frame, 150 overrun, 0 ignored, 0 abort
763213 packets output, 80900472 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions no alarm present
Timeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 5
Table 19-16 describes significant fields relevant to the CT3IP shown in the display that are different from the fields described in Table 19-12.
Table 19-16 show interfaces serial Field Descriptions—CT3IP
Field
|
Description
|
Timeslot(s) Used
|
Number of time slots assigned to the T1 channel.
|
Transmitter delay
|
Number of idle flags inserted between each HDLC frame.
|
transmit queue length
|
Number of packets allowed in the transmit queue.
|
non-inverted data
|
Indicates whether or not the interface is configured for inverted data.
|
Example of an HDLC Synchronous Serial Interface on a Cisco 7500 Series Router
The following is sample output from the show interfaces serial command for an HDLC synchronous serial interface on a Cisco 7500 series router:
Router# show interfaces serial 1/0
Serial1/0 is up, line protocol is up
Internet address is 172.19.190.203, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:07, output 0:00:00, output hang never
Last clearing of "show interface" counters 2w4d
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
16263 packets input, 1347238 bytes, 0 no buffer
Received 13983 broadcasts, 0 runts, 0 giants
2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
22146 packets output, 2383680 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
Table 19-12 describes significant fields shown in the display.
Example of HDLC Encapsulation
The following example displays High-Level Data Link Control (HDLC) encapsulation on serial interface 0:
Router# show interfaces serial 0
Serial0 is up, line protocol is up (looped)
Internet address is 10.1.1.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback set, keepalive set (10 sec)
Table 19-12 describes significant fields shown in the display.
Example of a G.703 Interface with Framing
The following is sample output from the show interfaces serial command for a G.703 interface on which framing is enabled:
Router# show interfaces serial 2/3
Serial2/3 is up, line protocol is up
Internet address is 10.4.4.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 0:00:21, output 0:00:21, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
53 packets input, 7810 bytes, 0 no buffer
Received 53 broadcasts, 0 runts, 0 giants
2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
56 packets output, 8218 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
2 alarm indications, 333 remote alarms, 332 rx LOF, 0 rx LOS
RTS up, CTS up, DTR up, DCD up, DSR up
BER inactive, NELR inactive, FELR inactive
Table 19-12 describes significant fields shown in the display.
Example with Frame Relay Encapsulation
When using Frame Relay encapsulation, use the show interfaces serial command to display information on the multicast data-link connection identifier (DLCI), the DLCI of the interface, and the DLCI used for the Local Management Interface (LMI).
The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and frame-relay local-dlci configuration commands. The status information is taken from the LMI, when active.
The following is sample output from the show interfaces serial command when Frame Relay encapsulation and LMI are enabled:
Router# show interfaces serial
Serial 2 is up, line protocol is up
Hardware type is MCI Serial
Internet address is 172.20.122.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)
multicast DLCI 1022, status defined, active
source DLCI 20, status defined, active
LMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2
Last input 7:21:29, output 0:00:37, output hang never
Output queue 0/100, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
47 packets input, 2656 bytes, 0 no buffer
Received 5 broadcasts, 0 runts, 0 giants
5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 57 abort
518 packets output, 391205 bytes
0 output errors, 0 collisions, 0 interface resets, 0 restarts
In this display, the multicast DLCI has been changed to 1022 using the frame-relay multicast-dlci interface configuration command.
The display shows the statistics for the LMI as the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). Refer to the Frame Relay Interface specification for additional explanations of this output.
Example with Frame Relay Queueing and Fragmentation at the Interface
The following is sample output from the show interfaces serial command when low-latency queueing and FRF.12 end-to-end fragmentation are configured on a Frame Relay interface:
Router# show interfaces serial 3/2
Serial3/2 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, crc 16, loopback not set
LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 1023 LMI type is CISCO frame relay DTE
Fragmentation type: end-to-end, size 80, PQ interleaves 0
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
Last input 2d15h, output 2d15h, output hang never
Last clearing of "show interface" counters 00:01:31
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1094 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up
Table 19-17 describes significant fields shown in the display that are different from the fields described in Table 19-12.
Table 19-17 show interfaces serial Field Descriptions—Frame Relay Interface Queueing and Fragmentation
Field
|
Description
|
txload
|
Interface load in the transmit direction.
|
rxload
|
Interface load in the receive direction.
|
crc
|
Number of Layer 1 checksum errors during reception.
|
LMI enq sent
|
Number of Frame Relay status inquiry messages sent.
|
LMI stat recvd
|
Number of Frame Relay status request messages received.
|
LMI upd recvd
|
Number of single PVC asynchronous status messages received.
|
DTE LMI up
|
LMI peers are synchronized.
|
LMI enq recvd
|
Number of Frame Relay status inquiry messages received.
|
LMI stat sent
|
Number of Frame Relay status request messages sent.
|
LMI upd sent
|
Number of single PVC asynchronous status messages sent.
|
Fragmentation type
|
Type of fragmentation: end-to-end, Cisco, or VoFR
|
size
|
Fragmentation size.
|
PQ interleaves
|
Number of priority queue frames that have interleaved data fragments.
|
Broadcast queue
|
Number on queue/queue depth.
|
broadcasts sent/dropped
|
Number of broadcasts sent and dropped.
|
interface broadcasts
|
Number of broadcasts sent on interface.
|
Input queue
|
size—Current size of the input queue. max—Maximum size of the queue. drops—Number of messages discarded. flushes—Number of times that data on queue has been discarded.
|
Queueing strategy
|
Type of queueing configured on the interface.
|
Output queue
|
size—Current size of the output queue. max total—Maximum number of frames that can be queued. threshold—Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped. drops—Number of dropped messages.
|
Conversations
|
active—Number of currently active conversations. max active—Maximum number of conversations that have ever occurred at one time. max total—Maximum number of active conversations allowed.
|
throttles
|
Number of times the receiver on the port was disabled, possibly because of processor or buffer overload.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
Example with ANSI LMI
For a serial interface with the ANSI Local Management Interface (LMI) enabled, use the show interfaces serial command to determine the LMI type implemented. The following is sample output from the show interfaces serial command for a serial interface with the ANSI LMI enabled:
Router# show interfaces serial
Serial 1 is up, line protocol is up
Internet address is 172.18.121.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY, loopback not set, keepalive set
LMI DLCI 0, LMI sent 10, LMI stat recvd 10
Last input 0:00:00, output 0:00:00, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 1 packets/sec
Five minute output rate 1000 bits/sec, 1 packets/sec
261 packets input, 13212 bytes, 0 no buffer
Received 33 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
238 packets output, 14751 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Notice that the show interfaces serial output for a serial interface with ANSI LMI shown in this display is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. Table 19-18 describes the few differences that exist.
Table 19-18 show interfaces serial Field Descriptions—ANSI LMI
Field
|
Description
|
LMI DLCI
|
Identifies the DLCI used by the LMI for this interface. The default is 1023.
|
LMI sent
|
Number of LMI packets that the router sent.
|
LMI type is ANSI Annex D
|
Indicates that the interface is configured for the ANSI-adopted Frame Relay specification T1.617 Annex D.
|
Example with LAPB Encapsulation
Use the show interfaces serial command to display operation statistics for an interface that uses Link Access Procedure, Balanced (LAPB) encapsulation. The following is partial sample output from the show interfaces serial command for a serial interface that uses LAPB encapsulation:
Router# show interfaces serial 1
LAPB state is SABMSENT, T1 3000, N1 12056, N2 20, k7,Protocol ip
VS 0, VR 0, RCNT 0, Remote VR 0, Retransmissions 2
IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABMs 3/0 FRMRs 0/0 DISCs 0/0
Table 19-19 shows the fields relevant to all LAPB connections.
Table 19-19 show interfaces serial Field Descriptions—LAPB
Field
|
Description
|
LAPB state is
|
State of the LAPB protocol.
|
T1 3000, N1 12056, ...
|
Current parameter settings.
|
Protocol
|
Protocol encapsulated on a LAPB link; this field is not present on interfaces configured for multiprotocol LAPB or X.25 encapsulations.
|
VS
|
Modulo 8 frame number of the next outgoing information frame.
|
VR
|
Modulo 8 frame number of the next information frame expected to be received.
|
RCNT
|
Number of received information frames that have not yet been acknowledged.
|
Remote VR
|
Number of the next information frame that the remote device expects to receive.
|
Retransmissions
|
Count of current retransmissions because of expiration of T1.
|
Window is closed
|
No more frames can be transmitted until some outstanding frames have been acknowledged. This message should be displayed only temporarily.
|
IFRAMEs
|
Count of information frames in the form of sent/received.
|
RNRs
|
Count of Receiver Not Ready frames in the form of sent/received.
|
REJs
|
Count of Reject frames in the form of sent/received.
|
SABMs
|
Count of Set Asynchronous Balanced Mode commands in the form of sent/received.
|
FRMRs
|
Count of Frame Reject frames in the form of sent/received.
|
DISCs
|
Count of Disconnect commands in the form of sent/received.
|
Example with PPP Encapsulation
The output for an interface configured for synchronous PPP encapsulation differs from the standard show interfaces serial output. An interface configured for PPP might include the following information:
Router# show interfaces serial 1
ncp ipcp state = OPEN ncp osicp state = NOT NEGOTIATED
ncp ipxcp state = NOT NEGOTIATED ncp deccp state = NOT NEGOTIATED
ncp bridgecp state = NOT NEGOTIATED ncp atalkcp state = NOT NEGOTIATED
Table 19-20 show the fields relevant to PPP connections.
Table 19-20 show interfaces serial Field Descriptions—PPP Encapsulation
Field
|
Description
|
lcp state
|
Link Control Protocol.
|
ncp ipcp state
|
Network Control Protocol Internet Protocol Control Protocol.
|
ncp osicp state
|
Network Control Protocol OSI (CLNS) Control Protocol.
|
ncp ipxcp state
|
Network Control Protocol IPX (Novell) Control Protocol.
|
ncp deccp state
|
Network Control Protocol DECnet Control Protocol.
|
ncp bridgecp state
|
Network Control Protocol Bridging Control Protocol.
|
ncp atalkcp state
|
Network Control Protocol AppleTalk Control Protocol.
|
Example with SDLC Connections
Use the show interfaces serial command to display the Synchronous Data Link Control (SDLC) information for a given SDLC interface. The following is sample output from the show interfaces serial command for an SDLC primary interface that supports the SDLLC function:
Router# show interfaces serial
Serial 0 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC-PRIMARY, loopback not set
Timers (msec): poll pause 100 fair poll 500. Poll limit 1
[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
largest token ring frame 2052]
SDLC addr C1 state is CONNECT
VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
Poll: clear, Poll count: 0, chain: p: C1 n: C1
SDLLC [largest SDLC frame: 265, XID: disabled]
Last input 00:00:02, output 00:00:01, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 517 bits/sec, 30 packets/sec
Five minute output rate 672 bits/sec, 20 packets/sec
357 packets input, 28382 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
926 packets output, 77274 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Table 19-21 shows the fields relevant to all SDLC connections.
Table 19-21 show interfaces serial Field Descriptions—SDLC Enabled
Fi |