Table Of Contents
show interfaces
show interfaces content-engine
show interfaces ctunnel
show interfaces ethernet
show interfaces fastethernet
show interfaces fddi
show interfaces gigabitethernet
show interfaces hssi
show interfaces loopback
show interfaces port-channel
show interfaces pos
show interfaces serial
show interfaces tokenring
show interfaces tunnel
show interfaces vg-anylan
show ipc
show ip interface
show ipc hog-info
show pas caim
show pas eswitch address
show pas isa controller
show pas isa interface
show pas vam controller
show pas vam interface
show pci aim
show power inline
show redundancy
show redundancy interlink
show service-module serial
show smf
show storm-control
show syscon sdp
show tdm backplane
show tdm connections
show tdm data
show tdm detail
show tdm information
show tdm pool
shutdown (controller)
shutdown (hub)
shutdown (interface)
smt-queue-threshold
snmp ifindex clear
snmp ifindex persist
snmp trap illegal-address
snmp-server ifindex persist
source-address
speed
squelch
srp buffer-size
srp deficit-round-robin
srp loopback
srp priority-map
srp random-detect
srp shutdown
srp tx-traffic-rate
storm-control
switchport mode
switchport trunk
switchport voice vlan
syscon address
syscon shelf-id
syscon source-interface
show interfaces
To display statistics for all interfaces configured on the router or access server, use the show interfaces command in privileged EXEC mode. The resulting output varies, depending on the network for which an interface has been configured.
Cisco 2500 Series, Cisco 2600 Series, Cisco 4700 Series, and Cisco 7000 Series
show interfaces [type number] [first] [last] [accounting]
Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor
show interfaces [type slot/port] [accounting]
Cisco 7500 Series with Ports on VIPs
show interfaces [type slot/port-adapter/port]
Syntax Description
type
|
(Optional) Interface type. Allowed values for type include async, bri0, dialer, ethernet, fastethernet, fddi, hssi, loopback, null, serial, tokenring, and tunnel.
For the Cisco 4500 series routers, type can be atm, e1, ethernet, fastethernet, fddi, serial, t1, and token..
For the Cisco 7000 family, type can be atm, e1, ethernet, fastethernet, fddi, serial, t1, and tokenring. For the Cisco 7500 series type can also include pos.
|
number
|
(Optional) Port number on the selected interface.
|
first last
|
(Optional) For the Cisco 2500 series routers, ISDN BRI only. The first argument can be either 1 or 2. The last argument can only be 2, indicating B channels 1 and 2.
D-channel information is obtained by using the command without the optional arguments.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot information.
|
/port
|
(Optional) Port number. Refer to the appropriate hardware manual for port information.
|
/port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(3)T
|
This command was modified to include support for flow-based WRED.
|
12.0(4)T
|
This command was modified to include enhanced display information for dialer bound interfaces.
|
12.0(7)T
|
This command was modified to include dialer as an interface type and to reflect the default behavior.
|
Usage Guidelines
Display Interpretation
The show interfaces command displays statistics for the network interfaces. The resulting display on the Cisco 7200 series routers shows the interface processors in slot order. If you add interface processors after booting the system, they will appear at the end of the list, in the order in which they were inserted.
Information About Specific Interfaces
If you use the show interfaces command on the Cisco 7200 series routers without the slot/port arguments, information for all interface types will be shown. For example, if you type show interfaces ethernet you will receive information for all ethernet, serial, Token Ring, and FDDI interfaces. Only by adding the type slot/port argument can you specify a particular interface.
Removed Interfaces
If you enter a show interfaces command for an interface type that has been removed from the router or access server, interface statistics will be displayed accompanied by the following text: "Hardware has been removed."
Weighted Fair Queueing Information
If you use the show interfaces command on a router or access server for which interfaces are configured to use weighted fair queueing through the fair-queue interface command, additional information is displayed. This information consists of the current and high-water mark number of flows.
Accounting Information
The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.
Dialer Interfaces Configured for Binding
If you use the show interfaces command on dialer interfaces configured for binding, the display will report statistics on each physical interface bound to the dialer interface; see the following examples for more information.
Command Variations
You will use the show interfaces command frequently while configuring and monitoring devices. The various forms of the show interfaces commands are described in detail in the sections that follow.
Examples
The following is sample output from the show interfaces command. Because your display will depend on the type and number of interface cards in your router or access server, only a portion of the display is shown.
Note 
If an asterisk (*) appears after the throttles counter value, it means that the interface was throttled at the time the command was run.
Ethernet 0 is up, line protocol is up
Hardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)
Internet address is 10.108.28.8, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:00:00, output 0:00:00, output hang never
Last clearing of "show interface" counters 0:00:00
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 2000 bits/sec, 4 packets/sec
1127576 packets input, 447251251 bytes, 0 no buffer
Received 354125 broadcasts, 0 runts, 0 giants, 57186* throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5332142 packets output, 496316039 bytes, 0 underruns
0 output errors, 432 collisions, 0 interface resets, 0 restarts
Example with Custom Output Queueing
The following shows partial sample output when custom output queueing is enabled:
Last clearing of "show interface" counters 0:00:06
Input queue: 0/75/0 (size/max/drops); Total output drops: 21
Output queues: (queue #: size/max/drops)
0: 14/20/14 1: 0/20/6 2: 0/20/0 3: 0/20/0 4: 0/20/0 5: 0/20/0
6: 0/20/0 7: 0/20/0 8: 0/20/0 9: 0/20/0 10: 0/20/0
When custom queueing is enabled, the drops accounted for in the output queues result from bandwidth limitation for the associated traffic and leads to queue length overflow. Total output drops include drops on all custom queues as well as the system queue. Fields are described with the Weighted Fair Queueing output in Table 39.
Example Including Weighted-Fair-Queueing Output
For each interface on the router or access server configured to use weighted fair queueing, the show interfaces command displays the information beginning with Input queue: in the following display:
Ethernet 0 is up, line protocol is up
Hardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)
Internet address is 10.108.28.8, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:00:00, output 0:00:00, output hang never
Last clearing of "show interface" counters 0:00:00
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 2000 bits/sec, 4 packets/sec
1127576 packets input, 447251251 bytes, 0 no buffer
Received 354125 broadcasts, 0 runts, 0 giants, 57186* throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5332142 packets output, 496316039 bytes, 0 underruns
0 output errors, 432 collisions, 0 interface resets, 0 restarts
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Output queue: 7/64/0 (size/threshold/drops)
Conversations 2/9 (active/max active)
Table 39 describes the input queue and output queue fields shown in the preceding two displays.
Table 39 Weighted-Fair-Queueing Output Field Descriptions
Field
|
Description
|
Input queue:
|
•size
|
Current size of the input queue.
|
•max
|
Maximum size of the queue.
|
•drops
|
Number of messages discarded in this interval.
|
•Total output drops
|
Total number of messages discarded in this session.
|
Output queue:
|
•size
|
Current size of the output queue.
|
•threshold
|
Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped.
|
•drops
|
Number of dropped messages.
|
•Conversations: active
|
Number of currently active conversations.
|
•Conversations: max active
|
Maximum number of concurrent conversations allowed.
|
Example with Accounting Option
To display the number of packets of each protocol type that have been sent through all configured interfaces, use the show interfaces accounting EXEC command. When you use the accounting option, only the accounting statistics are displayed.
Note Except for protocols that are encapsulated inside other protocols, such as IP over X.25, the accounting option also shows the total of all bytes sent and received, including the MAC header. For example, it totals the size of the Ethernet packet or the size of a packet that includes High-Level Data Link Control (HDLC) encapsulation.
Per-packet accounting information is displayed for protocols. The following is an example of protocols for which accounting information is displayed. This list is not inclusive of all protocols and could vary among platforms.
•Apollo
•AppleTalk
•ARP (for IP, Apollo, Frame Relay, SMDS)
•CLNS
•DEC MOP
The routers use MOP packets to advertise their existence to Digital Equipment Corporation machines that use the MOP protocol. A router periodically broadcasts MOP packets to identify itself as a MOP host. This results in MOP packets being counted, even when DECnet is not being actively used.
•DECnet
•IP
•LAN Manager (LAN Network Manager and IBM Network Manager)
•Novell
•Serial Tunnel (SDLC)
•Spanning Tree
•SR Bridge
•Transparent Bridge
•VINES
•XNS
The following is sample output from the show interfaces accounting command:
Router# show interfaces accounting
Interface TokenRing0 is disabled
Protocol Pkts In Chars In Pkts Out Chars Out
IP 873171 735923409 34624 9644258
Novell 163849 12361626 57143 4272468
ARP 69618 4177080 1529 91740
Interface Serial0 is disabled
Protocol Pkts In Chars In Pkts Out Chars Out
Interface Serial1 is disabled
Interface Ethernet2 is disabled
Interface Serial2 is disabled
Interface Ethernet3 is disabled
Interface Serial3 is disabled
Interface Ethernet4 is disabled
Interface Ethernet5 is disabled
Interface Ethernet6 is disabled
Interface Ethernet7 is disabled
Interface Ethernet8 is disabled
Interface Ethernet9 is disabled
Protocol Pkts In Chars In Pkts Out Chars Out
When the output indicates an interface is "disabled," the router has received excessive errors (over 5000 in a keepalive period).
The following is sample output from the show interfaces accounting command when a switched packet is dropped:
Router# show interfaces accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 37342 21789327 954 86850
Interface FastEthernet1/0 is disabled
Interface FastEthernet1/1 is disabled
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface
Table 40 describes the fields shown in the display.
Table 40 show interfaces accounting Field Descriptions
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
Example with DWRED
The following is sample output from the show interfaces command when distributed weighted RED (DWRED) is enabled on an interface. Notice that the packet drop strategy is listed as "VIP-based weighted RED."
Router# show interfaces hssi 0/0/0
Hssi0/0/0 is up, line protocol is up
Description: 45Mbps to R1
Internet address is 10.200.14.250/30
MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 00:00:02, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Packet Drop strategy: VIP-based weighted RED
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1976 packets input, 131263 bytes, 0 no buffer
Received 1577 broadcasts, 0 runts, 0 giants
4 input errors, 4 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1939 packets output, 130910 bytes, 0 underruns
0 output errors, 0 applique, 3 interface resets
0 output buffers copied, 0 interrupts, 0 failures
Example with ALC
The following is sample output from the show interfaces command for serial interface 2 when ALC is enabled:
Router# show interfaces serial 2
Serial2 is up, line protocol is up
MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation ALC, loopback not set
ascus in UP state: 42, 46
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
DCD=down DSR=down DTR=down RTS=down CTS=down
Example with SDLC
The following is sample output from the show interfaces command for a Synchronous Data Link Control (SDLC) primary interface supporting the SDLC function:
Serial 0 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC-PRIMARY, loopback not set
Timers (msec): poll pause 100 fair poll 500. Poll limit 1
[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
largest token ring frame 2052]
SDLC addr C1 state is CONNECT
VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
Poll: clear, Poll count: 0, chain: p: C1 n: C1
SDLLC [largest SDLC frame: 265, XID: disabled]
Last input 00:00:02, output 00:00:01, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 517 bits/sec, 30 packets/sec
Five minute output rate 672 bits/sec, 20 packets/sec
357 packets input, 28382 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
926 packets output, 77274 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Table 41 shows the fields relevant to all SDLC connections.
Table 41 show interfaces Field Descriptions When SDLC Is Enabled
Field
|
Description
|
Timers (msec)
|
List of timers in milliseconds.
|
poll pause, fair poll, Poll limit
|
Current values of these timers, as described in the individual commands in this chapter.
|
T1, N1, N2, K
|
Current values for these variables, as described in the individual commands in this chapter.
|
Table 42 shows other data given for each SDLC secondary interface configured to be attached to this interface.
Table 42 SDLC Field Descriptions
Field
|
Description
|
addr
|
Address of this secondary interface.
|
State
|
Current state of this connection. The possible values follow:
•DISCONNECT—No communication is being attempted to this secondary.
•CONNECT—A normal connect state exists between this router and this secondary.
•DISCSENT—This router has sent a disconnect request to this secondary and is awaiting its response.
•SNRMSENT—This router has sent a connect request (SNRM) to this secondary and is awaiting its response.
•THEMBUSY—This secondary has told this router that it is temporarily unable to receive any more information frames.
•USBUSY—This router has told this secondary that it is temporarily unable to receive any more information frames.
•BOTHBUSY—Both sides have told each other that they are temporarily unable to receive any more information frames.
•ERROR—This router has detected an error, and is waiting for a response from the secondary acknowledging this.
|
VS
|
Sequence number of the next information frame this station sends.
|
VR
|
Sequence number of the next information frame from this secondary that this station expects to receive.
|
RCNT
|
Number of correctly sequenced I-frames received when the Cisco IOS software was in a state in which it is acceptable to receive I-frames.
|
Remote VR
|
Last frame transmitted by this station that has been acknowledged by the other station.
|
Current retransmit count
|
Number of times the current I-frame or sequence of I-frames has been retransmitted.
|
Hold queue
|
Number of frames in hold queue/Maximum size of hold queue.
|
IFRAMEs, RNRs, SNRMs, DISCs
|
Sent/received count for these frames.
|
Poll
|
"Set" if this router has a poll outstanding to the secondary; "clear" if it does not.
|
Poll count
|
Number of polls, in a row, given to this secondary at this time.
|
chain
|
Shows the previous (p) and next (n) secondary address on this interface in the round robin loop of polled devices.
|
Example with Flow-Based WRED
The following is sample output from the show interfaces command issued for the Serial interface 1 for which flow-based weighted RED (WRED) is enabled. The output shows that there are 8 active flow-based WRED flows, that the maximum number of flows active at any time is 9, and that the maximum number of possible flows configured for the interface is 16:
Router# show interfaces serial 1
Serial1 is up, line protocol is up
Internet address is 10.1.2.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
Reliability 255/255, txload 237/255, rxload 1/255
Encapsulation HDLC, loopback not set
Last input 00:00:22, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:17:58
Input queue: 0/75/0 (size/max/drops); Total output drops: 2479
Queueing strategy: random early detection(RED)
flows (active/max active/max): 8/9/16
drops: class random tail min-th max-th mark-prob
30 second input rate 1000 bits/sec, 2 packets/sec
30 second output rate 119000 bits/sec, 126 packets/sec
1346 packets input, 83808 bytes, 0 no buffer
Received 12 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
84543 packets output, 9977642 bytes, 0 underruns
0 output errors, 0 collisions, 6 interface resets
0 output buffer failures, 0 output buffers swapped out
DCD=up DSR=up DTR=up RTS=up CTS=up
Example with DWFQ
The following is sample output from the show interfaces command when distributed weighted fair queueing (DWFQ) is enabled on an interface. Notice that the queueing strategy is listed as "VIP-based fair queueing."
Router# show interfaces fastethernet 1/1/0
Fast Ethernet 1/1/0 is up, line protocol is up
Hardware is cyBus Fast Ethernet Interface, address is 0007.f618.4448 (bia 00e0)
Description: pkt input i/f for WRL tests (to pagent)
Internet address is 10.0.2.70/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set, fdx, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 01:11:01, output hang never
Last clearing of "show interface" counters 01:12:31
Queueing strategy: VIP-based fair queueing
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
1 packets output, 60 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffers copied, 0 interrupts, 0 failures
Example with DNIS Binding
When the show interfaces command is issued on an unbound dialer interface, the output looks as follows:
Router# show interfaces dialer0
Dialer0 is up (spoofing), line protocol is up (spoofing)
Internet address is 10.1.1.2/8
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 3/255
Encapsulation PPP, loopback not set
DTR is pulsed for 1 seconds on reset
Last input 00:00:34, output never, output hang never
Last clearing of "show interface" counters 00:05:09
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 0 packets/sec
18 packets input, 2579 bytes
14 packets output, 5328 bytes
But when the show interfaces command is issued on a bound dialer interface, you will get an additional report that indicates the binding relationship. The output is shown here:
Router# show interfaces dialer0
Dialer0 is up, line protocol is up
Internet address is 10.1.1.2/8
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set
DTR is pulsed for 1 seconds on reset
Interface is bound to BRI0:1
Last input 00:00:38, output never, output hang never
Last clearing of "show interface" counters 00:05:36
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
38 packets input, 4659 bytes
34 packets output, 9952 bytes
BRI0:1 is up, line protocol is up
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
Interface is bound to Dialer0 (Encapsulation PPP)
Last input 00:00:39, output 00:00:11, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
78 packets input, 9317 bytes, 0 no buffer
Received 65 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
93 packets output, 9864 bytes, 0 underruns
0 output errors, 0 collisions, 7 interface resets
0 output buffer failures, 0 output buffers swapped out
At the end of the Dialer0 output, the show interfaces command is executed on each physical interface bound to it.
Example with BRI
In this example, the physical interface is the B1 channel of the BRI0 link. This example also illustrates that the output under the B channel keeps all hardware counts that are not displayed under any logical or virtual access interface. The line in the report that states "Interface is bound to Dialer0 (Encapsulation LAPB)" indicates that this B interface is bound to Dialer0 and the encapsulation running over this connection is LAPB, not PPP, which is the encapsulation configured on the D interface and inherited by the B channel.
Router# show interfaces bri0:1
BRI0:1 is up, line protocol is up
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
Interface is bound to Dialer0 (Encapsulation LAPB)
Last input 00:00:31, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
110 packets input, 13994 bytes, 0 no buffer
Received 91 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
135 packets output, 14175 bytes, 0 underruns
0 output errors, 0 collisions, 12 interface resets
0 output buffer failures, 0 output buffers swapped out
Any protocol configuration and states should be displayed from the Dialer0 interface.
show interfaces content-engine
To display basic interface configuration information for a content engine (CE) network module, use the show interfaces content-engine command in privileged EXEC mode.
show interfaces content-engine slot/unit
Syntax Description
slot
|
Number of the router chassis slot for the network module.
|
unit
|
Number of the daughter card on the network module. For CE network modules, always use 0.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(11)YT
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
The output for this command contains the basic configuration for the interface, as well as the number of packets transmitted, output rate, and so forth.
Examples
The following example displays interface status and data for the CE network module in slot 1 for Cisco 2600 series routers (except the Cisco 2691). Note that the bandwidth is 10 Mbps.
Router# show interfaces content-engine 1/0
Content-Engine1/0 is up, line protocol is up
Hardware is I82559FE, address is 0006.280e.10b0 (bia 0006.280e.10b0)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:50, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
13 packets input, 5835 bytes, 0 no buffer
Received 13 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
71 packets output, 6285 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
The following example displays interface status and data for a CE network module in slot 3 of a Cisco 2691. This example shows the 100-Mbps bandwidth of a Cisco 2691 and all the other supported routers except the remainder of the Cisco 2600 series.
Router# show interfaces content-engine 3/0
Content-Engine3/0 is up, line protocol is up
Hardware is I82559FE, address is 0004.9a0b.4b30 (bia 0004.9a0b.4b30)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:41, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
14 packets input, 6176 bytes, 0 no buffer
Received 14 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
109 packets output, 16881 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Table 43 describes the significant fields shown in the display.
Table 43 show interfaces content-engine Field Descriptions
Field
|
Description
|
Content-Engine
|
Indicates whether the CE interface hardware is currently active. If the CE interface hardware is operational, the output states that "Content-Engine slot/port is up." If it has been taken down by an administrator, the output states that "Content-Engine slot/port is administratively down."
|
line protocol
|
Indicates whether the software processes that handle the line protocol consider the line usable or whether the line has been taken down by an administrator.
|
Hardware...address
|
Hardware type and address.
|
MTU
|
Maximum transmission unit (MTU) of the content engine interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
reliability
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
txload
|
Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
rxload
|
Receive load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to the interface.
|
loopback
|
Indicates whether loopback is set.
|
Keepalive
|
Indicates whether keepalives are set and the interval between keepalives if they have been set.
|
ARP type...Timeout
|
Type of Address Resolution Protocol (ARP) assigned and length of timeout.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by the interface and processed locally on the router. This field is useful for detecting when a dead interface failed.
Note This field is not updated by fast-switched traffic.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. This field is useful for detecting when a dead interface failed.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because a transmission took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
Asterisks (***) indicate that the elapsed time is too large to be displayed.
A time of all zeroes (0:00:00) indicates that the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Input queue
|
Number of packets in the input queue. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Total output drops
|
Number of packets in the output queue that have been dropped because of a full queue.
|
Queueing strategy
|
Queueing strategy applied to the interface, which is configurable under the interface. The default is FIFO.
|
Output queue
|
Number of packets in the output queue. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate,
5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic that it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within 2 percent of the instantaneous rate of a uniform stream of traffic over that period.
Note The 5-minute period referenced in this output is a load interval that is configurable under the interface. The default value is 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received...broadcasts
|
Number of broadcasts received.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
|
throttles
|
Number of times that the interface requested another interface within the router to slow down.
|
input errors
|
Errors that include runts, giants, no buffer, cyclic redundancy check (CRC), frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
|
CRC
|
Errors created when the CRC generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station that is transmitting bad data.
|
frame
|
Number of packets received incorrectly that have a CRC error and a non integer number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
|
overrun
|
Number of times that the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets that were ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from system buffer space described. Broadcast storms and bursts of noise can cause the ignored count to increase.
|
input packets with dribble condition detected
|
Number of packets with dribble condition. Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages that have been transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, that have been transmitted by the system.
|
underruns
|
Number of times that the transmitter has run faster than the router could handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the content engine that is being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages that have been retransmitted because of an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets that were queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
babbles
|
Count of frames greater than 1518 bytes that have been transmitted, indicating that the transmitter has been on the interface longer than the time necessary to transmit the largest frame.
|
late collision
|
Number of late collisions. A collision becomes a late collision when it occurs after the preamble has been transmitted.
|
deferred
|
Deferred indicates that the chip, while ready to transmit a frame, had to defer because the carrier was asserted.
|
lost carrier
|
Number of times that the carrier was lost during transmission.
|
no carrier
|
Number of times that the carrier was not present during the transmission.
|
output buffer failures,
output buffers swapped out
|
Number of failed buffers and number of buffers swapped out.
|
Related Commands
Command
|
Description
|
interface content-engine
|
Configures an interface for a CE network module and enters interface configuration mode.
|
show controllers content-engine
|
Displays controller information for CE network modules.
|
show interfaces ctunnel
To display information about an IP over Connectionless Network service (CLNS) tunnel (CTunnel), use the show interfaces ctunnel command in privileged EXEC mode.
show interfaces ctunnel interface-number [accounting]
Syntax Description
interface-number
|
Virtual interface number.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
For the show interfaces ctunnel command, all output that relates to a physical medium is irrelevant and should be ignored because the CTunnel is a virtual interface.
Examples
The following is sample output from the show interfaces ctunnel command:
Router# show interfaces ctunnel 1
CTunnel1 is up, line protocol is up
Internet address is 10.0.0.1/24
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Tunnel destination 49.0001.2222.2222.2222.cc
Last input never, output 00:00:05, output hang never
Last clearing of "show interface" counters never
Output queue 0/0, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1 packets output, 104 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 44 describes the significant fields shown in the display.
Table 44 show interfaces ctunnel Field Descriptions
Field
|
Description
|
CTunnel is {up | down | administratively down}
|
Interface is currently active (up) or inactive (down). Shows interface is administratively down if disabled.
|
line protocol is {up | down}
|
Shows line protocol up if a valid route is available to the CLNS tunnel (CTunnel) destination. Shows line protocol down if no route is available, or if the route would be recursive.
|
Hardware
|
Type of interface, in this instance CTunnel.
|
Internet address
|
IP address of the interface.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth, as specified by the user, that is available on the link.
|
DLY
|
Delay of the interface, in microseconds.
|
Encapsulation
|
Encapsulation method is always TUNNEL for tunnels.
|
Loopback
|
Shows whether loopback is set or not.
|
Keepalive
|
Shows whether keepalives are set or not.
|
Tunnel destination
|
The NSAP address of the tunnel destination. The N-Selector part of the displayed NSAP address is set by the router and cannot be changed.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates that the elapsed time is too large to be displayed.
0:00:00 indicates that the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
Type of queueing active on this interface.
|
Output queue, drops
Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of 4 time constants must pass before the average will be within 2 percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no memory buffer available.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
This field does not apply to the CTunnel virtual interface.
|
giants
|
This field does not apply to the CTunnel virtual interface.
|
throttles
|
This field does not apply to the CTunnel virtual interface.
|
input errors
|
This field does not apply to the CTunnel virtual interface.
|
CRC
|
This field does not apply to the CTunnel virtual interface.
|
frame
|
This field does not apply to the CTunnel virtual interface.
|
overrun
|
This field does not apply to the CTunnel virtual interface.
|
ignored
|
This field does not apply to the CTunnel virtual interface.
|
abort
|
This field does not apply to the CTunnel virtual interface.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes transmitted by the system.
|
underruns
|
This field does not apply to the CTunnel virtual interface.
|
output errors
|
This field does not apply to the CTunnel virtual interface.
|
collisions
|
This field does not apply to the CTunnel virtual interface.
|
interface resets
|
Number of times an interface has been reset. The interface may be reset manually by the administrator or automatically by the system when an internal error occurs.
|
output buffer failures
|
Number of buffer failures.
|
output buffers swapped out
|
Number of output buffer allocation failures.
|
Related Commands
Command
|
Description
|
show interfaces
|
Displays the statistical information specific to interfaces.
|
show interfaces ethernet
To display information about an Ethernet interface on the router, use the show interfaces ethernet command in privileged EXEC mode.
Standard Syntax
show interfaces ethernet [number] [accounting]
Cisco 7200 and 7500 Series
show interfaces ethernet [slot/port] [accounting]
Cisco 7500 Series with Ports on VIPs
show interfaces ethernet [slot/port-adapter/port]
Syntax Description
number
|
(Optional) Port number on the selected interface.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
/port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
/port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
If you do not provide values for the number argument (or slot, port, and port-adapter arguments), the command displays statistics for all network interfaces. The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.
Examples
The following is sample output from the show interfaces ethernet command for Ethernet interface 0:
Router# show interfaces ethernet 0
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.3ef1.702b (bia 0060.3ef1.702b)
Internet address is 172.21.102.33/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:20, output 00:00:06, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
115331 packets input, 27282407 bytes, 0 no buffer
Received 93567 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
143782 packets output, 14482169 bytes, 0 underruns
0 output errors, 1 collisions, 5 interface resets
0 babbles, 0 late collision, 7 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Table 45 describes significant fields shown in the display.
Table 45 show interfaces ethernet Field Descriptions
Field
|
Description
|
Ethernet ... is up ... is administratively down
|
Indicates whether the interface hardware is currently active and if it has been taken down by an administrator. "Disabled" indicates the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default.
|
line protocol is {up | down | administratively down}
|
Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful) or if it has been taken down by an administrator.
|
Hardware
|
Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.
|
Internet address
|
Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
ARP type:
|
Type of Address Resolution Protocol assigned.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate,
5 minute output rate
|
Average number of bits and packets transmitted per second in the last five minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).
The five-minute input and output rates should be used only as an approximation of traffic per second during a given five-minute period. These rates are exponentially weighted averages with a time constant of five minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes input
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffers
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received ... broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
|
input error
|
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
|
overrun
|
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages transmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times a Type 2 Ethernet controller was restarted because of errors.
|
babbles
|
The transmit jabber timer expired.
|
late collision
|
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
|
deferred
|
Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
|
lost carrier
|
Number of times the carrier was lost during transmission.
|
no carrier
|
Number of times the carrier was not present during the transmission.
|
output buffer failures
|
Number of failed buffers and number of buffers swapped out.
|
Example on Cisco 7500 Series Routers
The following sample output illustrates the show interfaces ethernet command on a Cisco 7500 series router:
Router# show interfaces ethernet 4/2
Ethernet4/2 is up, line protocol is up
Hardware is cxBus Ethernet, address is 0000.0c02.d0ce (bia 0000.0c02.d0ce)
Internet address is 10.108.7.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:00:00, output 0:00:09, output hang never
Last clearing of "show interface" counters 0:56:40
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 3000 bits/sec, 4 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
4961 packets input, 715381 bytes, 0 no buffer
Received 2014 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
567 packets output, 224914 bytes, 0 underruns
0 output errors, 168 collisions, 0 interface resets, 0 restarts
0 babbles, 2 late collision, 7 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Example with Accounting Option
The following is sample output from the show interfaces ethernet command with the accounting option on a Cisco 7500 series router:
Router# show interfaces ethernet 4/2 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 7344 4787842 1803 1535774
Appletalk 33345 4797459 12781 1089695
Table 46 describes the fields shown in the display.
Table 46 show interfaces ethernet Field Descriptions—Accounting
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
show interfaces fastethernet
To display information about the Fast Ethernet interfaces, use the show interfaces fastethernet command in user EXEC or privileged EXEC mode.
Standard Syntax
show interfaces fastethernet [number]
Cisco 7200 and Cisco 7500 Series
show interfaces fastethernet [slot/port]
Cisco 7500 Series with a VIP
show interfaces fastethernet [slot/port-adapter/port]
Syntax Description
number
|
(Optional) Port, connector, or interface card number. On a Cisco 4700 series routers, specifies the network interface module (NIM) or NPM number. The numbers are assigned at the factory at the time of installation or when added to a system.
|
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Examples
The following is sample output from the show interfaces fastethernet command on a Cisco 4700 series router:
Router# show interfaces fastethernet 0
Fast Ethernet0 is up, line protocol is up
Hardware is DEC21140, address is 0000.0c0c.1111 (bia 0002.eaa3.5a60)
Internet address is 10.0.0.1 255.0.0.0
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set, hdx, 100BaseTX
ARP type: ARPA, ARP Timeout 4:00:00
Last input never, output 0:00:16, output hang 0:28:01
Last clearing of "show interface" counters 0:20:05
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 1786161921 ignored, 0 abort
0 input packets with dribble condition detected
67 packets output, 8151 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets, 0 restarts
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
The following is sample output from the show interfaces fastethernet command on a Cisco AS5300 access server:
Router# show interfaces fastethernet 0
Fast Ethernet0 is up, line protocol is up
Hardware is DEC21140AD, address is 00e0.1e3e.c179 (bia 00e0.1e3e.c179)
Internet address is 10.17.30.4/16
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
Half-duplex, 10Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/120, 8 drops
5 minute input rate 2000 bits/sec, 3 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
158773 packets input, 17362631 bytes, 4 no buffer
Received 158781 broadcasts, 0 runts, 0 giants, 7 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
6299 packets output, 622530 bytes, 0 underruns
1 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 1 no carrier
0 output buffer failures, 0 output buffers swapped out
The following shows information specific to the first Fast Ethernet Interface Processor (FEIP) port in slot 0 on a Cisco 7500 series router:
Router# show interfaces fastethernet 0/1
Fast Ethernet0/1 is administratively down, line protocol is down
Hardware is cxBus Fast Ethernet, address is 0000.0c35.dc16 (bia 0000.0c35.dc16)
Internet address is 10.1.0.64 255.255.0.0
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set, half-duplex, RJ45 (or MII)
ARP type: ARPA, ARP Timeout 4:00:00
Last input never, output 2:03:52, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 1 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
5 packets output, 805 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets, 0 restarts
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Table 47 describes the fields shown in these displays.
Table 47 show interfaces fastethernet Field Descriptions
Field
|
Description
|
Fast Ethernet0 is ... is up
...is administratively down
|
Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.
|
line protocol is
|
Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.
|
Hardware
|
Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.
|
Internet address
|
Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
ARP type
|
Type of Address Resolution Protocol assigned.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate,
5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received ... broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
|
input errors
|
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
|
overrun
|
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Number of packets whose receipt was aborted.
|
watchdog
|
Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048.
|
multicast
|
Number of multicast packets received.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times a Type 2 Ethernet controller was restarted because of errors.
|
babbles
|
The transmit jabber timer expired.
|
late collision
|
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
|
deferred
|
Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
|
lost carrier
|
Number of times the carrier was lost during transmission.
|
no carrier
|
Number of times the carrier was not present during the transmission.
|
output buffer failures
|
Number of failed buffers and number of buffers swapped out.
|
The following example of the show interfaces fastethernet command shows all the information specific to the first PA-12E/2FE interface port (interface port 0) in port adapter slot 3:
Router# show interfaces fastethernet 3/0
Fast Ethernet3/0 is up, line protocol is up
Hardware is TSWITCH, address is 00e0.f7a4.5130 (bia 00e0.f7a4.5130)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:05:30, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
312 packets input, 18370 bytes, 0 no buffer
Received 216 broadcasts, 0 runts, 0 giants, 0 throttles
3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored, 0 abort
0 input packets with dribble condition detected
15490 packets output, 1555780 bytes, 0 underruns
2 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
2 output buffer failures, 0 output buffers swapped out
Table 48 describes the fields shown in this display.
Table 48 show interfaces fastethernet Field Descriptions—PA-12E/2FE
Field
|
Description
|
Fast Ethernet... is up
...is administratively down
|
Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.
|
line protocol is
|
Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.
|
Hardware
|
Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.
|
Internet address
|
Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
ARP type
|
Type of Address Resolution Protocol assigned.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate,
5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received ... broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
|
throttles
|
Number of times the receiver on the port was disabled, possibly because of buffer or processor overload.
|
input errors
|
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
|
overrun
|
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Number of packets whose receipt was aborted.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
babbles
|
Transmit jabber timer expired.
|
late collision
|
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
|
deferred
|
Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
|
lost carrier
|
Number of times the carrier was lost during transmission.
|
no carrier
|
Number of times the carrier was not present during the transmission.
|
show interfaces fddi
To display information about the FDDI interface, use the show interfaces fddi command in user EXEC or privileged EXEC mode.
Standard Syntax
show interfaces fddi number [accounting]
Cisco 7000 and Cisco 7200 Series
show interfaces fddi [slot/port] [accounting]
Cisco 7500 Series
show interfaces fddi [slot/port-adapter/port] [accounting]
Syntax Description
number
|
Port number on the selected interface.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.3
|
This command was modified to include support for FDDI full-duplex, single- and multimode port adapters (PA-F/FD-SM and PA-F/FD-MM).
|
Examples
The following is a sample partial display of FDDI-specific data from the show interfaces fddi command on a Cisco 7500 series router:
Router# show interfaces fddi 3/0/0
Fddi3/0/0 is up, line protocol is up
Hardware is cxBus Fddi, address is 0000.0c02.adf1 (bia 0000.0c02.adf1)
Internet address is 10.108.33.14, subnet mask is 255.255.255.0
MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive not set
ARP type: SNAP, ARP Timeout 4:00:00
Phy-A state is active, neighbor is B, cmt signal bits 008/20C, status ILS
Phy-B state is active, neighbor is A, cmt signal bits 20C/008, status ILS
ECM is in, CFM is thru, RMT is ring_op
Token rotation 5000 usec, ring operational 21:32:34
Upstream neighbor 0000.0c02.ba83, downstream neighbor 0000.0c02.ba83
Last input 0:00:05, output 0:00:00, output hang never
Last clearing of "show interface" counters 0:59:10
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 69000 bits/sec, 44 packets/sec
Five minute output rate 0 bits/sec, 1 packets/sec
113157 packets input, 21622582 bytes, 0 no buffer
Received 276 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4740 packets output, 487346 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
0 transitions, 2 traces, 3 claims, 2 beacons
The following is sample output from the show interfaces fddi command for the full-duplex FDDI port adapter on a Cisco 7500 series router:
Router# show interfaces fddi 0/1/0
Fddi0/1/0 is up, line protocol is up
Hardware is cxBus FDDI, address is 0060.3e33.3608 (bia 0060.3e33.3608)
Internet address is 10.1.1.1/24
MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive not set
ARP type: SNAP, ARP Timeout 04:00:00
FDX supported, FDX enabled, FDX state is operation
Phy-A state is maintenance, neighbor is Unknown, status HLS
Phy-B state is active, neighbor is A, status SILS
ECM is in, CFM is c_wrap_b, RMT is ring_op,
Requested token rotation 5000 usec, negotiated 4997 usec
Configured tvx is 2500 usec
LER for PortA = 0A, LER for PortB = 0A ring operational 00:02:45
Upstream neighbor 0060.3e73.4600, downstream neighbor 0060.3e73.4600
Last input 00:00:12, output 00:00:13, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
62 packets input, 6024 bytes, 0 no buffer
Received 18 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
71 packets output, 4961 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
3 transitions, 0 traces, 100 claims, 0 beacon
Table 49 describes the fields shown in the display.
Table 49 show interfaces fddi Field Descriptions
Field
|
Description
|
Fddi is {up | down | administratively down
|
Gives the interface processor unit number and tells whether the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
|
line protocol is {up | down}
|
Indicates whether the software processes that handle the line protocol consider the interface usable.
|
Hardware
|
Provides the hardware type, followed by the hardware address.
|
Field
|
Description
|
Internet address
|
IP address, followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether or not loopback is set.
|
keepalive
|
Indicates whether or not keepalives are set.
|
ARP type
|
Type of Address Resolution Protocol assigned.
|
FDX
|
Displays full-duplex information. Values are: not supported or supported. When the value is supported, the display indicates whether full-duplex is enabled or disabled. When enabled, the state of the FDX negotiation process is displayed. The negotiation states only relate to the full-duplex negotiation process. You must also ensure that the interface is up and working by looking at other fields in the show interfaces fddi command such as line protocol and RMT. Negotiation states are:
•idle—Interface is working but not in full-duplex mode yet. If persistent, it could mean that the interface did not meet all negotiation conditions (for example, there are more than two stations in the ring).
•request—Interface is working but not in full-duplex mode yet. If persistent, it could mean that the remote interface does not support full-duplex or full-duplex is not enabled on the interface.
•confirm—Transient state.
•operation—Negotiations completed successfully, and both stations are operating in full-duplex mode.
|
Phy-{A | B}
|
Lists the state the Physical A or Physical B connection is in; one of the following: off, active, trace, connect, next, signal, join, verify, or break.
|
Field
|
Description
|
neighbor
|
State of the neighbor:
•A—Indicates that the connection management (CMT) process has established a connection with its neighbor. The bits received during the CMT signaling process indicate that the neighbor is a Physical A type dual attachment station (DAS) or concentrator that attaches to the primary ring IN and the secondary ring OUT when attaching to the dual ring.
•S—Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the neighbor is one Physical type in a single attachment station (SAS).
•B—Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the neighbor is a Physical B dual attachment station or concentrator that attaches to the secondary ring IN and the primary ring OUT when attaching to the dual ring.
•M—Indicates that the CMT process has established a connection with its neighbor and that the bits received during the CMT signaling process indicate that the router's neighbor is a Physical M-type concentrator serving as a Master to a connected station or concentrator.
•unk—Indicates that the network server has not completed the CMT process and, as a result, does not know about its neighbor. See the section "Setting Bit Control" for an explanation of the bit patterns.
|
cmt signal bits
|
Shows the transmitted/received CMT bits. The transmitted bits are 0x008 for a Physical A type and 0x20C for Physical B type. The number after the slash (/) is the received signal bits. If the connection is not active, the received bits are zero (0); see the line beginning Phy-B in the display. This applies to FIP interfaces only.
|
Field
|
Description
|
status
|
Status value displayed is the actual status on the fiber. The FDDI standard defines the following values:
•LSU—Line State Unknown, the criteria for entering or remaining in any other line state have not been met.
•NLS—Noise Line State is entered upon the occurrence of 16 potential noise events without satisfying the criteria for entry into another line state.
•MLS—Master Line State is entered upon the receipt of eight or nine consecutive HQ or QH symbol pairs.
•ILS—Idle Line State is entered upon receipt of four or five idle symbols.
•HLS—Halt Line State is entered upon the receipt of 16 or 17 consecutive H symbols.
•QLS—Quiet Line State is entered upon the receipt of 16 or 17 consecutive Q symbols or when carrier detect goes low.
•ALS—Active Line State is entered upon receipt of a JK symbol pair when carrier detect is high.
•OVUF—Elasticity buffer Overflow/Underflow. The normal states for a connected Physical type are ILS or ALS. If the report displays the QLS status, this indicates that the fiber is disconnected from Physical B, or that it is not connected to another Physical type, or that the other station is not running.
|
ECM is...
|
ECM is the SMT entity coordination management, which overlooks the operation of CFM and PCM. The ECM state can be one of the following:
•out—Router is isolated from the network.
•in—Router is actively connected to the network. This is the normal state for a connected router.
•trace—Router is trying to localize a stuck beacon condition.
•leave—Router is allowing time for all the connections to break before leaving the network.
•path_test—Router is testing its internal paths.
•insert—Router is allowing time for the optical bypass to insert.
•check—Router is making sure optical bypasses switched correctly.
•deinsert—Router is allowing time for the optical bypass to deinsert.
|
Field
|
Description
|
CFM is...
|
Contains information about the current state of the MAC connection. The Configuration Management state can be one of the following:
•isolated—MAC is not attached to any Physical type.
•wrap_a—MAC is attached to Physical A. Data is received on Physical A and transmitted on Physical A.
•wrap_b—MAC is attached to Physical B. Data is received on Physical B and transmitted on Physical B.
•wrap_s—MAC is attached to Physical S. Data is received on Physical S and transmitted on Physical S. This is the normal mode for a single attachment station (SAS).
•thru—MAC is attached to Physical A and B. Data is received on Physical A and transmitted on Physical B. This is the normal mode for a dual attachment station (DAS) with one MAC. The ring has been operational for 1 minute and 42 seconds.
|
RMT is...
|
RMT (Ring Management) is the SMT MAC-related state machine. The RMT state can be one of the following:
•isolated—MAC is not trying to participate in the ring. This is the initial state.
•non_op—MAC is participating in ring recovery, and ring is not operational.
•ring_op—MAC is participating in an operational ring. This is the normal state while the MAC is connected to the ring.
•detect—Ring has been nonoperational for longer than normal. Duplicate address conditions are being checked.
•non_op_dup—Indications have been received that the address of the MAC is a duplicate of another MAC on the ring. Ring is not operational.
•ring_op_dup—Indications have been received that the address of the MAC is a duplicate of another MAC on the ring. Ring is operational in this state.
•directed—MAC is sending beacon frames notifying the ring of the stuck condition.
•trace—Trace has been initiated by this MAC, and the RMT state machine is waiting for its completion before starting an internal path test.
|
token rotation
|
Token rotation value is the default or configured rotation value as determined by the fddi token-rotation-time command. This value is used by all stations on the ring. The default is 5000 microseconds. For FDDI full-duplex, this indicates the value in use prior to entering full-duplex operation.
|
negotiated
|
Actual (negotiated) target token rotation time.
|
Field
|
Description
|
ring operational
|
When the ring is operational, the displayed value will be the negotiated token rotation time of all stations on the ring. Operational times are displayed by the number of hours:minutes:seconds the ring has been up. If the ring is not operational, the message "ring not operational" is displayed.
|
Configured tvx
|
Transmission timer.
|
LER
|
Link error rate.
|
Upstream | downstream neighbor
|
Displays the canonical MAC address of outgoing upstream and downstream neighbors. If the address is unknown, the value will be the FDDI unknown address (0x00 00 f8 00 00 00).
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
|
Output queue, input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate
5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The five-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
Field
|
Description
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the media.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
frame
|
Number of packets received incorrectly that have a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device. On an FDDI LAN, this also can be the result of a failing fiber (cracks) or a hardware malfunction.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of transmit aborts (when the router cannot feed the transmitter fast enough).
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, because some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Because an FDDI ring cannot have collisions, this statistic is always zero.
|
interface resets
|
Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
|
restarts
|
Should always be zero for FDDI interfaces.
|
output buffer failures
|
Number of no resource errors received on the output.
|
Field
|
Description
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
transitions
|
The number of times the ring made a transition from ring operational to ring nonoperational, or vice versa. A large number of transitions indicates a problem with the ring or the interface.
|
traces
|
Trace count applies to both the FCI, FCIT, and FIP. Indicates the number of times this interface started a trace.
|
claims
|
Pertains to FCIT and FIP only. Indicates the number of times this interface has been in claim state.
|
beacons
|
Pertains to FCIT and FIP only. Indicates the number of times the interface has been in beacon state.
|
The following is sample output that includes the accounting option. When you use the accounting option, only the accounting statistics are displayed.
Router# show interfaces fddi 3/0 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 7344 4787842 1803 1535774
Appletalk 33345 4797459 12781 1089695
Table 50 describes the fields shown in the display.
Table 50 show interfaces fddi Field Descriptions—Accounting
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
show interfaces gigabitethernet
To check the status and configuration settings of the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E, use the show interfaces gigabitethernet command in privileged EXEC mode.
show interfaces gigabitethernet slot/port
Syntax Description
slot
|
Slot number on the interface.
|
port
|
Port number on the interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1 CC
|
This command was introduced.
|
12.1(3a)E
|
This command was implemented on the Cisco 7200-I/O-GE+E controller.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
This command is used on the Cisco 7200-I/O-GE+E to display the configuration status of the Gigabit Ethernet interface. Slot 0 is always reserved for the Gigabit Ethernet port on the I/O controller.
Examples
The following is sample output from the show interfaces gigabitethernet command:
Router# show interfaces gigabitethernet 0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is 82543 (Livengood), address is 00d0.ffb6.4c00 (bia 00d0.ffb6.4c00)
Internet address is 10.1.1.3/8
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Full-duplex mode, link type is autonegotiation, media type is SX
output flow-control is on, input flow-control is on
ARP type:ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2252 packets input, 135120 bytes, 0 no buffer
Received 2252 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
2631 packets output, 268395 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Related Commands
Command
|
Description
|
show controllers gigabitethernet
|
Displays initialization block information, transmit ring, receive ring, and errors for the interface controllers for the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E.
|
show interfaces hssi
To display information about the high-speed serial interface (HSSI), use the show interfaces hssi command in privileged EXEC mode.
Standard Syntax
show interfaces hssi number [accounting]
Cisco 7500 Series
show interfaces hssi [slot/port] [accounting]
Syntax Description
number
|
Port number on the selected interface.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show interfaces hssi command when HSSI is enabled:
Router# show interfaces hssi 0
HSSI 0 is up, line protocol is up
Internet address is 10.136.67.190, subnet mask is 255.255.255.0
MTU 4470 bytes, BW 45045 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:03, output 0:00:00, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
17 packets output, 994 bytes, 0 underruns
0 output errors, 0 applique, 4 interface resets, 0 restarts
Table 51 describes significant fields shown in the display.
Table 51 show interfaces hssi Field Descriptions
Field
|
Description
|
HSSI is {up | down | administratively down}
|
Indicates whether the interface hardware is currently active (whether carrier detect is present) and whether it has been taken down by an administrator. "Disabled" indicate that the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default.
|
line protocol
is {up | down |
administratively down}
|
Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful).
|
Hardware
|
Specifies the hardware type.
|
Internet address
|
Lists the Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether loopback is set and type of loopback test.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, drops
Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes input
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
parity
|
Report of the parity errors on the HSSI.
|
rx disabled
|
Indicates that the HSSI could not find a free buffer on the ciscoBus controller to reserve for use for the HSSI receiver. When this happens, the HSSI shuts down its receiver and waits until a buffer is available. Data is not lost unless a packet comes in and overflows the HSSI FIFO. Usually, the receive disables are frequent but do not last for long, and the number of dropped packets is less than the count in the "rx disabled" field. A receive disabled condition can happen in systems that are under heavy traffic load and that have shorter packets. In this situation, the number of buffers available on the ciscoBus controller is at a premium. One way to alleviate this problem is to reduce the maximum transmission unit (MTU) on the HSSI interface from 4500 (FDDI size) to 1500 (Ethernet size). Doing so allows the software to take the fixed memory of the ciscoBus controller and divide it into a larger number of smaller buffers, rather than a small number of large buffers. Receive disables are not errors, so they are not included in any error counts.
|
input errors
|
Sum of all errors that prevented the receipt of datagrams on the interface being examined. This may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.
|
CRC
|
Cyclic redundancy checksum (CRC) generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC errors are also reported when a far-end abort occurs, and when the idle flag pattern is corrupted. This makes it possible to get CRC errors even when there is no data traffic.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the ability of the receiver to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Number of packets whose receipt was aborted.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes output
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router receiver can handle.
|
congestion drop
|
Number of messages discarded because the output queue on an interface grew too long. This can happen on a slow, congested serial link.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
applique
|
Indicates that an unrecoverable error has occurred on the High-System Availability (HSA) applique. The system then invokes an interface reset.
|
interface resets
|
Number of times that an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times that the controller was restarted because of errors.
|
carrier transitions
|
Number of times that the carrier detect signal of the interface has changed state. Indicates modem or line problems if the carrier detect line is changing state often.
|
The following is sample output from the show interfaces hssi command on a Cisco 7500 series router:
Router# show interfaces hssi 1/0
Hssi1/0 is up, line protocol is up
Internet address is 10.108.38.14, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 45045 Kbit, DLY 1000000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:00, output 0:00:08, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 1000 bits/sec, 2 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
630573548 packets input, 2077237628 bytes, 0 no buffer
Received 2832063 broadcasts, 0 runts, 0 giants
0 parity, 1970 rx disabled
113 input errors, 20 CRC, 93 frame, 0 overrun, 0 ignored, 0 abort
629721628 packets output, 1934313295 bytes, 0 underruns
0 output errors, 0 applique, 62 interface resets, 0 restarts
The following is sample output from the show interfaces hssi command with the accounting option on a Cisco 7500 series router:
Router# show interfaces hssi 1/0 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 7344 4787842 1803 1535774
Appletalk 33345 4797459 12781 1089695
Table 52 describes the fields shown in the display.
Table 52 show interfaces hssi Field Descriptions—Accounting
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
show interfaces loopback
To display information about the loopback interface, use the show interfaces loopback command in privileged EXEC mode.
show interfaces loopback [number] [accounting]
Syntax Description
number
|
(Optional) Port number on the selected interface.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show interfaces loopback command:
Router# show interfaces loopback 0
Loopback0 is up, line protocol is up
MTU 1500 bytes, BW 1 Kbit, DLY 50 usec, rely 255/255, load 1/255
Encapsulation UNKNOWN, loopback not set, keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/0, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
The following is sample output when the accounting keyword is included:
Router# show interfaces loopback 0 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
Table 53 describes significant fields shown in the displays.
Table 53 show interfaces loopback Field Descriptions
Field
|
Description
|
Loopback is {up | down | administratively down}
|
Indicates whether the interface hardware is currently active (whether carrier detect is present), is currently inactive, or has been taken down by an administrator.
|
line protocol is {up | down | administratively down}
|
Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful).
|
Hardware
|
Hardware is Loopback.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether loopback is set and type of loopback test.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, drops; Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes input
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
input errors
|
Sum of all errors that prevented the receipt of datagrams on the interface being examined. This may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error and others may have errors that do not fall into any of the specifically tabulated categories.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC errors are also reported when a far-end abort occurs, and when the idle flag pattern is corrupted. This makes it possible to get CRC errors even when there is no data traffic.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Number of packets whose receipt was aborted.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes output
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never happen (be reported) on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Loopback interface does not have collisions.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times the controller was restarted because of errors.
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
show interfaces port-channel
To display the information about the Fast EtherChannel on Cisco 7000 series routers with the RSP7000 and RSP7000CI, Cisco 7200 series routers, and Cisco 7500 series routers, use the show interfaces port-channel command in user EXEC or privileged EXEC mode.
show interfaces port-channel [channel-number]
Syntax Description
channel-number
|
(Optional) Port channel number. Range is from 1 to 4.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.1 CA
|
This command was introduced.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Examples
The following is sample output from the show interfaces port-channel command:
Note By default the hardware type is set to Fast EtherChannel.The default MTU is set to 1500 bytes. The maximum MTU size that can be configured on the native Gigabit Ethernet ports on the Cisco 7200 series router is 9216. The range of configurable MTU value is from 1500 to 9216.
Router# show interfaces port-channel 1
Port-channel1 is up, line protocol is up
Hardware is FEChannel, address is 0000.0ca8.6220 (bia 0000.0000.0000)
MTU 1500 bytes, BW 400000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set, fdx
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 4
Member 0 : Fast Ethernet1/0/0
Member 1 : Fast Ethernet1/1/0
Member 2 : Fast Ethernet4/0/0
Member 3 : Fast Ethernet4/1/0
Last input 01:22:13, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
223 packets input, 11462 bytes, 0 no buffer
Received 1 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
192 packets output, 13232 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
The following sample output from the show interfaces port-channel shows Gigabit EtherChannel as hardware type and the MTU value as 9216:
Router# show interface port-channel 1
Port-channel1 is up, line protocol is up
Hardware is GEChannel, address is 0001.c929.c41b (bia 0001.c929.c41b)
MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Unknown duplex, Unknown Speed, media type is unknown media type
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 1
Member 0 : GigabitEthernet0/1 , Full-duplex, 1000Mb/s
No. of Non-active members in this channel: 0
Last input 00:00:04, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
95 packets input, 34383 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1 packets output, 77 bytes, 0 underruns
2 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Table 54 describes significant fields shown in the display.
Table 54 show interfaces port-channel Field Descriptions
Field
|
Description
|
Port-channel1 is up, line protocol is up
|
Indicates if the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
|
Hardware is
|
Hardware type (Fast EtherChannel).
|
address is
|
Address being used by the interface.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to the interface.
|
loopback
|
Indicates if loopbacks are set.
|
keepalive
|
Indicates if keepalives are set.
|
fdx
|
Indicates the interface is operating in full-duplex mode.
|
ARA type
|
ARP type on the interface.
|
ARP timeout
|
Number of hours, minutes, and seconds an ARP cache entry will stay in the cache.
|
No. of active members in this channel: 4
|
Number of Fast Ethernet interfaces that are currently active (not down) and part of the Fast EtherChannel group.
|
Member 0: Fast Ethernet1/0/0
|
Specific Fast Ethernet interface that is part of the Fast EtherChannel group.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms)) ago.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
|
Output queue, drops
input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
|
5 minute input rate
5 minute output rate
|
Average number of bits and packets received or transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes (input)
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
|
abort
|
Illegal sequence of ones bit on the interface.
|
watchdog
|
Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048.
|
multicast
|
Number of multicast packets received.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes (output)
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
|
babbles
|
The transmit jabber timer expired.
|
late collision
|
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
|
deferred
|
Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.
|
lost carrier
|
Number of times the carrier was lost during transmission.
|
no carrier
|
Number of times the carrier was not present during the transmission.
|
output buffer failures
|
Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory.
|
output buffers swapped out
|
Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty.
|
Related Commands
Command
|
Description
|
interface multilink
|
Specifies a Fast EtherChannel and enters interface configuration mode.
|
show interfaces pos
To display information about the Packet OC-3 interface in Cisco 7500 series routers, use the show interfaces pos command in user EXEC or privileged EXEC mode.
Cisco 7000 and Cisco 7500 Series with VIPs
show interfaces pos [slot/port-adapter/port]
Syntax Description
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
/port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
/port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
The show interface posi command was introduced.
|
11.3
|
The name of the command was modified from show interface posi to show interfaces pos, and the sample output was updated.
|
Examples
The following is sample output from the show interfaces pos command on a Cisco 7513 router with one Packet OC-3 Interface Processor (POSIP):
Router# show interfaces pos 2/0/0
POS2/0/0 is up, line protocol is up
Hardware is cyBus Packet over Sonet
Description: PRI-T1 net to zippy (4K) to Pac-Bell
Internet address is 10.1.1.1/27
MTU 4470 bytes, BW 1000 Kbit, DLY 40000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (3 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:23:09
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
1046 packets input, 54437 bytes, 0 no buffer
Received 485 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4013 packets output, 1357412 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 55 describes the significant fields shown in the display.
Table 55 show interfaces pos Field Descriptions
Field
|
Description
|
POS2/0/0 is up, line protocol is up
|
Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.
|
Hardware is cyBus Packet over Sonet
|
Hardware type.
|
Internet address is
|
Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether loopbacks are set.
|
keepalive
|
Indicates whether keepalives are set.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
(Last) output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 2231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
|
Output queue, drops
input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
|
5 minute input rate
5 minute output rate
|
Average number of bits and packets received or transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes (input)
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
parity
|
Report of the parity errors on the interface.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
|
abort
|
Illegal sequence of one bits on the interface.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes (output)
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
applique
|
Indicates an unrecoverable error has occurred on the POSIP applique. The system then invokes an interface reset.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
|
carrier transitions
|
Number of times the carrier detect signal of the interface has changed state.
|
Related Commands
Command
|
Description
|
interface
|
Configures an interface type and enters interface configuration mode.
|
show interfaces serial
To display information about a serial interface, use the show interfaces serial command in privileged EXEC mode. When using Frame Relay encapsulation, use the show interfaces serial command in user EXEC or privileged EXEC mode to display information about the multicast data-link connection identifier (DLCI), the DLCIs used on the interface, and the DLCI used for the Local Management Interface (LMI).
Cisco 4000 Series
show interfaces serial [number[:channel-group]] [accounting]
Cisco 7000 and Cisco 7500 Series with the RSP7000, RSP7000CI, or Ports on VIPs
show interfaces serial [slot/port-adapter/port]
Cisco 7500 Series
show interfaces serial [slot/port[:channel-group]] [accounting]
Cisco 7500 Series with a CT3IP
show interfaces serial [slot/port-adapter/port][:t1-channel] [accounting | crb]
Cisco AS5350 and Cisco AS5400 Universal Gateways
show interfaces serial slot/port
Cisco AS5800 Access Servers
show interfaces serial dial-shelf/slot/t3-port:t1-num:chan-group
Syntax Description
number
|
(Optional) Number of the port being displayed.
|
:channel-group
|
(Optional) On the Cisco 4000 series with a Network Management Processor (NPM) or the Cisco 7500 series routers with a MultiChannel Interface Processor (MIP), specifies the T1 channel-group number in the range of 0 to 23 defined with the channel-group controller configuration command.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
(Optional) Number of the slot being displayed. Refer to the appropriate hardware manual for slot and port information.
|
/port
|
(Optional) Number of the port being displayed. Refer to the appropriate hardware manual for slot and port information.
|
/port-adapter
|
(Optional) Number of the port adapter being displayed. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
:t1-channel
|
(Optional) T1 channel number. For the CT3IP, the T1 channel is a number between 1 and 28.
T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This scheme ensures consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
|
crb
|
(Optional) Displays interface routing and bridging information.
|
dial-shelf
|
Dial shelf chassis in the Cisco AS5800 access server that contains the CT3 interface card.
|
slot
|
Location of the CT3 interface card in the dial shelf chassis.
|
t3-port
|
T3 port number. The only valid value is 0.
|
:t1-num
|
T1 time slot in the T3 line. The value can be from 1 to 28.
|
:chan-group
|
Channel group identifier.
|
Command Modes
User EXEC (when Frame Relay encapsulation is used)
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced on the Cisco 4000 series routers.
|
11.0
|
This command was implemented on the Cisco 7000 series routers.
|
11.1 CA
|
This command was modified to include sample output for the PA-2JT2, PA-E3, and PA-T3 serial port adapters.
|
11.3
|
This command was modified to include the CT3IP.
|
12.0(3)T
|
This command was implemented on the Cisco AS5800 access servers.
|
12.0(4)T
|
This command was modified to include enhanced display information for dialer bound interfaces.
|
12.2(11)T
|
This command was implemented on the Cisco AS5350 and Cisco AS5400.
|
12.2(13)T
|
This command was modified to display information about Frame Relay interface queueing and fragmentation.
|
Usage Guidelines
Frame Relay
Use this command to determine the status of the Frame Relay link. This display also indicates Layer 2 status if switched virtual circuits (SVCs) are configured.
Channel Groups as Virtual Serial Interfaces
To find out about channel groups configured as virtual serial interfaces, to verify that the router has High-Level Data Link Control (HDLC) encapsulation on the interface, and to verify that the interface sees the loopback, use the show interfaces serial command in privileged EXEC mode.
Examples
Example of Synchronous Serial Interface
The following is sample output from the show interfaces serial command for a synchronous serial interface:
Router# show interfaces serial
Serial 0 is up, line protocol is up
Internet address is 192.168.10.203, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:07, output 0:00:00, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
16263 packets input, 1347238 bytes, 0 no buffer
Received 13983 broadcasts, 0 runts, 0 giants
2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
22146 packets output, 2383680 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
Table 56 describes significant fields shown in the display.
Table 56 show interfaces serial Field Descriptions—Synchronous Serial Interface
Field
|
Description
|
Serial ... is {up | down} ... is administratively down
|
Indicates whether the interface hardware is currently active (whether carrier detect is present), is currently inactive, or has been taken down by an administrator.
|
line protocol is {up | down}
|
Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful) or whether the line has been taken down by an administrator.
|
Hardware is
|
Specifies the hardware type.
|
Internet address is
|
Specifies the Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Indicates the value of the bandwidth parameter that has been configured for the interface (in kbps). If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 kbps for T1 and 56 kbps for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether or not loopback is set.
|
keepalive
|
Indicates whether or not keepalives are set.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Output queue, drops
input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
5 minute input rate
5 minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
Received... broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
|
carrier transitions
|
Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes output
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface from being examined. Note that this might not balance with the sum of the enumerated output errors because some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. Some collisions are normal. However, if your collision rate climbs to around 4 or 5 percent, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds' time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times the controller was restarted because of errors.
|
alarm indications, remote alarms, rx LOF, rx LOS
|
Number of CSU/DSU alarms and number of occurrences of receive loss of frame and receive loss of signal.
|
BER inactive, NELR inactive, FELR inactive
|
Status of G.703-E1 counters for bit-error rate (BER) alarm, near-end loop remote (NELR), and far-end loop remote (FELR). Note that you cannot set the NELR or FELR.
|
Example of PA-2JT2 Serial Interface
The following is sample output from the show interfaces serial command for a PA-2JT2 serial interface:
Router# show interfaces serial 3/0/0
Serial3/0/0 is up, line protocol is up
Internet address is 10.0.0.1/8
MTU 1500 bytes, BW 6312 Kbit, DLY 20000 usec, rely 255/255, load 26/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 00:04:31, output 00:04:31, output hang never
Last clearing of "show interface" counters 00:06:07
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 162000 bits/sec, 8 packets/sec
5 minute output rate 162000 bits/sec, 8 packets/sec
20005 packets input, 20080520 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
20005 packets output, 20080520 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 cv errors, 0 crc5 errors, 0 frame errors
rxLOS inactive, rxLOF inactive, rxPAIS inactive
rxAIS inactive, rxRAI inactive, rxHBER inactive
Table 57 describes significant fields shown in the display that are different from the fields described in Table 56.
Table 57 show interfaces serial Field Descriptions—PA-2JT2
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
carrier transitions
|
Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.
|
cv errors
|
B8ZS/B6ZS (zero suppression) coding violation counter.
|
crc5 errors
|
CRC-5 error counter.
|
frame errors
|
Framing error counter.
|
rxLOS
|
Receive loss of signal alarm. Values are active or inactive.
|
rxLOF
|
Receive loss of frame alarm. Values are active or inactive.
|
rxPAIS
|
Receive loss of payload alarm indication signal (AIS). Values are active or inactive.
|
rxAIS
|
Receive loss of physical AIS. Values are active or inactive.
|
rxRAI
|
Receive remote AIS. Values are active or inactive.
|
rxHBER
|
Receive high bit-error rate alarm. Values are active or inactive.
|
Example of PA-E3 Serial Port Adapter
The following is sample output from the show interfaces serial command for a PA-E3 serial port adapter installed in chassis slot 2:
Router# show interfaces serial 2/0
Serial2/0 is up, line protocol is up
Internet address is 172.17.1.1/24
MTU 4470 bytes, BW 34010 Kbit, DLY 200 usec, rely 128/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 1w0d, output 00:00:48, output hang never
Last clearing of "show interface" counters 1w0d
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
20 packets input, 2080 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
11472 packets output, 3824748 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
rxLOS inactive, rxLOF inactive, rxAIS inactive
txAIS inactive, rxRAI inactive, txRAI inactive
Table 58 describes significant fields shown in the display that are different from the fields described in Table 56.
Table 58 show interfaces serial Field Descriptions—PA-E3
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
parity
|
Number of the parity errors on the interface.
|
applique
|
Indicates that an unrecoverable error has occurred on the E3 applique. The router then invokes an interface reset.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
rxLOS, rxLOF, rxAIS
|
Receive loss of signal, loss of frame, and alarm indication signal status. Values are inactive or active.
|
txAIS, rxRAI, txRAI
|
Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active. When the router receives an LOS, LOF, or AIS, the txRAI is active. When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.
|
Example of 1-Port PA-T3 Serial Port Adapter Installed in a VIP2
The following is sample output from the show interfaces serial command for a 1-port PA-T3 serial port adapter installed in a VIP2 in chassis slot 1, in port adapter slot 0:
Router# show interfaces serial 1/0/0
Serial1/0/0 is up, line protocol is up
Hardware is cyBus PODS3 Serial
Internet address is 172.18.1.1/24
MTU 4470 bytes, BW 44736 Kbit, DLY 200 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 00:00:05, output 00:00:02, output hang never
Last clearing of "show interface" counters 5d02h
Output queue 0/40, 0 drops; input queue 0/75, 27269 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
79039 packets input, 14195344 bytes, 0 no buffer
Received 84506 broadcasts, 0 runts, 0 giants
9574 input errors, 6714 CRC, 0 frame, 1 overrun, 0 ignored, 2859 abort
62472 packets output, 13751644 bytes, 0 underruns
0 output errors, 0 applique, 10 interface resets
0 output buffer failures, 0 output buffers swapped out
rxLOS inactive, rxLOF inactive, rxAIS inactive
txAIS inactive, rxRAI inactive, txRAI inactive
Table 59 describes significant fields shown in the display that are different from the fields described in Table 56.
Table 59 show interfaces serial Field Descriptions—PA-T3
Field
|
Description
|
Last clearing of "show interface" counters
|
Time the counters were last cleared.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
parity
|
Number of the parity errors on the interface.
|
applique
|
Indicates that an unrecoverable error has occurred on the T3 applique. The router then invokes an interface reset.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
rxLOS, rxLOF, rxAIS
|
Receive loss of signal, loss of frame, and alarm indication signal status. Values are inactive or active.
|
txAIS, rxRAI, txRAI
|
Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active. When the router receives an LOS, LOF, or AIS, the txRAI is active. When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.
|
Example of CT3IP Serial Interface
The following is sample output from the show interfaces serial command for the CT3IP serial interface:
Router# show interfaces serial 3/0/0:25
Serial3/0/0:25 is up, line protocol is up
Internet address is 10.25.25.2/24
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, rely 255/255, load 12/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 00:19:01, output 00:11:49, output hang never
Last clearing of "show interface" counters 00:19:39
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 69000 bits/sec, 90 packets/sec
5 minute output rate 71000 bits/sec, 90 packets/sec
762350 packets input, 79284400 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
150 input errors, 0 CRC, 0 frame, 150 overrun, 0 ignored, 0 abort
763213 packets output, 80900472 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions no alarm present
Timeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 5
Table 60 describes significant fields relevant to the CT3IP shown in the display that are different from the fields described in Table 56.
Table 60 show interfaces serial Field Descriptions—CT3IP
Field
|
Description
|
Timeslot(s) Used
|
Number of time slots assigned to the T1 channel.
|
Transmitter delay
|
Number of idle flags inserted between each HDLC frame.
|
transmit queue length
|
Number of packets allowed in the transmit queue.
|
non-inverted data
|
Indicates whether or not the interface is configured for inverted data.
|
Example of an HDLC Synchronous Serial Interface on a Cisco 7500 Series Router
The following is sample output from the show interfaces serial command for an HDLC synchronous serial interface on a Cisco 7500 series router:
Router# show interfaces serial 1/0
Serial1/0 is up, line protocol is up
Internet address is 172.19.190.203, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input 0:00:07, output 0:00:00, output hang never
Last clearing of "show interface" counters 2w4d
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
16263 packets input, 1347238 bytes, 0 no buffer
Received 13983 broadcasts, 0 runts, 0 giants
2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
22146 packets output, 2383680 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
Table 56 describes significant fields shown in the display.
Example of HDLC Encapsulation
The following example displays High-Level Data Link Control (HDLC) encapsulation on serial interface 0:
Router# show interfaces serial 0
Serial0 is up, line protocol is up (looped)
Internet address is 10.1.1.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback set, keepalive set (10 sec)
Table 56 describes significant fields shown in the display.
Example of a G.703 Interface with Framing
The following is sample output from the show interfaces serial command for a G.703 interface on which framing is enabled:
Router# show interfaces serial 2/3
Serial2/3 is up, line protocol is up
Internet address is 10.4.4.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive not set
Last input 0:00:21, output 0:00:21, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
53 packets input, 7810 bytes, 0 no buffer
Received 53 broadcasts, 0 runts, 0 giants
2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
56 packets output, 8218 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
2 alarm indications, 333 remote alarms, 332 rx LOF, 0 rx LOS
RTS up, CTS up, DTR up, DCD up, DSR up
BER inactive, NELR inactive, FELR inactive
Table 56 describes significant fields shown in the display.
Example with Frame Relay Encapsulation
When using Frame Relay encapsulation, use the show interfaces serial command to display information on the multicast data-link connection identifier (DLCI), the DLCI of the interface, and the DLCI used for the local management interface (LMI).
The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and frame-relay local-dlci configuration commands. The status information is taken from the LMI, when active.
The following is sample output from the show interfaces serial command when Frame Relay encapsulation and LMI are enabled:
Router# show interfaces serial
Serial 2 is up, line protocol is up
Hardware type is MCI Serial
Internet address is 172.20.122.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)
multicast DLCI 1022, status defined, active
source DLCI 20, status defined, active
LMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2
Last input 7:21:29, output 0:00:37, output hang never
Output queue 0/100, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
47 packets input, 2656 bytes, 0 no buffer
Received 5 broadcasts, 0 runts, 0 giants
5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 57 abort
518 packets output, 391205 bytes
0 output errors, 0 collisions, 0 interface resets, 0 restarts
In this display, the multicast DLCI has been changed to 1022 using the frame-relay multicast-dlci interface configuration command.
The display shows the statistics for the LMI as the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). Refer to the Frame Relay Interface specification for additional explanations of this output.
Example with Frame Relay Queueing and Fragmentation at the Interface
The following is sample output from the show interfaces serial command when low-latency queueing and FRF.12 end-to-end fragmentation are configured on a Frame Relay interface:
Router# show interfaces serial 3/2
Serial3/2 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, crc 16, loopback not set
LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 1023 LMI type is CISCO frame relay DTE
Fragmentation type: end-to-end, size 80, PQ interleaves 0
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
Last input 2d15h, output 2d15h, output hang never
Last clearing of "show interface" counters 00:01:31
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1094 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up
Table 61 describes significant fields shown in the display that are different from the fields described in Table 56.
Table 61 show interfaces serial Field Descriptions—Frame Relay Interface Queueing and Fragmentation
Field
|
Description
|
txload
|
Interface load in the transmit direction.
|
rxload
|
Interface load in the receive direction.
|
crc
|
Length the cyclic redundancy check (CRC) used on the interface.
|
LMI enq sent
|
Number of Frame Relay status inquiry messages sent.
|
LMI stat recvd
|
Number of Frame Relay status request messages received.
|
LMI upd recvd
|
Number of single PVC asynchronous status messages received.
|
DTE LMI up
|
LMI peers are synchronized.
|
LMI enq recvd
|
Number of Frame Relay status inquiry messages received.
|
LMI stat sent
|
Number of Frame Relay status request messages sent.
|
LMI upd sent
|
Number of single PVC asynchronous status messages sent.
|
Fragmentation type
|
Type of fragmentation: end-to-end, Cisco, or VoFR
|
size
|
Fragmentation size.
|
PQ interleaves
|
Number of priority queue frames that have interleaved data fragments.
|
Broadcast queue
|
Number on queue/queue depth.
|
broadcasts sent/dropped
|
Number of broadcasts sent and dropped.
|
interface broadcasts
|
Number of broadcasts sent on interface.
|
Input queue
|
size—Current size of the input queue.
max—Maximum size of the queue.
drops—Number of messages discarded.
flushes—Number of times that data on queue has been discarded.
|
Queueing strategy
|
Type of queueing configured on the interface.
|
Output queue
|
size—Current size of the output queue.
max total—Maximum number of frames that can be queued.
threshold—Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped.
drops—Number of dropped messages.
|
Conversations
|
active—Number of currently active conversations.
max active—Maximum number of conversations that have ever occurred at one time.
max total—Maximum number of active conversations allowed.
|
throttles
|
Number of times the receiver on the port was disabled, possibly because of processor or buffer overload.
|
output buffer failures
|
Number of "no resource" errors received on the output.
|
output buffers swapped out
|
Number of packets swapped to DRAM.
|
Example with ANSI LMI
For a serial interface with the ANSI Local Management Interface (LMI) enabled, use the show interfaces serial command to determine the LMI type implemented. The following is sample output from the show interfaces serial command for a serial interface with the ANSI LMI enabled:
Router# show interfaces serial
Serial 1 is up, line protocol is up
Internet address is 172.18.121.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY, loopback not set, keepalive set
LMI DLCI 0, LMI sent 10, LMI stat recvd 10
Last input 0:00:00, output 0:00:00, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 1 packets/sec
Five minute output rate 1000 bits/sec, 1 packets/sec
261 packets input, 13212 bytes, 0 no buffer
Received 33 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
238 packets output, 14751 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Notice that the show interfaces serial output for a serial interface with ANSI LMI shown in this display is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. Table 62 describes the few differences that exist.
Table 62 show interfaces serial Field Descriptions—ANSI LMI
Field
|
Description
|
LMI DLCI 0
|
Identifies the DLCI used by the LMI for this interface. The default is 1023.
|
LMI sent 10
|
Number of LMI packets that the router sent.
|
LMI type is ANSI Annex D
|
Indicates that the interface is configured for the ANSI-adopted Frame Relay specification T1.617 Annex D.
|
Example with LAPB Encapsulation
Use the show interfaces serial command to display operation statistics for an interface that uses Link Access Procedure, Balanced (LAPB) encapsulation. The following is partial sample output from the show interfaces serial command for a serial interface that uses LAPB encapsulation:
Router# show interfaces serial 1
LAPB state is SABMSENT, T1 3000, N1 12056, N2 20, k7,Protocol ip
VS 0, VR 0, RCNT 0, Remote VR 0, Retransmissions 2
IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABMs 3/0 FRMRs 0/0 DISCs 0/0
Table 63 shows the fields relevant to all LAPB connections.
Table 63 show interfaces serial Field Descriptions—LAPB
Field
|
Description
|
LAPB state is
|
State of the LAPB protocol.
|
T1 3000, N1 12056, ...
|
Current parameter settings.
|
Protocol
|
Protocol encapsulated on a LAPB link; this field is not present on interfaces configured for multiprotocol LAPB or X.25 encapsulations.
|
VS
|
Modulo 8 frame number of the next outgoing information frame.
|
VR
|
Modulo 8 frame number of the next information frame expected to be received.
|
RCNT
|
Number of received information frames that have not yet been acknowledged.
|
Remote VR
|
Number of the next information frame that the remote device expects to receive.
|
Retransmissions
|
Count of current retransmissions because of expiration of T1.
|
Window is closed
|
No more frames can be transmitted until some outstanding frames have been acknowledged. This message should be displayed only temporarily.
|
IFRAMEs
|
Count of information frames in the form of sent/received.
|
RNRs
|
Count of Receiver Not Ready frames in the form of sent/received.
|
REJs
|
Count of Reject frames in the form of sent/received.
|
SABMs
|
Count of Set Asynchronous Balanced Mode commands in the form of sent/received.
|
FRMRs
|
Count of Frame Reject frames in the form of sent/received.
|
DISCs
|
Count of Disconnect commands in the form of sent/received.
|
Router# show interfaces serial 1
Table 64 show the fields relevant to PPP connections.
Table 64 show interfaces serial Field Descriptions—PPP Encapsulation
Field
|
Description
|
lcp state
|
Link Control Protocol.
|
ncp ipcp state
|
Network Control Protocol Internet Protocol Control Protocol.
|
ncp osicp state
|
Network Control Protocol OSI (CLNS) Control Protocol.
|
ncp ipxcp state
|
Network Control Protocol IPX (Novell) Control Protocol.
|
ncp deccp state
|
Network Control Protocol DECnet Control Protocol.
|
ncp bridgecp state
|
Network Control Protocol Bridging Control Protocol.
|
ncp atalkcp state
|
Network Control Protocol AppleTalk Control Protocol.
|
Example with SDLC Connections
Use the show interfaces serial command to display the Synchronous Data Link Control (SDLC) information for a given SDLC interface. The following is sample output from the show interfaces serial command for an SDLC primary interface that supports the SDLLC function:
Router# show interfaces serial
Serial 0 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC-PRIMARY, loopback not set
Timers (msec): poll pause 100 fair poll 500. Poll limit 1
[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
largest token ring frame 2052]
SDLC addr C1 state is CONNECT
VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
Poll: clear, Poll count: 0, chain: p: C1 n: C1
SDLLC [largest SDLC frame: 265, XID: disabled]
Last input 00:00:02, output 00:00:01, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 517 bits/sec, 30 packets/sec
Five minute output rate 672 bits/sec, 20 packets/sec
357 packets input, 28382 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
926 packets output, 77274 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Table 65 shows the fields relevant to all SDLC connections.
Table 65 show interfaces serial Field Descriptions—SDLC Enabled
Field
|
Description
|
Timers (msec): poll pause, fair poll, Poll limit
|
Current values of these timers for the primary SDLC interface.
|
T1, N1, N2, K
|
Values for these parameters for the primary SDLC interface.
|
Table 66 shows other data given for each SDLC secondary interface configured to be attached to the serial interface.
Table 66 SDLC Secondary Interface Descriptions
Field
|
Description
|
addr
|
Address of this SDLC secondary interface.
|
state is
|
Current state of this connection, which is one of the following:
•DISCONNECT—No communication is being attempted to this secondary.
• CONNECT—A normal connect state exists between this router and this secondary.
•DISCSENT—This router has sent a disconnect request to this secondary and is awaiting its response.
•SNRMSENT—This router has sent a connect request (SNRM) to this secondary and is awaiting its response.
•THEMBUSY—This secondary has told this router that it is temporarily unable to receive any more information frames.
•USBUSY—This router has told this secondary that it is temporarily unable to receive any more information frames.
•BOTHBUSY—Both sides have told each other that they are temporarily unable to receive any more information frames.
•ERROR—This router has detected an error and is waiting for a response from the secondary acknowledging this.
|
VS
|
Sequence number of the next information frame that this station sends.
|
VR
|
Sequence number of the next information frame from this secondary that this station expects to receive.
|
Remote VR
|
Last frame transmitted by this station that has been acknowledged by the other station.
|
Current retransmit count:
|
Number of times the current I-frame or sequence of I-frames has been retransmitted.
|
Hold Queue
|
Number of frames in hold queue and maximum size of hold queue.
|
IFRAMEs, RNRs, SNRMs, DISCs
|
Sent/received count for these frames.
|
Poll
|
"Set" if this router has a poll outstanding to the secondary; "clear" if it does not.
|
Poll Count
|
Number of polls in a row that have been given to this secondary at this time.
|
Chain
|
Shows the previous (p) and next (n) secondary address on this interface in the round robin loop of polled devices.
|
Example with SDLLC
Use the show interfaces serial command to display the SDLLC statistics for SDLLC-configured interfaces. The following is sample output from the show interfaces serial command for a serial interface configured for SDLLC:
Router# show interfaces serial
Serial 0 is up, line protocol is up
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC-PRIMARY, loopback not set
Timers (msec): poll pause 100 fair poll 500. Poll limit 1
[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none
SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10
largest token ring frame 2052]
SDLC addr C1 state is CONNECT
VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0
Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0
Poll: clear, Poll count: 0, chain: p: C1 n: C1
SDLLC [largest SDLC frame: 265, XID: disabled]
Last input 00:00:02, output 00:00:01, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 517 bits/sec, 30 packets/sec
Five minute output rate 672 bits/sec, 20 packets/sec
357 packets input, 28382 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
926 packets output, 77274 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
6608 Last polled device: none
SDLLC [ma: 0000.0C01.14--, ring: 7 brid2 carrier transitions
Most of the output shown in the display is generic to all SDLC-encapsulated interfaces and is described in the Cisco IOS Bridging and IBM Networking Command Reference, Volume 2 of 2: IBM Networking. Table 67 shows the parameters specific to SDLLC.
Table 67 SDLLC Parameter Descriptions
Field
|
Description
|
SDLLC ma
|
Lists the MAC address configured for this interface. The last byte is shown as "--" to indicate that it is filled in with the SDLC address of the connection.
|
ring, bridge, target ring
|
Lists the parameters as configured by the sdllc traddr command.
|
largest token ring frame
|
Shows the largest Token Ring frame that is accepted on the Logical Link control, type 2 (LLC2) side of the connection.
|
largest SDLC frame
|
Shows the largest SDLC frame that is accepted and will be generated on the SDLC side of the connection.
|
XID
|
Enabled or disabled: Shows whether XID processing is enabled on the SDLC side of the connection. If enabled, it will show the XID value for this address.
|
Example with X.25
The following is partial sample output from the show interfaces serial command for a serial X.25 interface:
Router# show interfaces serial 1
X25 address 000000010100, state R1, modulo 8, idle 0, timer 0, nvc 1
Window size: input 2, output 2, Packet size: input 128, output 128
Timers: T20 180, T21 200, T22 180, T23 180, TH 0
Channels: Incoming-only none, Two-way 1-1024, Outgoing-only none
(configuration on RESTART: modulo 8,
Window size: input 2 output 2, Packet size: input 128, output 128
Channels: Incoming-only none, Two-way 5-1024, Outgoing-only none)
RESTARTs 3/2 CALLs 1000+2/1294+190/0+0/ DIAGs 0/0
The stability of the X.25 protocol requires that some parameters not be changed without a restart of the protocol. Any change to these parameters is held until a restart is sent or received. If any of these parameters changes, information about the router configuration at restart will be displayed as well as the values that are currently in effect.
Table 68 describes significant fields shown in the display.
Table 68 show interfaces serial Field Descriptions—X.25 Enabled
Field
|
Description
|
X25 address
|
Address used to originate and accept calls.
|
state
|
State of the interface. Possible values follow:
•R1 is the normal ready state.
•R2 is the DTE restarting state.
•R3 is the DCE restarting state.
If the state is R2 or R3, the interface is awaiting acknowledgment of a Restart packet.
|
modulo
|
Modulo value; determines the packet sequence numbering scheme used.
|
idle
|
Number of minutes for which the Cisco IOS software waits before closing idle virtual circuits that it originated or accepted.
|
timer
|
Value of the interface timer, which is zero unless the interface state is R2 or R3.
|
nvc
|
Default maximum number of simultaneous virtual circuits permitted to and from a single host for a particular protocol.
|
Window size: input, output
|
Default window sizes (in packets) for the interface. The x25 facility interface configuration command can be used to override these default values for the switched virtual circuits originated by the router.
|
Packet size: input, output
|
Default maximum packet sizes (in bytes) for the interface. The x25 facility interface configuration command can be used to override these default values for the switched virtual circuits originated by the router.
|
Timers:
|
Values of the X.25 timers:
•T10 through T13 for a DCE device
•T20 through T23 for a DTE device
|
TH
|
Packet acknowledgment threshold (in packets). This value determines how many packets are received before an explicit acknowledgment is sent. The default value (0) sends an explicit acknowledgment only when the incoming window is full.
|
Channels: Incoming-only, Two-way, Outgoing-only
|
Displays the virtual circuit ranges for this interface.
|
RESTARTs
|
Shows Restart packet statistics for the interface using the format Sent/Received.
|
CALLs
|
Successful calls sent + failed calls/calls received + calls failed/calls forwarded + calls failed. Calls forwarded are counted as calls sent.
|
DIAGs
|
Diagnostic messages sent and received.
|
Example with Accounting Option
The following example illustrates the show interfaces serial command with the accounting option on a Cisco 7500 series routers:
Router# show interfaces serial 1/0 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 7344 4787842 1803 1535774
Appletalk 33345 4797459 12781 1089695
Table 69 describes the fields shown in the display.
Table 69 show interfaces serial Field Descriptions—Accounting
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
Example with Cisco AS5800 Access Server
The following example shows the activity that occurred on the serial interface in shelf 1, slot 4, port 0 for time slot 2 in group 23:
Router# show interfaces serial 1/4/0:2:23
Serial1/4/0:2:23 is up, line protocol is up (spoofing)
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters 22:24:30
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5274 packets input, 20122 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5274 packets output, 30836 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions no alarm present
Timeslot(s) Used:24, subrate: 64Kb/s, transmit delay is 0 flags
Table 70 describes the significant fields shown in the display that are different from the fields described in Table 56.
Table 70 show interfaces serial Command Field Descriptions—Cisco AS5800
Field
|
Description
|
Last clearing of "show interface" counters
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) were last reset to zero.
|
Queueing strategy
|
Displays the type of queueing configured for this interface. In the example output, the type of queueing configured is FIFO.
|
throttles
|
Number of times that the receiver on the port was disabled, possibly because of buffer or processor overload.
|
output buffer failures
|
Number of times that the output buffer has failed.
|
output buffer swapped out
|
Number of times that the output buffer has been swapped out.
|
Timeslot(s) Used
|
Number of time slots assigned to the T1 channel.
|
subrate
|
Bandwidth of each time slot.
|
transmit delay is ...
|
Number of idle flags inserted between each frame.
|
Related Commands
Command
|
Description
|
show controllers serial
|
Displays information about the virtual serial interface.
|
show interfaces tokenring
To display information about the Token Ring interface and the state of source route bridging, use the show interfaces tokenring command in privileged EXEC mode.
Standard Syntax
show interfaces tokenring number [accounting]
Cisco 7200 and Cisco 7500 Series
show interfaces tokenring slot/port [accounting]
Cisco 7500 Series with Ports on VIPs
show interfaces tokenring [slot/port-adapter/port]
Syntax Description
number
|
Interface port line number.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
slot
|
On the Cisco 7000 series routers, slot location of the interface processor. On the Cisco 7000, the value can be 0, 1, 2, 3, or 4. On the Cisco 7010, the value can be 0, 1, or 2.
On the Cisco 7200 series routers, slot location of the port adapter; the value can be 1, 2, 3, 4, 5, or 6.
|
/port
|
Port number on the interface. On the Cisco 7000 series routers this argument is required, and the values can be 0, 1, 2, or 3.
(Optional) For the VIP, this argument is optional, and the port value can be 0, 1, 2, or 3 for 4-port Token Ring interfaces.
On the Cisco 7200 series routers, the number depends on the type of port adapter installed.
|
/port-adapter
|
(Optional) On the Cisco 7000 series and Cisco 7500 series routers, specifies the ports on a VIP. The value can be 0 or 1.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.3(3)T
|
The information was modified to include the PA-4R-FDX full-duplex Token Ring port adapter.
|
Usage Guidelines
If you do not provide values for the slot and port arguments, the command displays statistics for all the network interfaces. The optional accounting keyword displays the number of packets of each protocol type that have been sent through the interface.
Examples
The following is sample output from the show interfaces tokenring command:
Router# show interfaces tokenring
TokenRing 0 is up, line protocol is up
Hardware is 16/4 Token Ring, address is 5500.2000.dc27 (bia 0000.3000.072b)
Internet address is 10.136.230.203, subnet mask is 255.255.255.0
MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive set (10 sec)
ARP type: SNAP, ARP Timeout 4:00:00
Single ring node, Source Route Bridge capable
Group Address: 0x00000000, Functional Address: 0x60840000
Last input 0:00:01, output 0:00:01, output hang never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
16339 packets input, 1496515 bytes, 0 no buffer
Received 9895 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
32648 packets output, 9738303 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets, 0 restarts
Table 71 describes the significant fields shown in the displays.
Table 71 show interfaces tokenring Field Descriptions
Field
|
Description
|
Token Ring is {up | down}
|
Interface is either currently active and inserted into ring (up) or inactive and not inserted (down).
On the Cisco 7500 series routers, gives the interface processor type, slot number, and port number.
|
Token Ring is Reset
|
Hardware error has occurred.
|
Token Ring is Initializing
|
Hardware is up, in the process of inserting the ring.
|
Token Ring is Administratively Down
|
Hardware has been taken down by an administrator.
|
line protocol is {up | down | administratively down}
|
Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful).
|
Hardware
|
Hardware type. "Hardware is Token Ring" indicates that the board is a CSC-R board. "Hardware is 16/4 Token Ring" indicates that the board is a CSC-R16 board. Also shows the address of the interface.
|
Internet address
|
Lists the Internet address followed by subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
ARP type
|
Type of Address Resolution Protocol assigned.
|
Ring speed
|
Speed of Token Ring—4 or 16 Mbps.
|
{Single ring | multiring node}
|
Indicates whether a node is enabled to collect and use source routing information (RIF) for routable Token Ring protocols.
|
Group Address
|
Interface's group address, if any. The group address is a multicast address; any number of interfaces on the ring may share the same group address. Each interface may have at most one group address.
|
Functional Address:
|
Bit-significant group address. Each "on" bit represents a function performed by the station.
|
Ethernet Transit OUI:
|
The Organizational Unique Identifier (OUI) code to be used in the encapsulation of Ethernet Type II frames across Token Ring backbone networks.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, drops
Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes input
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the of them medium maximum packet size.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes output
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Since a Token Ring cannot have collisions, this statistic is nonzero only if an unusual event occurred when frames were being queued or dequeued by the system software.
|
interface resets
|
Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
|
restarts
|
Should always be zero for Token Ring interfaces.
|
transitions
|
Number of times the ring made a transition from up to down, or vice versa. A large number of transitions indicates a problem with the ring or the interface.
|
The following is sample output from the show interfaces tokenring command on a Cisco 7500 series routers:
Router# show interfaces tokenring 2/0
TokenRing2/0 is administratively down, line protocol is down
Hardware is cxBus Token Ring, address is 0000.3040.8b4a (bia 0000.3040.8b4a)
MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive set (10 sec)
ARP type: SNAP, ARP Timeout 4:00:00
Single ring node, Source Route Transparent Bridge capable
Ethernet Transit OUI: 0x0000F8
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets, 0 restarts
The following example on the Cisco 7500 series routers includes the accounting option. When you use the accounting option, only the accounting statistics are displayed.
Router# show interfaces tokenring 2/0 accounting
Protocol Pkts In Chars In Pkts Out Chars Out
IP 7344 4787842 1803 1535774
Appletalk 33345 4797459 12781 1089695
Table 72 describes the fields shown in the display.
Table 72 show interfaces tokenring Field Descriptions—Accounting
Field
|
Description
|
Protocol
|
Protocol that is operating on the interface.
|
Pkts In
|
Number of packets received for that protocol.
|
Chars In
|
Number of characters received for that protocol.
|
Pkts Out
|
Number of packets transmitted for that protocol.
|
Chars Out
|
Number of characters transmitted for that protocol.
|
show interfaces tunnel
To list tunnel interface information, use the show interfaces tunnel command in privileged EXEC mode.
show interfaces tunnel number [accounting]
Syntax Description
number
|
Port line number.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show interfaces tunnel command:
Router# show interfaces tunnel 4
Tunnel4 is up, line protocol is down
Hardware is Routing Tunnel
MTU 1500 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255
Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)
Tunnel source 0.0.0.0, destination 0.0.0.0
Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/0, 0 drops; input queue 0/75, 0 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
Table 73 describes significant fields shown in the display.
Table 73 show interfaces tunnel Field Descriptions
Field
|
Description
|
Tunnel is {up | down}
|
Interface is currently active and inserted into ring (up) or inactive and not inserted (down).
On the Cisco 7500 series routers, gives the interface processor type, slot number, and port number.
|
line protocol is {up | down | administratively down}
|
Shows line protocol up if a valid route is available to the tunnel destination. Shows line protocol down if no route is available, or if the route would be recursive.
|
Hardware
|
Specifies the hardware type.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method is always TUNNEL for tunnels.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Tunnel source
|
IP address used as the source address for packets in the tunnel.
|
destination
|
IP address of the host destination.
|
Tunnel protocol
|
Tunnel transport protocol (the protocol the tunnel is using). This is based on the tunnel mode command, which defaults to GRE.
|
key
|
ID key for the tunnel interface, unless disabled.
|
sequencing
|
Indicates whether the tunnel interface drops datagrams that arrive out of order. Can be disabled.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
Last output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Output queue, drops
Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of them medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of a station transmitting bad data.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.
|
abort
|
Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. Some collisions are normal. However, if your collision rate climbs to around 4 or 5 percent, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
|
restarts
|
Number of times that the controller was restarted because of errors.
|
Related Commands
Command
|
Description
|
show ip interface
|
Displays the statistical information specific to a serial interface.
|
show interfaces vg-anylan
To display the information about the 100VG-AnyLAN port adapter on Cisco 7200 series routers and Cisco 7500 series routers, use the show interfaces vg-anylan command in user EXEC or privileged EXEC mode.
Cisco 7200 Series
show interfaces vg-anylan [slot/port]
Cisco 7500 Series with VIPs
show interfaces vg-anylan [slot/port-adapter/port]
Syntax Description
slot
|
(Optional) Slot number. Refer to the appropriate hardware manual for slot and port information.
|
port
|
(Optional) Port number. Refer to the appropriate hardware manual for slot and port information.
|
port-adapter
|
(Optional) Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Examples
The following is sample output from the show interfaces vg-anylan command:
Router# show interfaces vg-anylan 3/0/0
VG-AnyLAN3/0/0 is up, line protocol is up
Hardware is cyBus VG-AnyLAN Interface
Frame type is 802.3, address is 0060.3e64.2460 (bia 0060.3e64.2460)
Internet address is 10.1.1.5/16
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:26, output 00:00:09, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5316 packets input, 857349 bytes, 0 no buffer
Received 5310 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
7920 packets output, 754259 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
0 vg alignment error, 0 vg balance error
0 vg invalid ipm error, 0 vg symbol error
0 vg skew error, 0 vg frame delimit error
0 vg high priority packets, 0 vg high priority octets
0 output errors, 0 collisions, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
0 vg alignment error, 0 vg balance error
0 vg invalid ipm error, 0 vg symbol error
0 vg skew error, 0 vg frame delimit error
0 vg high priority packets, 0 vg high priority octets
Table 74 describes significant fields shown in the display.
Table 74 show interfaces vg-anylan Field Descriptions
Field
|
Description
|
VG-AnyLAN3/0/0 is up, line protocol is up
|
Indicates if the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator.
|
Hardware is cyBus VG-AnyLAN
|
Hardware type.
|
Frame type is 803.2
|
Currently the frame type supported is 803.2.
|
Internet address
|
Internet address and subnet mask.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface, in kilobits per second.
|
DLY
|
Delay of the interface, in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to the interface.
|
loopback
|
Indicates if loopbacks are set.
|
keepalive
|
Indicates if keepalives are set.
|
ARA type
|
ARP type on the interface.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
|
Queueing strategy
|
First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).
|
Output queue, drops
input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.
|
5 minute input rate
5 minute output rate
|
Average number of bits and packets received or transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes (input)
|
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the minimum packet size of the medium.
|
giants
|
Number of packets that are discarded because they exceed the maximum packet size of the medium.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
|
abort
|
Illegal sequence of one bits on the interface.
|
input packets with dribble condition detected
|
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes (output)
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.
|
output buffer failures
|
Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory.
|
output buffers swapped out
|
Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty.
|
vg alignment error
|
Number of nonoctets received.
|
vg balance error
|
Number of incorrect balanced symbols received.
|
vg invalid ipm error
|
Number of packets received with an invalid packet marker (IPM).
|
vg symbol error
|
Number of symbols received that were not correctly decoded.
|
vg skew error
|
Number of skews between four pairs of twisted-pair wire that exceeded the allowable skew.
|
vg frame delimit error
|
Number of start-of-frame errors or false-start errors received.
|
vg high priority packets
|
Number of high-priority packets received.
|
vg high priority octets
|
Number of high-priority octets received.
|
Related Commands
Command
|
Description
|
interface vg-anylan
|
Specifies the interface on a 100VG-AnyLAN port adapter and enters interface configuration mode on Cisco 7200 series routers and Cisco 7500 series routers.
|
show ipc
To display interprocess communication (IPC) statistics, use the show ipc command in privileged EXEC mode.
show ipc {nodes | ports [open] | queue | status [cumulative]}
Syntax Description
nodes
|
Displays participating nodes.
|
ports
|
Displays local and registered IPC ports.
|
open
|
(Optional) Displays local IPC ports that have been opened by the current seat (node).
|
queue
|
Displays information about the IPC retransmission queue and IPC message queue.
|
status
|
Displays the status of the local IPC server.
|
cumulative
|
(Optional) Displays cumulative totals for the status counters of the local IPC server since the router was rebooted.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(12c)EW
|
This command was introduced.
|
12.2(15)T
|
The cumulative keyword was added.
|
Usage Guidelines
The Cisco IOS version of IPC provides a reliable ordered delivery of messages using an underlying platform driver transport or UDP transport protocol.
Nodes
A node (referred to as a seat) is an intelligent element like a processor that can communicate using IPC services. A seat is where entities and ports reside. A seat manager performs all the interprocessor communications by receiving messages from the network and forwarding the messages to the appropriate port.
Ports
IPC communication endpoints (ports) receive and queue received IPC messages.
Queue
Use the queue keyword to display information about the IPC retransmission queue and the IPC message queue.
Status
Use the status keyword to display the IPC statistics generated after a clear ipc statistics command has been entered. The show ipc status command with the cumulative keyword displays the IPC statistics gathered since the router was rebooted, regardless of how many times the statistics have been cleared.
Examples
The following is sample output from the show ipc command with the nodes keyword displaying the participating seats (nodes):
There are 3 nodes in this IPC realm.
ID Type Name Last Sent Last Heard
10000 Local IPC Master 0 0
2010000 Local GALIOS IPC:Card 1 0 0
2020000 Ethernet GALIOS IPC:Card 2 12 26
Table 75 describes the significant fields shown in the display.
Table 75 show ipc nodes Field Descriptions
Field
|
Description
|
ID
|
Port ID.
|
Type
|
Type of seat (node).
|
Name
|
Seat name.
|
Last Sent
|
Sequence number of the message that was last sent.
|
Last Heard
|
Sequence number of the in-sequence message that was last heard.
|
The following is sample output from the show ipc command with the ports keyword displaying the local and registered IPC ports:
There are 11 ports defined.
Port ID Type Name (current/peak/total)
10000.1 unicast IPC Master:Zone
10000.2 unicast IPC Master:Echo
10000.3 unicast IPC Master:Control
10000.4 unicast Remote TTY Server Port
10000.5 unicast GALIOS RF :Active
index = 0 seat_id = 0x2020000 last sent = 0 heard = 1635 0/1/1635
10000.6 unicast GALIOS RED:Active
index = 0 seat_id = 0x2020000 last sent = 0 heard = 2 0/1/2
2020000.3 unicast GALIOS IPC:Card 2:Control
2020000.4 unicast GALIOS RFS :Standby
2020000.5 unicast Slave: Remote TTY Client Port
2020000.6 unicast GALIOS RF :Standby
2020000.7 unicast GALIOS RED:Standby
RPC packets: current/peak/total
Table 76 describes the significant fields shown in the display.
Table 76 show ipc ports Field Descriptions
Field
|
Description
|
Port ID
|
Port ID.
|
Type
|
Type of port.
|
Name
|
Port name.
|
current/peak/total
|
Displays information about the number of messages held by this IPC session.
|
The following is sample output from the show ipc command with the queue keyword displaying information about the IPC retransmission queue:
There are 0 IPC messages waiting for acknowledgement in the transmit queue.
There are 0 IPC messages waiting for a response.
There are 0 IPC messages waiting for additional fragments.
There are 0 IPC messages currently on the IPC inboundQ.
There are 0 messages currently in use by the system.
The following is sample output from the show ipc command with the status keyword displaying information about the local IPC server:
Time last IPC stat cleared : never
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 189 70
Total Protocol Control Frames 70 44
Total via Unreliable Connection-Less Service 145 0
Total via Unreliable Sequenced Connection-Less Svc 0 0
Total via Reliable Connection-Oriented Service 44 70
Total Acknowledgements 70 44
Total Negative Acknowledgements 0 0
Total via Local Driver 0 0
Total via Platform Driver 0 70
Total Frames Dropped by Platform Drivers 0 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Out-of-Sequence Frame 0 Tx Test Drop 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
Table 77 describes the significant fields shown in the display.
Table 77 show ipc status Field Descriptions
Field
|
Description
|
Time last IPC stat cleared
|
Displays time, in dd:hh:mm, since the IPC statistics were last cleared.
|
This processor is
|
Shows whether the processor is the IPC master or an IPC slave.
|
IPC Message Headers Cached
|
Number of message headers available in the IPC message cache.
|
Rx Side
|
Information about IPC messages received.
|
Tx Side
|
Information about IPC messages sent.
|
Service Usage
|
Number of IPC messages received or sent via connectionless or connection-oriented protocols.
|
IPC Protocol Version 0
|
Number of acknowledgements and negative acknowledgements received or sent by the system.
|
Device Drivers
|
Number of IPC messages received or sent using the underlying device drivers.
|
Reliable Tx Statistics
|
Number of IPC messages that were retransmitted or that timed out on retransmission using a reliable connection-oriented protocol.
|
Rx Errors
|
Number of IPC messages received that displayed various internal frame or delivery errors.
|
Tx Errors
|
Number of IPC messages sent that displayed various transmission errors.
|
Buffer Errors
|
Number of message allocation failures from the IPC message cache, IPC emergency message cache, IPC frame allocation cache, and the IPC frame memory allocation cache.
|
Misc Errors
|
Various miscellaneous errors that relate to the IPC open queue, or to the hardware queue, or to other hardware failures.
|
Tx Driver Errors
|
Number of messages that relate to IPC transmission driver failures including messages to or from a destination without a valid transport entity from the seat; number of messages dropped because packet size is larger than the maximum transmission unit (MTU); and number of messages without a valid destination address.
|
The following example shows how to display cumulative IPC counters for the local IPC server. Note that the recent IPC clearing has not cleared the IPC counters because the cumulative keyword displays the IPC statistics generated since the router was rebooted.
Router# show ipc status cumulative
Time last IPC stat cleared : 00:00:05
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 3473 92
Total Protocol Control Frames 92 54
Total via Unreliable Connection-Less Service 2449 0
Total via Unreliable Sequenced Connection-Less Svc 970 0
Total via Reliable Connection-Oriented Service 54 92
Total Acknowledgements 0 0
Total Negative Acknowledgements 0 0
Total via Local Driver 0 0
Total via Platform Driver 0 92
Total Frames Dropped by Platform Drivers 0 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Out-of-Sequence Frame 0 Tx Test Drop 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
Related Commands
Command
|
Description
|
clear ipc statistics
|
Clears and resets the IPC statistics.
|
show ip interface
To display the usability status of interfaces configured for IP, use the show ip interface command in privileged EXEC mode.
show ip interface [type number] [brief]
Syntax Description
type
|
(Optional) Interface type.
|
number
|
(Optional) Interface number.
|
brief
|
(Optional) Displays a summary of the usability status information for each interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(3)T
|
This command was expanded to include the status of ip wccp redirect out and ip wccp redirect exclude add in commands.
|
12.2(14)S
|
This command was expanded to display the status of NetFlow on a subinterface.
|
12.2(15)T
|
The command output enhancements introduced in Cisco IOS Release 12.2(14)S were integrated into Cisco IOS Release 12.2(15)T.
|
12.3(6)
|
The command output was modified to identify the downstream VRF in the output.
|
12.3(11)T
|
This command was integrated into Cisco IOS Release 12.3(11)T.
|
12.3(14)YM2
|
This command was modified to show the usability status of interfaces configured for Multi-Processor Forwarding (MPF) and implemented on the Cisco 7301 and Cisco 7206VXR routers.
|
12.4(4)T
|
This command was integrated into Cisco IOS Release 12.4(4)T.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
Usage Guidelines
The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable. A usable interface can send and receive packets. If an interface is not usable, the directly connected routing entry is removed from the routing table. Removing the entry allows the software to use dynamic routing protocols to determine backup routes to the network, if any.
If the interface can provide two-way communication, the line protocol is marked "up." If the interface hardware is usable, the interface is marked "up."
If you specify an optional interface type, you see information for that specific interface.
If you specify no optional arguments, you see information on all the interfaces.
When an asynchronous interface is encapsulated with PPP or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
The show ip interface brief command can be used to view a summary of the router interfaces. This command displays the IP address, interface status, and additional information.
Examples
The following examples from Cisco IOS Release 12.3(14)YM2 show:
•Configuration information on interface Gigabit Ethernet0/3, where the IP flow egress feature is configured on the output side (where packets go out of the interface) and the policy route-map named PBR_NAME is configured on the input side (where packets come into the interface).
•Interface information on Gigabit Ethernet interface 0/3 showing that MPF is enabled and that both features are not supported by MPF and are ignored.
The highlighted arrows (for documentation purposes only) show the configured output and input features and the additional MPF interface information.
Router# show running-config interface g 0/3
interface GigabitEthernet0/3
ip address 10.1.1.1 255.255.0.0
ip flow egress <== output
ip policy route-map PBR_NAME <== input
Router# show ip interface g 0/3
GigabitEthernet0/3 is up, line protocol is up
Internet address is 10.1.1.1/16
Broadcast address is 255.255.255.255
Address determined by setup command
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP CEF switching is enabled
IP Feature Fast switching turbo vector
IP VPN Flow CEF switching turbo vector
IP multicast fast switching is enabled
IP multicast distributed fast switching is disabled
IP route-cache flags are Fast, CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Policy routing is enabled, using route map PBR
Network address translation is disabled
BGP Policy Mapping is disabled
IP Multi-Processor Forwarding is enabled <======== MPF information
IP Input features, "PBR",
are not supported by MPF and are IGNORED
IP Output features, "NetFlow",
are not supported by MPF and are IGNORED
The following example identifies a downstream VRF. The highlighted line (for documentation purposes only) identifies the downstream VRF.
Router# show ip interface vi 3
Virtual-Access3 is up, line protocol is up
Interface is unnumbered. Using address of Loopback2 (10.0.0.8)
Broadcast address is 255.255.255.255
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is enabled
IP Flow switching is disabled
IP CEF switching is enabled
IP Feature Fast switching turbo vector
IP VPN CEF switching turbo vector
VPN Routing/Forwarding "U"
Downstream VPN Routing/Forwarding "D"
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
IP route-cache flags are Fast, CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
Table 78 describes the significant fields shown in the display.
Table 78 show ip interface Field Descriptions
Field
|
Description
|
Virtual-Access3 is up
|
If the interface hardware is usable, the interface is marked "up." For an interface to be usable, both the interface hardware and line protocol must be up.
|
Broadcast address is
|
Displays the broadcast address.
|
Peer address is
|
Displays the peer address.
|
MTU is
|
Displays the MTU value set on the interface.
|
Helper address
|
Displays a helper address, if one has been set.
|
Directed broadcast forwarding
|
Indicates whether directed broadcast forwarding is enabled.
|
Outgoing access list
|
Indicates whether the interface has an outgoing access list set.
|
Inbound access list
|
Indicates whether the interface has an incoming access list set.
|
Proxy ARP
|
Indicates whether Proxy Address Resolution Protocol (ARP) is enabled for the interface.
|
Security level
|
Specifies the IP Security Option (IPSO) security level set for this interface.
|
Split horizon
|
Indicates that split horizon is enabled.
|
ICMP redirects
|
Specifies whether redirect messages will be sent on this interface.
|
ICMP unreachables
|
Specifies whether unreachable messages will be sent on this interface.
|
ICMP mask replies
|
Specifies whether mask replies will be sent on this interface.
|
IP fast switching
|
Specifies whether fast switching has been enabled for this interface. It is generally enabled on serial interfaces, such as this one.
|
IP Flow switching
|
Specifies whether Flow switching is enabled for this interface.
|
IP CEF switching
|
Specifies whether Cisco Express Forwarding is enabled for the interface.
|
Downstream VPN Routing/Forwarding "D"
|
Specifies the VRF where the PPP peer routes and AAA per-user routes are being installed.
|
IP multicast fast switching
|
Specifies whether multicast fast switching is enabled for the interface.
|
IP route-cache flags are Fast, Flow init, CEF, Ingress Flow
|
Specifies whether NetFlow has been enabled on an interface. Displays "Flow init" to specify that NetFlow is enabled on the interface. Displays "Ingress Flow" to specify that NetFlow is enabled on a subinterface using the ip flow ingress command. Specifies "Flow" to specify that NetFlow is enabled on a main interface using the ip route-cache flow command.
|
Router Discovery
|
Specifies whether the discovery process has been enabled for this interface. It is generally disabled on serial interfaces.
|
IP output packet accounting
|
Specifies whether IP accounting is enabled for this interface and what the threshold (maximum number of entries) is.
|
TCP/IP header compression
|
Indicates whether compression is enabled or disabled.
|
WCCP Redirect outbound is disabled
|
Indicates the status of whether packets received on an interface are redirected to a cache engine. Displays "enabled" or "disabled."
|
WCCP Redirect exclude is disabled
|
Indicates the status of whether packets targeted for an interface will be excluded from being redirected to a cache engine. Displays "enabled" or "disabled."
|
The following is sample output from the show ip interface brief command:
Router# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Ethernet0 10.108.00.5 YES NVRAM up up
Ethernet1 unassigned YES unset administratively down down
Loopback0 10.108.200.5 YES NVRAM up up
Serial0 10.108.100.5 YES NVRAM up up
Serial1 10.108.40.5 YES NVRAM up up
Serial2 10.108.100.5 YES manual up up
Serial3 unassigned YES unset administratively down down
Table 79 show ip interface brief Field Descriptions
Field
|
Description
|
Interface
|
Type of interface.
|
IP-Address
|
IP Address assigned to the interface.
|
OK?
|
"Yes" means that the IP Address is currently valid. "No" means that the IP Address is not currently valid.
|
Method
|
The method field has the following possible values:
•RARP or SLARP—Reverse Address Resolution Protocol (RARP) or Serial Line Address Resolution Protocol (SLARP) request
•BOOTP—Bootstrap protocol
•TFTP—Configuration file obtained from TFTP server
•manual—Manually changed by CLI command
•NVRAM—Configuration file in NVRAM
•IPCP—ip address negotiated command
•DHCP—ip address dhcp command
•unassigned—No IP address
•unset—Unset
•other—Unknown
|
Status
|
Indicates the status of interface. Valid values and their meanings are:
•up—Interface is administratively up.
•down—Interface is administratively down.
•administratively down—Interface is administratively down.
|
Protocol
|
Indicates the operational status of the routing protocol on this interface.
|
Related Commands
Command
|
Description
|
ip address
|
Sets a primary or secondary IP address for an interface.
|
ip vrf autoclassify
|
Enables VRF autoclassify on a source interface.
|
match ip source
|
Specifies a source IP address to match to required route maps that have been set up based on VRF connected routes.
|
route-map
|
Defines the conditions for redistributing routes from one routing protocol into another, or to enable policy routing.
|
set vrf
|
Enables VPN VRF selection within a route map for policy-based routing VRF selection.
|
show ip arp
|
Displays the ARP cache, in which SLIP addresses appear as permanent ARP table entries.
|
show route-map
|
Displays static and dynamic route maps.
|
show ipc hog-info
To provide information about interprocess communication (IPC) messages that consume excessive CPU, use the show ipc hog-info command in privileged EXEC mode.
show ipc hog-info
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The Cisco IOS version of IPC provides a reliable ordered delivery of messages using an underlying platform driver transport or User Datagram Protocol (UDP) transport protocol.
The show ipc hog-info command displays information about IPC messages that are being processed when a CPUHOG error occurs, indicating that the client processing an IPC message is using too much CPU, or when an IPC message callback exceeds 200 milliseconds.
Examples
The following example shows that the IPC process has had a CPUHOG error or the message callback exceeded the 200-millisecond threshold:
Router# show ipc hog-info
Time last IPC process hogged CPU: 00:05:09
Source Destination Name Message-Type Time-taken
1030000 10000.14 ISSU Process: Active Por 0 864
1030000 10000.D RF : Active 0 0
In the following example, the show ipc status command shows a counter incrementing whenever a callback exceeds 200 milliseconds:
Time last IPC stat cleared : never
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 14328 3258
Total Protocol Control Frames 1628 713
Total via Unreliable Connection-Less Service 7865 0
Total via Unreliable Sequenced Connection-Less Svc 0 0
Total via Reliable Connection-Oriented Service 831 1629
Total Acknowledgments 1628 713
Total Negative Acknowledgments 0 0
Total via Local Driver 12 12
Total via Platform Driver 9478 1619
Total Frames Dropped by Platform Drivers 0 0
Total Frames Sent when media is quiesced 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Rel Out-of-Seq Frame 0 Unrel Out-of-Seq Frame 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Rx IPC Frag Dropped 0
Rx IPC Transform Errors 0 Tx IPC Transform Errors 0
Unable to Deliver Msg 0 Tx Test Drop 0
Ctrl Frm Alloc Failed 0 Rx Msg Callback Hog 11
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
IPC Frame MemD Alloc 0 Invalid Messages 0
Related Commands
Command
|
Description
|
show ipc
|
Displays IPC statistics.
|
show pas caim
To show debug information about the data compression Advanced Interface Module (CAIM) daughter card, use the show pas caim command in user EXEC or privileged EXEC mode.
show pas caim {rings | dma | coprocessor | stats | cnxt_table | page_table} element-number
Syntax Description
rings element-number
|
Displays current content of the Direct Memory Access (DMA) ring buffer.
|
dma element-number
|
Displays registers of the Jupiter DMA controller.
|
coprocessor element-number
|
Displays registers of the Hifn 9711 compression coprocessor.
|
stats element-number
|
Displays statistics that describes operation of the data compression Advanced Interface Module (AIM).
|
cnxt_table element-number
|
Displays the context of the specific data compression AIM element.
|
page_table element-number
|
Displays the page table for each CAIM element.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)T
|
This command was introduced.
|
Usage Guidelines
This command displays performance statistics that describe the operation of the CAIM. This command is primarily intended for engineering debug, but it can also be useful to Cisco support personnel and to Cisco customers in troubleshooting network problems. Table 80 lists the output values for this command.
Table 80 show pas caim Output Values and Descriptions
Value
|
Description
|
uncomp paks in
|
Number of packets containing uncompressed data input to the CAIM for compression.
|
comp paks out
|
Number of packets containing uncompressed data that were successfully compressed.
|
comp paks in
|
Number of packets containing compressed data input to the CAIM for compression.
|
uncomp paks out
|
Number of packets containing compressed data that were successfully decompressed.
|
uncomp bytes in / comp bytes out
|
Summarizes the compression performance of the CAIM. The "uncomp bytes in" statistic gives the total number of uncompressed bytes submitted to the CAIM for compression. The "Comp bytes out" statistic gives the resulting number of compressed bytes output by the CAIM. If one forms the ratio of "uncomp bytes in" to "comp bytes out", one obtains the average compression ratio achieved by the CAIM.
|
comp bytes in / uncomp bytes out
|
Summarizes the decompression performance of the CAIM. The "comp bytes in" statistic gives the total number of compressed bytes submitted to the CAIM for decompression. The "uncomp bytes out" statistic gives the resulting number of uncompressed bytes output by the CAIM. The average decompression ratio achieved can be computed as the ratio of "uncomp bytes out" to "comp bytes in".
Note that each packet submitted for compression or decompression has a small header at the front which is always clear data and hence never compressed nor decompressed. The "comp bytes in / uncomp bytes out" and "uncomp bytes in / comp bytes out" statistics do not include this header.
|
uncomp paks/sec in
|
A time average of the number of packets per second containing uncompressed data submitted as input to the CAIM for compression. It is computed as the ratio of the "uncomp paks in" statistic to the "seconds since last clear" statistic.
|
comp paks/sec out
|
A time average of the number of packets per second containing uncompressed data which were successfully compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" statistic.
|
comp paks/sec in
|
A time average of the number of packets per second containing compressed data submitted as input to the CAIM for decompression. It is computed as the ratio of the "comp paks in" statistic to the "seconds since last clear" statistic.
|
uncomp paks/sec out
|
A time average of the number of packets per second containing compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp paks out" statistic to the "seconds since last clear" statistic.
Note that the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics are averages over the entire time since the last "clear count" command was issued. This means that as time progresses, these statistics become averages over an ever larger time interval. As time progresses, these statistics become ever less sensitive to current prevailing conditions. Note also that the "uncomp paks in", "comp paks out", "comp paks in", and "uncomp paks out" statistics are 32-bit counters and can roll over from 0xffff ffff to 0. When they do so, the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics can be rendered meaningless. It is therefore recommend that one issue a "clear count" command before sampling these statistics.
|
uncomp bits/sec in
|
A time average of the number of bits per second of uncompressed data which were submitted to the CAIM for compression. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
|
comp bits/sec out
|
A time average of the number of bits per second of uncompressed data which were successfully compressed by the CAIM. It is computed as the ratio of the "comp bytes out" statistic, times 8, to the "seconds since last clear" statistic.
|
comp bits/sec in
|
A time average of the number of bits per second of compressed data which were submitted to the CAIM for decompression. It is computed as the ratio of the "comp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
|
uncomp bits/sec out
|
A time average of the number of bits per second of compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
Note again that these "bits/sec" statistics are time averages over the "seconds since last clear" statistics, and therefore become less and less sensitive to current conditions as time progresses. Also, these "bits/sec" statistics are computed from 32-bit counters, and when the counters roll over from the maximum 32-bit value to 0, the "bits/sec" statistics become inaccurate. It is again recommended that one issue the "clear count" command before sampling the "bits/sec" statistics.
|
The remaining statistics summarize operational state and error conditions encountered by the CAIM, and have the following interpretations:
|
holdq
|
Gives the number of packets occupying the "hold queue" of the CAIM. The hold queue is a holding area, or "overflow" area, for packets to be processed by the CAIM. Normally, the CAIM is fast enough that no overflow into the hold queue occurs, and so normally this statistic should show zero.
|
hw_enable
|
Flag indicating if the CAIM is disabled or not. Zero implies disabled; one implies enabled. The CAIM can become disabled if certain fatal hardware error conditions are detected. It can be reenabled by issuing the clear aim element-number command.
|
src_limited
|
Flag indicating if the CAIM is in "source limited" mode. In source limited mode, the CAIM can only process a single command at a time. In non source limited mode, the CAIM can process several commands at a time using a pipeline built into the 9711 coprocessor. Note that the normal mode of operation is "non-source limited", and there is no command to place the CAIM in "source limited" mode. Hence, this statistic should always read zero.
|
num cnxts
|
Gives the number of "contexts" which are currently open on the CAIM. Each interface configured for compression opens two contexts, one for each direction of data transfer.
|
no data
|
Counts the number of times in which the CAIM performed either a compress or decompression operation, and the output data length was reported with a length of zero. In normal operation, this statistic should always read zero. A nonzero value is an indication of a malfunctioning CAIM.
|
drops
|
Counts the total number of times in which the CAIM was forced to drop a packet it was asked to compress or decompress. This can happen for a number of reasons, and the remaining statistics summarize these reasons. This statistic indicates that the CAIM is being overloaded with requests for compression/decompression.
|
nobuffers
|
Counts the total number of times the CAIM needed to allocate memory for buffers but could not obtain memory. The CAIM allocates memory for buffers for holding the results of compression or decompression operations. In normal operation, there is plenty of memory available for holding CAIM results. This statistic, if nonzero, indicates that there is a significant backup in memory, or perhaps a memory leak.
|
enc adj errs
|
Each packet compressed or decompressed involves an adjustment of the encapsulation of the packet between the LZS-DCP, FRF9, or MPPC encapsulation used to transport compressed packets to the standard encapsulation used to transport clear data. This statistic counts the number of times this encapsulation adjustment failed. In normal operation, this statistic should be zero. A nonzero value indicates that we are short in a specific memory resource referred to as "paktypes", and that packets are being dropped because of this shortage.
|
fallbacks
|
Number of times the data compression AIM card could not use its pre-allocated buffers to store compression results and had to "fallback" to using a common buffer pool.
|
no replace
|
Each time a compression or decompression operation is completed and the resultant data fill up a buffer, the CAIM software allocates a new buffer to replace the buffer filled. If no buffers are available, then the packet involved in this operation is dropped and the old buffer reused. This statistic thus represents the number of times such an allocation failure occurred. In normal operation there is plenty of memory available for these buffers. A nonzero value for this statistic is thus a serious indication of a memory leak or other backup in buffer usage somewhere in the system.
|
num seq errs
|
This statistic is incremented when the CAIM produces results in a different order than that in which the requests were submitted. Packets involved in such errors are dropped. A nonzero value in this statistic indicates a serious malfunction in the CAIM.
|
num desc errs
|
Incremented when the CAIM reports error in a compression or decompression operation. Such errors are most likely bus errors, and they indicate a serious malfunction in the CAIM.
|
cmds complete
|
Reports the number of compression/decompression commands completed. This statistic should steadily increase in normal operation (assuming that the CAIM is continuously being asked to perform compression or decompression). If this statistic is not steadily increasing or decreasing when a steady stream of compression/decompression is expected, this is an indication of a malfunctioning CAIM.
|
bad reqs
|
Reports the number of compression/decompression requests that the CAIM software determined it could not possibly handle. This occurs only if a severely scattered packet (with more than 64 "particles", or separate buffers of data) is handed to the CAIM to compress or decompress. This statistic should not increment during normal operation. A nonzero value indicates a software bug.
|
dead cntxts
|
Number of times a packet was successfully compressed or decompressed, only to find that the software "context", or stream sourcing the packet, was no longer around. In such a case the packet is dropped. This statistic can be incremented at times when a serial interface is administratively disabled. If the timing is right, the CAIM may be right in the middle of operating on a packet from that interface when the disable takes effect. When the CAIM operation completes, it finds that the interface has been disabled and all "compression contexts" pertaining to that interface have been deleted. Another situation in which this can occur is when a Frame Relay DLC goes down. This is a normal and tolerable. If this statistic is incrementing when no such situations exist, it is an indication of a software bug.
|
no paks
|
If a packet to be compressed or decompressed overflows into the hold queue, then it must undergo an operation called "reparenting". This involves the allocation of a "paktype" structure for the packet. If no paktype structures are available, then the packet is dropped and this statistic is incremented. A nonzero value of this statistic indicates that the CAIM is being overtaxed, that is, it is being asked to compress/decompress at a rate exceeding its capabilities.
|
enq errors
|
Closely related to the "no paks" statistic. The hold queue for the CAIM is limited in length, and if the hold queue grows to this length, no further packets may be placed on it. A nonzero value of this statistic therefore also indicates that the CAIM is being overtaxed.
|
rx pkt drops
|
Contains the total number of packets dropped because of "no paks" or "enq errors", which were destined to be decompressed.
|
tx pkt drops
|
Contains the total number of packets dropped because of "no paks" or "enq errors", which were destined to be compressed
|
dequeues
|
Indicates the total number of packets which were removed from the CAIM hold queue when the CAIM became available for servicing its hold queue.
|
requeues
|
Indicates the total number of packets that were removed from the hold queue, only to find that the necessary CAIM resources were not available (it is not possible to determine whether CAIM resources are available until the packet is dequeued). Such packets are requeued onto the hold queue, with order in the queue preserved.
|
drops disabled
|
Indicates the total number of packets which were submitted for compression or decompression, but that were dropped because the CAIM was disabled.
|
clears
|
Indicates the number of times the CAIM was reset using the clear aim element-number command.
|
# ints
|
Indicates the number of interrupts serviced by the CAIM software. This statistic should steadily increase (assuming that the CAIM workload is steady). If this statistic is not incremented when expected, it indicates a severe CAIM malfunction.
|
# purges
|
Indicates the total number of times the compression history for a session had to be purged. This statistic is incremented a couple of times at startup. Thereafter, any increase in this statistic is an indication that the other side of the serial link detected bad data or gaps in the compressed packets being passed to it, and hence signalled a request to purge compression history in order to get back in synchronization. This can indicate that the CAIM is being overtaxed or that the serial interface is overtaxed and being forced to drop output packets.
|
no cnxts
|
Indicates the total number of times a request was issued to open a context, but the CAIM could not support any more contexts. Recall that two contexts are required for each interface configured for compression.
|
bad algos
|
Indicates the total number of times a request was issued to open a context for a compression algorithm not supported by the CAIM. Recall that the CAIM supports the LZS and MPPC algorithms only.
|
no crams
|
Indicates the total number of times a request was issued to open a context but there was insufficient compression DRAM to open another context. The CAIM software is set up to run out of contexts before it runs out of compression DRAM, so this statistic should always be zero.
|
bad paks
|
Indicates the total number of times a packet was submitted for compression or decompression to the CAIM, but the packet had an invalid size.
|
# opens
|
Indicates the total number of times a context was opened.
|
# closes
|
Indicates the total number of times a context was closed.
|
# hangs
|
Indicates the total number of times a CAIM appeared hung up, necessitating a clear of the CAIM.
|
Examples
The show pas caim rings element-number command displays the current state of the DMA ring buffers maintained by the CAIM software. These rings feed the CAIM with data and commands. It is intended for an engineering debug of the compression AIM. It produces the following output:
Router# show pas caim rings 0
CAIM Command Ring: 0x01A2BC00 Stack: 0x01A2BE40 Shadow: 0x80F88BAC
Head: 0021 Tail: 0021 Count: 0000
CAIM Source Ring: 0x01A2C900 Shadow: 0x80F88BAC
Head: 0021 Tail: 0021 Num: 0000
CAIM Results Ring: 0x01A2C280 Stack: 0x01A2C4C0
CAIM Dest Ring: 0x01A2CB40 Shadow: 0x80F892D8 Head=021 Tail=000
Desc: 0x01A2CBE8 flags: 0x8000060C dptr: 0x019E7EB8 part: 0x80F84BE0
Desc: 0x01A2CBF0 flags: 0x8000060C dptr: 0x019FC63C part: 0x80F85240
Table 81 describes the significant fields shown in the display.
Table 81 show pas caim rings Field Descriptions
Field
|
Description
|
CAIM Command Ring
|
Feeds commands to the CAIM.
|
command ring address
|
Address of the command ring.
|
Command Ring Stack
|
Ring that feeds additional commands to the CAIM.
|
command ring stack address
|
Address of the command ring stack.
|
Command Ring Shadow
|
Software ring that stores additional information about each command.
|
command ring shadow address
|
Address of the command ring shadow.
|
Command Ring Head
|
Index into the Source Ring, specifying where the next entry will be extracted from.
|
Command Ring Tail
|
Index into the Source Ring, specifying where the next entry will be inserted.
|
CAIM Source Ring
|
Feeds information about input data to the CAIM.
|
source ring address
|
Address of the source ring.
|
Source Ring Shadow
|
Ring that contains additional information about each source buffer.
|
source ring shadow address
|
Address of the source ring shadow.
|
Source Ring Head
|
Specifies where the next entry will be extracted from.
|
Source Ring Tail
|
Specifies where the next entry will be inserted.
|
CAIM Results Ring
|
Receives information about each CAIM command as it is completed.
|
results ring address
|
Address of the results ring.
|
Results Ring Stack
|
Ring that receives additional information about each completed command.
|
results ring stack address
|
Address of the results ring stack.
|
Results Ring Head
|
Specifies where the next entry will be extracted from.
|
Results Ring Tail
|
Specifies where the next entry will be inserted.
|
CAIM Dest Ring
|
Holds information about the buffers available to the CAIM for output data.
|
dest ring address
|
Address of the dest ring.
|
Dest Ring Shadow
|
Ring that holds additional information about each output buffer.
|
dest ring shadow address
|
Address of the dest ring shadow.
|
Dest Ring Head
|
Index into the Source Ring, specifying where the next entry will be extracted from.
|
Dest Ring Tail
|
Index into the Source Ring, specifying where the next entry will be inserted.
|
The remaining fields describe each output data buffer.
|
dest
|
Address of a so-called descriptor, used by the Jupiter DMA engine.
|
flags
|
Contains flags describing attributes of the buffer.
|
dptr
|
Displays the actual address of the output buffer.
|
part
|
Displays the address of the corresponding particle type structure, a software-defined structure that describes a buffer when it is a component of a network data buffer.
|
The show pas caim dma element-number command displays the registers of the Jupiter DMA Controller. These registers control the operation of the Jupiter DMA Controller. This command is intended for Engineering debug of the CAIM. You can find detailed descriptions of the various fields in the Jupiter DMA Controller specification. It produces the following output:
Router# show pas caim dma 0
Jupiter DMA Controller Registers: (0x40200000
Cmd Ring: 0x01A2BCA8 Src Ring: 0x01A2C9A8
Res Ring: 0x01A2C328 Dst Ring: 0x01A2CBE8
Status/Cntl: present: 0x80808084 last int: 0x80808084
Inten: 0x10100000 config: 0x00100003
The show pas caim compressor element-number command displays the registers of the Hifn 9711 compression coprocessor. These registers control the operation of the Hifn 9711 part. This command is intended for engineering to debug the CAIM. Detailed descriptions of the various fields may be found in the Hifn 9711 data book. It produces the following output:
Router# show pas caim compressor 0
Hifn9711 Data Compression Coprocessor Registers (0x40201000):
Config: 0x000051D4 Inten: 0x00000E00
Status: 0x00004000 FIFO status: 0x00004000
Table 82 describes the fields shown in the preceding display.
Table 82 show pas caim compressor Field Descriptions
Field
|
Description
|
Hifn9711 Data Compression Coprocessor Registers
|
Controls the operation of the Hifn 9711 part.
|
registers address
|
Address of the registers in the address space of the processor.
|
Config
|
Displays the current contents of the 9711 configuration register.
|
Inten
|
Displays the contents of the 9711 interrupt enable register.
|
Status
|
Displays the contents of the 9711 status register.
|
FIFO status
|
Contents of the 9711 FIFO Status register.
|
FIFO config
|
Contents of the 9711 FIFO Config register.
|
The show pas caim cnxt_table element-number command displays the context table for the specified CAIM element. The context table is a table of information concerning each compression context. It produces the following output:
Router# show pas caim cnxt_table 0
Context: 0x8104F320 Type: Compr Algo: Stac
Hdrlen: 0006 History: 0x0000
Callback: 0x8011D68C Shutdown: x8011EBE4 Purge: N
Comp_db: 0x81034BC0 idb: 0x81038084 ds: 0x8104E514
Context: 0x8104F340 Type: Decomp Algo: Stac
Hdrlen: 0002 History: 0x0000
Callback: 0x8011E700 Shutdown: x8011EBE4 Purge: N
Comp_db: 0x81034BC0 idb: 0x81038084 ds: 0x8104E514
Table 83 describes the fields shown in the preceding display.
Table 83 show pas caim cnxt_table Fields Descriptions
Field
|
Description
|
Context
|
Numeric internal reference for the compression context.
|
Type
|
Gives the type of context:
•Compr—compression context
•Decomp—decompression context
|
Algo
|
Gives the compression algorithm used:
•Stac
•Mppc
|
Hdrlen
|
Gives the number of bytes in the compression header for each compressed packet.
|
History
|
Gives the 16-KB page number in compression RAM for the context.
|
Callback
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Shutdown
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Comp_db
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
idb
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
idb
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Purge
|
Indicates whether the compression context has been flagged to have its history purged.
|
The show pas caim page_table element-number command displays the page table for the selected CAIM element. The page table is a table of entries describing each page in compression RAM. It produces the following output:
Router# show pas caim page_table 0
Page 0x0000 Comp cnxt: 8104F320 Decmp cnxt: 8104F340 Algo: Stac
Table 84 describes the fields shown in the preceding display.
Table 84 show pas caim page_table Field Descriptions
Field
|
Description
|
Page
|
16 KB page number of the page.
|
Comp cnxt
|
Contains an internal numeric reference to the context structures using this page.
|
Decmp cnxt
|
Contains an internal numeric reference to the context structures using this page.
|
Algo
|
Gives the compression algorithm used:
•Stac
•Mppc
|
The following example shows statistics of an active data compression AIM session:
Router# show pas caim stats 0
ds:0x80F56A44 idb:0x80F50DB8
422074 uncomp paks in --> 422076 comp paks out
422071 comp paks in --> 422075 uncomp paks out
633912308 uncomp bytes in--> 22791798 comp bytes out
27433911 comp bytes in --> 633911762 uncomp bytes out
974 uncomp paks/sec in--> 974 comp paks/sec out
974 comp paks/sec in --> 974 uncomp paks/sec out
11739116 uncomp bits/sec in--> 422070 comp bits/sec out
508035 comp bits/sec in --> 11739106 uncomp bits/sec out
433 seconds since last clear
holdq: 0 hw_enable: 1 src_limited: 0 num cnxts: 4
no data: 0 drops: 0 nobuffers: 0 enc adj errs: 0 fallbacks: 0
no Replace: 0 num seq errs: 0 num desc errs: 0 cmds complete: 844151
Bad reqs: 0 Dead cnxts: 0 No Paks: 0 enq errs: 0
rx pkt drops: 0 tx pkt drops: 0 dequeues: 0 requeues: 0
drops disabled: 0 clears: 0 ints: 844314 purges: 0
no cnxts: 0 bad algos: 0 no crams: 0 bad paks: 0
# opens: 0 # closes: 0 # hangs: 0
Related Commands
Command
|
Description
|
show compress
|
Displays compression statistics.
|
show pas eswitch address
To display the Layer 2 learned addresses for an interface, use the show pas eswitch address command in user EXEC or privileged EXEC mode.
show pas eswitch address [ethernet | fastethernet] [slot/port]
Syntax Description
ethernet | fastethernet
|
(Optional) Type of interface.
|
slot
|
(Optional) Slot number of the interface.
|
port
|
(Optional) Interface number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2 P
|
This command was introduced.
|
Examples
The following sample output shows that the first PA-12E/2FE interface (listed below as port 0) in port adapter slot 3 has learned the Layer 2 address 00e0.f7a4.5100 for bridge group 30 (listed below as BG 30):
Router# show pas eswitch address fastethernet 3/0
U 00e0.f7a4.5100, AgeTs 56273 s, BG 30 (vLAN 0), Port 0
show pas isa controller
To show controller information that is specific to the Virtual Private Network (VPN) accelerator controller when an Integrated Services Adapter (ISA) is installed, use the show pas isa controller EXEC command.
show pas isa controller
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Examples
The following is sample output from the show pas isa controller command:
Router# show pas isa controller
Addresses of Rings and instance structure:
TX: 0x4B0E97C0 TX Shadow:0x62060E00
RX: 0x4B0EB840 RX Pool:0x4B0EBC80 RX Pool Shadow:0x62068E58
TX: 0x4B0EA800 TX Shadow:0x62066E2C
RX: 0x4B0EC0C0, RX Shadow:0x62069284
Instance Structure address:0x620603D8
Firmware write head/tail offset:0x4B0EC900
Firmware read head/tail offset:0x3EA00000
Related Commands
Command
|
Description
|
show pas isa interface
|
Displays interface status information that is specific to the VPN accelerator card.
|
show pas isa interface
To display interface information that is specific to the Virtual Private Network (VPN) accelerator card when an Integrated Services Adapter (ISA) is installed, use the show pas isa interface command in privileged EXEC mode.
show pas isa interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Examples
The following is sample output from the show pas isa interface command:
Router# show pas isa interface
Statistics of packets and bytes through this interface:
2876894 packets in 2910021 packets out
420 paks/sec in 415 paks/sec out
2327 Kbits/sec in 2408 Kbits/sec out
632 commands out 632 commands acknowledged
low_pri_pkts_sent 1911 low_pri_pkts_rcvd: 1911
invalid_sa: 260 invalid_flow: 33127
invalid_dh: 0 ah_seq_failure: 0
ah_spi_failure: 0 esp_auth_failure: 0
esp_seq_failure: 0 esp_spi_failure: 0
esp_protocol_absent: 0 ah_protocol_absent: 0
bad_key_group: 0 no_shared_secret: 0
no_skeyids: 0 pad_size_error: 0
cmd_ring_full: 0 bulk_ring_full: 990
bad_peer_pub_len: 0 authentication_failure: 0
fallback: 1606642 no_particle: 0
6922 seconds since last clear of counters
Table 85 describes the significant fields shown in the display.
Table 85 show pas isa interface Field Descriptions
Field
|
Description
|
packets in/out
|
Number of data packets received from, or sent to, the Integrated Service Adapter (ISA).
|
paks/sec in/out
|
Number of packets received in, or sent out, with the total number of seconds that the ISA is active.
|
Kbits/sec in/out
|
Number of kilobits (Kbits) received in, or sent out, with the total number of seconds that the ISA is active.
|
commands out
|
Number of commands going to the ISA. Examples of commands include setting up encryption sessions and retrieving statistics or status from the ISA.
|
commands acknowledged
|
Number of commands returning from the ISA. Examples of commands include setting up encryption sessions and retrieving statistics or status from the ISA.
|
low_pri_pkts_sent
|
This is a summary counter for number of Internet Key Exchange (IKE) and IPSec commands submitted to ISA.
|
low_pri_pkts_rcvd
|
This is a summary counter for number of IKE & IPSEC command responses received from ISA.
|
invalid_sa
|
Reference to an unusable security association key pair.
|
invalid_flow
|
An invalid packet using an IPSec key is received for encryption or decryption.
Example: session has expired.
|
invalid_dh
|
Reference to an unusable Diffie-Hellman( DH) key pair.
|
ah_seq_failure
|
Unacceptably late Authentication Header (AH) header received.
|
ah_spi_failure
|
SPI specified in the AH header does not match the SPI associated with the IPSec AH key.
|
esp_auth_failure
|
Number of ESP packets received with authentication failures.
|
esp_seq_failure
|
Unacceptably late ESP packet received.
|
esp_spi_failure
|
SPI specified in the ESP header does not match the SPI associated with the IPSec ESP key.
|
esp_protocol_absent
|
Packet is missing expected ESP header.
|
ah_protocol_absent
|
Packet is missing expected AH header.
|
bad_key_group
|
Unsupported key group requested during a Diffie-Hellman generation.
|
no_shared_secret
|
Attempting to use a Diffie-Hellman shared secret that is not generated.
|
no_skeyids
|
Attempting to use a shared secret that is not generated.
|
pad_size_error
|
The length of the ESP padding is greater than the length of the entire packet.
|
cmd_ring_full
|
New IKE setup messages are not queued for processing until the previous queued requests are processed.
|
bulk_ring_full
|
New packets requiring IPSec functionality are not queued to the ISA until the ISA completes the processing of existing requests.
|
bad_peer_pub_len
|
Length of peer's DH public key does not match the length specified for the negotiated DH key group.
|
authentication_failure
|
Authentication failed.
|
fallback
|
The number of instances when the driver is successful in getting a replacement buffer from the global pool.
|
no_particle
|
The number of instances when the driver was unable to get a replacement buffer from the driver pool and the global (fallback) pool.
|
Related Commands
Command
|
Description
|
show pas isa controller
|
Displays controller status information that is specific to the VPN accelerator card.
|
show pas vam controller
To display controller information that is specific to the VPN Acceleration Module (VAM), use the show pas vam controller command in privileged EXEC mode.
show pas vam controller
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(9)E
|
This command was introduced.
|
12.2(9)YE
|
This command was integrated into Cisco IOS Release 12.2(9)YE.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Examples
The following is sample output from the show pas vam controller command:
Router# show pas vam controller
Addresses of Rings and instance structure:
OMQ=0xF2CB2E0, OMQ Shadow = 0x630E6638, {1, 1, 0, 256}
PKQ=0xF2CF320, PKQ Shadow = 0x630EBE64, {232, 232, 0, 256}
ERQ=0xF2D3360, ERQ Shadow = 0x630F1690, {0, 0, 0, 256}
TX: 0x0F2D73A0 TX Shadow:0x630F6EBC, {6, 6, queued=0}
RX: 0x7F2D93E0 {13, 0, 256}
RX Pool:0x7F2DA420 RX Pool Shadow:0x630FCAE8, {6, 0, 255}
Instance Structure address:0x630E5898
mini-omq=0xF2DB460, shdw=0x63102714
Group0=0x3D800000, Group1=0x3D801000
Heartbeat info:<Addr, Value> = <0xF2DB520, 0x2A55A>
Running default HSP (addr=0x629D36AC, size=294268)
Related Commands
Command
|
Description
|
show pas vam interface
|
Displays interface status information specific to the VPN accelerator module.
|
show pas vam interface
To display interface information that is specific to the VPN Acceleration Module (VAM), use the show pas vam interface command in privileged EXEC mode.
show pas vam interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(9)E
|
This command was introduced.
|
12.2(9)YE
|
This command was integrated into Cisco IOS Release 12.2(9)YE.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
Enter the show pas vam interface command to see if the VAM is currently processing crypto packets.
Examples
The following is sample output from the show pas vam interface command:
Router# show pas vam interface
ds: 0x621CE0D8 idb:0x621C28DC
Statistics of packets and bytes that through this interface:
1110 packets in 1110 packets out
123387 bytes in 100979 bytes out
0 paks/sec in 0 paks/sec out
0 Kbits/sec in 0 Kbits/sec out
3507 commands out 3507 commands acknowledged
ppq_full_err : 0 ppq_rx_err : 0
cmdq_full_err : 0 cmdq_rx_err : 0
no_buffer : 0 fallback : 0
dst_overflow : 0 nr_overflow : 0
sess_expired : 0 pkt_fragmented : 0
out_of_mem : 0 access_denied : 0
invalid_fc : 0 invalid_param : 0
invalid_handle : 0 output_overrun : 0
input_underrun : 0 input_overrun : 0
key_invalid : 0 packet_invalid : 0
decrypt_failed : 0 verify_failed : 0
attr_invalid : 0 attr_val_invalid : 0
attr_missing : 0 obj_not_wrap : 0
bad_imp_hash : 0 cant_fragment : 0
out_of_handles : 0 compr_cancelled : 0
rng_st_fail : 0 other_errors : 0
3420 seconds since last clear of counters
Table 86 describes the significant fields shown in the display.
Table 86 show pas vam interface Field Descriptions
Field
|
Description
|
packets in/out
|
Number of data packets received from, or sent to, the VAM.
|
bytes in/out
|
Number of data bytes received from, or sent to, the VAM.
|
paks/sec in/out
|
Number of packets received in, or sent out, with the total number of seconds that the VAM is active.
|
Kbits/sec in/out
|
Number of kilobits (Kbits) received in, or sent out, with the total number of seconds that the VAM is active.
|
commands out
|
Number of commands going to the VAM. Examples of commands include setting up encryption sessions and retrieving statistics or status from the VAM.
|
commands acknowledged
|
Number of commands returning from the VAM. Examples of commands include setting up encryption sessions and retrieving statistics or status from the VAM.
|
ppq_full_err
|
Number of packets dropped because of a lack of space in the packet processing queues for the VAM. This usually means that input traffic has reached VAM maximum throughput possible.
|
ppq_rx_err
|
Summary counter for all errors related to packet processing.
|
cmdq_full_err
|
Number of commands dropped because of a lack of space in the command processing queues for the VAM. This error indicates that the input tunnel setup rate has reached the VAM maximum setup rate. The Internet Key Exchange (IKE) process retries the tunnel creation and deletion when commands are dropped by VAM.
|
cmdq_rx_err
|
Summary counter for all errors related to command processing (for example, IKE, or IPSec session creation or deletion).
|
no_buffer
|
Errors related to the VAM running out of buffers. May occur with large packets. Although VAM buffers cannot be tuned, try tuning buffers for other interfaces.
|
fallback
|
Internal VAM buffer pool is completely used up and VAM has to fallback to global buffer pool. This may cause minor performance impact, however, packets are still processed so this error can be ignored.
|
dst_overflow
|
Counter that is incremented when the VAM has completed an operation, but there is no available space into which to place the result.
|
nr_overflow
|
Counter that is incremented when the VAM has completed an operation, but there is no available space into which to place the result.
|
sess_expired
|
Counter that is incremented if the session used to encrypt or decrypt the packet has expired because of time or space limit.
|
pkt_fragmented
|
Counter that is incremented when the input packet has to be fragmented after encryption. This counter should always be 0 as fragmentation by VAM is disabled.
|
out_of_mem
|
Counter that is incremented when the VAM runs out of memory.
|
access_denied
|
Counter that is incremented when the VAM is requested to perform an operation on an object that can not be modified.
|
invalid_fc
|
Counter that is incremented when the VAM has received a request that is illegal for the specified object type.
|
invalid_param
|
Counter that is incremented when the VAM has received invalid parameters within a command.
|
invalid_handle
|
Counter that is incremented when the VAM receives a request for an operation to be performed on an object that does not exist.
|
output_overrun
|
Counter that is incremented when the space allocated for a response is not large enough to hold the result posted by the VAM.
|
input_underrun
|
Counter that is incremented when the VAM receives a packet for which it finds a premature end to the data, for example, a truncated packet.
|
input_overrun
|
Counter that is incremented when the VAM receives a buffer that is too large for the requested operation.
|
key_invalid
|
Counter that is incremented when the VAM receives a request for an operation on a key where the key is invalid or of the wrong type.
|
packet_invalid
|
Counter that is incremented when the VAM receives a packet whose body is badly formed.
|
decrypt_failed
|
Counter that is incremented when the VAM receives a packet that cannot be decrypted because the decrypted data was not properly formatted (for example, padding is wrong).
|
verify_failed
|
Counter that is incremented when the VAM receives a packet which could not be verified because the verification of a signature or authentication value failed.
|
attr_invalid
|
Counter that is incremented when the VAM receives a packet which specifies an attribute that is not correct for the specified object or operation.
|
attr_val_invalid
|
Counter that is incremented when the VAM encounters errors during packet or command processing. The packets or commands are dropped in such cases.
|
attr_missing
|
Counter that is incremented when the VAM receives an operation request for which the value of a required attribute is missing.
|
obj_not_wrap
|
Counter that is incremented when the VAM receives an operation request to retrieve an object that is hidden or unavailable for export beyond the FIPS boundary of the VPN Module.
|
bad_imp_hash
|
Counter that is incremented when the VAM sees a hash miscompare on unwrap.
|
cant_fragment
|
Counter that is incremented when the VAM determines a need to fragment a packet, but cannot fragment because the "don't fragment" bit is set. This counter should always be zero because the fragmentation on the VAM is disabled.
|
out_of_handles
|
Counter that is incremented when the VAM has run out of available space for objects of the requested type.
|
comp_cancelled
|
Due to the operation of the compression algorithm, some data patterns cannot be compressed. Usually data that has already been compressed or data that does not have a sufficient number of repetitive patterns cannot be compressed and a compress operation would actually result in expansion of the data.
There are certain known data patterns which do not compress. In these cases, the compression engine cancels the compression of the data and returns the original, uncompressed data without an IPPCP header.
These counters are useful to determine if the content of the traffic on the network is actually benefiting from compression. If a large percentage of the network traffic is already compressed files, these counters may indicate that compression on these streams are not improving the performance of the network.
|
rng_st_fail
|
Counter that is incremented when the VAM detects a Random Number Generator self test failure.
|
pkt_replay_err
|
Counter that is incremented when a replay error is detected by the VAM.
|
other_errors
|
Counter that is incremented when the VAM encounters a packet or command error that is not listed in other error categories. An example could be if the packet IP header checksum is incorrect.
|
Related Commands
Command
|
Description
|
show pas vam controller
|
Displays controller status information that is specific to the VPN accelerator module.
|
show pci aim
To show the IDPROM contents for each compression Advanced Interface Module (AIM) daughter card in the Cisco 2600 router, use the show pci aim command in user EXEC or privileged EXEC mode.
show pci aim
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
Usage Guidelines
This command shows the IDPROM contents for each compression AIM daughtercard present in the system, by AIM slot number (currently 0, since that is the only daughtercard installed for Cisco IOS Release 12.0(1)T). The IDPROM is a small PROM built into the AIM board used to identify it to the system. It is sometimes referred to as an EEPROM because it is implemented using electronically erasable PROM.
Examples
The following example shows the IDPROM output for the installed compression AIM daughter card:
0x00: 04 FF 40 01 2D 41 01 00 FF FF FF FF FF FF FF FF
0x10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Related Commands
Command
|
Description
|
clear aim
|
Clears data compression AIM registers and resets the hardware.
|
test aim eeprom
|
Tests the data compression AIM after it is installed in a Cisco 2600 series router.
|
show power inline
To display the power status for a specified port or for all ports, use the show power inline command in privileged EXEC mode.
show power inline [interface-type slot/port] [actual | configured]
Syntax Description
interface-type
|
(Optional) Type of interface.
|
slot
|
(Optional) Slot number.
|
/port
|
(Optional) Port number.
|
actual
|
(Optional) Displays the present power status, which might not be the same as the configured power.
|
configured
|
(Optional) Displays the configured power status.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)XU
|
This command was introduced.
|
12.2(2)XT
|
This command was introduced on the Cisco 2600 series, the Cisco 3600 series, and the Cisco 3700 series routers to support switchport creation.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support switchport creation on Cisco 2600 series, the Cisco 3600 series, and Cisco 3700 series routers.
|
Usage Guidelines
The show power inline command displays the amount of power used to operate a Cisco IP phone. To view the amount of power requested, use the show cdp neighbors command.
Examples
The following is sample output from the show power inline fa0/4 actual command asking for the actual status of each interface rather than what is configured for each:
Router# show power inline fastethernet 0/4 actual
-------------------- -----
Notice that the status shown for the FastEthernet interface 0/4, there is no power.
Related Commands
Command
|
Description
|
power inline
|
Determines how inline power is applied to devices on the specified Fast Ethernet port.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show redundancy
To display current or historical status and related information on planned or logged handovers, use the show redundancy command in privileged EXEC mode.
show redundancy [clients | counters | debug-log | handover | history | states]
Syntax Description
clients
|
(Optional) Redundancy-aware client-application list.
|
counters
|
(Optional) Redundancy-related operational measurements.
|
debug-log
|
(Optional) Log of up to 256 redundancy-related debug entries.
|
handover
|
(Optional) Details of any pending scheduled handover.
|
history
|
(Optional) Log of past status and related information about logged handovers. This is the only keyword supported on the Cisco AS5800.
|
states
|
(Optional) Redundancy-related states: disabled, initialization, standby, active (various substates for the latter two).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.3(6)AA
|
This command was introduced.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T. Support for the Cisco 5800 and Cisco AS5850 is not included in this release.
|
12.2(11)T
|
This command is supported on the Cisco AS5800, and Cisco AS5850 in this release.
|
Usage Guidelines
Cisco AS5800: Use this command from the router-shelf console to determine when failover is enabled. Use this command with the history keyword to log failover events.
Cisco AS5850: To use this command, you must have two route-switch-controller (RSC) cards installed and you must be connected to one of them.
Examples
The following is sample output from the show redundancy handover and show redundancy states commands on a Cisco AS5850:
Router# show redundancy handover
No busyout period specified
Handover pending at 23:00:00 PDT Wed May 9 2001
Router# show redundancy states
my state = 14 -ACTIVE_EXTRALOAD
peer state = 4 -STANDBY COLD
Redundancy Mode = Handover-split: If one RSC fails, the peer RSC will take over the
feature boards
Maintenance Mode = Disabled
Manual Swact = Disabled Reason: Progression in progress
client_notification_TMR = 30000 milliseconds
keep_alive TMR = 4000 milliseconds
The following is sample output from the show redundancy command on a Cisco AS5800:
Hub is in 'active' state.
Clock is in 'active' state.
Hub is in 'backup' state.
Clock is in 'backup' state.
The following is sample output from the show redundancy history command on a Cisco AS5800:
Router# show redundancy history
DSC Redundancy Status Change History:
981130 18:56 Slot 12 DSC: Hub, becoming active - RS instruction
981130 19:03 Slot 12 DSC: Hub, becoming active - D13 order
The following is sample output from two Cisco AS5800 router shelves configured as a failover pair. The active router shelf is initially RouterA. The show redundancy history and show redundancy commands have been issued. The show redundancy command shows that failover is enabled, shows the configured group number, and shows that this router shelf is the active one of the pair. Compare this output with that from the backup router shelf (RouterB) further below.
Note When RouterA is reloaded, thereby forcing a failover, new entries are shown on RouterB when a show redundancy history command is issued after failover has occurred.
Log from the First Router (RouterA)
RouterA# show redundancy history
DSC Redundancy Status Change History:
010215 18:17 Slot -1 DSC:Failover configured -> ACTIVE role by default.
010215 18:18 Slot -1 DSC:Failover -> BACKUP role.
010215 18:18 Slot 12 DSC:Failover -> ACTIVE role.
010215 18:18 Slot 12 DSC:Hub, becoming active - arb timeout
failover mode enabled, failover group = 32
Hub is in 'active' state.
Clock is in 'active' state.
Proceed with reload? [confirm] y
*Feb 15 20:19:11.059:%SYS-5-RELOAD:Reload requested
System Bootstrap, Version xxx
Copyright xxx by cisco Systems, Inc.
C7200 processor with 131072 Kbytes of main memory
Log from the Second Router (RouterB)
failover mode enabled, failover group = 32
Hub is in 'backup' state.
Clock is in 'backup' state.
*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Switching to DSC 13
*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Failover:changing to active mode
*Feb 16 03:24:54.931:%DIAL13-3-MSG:
02:32:06:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC
*Feb 16 03:24:55.491:%OIR-6-INSCARD:Card inserted in slot 12, interfaces administratively
shut down
*Feb 16 03:24:58.455:%DIAL13-3-MSG:
02:32:09:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC
*Feb 16 03:25:04.939:%DIAL13-0-MSG:
failover mode enabled, failover group = 32
Hub is in 'active' state.
Clock is in 'backup' state.
RouterB# show redundancy history
DSC Redundancy Status Change History:
010216 03:09 Slot -1 DSC:Failover configured -> BACKUP role.
010216 03:24 Slot 13 DSC:Failover -> ACTIVE role.
010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail
010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail
*Feb 16 03:26:14.079:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 1 Succeeded
*Feb 16 03:26:14.255:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 3 Succeeded
*Feb 16 03:26:14.979:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 10 Succeeded
Related Commands
Command
|
Description
|
debug redundancy
|
Displays information used for troubleshooting dual (redundant) router shelves (Cisco AS5800) or RSCs (Cisco AS5850).
|
hw-module
|
Enables the router shelf to stop a DSC or to restart a stopped DSC.
|
redundancy
|
Enters redundancy configuration mode.
|
show chassis
|
Displays, for a router with two RSCs, information about mode (handover-split or classic-split), RSC configuration, and slot ownership.
|
show redundancy interlink
To display interlink utilization, use the show redundancy interlink command in user EXEC or privileged EXEC mode.
show redundancy interlink [rx | tx [pps | bps]] [histogram]
Syntax Description
rx
|
(Optional) Receive interlink utilization histograms.
|
tx
|
(Optional) Transmit interlink utilization histograms.
|
pps
|
(Optional) Packets per second (pps) histograms.
|
bps
|
(Optional) Bytes per second (bps) histograms.
|
histogram
|
(Optional) Usage information.
|
Command Default
Interlink utilization information is not displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced on the Cisco AS5850.
|
12.2(31)SB
|
This command was introduced on the Cisco 10000 series Internet routers. Support for the Cisco AS5850 is not included in this release.
|
Usage Guidelines
Use the show redundancy interlink command to display the current or historical status on interlink utilization.
Examples
The following histogram displays receive BPS interlink information for the past minute, the past hour, and the past three days:
Router# show redundancy interlink rx bps histogram
1111111111111111111111111111111111111111111112222222222111
0....5....1....1....2....2....3....3....4....4....5....5....
Interlink Rx BPS (last 60 seconds)
# = Bits Per Second (x1000)
2111112111112121111121111111211111111111111111111111111111
0....5....1....1....2....2....3....3....4....4....5....5....
Interlink Rx BPS (last 60 minutes)
* = maximum BPS (x1000) # = average BPS (x1000)
1111222221111111112111111111111111211211111111111111121112111111111111
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
Interlink Rx BPS (last 72 hours)
* = maximum BPS (x1000) # = average BPS (x1000)
show service-module serial
To display the performance report for an integrated CSU/DSU, use the show service-module serial command in privileged EXEC mode.
show service-module serial number [performance-statistics [interval-range]]
Syntax Description
number
|
Interface number 0 or 1.
|
performance-statistics
|
(Optional) Displays the CSU/DSU performance statistics for the past 24 hours. This keyword applies only to the fractional T1/T1 module.
|
interval-range
|
(Optional) Specifies the number of 15-minute intervals displayed. You can choose a range from 1 to 96, where each value represents the CSU/DSU activity performed in that 15-minute interval. For example, a range of 2-3 displays the performance statistics for the intervals two and three.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
This command applies to the 2- and 4-wire 56/64-kbps CSU/DSU module and FT1/T1 CSU/DSU module. The performance-statistics keyword applies only to the FT1/T1 CSU/DSU module.
Examples
The following sample output shows CSU/DSU performance statistics on a Cisco 2524 or Cisco 2525 router for intervals 30 to 32. Each interval is 15 minutes long. All the data is zero because no errors were discovered on the T1 line:
Router# show service-module serial 1 performance-statistics 30-32
Total Data (last 58 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
Data in current interval (131 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 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 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 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
The following is sample output from the show service-module serial command for a fractional T1 line:
Router1# show service-module serial 0
Module type is T1/fractional
Hardware revision is B, Software revision is 1.1 ,
Image checksum is 0x2160B7C, Protocol revision is 1.1
Unit is currently in test mode:
line loopback is in progress
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536 Kbits/sec.
Last user loopback performed:
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:05:50
loss of signal : 1, last occurred 0:01:50
AIS alarm : 1, current duration 0:00:49
Module access errors : 0,
Total Data (last 0 15 minute intervals):
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 current interval (351 seconds elapsed):
1466 Line Code Violations, 0 Path Code Violations
25 Slip Secs, 49 Fr Loss Secs, 40 Line Err Secs, 1 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 49 Unavail Secs
The following sample output from the show service-module serial command displays the status of a switched 56-KB line:
Router1# show service-module serial 1
Module type is 4-wire Switched 56
Hardware revision is B, Software revision is 1.00,
Image checksum is 0x44453634, Protocol revision is 1.0
Connection state: active,
Receiver has loss of signal, loss of sealing current,
Unit is currently in test mode:
line loopback is in progress
Current line rate is 56 Kbits/sec
Last user loopback performed:
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:13:54
oos/oof : 3, last occurred 0:00:24
loss of signal : 3, current duration 0:00:24
loss of sealing curren: 2, current duration 0:04:39
rate adaption attempts: 0,
The following shows sample output from the show service-module serial command issued on a Cisco 3640 modular access router:
Router# show service-module serial 0/1
Module type is 4-wire Switched 56
Hardware revision is B, Software revision is 1.00,
Image checksum is 0x42364436, Protocol revision is 1.0
Current line rate is 56 Kbits/sec
Last module self-test (done at startup): Passed
Last clearing of alarm counters 4d02h
loss of sealing curren: 0,
rate adaptation attemp: 0,
The following shows sample output from the show service-module serial command issued on a Cisco 1605 router:
Router# show service-module serial 0
Module type is 4-wire Switched 56
Hardware revision is B, Software revision is 1.00,
Image checksum is 0x42364436, Protocol revision is 1.0
Receiver has oos/oof, loss of signal,
Current line rate is 56 Kbits/sec
Last module self-test (done at startup): Passed
Last clearing of alarm counters 1d02h
oos/oof : 1, current duration 1d02h
loss of signal : 1, current duration 1d02h
rate adaptation attemp: 0,
Table 87 describes the fields displayed by the show service-module serial command.
Table 87 show service-module serial Field Descriptions
Field
|
Description
|
Module type
|
CSU/DSU module installed in the router. The possible modules are T1/fractional, 2-wire switched 56-kbps, and 4-wire 56/64-kbps.
|
Receiver has AIS alarm
|
Alarms detected by the FT1/T1 CSU/DSU module or 2- and 4-wire 56/64-kbps CSU/DSU modules.
Possible T1 alarms are as follows:
•Transmitter is sending remote alarm.
•Transmitter is sending AIS.
•Receiver has loss of signal.
•Receiver has loss of frame.
•Receiver has remote alarm.
•Receiver has no alarms.
Possible switched 56k alarms are as follows:
•Receiver has loss of signal.
•Receiver has loss of sealing current.
•Receiver has loss of frame.
•Receiver has rate adaptation attempts.
|
|
|
|
|
|
|
|
|
Unit is currently in test mode
|
Loopback tests are in progress.
|
Framing
|
Indicates frame type used on the line. Can be extended super frame or super frame.
|
Line Code
|
Indicated line-code type configured. Can be alternate mark inversion (AMI) or binary 8-zero substitution (B8ZS).
|
Current clock source
|
Clock source configured on the line, which can be supplied by the service provider (line) or the integrated CSU/DSU module (internal).
|
Fraction
|
Number of time slots defined for the FT1/T1 module, which can range from 1 to 24.
|
Net bandwidth
|
Total bandwidth of the line (for example, 24 time slots multiplied by 64 kbps equals a bandwidth of 1536 kbps).
|
Last user loopback performed
|
Type and outcome of the last performed loopback.
|
Last module self-test (done at startup): Passed
|
Status of the last self-test performed on an integrated CSU/DSU module.
|
Last clearing of alarm counters
|
List of network alarms that were detected and cleared on the CSU/DSU module.
|
Total Data
Data in current interval
|
Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. 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 or excessive zeroes error event.
|
Path Code Violations
|
Indicates a frame synchronization bit error in the D4 and E1-no cyclic redundancy checksum (CRC) formats or a CRC error in the extended super frame (ESF) and E1-CRC formats.
|
Slip Secs
|
Indicates the replication or detection 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 error is detected.
|
Line Err Secs
|
Line errored seconds is a second in which one or more line code violation errors are detected.
|
Errored Secs
|
In ESF and E1-CRC links, an errored second is a second in which one of the following is 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-no-CRC links, the presence of bipolar violation also triggers an errored second.
|
Bursty Err Secs
|
Second with fewer than 320 and more than 1 path coding violation errors. No severely errored frame defects or incoming AIS defects are detected. 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 D4 signals, a count of 1-second intervals with framing errors, or an Out-of-Frame defect, or 1544 line code violations.
|
Unavail Secs
|
Total time the line was out of service.
|
Related Commands
Command
|
Description
|
clear service-module serial
|
Resets an integrated CSU/DSU.
|
show smf
To display the configured software MAC address filter (SMF) on various interfaces of a router, use the show smf command in user EXEC or privileged EXEC mode.
show smf [interface-name]
Syntax Description
interface-name
|
(Optional) Displays information about the specified interface. Choices can include atm, ethernet, fastethernet, null, serial, tokenring, and async.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced in a release prior to 10.0.
|
Usage Guidelines
The SMF is active whenever the router is doing bridging or Integrated Routing and Bridging (IRB). MAC address filtering can be used as a security feature in bridging or switching environments.
Examples
The following is sample output from the show smf command:
Router# show smf fastethernet
Software MAC address filter on FastEthernet0/0.2
Hash Len Address Matches Act Type
0x00: 0 ffff.ffff.ffff 0 RCV Physical broadcast
0x0C: 0 0100.0c00.0000 0 RCV ISL vLAN Multicast
0x2A: 0 0900.2b01.0001 0 RCV DEC spanning tree
0xA6: 0 0010.a6ae.6000 0 RCV Interface MAC address
0xC1: 0 0100.0ccc.cccd 0 RCV SSTP MAC address
0xC2: 0 0180.c200.0000 0 RCV IEEE spanning tree
0xC2: 1 0180.c200.0000 0 RCV IBM spanning tree
0xC2: 2 0100.0ccd.cdce 0 RCV VLAN Bridge STP
Table 88 describes the fields shown in the display.
Table 88 show smf Field Descriptions
Field
|
Description
|
Hash
|
Position in the hash table for this entry.
|
Len
|
Length of the entry.
|
Address
|
MAC address for the interface.
|
Matches
|
Number of hits for the address.
|
Act
|
Action taken. Values can be receive (RCV), forward (FWD), or discard (DIS).
|
Type
|
Type of MAC address.
|
show storm-control
To view switchport characteristics, including storm-control levels set on the interface, use the show storm-control command in privileged EXEC mode.
show storm-control
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)XT
|
This command was introduced.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support switchport creation on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
Examples
The following example shows how to verify the storm-control levels set on the interface:
Router# show storm-control
Storm control:broadcast multicast unicast threshold 25 with default packet-size 64
Notice that the display showing status of storm control includes the default packet size and the threshold level that limits the percentage of bandwidth placed on broadcast traffic. A threshold value of 100 percent means that no limit is placed on broadcast traffic. Valid entries are from 1 to 100. If no threshold is reported for each, no threshold is set for that type of traffic.
Related Commands
Command
|
Description
|
show interface counters
|
Displays the count of discarded packets.
|
storm control
|
Sets the storm-control threshold value and blocks forwarding of unnecessary flooded traffic.
|
show syscon sdp
To display information about the Shelf Discovery Protocol (SDP), use the show syscon sdp command in privileged EXEC or user EXEC mode.
show syscon sdp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
User EXEC
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
Examples
The following is sample output from the show syscon sdp command:
Current time 10:46:32 PST Jan 28 1998, system controller 172.23.66.100
Last hello packet received at 10:45:38 PST Jan 28 1998
0 packets with bad MD5 hash
5884 Hello packets received
0 Command packets received
Table 89 describes the fields shown in the sample display.
Table 89 show syscon sdp Field Descriptions
Field
|
Description
|
Current time
|
Current time and date.
|
system controller
|
IP address of the system controller.
|
Last hello packet received
|
Time and date when the last hello packet from the system controller was received by the shelf.
|
Total SDP packets
|
Total number of SDP packets sent or received by the shelf.
|
packets with bad MD5 hash
|
Number of packets with a bad MD5 hash.
|
Hello packets received
|
Number of hello packets received by the shelf from the system controller.
|
Hello packets sent
|
Number of hello packets sent from the shelf to the system controller.
|
Command packets received
|
Number of packets containing commands received by the shelf.
|
Command packets sent
|
Number of commands sent by the shelf.
|
Related Commands
Command
|
Description
|
syscon address
|
Specifies the system controller for a managed shelf.
|
syscon source-interface
|
Specifies the interface to use for the source address in SDP packets.
|
show tdm backplane
To display modem and PRI channel assignments with streams and channels on the modem side as assigned to the unit and channels on the PRI side of the time-division multiplexing (TDM) assignment, use the show tdm backplane command in privileged EXEC mode.
show tdm backplane stream [stream-number]
Syntax Description
stream
|
Backplane stream in the range 0 to 7. There are 8 backplane "streams" on the TDM backplane for the Cisco AS5300 access server. Each stream runs at 2 MHz and has 32 channels (running at 64 Hz) on the Cisco AS5300 access server backplane hardware.
|
stream-number
|
(Optional) Actual number entered (either 0 to 7 or 0 to 15).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)XD
|
This command was introduced.
|
12.0(3)T
|
This command was integrated into Cisco IOS Release 12.0(3)T.
|
Usage Guidelines
The show tdm backplane command shows the status of the TDM backplane, related data structure values, and TDM chip memory settings. This commands is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
Examples
The following example shows sample output for the show tdm backplane command. When the debug tdm detail command is executed, more detail is shown. The following examples are run with the debug tdm detail command executed:
Router# show tdm backplane
Show BackPlane Connections
TDM Backplane Connection for Stream 0
Modem (St/Ch)<->PRI (Unit/Ch) xx/xx:Not Used ??/??:Unknown State
0 : xx/xx<->xx/xx, xx/xx<->xx/xx, 00/02<->00/30, 00/03<->03/10
4 : 00/04<->00/15, 00/05<->02/02, 00/06<->02/07, 00/07<->02/08
8 : xx/xx<->xx/xx, 00/09<->03/11, 00/10<->02/09, xx/xx<->xx/xx
12 : 00/12<->00/17, 00/13<->02/17, 00/14<->02/18, 00/15<->02/10
16 : xx/xx<->xx/xx, xx/xx<->xx/xx, 00/18<->00/19, 00/19<->02/19
20 : 00/20<->02/11, xx/xx<->xx/xx, xx/xx<->xx/xx, 00/23<->00/07
24 : xx/xx<->xx/xx, 00/25<->00/01, 00/26<->00/20, 00/27<->02/20
28 : xx/xx<->xx/xx, 00/29<->00/18, xx/xx<->xx/xx, xx/xx<->xx/xx
TDM Backplane Connection for Stream 1
Modem (St/Ch)<->PRI (Unit/Ch) xx/xx:Not Used ??/??:Unknown State
0 : xx/xx<->xx/xx, xx/xx<->xx/xx, xx/xx<->xx/xx, 01/03<->03/09
4 : 01/04<->00/03, 01/05<->02/13, xx/xx<->xx/xx, xx/xx<->xx/xx
8 : xx/xx<->xx/xx, xx/xx<->xx/xx, 01/10<->02/14, 01/11<->00/04
12 : 01/12<->00/21, xx/xx<->xx/xx, 01/14<->00/05, xx/xx<->xx/xx
16 : xx/xx<->xx/xx, xx/xx<->xx/xx, xx/xx<->xx/xx, 01/08<->02/12
20 : 01/20<->00/06, 01/09<->00/02, xx/xx<->xx/xx, xx/xx<->xx/xx
24 : 01/24<->03/01, xx/xx<->xx/xx, 01/26<->02/15, xx/xx<->xx/xx
28 : 01/28<->03/05, xx/xx<->xx/xx, xx/xx<->xx/xx, xx/xx<->xx/xx
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm connections
|
Displays details about a specific TDM channel programmed on the Mitel chip.
|
show tdm data
|
Displays information about TDM bus connection memory on Cisco access servers.
|
show tdm detail
|
Displays information about the specified TDM device.
|
show tdm information
|
Displays TDM resources available for the specified TDM device.
|
show tdm pool
|
Displays information about the specified TDM pool.
|
show tdm connections
To display a snapshot of the time-division multiplexing (TDM) bus connection memory in a Cisco access server or to display information about the connection memory programmed on the Mitel TDM chip in a Cisco AS5800 access server, use the show tdm connections command in privileged EXEC mode.
Standard Syntax
show tdm connections [motherboard | slot slot-number]
Cisco AS5800 Access Server
show tdm connections {motherboard {stream stream-number} | slot slot-number {device
device-number {stream stream-number}}}
Syntax Description
motherboard
|
(Optional) Displays connection memory for the TDM bus connections on the motherboard in the Cisco access server only.
Cisco AS5800 Access Server
The motherboard in the Cisco AS5800 access server has ethernet and serial interfaces, console port, and aux port. The motherboard has one TDM device (MT8980) for the Cisco 5300 access server.
|
slot slot-number
|
(Optional) Slot number.
Cisco AS5800 Access Server
There are three slots on the Cisco AS5800 access server. The range of the slots is from 0 to 2. A modem card or a trunk PRI card can be inserted into each slot. Each card in the slot has one or two TDM devices (either MT8980 or MT90820) on them.
|
stream
|
Device stream in the range 0 to 7. There are 8 backplane "streams" on the TDM backplane for the Cisco AS5800 access server. Each stream runs at 2 Mhz and has 32 channels (running at 64 Hz) on the Cisco AS5800 access server backplane hardware.
|
stream-number
|
Stream number (the range is from 0 to 7 or 0 to 15).
|
device
|
TDM device on the motherboard or slot cards. The range for the Cisco AS5800 access server is from 0 to 1. Each card has at least one TDM device (MT8980 or MT80920), and some of the slot cards have two devices (for example, the Octal PRI has two MT90820 TDM devices). The TDM device is also referred to as "TSI Chip Number" in the online help.
|
device-number
|
Valid range is from 0 to 1.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.0(3)T
|
This command was modified to include support for the Cisco AS5800 access server.
|
Usage Guidelines
Cisco AS5800 Access Server
The show tdm connections command shows the status of the TDM chip memory settings. This command is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
Examples
Cisco AS5800 Access Server
The following example shows sample output for the show tdm connections command. When the debug tdm detail command is executed, more detail is shown. The following examples are run with the debug tdm detail executed.
Router# show tdm connections slot 0
Slot 0 MT8980 TDM Device 0, Control Register = 0x1E, ODE Register = 0x01
Connection Memory for ST0:
Ch0: 0x00 0xE1, Ch1: 0x00 0xE2, Ch2: 0x01 0xDE, Ch3: 0x00 0x00
Ch4: 0x01 0xCF, Ch5: 0x00 0xE4, Ch6: 0x00 0xE5, Ch7: 0x00 0x00
Ch8: 0x00 0xEB, Ch9: 0x00 0xE6, Ch10: 0x00 0xE7, Ch11: 0x00 0x00
Ch12: 0x01 0xD1, Ch13: 0x00 0xE8, Ch14: 0x00 0x00, Ch15: 0x00 0xE9
Ch16: 0x00 0x00, Ch17: 0x00 0xD2, Ch18: 0x01 0xD3, Ch19: 0x00 0xEA
Ch20: 0x00 0xEB, Ch21: 0x00 0xC1, Ch22: 0x00 0xEC, Ch23: 0x01 0xC7
Ch24: 0x00 0xED, Ch25: 0x01 0xC1, Ch26: 0x01 0xD4, Ch27: 0x00 0xEE
Ch28: 0x00 0xE1, Ch29: 0x01 0xD2, Ch30: 0x00 0x00, Ch31: 0x00 0x00
Connection Memory for ST1:
Ch0: 0x00 0xEF, Ch1: 0x00 0xC2, Ch2: 0x00 0xED, Ch3: 0x00 0xF1
Ch4: 0x01 0xC3, Ch5: 0x00 0xF2, Ch6: 0x00 0xE2, Ch7: 0x00 0x00
Ch8: 0x00 0xF3, Ch9: 0x00 0xFF, Ch10: 0x00 0xF4, Ch11: 0x01 0xC4
Ch12: 0x01 0xD5, Ch13: 0x00 0xF5, Ch14: 0x01 0xC5, Ch15: 0x00 0xEE
Ch16: 0x00 0xF6, Ch17: 0x00 0xE3, Ch18: 0x00 0x00, Ch19: 0x00 0xF7
Ch20: 0x01 0xC6, Ch21: 0x01 0xC2, Ch22: 0x00 0xF8, Ch23: 0x00 0xE4
Ch24: 0x00 0xF9, Ch25: 0x00 0xC7, Ch26: 0x00 0x00, Ch27: 0x00 0xFA
Ch28: 0x00 0xFB, Ch29: 0x00 0xE5, Ch30: 0x00 0x00, Ch31: 0x00 0x00
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm data
|
Displays information about TDM bus connection memory on Cisco access servers.
|
show tdm data
To display a snapshot of the time-division multiplexing (TDM) bus data memory in a Cisco access server or to display data memory that is programmed on the Mitel TDM chip in a Cisco 5800 access server, use the show tdm data command in privileged EXEC mode.
Standard Syntax
show tdm data [motherboard | slot slot-number]
Cisco AS5800 Access Server
show tdm data {motherboard {stream stream-number} | slot slot-number {device device-number
{stream stream-number}}}
Syntax Description
motherboard
|
(Optional) Displays bus data memory for the TDM bus connections on the motherboard in the Cisco access server only.
Cisco AS5800 Access Server
The motherboard on the Cisco AS5300 access server has the ethernet I/Fs, serial I/Fs, console port, and aux port. The motherboard has one TDM device (MT8980) for the Cisco AS5300 access server.
|
slot slot-number
|
(Optional) Slot number.
Cisco AS5800 Access Server
In addition to the motherboard, there are three slots on the Cisco AS5300 access server. The range of the slots is 0 to 2. A modem card or a trunk PRI card can be inserted in each slot. Each card in the slot has one or two TDM devices (either MT8980 or MT90820) on them.
|
stream
|
TDM device stream in the range 0 to 15. There are up to 16 streams on a TDM device (Mitel 90820). The TDM device is also known as the TSI chip. The help on the command (by typing ?) indicates whether the stream is "Stream number within the TSI chip" or "Backplane Stream."
|
stream-number
|
Stream number within the range of either 0 to 7 or 0 to 15.
|
device
|
TDM device on the motherboard, or slot cards. Valid range for the Cisco AS5300 access server is 0 to 1. Each card has at least one TDM device (MT8980 or MT80920), and the Octal PRI has two MT90820 TDM devices. Also referred to as TSI Chip Number in the help pages.
|
device-number
|
Valid range is from 0 to 1.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.0(3)T
|
This command was modified to include support for the Cisco AS5800 access server.
|
Usage Guidelines
The data memory for all TDM bus connections in the access server is displayed if you do not specify a motherboard or slot.
Cisco AS5800 Access Server
The show tdm data command shows the status of the TDM data structure values. This command is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
Examples
The following is sample output for the show tdm data command on a Cisco AS5800 access server. When the debug tdm detail command is executed, more detail is shown. The following example is run with the debug tdm detail executed:
Motherboard MT8980 TDM Device 0, Control Register = 0x1F, ODE Register = 0xE1
Ch0: 0xFF, Ch1: 0xFF, Ch2: 0x98, Ch3: 0x61
Ch4: 0x0C, Ch5: 0xE1, Ch6: 0x8D, Ch7: 0x86
Ch8: 0xFF, Ch9: 0xF3, Ch10: 0xE4, Ch11: 0xFF
Ch12: 0x51, Ch13: 0x02, Ch14: 0x18, Ch15: 0x14
Ch16: 0xFF, Ch17: 0xFF, Ch18: 0x05, Ch19: 0xC7
Ch20: 0x00, Ch21: 0xFF, Ch22: 0xFF, Ch23: 0x98
Ch24: 0xFF, Ch25: 0x15, Ch26: 0x5C, Ch27: 0x15
Ch28: 0xFF, Ch29: 0x80, Ch30: 0xFF, Ch31: 0xFF
Ch0: 0xFF, Ch1: 0xFF, Ch2: 0xFF, Ch3: 0x62
Ch4: 0x94, Ch5: 0x88, Ch6: 0xFF, Ch7: 0xFF
Ch8: 0xFF, Ch9: 0xFF, Ch10: 0xFB, Ch11: 0x91
Ch12: 0xF7, Ch13: 0xFF, Ch14: 0x96, Ch15: 0xFF
Ch16: 0xFF, Ch17: 0xFF, Ch18: 0xFF, Ch19: 0x94
Ch20: 0x8F, Ch21: 0x95, Ch22: 0xFF, Ch23: 0xFF
Ch24: 0xE2, Ch25: 0xFF, Ch26: 0xD3, Ch27: 0xFF
Ch28: 0x87, Ch29: 0xFF, Ch30: 0xFF, Ch31: 0xFF
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm connections
|
Displays details about a specific TDM channel programmed on the Mitel chip.
|
show tdm detail
To display details about a specific time-division mulltiplexing (TDM) channel programmed on the Mitel chip, use the show tdm detail command in privileged EXEC mode.
show tdm detail slot-number/device-number source-stream-number/source-channel-number
Syntax Description
slot-number
|
There are three slots on the Cisco AS5300 access server. A modem card or a trunk PRI card can be inserted in each slot. Each card has one or two TDM devices (either MT8980 or MT90820) on it. The valid range is from 0 to 2.
|
/device-number
|
TDM device on the motherboard or slot cards. Each card has at least one TDM device (MT8980 or MT80920), and the Octal PRI has two MT90820 TDM devices. Also referred to a TSI Chip Number in the online help. The valid range is from 0 to 1.
|
source-stream-number
|
Source stream number from the TDM device. The valid range is from 0 to 15.
|
/source-channel-number
|
Source channel from the TDM device stream. The valid range is from 0 to 31.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)XD
|
This command was introduced.
|
12.0(3)T
|
This command was integrated into Cisco IOS Release 12.0(3)T.
|
Usage Guidelines
The show tdm detail command shows the status of the TDM backplane, related data structure values, and TDM chip memory settings. This command is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
This command indicates connection memory and map, data memory, and whether the channel is enabled or disabled. Specify the specific slot, TDM device, TDM stream, and TDM channel.
Examples
The following example shows sample output displayed for the show tdm detail command. When the debug tdm detail command is executed, more detail is shown. The following example was run with the debug tdm detail command executed:
Router# show tdm detail 0/0 1/2
Show Detail TDM device info: slot 0 unit 0
Connection Memory: 0x00ED, Output is Disable
Connection Map: STi7 CHi13 ----> STo1 CHo2
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm backplane
|
Displays modem and PRI channel assignments with streams and channels on the modem side as assigned to the unit and channels on the PRI side of the TDM assignment.
|
show tdm connections
|
Displays details about a specific TDM channel programmed on the Mitel chip.
|
show tdm data
|
Displays information about TDM bus connection memory on Cisco access servers.
|
show tdm information
|
Displays TDM resources available for the specified TDM device.
|
show tdm pool
|
Displays information about the specified TDM pool.
|
show tdm information
To display information about the specified time-division multiplexing (TDM) device, use the show tdm information command in privileged EXEC mode.
show tdm information {motherboard | slot slot-number {device device-number}}
Syntax Description
motherboard
|
Motherboard on the Cisco AS5300 access server has the Ethernet I/Fs, serial I/Fs, console port, and aux port. The motherboard has one TDM device (MT8980) for the Cisco AS5300 access server.
|
slot
|
There are three slots on the Cisco AS5300 access server. The range of the slots is 0 to 2. A modem card or a trunk PRI card can be inserted in each slot. Each card has one or two TDM devices (either MT8980 or MT90820) on it.
|
slot-number
|
Slot number. Valid range is from 0 to 2.
|
device
|
TDM device on the motherboard or slot cards. The valid range is from 0 to 1. Each card has at least one TDM device (MT8980 or MT80920), and the Octal PRI has two MT90820 TDM devices. Also referred to as TSI Chip Number in the online help.
|
device-number
|
Device number. Valid range is from 0 to 1.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)XD
|
This command was introduced.
|
12.0(3)T
|
This command was integrated into Cisco IOS Release 12.0(3)T.
|
Usage Guidelines
The show tdm information command shows the status of the TDM backplane, related data structure values, and TDM chip memory settings. This command is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
This command displays the register base address, device type, and capabilities on a per-slot basis.
Examples
The following example shows sample output for the show tdm information command. When the debug tdm detail command is executed, more detail is shown. The following example is run with the debug tdm detail command executed:
Router# show tdm information motherboard
TDM Slot Info display for Motherboard:
Slot Info ptr @0x610D39C0 Feature info ptr @0x60B737E8
Feature board is MOTHERBOARD, NIM ID: 0x30
TSI device is MT8980, 1 on this board. Each TSI device supports 0 DS1s
First TSI device is at offset: 0x100
TSI device 0, register base 0x3E801100
TDM Device Info ptr @0x611AA3EC for slot -1
TSI device Info ptr @0x60FCC0BC memory size = 0x100
This device supports 8 streams with 32 channels per stream
TDM Information display for slot 0:
Slot Info ptr @0x610D39E4 Feature info ptr @0x60B73818
Feature board is E1 Quad PRI, NIM ID: 0x43
TSI device is MT8980, 2 on this board. Each TSI device supports 2 DS1s
First TSI device is at offset: 0x100, Second TSI device is at Offset: 0x200
Framer Streams start at 6
TSI device 0, register base 0x3C400100
TDM Device Info ptr @0x61222054 for slot 0
TSI device Info ptr @0x60FCC0BC memory size = 0x100
This device supports 8 streams with 32 channels per stream
TSI device 1, register base 0x3C400200
TDM Device Info ptr @0x61222098 for slot 0
TSI device Info ptr @0x60FCC0BC memory size = 0x100
This device supports 8 streams with 32 channels per stream
TDM Information display for slot 1:
Slot Info ptr @0x610D3A08 Feature info ptr @0x60B738A8
Feature board is High Density Modems, NIM ID: 0x47
TSI device is MT8980, 1 on this board. Each TSI device supports 0 DS1s
First TSI device is at offset: 0x100
TSI device 0, register base 0x3C500100
TDM Device Info ptr @0x612F1B80 for slot 1
TSI device Info ptr @0x60FCC0BC memory size = 0x100
This device supports 8 streams with 32 channels per stream
TDM Information display for slot 2:
Slot Info ptr @0x610D3A2C Feature info ptr @0x60B738A8
Feature board is High Density Modems, NIM ID: 0x47
TSI device is MT8980, 1 on this board. Each TSI device supports 0 DS1s
First TSI device is at offset: 0x100
TSI device 0, register base 0x3C600100
TDM Device Info ptr @0x613A6F60 for slot 2
TSI device Info ptr @0x60FCC0BC memory size = 0x100
This device supports 8 streams with 32 channels per stream
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm backplane
|
Displays modem and PRI channel assignments with streams and channels on the modem side as assigned to the unit and channels on the PRI side of the TDM assignment.
|
show tdm connections
|
Displays details about a specific TDM channel programmed on the Mitel chip.
|
show tdm data
|
Displays information about TDM bus connection memory on Cisco access servers.
|
show tdm detail
|
Displays information about the specified TDM device.
|
show tdm pool
|
Displays information about the specified TDM pool.
|
show tdm pool
To display time-division multiplexing (TDM) resources available for a TDM device, use the show tdm pool command in privileged EXEC mode.
show tdm pool [slot slot-number]
Syntax Description
slot
|
(Optional) There are three slots on the Cisco AS5300 access server with a range of 0 to 2. A modem card or a trunk PRI card can be inserted in each slot. Each card has one or two TDM devices (either MT8980 or MT90820) on it.
|
slot-number
|
(Optional) Slot number. Valid range is from 0 to 2 for the Cisco AS5300 access server.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)XD
|
This command was introduced.
|
12.0(3)T
|
This command was integrated into Cisco IOS Release 12.0(3)T.
|
Usage Guidelines
The show tdm pool command shows the status of the TDM backplane, related data structure values, and TDM chip memory settings. This command is generally used only by a Cisco technical support representative during troubleshooting of data continuity problems.
This command displays TDM groups, where group 0 is streams 0 to 3 and group 1 is streams 4 to 7. It also displays register address and capabilities on a per-slot basis.
Examples
The following example shows sample output for the show tdm pool command. When the debug tdm detail command is executed, more detail is shown. The following example was run with the debug tdm detail command executed:
Dynamic Backplane Timeslot Pool:
Grp ST Ttl/Free Req(Cur/Ttl/Fail) Queues(Free/Used) Pool Ptr
0 0-3 120 60 60 361 0 0x61077E28 0x61077E28 0x61077E20
1 4-7 0 0 0 0 0 0x61077E38 0x61077E28 0x61077E24
Related Commands
Command
|
Description
|
debug tdm detail
|
Displays debugging messages about TDM commands.
|
show tdm backplane
|
Displays modem and PRI channel assignments with streams and channels on the modem side as assigned to the unit and channels on the PRI side of the TDM assignment.
|
show tdm connections
|
Displays details about a specific TDM channel programmed on the Mitel chip.
|
show tdm data
|
Displays information about TDM bus connection memory on Cisco access servers.
|
show tdm detail
|
Displays information about the specified TDM device.
|
show tdm information
|
Displays TDM resources available for the specified TDM device.
|
shutdown (controller)
To disable the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the shutdown command in controller configuration mode. To restart a disabled CT3IP, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Using this command assumes that the controller is already enabled. By default, if this command is not issued, the controller remains enabled.
Command Modes
Controller configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
Shutting down the CT3IP disables all functions on the interface and sends a blue alarm to the network. The shutdown command marks the interface as unavailable. To check if the CT3IP is disabled, use the show controllers t3 command.
Examples
The following example shuts down the CT3IP:
Router(config)# controller t3 9/0/0
Router(config-controller)# shutdown
Related Commands
Command
|
Description
|
show controllers t3
|
Displays the hardware and software driver information for a T3 controller.
|
shutdown (hub)
To shut down a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router, use the shutdown command in hub configuration mode. To restart the disabled hub, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Using this command assumes that the hub is already enabled. By default, if this command is not issued, the hub remains enabled.
Command Modes
Hub configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Examples
The following example shuts down hub 0, ports 1 through 3:
Router(config)# hub ethernet 0 1 3
Router(config-hub)# shutdown
Related Commands
Command
|
Description
|
hub
|
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
|
shutdown (interface)
To disable an interface, use the shutdown command in interface configuration mode. To restart a disabled interface, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Using this command assumes that the interface is already enabled. By default, if this command is not issued, the interface remains enabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The shutdown command disables all functions on the specified interface. On serial interfaces, this command causes the data terminal ready (DTR) signal to be dropped. On Token Ring interfaces, this command causes the interface to be removed from the ring. On FDDI interfaces, this command causes the optical bypass switch, if present, to go into bypass mode.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the show interfaces EXEC command; an interface that has been shut down is shown as administratively down in the display from this command.
Examples
The following example turns off Ethernet interface 0:
Router(config)# interface ethernet 0
Router(config-if)# shutdown
08:32:03:%LINK-5-CHANGED:Interface Ethernet 0, changed state to administratively down
The following example turns the interface back on:
Router(config)# interface ethernet 0
Router(config-if)# no shutdown
08:32:16:%LINK-3-UPDOWN:Interface Ethernet 0, changed state to up
08:32:17:%LINEPROTO-5-UPDOWN:Line protocol on Interface Ethernet 0, changed state to up
Related Commands
Command
|
Description
|
interface
|
Configures an interface type and enters interface configuration mode.
|
show interfaces
|
Displays the statistical information specific to a serial interface.
|
smt-queue-threshold
To set the maximum number of unprocessed FDDI station management (SMT) frames that will be held for processing, use the smt-queue-threshold command in global configuration mode. To restore the queue to the default, use the no form of this command.
smt-queue-threshold number
no smt-queue-threshold
Syntax Description
number
|
Number of buffers used to store unprocessed SMT messages that are to be queued for processing. Acceptable values are positive integers. The default value is equal to the number of FDDI interfaces installed in the router.
|
Defaults
The default threshold value is equal to the number of FDDI interfaces installed in the router.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command helps ensure that routers keep track of FDDI upstream and downstream neighbors, particularly when a router includes more than one FDDI interface.
In FDDI, upstream and downstream neighbors are determined by transmitting and receiving SMT Neighbor Information Frames (NIFs). The router can appear to lose track of neighbors when it receives an SMT frame and the queue currently contains an unprocessed frame. This occurs because the router discards incoming SMT frames if the queue is full. Discarding SMT NIF frames can cause the router to lose its upstream or downstream neighbor.
Caution Use this command carefully because the SMT buffer is charged to the inbound interface (input hold queue) until the frame is completely processed by the system. Setting this value to a high limit can impact buffer usage and the ability of the router to receive routable packets or routing updates.
Examples
The following example specifies that the SMT queue can hold ten messages. As SMT frames are processed by the system, the queue is decreased by one:
Router(config)# smt-queue-threshold 10
snmp ifindex clear
To clear any previously configured SNMP ifIndex commands issued in interface configuration mode for a specific interface, use the snmp ifindex clear command in interface configuration mode.
snmp ifindex clear
Syntax Description
This command has no arguments or keywords.
Defaults
The SNMP index is not cleared.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(11)S
|
This command was introduced.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
Interface Index Persistence means that ifIndex values in the IF-MIB persist across reboots, allowing for consistent identification of specific interfaces using Simple Network Management Protocol (SNMP).
Use the snmp ifindex clear command on a specific interface when you want that interface to use the global configuration setting for ifIndex persistence. This command clears any ifIndex configuration commands previously entered for that specific interface.
This command does not have a no form.
Examples
In the following example, ifIndex persistence is enabled for all interfaces:
Router(config)# snmp-server ifindex persist
IfIndex persistence is then disabled for Ethernet interface 0/1 only:
Router(config)# interface ethernet 0/1
Router(config-if)# no snmp ifindex persist
Later, the ifIndex configuration command is cleared from the configuration for Ethernet interface 0/1:
Router(config)# interface ethernet 0/1
Router(config-if)# snmp ifindex clear
This leaves ifIndex persistence enabled for all interfaces, as specified by the snmp-server ifindex persist global configuration command.
Related Commands
Command
|
Description
|
snmp ifindex persist
|
Enables ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots (ifIndex persistence) only on a specific interface.
|
snmp-server ifindex persist
|
Enables ifIndex values that will remain constant across reboots for use by SNMP.
|
snmp ifindex persist
To enable ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots (ifIndex persistence) on a specific interface only, use the snmp ifindex persist command in interface configuration mode. To disable ifIndex persistence on a specific interface only, use the no form of this command.
snmp ifindex persist
no snmp ifindex persist
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(11)S
|
This command was introduced.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
Interface Index Persistence means that ifIndex values in the IF-MIB persist across reboots, allowing for consistent identification of specific interfaces using Simple Network Management Protocol (SNMP).
The snmp ifindex persistence interface configuration command enables and disables ifIndex persistence for individual entries (corresponding to individual interfaces) in the ifIndex table of the IF-MIB.
The snmp-server ifindex persistence global configuration command enables and disables ifIndex persistence for all interfaces on the routing device (this applies only to interfaces that have ifDescr and ifIndex entries in the ifIndex table of the IF-MIB).
IfIndex commands configured for an interface apply to all subinterfaces on that interface.
Examples
In the following example, ifIndex persistence is enabled for Ethernet interface 0/1 only:
Router(config)# interface ethernet 0/1
Router(config-if)# snmp ifindex persist
In the following example, ifIndex persistence is enabled for all interfaces and then disabled for interface Ethernet interface 0/1 only:
Router(config)# snmp-server ifindex persist
Router(config)# interface ethernet 0/1
Router(config-if)# no snmp ifindex persist
Related Commands
Command
|
Description
|
snmp ifindex clear
|
Clears any previously configured snmp ifIndex commands issued in interface configuration mode for a specific interface.
|
snmp-server ifindex persist
|
Enables ifIndex values that will remain constant across reboots for use by SNMP.
|
snmp trap illegal-address
To issue a Simple Network Management Protocol (SNMP) trap when a MAC address violation is detected on an Ethernet hub port of a Cisco 2505, Cisco 2507, or Cisco 2516 router, use the snmp trap illegal-address command in hub configuration mode. To disable this function, use the no form of this command.
snmp trap illegal-address
no snmp trap illegal-address
Syntax Description
This command has no arguments or keywords.
Defaults
No SNMP trap is issued.
Command Modes
Hub configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
In addition to setting the snmp trap illegal-address command on the Ethernet hub, you can set the frequency that the trap is sent to the network management station (NMS). This is done on the NMS via the Cisco Repeater MIB. The frequency of the trap can be configured for once only or at a decaying rate (the default). If the decaying rate is used, the first trap is sent immediately, the second trap is sent after one minute, the third trap is sent after two minutes, and so on until 32 minutes, at which time the trap is sent every 32 minutes. If you use a decaying rate, you can also set the trap acknowledgment so that the trap will be acknowledged after it is received and will no longer be sent to the network management station.
Because traps are not reliable, additional information on a port basis is provided by the Cisco Repeater MIB. The network management function can query the following information: the last illegal MAC source address, the illegal address trap acknowledgment, the illegal address trap enabled, the illegal address first heard (timestamp), the illegal address last heard (timestamp), the last illegal address trap count for the port, and the illegal address trap total count for the port.
In addition to issuing a trap when a MAC address violation is detected, the port is also disabled as long as the MAC address is invalid. The port is enabled and the trap is no longer sent when the MAC address is valid (that is, either the address was configured correctly or learned).
Examples
The following example enables an SNMP trap to be issued when a MAC address violation is detected on hub ports 2, 3, or 4. SNMP support must already be configured on the router.
Router(config)# hub ethernet 0 2 4
Router(config-hub)# snmp trap illegal-address
Related Commands
Command
|
Description
|
hub
|
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
|
snmp-server ifindex persist
To globally enable ifIndex values that will remain constant across reboots for use by Simple Network Management Protocol (SNMP), use the snmp-server ifindex persist command in global configuration mode. To globally disable ifIndex persistence, use the no form of this command.
snmp-server ifindex persist
no snmp-server ifindex persist
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(11)S
|
This command was introduced.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
Interface Index Persistence means that ifIndex values in the IF-MIB persist across reboots, allowing for consistent identification of specific interfaces using SNMP.
The snmp-server ifindex persist global configuration command will not override interface-specific configuration. Interface-specific configuration of ifIndex persistence is performed with the [no] snmp ifindex persist and snmp ifindex clear interface configuration commands.
The [no] snmp-server ifindex persist global configuration command enables and disables ifIndex persistence for all interfaces on the routing device using ifDescr and ifIndex entries in the ifIndex table of the IF-MIB.
Examples
In the following example, ifIndex persistence is enabled for all interfaces:
Router(config)# snmp-server ifindex persist
Note that in this example if ifIndex persistence was previously disabled for a specific interface using the no snmp ifindex persist interface configuration command, ifIndex persistence will remain disabled for that interface. The global ifIndex command does not override the interface-specific commands.
Related Commands
Command
|
Description
|
snmp ifindex clear
|
Clears any previously configured snmp ifIndex commands issued in interface configuration mode for a specific interface.
|
snmp ifindex persist
|
Enables ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots (ifIndex persistence) only on a specific interface.
|
source-address
To configure source address control on a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router, use the source-address command in hub configuration mode. To remove a previously defined source address, use the no form of this command.
source-address [mac-address]
no source-address
Syntax Description
mac-address
|
(Optional) MAC address in the packets that the hub will allow to access the network.
|
Defaults
Source address control is disabled.
Command Modes
Hub configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
If you omit the MAC address, the hub uses the value in the last source address register, and if the address register is invalid, it will remember the first MAC address it receives on the previously specified port and allow only packets from that MAC address onto that port.
Examples
The following example configures the hub to allow only packets from MAC address 1111.2222.3333 on port 2 of hub 0:
Router(config)# hub ethernet 0 2
Router(config-hub)# source-address 1111.2222.3333
The following example configures the hub to use the value of the last source address register. If the address register is invalid, it will remember the first MAC address it receives on port 2 and allow only packets from the learned MAC address on port 2:
Router(config)# hub ethernet 0 2
Router(config-hub)# source-address
Related Commands
Command
|
Description
|
hub
|
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
|
speed
To configure the speed for a Fast Ethernet interface, use the speed command in interface configuration mode. To disable a speed setting, use the no form of this command.
speed {10 | 100 | auto}
no speed
Syntax Description
10
|
Configures the interface to transmit at 10 Mbps.
|
100
|
Configures the interface to transmit at 100 Mbps. This is the default.
|
auto
|
Turns on the Fast Ethernet autonegotiation capability. The interface automatically operates at 10 or 100 Mbps depending on environmental factors, such as the type of media and transmission speeds for the peer routers, hubs, and switches used in the network configuration.
|
Defaults
100 Mbps
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.2(10)P
|
This command was introduced.
|
Usage Guidelines
The autonegotiation capability is turned on for the Fast Ethernet interface by either configuring the speed auto interface configuration command or the duplex auto interface configuration command.
Table 90 describes the performance of the system for different combinations of the duplex and speed modes. The specified duplex command configured with the specified speed command produces the resulting system action.
Table 90 Relationship Between duplex and speed Commands
duplex Command
|
speed Command
|
Resulting System Action
|
duplex auto
|
speed auto
|
Autonegotiates both speed and duplex modes.
|
duplex auto
|
speed 100 or speed 10
|
Autonegotiates both speed and duplex modes.
|
duplex half or duplex full
|
speed auto
|
Autonegotiates both speed and duplex modes.
|
duplex half
|
speed 10
|
Forces 10 Mbps and half duplex.
|
duplex full
|
speed 10
|
Forces 10 Mbps and full duplex.
|
duplex half
|
speed 100
|
Forces 100 Mbps and half duplex.
|
duplex full
|
speed 100
|
Forces 100 Mbps and full duplex.
|
Examples
The following example shows how to configure a speed of 10 Mbps for Fast Ethernet interface 0:
Router(config)# interface fastethernet 0
Router(config-if)# speed 10
Related Commands
Command
|
Description
|
duplex
|
Configures the duplex operation on an interface.
|
interface fastethernet
|
Selects a particular Fast Ethernet interface for configuration.
|
show controllers fastethernet
|
Displays information about initialization block information, transmit ring, receive ring, and errors for the Fast Ethernet controller chip on the Cisco 4700, Cisco 7200 series, or Cisco 7500 series routers.
|
show interfaces fastethernet
|
Displays information about the Fast Ethernet interfaces.
|
squelch
To extend the Ethernet twisted-pair 10BASE-T capability beyond the standard 100 meters on the Cisco 4000 platform, use the squelch command in interface configuration mode. To restore the default, use the no form of this command.
squelch {normal | reduced}
no squelch
Syntax Description
normal
|
Allows normal capability. This is the default.
|
reduced
|
Allows extended 10BASE-T capability.
|
Defaults
Normal range
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following example extends the twisted-pair 10BASE-T capability on the cable attached to Ethernet interface 2:
Router(config)# interface ethernet 2
Router(config-if)# squelch reduced
srp buffer-size
To make adjustments to buffer settings on the receive side for different priority traffic, use the srp buffer-size command in interface configuration mode. To disable buffer size configurations, use the no form of this command.
srp buffer-size receive [low buffer | medium buffer | high buffer]
no srp buffer-size receive [low buffer | medium buffer | high buffer]
Syntax Description
receive
|
Allocates SDRAM buffer for incoming packets.
|
low buffer
|
(Optional) Specifies buffer size, in kilobytes, for low-priority packets. Any number from 16 to 8192. The default is 8192.
|
medium buffer
|
(Optional) Specifies buffer size, in kilobytes, for medium-priority packets. Any number from 16 to 8192. The default is 4096.
|
high buffer
|
(Optional) Specifies buffer size, in kilobytes, for high-priority packets. Any number from 16 to 8192. The default is 4096.
|
Defaults
low = 8192 kilobytes, medium = 4096 kilobytes, high = 4096 kilobytes
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was implemented on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Examples
The following example sets the buffer size for the receive side at the high setting of 17 kilobytes:
Router(config-if)# srp buffer-size receive high 17
Related Commands
Command
|
Description
|
mtu
|
Adjusts the maximum packet size MTU size.
|
srp deficit-round-robin
|
Transfers packets from the internal receive buffer to Cisco IOS software.
|
srp deficit-round-robin
To transfer packets from the internal receive buffer to Cisco IOS software, use the srp deficit-round-robin command in interface configuration mode. To disable the packet transfer, use the no form of this command.
srp deficit-round-robin [input | output] [low | medium | high ] [quantum number | deficit
number]
no srp deficit-round-robin
Syntax Description
input
|
(Optional) Specifies input buffer.
|
output
|
(Optional) Specifies output buffer.
|
low
|
(Optional) Specifies low-priority queue level.
|
medium
|
(Optional) Specifies medium-priority queue level.
|
high
|
(Optional) Specifies high-priority queue level.
|
quantum number
|
(Optional) Specifies the Deficit Round Robin (DRR) quantum value. Any number from 9216 to 32767. The default is 9216.
|
deficit number
|
(Optional) Specifies the DRR deficit value. Any number from 0 to 65535. The default is 16384.
|
Defaults
quantum: 9216
deficit: 16384
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was implemented on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Examples
The following example shows how to configure packets for the medium-priority input queue:
Router(config)# srp deficit-round-robin input medium deficit 15000
Related Commands
Command
|
Description
|
srp buffer-size
|
Makes adjustments to buffer settings on the receive side for different priority traffic.
|
srp priority-map
|
Sets priority mapping for transmitting and receiving packets.
|
srp random-detect
|
Configures WRED parameters on packets received through an SRP interface.
|
srp loopback
To loop the spatial reuse protocol (SRP) interface on an OC-12c DPTIP, use the srp loopback command in interface configuration mode. To remove the loopback, use the no form of this command.
srp loopback {internal | line} {a | b}
no srp loopback
Syntax Description
internal
|
Sets the loopback toward the network before going through the framer
|
line
|
Loops the payload data toward the network.
|
a
|
Loops back the A side of the interface (inner tx, outer rx).
|
b
|
Loops back the B side of the interface (outer tx, inner rx).
|
Defaults
No loops are configured.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was introduced on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
Use this command for troubleshooting purposes.
Examples
The following example configures the loopback test on the A side of the SRP interface:
Router(config-if)# srp loopback line a
srp priority-map
To set priority mapping for transmitting and receiving packets, use the srp priority-map command in interface configuration mode. To disable priority mapping use the no form of this command.
srp priority-map {receive {low priority | medium priority | high priority | {transmit {medium
priority | high priority}}
no srp priority-map
Syntax Description
receive
|
Specifies priority mapping for receiving packets.
|
transmit
|
Specifies priority mapping for transmitting packets.
|
low priority
|
(Optional) Specifies mapping for low-priority packets. Any number from 1 to 8. The default is 1.
|
medium buffer
|
(Optional) Specifies mapping for medium-priority packets. Any number from 1 to 8. The default is 3.
|
high buffer
|
(Optional) Specifies mapping for high-priority packets. Any number from 1 to 8. The default is 5 for receiving packets, and default is 7 for transmitting packets.
|
Defaults
receive low: 1
receive medium: 3
receive high: 5
transmit high: 7
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was implemented on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
The spatial reuse protocol (SRP) interface provides commands to enforce quality of service (QoS) functionality on the transmit side and receive side of Cisco routers. SRP uses the IP type of service (ToS) field values to determine packet priority.
The SRP interface classifies traffic on the transmit side into high- and low-priority traffic. High-priority traffic is rate shaped and has higher priority than low-priority traffic. You have the option to configure high- or low-priority traffic and can rate limit the high-priority traffic.
The srp priority-map transmit command enables the user to specify IP packets with values equal to or greater than the ToS value to be considered as high-priority traffic.
On the receive side, when WRED is enabled, SRP hardware classifies packets into high-, medium-, and low-priority packets on the basis of the IP ToS value. After classification, it stores the packet into the internal receive buffer. The receive buffer is partitioned for each priority packet. Cisco routers can employ WRED on the basis of the IP ToS value. Routers also employ the Deficit Round Robin (DRR) algorithm to transfer packets from the internal receive buffer to Cisco IOS software.
The srp priority-map receive command enables the user to classify packets as high, medium, or low based on the IP ToS value.
Examples
The following example configures Cisco 7500 series routers to transmit packets with priority greater than 5 as high-priority packets:
Router(config-if)# srp priority-map transmit high 6
Related Commands
Command
|
Description
|
srp random-detect
|
Configures WRED parameters on packets received through an SRP interface.
|
srp random-detect
To configure weighted RED (WRED) parameters on packets received through an spatial reuse protocol (SRP) interface, use the srp random-detect command in interface configuration mode. To return the value to the default, use the no form of this command.
srp random-detect {compute-interval interval | enable | input [low | medium | high] |
[exponential-weight weight | precedence precedence]}
no srp random-detect
Syntax Description
compute-interval compute-interval
|
Specifies the queue depth compute interval, in nanoseconds. Number in the range from 1 to 128. Default is 128.
|
enable
|
Enables WRED.
|
input
|
Specifies WRED on packet input path.
|
low
|
(Optional) Specifies low-priority queue level.
|
medium
|
(Optional) Specifies medium-priority queue level.
|
high
|
(Optional) Specifies high-priority queue level.
|
exponential-weight weight
|
(Optional) Specifies the queue weight, in bits. Number in the range from 0 to 6. The default is 6.
|
precedence number
|
(Optional) Specifies the input queue precedence. Number in the range from 0 to 7. The default is 7.
|
Defaults
compute-interval: 128
weight: 6
precedence: 7
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was implemented on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Examples
The following example configures WRED parameters on packets received through an SRP interface with a weight factor of 5:
Router(config-if)# srp random-detect input high exponential-weight 5
srp shutdown
To disable the spatial reuse protocol (SRP) interface, use the srp shutdown command in interface configuration mode. To restart a disabled interface, use the no form of this command.
srp shutdown [a | b]
no srp shutdown [a | b]
Syntax Description
a
|
(Optional) Specifies side A of the SRP interface.
|
b
|
(Optional) Specifies side B of the SRP interface.
|
Defaults
The SRP interface continues to be enabled until this command is issued.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was introduced on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Usage Guidelines
The srp shutdown command disables all functions on the specified side.
Examples
The following example turns off side A of the SRP interface:
Router(config-if)# srp shutdown a
srp tx-traffic-rate
To limit the amount of high-priority traffic that the spatial reuse protocol (SRP) interface can handle, use the srp tx-traffic-rate command in interface configuration mode. Use the no form of this command to disable transmitted traffic rate.
srp tx-traffic-rate number
no srp tx-traffic-rate number
Syntax Description
number
|
Transmission speed, in kilobits per second. The range is from 1 to 65535. Default is 10.
|
Defaults
number: 10
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)S
|
This command was introduced.
|
12.0(7)XE1
|
This command was implemented on Cisco 7500 series routers.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
Examples
The following example configures SRP traffic to transmit at 1000 kilobits per second:
Router(config-if)# srp tx-traffic-rate 1000
storm-control
To set the storm-control threshold value and block forwarding of unnecessary flooded traffic, use the storm-control command in interface configuration mode. To turn off storm control and restore the default threshold, use the no form of this command.
storm-control {broadcast threshold | multicast threshold | unicast threshold}
no storm-control
Syntax Description
broadcast
|
Specifies the broadcast suppression level for an interface as a percentage of total bandwidth.
|
multicast
|
Specifies the multicast suppression level for an interface as a percentage of total bandwidth.
|
unicast
|
Specifies the unicast suppression level for an interface as a percentage of total bandwidth.
|
threshold
|
Specifies the limit (percentage) placed on broadcast traffic: A threshold value of 100 percent means that no limit is placed on broadcast traffic. Valid entries are from 1 to 100.
|
Defaults
The storm-control command is disabled and the threshold value is 100 percent.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2(2)XT
|
This command was introduced on the Cisco 2600 series, the Cisco 3600 series, and the Cisco 3700 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support switchport creation on Cisco 2600 series, the Cisco 3600 series, and Cisco 3700 series routers.
|
Usage Guidelines
Use the storm-control command to block the forwarding of unnecessary flooded traffic.
Examples
The following example shows how to limit the threshold of broadcast traffic to 70 percent.
Router(config-if)# storm-control multicast 70
Related Commands
Command
|
Description
|
show interface counters
|
Displays the count of discarded packets.
|
show storm-control
|
Displays switchport characteristics, including storm-control levels set on the interface.
|
switchport mode
To set the interface type, use the switchport mode command in interface configuration mode. To reset the mode to the appropriate default mode for the device, use the appropriate no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
switchport mode {access | trunk}
Catalyst Switches
switchport mode {access | trunk | dynamic {auto | desirable}}
no switchport mode
switchport mode private-vlan {host | promiscuous}
no switchport mode private-vlan
Syntax Description
access
|
Specifies a nontrunking, nontagged single VLAN Layer 2 interface.
|
trunk
|
Specifies a trunking VLAN Layer 2 interface.
|
dynamic auto
|
Specifies that the interface convert the link to a trunk link.
|
dynamic desirable
|
Specifies that the interface actively attempt to convert the link to a trunk link.
|
private-vlan host
|
Specifies that the ports with a valid PVLAN association become active host private VLAN ports.
|
private-vlan promiscuous
|
Specifies that the ports with a valid PVLAN mapping become active promiscuous ports.
|
Defaults
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The default is access mode.
Catalyst Switches
The default mode is dependent on the platform; it should be either dynamic auto for platforms that are intended as wiring closets or dynamic desirable for platforms that are intended as backbone switches. The default for PVLAN ports is that no mode is set.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(7)XE
|
This command was introduced on the Catalyst 6000 family switches.
|
12.1(1)E
|
This command was integrated on the Catalyst 6000 family switches
|
12.1(8a)EX
|
The switchport mode private-vlan {host | promiscuous} syntax was added.
|
12.2(2)XT
|
Creation of switchports became available on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T for creation of switchports on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
If you enter a forced mode, the interface does not negotiate the link to the neighboring interface. Ensure that the interface ends match.
The no form of the command is not supported on the Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers.
Catalyst Switches
If you enter access mode, the interface goes into permanent nontrunking mode and negotiates to convert the link into a nontrunk link even if the neighboring interface does not agree to the change.
If you enter trunk mode, the interface goes into permanent trunking mode and negotiates to convert the link into a trunk link even if the neighboring interface does not agree to the change.
If you enter dynamic auto mode, the interface converts the link to a trunk link if the neighboring interface is set to trunk mode or desirable mode.
If you enter dynamic desirable mode, the interface becomes a trunk interface if the neighboring interface is set to trunk mode, desirable mode, or auto mode.
If you configure a port as a promiscuous or host PVLAN port and one of the following applies, the port becomes inactive:
•The port does not have a valid PVLAN association or mapping configured.
•The port is a span destination.
Similarly, if a private port PVLAN association or mapping is deleted or if a private port is configured as a span destination, it becomes inactive.
Examples
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The following example shows how to set the interface to access desirable mode:
Router(config-if)# switchport mode access
The following example shows how to set the interface to trunk mode:
Router(config-if)# switchport mode trunk
Catalyst Switches
The following example shows how to set the interface to dynamic desirable mode:
Router(config-if)# switchport mode dynamic desirable
The following example shows how to set a port to PVLAN host mode:
Router(config-if)# switchport mode private-vlan host
The following example shows how to set a port to PVLAN promiscuous mode:
Router(config-if)# switchport mode private-vlan promiscuous
Related Commands
Command
|
Description
|
show interfaces switchport
|
Displays administrative and operational status of a switching (nonrouting) port.
|
show interfaces trunk
|
|
switchport
|
Modifies the switching characteristics of the Layer 2-switched interface.
|
switchport private-vlan host-association
|
Defines a PVLAN association for an isolated or community port.
|
switchport private-vlan mapping
|
Defines the PVLAN mapping for a promiscuous port.
|
switchport trunk
To set the trunk characteristics when the interface is in trunking mode, use the switchport trunk commands in interface configuration mode. To reset all of the trunking characteristics back to the original defaults, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
switchport trunk {encapsulation dot1q | native vlan | allowed vlan}}
no switchport trunk {encapsulation dot1q | native vlan | allowed vlan}
Catalyst Switches
no switchport trunk {encapsulation isl | dot1q | negotiate} | {native vlan | allowed vlan |
pruning vlan}}
no switchport trunk {encapsulation {isl | dot1q | negotiate}}| {native vlan | allowed vlan |
pruning vlan}}
Syntax Description
allowed vlan vlan-list
|
Sets the list of allowed VLANs that transmit traffic from this interface in tagged format when in trunking mode. See the "Usage Guidelines" section for vlan-list formatting guidelines.
|
encapsulation dot1q
|
Sets the trunk encapsulation format to 802.1Q.
|
encapsulation isl
|
Sets the trunk encapsulation format to Inter-Switch Link (ISL).
|
encapsulation negotiate
|
Specifies that if the Dynamic Inter-Switch Link (DISL) protocol and Dynamic Packet Transport (DPT) negotiation do not resolve the encapsulation format, ISL is the selected format.
|
native vlan vlan-id
|
Sets the native VLAN for the trunk in 802.1Q trunking mode.
|
pruning vlan vlan-list
|
Sets the list of VLANs that are enabled for VTP pruning when in trunking mode. See the "Usage Guidelines" section for the vlan-list argument formatting guidelines.
|
Defaults
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The default encapsulation type is dot1q.
The default access VLAN and trunk interface native VLAN is a default VLAN that corresponds to the platform or interface hardware.
The default for all VLAN lists is to include all VLANs.
Catalyst Switches
The default encapsulation type is dependent on the platform or interface hardware itself.
The default access VLAN and trunk interface native VLAN is a default VLAN corresponding to the platform or interface hardware.
The default for all VLAN lists is to include all VLANs.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(7)XE
|
This command was introduced on the Catalyst 6000 family switch.
|
12.1(1)E
|
switchport creation on Catalyst 6000 family switches was added.
|
12.2(2)XT
|
This command was introduced to support switchport creation on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support switchport creation on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
Usage Guidelines
802.1Q trunks:
•When you connect Cisco switches through an 802.1Q trunk, make sure that the native VLAN for an 802.1Q trunk is the same on both ends of the trunk link. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning-tree loops might result.
•Disabling spanning tree on the native VLAN of an 802.1Q trunk without disabling spanning tree on every VLAN in the network can cause spanning-tree loops. Cisco recommends that you leave spanning tree enabled on the native VLAN of an 802.1Q trunk. If this is not possible, disable spanning tree on every VLAN in the network. Make sure that your network is free of physical loops before disabling spanning tree.
•When you connect two Cisco switches through 802.1Q trunks, the switches exchange spanning-tree BPDUs on each VLAN allowed on the trunks. The BPDUs on the native VLAN of the trunk are sent untagged to the reserved IEEE 802.1d spanning-tree multicast MAC address (01-80-C2-00-00-00). The BPDUs on all other VLANs on the trunk are sent tagged to the reserved Shared Spanning Tree Protocol (SSTP) multicast MAC address (01-00-0c-cc-cc-cd).
•The 802.1Q switches that are not Cisco switches maintain only a single instance of spanning-tree (the Mono Spanning Tree, or MST) that defines the spanning-tree topology for all VLANs. When you connect a Cisco switch to a switch through an 802.1Q trunk without a Cisco switch, the MST of the switch and the native VLAN spanning tree of the Cisco switch combine to form a single spanning-tree topology known as the CST.
•Because Cisco switches transmit BPDUs to the SSTP multicast MAC address on VLANs other than the native VLAN of the trunk, switches that are not Cisco switches do not recognize these frames as BPDUs and flood them on all ports in the corresponding VLAN. Other Cisco switches connected to the 802.1Q cloud receive these flooded BPDUs. This allows Cisco switches to maintain a per-VLAN spanning-tree topology across a cloud of 802.1Q switches that are not Cisco switches. The 802.1Q cloud of switches separating the Cisco switches is treated as a single broadcast segment among all switches connected to the 802.1Q cloud of switches that are not Cisco switches through 802.1Q trunks.
•Make certain that the native VLAN is the same on all of the 802.1Q trunks that connects the Cisco switches to the 802.1Q cloud of switches that are not Cisco switches.
•If you are connecting multiple Cisco switches to a non-Cisco 802.1Q cloud, all of the connections must be through 802.1Q trunks. You cannot connect Cisco switches to a non-Cisco 802.1Q cloud through ISL trunks or through access ports. Doing so will cause the switch to place the ISL trunk port or access port into the spanning-tree "port inconsistent" state and no traffic will pass through the port.
no switchport trunk native vlan Form of the Command
The no form of the no switchport trunk native vlan command resets the native mode VLAN to the appropriate default VLAN for the device.
no switchport trunk allowed vlan Form of the Command
The no form of the no switchport trunk allowed vlan command resets the list to the default list, which allows all VLANs.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The switchport trunk encapsulation command is supported only for platforms and interface hardware that can support 802.1Q formats.
The vlan-list format is all | none | add | remove | except vlan-list[,vlan-list...] where:
•all—Specifies all VLANs from 1 to 1005.
•none—Indicates an empty list. This keyword is not supported in the switchport trunk allowed vlan form of the command.
•add—Adds the defined list of VLANs to those currently set instead of replacing the list.
•remove—Removes the defined list of VLANs from those currently set instead of replacing the list.
•except—Lists the VLANs that should be calculated by inverting the defined list of VLANs.
•vlan-list—is either a single VLAN number from 1 to 1005 or a continuous range of VLANs described by two VLAN numbers, the lesser one first, separated by a hyphen that represents the VLAN IDs of the allowed VLANs when this port is in trunking mode.
Catalyst Switches
The switchport trunk encapsulation command is supported only for platforms and interface hardware that can support both ISL and 802.1Q formats.
If you enter the negotiate keyword and DISL and DTP negotiation do not resolve the encapsulation format, ISL is the selected format. The no form of the command resets the trunk encapsulation format back to the default.
The no form of the switchport trunk {encapsulation {isl | dot1q | negotiate} pruning vlan command resets the list to the default list, which enables all VLANs for VTP pruning.
The vlan-list format is all | none | add | remove | except vlan-list[,vlan-list...] where:
•all—Specifies all VLANs from 1 to 1005. This keyword is not supported in the switchport trunk pruning vlan command.
•none—Indicates an empty list. This keyword is not supported in the switchport trunk allowed vlan command.
•add—Adds the defined list of VLANs to those currently set, instead of replacing the list.
•remove—Removes the defined list of VLANs from those currently set instead of replacing the list.
•except—Lists the VLANs that should be calculated by inverting the defined list of VLANs.
•vlan-list—Is either a single VLAN number from 1 to 1005 or a continuous range of VLANs described by two VLAN numbers, the lesser one first, separated by a hyphen that represents the VLAN IDs of the allowed VLANs when this port is in trunking mode.
Examples
The following example shows how to cause a port interface configured as a switched interface to encapsulate in 802.1Q trunking format regardless of its default trunking format in trunking mode:
Router(config-if)# switchport trunk encapsulation dot1q
Related Commands
Command
|
Description
|
show interfaces switchport
|
Displays administrative and operational status of a switching (nonrouting) port.
|
switchport voice vlan
To configure the voice VLAN on the port, use the switchport voice vlan command in interface configuration mode. To return the setting to its default, use the no form of this command.
switchport voice vlan {vlan-id | dot1p | none | untagged}
no switchport voice vlan
Syntax Description
vlan-id
|
VLAN used for voice traffic. Valid IDs are from 1 to 1005 (IDs 1006 to 4096 are not supported).
Do not enter leading zeros. The switch port is an 802.1Q trunk port.
|
dot1p
|
The telephone uses priority tagging and uses VLAN 0. The switch port is an 802.1Q trunk port.
|
none
|
The telephone is not instructed through the command- line interface (CLI) about the voice VLAN. The telephone uses the configuration from the telephone keypad.
|
untagged
|
The telephone does not tag frames; it uses VLAN 4095. The switch port can be an access port or an 802.1Q trunk port.
|
Defaults
The switch default is to not automatically configure the telephone (none).
The Cisco IP 7960 telephone default is to generate an 802.1Q/802.1P frame.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2(2)XT
|
This command was introduced.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support creation of switchports.
|
Usage Guidelines
Ports that are not configured as trunk ports but that have a configured voice VLAN are access ports with a voice VLAN ID (VVID).
Examples
The following example shows how to configure VLAN 2 as the voice VLAN:
Switch(config-if)# switchport voice vlan 2
syscon address
To specify the system controller for a managed shelf, use the syscon address command in global configuration mode. To stop the management of the shelf by the system controller, use the no form of this command.
syscon address ip-address password
no syscon address
Syntax Description
ip-address
|
IP address of the system controller.
|
password
|
Password string.
|
Command Default
No system controller is specified.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
Usage Guidelines
This command is required in order for the shelf to be managed by the system controller.
Examples
The following example configures a shelf to be managed by a system controller at 10.2.3.4 using the password green:
Router# syscon address 10.2.3.4 green
Related Commands
Command
|
Description
|
show syscon sdp
|
Displays information about the Shelf Discovery Protocol.
|
syscon source-interface
|
Specifies the interface to use for the source address in SDP packets.
|
syscon shelf-id
To specify a shelf ID for a managed shelf, use the syscon shelf-id command in global configuration mode. To remove the shelf ID, use the no form of this command.
syscon shelf-id number
no syscon shelf-id
Syntax Description
number
|
Shelf ID. The value ranges from 0 to 9999.
|
Command Default
No shelf ID is specified.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
Usage Guidelines
Use this command to specify a shelf ID for a managed shelf. Some platforms, such as the Cisco AS5800, use other commands to assign a shelf ID. In these situations, do not specify a shelf ID with the syscon shelf-id command. Use the platform-specific command instead.
Examples
The following example configures a shelf ID of 5 for the managed shelf:
Router# syscon shelf-id 5
Related Commands
Command
|
Description
|
show syscon sdp
|
Displays information about the Shelf Discovery Protocol.
|
syscon address
|
Specifies the system controller for a managed shelf.
|
syscon source-interface
To specify the interface to use for the source address in Shelf Discovery Protocol (SDP) packets, use the syscon source-interface command in global configuration mode. To return to the default source interface for a packet (the interface that sent the packet from the shelf), use the no form of this command.
syscon source-interface type number
no syscon source-interface
Syntax Description
type number
|
Type and number of the interface to use for the source IP address.
|
Command Default
SDP packets use the IP address of the output interface.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
Usage Guidelines
Use this command to ensure that all SDP packets sent by the managed shelf have the same source IP address.
Examples
The following example configures a shelf to use the IP address of Ethernet interface 99/1/0:
Router# syscon source-address Ethernet99/1/0
Related Commands
Command
|
Description
|
show syscon sdp
|
Displays information about the Shelf Discovery Protocol.
|
syscon shelf-id
|
Specifies a shelf ID for a managed shelf.
|
