Table Of Contents

show ip interface

show ipc

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 rbscp

show redundancy

show redundancy (HSA redundancy)

show redundancy interlink

show (satellite initial configuration)

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)

signaling

smt-queue-threshold

snmp ifindex clear

snmp ifindex persist

snmp trap illegal-address

snmp-server ifindex persist

snr margin

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

switchport mode

switchport trunk

switchport voice vlan

syscon address

syscon shelf-id

syscon source-interface

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

 duplex auto

 speed auto

 media-type gbic

 negotiation auto

end

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

  MTU is 1500 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Outgoing access list is not set

  Inbound access list is not set

  Proxy ARP is enabled

  Local Proxy ARP is disabled

  Security level is default

  Split horizon is enabled

  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

  Peer address is 10.8.1.1

  MTU is 1492 bytes

  Helper address is not set

  Directed broadcast forwarding is disabled

  Outgoing access list is not set

  Inbound  access list is not set

  Proxy ARP is enabled

  Local Proxy ARP is disabled

  Security level is default

  Split horizon is enabled

  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 84 describes the significant fields shown in the display.

Table 84 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 85 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

To display interprocess communication (IPC) statistics, use the show ipc command in privileged EXEC mode.

show ipc {nodes | ports [open] | queue | status [cumulative] | zones}

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 the 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.
zones	Displays information about the IPC zones and seats.

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.
12.3(7)T	The zones 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 that have been generated since a clear ipc statistics command was entered. The show ipc status command with the cumulative keyword displays the IPC statistics that have been gathered since the router was rebooted, regardless of how many times the statistics have been cleared.

Zones

The IPC zone manager allows more than one group of IPC seats to exist to enable direct communication between line cards and the route processor. Use the zones keyword to display the IPC zone and seat information.

Examples

The following is sample output from the show ipc command with the nodes keyword displaying the participating seats (nodes):

Router# show ipc nodes

There are 6 nodes in this IPC realm.

   ID      Type       Name                     Last  Last

                                               Sent Heard

0.10000    Local      IPC Master                  0     0 

0.1060000  RSP-CY     RSP IPC card slot 6         9    79 

0.1050000  RSP-CY     RSP IPC card slot 5        21    22 

0.1080000  RSP-CY     RSP IPC card slot 8        21    22 

1.10000    Local      IPC Master: -Zone#1         0     0 

2.10000    Local      IPC Master: -Zone#2

Table 86 describes the significant fields shown in the display.

Table 86 show ipc nodes Field Descriptions 

Field	Description
ID	Port ID, which consists of a zone ID followed by the seat 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:

Router# show ipc ports

There are 11 ports defined.

Port ID     Type    Name            (current/peak/total) 

1.10000.1   unicast IPC Master:Zone 

1.10000.2   unicast IPC Master:Echo 

1.10000.3   unicast IPC Master:Control 

1.10000.4   unicast Remote TTY Server Port 

1.10000.5   unicast GALIOS RF :Active 

index = 0 seat_id = 0x2020000 last sent = 0 heard = 1635 0/1/1635

1.10000.6   unicast GALIOS RED:Active 

index = 0 seat_id = 0x2020000 last sent = 0 heard = 2 0/1/2

2.2020000.3 unicast GALIOS IPC:Card 2:Control 

2.2020000.4 unicast GALIOS RFS :Standby 

2.2020000.5 unicast Slave: Remote TTY Client Port 

2.2020000.6 unicast GALIOS RF :Standby 

2.2020000.7 unicast GALIOS RED:Standby 

RPC packets: current/peak/total 0/1/17

Table 87 describes the significant fields shown in the display.

Table 87 show ipc ports Field Descriptions 

Field	Description
Port ID	Port ID, which consists of a zone ID followed by the seat 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 and the IPC message queue:

Router# show ipc 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:

Router# show ipc status

IPC System Status

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.

                                                      Rx Side     Tx Side

Total Frames                                              189         140

Total from Local Ports                                    189          70

Total Protocol Control Frames                              70          44

Total Frames Dropped                                        0           0

                           Service Usage

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

                            IPC Protocol Version 0

Total Acknowledgements                                     70          44

Total Negative Acknowledgements                             0           0

                            Device Drivers

Total via Local Driver                                      0           0

Total via Platform Driver                                   0          70

Total Frames Dropped by Platform Drivers                    0           0

                    Reliable Tx Statistics

Re-Transmission                                                         0

Re-Tx Timeout                                                           0

Rx Errors                              Tx Errors

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

Unable to Deliver Msg             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

IPC Frame MemD Alloc              0

         Tx Driver Errors

No Transport                      0

MTU Failure                       0

Dest does not Exist               0

Table 88 describes the significant fields shown in the display.

Table 88 show ipc status Field Descriptions 

Field	Description
Time last IPC stat cleared	Displays the time, in dd:hh:mm (or never), 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 IPC frame memory allocation cache.
Misc Errors	Various miscellaneous errors that relate to the IPC open queue, 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 the 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 that have been generated since the router was rebooted.

Router# show ipc status cumulative

IPC System Status

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.

                                                      Rx Side     Tx Side

Total Frames                                             3473         184

Total from Local Ports                                   3473          92

Total Protocol Control Frames                              92          54

Total Frames Dropped                                        0           0

                             Service Usage

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

                     IPC Protocol Version 0

Total Acknowledgements                                      0           0

Total Negative Acknowledgements                             0           0

                            Device Drivers

Total via Local Driver                                      0           0

Total via Platform Driver                                   0          92

Total Frames Dropped by Platform Drivers                    0           0

                    Reliable Tx Statistics

Re-Transmission                                                         0

Re-Tx Timeout                                                           0

Rx Errors                              Tx Errors

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

Unable to Deliver Msg             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

IPC Frame MemD Alloc              0

         Tx Driver Errors

No Transport                      0

MTU Failure                       0

Dest does not Exist               0

The following is sample output from the show ipc command with the zones keyword displaying information about the IPC zones and seats:

Router# show ipc zones

There are 3 Zones in this IPC realm.

Zone ID   Seat ID   Name

      0    10000    IPC Default Zone                        

      1    10000    IPC TEST ZONE#1                         

      2    10000    IPC TEST ZONE#2

Table 89 describes the significant fields shown in the display.

Table 89 show ipc zones Field Descriptions 

Field	Description
Zone ID	Zone number.
Seat ID	Seat number.
Name	Zone name.

Related Commands

Command	Description
clear ipc statistics	Clears and resets the IPC statistics.

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

IPC Messages Processed:

Source       Destination  Name                      Message-Type  Time-taken

                                                        (0x)       (msec)

 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:

Router# show ipc status

                            IPC System Status

 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.

                                                    Rx Side     Tx Side

 Total Frames                                             9501        3973

 Total from Local Ports                                  14328        3258

 Total Protocol Control Frames                            1628         713

 Total Frames Dropped                                        0           0

                             Service Usage

 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

                      IPC Protocol Version 0

 Total Acknowledgments                                   1628         713

 Total Negative Acknowledgments                             0           0

                             Device Drivers

 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

                     Reliable Tx Statistics

 Re-Transmission                                                         0

 Re-Tx Timeout                                                           0

          Rx Errors                              Tx Errors

 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

          Tx Driver Errors

 No Transport                      0

 MTU Failure                       0

 Dest does not Exist               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 90 lists the output values for this command.

Table 90 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

 Head=021  Tail=021

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 91 describes the significant fields shown in the display.

Table 91 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

        Num DMA ints: 143330469

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

        FIFO config: 0x00000101

Table 92 describes the fields shown in the preceding display.

Table 92 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

CAIM0 Context Table

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 93 describes the fields shown in the preceding display.

Table 93 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

CAIM0 Page Table

    Page  0x0000 Comp cnxt: 8104F320  Decmp cnxt: 8104F340  Algo: Stac

Table 94 describes the fields shown in the preceding display.

Table 94 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

CompressionAim0

    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

Interface ISA5/1 :

Encryption Mode = IPSec 

Addresses of Rings and instance structure:

High Priority Rings

   TX: 0x4B0E97C0 TX Shadow:0x62060E00

   RX: 0x4B0EB840 RX Pool:0x4B0EBC80 RX Pool Shadow:0x62068E58

Low Priority Rings

   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

Interface ISA5/1 : 

        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 95 describes the significant fields shown in the display.

Table 95 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

Encryption Mode = IPSec

Addresses of Rings and instance structure:

Low Priority Queue:

    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}

High Priority Rings:

   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

Misc registers:

mini-omq=0xF2DB460, shdw=0x63102714

Group0=0x3D800000, Group1=0x3D801000

IndexReg = 0xDFFE700

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 

Interface VAM 2/1 :

        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 96 describes the significant fields shown in the display.

Table 96 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:

Router# show pci aim

AIM Slot 0: ID 0x012D

        Hardware Revision        : 1.0

        EEPROM format version 4

        EEPROM contents (hex):

          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

Interface            Power

-------------------- -----

FastEthernet0/4      no

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 rbscp

To display state and statistical information about Rate Based Satellite Control Protocol (RBSCP) tunnels, use the show rbscp command in user EXEC or privileged EXEC mode.

show rbscp {all | state | statistics} [tunnel tunnel-number]

Syntax Description

all	Displays both RBSCP state and RBSCP statistical information.
state	Displays the RBSCP state information.
statistics	Displays RBSCP statistical information.
tunnel	(Optional) Displays the RBSCP information for the tunnel interface specified in the tunnel-number argument. If a tunnel interface is not specified, information for all RBSCP tunnels is displayed. •tunnel-number—Number of the tunnel interface in the range from 0 to 2147483647.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
12.3(7)T	This command was introduced.

Usage Guidelines

The output of this command is most helpful to the person who has the task of configuring and monitoring RBSCP tunnels. The output shows various state and statistical information about RBSCP tunnels.

Examples

The following is sample output from the show rbscp all command:

Router# show rbscp all

Tunnel0 is up, line protocol is up

RBSCP operational state:  IS OPENING

RBSCP operating mode: (264h) ack_split window_stuffing inorder SCTP_report

  window step: 1

  drop scale : 0

  ACK split size: 4

  input drop scale: 2

  initial TSN: 1h

  fuzz factor: 0

  next TSN: 1h

  next sequence: 1h

  current outstanding: 0

  max out per RTT: 68750

  packets since SACK: 0

  cumulative ack: 0h

  TSN at SACK: 1h

  last cumulative ack: 0h

  last delivered TSN: 0h

  next FWDTSN corr: 6h

  RTO: 704 ms

  RTT: 550 ms     srtt_sa: 0      srtt_sv: 4

  sentQ: num packets: 0, num bytes: 0

  tmitQ: num packets: 0, num bytes: 0

RBSCP protocol statistics:

  Init FWD-TSNs sent 0, received 0

  TUNNEL-UPs sent 0, received 0

  CLOSEDs sent 0, received 0

  TSNs sent 0, resent 0, lost by sender 0

  TSNs received 0 (duplicates 0)

  FWD-TSNs sent 63 (heartbeats 0)

  FWD-TSNs received 0 (ignored 0)

  FWD-TSNs caused 0 packet drops, 0 whole window drops

  SACKs sent 0, received 0 (ignored 0)

  Recovered with RTX 0

  Received with delay 0

  Most released at once 0

  Failed sends into the: tunnel 1, network 0

  Dropped due to: excess delay 0, tmit queue full 0

  Max on any queue: num packets: 0, num bytes: 0

  Max outstanding: 0

Table 97 describes the significant fields shown in the display.

Table 97 show rbscp all Field Descriptions

Field	Description
tunnel is {up | down}	Interface is currently active (up) or inactive (down).
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.
RBSCP operational state	Indicates the current RBSCP state.
RBSCP operating mode	Indicates the RBSCP operating mode.
window step	Step size for the window scale.
drop scale	Scale factor for the number of bytes that can be queued before packets are dropped on the output side.
Ack split size	Number of TCP acknowledgements to send for every ack received.
input drop scale	Scale factor for the number of bytes that can be queued before packets are dropped on the input side.
initial TSN	Transport Sequence Number (TSN) of the first outgoing RBSCP/IP packet sent to a peer. RBSCP uses sequence numbers to ensure a reliable service. Peers will send the TSN back in the acknowledgment packet.
fuzz factor	Value added to the RBSCP delay clock to pad the delay when large round-trip time (RTT) fluctuations occur.
next TSN	TSN of the next outgoing RBSCP/IP packet.
next sequence	Next sequence number to use, in hex.
current outstanding	Current number of bytes that are in transit or are unacknowledged.
max out per RTT	Maximum number of bytes allowed to be sent out per RTT.
packets sent since SACK	Number of packets sent since an RBSCP Selective Acknowledgement (SACK).
cumulative ack	Cumulative acknowledgement point which is the highest in sequence TSN that was received from a peer.
TSN at SACK	Value of highest TSN for the last SACK that was received from a peer.
last cumulative ack	Last cumulative acknowledgement point that was received from the peer.
last delivered TSN	Last TSN received that was subsequently delivered to an upper level protocol.
next FWDTSN corr	Next FWD_TSN correlation entry to use.
RTO	Retransmission timeout, in milliseconds.
RTT	Round-trip time estimate, in milliseconds.
srtt_sa	Smoothed round-trip time average.
srtt_sv	Smoothed round-trip time variance.
sentQ	Number of packets and bytes sent but not yet acknowledged.
tmitQ	Number of packets and bytes ready to be sent.
Init FWD-TSNs	Number of TSNs sent and received for initializing the RBSCP tunnel.
TUNNEL-UPs	Number of TUNNEL_UP messages sent and received.
CLOSEDs	Number of CLOSED messages sent and received.
heartbeats	Heartbeats are equivalent to keepalive messages.
Recovered with RTX	Number of packets recovered using a retransmitted message.
Received with delay	Number of packets that included a delay value.
Most released at once	Maximum burst of packets sent in one interval.
Failed sends	Number of packets that were sent but failed because of an internal error, such as no route or the underlying interface is down.

The following is sample output from the show rbscp state command:

Router# show rbscp state

Tunnel0 is up, line protocol is up

RBSCP operational state:  IS OPENING

RBSCP operating mode: (264h) ack_split window_stuffing inorder SCTP_report

  window step: 1

  drop scale : 0

  ACK split size: 4

  input drop scale: 2

  initial TSN: 1h

  fuzz factor: 0

  next TSN: 1h

  next sequence: 1h

  current outstanding: 0

  max out per RTT: 68750

  packets since SACK: 0

  cumulative ack: 0h

  TSN at SACK: 1h

  last cumulative ack: 0h

  last delivered TSN: 0h

  next FWDTSN corr: 0h

  RTO: 704 ms

  RTT: 550 ms     srtt_sa: 0      srtt_sv: 4

  sentQ: num packets: 0, num bytes: 0

  tmitQ: num packets: 0, num bytes: 0

The following is sample output from the show rbscp statistics command:

Router# show rbscp statistics tunnel 0

Tunnel0 is up, line protocol is up

RBSCP protocol statistics:

  Init FWD-TSNs sent 0, received 0

  TUNNEL-UPs sent 0, received 0

  CLOSEDs sent 0, received 0

  TSNs sent 0, resent 0, lost by sender 0

  TSNs received 0 (duplicates 0)

  FWD-TSNs sent 136 (heartbeats 0)

  FWD-TSNs received 0 (ignored 0)

  FWD-TSNs caused 0 packet drops, 0 whole window drops

  SACKs sent 0, received 0 (ignored 0)

  Recovered with RTX 0

  Received with delay 0

  Most released at once 0

  Failed sends into the: tunnel 1, network 0

  Dropped due to: excess delay 0, tmit queue full 0

  Max on any queue: num packets: 0, num bytes: 0

  Max outstanding: 0

Related Commands

Command	Description
clear rbscp	Resets and restarts RBSCP tunnels.

show redundancy

To display information about the current redundant configuration and recent changes in states, use the show redundancy command in EXEC mode. To display current or historical status and related information on planned or logged handovers, use the show redundancy command in privileged EXEC mode.

EXEC Mode

show redundancy

Privileged EXEC Mode

show redundancy [clients | counters | debug-log | handover | history | states | inter-device]

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).
inter-device	(Optional) Redundancy inter-device operational state and statistics.

Command Modes

EXEC
Privileged EXEC

Command History

Release	Modification
11.3(6)AA	This command was introduced in privileged EXEC mode.
12.2(8)T	The privileged EXEC mode form of this command was integrated. Support for the Cisco AS5800 and Cisco AS5850 is not included in this release.
12.2(11)T	The privileged EXEC mode form of this command was implemented on the Cisco AS5800 and Cisco AS5850.
12.3(8)T	The inter-device keyword was added to the privileged EXEC form of the command.
12.2(8)MC2	This command was introduced in EXEC mode.
12.3(11)T	The EXEC form of this command was integrated.

Usage Guidelines

EXEC Mode

When used in EXEC mode, this command has no keywords or arguments.

Privileged EXEC Mode

In the standby group name group-name command, if you omit the group-name or if you enter a group name that does not begin with one or two, the configuration will fail and there will be a mismatch in the information displayed by the show redundancy and show standby commands.

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

Cisco AS5850 Example

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

Mode = Duplex

Unit = Preferred Primary

Unit ID = 6

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

Communications = Up

client count = 3

client_notification_TMR = 30000 milliseconds

keep_alive TMR = 4000 milliseconds

keep_alive count = 1

keep_alive threshold = 7

RF debug mask = 0x0

Cisco AS5800 Example

The following is sample output from the show redundancy command on a Cisco AS5800:

Router# show redundancy

DSC in slot 12:

Hub is in 'active' state.

Clock is in 'active' state.

DSC in slot 13:

Hub is in 'backup' state.

Clock is in 'backup' state.

Cisco AS5800 with History Example

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

Cisco AS5800 Router Shelves as Failover Pair Example

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

RouterA# show redundancy

failover mode enabled, failover group = 32

Currently ACTIVE role.

DSC in slot 12:

Hub is in 'active' state.

Clock is in 'active' state.

No connection to slot 13

RouterA# reload

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)

RouterB# show redundancy

failover mode enabled, failover group = 32

Currently BACKUP role.

No connection to slot 12

DSC in slot 13:

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:

RouterB# show redundancy

failover mode enabled, failover group = 32

Currently ACTIVE role.

No connection to slot 12

DSC in slot 13:

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

EXEC Mode Example

The following is sample output generated by this command in EXEC mode.

Router# show redundancy

MWR1900 is the Active Router 

Previous States with most recent at bottom 

 INITL_INITL     Dec 31 19:00:00.000 

 LISTN_INITL     Feb 28 19:00:15.568 

 LISTN_LISTN     Feb 28 19:00:15.568 

 SPEAK_LISTN     Feb 28 19:00:18.568 

 SPEAK_SPEAK     Feb 28 19:00:18.568 

 STDBY_SPEAK     Mar 19 08:54:26.191 

 ACTIV_SPEAK     Mar 19 08:54:26.191 

 ACTIV_STDBY     Mar 19 08:54:26.191 

 ACTIV_ACTIV     Mar 19 08:54:26.191 

 INITL_ACTIV     Mar 19 08:56:22.700 

 INITL_INITL     Mar 19 08:56:22.700 

 INITL_LISTN     Mar 19 08:56:28.544 

 LISTN_LISTN     Mar 19 08:56:28.652 

 LISTN_SPEAK     Mar 19 08:56:31.544 

 SPEAK_SPEAK     Mar 19 08:56:31.652 

 SPEAK_STDBY     Mar 19 08:56:34.544 

 SPEAK_ACTIV     Mar 19 08:56:34.544 

 STDBY_ACTIV     Mar 19 08:56:34.652 

 ACTIV_ACTIV     Mar 19 08:56:34.652 

 INITL_ACTIV     Mar 19 10:20:41.455 

 INITL_INITL     Mar 19 10:20:41.455 

 INITL_LISTN     Mar 19 10:20:49.243 

 LISTN_LISTN     Mar 19 10:20:49.299 

 LISTN_SPEAK     Mar 19 10:20:52.244 

 SPEAK_SPEAK     Mar 19 10:20:52.300 

 SPEAK_STDBY     Mar 19 10:20:55.244 

 STDBY_STDBY     Mar 19 10:20:55.300 

 ACTIV_STDBY     Mar 19 10:21:01.692 

 ACTIV_ACTIV     Mar 19 10:21:01.692 

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.
mode y-cable	Invokes y-cable mode.
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 standby	Displays the standby configuration.
standalone	Specifies whether the MWR 1941-DC router is used in a redundant or stand-alone configuration.
standby	Sets HSRP attributes.

show redundancy (HSA redundancy)

To display the current redundancy mode, use the show redundancy command in user EXEC or privileged EXEC mode.

show redundancy

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
11.2 GS	This command was introduced.
12.0(16)ST	This command was modified to display information about Route Processor Redundancy (RPR).
12.0(19)ST1	This command was modified to display information about RPR Plus (RPR+).
12.3(7)T	The command modifications to support RPR and RPR+ were integrated into Cisco IOS Release 12.3(7)T.

Usage Guidelines

Use this command to display the redundancy mode of a Cisco 7500 series router. The default redundancy mode is High System Availability (HSA). Use the redundancy configuration command to enter redundancy configuration mode. Use the mode rpr command in redundancy configuration mode to configure RPR as the high availability mode. HSA is the default high availability mode.

Examples

The following is sample output from the show redundancy command for a router with RPR configured:

Router# show redundancy

redundancy mode rpr

hw-module slot 2 image slot0:rsp-pv-mz

hw-module slot 3 image slot0:rsp-pv-mz

Related Commands

Command	Description
hw-module sec-cpu reset	Resets and reloads the standby RSP with the specified Cisco IOS image and executes the image.
hw-module slot image	Specifies a high availability Cisco IOS image to run on a standby RSP.
mode (HSA redundancy)	Configures the redundancy mode.
redundancy	Enters redundancy configuration mode.

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

5000

4500

4000

3500

3000

2500

2000

1500

1000

  500

     0....5....1....1....2....2....3....3....4....4....5....5....

               0    5    0    5    0    5    0    5    0    5

                    Interlink Rx BPS (last 60 seconds)

                       # = Bits Per Second (x1000)

      2111112111112121111121111111211111111111111111111111111111

5000

4500

4000

3500

3000

2500

2000

1500

1000

  500

     0....5....1....1....2....2....3....3....4....4....5....5....

               0    5    0    5    0    5    0    5    0    5

                    Interlink Rx BPS (last 60 minutes)

            * = maximum BPS (x1000)    # = average BPS (x1000)

1111222221111111112111111111111111211211111111111111121112111111111111

5000

4500

4000

3500

3000

2500

2000

1500

1000

  500

0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.

               0    5    0    5    0    5    0    5    0    5    0     

5    0

                    Interlink Rx BPS (last 72 hours)

            * = maximum BPS (x1000)    # = average BPS (x1000)

show (satellite initial configuration)

To display the initial configuration parameters for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the show command in satellite initial configuration mode.

show

Syntax Description

This command has no arguments or keywords.

Command Modes

Satellite initial configuration

Command History

Release	Modification
12.3(14)T	This command was introduced.

Usage Guidelines

This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.

You can also view the satellite initial configuration parameters by entering the service-module satellite slot/0 status command in privileged EXEC mode.

Examples

The following example shows the satellite initial configuration parameters for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT):

Router(sat-init-config)# show 

!

! Initial Configuration Parameters:

!

id aa-group 298

id software group 598

id vsat 6201

mode download

mode two-way

outbound data-pid 514

outbound data-rate 15000000

outbound frequency 1201000

outbound id 2

outbound modulation-type DVB

outbound sync ip address 172.16.0.3

outbound viterbi-rate 1/2

!

!

Router(sat-init-config)#

Related Commands

Command	Description
service-module satellite status	Displays status information related to the hardware and software on the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), including the initial configuration parameters.

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

Data in Interval 30:

    0 Line Code Violations, 0 Path Code Violations

    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 31:

    0 Line Code Violations, 0 Path Code Violations

    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 32:

    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

Receiver has AIS alarm,

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:

    remote loopback

    Failed to loopup remote

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

    loss of frame         :    0,

    AIS alarm             :    1, current duration 0:00:49

    Remote alarm          :    0,

    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:

    dte loopback

    duration 00:00:58

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

    loss of frame         :    0,

    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

Connection state: Idle

Receiver has no alarms.

CSU/DSU Alarm mask is 0

Current line rate is 56 Kbits/sec

Last module self-test (done at startup): Passed

Last clearing of alarm counters 4d02h

    oos/oof               :    0,

    loss of signal        :    0,

    loss of sealing curren:    0,

    loss of frame         :    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,

CSU/DSU Alarm mask is 4

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

    loss of frame         :    0,

    rate adaptation attemp:    0,

Table 98 describes the fields displayed by the show service-module serial command.

Table 98 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 99 describes the fields shown in the display.

Table 99 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 display switchport characteristics, including storm-control levels set on the interface, use the show storm-control command in privileged EXEC mode.

show storm-control [interface-type interface-number] [broadcast | multicast | unicast | history]

Syntax Description

interface-type interface-number	(Optional) Port for which information is to be displayed.
broadcast	(Optional) Displays broadcast storm information. This is the default.
multicast	(Optional) Displays multicast storm information.
unicast	(Optional) Displays unicast storm information.
history	(Optional) Displays storm history on a per-port basis.

Defaults

If the interface-type and interface-number values are omitted, the show storm-control command displays storm-control settings for all ports on the switch.

You can display broadcast, multicast, or unicast packet-storm information by using the corresponding keyword. When no keyword option is specified, the default is to display broadcast storm-control information.

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.
12.2(15)ZJ	The interface-type and interface-number arguments and the broadcast, multicast, unicast, and history keywords were added to support the Ethernet switch network module on the Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
12.3(4)T	The arguments and keywords were integrated into Cisco IOS Release 12.3(4)T on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.

Examples

The following is partial sample output from the show storm-control broadcast command:

Router# show storm-control broadcast

Interface  Filter State   Upper    Lower    Current

---------  -------------  -------  -------  -------

Fa0/1      <inactive>     100.00%  100.00%    0.00%

Fa0/2      <inactive>     100.00%  100.00%    0.00%

Fa0/3      <inactive>     100.00%  100.00%    0.00%

Fa0/4      Forwarding      30.00%   20.00%   20.32%

.

.

.

Table 100 describes the fields shown in the display.

Table 100 show storm-control broadcast Field Descriptions 

Field	Description
Interface	Displays the ID of the interface.
Filter State	Displays the status of the filter: •Blocking—Storm control is enabled, a storm has occurred, and the action is filter. •Forwarding—Storm control is enabled, and a storm has not occurred. •Inactive—Storm control is disabled. •Shutdown—Storm control is enabled, a storm has occurred, and the action is to shut down. Note If an interface is disabled by a broadcast, multicast, or unicast storm, the filter state for all traffic types is shutdown.
Upper	Displays the rising suppression level as a percentage of total available bandwidth.
Lower	Displays the falling suppression level as a percentage of total available bandwidth.
Current	Displays the bandwidth utilization of a specific traffic type as a percentage of total available bandwidth. This field is valid only when storm control is enabled.

The following is sample output from the show storm-control fastethernet0/4 history command, which displays the ten most recent storm events for an interface:

Router# show storm-control fastethernet0/4 history

 Interface Fa0/4 Storm Event History 

 Event Type          Event Start Time  Duration (seconds)

 ------------------  ----------------  ------------------

 Unicast             04:58:18          206      

 Broadcast           05:01:54          n/a

 Multicast           05:01:54          n/a

 Unicast             05:01:54          108      

 Broadcast           05:05:00          n/a

 Multicast           05:05:00          n/a

 Unicast             05:06:00          n/a

 Broadcast           05:09:39          n/a

 Multicast           05:09:39          n/a

 Broadcast           05:11:32          172 

Table 101 describes the fields shown in the display.

Table 101 show storm-control history Field Descriptions 

Field	Description
Interface	Displays the ID of the interface.
Event Type	Displays the type of storm event. The event type is one of the following: •Broadcast •Multicast •Unicast
Event Start Time	Time when the event started, in hours, minutes, seconds.
Duration (seconds)	Duration time of the event, in seconds. Note The duration field could be n/a when a storm is still present or when a new storm of a different type occurs before the current storm ends.

Related Commands

Command	Description
show interface counters	Displays the count of discarded packets.
storm control	Enables broadcast, multicast, or unicast storm control on a port.

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:

Router# show syscon sdp

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

11773 Total SDP packets

    0 packets with bad MD5 hash

    5884 Hello packets received

    5889 Hello packets sent

    0 Command packets received

    0 Command packets sent

Table 102 describes the fields shown in the sample display.

Table 102 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:

Router# show tdm data

Motherboard MT8980 TDM Device 0, Control Register = 0x1F, ODE Register = 0xE1

Data Memory for ST0:

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

Data Memory for ST1:

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

Data Memory for ST2:

.

.

.

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

ODE Register: 0x0001

Connection Memory: 0x00ED, Output is Disable

Connection Map: STi7 CHi13 ----> STo1 CHo2

Data Memory: 0x00FF

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

  HDLC   Streams start at 4

  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:

Router# show tdm pool

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.

signaling

To enable channel-associated signaling (CAS), use the signaling command in CEM configuration mode. To disable signaling, use the no form of this command.

signaling

no signaling

Syntax Description

This command has no arguments or keywords.

Defaults

CAS is disabled.

Command Modes

CEM configuration

Command History

Release	Modification
12.3(7)T	This command was introduced.

Examples

The following example demonstrates how to enable signaling.

Router(config-cem)# signaling

Related Commands

Command	Description
cem	Enters circuit emulation configuration mode.
show cem	Displays CEM channel statistics.

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

Router(config-if)# exit

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

Router(config-if)# exit

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

Router(config-if)# exit

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

Router(config-if)# exit

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.

snr margin

To set the signal-to-noise ratio (SNR) on the controller to improve the line stability, use the snr margin command in controller configuration mode. To reset the SNR to default settings, use the no form of this command.

snr margin {current [snr-value | disable] | snext [snr-value | disable]}

no snr margin {current | snext}

Syntax Description

current	Sets the current signal-to-noise ratio on the controller. To disable the current SNR, set current to disable.
snext	Sets the Self Near End Cross Talk (SNEXT) signal-to-noise ratio. To disable the SNEXT, set snext to disable.
snr-value	(Optional) Value, in decibels (dB), for the signal-to-noise ratio on the controller or the SNEXT. Range is from -10 to 10 . The default value is 0.
disable	(Optional) Disables the snr margin command.

Defaults

The default value for both current and snext is 0.

Command Modes

Controller configuration

Command History

Release	Modification
12.3(4)XD	This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
12.3(4)XG	This command was integrated into Cisco IOS Release 12.3(4)XG on the Cisco 1700 series routers.
12.3(7)T	This command was integrated into Cisco IOS Release 12.3(7)T on Cisco 2600 series, Cisco 3631, and Cisco 3700 series routers.
12.3(11)T	This command was integrated into Cisco IOS Release 12.3(11)T on Cisco 2800 series and Cisco 3800 series routers.

Usage Guidelines

The snr margin current command can create a more stable line by making the line train more than the current noise margin plus signal-to-noise ratio threshold during training time. If any external noise is applied that is less than the set SNR margin, the line will be stable.

The snr margin snext command can create a more stable line by making the line train more than the Self Near End Cross Talk (SNEXT) threshold during training time. If any external noise is applied that is less than the set SNEXT margin, the line will be stable.

Examples

SNR with SNEXT Disabled

The following example configures the signal-to-noise ratio to 5 dB on the DSL controller in slot 3 and port 0 and disables the SNEXT signal-to-ratio.

Router(config)# controller dsl 3/0

Router(config-controller)# snr margin current 5

Router(config)# controller dsl 3/0

Router(config-controller)# snr margin snext disable

SNR Margin set on CPE Router

The following example shows the snr margin snext 5 command issued on the customer premises equipment (CPE) router.

Router_CPE(config)# controller dsl 1/0

Router_CPE(config-controller)# snr margin snext 5 

Router_CPE(config-controller)#

*Jun 15 18:29:38.511: %CONTROLLER-5-UPDOWN: Controller DSL 1/0, changed state tn

*Jun 15 18:29:40.511: %LINK-3-UPDOWN: Interface ATM1/0, changed state to down

*Jun 15 18:29:41.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM1/0, cn

*Jun 15 18:30:04.579:  DSL 1/0 controller Link up! line rate: 4608 Kbps

*Jun 15 18:30:04.579: %CONTROLLER-5-UPDOWN: Controller DSL 1/0, changed state tp

*Jun 15 18:30:12.351: %LINK-3-UPDOWN: Interface ATM1/0, changed state to up

*Jun 15 18:30:13.351: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM1/0, cp

Status on CO Side with SNR Margin set on CPE Router

The following example is the resulting output on the router that is configured as the central office (CO) side after the snr margin snext 5 command is entered on the CPE side.

Router_CO#      

Jun 15 18:29:42.781: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state ton

Jun 15 18:29:44.784: %LINK-3-UPDOWN: Interface ATM0/0, changed state to down

Jun 15 18:29:45.786: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, chn

Jun 15 18:30:03.122:  DSL 0/0 controller Link up! line rate: 4608 Kbps

Jun 15 18:30:03.122: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state top

Jun 15 18:30:11.456: %LINK-3-UPDOWN: Interface ATM0/0, changed state to up

Jun 15 18:30:12.458: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, chp

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 103 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 103 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