|
|
Use the mdl interface configuration command to configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification for the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers. Use the no form of this command to remove the message.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port || transmit path | Enables transmission of the MDL Path message. |
| transmit idle-signal | Enables transmission of the MDL Idle Signal message. |
| transmit test-signal | Enables transmission of the MDL Test Signal message. |
| string eic string | Specifies the Equipment Identification Code; can be up to 10 characters. |
| string lic string | Specifies the Location Identification Code; can be up to 11 characters. |
| string fic string | Specifies the Frame Identification Code; can be up to 10 characters. |
| string unit string | Specifies the Unit Identification Code; can be up to 6 characters. |
| string pfi string | Specifies the 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 generator string | Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters. |
No MDL message is configured
Interface configuration
This command first appeared in Cisco IOS Release 11.3.
Use the show controllers t3 command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.
The following examples show several of the mdl commands for the CT3IP in slot 9:
controller t3 9/0/0 mdl string eic Router A mdl string lic Test Network mdl string fic Building B mdl string unit ABC
You can use the master index or search online for documentation of related commands.
To specify the physical connection for one of the following configurations, use the media type interface configuration command:
Use the no form of this command to restore the default value.
media-type {aui | 10baset | 100baset | mii}| aui | Selects a 15-pin physical connection. |
| 10baset | Selects an RJ45 10BaseT physical connection. |
| 100baset | Specifies an RJ45 100BaseT physical connection. |
| mii | Specifies a media-independent interface. |
AUI 15-pin physical connection is the default setting on the Cisco 4000 series.
100BaseT physical connection is the default setting on the Cisco 7000 series and 7200 series.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example selects an RJ45 10BaseT physical connection on Ethernet interface 1:
interface ethernet 1 media-type 10baset
The following example specifies a media-independent interface physical connection to Fast Ethernet slot 0, port 1 on the Cisco 7000 or 7200 series:
interface fastethernet 0/1 media-type mii
The following example specifies a media-independent interface physical connection to Fast Ethernet slot 0, port-adapter 1, port 1 on the Cisco 7500 series:
interface fastethernet 0/1/1 media-type mii
Use the mop enabled interface configuration command to enable an interface to support the Maintenance Operation Protocol (MOP). To disable MOP on an interface, use the no form of this command.
mop enabledThis command has no arguments or keywords.
Enabled on Ethernet interfaces and disabled on all other interfaces.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
In the following example, MOP is enabled for serial interface 0:
interface serial 0 mop enabled
You can use the master indexes or search online to find documentation of related commands.
mop retransmit-timer
mop retries
mop sysid
To enable an interface to send out periodic Maintenance Operation Protocol (MOP) system identification messages, use the mop sysid interface configuration command. To disable MOP message support on an interface, use the no form of this command.
mop sysidThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
You can still run MOP without having the background system ID messages sent. This lets you use the MOP remote console, but does not generate messages used by the configurator.
In the following example, serial interface 0 is enabled to send MOP system identification messages:
interface serial 0 mop sysid
You can use the master indexes or search online to find documentation of related commands.
mop device-code
mop enabled
To adjust the maximum packet size or maximum transmission unit (MTU) size, use the mtu interface configuration command. Use the no form of this command to restore the MTU value to its original default value.
mtu bytes| bytes | Desired size in bytes. |
Table 31 lists default MTU values according to media type.
| Media Type | Default MTU |
|---|---|
| Ethernet | 1500 |
| Serial | 1500 |
| Token Ring | 4464 |
| ATM | 4470 |
| FDDI | 4470 |
| HSSI (HSA) | 4470 |
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Each interface has a default maximum packet size or maximum transmission unit (MTU) size. This number generally defaults to the largest size possible for that type interface. On serial interfaces, the MTU size varies, but cannot be set smaller than 64 bytes.
Caution Changing an MTU size on a Cisco 7500 router will result in recarving of buffers and resetting of all interfaces. The following message is displayed:
%RSP-3-Restart:cbus complexThe following example specifies an MTU of 1000 bytes:
interface serial 1 mtu 1000
You can use the master indexes or search online to find documentation of related commands
encapsulation smds
ip mtu
Use the nrzi-encoding interface configuration command to enable nonreturn-to-zero inverted (NRZI) line-coding format. Use the no form of this command to disable this capability.
nrzi-encoding| mark | (Optional) Specifies that NRZI mark encoding is required on the PA-8T and PA-4T+ synchronous serial port adapters on Cisco 7200 and 7500 series routers. If mark is not specified, NRZI space encoding is used. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
This command was modified in Cisco IOS Release 11.3 to include the mark keyword.
In the following example, serial interface 1 is configured for NRZI encoding:
interface serial 1 nrzi-encoding
In the following example, serial interface 3/1/0 is configured for NRZI mark encoding:
interface serial 3/1/0 nrzi-encoding mark
To specify the mode of a slow-speed serial interface on a router as either synchronous or asynchronous, use the physical-layer interface configuration command. To return the interface to the default mode of synchronous, use the no form of this command.
physical-layer {sync | async}| sync | Place the interface in synchronous mode. |
| async | Place the interface in asynchronous mode. |
Synchronous mode
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command applies only to low-speed serial interfaces available on Cisco 2520 through 2523 routers.
If you specify the no physical-layer command, you return the interface to its default mode (synchronous).
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces.
When you enter this command, it does not appear in the output of show running config and show startup config commands, because the command is a physical layer command.
This example changes a low-speed serial interface from synchronous to asynchronous mode:
interface serial 2 physical-layer async
To select SDH STM-1 framing on a Packet OC-3 interface in Cisco 7500 series routers, use the pos framing-sdh interface configuration command. To revert to the default SONET STS-3c framing, use the no form of this command.
pos framing-sdhThis command has no keywords or arguments.
SONET STS-3c framing
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command was modified in Cisco IOS Release 11.3 to change the posi framing-sdh command to pos framing-sdh.
In the following example, the interface is configured for SDH STM-1 framing:
interface pos 3/0 pos framing-sdh no shutdown
You can use the master indexes or search online to find documentation of related commands.
interface pos
pos internal-clock
To set the internal clock as the transmission clock source on a Packet OC-3 interface in Cisco 7500 series routers, use the pos internal-clock interface configuration command. To revert to the default recovered receive clock as the transmission clock source, use the no form of this command.
pos internal-clockThis command has no keywords or arguments.
The recovered receive clock
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command was modified in Cisco IOS Release 11.3 to change the posi internal-clock command to pos internal-clock.
The following command reverts to the default recovered receive clock:
interface pos 3/0 no pos internal-clock
You can use the master indexes or search online to find documentation of related commands.
interface pos
pos framing-sdh
To enable SONET payload scrambling on a POS interface, use the pos scramble-atm interface configuration command. To disable scrambling, use the no form of this command.
pos scramble-atmThis command has no keywords or arguments.
Scrambling is disabled
Interface configuration
This command was added in Cisco IOS Release 11.2 P and 11.1 CA.
SONET payload scrambling applies a self-synchronous scrambler (x^43+1) to the Synchronous Payload Envelope (SPE) of the interface to ensure sufficient bit transition density. Both ends of the connection must use the same scrambling algorithm. When enabling POS scrambling on a VIP2 POSIP on the Cisco 7500 series that has a hardware revision of 1.5 or higher, you can specify CRC 16 only (that is, CRC 32 is currently not supported).
To determine the hardware revision of the POSIP, use the show diag command.
To determine whether scrambling is enabled on the interface, use the show interface pos command or show startup-config command.
The following example enables scrambling on the interface:
Router(config)#interface pos 3/0Router(config-if)#pos scramble-atmRouter(config-if)#no shutdownRouter(config-if)#endRouter#
interface pos
show interface pos
show startup-config
To specify ISDN Primary Rate Interface (PRI) on a channelized E1 or T1 card on the Cisco 7500, use the pri-group controller configuration command. Use the no form of this command to remove the ISDN PRI.
pri-group [timeslots range]| timeslots range | (Optional) Specifies a single range of values from 1 to 23. |
Disabled
Controller configuration
When you configure ISDN PRI, you must first specify an ISDN switch type for PRI and an E1 or T1 controller.
The following example specifies ISDN PRI on T1 slot 1, port 0:
isdn switch-type primary-4ess controllers t1 1/0 framing esf linecode b8zs pri-group timeslots 2-6
You can use the master indexes or search online to find documentation of related commands.
controller e1
controller t1
interface serial
isdn switch-type
To enable pulsing DTR signal intervals on the serial interfaces, use the pulse-time interface configuration command. Use the no form of this command to restore the default interval.
pulse-time seconds| seconds | Integer that specifies the DTR signal interval in seconds. |
0 seconds
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
When the serial line protocol goes down (for example, because of loss of synchronization) the interface hardware is reset and the DTR signal is held inactive for at least the specified interval. This function is useful for handling encrypting or other similar devices that use the toggling of the DTR signal to resynchronize.
The following example enables DTR pulse signals for three seconds on serial interface 2:
interface serial 2 pulse-time 3
To set the ring speed for the CSC-1R and CSC-2R Token Ring interfaces, use the ring-speed interface configuration command.
ring-speed speed| speed | Integer that specifies the ring speed, either 4 for 4-Mbps or 16 for 16-Mbps operation. |
16-Mbps operation
Caution Configuring a ring speed that is wrong or incompatible with the connected Token Ring will cause the ring to beacon, which effectively takes the ring down and makes it nonoperational.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example sets a Token Ring interface ring speed to 4 Mbps:
interface tokenring 0 ring-speed 4
To configure the network line speed for a serial interface on a 4-wire 56/64-kbps CSU/DSU module, use the service-module 56k clock rate interface configuration command. Use the no form of this command to enable a network line speed of 56 kbps, which is the default.
service-module 56k clock rate speed| speed | Network line speed in kbps. The default speed is 56 kbps. Choose from one of the following optional speeds:
· 2.4--2400 kbps · 4.8--4800 kbps · 9.6--9600 kbps · 19.2--19200 kbps · 38.4--38400 kbps · 56--56000 kbps · 64--64000 kbps · auto--Automatic line speed mode. Configure this option if your line speed is constantly changing. |
56 kbps
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
The 56-kbps line speed is available in switched mode, which is enabled using the service-module 56k network-type interface configuration command on the 4-wire CSU/DSU. If you have a 2-wire CSU/DSU module, the default is automatically set to switched mode.
The 64-kbps line speed cannot be used with back-to-back digital data service (DDS) lines. The subrate line speeds are determined by the service provider.
The keyword auto enables the CSU/DSU to decipher current line speed from the sealing current running on the network. Use auto only when transmitting over telco DDS lines and the clocking source is taken from the line.
The following example displays two routers connected in back-to-back DDS mode. However, notice that at first the configuration fails because the auto option is used. Later in the example the correct matching configuration is issued, which is 38.4 kbps.
Router1(config)#interface serial 0Router1(config-if)#service-module 56k clock source internalRouter1(config-if)#service-module 56k clock rate 38.4Router2(config-if)#service-module 56k clock rate autoa1#ping 10.1.1.2Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Router2(config-if)#service-module 56k clock rate 38.4Router1#ping 10.1.1.2Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 52/54/56 ms
When transferring from DDS mode to switched mode, you must set the correct clock rate, as shown in the following example:
Router2(config-if)#service-module 56k network-type ddsRouter2(config-if)#service-module 56k clock rate 38.4Router2(config-if)#service-module 56k network-type switched% Have to use 56k or auto clock rate for switched mode % Service module configuration command failed: WRONG FORMAT. Router2(config-if)#service-module 56k clock rate auto% WARNING - auto rate will not work in back-to-back DDS. Router2(config-if)#service-module 56k network-type switched
You can use the master indexes or search online to find documentation of related commands.
service-module 56k clock source
service-module 56k network-type
To set up the clock source on a serial interface for a 4-wire 56/64-kbps CSU/DSU module, use the service-module 56k clock source interface configuration command. Use the no form of this command to specify the clocking come from line.
service-module 56k clock source {line | internal}| line | Use the clocking provided by the active line coming in to the router. |
| internal | Use the internal clocking provided by the hardware module. |
Line clock
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
In most applications, the CSU/DSU should be configured with the clock source line command. For back-to-back configurations, configure one CSU/DSU with the clock source internal command and the other with clock source line command.
The following example configures internal clocking and transmission speed at 38.4 kbps.
router(config)#interface serial 0router(config-if)#service-module 56k clock source internalrouter(config-if)#service-module 56k clock rate 38.4
You can use the master indexes or search online to find documentation of related commands.
service-module 56k clock rate
To prevent application data from replicating loopback codes when operating at 64 kbps on a 4-wire CSU/DSU, use the service-module 56k data-coding interface configuration command. Use the no form of this command to enable normal transmission.
service-module 56k data-coding {normal | scrambled}| normal | Specifies normal transmission of data. |
| scrambled | Scrambles bit codes or user data before transmission. All control codes such as out of service and out of frame are avoided. |
Normal data transmission
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Enable the scrambled configuration only in 64-kbps digital data service (DDS) mode. If the network type is set to switched, the configuration is refused.
If you transmit scrambled bit codes, both CSU/DSUs must have this command configured for successful communication.
The following example scrambles bit codes or user data before transmission:
router(config)#interface serial 0router(config-if)#service-module 56k clock rate 64router(config-if)#service-module 56k data-coding scrambled
You can use the master indexes or search online to find documentation of related commands.
service-module 56k clock rate
To transmit packets in switched dial-up mode or digital data service (DDS) mode using a serial interface on a 4-wire 56/64-kbps CSU/DSU module, use the service-module 56k network-type interface configuration command. Use the no form of this command to transmit from a dedicated leased line in DDS mode.
service-module 56k network-type {dds | switched}| dds | Transmits packets in DDS mode or through a dedicated leased line. |
| switched | Transmits packets in switched dial-up mode. On a 2-wire switched 56-kbps CSU/DSU module this is the default and only setting. |
DDS is enabled for the 4-wire CSU/DSU.
Switched is enabled for the 2-wire CSU/DSU.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
In switched mode, you need additional dialer configuration commands to configure dial-out numbers. Before you enable the service-module 56k network-type switched command, both CSU/DSUs must use a clock source coming from the line and the clock rate configured to auto or 56 kbps. If the clock rate is not set correctly, this command will not be accepted.
The 2-wire and 4-wire 56/64-kbps CSU/DSU modules use V.25 bis dial commands to interface with the router. Therefore, the interface must be configured using the dialer in-band command. DTR dial is not supported.
The following example configures transmission in switched dial-up mode:
router(config)#interface serial 0router(config-if)#service-module 56k clock rate autorouter(config-if)#service-module 56k network-type switchedrouter(config-if)#dialer in-bandrouter(config-if)#dialer string 2576666router(config-if)#dialer-group 1
You can use the master indexes or search online to find documentation of related commands.
dialer in-band
service-module 56k clock rate
service-module 56k clock source
service-module 56k switched-carrier
To enable the acceptance of a remote loopback request on a serial interface on a 2- or 4-wire 56/64-kbps CSU/DSU module, use the service-module 56k remote-loopback interface configuration command. Use the no form of this command to disable the module from entering loopback.
service-module 56k remote-loopbackThis command has no arguments or keywords.
Enabled
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
The no service-module 56k remote-loopback command prevents the local CSU/DSU from being placed into loopback by remote devices on the line. The line provider is still able to put the module into loopback by reversing sealing current. Unlike the T1 module, the 2- or 4-wire 56/64-kbps CSU/DSU module can still initiate remote loopbacks with the no form of this command configured.
The following example enables transmitting and receiving remote loopbacks:
router(config)#interface serial 0router(config-if)#service-module 56k remote-loopback
You can use the master indexes or search online to find documentation of related commands.
loopback remote (interface)
To select a service provider to use with a 2- or 4-wire 56/64 kbps dial-up serial line, use the service-module 56k switched-carrier interface configuration command. Use the no form of this command to enable the default service provider.
service-module 56k switched-carrier {att | sprint | other}| att | AT&T or other digital network service provider. |
| sprint | Sprint or other service provider whose network requires echo cancelers. |
| other | Service provider besides AT&T or Sprint. |
ATT is enabled on the 4-wire 56/64-kbps CSU/DSU module.
Sprint is enabled on the 2-wire switched 56-kbps CSU/DSU module.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
On a Sprint network, echo-canceler tones are sent during call setup to prevent the echo cancelers from damaging digital data. The transmission of echo-canceler tones may increase call setup times by 8 seconds on the 4-wire module. Having echo cancellation enabled does not affect data traffic.
This configuration command is ignored if the network type is DDS.
The following example configures AT&T as a service provider:
router(config)#interface serial 0router(config-if)#service-module 56k network-type switchedrouter(config-if)#service-module 56k switched-carrier att
You can use the master indexes or search online to find documentation of related commands.
service-module 56k network-type
To specify the clock source for the fractional T1/T1 CSU/DSU module, use the service-module t1 clock source interface configuration command. Use the no form of this command to enable the line clock.
service-module t1 clock source {internal | line}| internal | Specifies the CSU/DSU internal clock. |
| line | Specifies the line clock. |
Line clock
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
The following example sets an internal clock source on serial line 0:
interface serial 0 service-module t1 clock source line
You can use the master indexes or search online to find documentation of related commands.
service-module 56k clock source
To guarantee the ones density requirement on an AMI line using the fractional T1/T1 module, use the service-module t1 data-coding inverted interface configuration command. Use the no form of this command to enable normal data transmission.
service-module t1 data-coding {inverted | normal}| inverted | Inverts bit codes by changing all 1 bits into 0 bits and all 0 bits into 1 bits. |
| normal | Requests that no bit codes be inverted before transmission. |
Normal transmission
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Data inversion is used to guarantee the ones density requirement on an AMI line when using bit-oriented protocols such as High-Level Data Link Control (HDLC), Point-to-Point Protocol (PPP), X.25, and Frame Relay. If the timeslot speed is set to 56 kbps, this command is rejected because line density is guaranteed when transmitting at 56 kbps. Use this command with the 64-kbps line speed.
If you transmit inverted bit codes, both CSU/DSUs must have this command configured for successful communication.
The following example inverts bit codes using a timeslot speed of 64 kbps:
service-module t1 timeslots all speed 64 service-module t1 data-coding inverted
You can use the master indexes or search online to find documentation of related commands.
service-module t1 linecode
service-module t1 timeslots
To select the frame type for a line using the fractional T1/T1 (FT1/T1) module, use the service-module t1 framing interface configuration command. Use the no form of this command to select the default, which is Extended Super Frame as the T1 frame type.
service-module t1 framing {esf | sf}| esf | Specifies Extended Super Frame as the T1 frame type. |
| sf | Specifies D4 Super Frame as the T1 frame type. |
esf
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command in configurations where the router communicates with FT1/T1 data lines. The service provider determines which framing type, either esf or sf, is required for your circuit.
The following example enables Super Frame as the FT1/T1 frame type:
service-module t1 framing sf
To configure the CSU line build out (LBO) on a fractional T1/T1 CSU/DSU module, use the service-module t1 lbo interface configuration command. Use the no form of this command to disable line build out.
service-module t1 lbo {-15 db | -7.5 db | none}| -15 db | Decreases outgoing signal strength by 15 dB. |
| -7.5 db | Decreases outgoing signal strength by 7.5 dB. |
| none | Transmits packets without decreasing outgoing signal strength. |
No line build out
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command to decrease the outgoing signal strength to an optimum value for a fractional T1 line receiver. The ideal signal strength should be -15 dB to -22 dB, which is calculated by adding the phone company loss + cable length loss + line build out.
You may use this command in back-to-back configurations, but it is not needed on most actual T1 lines.
The following example shows an Lbo setting of -7.5 dB:
service-module t1 lbo -7.5db
To select the line code for the fractional T1/T1 module, use the service-module t1 linecode interface configuration command. Use the no form of this command to select the default, which is the B8ZS line code.
service-module t1 linecode {ami | b8zs}| ami | Specifies alternate mark inversion (AMI) as the line code. |
| b8zs | Specifies binary 8 zero substitution (B8ZS) as the line code. |
b8zs
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Configuring B8ZS is a method of ensuring the ones density requirement on a T1 line by substituting intentional bipolar violations in bit positions four and seven for a sequence of eight zero bits. When the CSU/DSU is configured for AMI, you must guarantee the ones density requirement in your router configuration using the service-module t1 data-coding inverted command or the service-module t1 timeslots speed 56 command.
Your T1 service provider determines which line code, either ami or b8zs, is required for your T1 circuit.
The following example specifies AMI as the line code:
service-module t1 linecode ami
You can use the master indexes or search online to find documentation of related commands.
service-module t1 data-coding
service-module t1 timeslots
To generate remote alarms (yellow alarms) at the local CSU/DSU or detect remote alarms sent from the remote CSU/DSU, use the service-module t1 remote-alarm-enable interface configuration command. Use the no form of this command to disable remote alarms.
service-module t1 remote-alarm-enableThis command has no arguments or keywords.
Remote alarms disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Remote alarms are transmitted by the CSU/DSU when it detects an alarm condition, such as a red alarm (loss of frame) or blue alarm (unframed ones). The receiving CSU/DSU then knows there is an error condition on the line.
With D4 Super Frame configured, a remote alarm condition is transmitted by setting the bit 2 of each time slot to zero. For received user data that has the bit 2 of each time slot set to zero, the CSU/DSU interprets the data as a remote alarm and interrupts data transmission, which explains why remote alarms are disabled by default. With Extended Super Frame configured, the remote alarm condition is signalled out of band in the facilities data link.
You can see if the FT1/T1 CSU/DSU is receiving a remote alarm (yellow alarm) by issuing the show service-module command.
The following example enables remote alarm generation and detection:
service-module t1 remote-alarm-enable
You can use the master indexes or search online to find documentation of related commands.
service-module t1 framing
To specify if the fractional T1/T1 CSU/DSU module enters loopback mode when it receives a loopback code on the line, use the service-module t1 remote-loopback interface configuration command. Use the no form of this command to disable remote loopbacks.
service-module t1 remote-loopback {full | payload} [alternate | v54]| full | Configures the remote loopback code used to transmit or accept CSU loopback requests. |
| payload | Configures the loopback code used by the local CSU/DSU to generate or detect payload-loopback commands. |
| alternate | (Optional) Transmits a remote CSU/DSU loopback request using a 4-in-5 pattern for loopup and 2-in-3 pattern for loopdown. This is an inverted version of the standard loopcode request. |
| v54 | (Optional) Industry standard loopback code. Use this configuration for CSU/DSUs that may not support the Accunet loopup standards. This keyword is used only with a payload request, not a full request. |
Full and payload loopbacks with standard-loopup codes
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
You can simultaneously configure the full and payload loopback points. However, only one loopback code can be configured at a time. For example, if you configure the service-module t1 remote-loopback payload alternate command, a payload v54 request cannot be transmitted or accepted.
The no form of this command disables loopback requests. For example, the no service-module t1 remote-loopback full command ignores all full-bandwidth loopback transmissions and requests. Configuring the no form of the command may not prevent telco line providers from looping your router in esf mode, because fractional T1/T1 lines use facilities data link messages to initiate loopbacks.
If you enable the service-module t1 remote-loopback command, the loopback remote commands on the FT1/T1 CSU/DSU module will not be successful.
The following example displays two routers connected back-to-back through a fractional T1/T1 line:
Router#no service-module t1 remote-loopback fullRouter#service-module t1 remote-loopback payload alternateRouter#loopback remote full%SERVICE_MODULE-5-LOOPUPFAILED: Unit 0 - Loopup of remote unit failed Router#service-module t1 remote-loopback payload v54Router#loopback remote payload%SERVICE_MODULE-5-LOOPUPFAILED: Unit 0 - Loopup of remote unit failed Router#service-module t1 remote-loopback payload alternateRouter#loopback remote payload%SERVICE_MODULE-5-LOOPUPREMOTE: Unit 0 - Remote unit placed in loopback
You can use the master indexes or search online to find documentation of related commands.
loopback remote (interface)
To define timeslots that constitute a fractional T1/T1 (FT1/T1) channel, use the service-module t1 timeslots interface configuration command. Use the no form of this command to resume the default setting (all FT1/T1 timeslots transmit at 64 kbps).
service-module t1 timeslots {range | all} [speed {56 | 64}]| range | The DS0 timeslots that constitute the FT1/T1 channel. The range is from 1 to 24, where the first timeslot is numbered 1 and the last timeslot is numbered 24. Specify this field by using a series of subranges separated by commas. |
| all | Selects all FT1/T1 timeslots. |
| speed | (Optional) Specifies the timeslot speed. |
| 56 | 56 kbps. |
| 64 | 64 kbps. This is the default for all timeslots. |
64 kbps
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command specifies which timeslots are used in fractional T1 operation and determines the amount of bandwidth available to the router in each FT1/T1 channel.
The timeslot range must match the timeslots assigned to the channel group. Your service provider defines the timeslots that comprise a channel group.
To use the entire T1 line, enable the service-module t1 timeslots all command.
The following example displays a series of timeslot ranges and a speed of 64 kbps:
service-module t1 timeslots 1-10,15-20,22 speed 64
You can use the master indexes or search online to find documentation of related commands.
service-module t1 data-coding
service-module t1 linecode
To display compression statistics, use the show compress EXEC command.
show compressThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
This information was modified in Cisco IOS Release 11.3 to include sample output for hardware compression (implemented in the CSA hardware).
The following is sample output from the show compress command when software compression is used on the router:
Router# show compress
Serial0
uncompressed bytes xmt/rcv 10710562/11376835
1 min avg ratio xmt/rcv 2.773/2.474
5 min avg ratio xmt/rcv 4.084/3.793
10 min avg ratio xmt/rcv 4.125/3.873
no bufs xmt 0 no bufs rcv 0
resets 0
Table 32 describes the fields shown in the display.
| Field | Description |
|---|---|
| Serial0 | Name and number of the interface. |
| uncompressed bytes xmt/rcv | Total number of uncompressed bytes sent and received. |
| 1 min avg ratio xmt/rcv
5 min avg ratio xmt/rcv 10 min avg ratio xmt/rcv | Static compression ratio for bytes sent and received, averaged over 1, 5, and 10 minutes. |
| no bufs xmt | Number of times buffers were not available to compress data being sent. |
| no bufs rcv | Number of times buffers were not available to uncompress data being received. |
| resets | Number of resets (for example, line errors could cause resets). |
The following is sample output from the show compress command when hardware compression is enabled (that is, compression is implemented in the CSA hardware):
Router# show compress
Serial6/1
Hardware compression enabled
CSA in slot3 in use
Compressed bytes sent: 402 bytes 0 Kbits/sec ratio: 4.092
Compressed bytes recv: 390 bytes 0 Kbits/sec ratio: 3.476
restarts:1
last clearing of counters: 1278 seconds
Table 33 describes the fields shown in the display. The information displayed by the show compress command is the same for hardware and distributed compression. For Cisco 7200 series routers with multiple CSAs, an additional line is displayed indicating the CSA in use.
| Field | Description |
|---|---|
| Serial6/1 | Name and number of the interface. |
| Hardware compression enabled | Type of compression. |
| CSA in slot3 in use | Identifies CSA which is performing compression service. |
| Compressed bytes sent | Total number of compressed bytes sent including the kilobits per second. |
| Compressed bytes recv | Total number of compressed bytes received including the kilobits per second. |
| ratio | Compression ratio for bytes sent and received since the link last came up or since the counters were last cleared. |
| restarts | Number of times the compression process restarted or reset. |
| last clearing of counters | Duration since the last time the counters were cleared with the clear counters command. |
To display all information under the cBus controller card, use the show controllers cbus privileged EXEC command on the Cisco 7500 or Cisco 7513 routers. This command also shows the capabilities of the card and reports controller-related failures.
show controllers cbusThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is partial sample output from the show controllers cbus command on a n500 series router with one VIP2 interface processor. This example does not show output from additional interface processors that are usually installed in a Cisco 7500 series router.
Router# show controller cbus
MEMD at 40000000, 2097152 bytes (unused 2752, recarves 1, lost 0)
RawQ 48000100, ReturnQ 48000108, EventQ 48000110
BufhdrQ 48000138 (2849 items), LovltrQ 48000150 (42 items, 1632 bytes)
IpcbufQ 48000158 (32 items, 4096 bytes)
3570 buffer headers (48002000 - 4800FF10)
pool0: 15 buffers, 256 bytes, queue 48000140
pool1: 368 buffers, 1536 bytes, queue 48000148
pool2: 260 buffers, 4544 bytes, queue 48000160
pool3: 4 buffers, 4576 bytes, queue 48000168
slot1: VIP2, hw 2.2, sw 200.50, ccb 5800FF30, cmdq 48000088, vps 8192
software loaded from system
FLASH ROM version 255.255
FastEthernet1/0/0, addr 0000.0c41.6c20 (bia 0000.0c41.6c20)
gfreeq 48000148, lfreeq 480001D0 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A00, txacc 48001A02 (value 0), txlimit 20
Ethernet1/1/0, addr 0000.0c41.6c28 (bia 0000.0c41.6c28)
gfreeq 48000148, lfreeq 480001D8 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A08, txacc 48001A0A (value 0), txlimit 20
Ethernet1/1/1, addr 0000.0c41.6c29 (bia 0000.0c41.6c29)
gfreeq 48000148, lfreeq 480001E0 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A10, txacc 48001A12 (value 0), txlimit 20
Ethernet1/1/2, addr 0000.0c41.6c2a (bia 0000.0c41.6c2a)
gfreeq 48000148, lfreeq 480001E8 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A18, txacc 48001A1A (value 0), txlimit 20
Ethernet1/1/3, addr 0000.0c41.6c2b (bia 0000.0c41.6c2b)
gfreeq 48000148, lfreeq 480001F0 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A20, txacc 48001A22 (value 0), txlimit 20
Ethernet1/1/4, addr 0000.0c41.6c2c (bia 0000.0c41.6c2c)
gfreeq 48000148, lfreeq 480001F8 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A28, txacc 48001A2A (value 0), txlimit 20
Ethernet1/1/5, addr 0000.0c41.6c2d (bia 0000.0c41.6c2d)
gfreeq 48000148, lfreeq 48000200 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A30, txacc 48001A32 (value 0), txlimit 20
Ethernet1/1/6, addr 0000.0c41.6c2e (bia 0000.0c41.6c2e)
gfreeq 48000148, lfreeq 48000208 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A38, txacc 48001A3A (value 0), txlimit 20
Ethernet1/1/7, addr 0000.0c41.6c2f (bia 0000.0c41.6c2f)
gfreeq 48000148, lfreeq 48000210 (1536 bytes), throttled 0
rxlo 4, rxhi 30, rxcurr 0, maxrxcurr 0
txq 48001A40, txacc 48001A42 (value 0), txlimit 20
The following is partial sample output of the show controllers cbus command for a Packet over SONET Interface Processor (POSIP) in slot 0; its single Packet OC-3 interface is Posi0/0:
slot0: POSIP, hw 2.1, sw 200.01, ccb 5800FF30, cmdq 48000080, vps 8192
software loaded from flash slot0:rsp_posip.new
FLASH ROM version 160.4, VPLD version 2.2
Posi0/0, applique is SONET
gfreeq 48000148, lfreeq 48000158 (4480 bytes), throttled 0
rxlo 4, rxhi 226, rxcurr 0, maxrxcurr 186
txq 48000160, txacc 48000082 (value 150), txlimit 150
The following is partial output of the show controllers cbus command for a Multichannel Interface Processor (MIP). Not all of the 23 channels defined on serial interface 1/0 are shown.
slot1: MIP, hw 1.1, sw 205.03, ccb 5800FF40, cmdq 48000088, vps 8192
software loaded from system
T1 1/0, applique is Channelized T1
gfreeq 48000130, lfreeq 480001B0 (1536 bytes), throttled 0
rxlo 4, rxhi 360, rxcurr 0, maxrxcurr 3
Serial1/0:0, txq 480001B8, txacc 48000082 (value 3), txlimit 3
Serial1/0:1, txq 480001B8, txacc 4800008A (value 3), txlimit 3
Serial1/0:2, txq 480001B8, txacc 48000092 (value 3), txlimit 3
Serial1/0:3, txq 480001B8, txacc 4800009A (value 3), txlimit 3
Serial1/0:4, txq 480001B8, txacc 480000A2 (value 3), txlimit 3
Serial1/0:5, txq 480001B8, txacc 480000AA (value 3), txlimit 3
Serial1/0:6, txq 480001B8, txacc 480000B2 (value 3), txlimit 3
Serial1/0:7, txq 480001B8, txacc 480000BA (value 3), txlimit 3
Table 34 describes significant fields in the per-slot part of these displays.
| Field | Description |
|---|---|
| slot1: | Slot location of the specific interface processor (in this case Packet over SONET Interface Processor). |
| hw | Version number of the card. |
| sw | Version number of the card's internal software (in read-only memory). |
| software loaded from | Source device and file name from which the router software was loaded. |
| FLASH ROM version VPLD version | Version of Flash ROM |
| Pos1/0, applique is SONET | Location of the specific interface and the hardware applique type (in this case a Packet OC-3 interface). |
| gfreeq | Location of the global free queue that is shared among similar interfaces. |
| lfreeq | Location of the local free queue, which is a private queue of MEMD buffers. |
| throttled | Number of times input packet processing has been throttled on this interface. |
| rxlo | Minimum number of MEMD buffers held on local free queue. When idle, the interface returns buffers from its local queue to the global free queue until only this number of buffers remain in the local queue. |
| rxhi | Maximum number of MEMD buffers that the interface can remove from the global free queue in order to populate its local queue. |
| rxcurr | Number of MEMD buffers currently on the local free queue. |
| maxrxcurr | Maximum number of MEMD buffers that were enqueued on the local free queue. |
| txq | Address of the transmit queue. |
| txacc | Address of the transmit queue accumulator. |
| txlimit | Maximum number of buffers allowed in the transmit queue. |
The following is sample output from the show controllers cbus command on a Cisco 7500 series router:
Router# show controllers cbus
cBus 1, controller type 3.0, microcode version 2.0
128 Kbytes of main memory, 32 Kbytes cache memory
40 1520 byte buffers, 14 4484 byte buffers
Restarts: 0 line down, 0 hung output, 0 controller error
HSCI 1, controller type 10.0, microcode version 129.3
Interface 6 - Hssi0, electrical interface is Hssi DTE
5 buffer RX queue threshold, 7 buffer TX queue limit, buffer size 1520
ift 0004, rql 2, tq 0000 0000, tql 7
Transmitter delay is 0 microseconds
MEC 3, controller type 5.1, microcode version 130.6
Interface 18 - Ethernet2, station address 0000.0c02.a03c (bia 0000.0c02.a03c)
10 buffer RX queue threshold, 7 buffer TX queue limit, buffer size 1520
ift 0000, rql 10, tq 0000 0000, tql 7
Transmitter delay is 0 microseconds
Interface 19 - Ethernet3, station address 0000.0c02.a03d (bia 0000.0c02.a03d)
10 buffer RX queue threshold, 7 buffer TX queue limit, buffer size 1520
ift 0000, rql 10, tq 0000 0000, tql 7
Transmitter delay is 0 microseconds
Table 35 describes the fields shown in the following lines of output from the display.
cBus 1, controller type 3.0, microcode version 2.0 128 Kbytes of main memory, 32 Kbytes cache memory 40 1520 byte buffers, 14 4484 byte buffers Restarts: 0 line down, 0 hung output, 0 controller error
| Field | Description |
|---|---|
| cBus 1 | Card type and number (varies depending on card). |
| controller type 3.0 | Version number of the card. |
| microcode version 2.0 | Version number of the card's internal software (in read-only memory). |
| 128 Kbytes of main memory | Amount of main memory on the card. |
| 32 Kbytes cache memory | Amount of cache memory on the card. |
| 40 1520 byte buffers | Number of buffers of this size on the card. |
| 14 4484 byte buffers | Number of buffers of this size on the card. |
| Restarts 0 line down 0 hung output 0 controller error | Count of restarts due to the following conditions: Communication line down Output unable to transmit Internal error |
Table 36 describes the fields shown in the following lines of output from the display:
HSCI 1, controller type 10.0, microcode version 129.3
Interface 6 - Hssi0, electrical interface is Hssi DTE
5 buffer RX queue threshold, 7 buffer TX queue limit, buffer size 1520
ift 0004, rql 2, tq 0000 0000, tql 7
Transmitter delay is 0 microseconds
| Field | Description |
|---|---|
| HSCI 1 | Card type and number (varies depending on card). |
| controller type 10.0 | Version number of the card. |
| microcode version 129.3 | Version number of the card's internal software (in read-only memory). |
| Interface 6 | Physical interface number. |
| Hssi 0 | Logical name for this interface. |
| electrical interface is Hssi DTE | Self-explanatory. |
| 5 buffer RX queue threshold | Maximum number of buffers allowed in the receive queue. |
| 7 buffer TX queue limit | Maximum number of buffers allowed in the transmit queue. |
| buffer size 1520 | Size of the buffers on this card (in bytes). |
| ift 0004 | Interface type code. 0 = EIP 1 = FSIP 4 = HIP 5 = TRIP 6 = FIP 7 = AIP |
| rql 2 | Receive queue limit. Current number of buffers allowed for the receive queue. It is used to limit the number of buffers used by a particular inbound interface. When equal to 0, all of that interface's receive buffers are in use. |
| tq 0000 0000 | Transmit queue head and tail pointers. |
| tql 7 | Transmit queue limit. Current number of buffers allowed for transmit queue. It limits the maximum cBus buffers allowed to sit on a particular interface's transmit queue. |
| Transmitter delay is 0 microseconds | Transmitter delay between the packets. |
The following is sample output of the show controllers cbus display for an AIP installed in IP slot 4, the running AIP microcode is Version 170.30, the PLIM type is 4B/5B, and the available bandwidth is 100 Mbps:
Router# show controllers cbus
Switch Processor 5, hardware version 11.1, microcode version 170.46
Microcode loaded from system
512 Kbytes of main memory, 128 Kbytes cache memory
60 1520 byte buffers, 91 4496 byte buffers
Restarts: 0 line down, 0 hung output, 0 controller error
AIP 4, hardware version 1.0, microcode version 170.30
Microcode loaded from system
Interface 32 - ATM4/0, PLIM is 4B5B(100Mbps)
15 buffer RX queue threshold, 36 buffer TX queue limit, buffer size 4496
ift 0007, rql 12, tq 0000 0620, tql 36
Transmitter delay is 0 microseconds
The following is sample output of the show controllers cbus display for SMIP:
Router# show controllers cbus
SMIP 2, hardware version 1.0, microcode version 10.0
Microcode loaded from system
Interface 16 - T1 2/0, electrical interface is Channelized T1
10 buffer RX queue threshold, 14 buffer TX queue limit, buffer size 1580 ift 0001, rql 7, tq 0000 05B0, tql 14
Transmitter delay is 0 microseconds
Use the show controllers ethernet EXEC command to display information on the Cisco 2500 series, Cisco 3000, or Cisco 4000 series.
show controllers ethernet number| number | Interface number of the Ethernet interface. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show controllers ethernet command on the Cisco 4000:
Router# show controllers ethernet 0
LANCE unit 0, NIM slot 1, NIM type code 4, NIM version 1
Media Type is 10BaseT, Link State is Up, Squelch is Normal
idb 0x4060, ds 0x5C80, regaddr = 0x8100000
IB at 0x600D7AC: mode=0x0000, mcfilter 0000/0001/0000/0040
station address 0000.0c03.a14f default station address 0000.0c03.a14f
buffer size 1524
RX ring with 32 entries at 0xD7E8
Rxhead = 0x600D8A0 (12582935), Rxp = 0x5CF0(23)
00 pak=0x60336D0 ds=0x6033822 status=0x80 max_size=1524 pak_size=98
01 pak=0x60327C0 ds=0x6032912 status=0x80 max_size=1524 pak_size=98
02 pak=0x6036B88 ds=0x6036CDA status=0x80 max_size=1524 pak_size=98
03 pak=0x6041138 ds=0x604128A status=0x80 max_size=1524 pak_size=98
04 pak=0x603FAA0 ds=0x603FBF2 status=0x80 max_size=1524 pak_size=98
05 pak=0x600DC50 ds=0x600DDA2 status=0x80 max_size=1524 pak_size=98
06 pak=0x6023E48 ds=0x6023F9A status=0x80 max_size=1524 pak_size=1506
07 pak=0x600E3D8 ds=0x600E52A status=0x80 max_size=1524 pak_size=1506
08 pak=0x6020990 ds=0x6020AE2 status=0x80 max_size=1524 pak_size=386
09 pak=0x602D4E8 ds=0x602D63A status=0x80 max_size=1524 pak_size=98
10 pak=0x603A7C8 ds=0x603A91A status=0x80 max_size=1524 pak_size=98
11 pak=0x601D4D8 ds=0x601D62A status=0x80 max_size=1524 pak_size=98
12 pak=0x603BE60 ds=0x603BFB2 status=0x80 max_size=1524 pak_size=98
13 pak=0x60318B0 ds=0x6031A02 status=0x80 max_size=1524 pak_size=98
14 pak=0x601CD50 ds=0x601CEA2 status=0x80 max_size=1524 pak_size=98
15 pak=0x602C5D8 ds=0x602C72A status=0x80 max_size=1524 pak_size=98
16 pak=0x60245D0 ds=0x6024722 status=0x80 max_size=1524 pak_size=98
17 pak=0x6008328 ds=0x600847A status=0x80 max_size=1524 pak_size=98
18 pak=0x601EB70 ds=0x601ECC2 status=0x80 max_size=1524 pak_size=98
19 pak=0x602DC70 ds=0x602DDC2 status=0x80 max_size=1524 pak_size=98
20 pak=0x60163E0 ds=0x6016532 status=0x80 max_size=1524 pak_size=98
21 pak=0x602CD60 ds=0x602CEB2 status=0x80 max_size=1524 pak_size=98
22 pak=0x6037A98 ds=0x6037BEA status=0x80 max_size=1524 pak_size=98
23 pak=0x602BE50 ds=0x602BFA2 status=0x80 max_size=1524 pak_size=98
24 pak=0x6018988 ds=0x6018ADA status=0x80 max_size=1524 pak_size=98
25 pak=0x6033E58 ds=0x6033FAA status=0x80 max_size=1524 pak_size=98
26 pak=0x601BE40 ds=0x601BF92 status=0x80 max_size=1524 pak_size=98
27 pak=0x6026B78 ds=0x6026CCA status=0x80 max_size=1524 pak_size=98
28 pak=0x6024D58 ds=0x6024EAA status=0x80 max_size=1524 pak_size=74
29 pak=0x602AF40 ds=0x602B092 status=0x80 max_size=1524 pak_size=98
30 pak=0x601FA80 ds=0x601FBD2 status=0x80 max_size=1524 pak_size=98
31 pak=0x6038220 ds=0x6038372 status=0x80 max_size=1524 pak_size=98
TX ring with 8 entries at 0xDA20, tx_count = 0
tx_head = 0x600DA58 (12582919), head_txp = 0x5DC4 (7)
tx_tail = 0x600DA58 (12582919), tail_txp = 0x5DC4 (7)
00 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
01 pak=0x000000 ds=0x602126A status=0x03 status2=0x0000 pak_size=60
02 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
03 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
04 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
05 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
06 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=118
07 pak=0x000000 ds=0x6003ED2 status=0x03 status2=0x0000 pak_size=126
0 missed datagrams, 0 overruns, 2 late collisions, 2 lost carrier events
0 transmitter underruns, 0 excessive collisions, 0 tdr, 0 babbles
0 memory errors, 0 spurious initialization done interrupts
0 no enp status, 0 buffer errors, 0 overflow errors
10 one_col, 10 more_col, 22 deferred, 0 tx_buff
0 throttled, 0 enabled
Lance csr0 = 0x73
To display information about initialization block information, transmit ring, receive ring and errors for the Fast Ethernet controller chip on the Cisco 4500, Cisco 7200 series, or Cisco 7500 series, use the show controllers fastethernet EXEC command.
show controllers fastethernet number (Cisco 4500)EXEC
This command first appeared in Cisco IOS Release 11.2.
The output of this command is generally useful for diagnostic tasks performed by technical support only.
The following is sample output from the show controllers fastethernet command on a Cisco 4500 router:
c4500-1# show controllers fastethernet 0
DEC21140 Slot 0, Subunit 0
dec21140_ds=0x60001234, registers=0x3c001000, ib=0x42301563, ring entries=256
rxring=0x40235878, rxr shadow=0x64528745, rx_head=0, rx_tail=10
txring=0x43562188, txr shadow=0x65438721, tx_head=17, tx_tail=34, tx_count=17
DEC21140 Registers
CSR0=0x23457667, CSR3=0x12349878, CSR4=0x34528745, CSR5=0x76674565
CSR6=0x76453676, CSR7=0x76456574, CSR8=0x25367648, CSR9=0x87253674
CSR11=0x23456454, CSR12=0x76564787, CSR15=0x98273465
DEC21140 PCI registers
bus_no=0, device_no=0
CFID=0x12341234, CFCS=0x76547654, CFRV=0x87658765, CFLT=0x98769876
CBIO=0x12344321, CBMA=0x23454321, CFIT=0x34567654, CFDA=0x76544567
MII registers
Register 0x00: 0x1234 0x1234 0x2345 0x3456 0x4567 0x5678 0x6789 0x7890
Register 0x08: 0x9876 0x8765 0x7654 0x6543 0x5432 0x4321 0x3210 0x2109
Register 0x10: 0x1234 0x2345 0x3456 0x4567 0x5678 0x6789 0x7890
Register 0x18: 0x9876 0x8765 0x7654 0x6543 0x5432 0x4321
DEC21140 statistics
filtered_in_sw=1000, throttled=10, enabled=10
rx_fifo_overflow=10, rx_no_enp=12, rx_late_collision=18
rx_watchdog=15, rx_process_stopped=15, rx_buffer_unavailable=1500
tx_jabber_timeout=10, tx_carrier_loss=2, tx_deffered=15
tx_no_carrier=1, tx_late_collision=10, tx_excess_coll=10
tx_process_stopped=1, fata_tx_err=0
The following is sample output from the show controllers fastethernet command on a Cisco 7500 series router:
router# show controllers fastethernet 0/0
Interface FastEthernet0/0
Hardware is DEC21140
dec21140_ds=0x60895888, registers=0x3C018000, ib=0x4B019500
rx ring entries=128, tx ring entries=128
rxring=0x4B019640, rxr shadow=0x60895970, rx_head=0, rx_tail=0
txring=0x4B019EC0, txr shadow=0x60895B98, tx_head=77, tx_tail=77, tx_count=0
CSR0=0xFFFA4882, CSR3=0x4B019640, CSR4=0x4B019EC0, CSR5=0xFC660000
CSR6=0xE20CA202, CSR7=0xFFFFA241, CSR8=0xFFFE0000, CSR9=0xFFFDD7FF
CSR11=0xFFFE0000, CSR12=0xFFFFFF98, CSR15=0xFFFFFEC8
DEC21140 PCI registers:
bus_no=0, device_no=6
CFID=0x00091011, CFCS=0x02800006, CFRV=0x02000012, CFLT=0x0000FF00
CBIO=0x7C5AFF81, CBMA=0x48018000, CFIT=0x0000018F, CFDA=0x0000AF00
MII registers:
Register 0x00: 2000 780B 2000 5C00 01E1 0000 0000 0000
Register 0x08: 0000 0000 0000 0000 0000 0000 0000 0000
Register 0x10: 0000 0000 0000 0000 0000 0000 8040
Register 0x18: 8000 0000 0000 3800 A3B9
throttled=0, enabled=0, disabled=0
rx_fifo_overflow=0, rx_no_enp=0, rx_discard=0
tx_underrun_err=0, tx_jabber_timeout=0, tx_carrier_loss=1
tx_no_carrier=1, tx_late_collision=0, tx_excess_coll=0
tx_collision_cnt=0, tx_deferred=0, fatal_tx_err=0, mult_ovfl=0
HW addr filter: 0x60895FC0, ISL Enabled
Entry= 0: Addr=0100.0CCC.CCCC
Entry= 1: Addr=0300.0000.0001
Entry= 2: Addr=0100.0C00.0000
Entry= 3: Addr=FFFF.FFFF.FFFF
Entry= 4: Addr=FFFF.FFFF.FFFF
Entry= 5: Addr=FFFF.FFFF.FFFF
Entry= 6: Addr=FFFF.FFFF.FFFF
Entry= 7: Addr=FFFF.FFFF.FFFF
Entry= 8: Addr=FFFF.FFFF.FFFF
Entry= 9: Addr=FFFF.FFFF.FFFF
Entry=10: Addr=FFFF.FFFF.FFFF
Entry=11: Addr=FFFF.FFFF.FFFF
Entry=12: Addr=FFFF.FFFF.FFFF
Entry=13: Addr=FFFF.FFFF.FFFF
Entry=14: Addr=FFFF.FFFF.FFFF
Entry=15: Addr=0060.3E28.6E00
You can use the master indexes or search online to find documentation of related commands.
show interface fastethernet
To display all information under the FDDI Interface Processor (FIP) on the Cisco 7200 series and Cisco 7500 series, use the show controllers fddi user EXEC command.
show controllers fddiThis command has no arguments or keywords.
User EXEC
This command first appeared in Cisco IOS Release 10.0.
This command reflects the internal state of the chips and information the system uses for bridging and routing that is specific to the interface hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
The following is sample output from the show controllers fddi command:
Router# show controllers fddi
Fddi2/0 - hardware version 2.2, microcode version 1.2
Phy-A registers:
cr0 4, cr1 0, cr2 0, status 3, cr3 0
Phy-B registers:
cr0 4, cr1 4, cr2 0, status 3, cr3 0
FORMAC registers:
irdtlb 71C2, irdtneg F85E, irdthtt F5D5, irdmir FFFF0BDC
irdtrth F85F, irdtmax FBC5, irdtvxt 5959, irdstmc 0810
irdmode 6A20, irdimsk 0000, irdstat 8060, irdtpri 0000
FIP registers
ccb: 002C cmd: 0006 fr: 000F mdptr: 0000 mema: 0000
icb: 00C0 arg: 0003 app: 0004 mdpg: 0000 af: 0603
clm: E002 bcn: E016 clbn: 0198 rxoff: 002A en: 0001
clmbc: 8011 bcnbc: 8011 robn: 0004 park: 0000 fop: 8004
txchn: 0000 pend: 0000 act: 0000 tail: 0000 cnt: 0000
state: 0003 check: 0000 eof: 0000 tail: 0000 cnt: 0000
rxchn: 0000 buf0: 0534 nxt0: 0570 eof: 0000 tail: 0000
eofch: 0000 buf1: 051C nxt1: 0528 pool: 0050 err: 005C
head: 0984 cur: 0000 t0: 0030 t1: 0027 t2: 000F
tail: 0984 cnt: 0001 t3: 0000 rxlft: 000B used: 0000
txq_s: 0018 txq_f: 0018 Aarm: 0000 Barm: 1388 fint: 8004
Total LEM: phy-a 6, phy-b 13
The last line of output indicates how many times the specific PHY encountered an "UNKNOWN LINE STATE" event on the fiber.
To show hardware and software information about the LAN Extender chassis, use the show controllers lex EXEC command.
show controllers lex [number]| number | (Optional) Number of the LAN Extender interface about which to display information. |
| slot | Refer to the appropriate hardware manual for slot and port information. |
| port | Refer to the appropriate hardware manual for slot and port information. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
Use the show controllers lex command to display information about the hardware revision level, software version number, Flash memory size, serial number, and other information related to the configuration of the LAN Extender.
The following is sample output from the show controllers lex command:
Router#show controllers lex 0Lex0:FLEX Hardware revision 1FLEX Software version 255.0128K bytes of flash memorySerial number is 123456789Station address is 0000.4060.1100
The following is sample output from the show controllers lex command when the LAN Extender interface is not bound to a serial interface:
Router#show controllers lex 1Lex1 is not bound to a serial interface
Table 37 describes the fields shown in the output.
| Field | Description |
|---|---|
| Lex0: | Number of the LAN Extender interface. |
| FLEX Hardware revision | Revision number of the Cisco 1000 series LAN Extender chassis. |
| FLEX Software version | Revision number of the software running on the LAN Extender chassis. |
| 128K bytes of Flash memory | Amount of Flash memory in the LAN Extender. |
| Serial number | Serial number of the LAN Extender chassis. |
| Station address | MAC address of the LAN Extender chassis. |
Use the show controllers mci privileged EXEC command to display all information under the Multiport Communications Interface card or the SCI.
show controllers mciThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
This command displays information the system uses for bridging and routing that is specific to the interface hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
The following is sample output from the show controllers mci command:
Router# show controllers mci
MCI 0, controller type 1.1, microcode version 1.8
128 Kbytes of main memory, 4 Kbytes cache memory
22 system TX buffers, largest buffer size 1520
Restarts: 0 line down, 0 hung output, 0 controller error
Interface 0 is Ethernet0, station address 0000.0c00.d4a6
15 total RX buffers, 11 buffer TX queue limit, buffer size 1520
Transmitter delay is 0 microseconds
Interface 1 is Serial0, electrical interface is V.35 DTE
15 total RX buffers, 11 buffer TX queue limit, buffer size 1520
Transmitter delay is 0 microseconds
High speed synchronous serial interface
Interface 2 is Ethernet1, station address aa00.0400.3be4
15 total RX buffers, 11 buffer TX queue limit, buffer size 1520
Transmitter delay is 0 microseconds
Interface 3 is Serial1, electrical interface is V.35 DCE
15 total RX buffers, 11 buffer TX queue limit, buffer size 1520
Transmitter delay is 0 microseconds
High speed synchronous serial interface
Table 38 describes significant fields shown in the display.
| Field | Description |
|---|---|
| MCI 0 | Card type and unit number (varies depending on card). |
| controller type 1.1 | Version number of the card. |
| microcode version 1.8 | Version number of the card's internal software (in read-only memory). |
| 128 Kbytes of main memory | Amount of main memory on the card. |
| 4 Kbytes cache memory | Amount of cache memory on the card. |
| 22 system TX buffers | Number of buffers that hold packets to be transmitted. |
| largest buffer size 1520 | Largest size of these buffers (in bytes). |
| Restarts 0 line down 0 hung output 0 controller error | Count of restarts due to the following conditions: Communication line down Output unable to transmit Internal error |
| Interface 0 is Ethernet0 | Names of interfaces, by number. |
| electrical interface is V.35 DTE | Line interface type for serial connections. |
| 15 total RX buffers | Number of buffers for received packets. |
| 11 buffer TX queue limit | Maximum number of buffers in transmit queue. |
| Transmitter delay is 0 microseconds | Delay between outgoing frames. |
| Station address 0000.0c00.d4a6 | Hardware address of the interface. |
You can use the master indexes or search online to find documentation of related commands.
tx-queue-limit
To display all information about the ISA bus interface, use the show controllers pcbus privileged EXEC command.
show controllers pcbusThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
This command is valid on LanOptics' Branchcard or Stacknet 2000 products only.
The following is sample output from the show controllers pcbus command:
Router# show controllers pcbus
PCbus unit 0, Name = PCbus0 Hardware is ISA PCbus shared RAM
IDB at 0x3719B0, Interface driver data structure at 0x3735F8
Control/status register at 0x2110008, Shared memory at 0xC000000
Shared memory is initialized
Shared memory interface control block :
Magic no = 0x41435A56 (valid) Version = 1.0
Shared memory size = 64K bytes, Interface is NOT shutdown
Interface state is up, line protocol is up
Tx buffer : (control block at 0xC000010)
Start offset = 0x30, Size = 0x7FE8, Overflows = 1
GET_ptr = 0x4F6C, PUT_ptr = 0x4F6C, WRAP_ptr = 0x3BB0
Rx buffer : (control block at 0xC000020)
Start offset = 0x8018, Size 0x7FE8, Overflows = 22250698
GET_ptr = 0x60, PUT_ptr = 0x60, WRAP_ptr = 0x7FD0
Interrupts received = 567
Use the show controllers serial privileged EXEC command to display information that is specific to the interface hardware.
show controllers serialThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
Sample output of the show controllers serial command on the Cisco 4000 follows:
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
buffer size 1524
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
To display information about the T1 links, use the show controllers t1 privileged EXEC command.
show controllers t1 [slot/port] (Cisco 7500 series)| slot/port | Backplane slot number and port number on the interface. See your hardware installation manual for the specific slot and port numbers. |
| number | Network processor module (NPM) number, in the range 0 through 2. |
EXEC
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
If you specify a slot and port number, each 15 minute period will be displayed.
The following is sample output from the show controllers t1 command on the Cisco 7500 series:
Router# show controllers t1
T1 4/1 is up.
No alarms detected.
Framing is ESF, Line Code is AMI, Clock Source is line
Data in current interval (0 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs,
0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs,
0 Severely Err Secs, 0 Unavail Secs
Total Data (last 79 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs,
0 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs,
0 Severely Err Secs, 0 Unavail Secs
Table 39 describes the show controllers t1 display fields.
| Field | Description |
|---|---|
| T1 0/0 is up. | The T1 controller 0 in slot 0 is operating. The controller's state can be up, down, administratively down. Loopback conditions are shown by (Locally Looped) or (Remotely Looped). |
| No alarms detected. | Any alarms detected by the controller are displayed here. Possible alarms are as follows:
Transmitter is sending remote alarm. Transmitter is sending AIS. Receiver has loss of signal. Receiver is getting AIS. Receiver has loss of frame. Receiver has remote alarm. Receiver has no alarms. |
| Data in current interval (725 seconds elapsed) | 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. |
| Line Code Violations | Indicates the occurrence of either a Bipolar Violation (BPV) or Excessive Zeros (EXZ) error event. |
| Path Code Violations | Indicates a frame synchronization bit error in the D4 and E1-noCRC formats, or a CRC error in the ESF and E1-CRC formats. |
| Slip Secs | Indicates the replication or deletion of the payload bits of a DS1 frame. A slip may be performed 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 are detected: one or more Path Code Violations; one or more Out of Frame defects; one or more Controlled Slip events; a detected AIS defect.
For D4 and E1-noCRC links, the presence of Bipolar Violations also triggers an Errored Second. |
| Bursty Err Secs | A second with fewer than 320 and more than 1 Path Coding Violation error, no Severely Errored Frame defects and no detected incoming AIS defects. Controlled slips are not included in this parameter. |
| Severely Err Secs | For ESF signals, a second with one of the following errors: 320 or more Path Code Violation errors; one or more Out of Frame defects; a detected AIS defect.
For E1-CRC signals, a second with one of the following errors: 832 or more Path Code Violation errors; one or more Out of Frame defects. For E1-noCRC signals, a second with 2048 Line Code Violations or more. For D4 signals, a count of 1-second intervals with Framing Errors, or an Out of Frame defect, or 1544 Line Code Violations. |
| Unavail Secs | A count of the total number of seconds on the interface. |
To display information about the Channelized T3 Interface Processor (CT3IP) on Cisco 7500 series routers, use the show controllers t3 privileged EXEC command.
show controllers t3 [slot/port-adapter/port [:t1-channel]] [brief | tabular | remote performance [brief | tabular]]| slot | Refer to the appropriate hardware manual for slot and port information. |
| port-adapter | Refer to the appropriate hardware manual for information about port adapter compatibility. |
| port | Refer to the appropriate hardware manual for slot and port information. |
| :t1-channel | (Optional) For the CT3IP, the T1 channel is a number between 1 and 28. |
| remote performance | (Optional) Displays the far-end ANSI performance monitor information when enabled on the T1 channel with the t1 fdl ansi controller command. |
| brief | (Optional) Displays a subset of information. |
| tabular | (Optional) Displays information in a tabular format. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3.
This command was modified in Cisco IOS Release 11.3 to include the remote performance keyword.
The show controllers t3 command also displays Maintenance Data Link (MDL) information (received strings) if MDL is configured and framing is set to C-bit.
The following is partial sample output from the show controller t3 command:
Router# show controller t3 3/0/0
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0
Mx H/W version: 2, Mx ucode ver: 1.24
Applique type is Channelized T3
No alarms detected.
FEAC code received: No code is being received
Framing is M23, Line Code is B3ZS, Clock Source is Internal.
Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OK
Data in current interval (39 seconds elapsed):
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
Total Data (last 1 15 minute intervals):
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
T1 1 is down, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per ANSI T1.403 and AT&T 54016 spec.
Configured for FDL Remotely Line Looped
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
BERT test result (running)
Test Pattern: All 0's, Status: Sync, Sync Detected: 1
Interval: 4 minute(s), Tim Remain: 4 minute(s)
Bit Errors (Sync BERT Started): 0 bits
Bit Errors (Sync last Sync): 0 bits, Bits Received: 7 Mbits
...
T1 15 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
Data in current interval (69 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
Total Data (last 1 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
The following is partial sample output from the show controller t3 brief command:
router# show controllers t3 3/0/0 brief
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0
Mxt H/W version: 2, Mxt ucode ver: 1.24
Applique type is Channelized T3
No alarms detected.
FEAC code received: No code is being received
Framing is M23, Line Code is B3ZS, Clock Source is Internal.
Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OK
T1 1 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per ANSI T1.403 and AT&T 54016 spec.
Configured for FDL Remotely Line Looped
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
BERT test result (done)
Test Pattern: All 0's, Status: Not Sync, Sync Detected: 1
Interval: 4 minute(s), Tim Remain: 0 minute(s)
Bit Errors(Sync BERT Started): 0 bits
Bit Errors(Sync last Sync): 0 bits, Bits Received: 368 Mbits
...
The following is partial sample output from the show controllers t3 tabular command:
router# show controllers t3 3/0/0 tabular
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 1.2, CT3 F/W Version: 2.1.0
Mx H/W version: 2, Mx ucode ver: 1.25
Applique type is Channelized T3
No alarms detected.
MDL transmission is disabled
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.
Ext1: AIS, Ext2: LOS, Ext3: LOS, Test: LOS
INTERVAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES
08:56-09:11 0 0 0 0 0 0 0 0 0 0
08:41-08:56 0 0 0 0 0 0 0 0 0 0
08:26-08:41 0 0 0 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0 0 0 0
T1 2 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per AT&T 54016 spec.
No alarms detected.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
INTERVAL LCV PCV CSS SELS LES DM ES BES SES UAS SS
08:56-09:11 0 0 0 0 0 0 0 0 0 0 0
08:41-08:56 0 0 0 0 0 0 0 0 0 0 0
08:26-08:41 0 0 0 0 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0 0 0 0 0
The following is partial sample output from the show controller t3 remote performance command. This information is available if the t1 fdl ansi controller command is enabled for a T1 channel on a CT3IP.
Router# show controller t3 3/0/0 remote performance
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 20.2.0
Mx H/W version: 2, Mx ucode ver: 1.25
T1 1 - Remote Performance Data
Data in current interval (356 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Data in Interval 1:
1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Total Data (last 2 15 minute intervals):
1 Path Code Violations
1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
...
Table 40 describes the show controller t3 display fields.
| Field | Description |
|---|---|
| T3 3/0/0 is up | T3 controller in slot 3 is operating. The controller's state can be up, down, administratively down. Loopback conditions are shown by (Locally looped) or (Remotely Looped). |
| CT3 H/W Version | Version number of the hardware. |
| CT3 ROM Version | Version number of the ROM. |
| CT3 F/W Version | Version number of the firmware. |
| Mx H/W version | Hardware version number of the HDLC controller chip. |
| Mx ucode ver | Microcode version of the HDLC controller chip. |
| Applique type | Controller type. |
| No alarms detected | Any alarms detected by the controller are displayed here. Possible alarms are as follows:
|
|
MDL transmission is disabled | Status of the maintenance data link (either enabled or disabled). |
| FEAC code received | Whether or not a far-end alarm code request is being received. Possible values are as follows:
|
|
Framing is M23 | Framing type on the CT3IP. Values are: M23, C-Bit, and Auto-detect. |
| Line Code is B3ZS | Line coding format on the CT3IP. |
| Clock Source is Internal | Clock source on the CT3IP. Values are: internal or line. |
| BERT test result | BERT test information is available if the t1 bert controller command is enabled for the T1 channel on the CT3IP. The BERT results include the following information:
When the T1 channel has a BERT test running, the line state is DOWN. Also, when the BERT test is running and the Status field is Not Sync, the information in the total bit errors field is not valid. When the BERT test is done, the Status field is not relevant. |
| Data in current interval (39 seconds elapsed) | 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. |
| Line Code Violations | Line Code Violations (LCV) is a count of both Bipolar Violations (BPVs) and Excessive Zeros (EXZs) occurring over the accumulation period. An EXZ increments the LCV by one regardless of the length of the zero string. |
| P-bit Coding Violation | For all DS3 applications, a P-bit coding violation (PVC) error event is a P-bit parity error event. A P-bit parity error event is the occurrence of a received P-bit code on the DS3 M-frame that is not identical to the corresponding locally calculated code. |
| C-bit Coding Violation | For C-bit parity and SYNTRAN DS3 applications, the C-bit coding violation (CCV) is the count of coding violations reported via the C-bits. For C-bit parity, it is the count of CP-bit parity errors occurring in the accumulation interval. For SYNTRAN, it is a count of CRC-9 errors occurring in the accumulation interval. |
| P-bit Err Secs | P-bit errored seconds (PES) is a second with one or more PCVs, one or more out of frame defects, or a detected incoming AIS. This gauge is not incremented when unavailable seconds are counted. |
| P-bit Severely Err Secs | P-bit severely errored seconds (PSES) is a second with 44 or more PCVs, one or more out of frame defects, or a detected incoming AIS. This gauge is not incremented when unavailable seconds are counted. |
| Severely Err Framing Secs | Severely errored framing seconds (SEFS) is a second with one or more out of frame defects or a detected incoming AIS. |
| Unavailable Secs | Unavailable seconds (UAS) are calculated by counting the number of seconds that the interface is unavailable. For more information, refer to RFC 1407. |
| Line Err Secs | Line errored seconds (LES) is a second in which one or more code violations occurred or one or more LOS defects. |
| C-bit Errored Secs | C-bit errored seconds (CES) is a second with one or more C-bit code violations (CCV), one or more Out of Frame defects, or a detected incoming AIS. This gauge is not incremented when UASs are counted. |
| C-bit Severely Errored Secs | C-bit severely errored seconds (CSES) is a second with 44 or more CCVs, one or more Out of Frame defects, or a detected incoming AIS. This gauge is not incremented when UASs are counted. |
| Total Data (last 1 15 minute intervals) | Shows the last 15-minute accumulation period. |
| T1 1 is up | T1 channel is operating. The channel's state can be up, down, administratively down. Loopback conditions are shown by (Locally looped) or (Remotely looped). |
| speed | Speed of the T1 channel in kbps. |
| non-inverted data | Indicates if the T1 channel is configured for inverted data. |
| timeslots | Timeslots assigned to the T1 channel. |
| FDL per AT&T 54016 spec. | Performance monitoring is via Facility Data Link per ANSI T1.403. |
| No alarms detected | Any alarms detected by the T1 controller are displayed here. Possible alarms are as follows:
|
|
Framing is ESF | Type of framing used on the T1 channel. Values are: ESF or SF. |
| LineCode is B8ZS | Type of line coding used on the T1 channel. Values are: B8ZS or AMI. |
| Clock Source is Internal | Clock source on the T1 channel. Values are: internal or line. |
| Path Code Violations | Path coding violation (PCV) error event is a frame synchronization bit error in the D4 and E1-noCRC formats or a CRC error in the ESF and E1-CRC formats. |
| Slip Secs | Controlled slip second (CSS) is a one-second interval containing one or more controlled slips. |
| Fr Loss Secs | Frame loss seconds (SELS) is 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 | Degraded minute (DM) is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3. For more information, refer to RFC 1406. |
| Errored Secs | Errored seconds (ES) is a second with one or more path coding violations, one or more Out of Frame defects, or one or more controlled slip events or a detected AIS defect. |
| Bursty Err Secs | Bursty errored seconds (BES) is a second with fewer than 320 and more than one path coding violation error events, no Severely Errored Frame defects, and no detected incoming AIS defects. Controlled slips are not included in this parameter. |
| Severely Err Secs | Severely errored seconds (SES) is a second with 320 or more path code violation errors events, one or more Out of Frame defects, or a detected AIS defect. |
| Stuffed Secs | Stuffed seconds (SS) is a second in which one more bit stuffings take place. This happens when the Pulse Density Enforcer detects a potential violation in the output stream and inserts a 1 to prevent it. Such bit stuffings corrupt user data and indicate the network is misconfigured. This counter can be used to help diagnose this situation. |
To display information about memory management and error counters on the Token Ring Interface Processor (TRIP) for the Cisco 7500 series, use the show controllers token privileged EXEC command.
show controllers tokenThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
Depending on the card being used, the output can vary. This command also displays information that is proprietary to Cisco Systems. Thus, the information that show controllers token displays is of primary use to Cisco technical personnel. Information that is useful to users can be obtained with the show interfaces tokenring command, which is described later in this chapter.
Sample output for the show controllers token command on the Cisco 7500 follows:
Router> show controllers token
Tokenring4/0: state administratively down
current address: 0000.3040.8b4a, burned in address: 0000.3040.8b4a
Last Ring Status: none
Stats: soft: 0/0, hard: 0/0, sig loss: 0/0
tx beacon: 0/0, wire fault 0/0, recovery: 0/0
only station: 0/0, remote removal: 0/0
Monitor state: (active), chip f/w: '000000........', [bridge capable]
ring mode: 0"
internal functional: 00000000 (00000000), group: 00000000 (00000000)
internal addrs: SRB: 0000, ARB: 0000, EXB 0000, MFB: 0000
Rev: 0000, Adapter: 0000, Parms 0000
Microcode counters:
MAC giants 0/0, MAC ignored 0/0
Input runts 0/0, giants 0/0, overrun 0/0
Input ignored 0/0, parity 0/0, RFED 0/0
Input REDI 0/0, null rcp 0/0, recovered rcp 0/0
Input implicit abort 0/0, explicit abort 0/0
Output underrun 0/0, tx parity 0/0, null tcp 0/0
Output SFED 0/0, SEDI 0/0, abort 0/0
Output False Token 0/0, PTT Expired 0/0
Internal controller counts:
line errors: 0/0, internal errors: 0/0
burst errors: 0/0, ari/fci errors: 0/0
abort errors: 0/0, lost frame: 0/0
copy errors: 0/0, rcvr congestion: 0/0
token errors: 0/0, frequency errors: 0/0
Internal controller smt state:
Adapter MAC: 0000.0000.0000, Physical drop: 00000000
NAUN Address: 0000.0000.0000, NAUN drop: 00000000
Last source: 0000.0000.0000, Last poll: 0000.0000.0000
Last MVID: 0000, Last attn code: 0000
Txmit priority: 0000, Auth Class: 0000
Monitor Error: 0000, Interface Errors: 0000
Correlator: 0000, Soft Error Timer: 0000
Local Ring: 0000, Ring Status: 0000
Beacon rcv type: 0000, Beacon txmit type: 0000
Beacon type: 0000, Beacon NAUN: 0000.0000.0000
Beacon drop: 00000000, Reserved: 0000
Reserved2: 0000
Table 41 describes key show controllers token display fields.
| Field | Description |
|---|---|
| Tokenring4/0 | Interface processor type, slot, and port. |
| Last Ring Status | Last abnormal ring condition. Can be any of the following:
|
You can use the master indexes or search online to find documentation of related commands.
show interfaces tokenring
show source bridge
Use the show controllers vg-anylan user EXEC command to display the controller information for the 100VG-AnyLAN port adapter on Cisco 7200 series routers and Cisco 7500 series routers.
show controllers vg-anylan slot/port-adapter/port (on VIP cards in Cisco 7500 series)| slot | Refer to the appropriate hardware manual for slot and port information. |
| port-adapter | Refer to the appropriate hardware manual for information about port adapter compatibility. |
| port | Refer to the appropriate hardware manual for slot and port information. |
User EXEC
This command first appeared in Cisco IOS Release 11.3.
The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
The following is sample output from the show controllers vg-anylan command:
Router# show controllers vg-anylan 3/0
Interface VG-AnyLAN3/0
Hardware is MC68852
mc68852_ds=0x60A4C930, registers=0x3C300000, ib=0x4B056240
rx ring entries=31, tx ring entries=31
rxring=0x4B056340, rxr shadow=0x60A4CA08, rx_head=0, rx_tail=0
txring=0x4B057180, txr shadow=0x60A4D07C, tx_head=0, tx_tail=2,
tx_count=2,
MC68852 Registers:
hw_id: 5048, hw_id & page: 7053, opr1=0x26, opr2=0x2C, opr3=0x00
Page 0 - Performance:
isr=0x3400, imr=0x0A0A, flreg=0x0000
xfrct=0xC07E0080, rxcnt=0, txcnt=1F
Page 1 - MAC Address/Hash Table:
addrlow= 6009B9, addrhigh=9B1809B9,hash bytes=06 00 20 00 00 00 00 00
Page 2 - Hardware Mapping:
mmmsw=0x3785, mmlsw=0x0000, bmreg =0x04
Page 4 - LAN Configuration:
tccnf1=0x00, tccnf2=0x01
vccnf=0x99, vtrrg=0x0020, valow1=0x0000, valow2=0x0000
maccr1=0xBE, maccr2=0x00, maccr3=0x04, maccr4=0x03
Page 5 - MMU Registers:
rx mem stop addr=0xFF03, tx mem stop addr=0xFF07
MC68852 PCI registers:
bus_no=6, device_no=0
CFID=0x0005101A, CFCS=0x02800005, CFRV=0x02000000, CFLT=0x0000F800
CBIO=0x00006001, CBMA=0x00000000, CFIT=0x20080100, CFDA=0x0000000C
Actel Hardware CAM Control Registers:
CAM DEVICE BASE: 0x3C300800 Register Address: 0x3C300C00
CSR: 0x8000 CAMCR: 0xFFFF
USAR: 0000 MSAR: 0000 LSAR: 0000
FIFOCR: 0x8000 WRMASK: 0x0080
COMPARAND REG: 0000.0000.0000
PERSISTENT SOURCE: 0x0 PERSISTENT DEST: 0xFD010000
ACTEL CAM PCI registers:
bus_no=6, device_no=1
CFID=0x555511AA, CFCS=0x04800003, CFRV=0xF0F0F001, CFLT=0x00000000
CBIO=0x00006800, CBMA=0x00000000, CFIT=0x00000000, CFDA=0x00000000
pak_to_host=0x0, filtered_pak=0
throttled=0, enabled=0, disabled=0
tx_carrier_loss=0
fatal_tx_err=0, mult_ovfl=0
Use the show diagbus privileged EXEC command to display diagnostic information about the controller, interface processor, and port adapters associated with a specified slot of a Cisco 7200 series or Cisco 7500 series router.
show diagbus [slot]| slot | Refer to the appropriate hardware manual for slot and port information. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output for the Cisco 7513 with a VIP2 interface processor board in slot 8. This card has two 4-port Token Ring port adapters located in port adapter bays 0 and 1.
Router# show diagbus 8
Slot 8:
Physical slot 8, ~physical slot 0x7, logical slot 8, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP2 controller, HW rev 2.2, board revision UNKNOWN
Serial number: 03341418 Part number: 73-1684-02
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 15 02 02 00 32 FC 6A 49 06 94 02 00 00 00 00
0x30: 07 2B 00 2A 1A 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x3188 (01:20:53 ago)
Controller Memory Size: 8 MBytes
PA Bay 0 Information:
Token Ring PA, 4 ports
EEPROM format version 1
HW rev 1.1, Board revision 0
Serial number: 02827613 Part number: 73-1390-04
PA Bay 1 Information:
Token Ring PA, 4 ports
EEPROM format version 1
HW rev 1.1, Board revision 88
Serial number: 02023786 Part number: 73-1390-04
The following is sample output from the show diagbus command for the Ethernet interface in slot 2 on a Cisco 7200 series router:
Router# show diagbus 2
Slot 2:
Ethernet port adapter, 8 ports
Port adapter is analyzed
Port adapter insertion time 1d18h ago
Hardware revision 1.0 Board revision K0
Serial number 2023387 Part number 73-1391-03
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 01 01 00 00 1E DF DB 49 05 6F 03 00 00 00 00
0x30: A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
To display information about the hub (repeater) on an Ethernet interface of a Cisco 2505 or Cisco 2507, use the show hub EXEC command.
show hub [ethernet number [port [end-port]]]| ethernet | (Optional) Indicates that this is an Ethernet hub. |
| number | (Optional) Hub number, starting with 0. Since there is currently only one hub, this number is 0. |
| port | (Optional) Port number on the hub. On the Cisco 2505, port numbers range from 1 through 8. On the Cisco 2507, port numbers range from 1 through 16. If a second port number follows, then this port number indicates the beginning of a port range. |
| end-port | (Optional) Ending port number of a range. |
EXEC
This command first appeared in Cisco IOS Release 10.3.
If you do not specify a port or port range for the show hub command, the command displays all ports (for example, ports 1 through 16 on a Cisco 2507) by default. Therefore, the commands show hub, show hub ethernet 0, and show hub ethernet 0 1 16 all produce the same result.
If no ports are specified, the command displays some additional data about the internal port. The internal port is the hub's connection to Ethernet interface 0 inside the box. Ethernet interface 0 still exists; physical access to the interface is via the hub.
The following is sample output from the show hub command for hub 0, port 2 only:
Router# show hub ethernet 0 2
Port 2 of 16 is administratively down, link state is down
0 packets input, 0 bytes
0 errors with 0 collisions
(0 FCS, 0 alignment, 0 too long,
0 short, 0 runts, 0 late,
0 very long, 0 rate mismatches)
0 auto partitions, last source address (none)
Last clearing of "show hub" counters never
Repeater information (Connected to Ethernet0)
2792429 bytes seen with 18 collisions, 1 hub resets
Version/device ID 0/1 (0/1)
Last clearing of "show hub" counters never
The following is sample output from the show hub command for hub 0, all ports:
Router# show hub ethernet 0
Port 1 of 16 is administratively down, link state is up
2458 packets input, 181443 bytes
3 errors with 18 collisions
(0 FCS, 0 alignment, 0 too long,
0 short, 3 runts, 0 late,
0 very long, 0 rate mismatches)
0 auto partitions, last source address was 0000.0cff.e257
Last clearing of "show hub" counters never
.
.
.
Port 16 of 16 is down, link state is down
0 packets input, 0 bytes
0 errors with 0 collisions
(0 FCS, 0 alignment, 0 too long,
0 short, 0 runts, 0 late,
0 very long, 0 rate mismatches)
0 auto partitions, last source address (none)
Last clearing of "show hub" counters never
Repeater information (Connected to Ethernet0)
2792429 bytes seen with 18 collisions, 1 hub resets
Version/device ID 0/1 (0/1)
Last clearing of "show hub" counters never
Internal Port (Connected to Ethernet0)
36792 packets input, 4349525 bytes
0 errors with 14 collisions
(0 FCS, 0 alignment, 0 too long,
0 short, 0 runts, 0 late,
0 very long, 0 rate mismatches)
0 auto partitions, last source address (none)
Last clearing of "show hub" counters never
Table 42 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Port ... of ... is administratively down | Port number out of total ports; indicates whether the interface hardware is currently active, or down due to the following:
|
|
link state is up | Indicates whether port has been disabled by the link-test function. If the link-test function is disabled by the user, nothing will be shown here. |
| 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. |
| errors | Sum of FCS, alignment, too long, short, runts, very long, and rate mismatches. |
| collisions | Number of messages retransmitted due to Ethernet collisions. |
| FCS | Counter for the number of frames detected on the port with an invalid frame check sequence. |
| alignment | Counter for the number of frames of valid length (64 bytes to 1518 bytes) that have been detected on the port with an FCS error and a framing error. |
| too long | Counter for the number of frames that exceed the maximum valid packet length of 1518 bytes. |
| short | Counter for the number of instances when activity is detected with duration less than 74-82 bit times. |
| runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. For example, any Ethernet packet that is less than 64 bytes is considered a runt. |
| late | Counter for the number of instances when a collision is detected after 480-565 bit times in the frame. |
| very long | Counter for the number of times the transmitter is active in excess of 4 ms to 7.5 ms. |
| rate mismatches | Counter for the number of occurrences when the frequency, or data rate of incoming signal is noticably different from the local transmit frequency. |
| auto partitions | Counter for the number of instances where the repeater has partitioned the port from the network. |
| last source address | Source address of last packet received by this port. Indicates "none" if no packets have been received since power on or a hub reset. |
| Last clearing of "show hub" counters | Elapsed time since clear hub counters command. Indicates "never" if counters have never been cleared. |
| Repeater information (Connected to Ethernet0) | Indicates that the following information is about the hub connected to the Ethernet interface shown. |
| ... bytes seen with ... collisions, ... hub resets | Hub resets is the number of times the hub has been reset by network management software or by the clear hub command. |
| Version/device ID 0/1 (0/1) | Hub hardware version. IMR+ version device of daughter board. |
| Internal Port (Connected to Ethernet0) | Set of counters for the internal AUI port connected to the Ethernet interface. |
You can use the master indexes or search online to find documentation of related commands.
hub
|
|