Syntax Description

Module and port number; see the “Usage Guidelines” section for valid values.

Command Default

This command has no default settings.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(17b)SXA

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

Usage Guidelines

The
pos,
atm, and
ge-wan keywords are supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

The
interface-number designates the module and port number. Valid values depend on the chassis and module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number are from 1 to 48.

Examples

This example shows how to list all of the VLAN mappings that are configured on a port and indicate whether such mappings are enabled or disabled on the port:

The command output was modified to display information about the Unicast RPF notification feature.

12.2(33)SXI2

This command was modified. The command output was modified to display information about the Unicast RPF notification feature.

Cisco IOS XE Release 2.5

This command was modified. This command was implemented on the Cisco ASR 1000 Series Aggregation Services Routers.

Cisco IOS XE Release 3.9S

This command was implemented on Cisco 4400 Series ISRs.

Usage Guidelines

The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable (which means that it 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 lets the software 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, information for that specific interface is displayed. If you specify no optional arguments, information on all the interfaces is displayed.

When an asynchronous interface is encapsulated with PPP or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A
showipinterface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.

You can use the
showipinterfacebrief command to display a summary of the router interfaces. This command displays the IP address, the interface status, and other information.

The
showipinterfacebrief command does not display any information related to Unicast RPF.

Examples

The following example shows configuration information for interface Gigabit Ethernet 0/3. In this example, the IP flow egress feature is configured on the output side (where packets go out of the interface), and the policy route map named PBRNAME is configured on the input side (where packets come into the interface).

The following example shows interface information on Gigabit Ethernet interface 0/3. In this example, MPF is enabled, and both Policy Based Routing (PBR) and NetFlow features are not supported by MPF and are ignored.

Shows the VRF instance where the PPP peer routes and AAA per-user routes are being installed.

IP multicast fast switching

Shows whether multicast fast switching is enabled for the interface.

IP route-cache flags are Fast

Shows whether NetFlow is 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
ipflowingresscommand. Shows "Flow" to specify that NetFlow is enabled on a main interface using the
iproute-cacheflow command.

Router Discovery

Shows whether the discovery process is enabled for this interface. It is generally disabled on serial interfaces.

IP output packet accounting

Shows whether IP accounting is enabled for this interface and what the threshold (maximum number of entries) is.

TCP/IP header compression

Shows whether compression is enabled.

WCCP Redirect outbound is disabled

Shows the status of whether packets received on an interface are redirected to a cache engine. Displays "enabled" or "disabled."

WCCP Redirect exclude is disabled

Shows the status of whether packets targeted for an interface will be excluded from being redirected to a cache engine. Displays "enabled" or "disabled."

Netflow Data Export (hardware) is enabled

NetFlow Data Expert (NDE) hardware flow status on the interface.

The table below describes the significant fields shown in the display.

Examples

In the following example, command show ip interface brief shows a summary of the interfaces and their status on the device.

Syntax Description

(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.

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to 12.2(17d)SXB.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

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.

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.

Use the
queue keyword to display information about the IPC retransmission queue and the IPC message queue.

Status

Use thestatus keyword to display the IPC statistics that have been generated since a
clearipcstatistics command was entered. The
showipcstatus 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 thezones keyword to display the IPC zone and seat information.

Examples

The following is sample output from the
showipccommand with the
nodeskeyword displaying the participating seats (nodes):

The table below describes the significant fields shown in the display.

Table 4 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
showipccommand with the
queuekeyword 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
showipccommand with the
statuskeyword displaying information about the local IPC server:

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.

The table below describes the significant fields shown in the display.

Table 6 show ipc zones Field Descriptions

Field

Description

Zone ID

Zone number.

Seat ID

Seat number.

Name

Zone name.

Related Commands

Command

Description

clearipcstatistics

Clears and resets the IPC statistics.

show ipc hog-info

To provide information about interprocess communication (IPC) messages that consume excessive CPU, use the showipchog-infocommand in privileged EXEC mode.

showipchog-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:

Module and port number; see the “Usage Guidelines” section for valid values.

nullinterface-number

Specifies the null interface; the valid value is
0.

port-channelnumber

Specifies the channel interface; valid values are a maximum of 64 values ranging from 1 to 282.

vlanvlan-id

Specifies the VLAN; valid values are from 1 to 4094.

status

Displays status information about the Layer 3 manager.

Command Default

This command has no default settings.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

Usage Guidelines

The
interface-number argument designates the module and port number. Valid values for
interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.

The
port-channelnumbervalues from 257 to 282 are supported on the CSM and the FWSM only.

Cisco ASR 901 Series Aggregation Services Router

Syntax Description

(Optional) Number of the channel group. The following are valid values:

Cisco IOS 12.2 SB and Cisco IOS XE 2.4 Releases--from 1 to 64

Cisco IOS 12.2 SR Releases--from 1 to 308

Cisco IOS 12.2 SX Releases--from 1 to 496

Cisco IOS 15.1S Releases—from 1 to 564

Cisco ASR 901 Series Aggregation Services Router—from 1 to 8

counters

Displays information about the LACP traffic statistics.

internal

Displays LACP internal information.

neighbor

Displays information about the LACP neighbor.

detail

(Optional) Displays detailed internal information when used with the
internal keyword and detailed LACP neighbor information when used with the
neighbor keyword.

multi-chassis

Displays information about mLACP.

load-balance

Displays mLACP load balance information.

group

Displays mLACP redundancy group information,

number

Integer value used with the
group and
port-channel keywords.

Values from 1 to 4294967295 identify the redundancy group.

Values from 1 to 564 identify the port-channel interface.

port-channel

Displays mLACP port-channel information.

sys-id

Displays the LACP system identification. It is a combination of the port priority and the MAC address of the device

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Cisco IOS Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.2(33)SRB

Support for this command on the Cisco 7600 router was integrated into Cisco IOS Release 12.2(33)SRB.

Cisco IOS XE Release 2.4

This command was integrated into Cisco IOS XE Release 2.4.

12.2(33)SRE

This command was modified. The
multi-chassis,
group, and
port-channelkeywords and
number argument were added.

15.1(3)S

This command was modified. The
load-balance keyword was added.

15.1(2)SNG

This command was implemented on the Cisco ASR 901 Series Aggregation Services Router.

Usage Guidelines

Use the
show
lacp command to troubleshoot problems related to LACP in a network.

If you do not specify a value for the argument
channel-group-number, all channel groups are displayed. Values in the range of 257 to 282 are supported on the CSM and the FWSM only.

Examples

Examples

This example shows how to display the LACP system identification using the
show lacp sys-idcommand:

Device> show lacp sys-id
8000,AC-12-34-56-78-90

The system identification is made up of the system priority and the system MAC address. The first two bytes are the system priority, and the last six bytes are the globally administered individual MAC address that is associated to the system.

Examples

This example shows how to display the LACP statistics for a specific channel group:

The following table describes the significant fields shown in the display.

Table 11 show lacp neighbors Field Descriptions

Field

Description

Port

Port on which link bundling is configured.

Partner System ID

Peer’s LACP system identification (sys-id). It is a combination of the system priority and the MAC address of the peer device.

Partner Port Number

Port number on the peer device

Age

Number of seconds since the last LACP PDU was received on the port.

Flags

Indicators of device activity.

Port Priority

Port priority setting.

Admin Key

Defines the ability of a port to aggregate with other ports.

Oper Key

Determines the aggregation capability of the link.

Port State

Activity state of the port.

See the Port State description in the show lacp internal Field Descriptions table for state variables.

If no PDUs have been received, the default administrative information is displayed in braces.

Related Commands

Command

Description

clearlacpcounters

Clears the statistics for all interfaces belonging to a specific channel group.

lacpport-priority

Sets the priority for the physical interfaces.

lacpsystem-priority

Sets the priority of the system.

show link state group

To
display the link-state group information., use the showlinkstategroup command
in user EXEC or privileged EXEC mode
.

showlinkstategroupdetail

Syntax Description

detail

Displays the detailed information about the group.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

15.1(1)S

This command was introduced.

Usage Guidelines

Link State Ttracking (LST), also known as trunk failover, is a feature that binds the link state of multiple interfaces. When you configure LST for the first time, add upstream interfaces to the link state group before adding the downstream interface, otherwise the downstream interfaces would move into error-disable mode. The maximum number of link state groups configurable is 10.

Syntax Description

(Optional) Displays the entries for a specific destination IP address.

detail

(Optional) Specifies a detailed output.

flow

(Optional) Specifies the flow type.

tcp |
udp

Selects the flow type.

vlanvlan-id

(Optional) Specifies the virtual local area network (VLAN) ID; valid values are from 1 to 4094.

macddestination-mac-address

(Optional) Specifies the destination MAC address.

macssource-mac-address

(Optional) Specifies the source Media Access Control (MAC) address.

modulenumber

(Optional) Displays the entries that are downloaded on the specified module; see the “Usage Guidelines” section for valid values.

sourcehostname

(Optional) Displays the entries for a specific source address.

sourceip-address

(Optional) Displays the entries for a specific source IP address.

count

(Optional) Displays the total number of MLS entries.

static

(Optional) Displays the total number of static entries.

ipv6

Displays the total number of IPv6 entries.

mpls

Displays the total number of MPLS entries.

Command Default

This command has no default settings.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(14)SX

Support for this command was introduced on the Supervisor Engine 720.

12.2(17a)SX

This command is supported on releases prior to Release 12.2(17a)SX only.

12.2(17b)SXA

On Cisco 7600 series routers that are configured with a Supervisor Engine 720, this command is replaced by the show mls netflow ip command.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

Usage Guidelines

The
static,
ipv6 and
mpls keywords are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

The
interface-number argument designates the module and port number. Valid values for
interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48. This definition also applies to the
modulenumber keyword and argument.

When you view the output, note that a colon (:) is used to separate the fields.

(Optional) Displays the entries that are downloaded on the
specified slot; see the “Usage Guidelines” section for valid values.

sourcehostname

(Optional) Displays the entries for a specific source
address.

sourceipx-network

(Optional) Displays the entries for a specific destination
network address.

detail

(Optional) Displays the detailed list of entries.

count

(Optional) Displays the total number of MLS entries.

Command Default

This command has no default settings.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was
extended to Release 12.2(17d)SXB.

12.2(33)SRA

This command was integrated into Cisco IOS Release
12.2(33)SRA.

Usage Guidelines

This command is not supported on Cisco 7600 series routers that are
configured with a Supervisor Engine 720 with a PFC2.

When you enter the
ipx-network value, the format is N.H.H.H.

When you enter the
destination-mac-address value, the format for
the 48-bit MAC address is H.H.H.

The
interface-number argument designates the
module and port number. Valid values for
interface-number depend on the specified
interface type and the chassis and module used. For example, if you specify a
Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module
installed in a 13-slot chassis, valid values for the module number are from 1
to 13 and valid values for the port number are from 1 to 48. These valid values
also apply when entering the
modulenumber keyword and argument.

show network-clocks

To display the current configured and active network clock sources, use theshownetwork-clocks command in privileged EXEC mode.

shownetwork-clocks

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.2(33)SRD1

This command was introduced to display BITS clock information for the 7600-ES+ITU-2TG and 7600-ES+ITU-4TG.

Usage Guidelines

On the Cisco MC3810, this command applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC. The Cisco MC3810 has a background task that verifies whether a valid clocking configuration exists every 120 seconds. If this task detects an error, you will be reminded every 120 seconds until the error is corrected. A clocking configuration error may be generated for various reasons. Using the
shownetwork-clocks command, you can display the clocking configuration status.

On the Cisco 7600 series routers, this command applies to the following:

In this display, inactive configuration is the new configuration that has been established. Active configuration is the run-time configuration. Should an error be made in the new configuration, the inactive and active configurations will be different. In the previous example, the clock priority configuration is valid, and the system is being clocked as indicated.

The following is another sample output from the
shownetwork-clocks command:

In this display, the new clocking configuration has an error for controller T1 1. This is indicated by checking differences between the last valid configuration (active) and the new proposed configuration (inactive). The error may result from hardware (the system controller board or MFT) unable to support this mode, or controller T1 1 is currently configured as “clock source internal.”

Since the active and inactive configurations are different, the system will periodically display the warning message about the wrong configuration.

The following is another sample output from the
shownetwork-clocks command for the 7600-ES+ITU-2TG or 7600-ES+ITU-4TG:

Command Modes

Command History

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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. The table below lists the output values for this command.

Table 12 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
clearaimelement-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
clearaimelement-numbercommand.

# 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
showpascaimringselement-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:

The table below describes the significant fields shown in the display.

Table 13 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-numbercommand 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:

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:

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:

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:

Command Modes

Command History

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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):

show pas i82543 interface

To display interface information that is specific to Fast Ethernet or Gigabit Ethernet port adapters with an Intel 82543 processor on Cisco 7200 series routers, use the
showpasi82543interfacecommand in privileged EXEC mode.

(Optional) Displays the contents of the receive address registers on the i82543 chip.

statistics

(Optional) Displays i82543-specific statistical information.

Command Modes

Privileged EXEC(#)

Command History

Release

Modification

12.2(20)S

This command was introduced on Cisco 7200 series routers.

12.1(20)E

This command was integrated into Cisco IOS Release 12.1(20)E on Cisco 7200 series routers.

12.0(27)S

This command was integrated into Cisco IOS Release 12.0(27)S on Cisco 7200 series routers.

12.3(7)T

This command was integrated into Cisco IOS Release 12.3(7)T on Cisco 7200 series routers.

Usage Guidelines

Use the
showpasi82543interface command with the
statistics keyword to determine what types of packets are being processed. Similar statistical information is displayed by the
showcontrollersfastethernet and
showcontrollersgigabitethernet commands.

Note

We recommend that the
multicast-table and
receive-address keywords for this command be used only under the supervision of a Cisco engineer because of the cryptic output.

Examples

The following sample output shows the contents of the multicast address table present on the i82543 processor.

Cyclic redundancy checksum (CRC) generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.

Symbol error

Number of symbol errors between reads.

Missed Packets

Indicates whether the software processes that handle the line protocol believe that the interface is usable (that is, whether keepalives are successful) or if it has been taken down by an administrator.

Single Collision

Number of times that a transmit operation encountered a single collision.

Excessive Coll

This counter is incremented after a transmit operation has encountered more than 16 collisions.

Multiple Coll

Number of times that a transmit operation encountered more than 1 collision, but less than 16 collisions.

Late Coll

Number of late collisions. A late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is Ethernet cable segments that are too long for the speed at which you are transmitting.

Collision

Number of messages transmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.

Defer

Defer indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.

Receive Length

Number of receive length error events. A receive length error occurs if an incoming packet passes the filter criteria but is either oversized or undersized. Packets less than 64 bytes are undersized. Packets over 1522 bytes are oversized if LongPacketEnable (LPE) is 0. If LPE is 1, a packet is considered oversized if it exceeds 16,384 bytes.

Sequence Error

Number of sequence error events.

XON RX

Number of XON packets received.

XON TX

Number of XON packets transmitted.

XOFF RX

Number of XOFF packets received.

XOFF TX

Number of XOFF packets transmitted.

FC RX Unsupport

Number of unsupported flow control frames received.

Packet RX

Number of received packets of the following lengths in bytes: 64, 127, 255, 511, 1023, 1522.

Good Packet RX

Number of received packets without errors.

Broadcast RX

Number of broadcast packets received.

Multicast RX

Number of multicast packets received.

Good Packet TX

Number of transmitted packets without errors.

Good Octets

Number of good (without errors) octets received (RX) or transmitted (TX).

RX No Buff

Number of times that frames were received when there were no available buffers in host memory to store those frames. The packet will be received if there is space in FIFO memory.

RX Undersize

Number of received frames that passed through address filtering and were less than the minimum size of 64 bytes (from destination address through CRC, inclusively), but that contained a valid CRC.

RX Fragment

Number of received frames that passed through address filtering and were less than the minimum size of 64 bytes (from destination address through CRC, inclusively), but that contained a bad CRC.

RX Oversize

Number of received frames that passed through address filtering and were greater than the maximum size.

RX Octets

Total number of octets received.

TX Octets

Total number of octets transmitted.

TX Packet

Number of transmitted packets.

RX Packet

Number of received packets.

TX Broadcast

Number of broadcast packets transmitted.

TX Multicast

Number of multicast packets transmitted.

Packet TX

Number of transmitted packets of the following lengths in bytes: 64, 127, 255, 511, 1023, 1522.

TX Underruns

Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.

TX No CRS

Number of successful packet transmissions in which Carrier Sense (CRS) input from the physical layer was not asserted within one slot time of start of transmission.

RX Error Count

Number of receive packets in which RX_ER was asserted by the physical layer.

RX DMA Underruns

Number of receive direct memory access (DMA) underruns observed by the DMA.

RX Carrier Ext

Number of packets received in which the carrier extension error was signalled across the gigabit medium independent interface (GMII) interface.

TCP Segmentation

Number of TCP segmentation offload transmissions to the hardware.

TCP Seg Failed

Number of TCP segmentation offload transmissions to the hardware that failed to transmit all data in the TCP segmentation context payloads.

Related Commands

Commands

Description

showcompress

Displays compression statistics.

showcontrollersfastethernet

Displays information about Fast Ethernet controllers.

showcontrollersgigabitethernet

Displays information about Gigabit Ethernet controllers.

showinterfaces

Displays information about interfaces.

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 showpasisacontrollerEXEC command.

showpasisacontroller

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.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Related Commands

Command

Description

showpasisainterface

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
showpasisainterfacecommand in privileged EXEC mode.

showpasisainterface

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.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

The table below describes the significant fields shown in the display.

Table 19 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.

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

showpasvamcontroller

Displays controller status information that is specific to the VPN accelerator module.

show pas y88e8k interface

To display the y88e8k Port Adaptor Information (pas) message details of a Gigabit Ethernet interface, use the showpasy88e8kinterface command in User EXEC or privileged EXEC mode.

Displays the size of the ring. This is based on the bandwidth of the interface or virtual circuit (VC) and is a power of two.

particle size

Displays the particle size on the receive and transmit paths, in bytes.

ring head

Displays the head of the ring.

tail

Displays the tail of the ring.

rxr

Displays the Rx ring pointer.

next_desc_addr

Displays next Rx buffer descriptor address.

buf_ctrl

Displays the buffer control.

buf_addr_lo

Displays the buffer address.

frame_sw

Displays the Frame status word.

rxr_shadow

Displays the Rx ring shadow.

data_start

Displays the start of data in the particle.

data_bytes

Displays the number of bytes consumed for data storage.

Related Commands

Command

Description

tx-ring-limit

Limits the number of packets that can be used on a transmission ring on the DSL WIC or interface.

show pci aim

To show the IDPROM contents for each compression Advanced Interface Module (AIM) daughter card in the Cisco 2600 router, use the showpciaimcommand in user EXEC or privileged EXEC mode.

showpciaim

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.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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:

Examples

In the following example, a second Cisco IOS process is enabled on a Cisco ASR 1004 router using stateful switchover (SSO). The output of the
showplatform command is provided before and after the SSO configuration to verify that the second Cisco IOS process is enabled and active.

The table below describes the significant fields shown in the display.

Table 22 show platform Field Descriptions

Field

Description

Slot

Chassis slot.

Type

Hardware type.

State

Online state of the hardware. One of the following values:

All Hardware

booting--Hardware is initializing and software is booting.

disabled--Hardware is not operational.

init--Hardware or Cisco IOS process is initializing.

ok--Hardware is operational.

shutdown--Hardware was administratively shut down using the no shutdown command.

unknown--Hardware is not operational; state is unknown.

RP or ESP

init, standby--Standby RP or ESP is operational but is not yet in a high availability (HA) state. An RP or ESP switchover is not yet possible.

ok, active--Active RP or ESP is operational.

ok, standby--Standby RP or ESP is operational. The standby RP or ESP is ready to become active in the event of a switchover.

SPA

admin down--SPA was disabled using the shutdown command.

inserted--SPA is being inserted.

missing--SPA was removed.

out of service--SPA is not operational.

retrieval error--An error occurred while retrieving the SPA state; state is unknown.

stopped--SPA was gracefully deactivated using the hw-module subslot stop command.

Fan or Power Supply

fan, fail--Fan is failing.

ps, fail--Power supply is failing.

Insert time (ago)

Amount of time (hh:mm:ss format) the hardware has been online.

CPLD Version

Complex programmable logic device version number.

Firmware Version

Firmware (ROMmon) version number.

Examples

The following sample output from the
showplatformcopprate-limitarp command displays the list of interfaces on which a rate limiter is active for ARP, along with the count of confirmed and exceeded packets for the rate limiter:

The table below describes the significant fields shown in the display.

Table 23 show platform copp rate-limit Field Descriptions

Field

Description

Rate Limiter Status

Indicates if a rate limiter has been enabled on the interface.

Rate

Indicates the configured rate in packets per second (pps) or bits per second (bps).

Max Observation Period

Indicates the configured observation period, in seconds, before the per-interface rate limiter is automatically turned off.

Per Interface Rate Limiter Information

Displays the list of interfaces on which the rate limiter is active. In this example:

GigabitEthernet5/1.1 is free from attack.

GigabitEthernet5/2.1 has an exceed count of 4, and has a rate limiter enabled. The observation period is 35 minutes, which indicates that currently the interface is free from attack and is being kept under observation. The interface will remain under observation for an additional 35 minutes. If it remains free from attack after that time, the rate limiter is automatically removed.

GigabitEthernet5/2.2 has an exceed count of 16 and has a rate limiter enabled. The observation period has been designated as Max. This indicates that the interface is still under attack and has not yet entered the observation time window.

The following sample from the
showplatformeeprom command displays CPU EEPROM information:

Related Commands

Turns on or off rate-limiting for an interface on the Cisco 7600 SIP-400.

platformcoppobservationperiod

Sets the observation period before automatically turning off the per-interface rate limiter on the Cisco 7600 SIP-400.

pseudowireclass

Specifies the name of a Layer 2 pseudowire class.

showmsfc

Displays MSFC information.

show platform acl software-switched

To display whether ACLs are enabled for software-switched WAN packets, use the showplatformaclsoftware-switchedcommand in privileged EXEC mode.

showplatformaclsoftware-switched

Syntax Description

This command has no arguments or keywords.

Command Default

This command has no default settings.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(50)SY

This command was introduced.

12.2(33)SXI2

This command was integrated into Cisco IOS Release 12.2(33)SXI2.

Usage Guidelines

By default, ACLs are not applied to packets that are software-switched between WAN cards and the route processor. To determine whether ACLs are enabled for software-switched ingress or egress WAN packets, use the showplatformaclsoftware-switchedcommand.

Examples

This example shows how to display whether ACLs are enabled for software-switched WAN packets:

The following table describes the significant fields shown in the
display.

Table 24 show platform condition Field Descriptions

Field

Description

Conditions

Condition of platform debug.

Direction

Direction of platform debug.

show platform diag

To display diagnostic and debug information about individual platform components, use the
showplatformdiag command in privileged EXEC mode.

showplatformdiag

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 2.2

This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Cisco IOS XE Release 3.9S

This command was integrated into Cisco IOS XE Release 3.9S.

Usage Guidelines

This command can be used to display the debug and diagnostic information about the Cisco ASR 1000 shared port adapter (SPA) Interface Processor (SIP), SPA, Cisco ASR 1000 Embedded Services Processor (ESP), Cisco ASR 1000 Route Processor (RP), and power supplies. This command also indicates the status of the field replaceable unit (FRU) components in any Cisco ASR 1000 Series Router.

Use the show platform diag command to display the debug and diagnostic information related to your Cisco 4400 Series Integrated Services Router (ISR), any connected Service Modules (SM-X) or Network Interface Modules (NIMs), power supply for front panel Gigabit Ethernet (FPGE) ports, Fan Trays and other components of your router.

Examples

The following is sample output from the show platform diag command. The Embedded Services Processor (ESP) is shown as F0 or F1. The RPs are shown as R0 or R1. The power supplies are shown as P0 and P1.

show platform dwdm alarm history

To display platform DWDM alarm history, use the
showplatformdwdmalarmhistorycommand in privileged EXEC mode.

showplatformdwdmalarmhistory
[ portindex ]

Syntax Description

portindex

Specifies the port index.

For a 7600-ES+ITU-2TG, the valid values for the port index are 1, 2.

For a 7600-ES+ITU-4TG, the valid values for the port index are 1, 2, 3, 4.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRD1

This command was introduced on the Cisco 7600 series routers for the 7600-ES+ITU-2TG and the 7600-ES+ITU-4TG line cards only.

Usage Guidelines

If the port index is not specified, the alarm history (last 32 alarms) for all ports on that line card whose interface transport mode is Optical Transport Network (OTN) is displayed. If a port index is specified, the alarm history (last 32 alarms) for that particular port is displayed, if the interface transport mode of that port is OTN. An alarm is logged in the alarm history only if the reporting for that alarm is enabled. If reporting for an alarm is disabled with the no g709 otu report command or the no g709 odu report command, then neither the alarm declaration nor clearing will be logged in the alarm history.

Examples

The following examples illustrate the command when interface TenGigabitEthernet 2/1 and interface TenGigabitEthernet 2/3 are configured with a transport-mode of OTN. Because the transport modes of interface TenGigabitEthernet 2/2 and interface TenGigabitEthernet 2/4 are not OTN, nothing is displayed for dwdm 2/2 and dwdm 2/4.

Related Commands

show platform hardware capacity

To display the capacities and utilizations for the hardware resources, use the
showplatformhardwarecapacitycommand in privileged EXEC mode.

showplatformhardwarecapacity [resource-type]

Syntax Description

resource-type

(Optional) Hardware resource type; see the “Usage Guidelines” section for the valid values.

Command Default

This command has no default settings.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(18)SXF

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXI

This command was integrated into Cisco IOS Release 12.2(33)SXI. Support was added for the
ibc and
rewrite-engine keywords.

Usage Guidelines

The valid values for
resource-type are as follows:

acl--Displays the capacities and utilizations for ACL/QoS TCAM resources.

cpu--Displays the capacities and utilizations for CPU resources.

eobc--Displays the capacities and utilizations for Ethernet out-of-band channel resources.

fabric--Displays the capacities and utilizations for Switch Fabric resources.

flash--Displays the capacities and utilizations for Flash/NVRAM resources.

forwarding--Displays the capacities and utilizations for Layer 2 and Layer 3 forwarding resources.

ibc--Displays the capacities and utilizations for interboard communication resources.

interface--Displays the capacities and utilizations for interface resources.

monitor--Displays the capacities and utilizations for SPAN resources.

multicast--Displays the capacities and utilizations for Layer 3 multicast resources.

netflow--Displays the capacities and utilizations for NetFlow resources.

pfc--Displays the capacities and utilizations for all the PFC resources including Layer 2 and Layer 3 forwarding, NetFlow, CPU rate limiters, and ACL/QoS TCAM resources.

power--Displays the capacities and utilizations for power resources.

qos--Displays the capacities and utilizations for QoS policer resources.

rate-limit--Displays the capacities and utilizations for CPU rate limiter resources.

rewrite-engine--Displays the packet drop and performance counters of the central rewrite engine on supervisors and line cards. For detailed information, see the
showplatformhardwarecapacityrewrite-enginecommand documentation.

system--Displays the capacities and utilizations for system resources.

vlan--Displays the capacities and utilizations for VLAN resources.

The
showplatformhardwarecapacitycpucommand displays the following information:

CPU utilization for the last 5 seconds (busy time and interrupt time), the percentage of the last 1-minute average busy time, and the percentage of the last 5-minute average busy time.

Processor memory total available bytes, used bytes, and percentage used.

I/O memory total available bytes, used bytes, and percentage used.

The
showplatformhardwarecapacityeobccommand displays the following information:

Transmit and receive rate

Packets received and packets sent

Dropped received packets and dropped transmitted packets

The
showplatformhardwarecapacityforwarding command displays the following information:

The total available entries, used entries, and used percentage for the MAC tables.

The total available entries, used entries, and used percentage for the FIB TCAM tables. The display is done per protocol base.

The total available entries, used entries, and used percentage for the adjacency tables. The display is done for each region in which the adjacency table is divided.

The created entries, failures, and resource usage percentage for the NetFlow TCAM and ICAM tables.

The total available entries and mask, used entries and mask, reserved entries and mask, and entries and mask used percentage for the ACL/QoS TCAM tables. The output displays the available, used, reserved, and used percentage of the labels. The output displays the resource of other hardware resources that are related to the ACL/QoS TCAMs (such as available, used, reserved, and used percentage of the LOU, ANDOR, and ORAND).

The available, used, reserved, and used percentage for the CPU rate limiters.

The
showplatformhardwarecapacityinterface command displays the following information:

Tx/Rx drops--Displays the sum of transmit and receive drop counters on each online module (aggregate for all ports) and provides the port number that has the highest drop count on the module.

Tx/Rx per port buffer size--Summarizes the port-buffer size on a per-module basis for modules where there is a consistent buffer size across the module.

The
showplatformhardwarecapacitymonitor command displays the following SPAN information:

Syntax Description

Displays the central rewrite engine current performance counter values or the performance rate.

slotnumber

(Optional) Displays the counter values for the module in the specified slot. If no slot is specified, the counters are displayed for each slot.

rate[sample_interval]

(Optional) Displays the drop rate or rewrite rate for a sample interval in msec between 1 and 1000. The default interval is 50 msec.

details

(Optional) Displays each individual drop counter with its name and register ID number. This keyword is not available with the
performancekeyword.

Command Default

If the sample interval is not specified, the default interval is 50 msec.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SXI

This command was introduced.

15.1(1)S

Support was added for Cisco 7600 routers. This command replaces the
show platform hardware central-rewritecommand.

Usage Guidelines

In the output of the
showplatformhardwarecapacityrewrite-engineperformance command output, a value of �N/A� means the slot/channel has a rewrite engine, but does not support performance counters.

Examples

The following sample output of the
show platform hardware capacity rewrite-engine dropcommand displays the packet drop counters of the central rewrite engine in all installed supervisors and line cards:

Examples

The following sample output of the
show platform hardware capacity rewrite-engine dropcommand displays the packet drop counters of the central rewrite engine in all installed supervisors and line cards:

The following sample output of the
show platform hardware capacity rewrite-engine dropcommand displays the performance counters of the central rewrite engine in all installed supervisors and line cards:

subslot/--Secondary slot number of the SIP where the Cisco ASR 1000 Series shared port adapter (SPA) is installed.

port/--Interface number on the SPA.

t1-number--T1 time slot in the T3 line. The value can be from 1 to 28.

channel-group--Number 0 to 23 of the DS0 link on the T1 channel.

Note

When a port on a Channelized T3 SPA is configured to be in unchannelized mode, only the slot/subslot/port/ arguments are used to specify the unchannelized T3 interface. The t1-number and channel-group arguments are not used.

subslot/--Secondary slot number of the SIP where the Cisco ASR 1000 Series shared port adapter (SPA) is installed.

port--Interface number on the SPA.

(Optional) .subint--Subinterface number (for those SPAs that support subinterface configuration).

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Diagnostic (diag)

Command History

Release

Modification

Cisco IOS XE Release 2.1

This command was introduced on the Cisco ASR 1000 Series Routers.

Usage Guidelines

This command displays platform-specific information and configuration information related to a specific interface.

The table below lists the interface types.

Table 27 Interface Types

Interface Type

Description

async

Asynchronous interface

auto-template

Auto-template interface

bvi

Bridge group virtual interface

ctunnel

Connectionless Network Service (CLNS) tunnel (CTunnel) interface

container

Container interface

dialer

Dialer interface

esconphy

ESCON interface

fastethernet

Fast Ethernet IEEE 802.3 interface

filter

Filter interface

filtergroup

Filter group interface

gigabitethernet

Gigabit Ethernet IEEE 802.3 interface.

group-async

Group asynchronous interface

lex

LAN extender (LEX) interface

longreachethernet

Long Reach Ethernet interface

loopback

Loopback interface

multilink

Multilink group interface

null

Null interface

pos

Packet over SONET (POS) interface

port-channel

Ethernet channel of interfaces

portgroup

Port group interface

pos-channel

POS channel of interfaces

sbc

Session border controller interface

sysclock

Telecom bus clock controller interface

serial

Serial interface

tunnel

Tunnel interface

vif

Pragmatic General Multicast (PGM) host interface

virtual-ppp

Virtual point-to-point (PPP) interface

virtual-template

Virtual template interface

virtual-tokenring

Virtual Token Ring interface

vlan

Catalyst VLAN interface

fcpa

Fiber Channel interface

multiservice

Multiservice interface

voabyapssin

Variable optical attenuator (VOA) bypass-in interface

voabyapssout

VOA bypass-out interface

voafilterin

VOA filter-in interface

voafilterout

VOA filter-out interface

voain

VOA-in interface

voaout

VOA-out interface

Examples

Packets can be classified based on the IP precedence, IPv6 traffic class, MPLS experimental bits, or VLAN TOS bits. In the following example, incoming packets with IP precedence 6 or 7, IPv6 packets with traffic class 46, and MPLS packets with experimental bits 6 or 7 are classified as high priority packets:

Syntax Description

(Optional) Information about the particular VRF instance. The range is from 0 to 4294967295. If no VRF ID is specified, information about the global VRF, which is the prefix in global routing table, is displayed.

exact

(Optional) Find and displays the exact match of the IPV4 prefix.

brief

(Optional) Displays a summary of prefix information.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)XNB

This command was introduced on the Cisco ASR 1000 Series Routers.

Cisco IOS XE Release 3.4S

This command was integrated into Cisco IOS Release XE 3.4S. Support for IP Fast Reroute (IP FRR) was added.

Examples

The following is sample output from theshowplatformhardwareqfpactivefeaturecef-mplsprefixip command:

Syntax Description

Displays all the OCE chains that are used for handling the
incoming MPLS packets with a particular label.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.8S

This command was introduced on the Cisco ASR 1000 Series
Aggregation Services Routers.

Examples

The following is sample output from the show platform hardware qfp
active feature cef-mpls prefix mpls mpls-label exact command displaying all the
OCE chains used for handling incoming MPLS packets with a particular label:

show platform hardware qfp active feature multicast

To display the complete Output Chain Element (OCE) chains that are
connected by each leaf node in the multicast replication tree for a particular
output path in the Cisco QuantumFlow Processor (QFP) active feature on the
Cisco ASR 1000 Series Aggregation Services Routers, use the show platform
hardware qfp active feature multicast command in the privileged EXEC mode.

Displays the entire OCE that is connected by each leaf node
in the multicast replication tree for a particular output path.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 3.8S

This command was introduced on the Cisco ASR 1000 Series
Aggregation Services Routers.

Examples

The following is sample output from the show platform hardware qfp
active feature multicast v4mcast command displaying all the OCE chains used for
forwarding traffic to a particular IPv4 multicast address:

The following is sample output from the show platform hardware qfp
active feature multicast v6mcast command displaying all the OCE chains used for
forwarding traffic to a particular IPv6 multicast address:

show platform hardware qfp active infrastructure punt

To display the hardware and infrastructure information for punt
statistics and configuration in an active instance of the Cisco Quantum Flow
Processor (QFP), use the show platform hardware qfp active infrastructure
punt
command in privileged EXEC mode.

show platform hardware qfp active interface if-name statistics

To display the statistics of packet drops for each interface in the Packet Processor Engine (PPE), use the
show platform hardware qfp active interface if-name
statistics command in privileged EXEC mode.

Command Default

Command Modes

Command History

Usage Guidelines

You can use this command for troubleshooting the problems on an interface in a PPE by analyzing the statistics of packet drops.

Examples

The following sample output from the
show platform hardware qfp active interface if-name statistics command displays the statistics of packet drops on the Gigabit Ethernet interface 0/0/0.781 interface:

pv4uRpfStrictFailed - Specifies the number and bytes of packets that are dropped with this drop cause.

Ipv6uRpfStrictFailed - Specifies the number and bytes of packets that are dropped with this drop cause

Packets

Number of packets that are transmitted.

IPv4uRpfStrictFailed received 5 packets.

IPv6uRpfStrictFailed received 5 packets.

Octets

Total number of bytes of the packets that are received.

IPv4uRpfStrictFailed received 590 bytes of packets.

IPv6uRpfStrictFailed received 590 bytes of packets.

Output Drop Stats

Specifies the drop cause and the number of outgoing packets that are dropped.

Interface

Name of the interface.

Rx Pkts

Number of packets received on an interface.

Tx Pkts

Number of packets transmitted on an interface.

Related Commands

Command

Description

show platform hardware qfp active statistics drop

Displays the statistics of packet drops on all the interfaces in a PPE.

show platform hardware qfp statistics drop

To display the statistics of all the dropped packets on the Embedded Services Processor (ESP), use the
show platform
hardwareqfp
active statistics drop command in privileged EXEC mode.

show platform hardware qfp
{ active | standby }
statistics drop

Syntax Description

active

Active forwarding processor.

standby

Standby forwarding processor .

Command Default

No default behavior or values.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 2.0

This command was introduced.

Cisco IOS XE Release 3.5

This command was modified for Cisco ASR 1000 Series Routers. A new drop type, PPPoECAC, was added to theshow platform hardware qfp active statistics drop command.

Usage Guidelines

You can use this command for troubleshooting the problems on all the interfaces in a PPE by analyzing the statistics of packet drops.

You can use this command for troubleshooting the problems on all the interfaces in a packet processing engine (PPE) by analyzing the statistics of packet drops.

To improve the CPU utilization and memory of the Route Processor (RP) on Cisco ASR 1000 Series Router, the SRSM hardware feature has been implemented. When Call Admission Control (CAC) is enabled and the CAC threshold level is reached, the PPPoE packets are punted on the Embedded Service Processor (ESP) instead of being sent to the RP. Managing the PPPoE packets at the ESP level helps in controlling and minimizing RP CPU and memory utilization. A new drop type, PPPoECAC, is added to theshow platform hardware qfp active statistics drop command which indicates the number of PPPoE Active Discovery Initiation (PADI) and PPPoE Active Discovery Request (PADR) packets rejected by the hardware due to call admission control.

Note

The
show call admission statistics command shows how many packets were dropped by the RP and the
show platform hardware qfp active statistics drop command indicates how many packets were dropped by the ESP. A small number of packets are still dropped by the RP because it takes time for the drop message to reach the ESP. The actual number of packets dropped by SRSM is the total number of packets dropped by
show call admission statistics and
show platform hardware qfp active statistics drop commands.

Examples

The following sample output from the
show platform hardware
qfp
active
statistics
drop command displays the statistics of packet drops on all the interfaces in a PPPoE:

(Optional) Specifies the statistics of transmitted and received packets.

drop_summary

(Optional) Specifies the drop status summary report.

subinterface

(Optional) Specifies the subinterface and the drop statistics.

clear_drop

(Optional) Clears the drop statistics after reading.

detail

(Optional) Shows drop cause IDs.

dsp

Specifies digital signal processor (DSP) statistics.

client

Specifies DSP client statistics.

resource

Specifies DSP client resource statistics.

dsp-resource-id

Combinet Packet Protocol (CPP) DSP resource ID.

global

Specifies DSP global statistics.

clear

Clears statistics after reading.

stream

Specifies DSP stream statistics.

stream-id

Stream ID.

if-namename

Specifies the name of an interface, interface type, and port number of the selected interface.

if-handlehandle

Specifies the quantum flow processor (QFP) interface handle number.

info

(Optional) Specifies interface information.

path

(Optional) Specifies path information.

atm

Specifies information and statistics for the ATM interface.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 2.1

This command was introduced.

Cisco IOS XE Release 2.5

This command was modified. The
cpp
keyword was changed to
qfp.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

Cisco IOS XE Release 3.8S

This command was modified. The
path keyword was added.

Usage Guidelines

The
showplatformhardwareqfpinterface command displays information about the relationship between one interface and another in the target flow processor. In the command output, the main interface is identified if the interface is a subinterface; the group interface is identified if the interface is a member of a group; and the interfaces that are members of the group are identified if the interface is a group, bundle, or multipoint interface.

Examples

The following sample output shows information about the relationship between one interface and the other on the target flow processor:

Command Modes

Privileged EXEC (#)

Diagnostic (diag)

Command History

Release

Modification

Cisco IOS XE Release 2.1

This command was introduced.

15.0(1)S

This command was modified. The minimum bandwidth and the priority mode that cannot be configured in Strict Priority mode are not displayed in the output. The HP policer BW field was added to the output.

Examples

The following sample output from the show platform hardware slot 0 eobc interface primary status
command displays EOBC interface status for a SIP in chassis slot 0. This command provides the status of the EOBC in the indicated slot.

The table below describes the significant fields shown in the display.

Table 40 show platform hardware slot 0 fan status Field Descriptions

Field

Description

Fan speed

Speed at which the fans are spinning as a percentage of their maximum speed.

Fan 0, 1, 2

Specifies whether a fan is encountering a fault condition. “Normal” or “Fail.”

The following sample output from the show
platform hardware slot 0 plim qos input bandwidth command displays the ingress arbiter settings for all PLIM buffers that are in use for a SIP in chassis slot 0:

Bandwidth assigned for processing high-priority traffic on this interface in Kbps.

The following sample output from the show
platform hardware slot 0 plim statistics command displays PLIM statistics for a SIP in chassis slot 0. Interprocess communication (IPC) packets are internal control packets. The first set of RX and TX packet counts include both user packets and IPC packets. In this example, the RX/TX and RX IPC/TX IPC packet counts are the same because only IPC packets are being passed (no user packets).

Packets (user data and IPC data) received by the PLIM from the indicated SPA.

TX Pkts

Packets (user data and IPC data) transmitted from the PLIM to the indicated SPA.

RX IPC Pkts

IPC packets received by the PLIM from the indicated SPA.

TX IPC Pkts

IPC packets transmitted from the PLIM to the indicated SPA.

The following is sample output from the show platform hardware slot f0 serdes statistics command for Cisco ASR1000-ESP20 and later versions of the ESP. This output displays the byte counters and packet counters associated with the Enhanced SerDes Interconnect (ESI) links for the ESP. The output includes information about drop counters and the number of link-level flow control messages. Information is displayed from the standpoint of the card (in this example, ESP0), where the command is run. An ESP displays information from all the cards with active ESI links connected to it. A SIP or an RP displays statistics from each ESP.

Number of times the chassis software on the SIP made a request to the chassis software on the RP to allow a SPA to come online.

SPA OIR responses

Number of times the chassis software on the RP sent a response to an OIR request to the chassis software on the SIP.

SPA insertions

Number of SPA insertions since the last boot. The number is zero for SPAs that were in the chassis when the chassis booted.

SPA removals

Number of SPA removals since the last boot.

SPA driver starts

Number of times the SPA driver started.

SPA driver stops

Number of times the SPA driver stopped.

SPA driver deaths

Number of time the SPA driver reloaded.

The following sample output from the show platform hardware slot P0 mcu status displays the MCU hardware status and power supply in the slot:

If you use the
show platform hardware slotsipmcu status command or the
show platform
hardware slotsipfanstatus command on the Cisco ASR 1000 Series Router, we recommend that you use the value “Px” rather than “0” or other numeric values to specify the power supply slot. This command displays the MCU hardware status or fan status and references the power supply in the slot.

The table below describes the significant fields shown in the display.

Table 45 show platform hardware slot mcu status Field Descriptions

Field

Description

Model ID

Model ID of the card slot.

12V

Power supply in the slot in voltage.

Temp

Chassis temperature.

Input V

Voltage input for power supply.

Fan speed

Speed at which the fans are spinning as a percentage of their maximum speed.

Related Commands

Command

Description

show platform hardware interface

Displays information about an interface.

show platform hardware port

Displays information about an interface port on an SPA.

show platform hardware subslot

Displays information about an SPA.

show platform hardware throughput level

To display the current maximum throughput level for a virtual router, use the show platform hardware throughput level command in Privileged EXEC mode.

showplatformhardwarethroughputlevel

Command Modes

Privileged EXEC

Command History

Release

Modification

Cisco IOS XE 3.9S

This command was introduced on the Cisco CSR 1000V Cloud Services Router.

Usage Guidelines

The maximum throughput level is determined by the installed license. Depending on the configuration and installed license, you can change the maximum throughput level. See the platform hardware throughput level command for more information.

Examples

The following example displays the maximum throughput level on the router:

Router# show platform hardware throughput level
The current throughput level is 50000 kb/s

Command Modes

Privileged EXEC (#) Diagnostic (diag)

Command History

Release

Modification

Cisco IOS XE Release 2.1

This command was introduced on the Cisco ASR 1000 Series Routers.

15.0(1)S

This command was modified. The minimum bandwidth and the proirity mode that cannot be configured in Strict Priority mode are not displayed in the output. The HP policer BW field was added to the output.

Examples

The following example displays ingress arbiter settings for all PLIM buffers that are in use for a SPA in chassis slot 1:

Bandwidth assigned for processing high priority traffic on this interface in kb/s.

The following example displays PLIM statistics for a SPA in chassis slot 1. Interprocess communication (IPC) packets are internal control packets. The first set of RX and TX packet counts includes both user packets and IPC packets. In this example, the RX/TX and RX IPC/TX IPC packet counts are the same because no user packets are being passed, only IPC packets.

The table below describes the fields shown in the
showplatformisgmemorycommand display.

Table 48 show platform isg memory Field Descriptions

Field

Description

Allocator-Name

Name of the memory allocating process.

In-use

Indicates the current memory usage.

Allocated

Total memory allocated by the process.

Count

Number of allocated memory blocks.

show platform mgf

To show the details of the multi-gigabit fabric, use the
showplatformmgf command in privileged EXEC mode.

showplatformmgf
[ module | statisticscpu ]

Syntax Description

module

Shows details of the modules registered to the backplane switch manager (BPSM).

statistics

Displays the multi-gigabit fabric’s packet statistics.

cpu

Displays the multi-gigabit fabric’s cpu port statistics.

Command Default

None

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

15.0(1)M

This command was introduced for the Cisco 3900 Series, 2900 Series, and 1900 Series Integrated Services Routers (ISRs).

Usage Guidelines

To show the details of the multi-gigabit fabric, use the
showplatformmgf command in privileged EXEC mode. Or, enter the
showplatformmgf command and press Enter to display VLAN and slot assignments on the router. An asterisk next to the slot indicates that the vlan is the slot's default VLAN. The following example displays output from a Cisco 3945 ISR.

Note

Before Cisco IOS 15.1(3)T release, the Cisco Services Ready Engine (SRE) Service Module was managed by the platform backplane code. Therefore, when you entered the
show platform mgf
command, the Cisco SRE Service Module was displayed in the command output. But with Cisco IOS 15.1(3)T release, because the Cisco SRE Service Module is in the switchport managed module, it is no longer displayed in the
show platform mgf command output.

Related Commands

Command

Description

showplatform

To display platform information, use the show platform command in privileged EXEC mode.

show platform slot r0 pcie status

To display information about all Peripheral Component Interconnect (PCI) buses on the Route Processor (RP) slot on the Cisco ASR 1000 Series Aggregation Services Router and devices connected to the PCI buses, use the
show platform slot r0 pcie status command in user EXEC or privileged EXEC mode.

show platform slot r0 pcie status

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)
User EXEC (>)

Command History

Release

Modification

Cisco IOS XE Release 3.6

This command was introduced.

Examples

The following sample output from the
show platform slot r0 pcie status command displays information about all PCI buses on the RP slot on the Cisco ASR 1000 Series Aggregation Services Router and the devices connected to them:

Command Modes

Command History

Usage Guidelines

If no slot is specified, the command returns mounted file systems for the active RP.

This command allows you to ascertain the presence or absence of specific system mounts. For example, this command might be used to determine /tmp-related mounts, which are used to create many run-time directories and files.

Users may be requested to execute this command to collect information about the underlying configuration of the platform software.

The RP output can differ depending on how the router was booted, and whether there are USB devices inserted.

The SIP and ESP output can differ depending on whether the chassis is a dual or single RP.

Examples

The following example displays mounted file systems for the active RP: