Table Of Contents
show interfaces vlan mapping
show interfaces wlan-controller
show ip interface
show ipc
show ipc hog-info
show ipv6 ospf interface
show l2protocol-tunnel
show l3-mgr
show l3vpn encapsulation ip
show lacp
show link state group
show mac-address-table dynamic
show mls asic
show mls ip
show mls ipx
show mobility
show module
show msfc
show mvr
show mvr interface
show mvr members
show mvr receiver ports
show mvr source ports
show network-clocks
show pagp
show pas caim
show pas eswitch address
show pas i82543 interface
show pas isa controller
show pas isa interface
show pas vam controller
show pas vam interface
show pas y88e8k interface
show pci aim
show platform
show platform acl software-switched
show platform atom disp-tbl backup
show platform atom disp-tbl local-vc-label
show platform atom imp-tbl backup
show platform atom imp-tbl remote-vc-label
show platform atom tbl-summary
show platform diag
show platform discover-devices
show platform dwdm alarm history
show platform hardware capacity
show platform hardware interface
show platform hardware network-clocks
show platform hardware slot
show platform hardware qfp active feature cef-mpls prefix mpls
show platform hardware qfp active feature cef-mpls prefix ip
show platform hardware qfp active feature cef-mpls prefix ipv6
show platform hardware qfp active feature cef-mpls prefix mpls
show platform hardware qfp active statistics drop
show platform hardware qfp interface
show platform hardware slot
show platform hardware subslot
show platform hardware transceiver
show platform isg memory
show platform mgf
show platform software memory
show platform software mount
show platform software process list
show platform software status control-processor
show platform software tech-support
show platform time-source
show plim fpga
show policy-map interface
show power
show power inline
show ptp clock dataset
show ptp clock dataset parent
show ptp clock dataset time-properties
show ptp clock running
show ptp port dataset foreign-master
show ptp port dataset port
show pxf cpu access-lists
show pxf cpu iedge
show pxf cpu qos
show pxf dma
show pxf max-logical-interfaces
show qm-sp port-data
show rbscp
show redundancy
show redundancy (HSA redundancy)
show redundancy interlink
show rpc
show scp
show interfaces vlan mapping
To display the status of a virtual local area network (VLAN) mapping on a port, use the show interfaces vlan mapping command in user EXEC or privileged EXEC mode.
show interfaces interface interface-number vlan mapping
Syntax Description
interface
|
Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
|
interface-number
|
Module and port number; see the "Usage Guidelines" section for valid values.
|
Defaults
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:
Router# show interfaces gigabitethernet 5/2 vlan mapping
Original VLAN Translated VLAN
------------- ---------------
Related Commands
Command
|
Description
|
show vlan mapping
|
Registers a mapping of an 802.1Q VLAN to an ISL VLAN.
|
switchport vlan mapping enable
|
Enables VLAN mapping per switch port.
|
show interfaces wlan-controller
To show the Cisco Wireless Local Area Network (WLAN) controller network module interfaces on the router, use the show interfaces wlan-controller command in privileged EXEC mode.
show interfaces wlan-controller slot/unit
Syntax Description
slot/unit
|
Specifies the router slot and unit numbers for the WLAN controller network module.
|
Defaults
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.4(2)XA1
|
This command was introduced on the router software.
|
12.4(6)T
|
This command was integrated into Cisco IOS Release 12.4(6)T.
|
Examples
The following example shows how to read the hardware information about the interface WLAN controller in the router:
Router# show interfaces wlan-controller 1/0
wlan-controller1/0 is up, line protocol is up
Hardware is I82559FE, address is 0005.9a3d.7450 (bia 0005.9a3d.7450)
Internet address is 30.0.0.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:05, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2400779 packets input, 143127299 bytes
Received 2349587 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
468232 packets output, 106333102 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 1 no carrier
0 output buffer failures, 0 output buffers swapped out
show ip interface
To display the usability status of interfaces configured for IP, use the show ip interface command in privileged EXEC mode.
show ip interface [type number] [brief]
Syntax Description
type
|
(Optional) Interface type.
|
number
|
(Optional) Interface number.
|
brief
|
(Optional) Displays a summary of the usability status information for each interface.
|
Command Default
The full usability status is displayed for all interfaces configured for IP.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(3)T
|
The command output was modified to show the status of the ip wccp redirect out and ip wccp redirect exclude add in commands.
|
12.2(14)S
|
The command output was modified to display the status of NetFlow on a subinterface.
|
12.2(15)T
|
The command output was modified to display the status of NetFlow on a subinterface.
|
12.3(6)
|
The command output was modified to identify the downstream VPN routing and forwarding (VRF) instance in the output.
|
12.3(14)YM2
|
The command output was modified to show the usability status of interfaces configured for Multiprocessor Forwarding (MPF) and implemented on the Cisco 7301 and Cisco 7206VXR routers.
|
12.2(14)SX
|
This command was implemented on the Supervisor Engine 720.
|
12.2(17d)SXB
|
This command was integrated into Cisco IOS 12.2(17d)SXB on the Supervisor Engine 2, and the command output was changed to include NDE for hardware flow status.
|
12.4(4)T
|
This command was integrated into Cisco IOS Release 12.4(4)T.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
The command output was modified to display information about the Unicast Reverse Path Forwarding (RPF) notification feature.
|
12.4(20)T
|
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.
|
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 show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
You can use the show ip interface brief command to display a summary of the router interfaces. This command displays the IP address, the interface status, and other information.
The show ip interface brief 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).
Router# show running-config interface gigabitethernet 0/3
interface GigabitEthernet0/3
ip address 10.1.1.1 255.255.0.0
ip policy route-map PBRNAME
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.
Router# show ip interface gigabitethernet 0/3
GigabitEthernet0/3 is up, line protocol is up
Internet address is 10.1.1.1/16
Broadcast address is 255.255.255.255
Address determined by setup command
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP CEF switching is enabled
IP Feature Fast switching turbo vector
IP VPN Flow CEF switching turbo vector
IP multicast fast switching is enabled
IP multicast distributed fast switching is disabled
IP route-cache flags are Fast, CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Policy routing is enabled, using route map PBR
Network address translation is disabled
BGP Policy Mapping is disabled
IP Multi-Processor Forwarding is enabled
IP Input features, "PBR",
are not supported by MPF and are IGNORED
IP Output features, "NetFlow",
are not supported by MPF and are IGNORED
The following example identifies a downstream VRF instance. In the example, "Downstream VPN Routing/Forwarding "D"" identifies the downstream VRF instance.
Router# show ip interface virtual-access 3
Virtual-Access3 is up, line protocol is up
Interface is unnumbered. Using address of Loopback2 (10.0.0.8)
Broadcast address is 255.255.255.255
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is enabled
IP Flow switching is disabled
IP CEF switching is enabled
IP Feature Fast switching turbo vector
IP VPN CEF switching turbo vector
VPN Routing/Forwarding "U"
Downstream VPN Routing/Forwarding "D"
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
IP route-cache flags are Fast, CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
The following example shows the information displayed when Unicast RPF drop-rate notification is configured:
Router# show ip interface ethernet 2/3
Ethernet2/3 is up, line protocol is up
Internet address is 10.0.0.4/16
Broadcast address is 255.255.255.255
Address determined by non-volatile memory
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP Flow switching is disabled
IP CEF switching is disabled
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
IP route-cache flags are No CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
Unicast RPF Information
IP verify source reachable-via RX, allow default
0 suppressed verification drops
The following example shows how to display the usability status for a specific VLAN:
Router# show ip interface vlan 1
Vlan1 is up, line protocol is up
Internet address is 10.0.0.4/24
Broadcast address is 255.255.255.255
Address determined by non-volatile memory
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Local Proxy ARP is disabled
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP CEF switching is enabled
IP Fast switching turbo vector
IP Normal CEF switching turbo vector
IP multicast fast switching is enabled
IP multicast distributed fast switching is disabled
IP route-cache flags are Fast, CEF
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
BGP Policy Mapping is disabled
Sampled Netflow is disabled
IP multicast multilayer switching is disabled
Netflow Data Export (hardware) is enabled
Table 1 describes the significant fields shown in the display.
Table 1 show ip interface Field Descriptions
Field
|
Description
|
Virtual-Access3 is up
|
Shows whether the interface hardware is usable (up). For an interface to be usable, both the interface hardware and line protocol must be up.
|
Broadcast address is
|
Broadcast address.
|
Peer address is
|
Peer address.
|
MTU is
|
MTU value set on the interface, in bytes.
|
Helper address
|
Helper address, if one is set.
|
Directed broadcast forwarding
|
Shows whether directed broadcast forwarding is enabled.
|
Outgoing access list
|
Shows whether the interface has an outgoing access list set.
|
Inbound access list
|
Shows whether the interface has an incoming access list set.
|
Proxy ARP
|
Shows whether Proxy Address Resolution Protocol (ARP) is enabled for the interface.
|
Security level
|
IP Security Option (IPSO) security level set for this interface.
|
Split horizon
|
Shows whether split horizon is enabled.
|
ICMP redirects
|
Shows whether redirect messages will be sent on this interface.
|
ICMP unreachables
|
Shows whether unreachable messages will be sent on this interface.
|
ICMP mask replies
|
Shows whether mask replies will be sent on this interface.
|
IP fast switching
|
Shows whether fast switching is enabled for this interface. It is generally enabled on serial interfaces, such as this one.
|
IP Flow switching
|
Shows whether Flow switching is enabled for this interface.
|
IP CEF switching
|
Shows whether Cisco Express Forwarding switching is enabled for the interface.
|
Downstream VPN Routing/Forwarding "D"
|
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 ip flow ingress command. Shows "Flow" to specify that NetFlow is enabled on a main interface using the ip route-cache flow 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 following example shows how to display a summary of the usability status information for each interface:
Router# show ip interface brief
Interface IP-Address OK? Method Status Protocol
Ethernet0 10.108.00.5 YES NVRAM up up
Ethernet1 unassigned YES unset administratively down down
Loopback0 10.108.200.5 YES NVRAM up up
Serial0 10.108.100.5 YES NVRAM up up
Serial1 10.108.40.5 YES NVRAM up up
Serial2 10.108.100.5 YES manual up up
Serial3 unassigned YES unset administratively down down
Table 2 describes the significant fields shown in the display.
Table 2 show ip interface brief Field Descriptions
Field
|
Description
|
Interface
|
Type of interface.
|
IP-Address
|
IP address assigned to the interface.
|
OK?
|
"Yes" means that the IP Address is valid. "No" means that the IP Address is not valid.
|
Method
|
The Method field has the following possible values:
• RARP or SLARP—Reverse Address Resolution Protocol (RARP) or Serial Line Address Resolution Protocol (SLARP) request.
• BOOTP—Bootstrap protocol.
• TFTP—Configuration file obtained from the TFTP server.
• manual—Manually changed by the command-line interface.
• NVRAM—Configuration file in NVRAM.
• IPCP—ip address negotiated command.
• DHCP—ip address dhcp command.
• unassigned—No IP address.
• unset—Unset.
• other—Unknown.
|
Status
|
Shows the status of the interface. Valid values and their meanings are:
• up—Interface is up.
• down—Interface is down.
• administratively down—Interface is administratively down.
|
Protocol
|
Shows the operational status of the routing protocol on this interface.
|
Related Commands
Command
|
Description
|
ip address
|
Sets a primary or secondary IP address for an interface.
|
ip vrf autoclassify
|
Enables VRF autoclassify on a source interface.
|
match ip source
|
Specifies a source IP address to match to required route maps that have been set up based on VRF connected routes.
|
route-map
|
Defines the conditions for redistributing routes from one routing protocol into another or to enable policy routing.
|
set vrf
|
Enables VPN VRF selection within a route map for policy-based routing VRF selection.
|
show ip arp
|
Displays the ARP cache, in which SLIP addresses appear as permanent ARP table entries.
|
show route-map
|
Displays static and dynamic route maps.
|
show ipc
To display interprocess communication (IPC) statistics, use the show ipc command in privileged EXEC mode.
show ipc {nodes | ports [open] | queue | status [cumulative] | zones}
Syntax Description
nodes
|
Displays participating nodes.
|
ports
|
Displays local and registered IPC ports.
|
open
|
(Optional) Displays local IPC ports that have been opened by the current seat (node).
|
queue
|
Displays information about the IPC retransmission queue and the IPC message queue.
|
status
|
Displays the status of the local IPC server.
|
cumulative
|
(Optional) Displays cumulative totals for the status counters of the local IPC server since the router was rebooted.
|
zones
|
Displays information about the IPC zones and seats.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(12c)EW
|
This command was introduced.
|
12.2(15)T
|
The cumulative keyword was added.
|
12.3(7)T
|
The zones keyword was added.
|
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.
Ports
IPC communication endpoints (ports) receive and queue received IPC messages.
Queue
Use the queue keyword to display information about the IPC retransmission queue and the IPC message queue.
Status
Use the status keyword to display the IPC statistics that have been generated since a clear ipc statistics command was entered. The show ipc status command with the cumulative keyword displays the IPC statistics that have been gathered since the router was rebooted, regardless of how many times the statistics have been cleared.
Zones
The IPC zone manager allows more than one group of IPC seats to exist to enable direct communication between line cards and the route processor. Use the zones keyword to display the IPC zone and seat information.
Examples
The following is sample output from the show ipc command with the nodes keyword displaying the participating seats (nodes):
There are 6 nodes in this IPC realm.
0.10000 Local IPC Master 0 0
0.1060000 RSP-CY RSP IPC card slot 6 9 79
0.1050000 RSP-CY RSP IPC card slot 5 21 22
0.1080000 RSP-CY RSP IPC card slot 8 21 22
1.10000 Local IPC Master: -Zone#1 0 0
2.10000 Local IPC Master: -Zone#2
Table 3 describes the significant fields shown in the display.
Table 3 show ipc nodes Field Descriptions
Field
|
Description
|
ID
|
Port ID, which consists of a zone ID followed by the seat ID.
|
Type
|
Type of seat (node).
|
Name
|
Seat name.
|
Last Sent
|
Sequence number of the message that was last sent.
|
Last Heard
|
Sequence number of the in-sequence message that was last heard.
|
The following is sample output from the show ipc command with the ports keyword displaying the local and registered IPC ports:
There are 11 ports defined.
Port ID Type Name (current/peak/total)
1.10000.1 unicast IPC Master:Zone
1.10000.2 unicast IPC Master:Echo
1.10000.3 unicast IPC Master:Control
1.10000.4 unicast Remote TTY Server Port
1.10000.5 unicast GALIOS RF :Active
index = 0 seat_id = 0x2020000 last sent = 0 heard = 1635 0/1/1635
1.10000.6 unicast GALIOS RED:Active
index = 0 seat_id = 0x2020000 last sent = 0 heard = 2 0/1/2
2.2020000.3 unicast GALIOS IPC:Card 2:Control
2.2020000.4 unicast GALIOS RFS :Standby
2.2020000.5 unicast Slave: Remote TTY Client Port
2.2020000.6 unicast GALIOS RF :Standby
2.2020000.7 unicast GALIOS RED:Standby
RPC packets: current/peak/total 0/1/17
Table 4 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 show ipc command with the queue keyword displaying information about the IPC retransmission queue and the IPC message queue:
There are 0 IPC messages waiting for acknowledgement in the transmit queue.
There are 0 IPC messages waiting for a response.
There are 0 IPC messages waiting for additional fragments.
There are 0 IPC messages currently on the IPC inboundQ.
There are 0 messages currently in use by the system.
The following is sample output from the show ipc command with the status keyword displaying information about the local IPC server:
Time last IPC stat cleared : never
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 189 70
Total Protocol Control Frames 70 44
Total via Unreliable Connection-Less Service 145 0
Total via Unreliable Sequenced Connection-Less Svc 0 0
Total via Reliable Connection-Oriented Service 44 70
Total Acknowledgements 70 44
Total Negative Acknowledgements 0 0
Total via Local Driver 0 0
Total via Platform Driver 0 70
Total Frames Dropped by Platform Drivers 0 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Out-of-Sequence Frame 0 Tx Test Drop 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
Table 5 describes the significant fields shown in the display.
Table 5 show ipc status Field Descriptions
Field
|
Description
|
Time last IPC stat cleared
|
Displays the time, in dd:hh:mm (or never), since the IPC statistics were last cleared.
|
This processor is
|
Shows whether the processor is the IPC master or an IPC slave.
|
IPC Message Headers Cached
|
Number of message headers available in the IPC message cache.
|
Rx Side
|
Information about IPC messages received.
|
Tx Side
|
Information about IPC messages sent.
|
Service Usage
|
Number of IPC messages received or sent via connectionless or connection-oriented protocols.
|
IPC Protocol Version 0
|
Number of acknowledgements and negative acknowledgements received or sent by the system.
|
Device Drivers
|
Number of IPC messages received or sent using the underlying device drivers.
|
Reliable Tx Statistics
|
Number of IPC messages that were retransmitted or that timed out on retransmission using a reliable connection-oriented protocol.
|
Rx Errors
|
Number of IPC messages received that displayed various internal frame or delivery errors.
|
Tx Errors
|
Number of IPC messages sent that displayed various transmission errors.
|
Buffer Errors
|
Number of message allocation failures from the IPC message cache, IPC emergency message cache, IPC frame allocation cache, and IPC frame memory allocation cache.
|
Misc Errors
|
Various miscellaneous errors that relate to the IPC open queue, to the hardware queue, or to other hardware failures.
|
Tx Driver Errors
|
Number of messages that relate to IPC transmission driver failures including messages to or from a destination without a valid transport entity from the seat; number of messages dropped because the packet size is larger than the maximum transmission unit (MTU); and number of messages without a valid destination address.
|
The following example shows how to display cumulative IPC counters for the local IPC server. Note that the recent IPC clearing has not cleared the IPC counters because the cumulative keyword displays the IPC statistics that have been generated since the router was rebooted.
Router# show ipc status cumulative
Time last IPC stat cleared : 00:00:05
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 3473 92
Total Protocol Control Frames 92 54
Total via Unreliable Connection-Less Service 2449 0
Total via Unreliable Sequenced Connection-Less Svc 970 0
Total via Reliable Connection-Oriented Service 54 92
Total Acknowledgements 0 0
Total Negative Acknowledgements 0 0
Total via Local Driver 0 0
Total via Platform Driver 0 92
Total Frames Dropped by Platform Drivers 0 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Out-of-Sequence Frame 0 Tx Test Drop 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
The following is sample output from the show ipc command with the zones keyword displaying information about the IPC zones and seats:
There are 3 Zones in this IPC realm.
Table 6 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
|
clear ipc statistics
|
Clears and resets the IPC statistics.
|
show ipc hog-info
To provide information about interprocess communication (IPC) messages that consume excessive CPU, use the show ipc hog-info command in privileged EXEC mode.
show ipc hog-info
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The Cisco IOS version of IPC provides a reliable ordered delivery of messages using an underlying platform driver transport or User Datagram Protocol (UDP) transport protocol.
The show ipc hog-info command displays information about IPC messages that are being processed when a CPUHOG error occurs, indicating that the client processing an IPC message is using too much CPU, or when an IPC message callback exceeds 200 milliseconds.
Examples
The following example shows that the IPC process has had a CPUHOG error or the message callback exceeded the 200-millisecond threshold:
Router# show ipc hog-info
Time last IPC process hogged CPU: 00:05:09
Source Destination Name Message-Type Time-taken
1030000 10000.14 ISSU Process: Active Por 0 864
1030000 10000.D RF : Active 0 0
In the following example, the show ipc status command shows a counter incrementing whenever a callback exceeds 200 milliseconds:
Time last IPC stat cleared : never
This processor is the IPC master server.
Do not drop output of IPC frames for test purposes.
1000 IPC Message Headers Cached.
Total from Local Ports 14328 3258
Total Protocol Control Frames 1628 713
Total via Unreliable Connection-Less Service 7865 0
Total via Unreliable Sequenced Connection-Less Svc 0 0
Total via Reliable Connection-Oriented Service 831 1629
Total Acknowledgments 1628 713
Total Negative Acknowledgments 0 0
Total via Local Driver 12 12
Total via Platform Driver 9478 1619
Total Frames Dropped by Platform Drivers 0 0
Total Frames Sent when media is quiesced 0
Unsupp IPC Proto Version 0 Tx Session Error 0
Corrupt Frame 0 Tx Seat Error 0
Duplicate Frame 0 Destination Unreachable 0
Rel Out-of-Seq Frame 0 Unrel Out-of-Seq Frame 0
Dest Port does Not Exist 0 Tx Driver Failed 0
Rx IPC Msg Alloc Failed 0 Rx IPC Frag Dropped 0
Rx IPC Transform Errors 0 Tx IPC Transform Errors 0
Unable to Deliver Msg 0 Tx Test Drop 0
Ctrl Frm Alloc Failed 0 Rx Msg Callback Hog 11
Buffer Errors Misc Errors
IPC Msg Alloc 0 IPC Open Port 0
Emer IPC Msg Alloc 0 No HWQ 0
IPC Frame PakType Alloc 0 Hardware Error 0
IPC Frame MemD Alloc 0 Invalid Messages 0
Related Commands
Command
|
Description
|
show ipc
|
Displays IPC statistics.
|
show ipv6 ospf interface
To display Open Shortest Path First (OSPF)-related interface information, use the show ipv6 ospf interface command in user EXEC or privileged mode.
show ipv6 ospf [process-id] [area-id] interface [interface-type interface-number] [brief]
Syntax Description
process-id
|
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here is the number assigned administratively when the OSPF routing process is enabled.
|
area-id
|
(Optional) Displays information about a specified area only.
|
interface-type interface-number
|
(Optional) Interface type and number.
|
brief
|
(Optional) Displays brief overview information for OSPF interfaces, states, addresses and masks, and areas on the router.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(4)T
|
Command output is changed when authentication is enabled.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.4(9)T
|
Command output is changed when encryption is enabled.
|
12.2(33)SRB
|
The brief keyword was added.
|
12.4(15)XF
|
Output displays were modified so that VMI PPPoE interface-based local state values are displayed in the command output when a VMI interface is specified.
|
12.4(15)T
|
This command was integrated into Cisco IOS Release 12.4(15)T
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
Examples
show ipv6 ospf interface Standard Output Example
The following is sample output from the show ipv6 ospf interface command:
Router# show ipv6 ospf interface
ATM3/0 is up, line protocol is up
Link Local Address 2001:0DB1:205:5FFF:FED3:5808, Interface ID 13
Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3
Network Type POINT_TO_POINT, Cost: 1
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/2/2, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 12, maximum is 12
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 172.16.4.4
Suppress hello for 0 neighbor(s)
FastEthernet0/0 is up, line protocol is up
Link Local Address 2001:0DB1:205:5FFF:FED3:5808, Interface ID 3
Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3
Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 172.16.6.6, local address 2001:0DB1:205:5FFF:FED3:6408
Backup Designated router (ID) 172.16.3.3, local address 2001:0DB1:205:5FFF:FED3:5808
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 12, maximum is 12
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 172.16.6.6 (Designated Router)
Suppress hello for 0 neighbor(s)
Table 7 describes the significant fields shown in the display.
Table 7 show ipv6 ospf interface Field Descriptions
Field
|
Description
|
ATM3/0
|
Status of the physical link and operational status of protocol.
|
Link Local Address
|
Interface IPv6 address.
|
Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3
|
The area ID, process ID, instance ID, and router ID of the area from which this route is learned.
|
Network Type POINT_TO_POINT, Cost: 1
|
Network type and link-state cost.
|
Transmit Delay
|
Transmit delay, interface state, and router priority.
|
Designated Router
|
Designated router ID and respective interface IP address.
|
Backup Designated router
|
Backup designated router ID and respective interface IP address.
|
Timer intervals configured
|
Configuration of timer intervals.
|
Hello
|
Number of seconds until the next hello packet is sent out this interface.
|
Neighbor Count
|
Count of network neighbors and list of adjacent neighbors.
|
Cisco IOS Release 12.2(33)SRB Example
The following is sample output of the show ipv6 ospf interface command when the brief keyword is entered.
Router# show ipv6 ospf interface brief
Interface PID Area Intf ID Cost State Nbrs F/C
VL0 6 0 21 65535 DOWN 0/0
Tu0 1000 0 19 11111 DOWN 0/0
OSPF with Authentication on the Interface Example
The following is sample output from the show ipv6 ospf interface command with authentication enabled on the interface:
Router# show ipv6 ospf interface
Ethernet0/0 is up, line protocol is up
Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
Network Type BROADCAST, Cost:10
MD5 Authentication SPI 500, secure socket state UP (errors:0)
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
Backup Designated router (ID) 10.10.10.1, local address
2001:0DB1:A8BB:CCFF:FE00:6E00
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.11.11.1 (Designated Router)
Suppress hello for 0 neighbor(s)
OSPF with Null Authentication Example
The following is sample output from the show ipv6 ospf interface command with null authentication configured on the interface:
Router# show ipv6 ospf interface
Ethernet0/0 is up, line protocol is up
Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
Network Type BROADCAST, Cost:10
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
Backup Designated router (ID) 10.10.10.1, local address
2001:0DB1:A8BB:CCFF:FE00:6E00
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.11.11.1 (Designated Router)
Suppress hello for 0 neighbor(s)
OSPF with Authentication for the Area Example
The following is sample output from the show ipv6 ospf interface command with authentication configured for the area:
Router# show ipv6 ospf interface
Ethernet0/0 is up, line protocol is up
Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
Network Type BROADCAST, Cost:10
MD5 Authentication (Area) SPI 1000, secure socket state UP (errors:0)
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
Backup Designated router (ID) 10.10.10.1, local address
FE80::A8BB:CCFF:FE00:6E00
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.11.11.1 (Designated Router)
Suppress hello for 0 neighbor(s)
OSPF with Dynamic Cost Example
The following display shows sample output from the show ipv6 ospf interface command when the OSPF cost dynamic is configured.
Router1# show ipv6 ospf interface serial2/0
Serial2/0 is up, line protocol is up
Link Local Address 2001:0DB1:A8BB:CCFF:FE00:100, Interface ID 10
Area 1, Process ID 1, Instance ID 0, Router ID 172.1.1.1
Network Type POINT_TO_MULTIPOINT, Cost: 64 (dynamic), Cost Hysteresis: 200
Cost Weights: Throughput 100, Resources 20, Latency 80, L2-factor 100
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
Index 1/2/3, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)
Related Commands
Command
|
Description
|
interface vmi
|
Creates a virtual multipoint interface (VMI) that can be configured and applied dynamically.
|
show l2protocol-tunnel
To display the protocols that are tunneled on an interface or on all interfaces, use the show l2protocol-tunnel command.
show l2protocol-tunnel [{interface interface mod/port} | summary | vlan vlan}]
Syntax Description
interface interface
|
(Optional) Specifies the interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
|
mod/port
|
Module and port number.
|
summary
|
(Optional) Displays a summary of a tunneled port.
|
vlan vlan
|
(Optional) Limits the display to interfaces on the specified VLAN; valid values are from 1 to 4094.
|
Command Default
This command has no default settings.
Command Modes
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
|
The show l2protocol-tunnel summary command output was changed to display the following information:
• Global drop-threshold setting
• Up status of a Layer 2-protocol interface tunnel
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to the 12.2 SX release.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXI
|
This command was changed to add the optional vlan vlan keyword and argument.
|
Usage Guidelines
The show l2protocol-tunnel command displays only the ports that have protocol tunneling enabled.
The show l2protocol-tunnel summary command displays the ports that have protocol tunneling enabled, regardless of whether the port is down or currently configured as a trunk.
Examples
This example shows how to display the protocols that are tunneled on all interfaces:
Router# show l2protocol-tunnel
COS for Encapsulated Packets: 5
Drop Threshold for Encapsulated Packets: 3000
Port Protocol Shutdown Drop Encapsulation Decapsulation Drop
Threshold Threshold Counter Counter Counter
------- -------- --------- --------- ------------- ------------- -------------
Fa3/38 cdp ---- 3000 5 0 0
This example shows how to display a summary of Layer 2-protocol tunnel ports:
Router# show l2protocol-tunnel summary
COS for Encapsulated Packets:5
Drop Threshold for Encapsulated Packets:0
Port Protocol Shutdown Drop Status
(cdp/stp/vtp) (cdp/stp/vtp)
------- ----------- ---------------- ---------------- ----------
Fa9/1 --- stp --- ----/----/---- ----/----/---- down
Fa9/9 cdp stp vtp ----/----/---- ----/----/---- up
Fa9/47 --- --- --- ----/----/---- 1500/1500/1500 down(trunk)
Fa9/48 cdp stp vtp ----/----/---- ----/----/---- down(trunk)
This example shows how to display Layer 2-protocol tunnel information on interfaces for a specific VLAN:
Router# show l2protocol-tunnel vlan 1
COS for Encapsulated Packets: 5
Drop Threshold for Encapsulated Packets: 0
Port Protocol Thresholds Counters
Shutdown Drop Encap Decap Drop
------------------- -------- --------- --------- --------- --------- ---------
Related Commands
Command
|
Description
|
l2protocol-tunnel
|
Enables the protocol tunneling on an interface and specifies the type of protocol to be tunneled.
|
l2protocol-tunnel drop-threshold
|
Specifies the maximum number of packets that can be processed for the specified protocol on that interface before being dropped.
|
l2protocol-tunnel global drop-threshold
|
Enables rate limiting at the software level.
|
l2protocol-tunnel shutdown-threshold
|
Specifies the maximum number of packets that can be processed for the specified protocol on that interface in one second.
|
show l3-mgr
To display the information about the Layer 3 manager, use the show l3-mgr command in user EXEC or privileged EXEC mode.
show l3-mgr status
show l3-mgr {interface interface interface-number | null interface-number | port-channel number
| vlan vlan-id | status}}
Syntax Description
status
|
Displays information about the global variable.
|
interface
|
Displays information about the Layer 3 manager.
|
interface
|
Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
|
interface-number
|
Module and port number; see the "Usage Guidelines" section for valid values.
|
null interface-number
|
Specifies the null interface; the valid value is 0.
|
port-channel number
|
Specifies the channel interface; valid values are a maximum of 64 values ranging from 1 to 282.
|
vlan vlan-id
|
Specifies the VLAN; valid values are from 1 to 4094.
|
status
|
Displays status information about the Layer 3 manager.
|
Defaults
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-channel number values from 257 to 282 are supported on the CSM and the FWSM only.
Examples
This example shows how to display the status of the Layer 3 manager:
Router# show l3-mgr status
l3_mgr_max_queue_count: 1060
l3_mgr_req_q.ip_inv_count: 303
l3_mgr_req_q.ipx_inv_count: 0
l3_mgr_outpak_count: 18871
l3_mgr_inpak_count: 18871
l3_mgr_max_pending_pak: 4
l3_mgr_pending_pak_count: 0
current nde addr: 0.0.0.0
This example shows how to display the information about the Layer 3 manager for a specific interface:
Router# show l3-mgr interface fastethernet 5/40
show l3vpn encapsulation ip
To display the L3VPN encapsulation profile health and the underlying tunnel interface, use the show l3vpn encapsulation ip command in privileged EXEC mode.
show l3vpn encapsulation ip [profile name]
Syntax Description
profile name
|
(Optional) Name of the Layer 3 encapsulation profile.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SRE
|
This command was introduced.
|
Examples
The following is a sample output from the show l3vpn encapsulation ip command:
Router# show l3vpn encapsulation ip tunnelencap
transport ipv4 source Loopback0
Tunnel Tunnel0 Created [OK]
Tunnel Transport Source Loopback0
show lacp
To display Link Aggregation Control Protocol (LACP) information, use the show lacp command in user EXEC or privileged EXEC mode.
show lacp [channel-group-number ] | {counters | internal [detail] | neighbor [detail]} | [sys-id]
Syntax Description
channel-group- number
|
(Optional) Number of the channel group; valid values are from 1 to 282.
|
counters
|
Displays information about the LACP traffic statistics.
|
detail
|
(Optional) Detailed internal information.
|
internal
|
Displays LACP internal information.
|
neighbors
|
Displays information about the LACP neighbor.
|
sys-id
|
Displays the LACP system identification. It is a combination of the port priority and the MAC address of the device
|
Defaults
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 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.
|
Usage Guidelines
Use the show lacp command to troubleshoot problems related to LACP in a network.
If you do not specify a channel-group, all channel groups are displayed.
The channel-group values from 257 to 282 are supported on the CSM and the FWSM only.
You can enter the optional channel-group to specify a channel group for all keywords, except the sys-id keyword.
Examples
show lacp sys-id Example
This example shows how to display the LACP system identification using the show lacp sys-id command:
The system identification is made up of the system priority and the system MAC address. The first 2 bytes are the system priority, and the last 6 bytes are the globally administered individual MAC address that is associated to the system.
LACP Statistics for a Specific Channel Group Examples
This example shows how to display the LACP statistics for a specific channel group:
Router# show lacp 1 counters
Port Sent Recv Sent Recv Pkts Err
---------------------------------------------------
The output displays the following information:
•
The LACPDUs Sent and Recv columns display the LACPDUs that are sent and received on each specific interface.
•
The LACPDUs Pkts and Err columns display the marker-protocol packets.
The following example shows output from a show lacp number counters command:
Router1# show lacp 5 counters
LACPDUs Marker Marker Response LACPDUs
Port Sent Recv Sent Recv Sent Recv Pkts Err
---------------------------------------------------------------------
Table 8 describes the significant fields shown in the sample output of the show lacp number counters command.
Table 8 show lacp number counters Field Descriptions
Field
|
Description
|
LACPDUs
Sent Recv
|
Number of LACP PDUs sent and received.
|
Marker
Sent Recv
|
Attempts to avoid data loss when a member link is removed from an LACP bundle.
|
Marker Response
Sent Recv
|
Cisco IOS response to the Marker protocol.
|
LACPDUs
Pkts Err
|
Number of LACP PDU packets transmitted and the number of packet errors.
|
The following example shows output from a show lacp number internal command:
Router1# show lacp 5 internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi5/0/0 SA bndl 32768 0x5 0x5 0x42 0x3D
Table 9 describes the significant fields shown in the sample output of the show lacp number internal command.
Table 9 show lacp number internal Field Descriptions
Field
|
Description
|
Flags
|
Meanings of each flag value, which indicates a device activity.
|
Port
|
Port on which link bundling is configured.
|
Flags
|
Indicators of device activity.
|
State
|
Activity state of the port. States can be any of the following:
• Bndl—Port is attached to an aggregator and bundled with other ports.
• Susp—Port is in suspended state, so it is not attached to any aggregator.
• Indep—Port is in independent state (not bundled but able to switch data traffic). This condition differs from the previous state because in this case LACP is not running on the partner port.
• Hot-sby—Port is in hot standby state.
• Down—Port is down.
|
LACP port Priority
|
Priority assigned to the port.
|
Admin Key
|
Defines the ability of a port to aggregate with other ports.
|
Oper Key
|
Operational key that determines the aggregation capability of the link.
|
Port Number
|
Number of the port.
|
Port State
|
Activity state of the port.
|
Internal Information About a Spcific Channel Group Example
This example shows how to display internal information for the interfaces that belong to a specific channel:
Router# show lacp 1 internal
Flags: S - Device sends PDUs at slow rate. F - Device sends PDUs at fast rate.
A - Device is in Active mode. P - Device is in Passive mode.
LACPDUs LACP Port Admin Oper Port Port
Port Flags State Interval Priority Key Key Number State
Fa4/1 saC bndl 30s 32768 100 100 0xc1 0x75
Fa4/2 saC bndl 30s 32768 100 100 0xc2 0x75
Fa4/3 saC bndl 30s 32768 100 100 0xc3 0x75
Fa4/4 saC bndl 30s 32768 100 100 0xc4 0x75
Table 10 describes the fields that are shown in the example.
Table 10 show lacp internal Command Output Fields
Field
|
Description
|
State
|
State of the specific port at the current moment is displayed; allowed values are as follows:
• bndl—Port is attached to an aggregator and bundled with other ports.
• susp—Port is in a suspended state; it is not attached to any aggregator.
• indep—Port is in an independent state (not bundled but able to switch data traffic. In this case, LACP is not running on the partner port).
• hot-sby—Port is in a hot-standby state.
• down—Port is down.
|
LACPDUs Interval
|
Interval setting.
|
LACP Port Priority
|
Port-priority setting.
|
Admin Key
|
Administrative key.
|
Oper Key
|
Operator key.
|
Port Number
|
Port number.
|
Port State
|
State variables for the port that are encoded as individual bits within a single octet with the following meaning [1]:
• bit0: LACP_Activity
• bit1: LACP_Timeout
• bit2: Aggregation
• bit3: Synchronization
• bit4: Collecting
• bit5: Distributing
• bit6: Defaulted
• bit7: Expired
|
Information About LACP Neighbors for a Specific Port Example
This example shows how to display the information about the LACP neighbors for a specific port channel:
Router# show lacp 1 neighbors
Flags: S - Device sends PDUs at slow rate. F - Device sends PDUs at fast rate.
A - Device is in Active mode. P - Device is in Passive mode.
Channel group 1 neighbors
Port System ID Port Number Age Flags
Fa4/1 8000,00b0.c23e.d84e 0x81 29s P
Fa4/2 8000,00b0.c23e.d84e 0x82 0s P
Fa4/3 8000,00b0.c23e.d84e 0x83 0s P
Fa4/4 8000,00b0.c23e.d84e 0x84 0s P
If no PDUs have been received, the default administrative information is displayed in braces.
Related Commands
Command
|
Description
|
clear lacp counters
|
Clears the statistics for all interfaces belonging to a specific channel group.
|
lacp port-priority
|
Sets the priority for the physical interfaces.
|
lacp system-priority
|
Sets the priority of the system.
|
show link state group
To display the link-state group information., use the show link state group command in user EXEC or privileged EXEC mode.
show link state group detail
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.
Examples
The following example displays the link-state group information:
Router# show link state group 1
Link State Group: 1 Status: Enabled, Down
Router> show link state group detail
(Up):Interface up (Dwn):Interface Down (Dis):Interface disabled
Link State Group: 1 Status: Enabled, Down
Upstream Interfaces : Gi3/5(Dwn) Gi3/6(Dwn)
Downstream Interfaces : Gi3/1(Dis) Gi3/2(Dis) Gi3/3(Dis) Gi3/4(Dis)
Link State Group: 2 Status: Enabled, Down
Upstream Interfaces : Gi3/15(Dwn) Gi3/16(Dwn) Gi3/17(Dwn)
Downstream Interfaces : Gi3/11(Dis) Gi3/12(Dis) Gi3/13(Dis) Gi3/14(Dis)
(Up):Interface up (Dwn):Interface Down (Dis):Interface disabled
Related Commands
Command
|
Description
|
link state track
|
Configures the link state tracking number.
|
link state group
|
Configures the link state group and interface, as either an upstream or downstream interface in the group.
|
show mac-address-table dynamic
To display dynamic MAC address table entries only, use the show mac-address-table dynamic command in privileged EXEC mode.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
show mac-address-table dynamic [address mac-address | interface type slot/port | vlan vlan]
Catalyst Switches
show mac-address-table dynamic [address mac-address | detail | interface type number |
protocol protocol | | module number | vlan vlan] [[begin |exclude | include] expression]
Catalyst 6500 Series Switches
show mac-address-table dynamic [{address mac-addr} | {interface interface interface-number
[all | module number]} | {module num} | {vlan vlan-id [all | module number]}]
Syntax Description
address mac-address
|
(Optional) Specifies a 48-bit MAC address; valid format is H.H.H.
|
detail
|
(Optional) Specifies a detailed display of MAC address table information.
|
interface type number
|
(Optional) Specifies an interface to match; valid type values are FastEthernet and GigabitEthernet, valid number values are from 1 to 9.
|
interface type
|
(Optional) Specifies an interface to match; valid type values are FastEthernet and GigabitEthernet.
|
slot
|
(Optional) Adds dynamic addresses to module in slot 1 or 2.
|
port
|
(Optional) Port interface number ranges based on type of Ethernet switch network module used:
• 0 to 15 for NM-16ESW
• 0 to 35 for NM-36ESW
• 0 to 1 for GigabitEthernet
|
protocol protocol
|
(Optional) Specifies a protocol. See the "Usage Guidelines" section for keyword definitions.
|
module number
|
(Optional) Displays information about the MAC address table for a specific Distributed Forwarding Card (DFC) module.
|
vlan vlan
|
(Optional) Displays entries for a specific VLAN; valid values are from 1 to 1005.
|
begin
|
(Optional) Specifies that the output display begin with the line that matches the expression.
|
exclude
|
(Optional) Specifies that the output display exclude lines that match the expression.
|
include
|
(Optional) Specifies that the output display include lines that match the specified expression.
|
expression
|
Expression in the output to use as a reference point.
|
all
|
(Optional) Specifies that the output display all dynamic MAC-address table entries.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(7)XE
|
This command was introduced on Catalyst 6000 series switches.
|
12.2(2)XT
|
This command was implemented on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(14)SX
|
Support for this command was introduced on the Catalyst 6500 series switch.
|
12.2(33)SXH
|
This command was changed to support the all keyword on the Catalyst 6500 series switch.
|
Usage Guidelines
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The show mac-address-table dynamic command output for an EtherChannel interface changes the port-number designation (for example, 5/7) to a port-group number.
Catalyst Switches
The keyword definitions for the protocol argument are:
•
ip—Specifies IP protocol
•
ipx—Specifies Internetwork Packet Exchange (IPX) protocols
•
assigned—Specifies assigned protocol entries
•
other—Specifies other protocol entries
The show mac-address-table dynamic command output for an EtherChannel interface changes the port-number designation (for example, 5/7) to a port-group number.
Catalyst 6500 Series Switches
The mac-address is a 48-bit MAC address and the valid format is H.H.H.
The optional module num keyword and argument are supported only on DFC modules. The module num keyword and argument designate the module number.
Examples
The following examples show how to display all dynamic MAC address entries.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
Router# show mac-address-table dynamic
Non-static Address Table:
Destination Address Address Type VLAN Destination Port
------------------- ------------ ---- --------------------
000a.000a.000a Dynamic 1 FastEthernet4/0
002a.2021.4567 Dynamic 2 FastEthernet4/0
Catalyst Switches
Router# show mac-address-table dynamic
vlan mac address type protocol qos ports
-----+---------------+--------+---------+---+--------------------------------
200 0010.0d40.37ff dynamic ip -- 5/8
1 0060.704c.73ff dynamic ip -- 5/9
4095 0000.0000.0000 dynamic ip -- 15/1
1 0060.704c.73fb dynamic other -- 5/9
1 0080.1c93.8040 dynamic ip -- 5/9
4092 0050.f0ac.3058 dynamic ip -- 15/1
1 00e0.4fac.b3ff dynamic other -- 5/9
The following example shows how to display dynamic MAC address entries with a specific protocol type (in this case, assigned):
Router# show mac-address-table dynamic protocol assigned
vlan mac address type protocol qos ports
-----+---------------+--------+---------+---+--------------------------------
4092 0000.0000.0000 dynamic assigned -- Router
4092 0050.f0ac.3059 dynamic assigned -- Router
1 0010.7b3b.0978 dynamic assigned -- Fa5/9
The following example shows the detailed output for the previous example:
Router# show mac-address-table dynamic protocol assigned detail
MAC Table shown in details
========================================
Type Always Learn Trap Modified Notify Capture Protocol Flood
-------+------------+----+--------+------+-------+--------+-----+
QoS bit L3 Spare Mac Address Age Byte Pvlan Xtag SWbits Index
-----------------+--------+--------------+--------+-----+----+------+-----
DYNAMIC NO NO YES NO NO assigned NO
Bit Not On 0 0000.0000.0000 255 4092 0 0 0x3
DYNAMIC NO NO YES NO NO assigned NO
Bit Not On 0 0050.f0ac.3059 254 4092 0 0 0x3
DYNAMIC NO NO YES NO NO assigned NO
Bit Not On 0 0010.7b3b.0978 254 1 0 0 0x108
Catalyst 6500 Series Switches
This example shows how to display all the dynamic MAC-address entries for a specific VLAN:
Router# show mac-address-table dynamic vlan 200 all
Legend: * - primary entry
age - seconds since last seen
vlan mac address type learn age ports
------+----------------+--------+-----+----------+--------------------------
200 0010.0d40.37ff dynamic NO 23 Gi5/8
This example shows how to display all the dynamic MAC-address entries:
Router# show mac-address-table dynamic
Legend: * - primary entry
age - seconds since last seen
vlan mac address type learn age ports
------+----------------+--------+-----+----------+--------------------------
* 10 0010.0000.0000 dynamic Yes n/a Gi4/1
* 3 0010.0000.0000 dynamic Yes 0 Gi4/2
* 1 0002.fcbc.ac64 dynamic Yes 265 Gi8/1
* 1 0009.12e9.adc0 static No - Router
Related Commands
Command
|
Description
|
show mac-address-table address
|
Displays MAC address table information for a specific MAC address.
|
show mac-address-table aging-time
|
Displays the MAC address aging time.
|
show mac-address-table count
|
Displays the number of entries currently in the MAC address table.
|
show mac-address-table detail
|
Displays detailed MAC address table information.
|
show mac-address-table interface
|
Displays the MAC address table information for a specific interface.
|
show mac-address-table multicast
|
Displays multicast MAC address table information.
|
show mac-address-table protocol
|
Displays MAC address table information based on protocol.
|
show mac-address-table static
|
Displays static MAC address table entries only.
|
show mac-address-table vlan
|
Displays the MAC address table information for a specific VLAN.
|
show mls asic
To display the application-specific integrated circuit (ASIC) version, use the show mls asic command in user EXEC or privileged EXEC mode.
show mls asic
Syntax Description
This command has no arguments or keywords.
Defaults
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.
|
Examples
This example shows how to display the ASIC versions on a Supervisor Engine 2:
This example shows how to display the ASIC versions on a Supervisor Engine 720:
Tycho - ver:1 Cisco-id:1C8 Vendor-id:49
Related Commands
Command
|
Description
|
show mls df-table
|
Displays information about the DF table.
|
show mls ip
|
Displays the Multilayer Switching (MLS) IP information.
|
show mls ipx
|
Displays the Multilayer Switching (MLS) IPX information.
|
show mls qos
|
Displays Multilayer Switching (MLS) quality of service (QoS) information
|
show mls statistics
|
Displays the Multilayer Switching (MLS) statistics for the Internet Protocol (IP)
|
show mls ip
To display the Multilayer Switching (MLS) IP information, use the show mls ip command in user EXEC or privileged EXEC mode.
show mls ip [any | destination {hostname | ip-address} | detail | flow {tcp | udp} | {vlan vlan-id |
macd destination-mac-address | macs source-mac-address | module number |
source {hostname | ip-address} | count | static]
show mls ip {ipv6 | mpls}
Syntax Description
any
|
(Optional) Displays any MLS IP information.
|
destination hostname
|
(Optional) Displays the entries for a specific destination hostname.
|
destination ip-address
|
(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.
|
vlan vlan-id
|
(Optional) Specifies the virtual local area network (VLAN) ID; valid values are from 1 to 4094.
|
macd destination-mac-address
|
(Optional) Specifies the destination MAC address.
|
macs source- mac-address
|
(Optional) Specifies the source Media Access Control (MAC) address.
|
module number
|
(Optional) Displays the entries that are downloaded on the specified module; see the "Usage Guidelines" section for valid values.
|
source hostname
|
(Optional) Displays the entries for a specific source address.
|
source ip-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.
|
Defaults
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 module number keyword and argument.
When you view the output, note that a colon (:) is used to separate the fields.
Examples
This example shows how to display any MLS IP information:
Displaying Netflow entries in Supervisor Earl
DstIP SrcIP Prot:SrcPort:DstPort Src i/f:AdjPtr
--------------------------------------------------------------------
Pkts Bytes Age LastSeen Attributes
---------------------------------------------------
0.0.0.0 0.0.0.0 0 :0 :0 0 : 0x0
82 3772 1329 20:46:03 L3 - Dynamic
This example shows how to display MLS information on a specific IP address:
Router# show mls ip destination 172.20.52.122
Displaying Netflow entries in Supervisor Earl
DstIP SrcIP Dst i/f:DstMAC Pkts Bytes
-----------------------------------------------------------------------
SrcDstPorts SrcDstEncap Age LastSeen
----------------------------------------
172.20.52.122 0.0.0.0 5 : 00e0.4fac.b3ff 684 103469
Fa5/9,Fa5/9 ARPA,ARPA 281 07:17:02
Number of Entries Found = 1
This example shows how to display MLS information on a specific flow type:
Router# show mls ip flow udp
Displaying Netflow entries in Supervisor Earl
DstIP SrcIP Prot:SrcPort:DstPort Src i/f:AdjPtr
--------------------------------------------------------------------
Pkts Bytes Age LastSeen Attributes
---------------------------------------------------
0.0.0.0 0.0.0.0 0 :0 :0 0 : 0x0
78 3588 1259 20:44:53 L3 - Dynamic
This example shows how to display detailed MLS information:
Router# show mls ip detail
Displaying Netflow entries in Supervisor Earl
DstIP SrcIP Prot:SrcPort:DstPort Src i/f:AdjPtr
--------------------------------------------------------------------
Pkts Bytes Age LastSeen Attributes
---------------------------------------------------
Mask Pi R CR Xt Prio Dsc IP_EN OP_EN Pattern Rpf FIN_RDT FIN/RST
----+--+-+--+--+----+---+-----+-----+-------+---+-------+-------
Ig/acli Ig/aclo Ig/qosi Ig/qoso Fpkt Gemini MC-hit Dirty Diags
-------+-------+-------+-------+----+------+------+-----+------
QoS Police Count Threshold Leak Drop Bucket Use-Tbl Use-Enable
-----------+------------+---------+-----------+----+-------+-------+----------+
127.0.0.19 127.0.0.16 udp :68 :67 1009: 0x0
72 3312 1170 20:43:24 L3 - Dynamic
0 1 0 0 1 0 0 1 1 0 0 0 0
Related Commands
Command
|
Description
|
show mls asic
|
display the application-specific integrated circuit (ASIC) version
|
show mls df-table
|
Displays information about the DF table.
|
show mls ipx
|
Displays the Multilayer Switching (MLS) IPX information.
|
show mls qos
|
Displays Multilayer Switching (MLS) quality of service (QoS) information
|
show mls statistics
|
Displays the Multilayer Switching (MLS) statistics for the Internet Protocol (IP)
|
show mls ipx
To display Multilayer Switching (MLS) Internetwork Packet Exchange (IPX) information, use the show mls ipx command in user EXEC or privileged EXEC mode.
show mls ipx [destination ipx-network | interface interface interface-number | vlan vlan-id |
macd destination-mac-address | macs source-mac-address | module number |
source hostname | ipx-network] [detail | count]
Syntax Description
destination ipx-network
|
(Optional) Displays the entries for a specific destination network address.
|
interface
|
(Optional) Specifies the interface.
|
interface
|
(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
|
interface-number
|
(Optional) Module and port number; see the "Usage Guidelines" section for valid values.
|
vlan vlan-id
|
(Optional) Specifies the virtual local area network (VLAN) ID; valid values are from 1 to 4094.
|
macd destination-mac-address
|
(Optional) Specifies the destination Media Access Control (MAC) address.
|
macs source- mac-address
|
(Optional) Specifies the source MAC address.
|
module number
|
(Optional) Displays the entries that are downloaded on the specified slot; see the "Usage Guidelines" section for valid values.
|
source hostname
|
(Optional) Displays the entries for a specific source address.
|
source ipx-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.
|
Defaults
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 module number keyword and argument.
Examples
This example shows how to display MLS IPX information:
DstNet-DstNode SrcNet Dst i/f:DstMAC Pkts Bytes
-----------------------------------------------------------------------
SrcDstPorts SrcDstEncap Age LastSeen
----------------------------------------
Number of Entries Found = 0
This example shows how to display the total number of MLS entries:
Router# show mls ipx count
Related Commands
Command
|
Description
|
mls ipx
|
Enables MLS IPX on the interface.
|
show mls asic
|
display the application-specific integrated circuit (ASIC) version
|
show mls df-table
|
Displays information about the DF table.
|
show mls ip
|
Displays the Multilayer Switching (MLS) IP information.
|
show mls qos
|
Displays Multilayer Switching (MLS) quality of service (QoS) information
|
show mls statistics
|
Displays the Multilayer Switching (MLS) statistics for the Internet Protocol (IP)
|
show mobility
To display information about the Layer 3 mobility and the wireless network, use the show mobility command in privileged EXEC mode.
show mobility {ap [ip-address] | mn [ip ip-address] | mac mac-address | network network-id |
status}
Syntax Description
ap
|
Displays information about the access point.
|
ip-address
|
(Optional) IP address.
|
mn
|
Displays information about the mobile node.
|
ip ip-address
|
(Optional) Displays information about the IP database thread.
|
mac mac-address
|
Displays information about the MAC database thread.
|
network network-id
|
Displays information for a specific wireless network ID.
|
status
|
Displays status information.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(18)SXD
|
This command was introduced on the Supervisor Engine 720.
|
12.2(18)SXD3
|
The output of this command was changed to include the TCP adjust-mss status.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This command is supported on Cisco 7600 series routers that are configured with a WLSM only.
Examples
This example shows how to display information about the access point:
AP IP Address AP Mac Address Wireless Network-ID
--------------- -------------- -------------------
10.1.1.2 000d.29a2.a852 101 102 109 103
This example shows how to display information about the access points for a specific network ID:
Router# show mobility ap 172.16.1.2 detail
MAC Address : 000d.29a2.a852
Participating Wireless Tunnels: 101, 102, 109, 103
Registered Mobile Nodes on AP {172.16.1.2, 000d.29a2.a852} :
MN Mac Address MN IP Address AP IP Address Wireless Network-ID
-------------- --------------- --------------- -------------------
000a.8afa.85c9 10.1.3.11 172.16.1.2 103
000d.bdb7.83f7 10.1.2.11 172.16.1.2 102
000d.bdb7.83fb 10.1.1.11 172.16.1.2 101
Router# show mobility network-id 101
Wireless Network ID : 101
Wireless Tunnel Source IP Address : 10.1.1.1
Wireless Network Properties : Trusted
Wireless Network State : Up
Registered Access Point on Wireless Network 101:
AP IP Address AP Mac Address Wireless Network-ID
--------------- -------------- -------------------
176.16.1.2 000d.29a2.a852 101 102 109 103
Registered Mobile Nodes on Wireless Network 101:
MN Mac Address MN IP Address AP IP Address Wireless Network-ID
-------------- --------------- --------------- -------------------
000d.bdb7.83fb 10.1.1.11 176.16.1.2 101
Router# show mobility status
WLAN Module is located in Slot: 4 (HSRP State: Active) LCP
Communication status : up
MAC address used for Proxy ARP: 0030.a349.d800
Number of Wireless Tunnels : 1
Number of Access Points : 2
Number of Mobile Nodes : 0
Wireless Tunnel Bindings:
Src IP Address Wireless Network-ID Flags
--------------- ------------------- -------
Flags: T=Trusted, B=IP Broadcast enabled, A=TCP Adjust-mss enabled
Related Commands
Command
|
Description
|
mobility
|
Configures the wireless mGRE tunnels.
|
show module
To display the module status and information, use the show module command in user EXEC or privileged EXEC mode.
show module [mod-num | all | provision | version]
Syntax Description
mod-num
|
(Optional) Number of the module.
|
all
|
(Optional) Displays the information for all modules.
|
provision
|
(Optional) Displays the status about the module provisioning.
|
version
|
(Optional) Displays the version information.
|
Defaults
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
In the Mod Sub-Module fields, the show module command displays the supervisor engine number but appends the uplink daughter card's module type and information.
Entering the show module command with no arguments is the same as entering the show module all command.
Examples
This example shows how to display information for all modules on a Catalyst 6500 series switch that is configured with a Supervisor Engine 720:
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD0644030K
8 48 aCEF720 48 port 10/100/1000 Ethernet WS-X6748-GE-TX SAD07010045
9 32 dCEF720 32 port Gigabit Ethernet WS-X6832-SFP SAD07010045
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
5 00e0.aabb.cc00 to 00e0.aabb.cc3f 1.0 12.2(2003012 12.2(2003012 Ok
8 0005.9a3b.d8c4 to 0005.9a3b.d8c7 0.705 7.1(0.12-Eng 12.2(2003012 Ok
9 00e0.b0ff.f0f4 to 00e0.b0ff.f0f5 0.207 12.2(2002082 12.2(2003012 Ok
Mod Sub-Module Model Serial Hw Status
--- --------------------------- --------------- --------------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3 SAD0644031P 0.302 Ok
5 MSFC3 Daughtercard WS-SUP720 SAD06460172 0.701
This example shows how to display information for a specific module:
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD0644030K
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
5 00e0.aabb.cc00 to 00e0.aabb.cc3f 1.0 12.2(2003012 12.2(2003012 Ok
Mod Sub-Module Model Serial Hw Status
--- --------------------------- --------------- --------------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3 SAD0644031P 0.302 Ok
5 MSFC3 Daughtercard WS-SUP720 SAD06460172 0.701
This example shows how to display version information:
Router# show module version
Mod Port Model Serial # Versions
--- ---- ------------------ ----------- --------------------------------------
2 0 WS-X6182-2PA Hw : 1.0
Fw : 12.2(20030125:231135)
Sw : 12.2(20030125:231135)
4 16 WS-X6816-GBIC SAD04400CEE Hw : 0.205
WS-F6K-DFC3A SAD0641029Y Hw : 0.501
Fw : 12.2(20020828:202911)
Sw : 12.2(20030125:231135)
6 2 WS-X6K-SUP3-BASE SAD064300GU Hw : 0.705
Sw : 12.2(20030125:231135)
WS-X6K-SUP3-PFC3 SAD064200VR Hw : 0.701
Fw : 12.2(20021016:001154)
Sw : 12.2(20030125:231135)
WS-F6K-PFC3 SAD064300M7 Hw : 0.301
9 48 WS-X6548-RJ-45 SAD04490BAC Hw : 0.301
This example shows how to display module provisioning information:
Router# show module provision
Related Commands
Command
|
Description
|
show interfaces
|
Displays the status and statistics for the interfaces in the chassis.
|
show environment alarm
|
Displays the information about the environmental alarm.
|
show fm summary
|
Displays a summary of FM Information.
|
show environment status
|
Displays the information about the operational FRU status.
|
show msfc
To display Multilayer Switching Feature Card (MSFC) information, use the show msfc command in user EXEC or privileged EXEC mode.
show msfc {buffers | eeprom | fault | netint | tlb}
Syntax Description
buffers
|
Displays buffer-allocation information.
|
eeprom
|
Displays the internal information.
|
fault
|
Displays fault information.
|
netint
|
Displays network-interrupt information.
|
tlb
|
Displays information about the TLB registers.
|
Defaults
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.
|
Examples
These examples display the show msfc command output:
Router# show msfc buffers
Vlan Sel Min Max Cnt Rsvd
(FRU is 'Cat6k MSFC 2 daughterboard')
hexadecimal contents of block:
00: AB AB 01 90 13 22 01 00 00 02 60 03 00 EA 43 69 ....."....`...Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 00 00 00 00 00 sco Systems.....
20: 00 00 57 53 2D 46 36 4B 2D 4D 53 46 43 32 00 00 ..WS-F6K-MSFC2..
30: 00 00 00 00 00 00 53 41 44 30 36 32 31 30 30 36 ......SAD0621006
40: 37 00 00 00 00 00 00 00 00 00 37 33 2D 37 32 33 7.........73-723
50: 37 2D 30 33 00 00 00 00 00 00 41 30 00 00 00 00 7-03......A0....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 02 00 03 00 00 00 00 00 09 00 05 00 01 ................
80: 00 03 00 01 00 01 00 02 00 EA FF DF 00 00 00 00 ................
block-signature = 0xABAB, block-version = 1,
block-length = 144, block-checksum = 4898
IDPROM capacity (bytes) = 256 IDPROM block-count = 2
OEM String = 'Cisco Systems'
Product Number = 'WS-F6K-MSFC2'
Serial Number = 'SAD06210067'
Manufacturing Assembly Number = '73-7237-03'
Manufacturing Assembly Revision = 'A0'
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.5.1.3.1.1.2.234
Power Consumption = -33 centiamperes RMA failure code = 0-0-0-0
*** end of common block ***
hexadecimal contents of block:
00: 60 03 01 62 0A C2 00 00 00 00 00 00 00 00 00 00 `..b............
10: 00 00 00 00 00 01 00 23 00 08 7C A4 CE 80 00 40 .......#..|....@
20: 01 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 14 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
50: 10 00 4B 3C 41 32 80 80 80 80 80 80 80 80 80 80 ..K<A2..........
block-signature = 0x6003, block-version = 1,
block-length = 98, block-checksum = 2754
*** linecard specific block ***
feature-bits = 00000000 00000000
hardware-changes-bits = 00000000 00000001
mac base = 0008.7CA4.CE80
epld_versions = 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00
pair #0: type=14, count=01
pair #1: type=00, count=00
pair #2: type=00, count=00
pair #3: type=00, count=00
pair #4: type=00, count=00
pair #5: type=00, count=00
pair #6: type=00, count=00
pair #7: type=00, count=00
sensor #0: critical = 75 oC, warning = 60 oC
sensor #1: critical = 65 oC, warning = 50 oC
sensor #2: critical = -128 oC (sensor not present), warning = -128 oC (senso
sensor #3: critical = -128 oC (sensor not present), warning = -128 oC (senso
sensor #4: critical = -128 oC (sensor not present), warning = -128 oC (senso
sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (senso
sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (senso
sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (senso
*** end of linecard specific block ***
Vlan Sel Min Max Cnt Rsvd
Network IO Interrupt Throttling:
throttle count=0, timer count=0
netint usec=3999, netint mask usec=400
Virt Address range Phy Address range Attributes
0x10000000:0x1001FFFF 0x010000000:0x01001FFFF CacheMode=2, RW, Valid
0x10020000:0x1003FFFF 0x010020000:0x01003FFFF CacheMode=2, RW, Valid
0x10040000:0x1005FFFF 0x010040000:0x01005FFFF CacheMode=2, RW, Valid
0x10060000:0x1007FFFF 0x010060000:0x01007FFFF CacheMode=2, RW, Valid
0x10080000:0x10087FFF 0x010080000:0x010087FFF CacheMode=2, RW, Valid
0x10088000:0x1008FFFF 0x010088000:0x01008FFFF CacheMode=2, RW, Valid
0x18000000:0x1801FFFF 0x010000000:0x01001FFFF CacheMode=0, RW, Valid
0x19000000:0x1901FFFF 0x010000000:0x01001FFFF CacheMode=7, RW, Valid
0x1E000000:0x1E1FFFFF 0x01E000000:0x01E1FFFFF CacheMode=2, RW, Valid
0x1E880000:0x1E881FFF 0x01E880000:0x01E881FFF CacheMode=2, RW, Valid
0x1FC00000:0x1FC7FFFF 0x01FC00000:0x01FC7FFFF CacheMode=2, RO, Valid
0x30000000:0x3001FFFF 0x070000000:0x07001FFFF CacheMode=2, RW, Valid
0x40000000:0x407FFFFF 0x000000000:0x0007FFFFF CacheMode=3, RO, Valid
0x40800000:0x40FFFFFF 0x000800000:0x000FFFFFF CacheMode=3, RO, Valid
0x41000000:0x417FFFFF 0x001000000:0x0017FFFFF CacheMode=3, RO, Valid
0x41800000:0x419FFFFF 0x001800000:0x0019FFFFF CacheMode=3, RO, Valid
0x41A00000:0x41A7FFFF 0x001A00000:0x001A7FFFF CacheMode=3, RO, Valid
0x41A80000:0x41A9FFFF 0x001A80000:0x001A9FFFF CacheMode=3, RO, Valid
0x41AA0000:0x41ABFFFF 0x001AA0000:0x001ABFFFF CacheMode=3, RO, Valid
0x41AC0000:0x41AC7FFF 0x001AC0000:0x001AC7FFF CacheMode=3, RO, Valid
0x41AC8000:0x41ACFFFF 0x001AC8000:0x001ACFFFF CacheMode=3, RO, Valid
0x41AD0000:0x41AD7FFF 0x001AD0000:0x001AD7FFF CacheMode=3, RO, Valid
0x41AD8000:0x41AD9FFF 0x001AD8000:0x001AD9FFF CacheMode=3, RO, Valid
0x41ADA000:0x41ADBFFF 0x001ADA000:0x001ADBFFF CacheMode=3, RW, Valid
0x41ADC000:0x41ADDFFF 0x001ADC000:0x001ADDFFF CacheMode=3, RW, Valid
0x41ADE000:0x41ADFFFF 0x001ADE000:0x001ADFFFF CacheMode=3, RW, Valid
0x41AE0000:0x41AFFFFF 0x001AE0000:0x001AFFFFF CacheMode=3, RW, Valid
0x41B00000:0x41B7FFFF 0x001B00000:0x001B7FFFF CacheMode=3, RW, Valid
0x41B80000:0x41BFFFFF 0x001B80000:0x001BFFFFF CacheMode=3, RW, Valid
0x41C00000:0x41DFFFFF 0x001C00000:0x001DFFFFF CacheMode=3, RW, Valid
0x41E00000:0x41FFFFFF 0x001E00000:0x001FFFFFF CacheMode=3, RW, Valid
0x42000000:0x43FFFFFF 0x002000000:0x003FFFFFF CacheMode=3, RW, Valid
0x44000000:0x45FFFFFF 0x004000000:0x005FFFFFF CacheMode=3, RW, Valid
0x46000000:0x47FFFFFF 0x006000000:0x007FFFFFF CacheMode=3, RW, Valid
0x06E00000:0x06FFFFFF 0x006E00000:0x006FFFFFF CacheMode=2, RW, Valid
0x07000000:0x077FFFFF 0x007000000:0x0077FFFFF CacheMode=2, RW, Valid
0x07800000:0x07FFFFFF 0x007800000:0x007FFFFFF CacheMode=2, RW, Valid
Related Commands
Command
|
Description
|
show environment alarm
|
Displays the information about the environmental alarm.
|
show fm summary
|
Displays a summary of FM Information.
|
show environment status
|
Displays the information about the operational FRU status.
|
show mvr
To display the Multicast VLAN Registration (MVR) details configured on the router, use the show mvr command in Privileged EXEC mode.
mvr
no mvr
Syntax Description
This command has no arguments or keywords
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
15.1(3)S
|
This command was introduced on the Cisco 7600 routers.
|
Examples
This example displays the show mvr output:
MVR Max Multicast Groups: 1000
MVR Current multicast groups: 256
MVR Global query response time: 10 (tenths of sec)
Related Commands
Command
|
Description
|
mvr
|
Enables Multicast VLAN Registration (MVR) on the router.
|
mvr group
|
Configures a MVR group on the router.
|
mvr max-groups
|
Configures the MVR maximum number of groups on the router.
|
mvr querytime
|
Configures the MVR query response time.
|
mvr vlan
|
Configures the VLAN in which multicast data is received.
|
mvr type
|
Configures a switch port as an MVR receiver or source port.
|
mvr immediate
|
Enables the immediate leave feature of MVR on the port.
|
show mvr groups
|
Displays the MVR group configuration.
|
show mvr interface
|
Displays the details of all MVR member interfaces or a single requested MVR member interface.
|
show mvr members
|
Displays the details of all MVR members and number of MVR members in all active MVR groups on a particular VLAN or port.
|
show mvr receiver-ports
|
Displays all receiver ports that are members of an IP multicast group or those on the specified interface port.
|
show mvr source-ports
|
Displays all source ports that are members of an IP multicast group or those on the specified interface port.
|
clear mvr counters
|
Clears the join counters of all the MVR ports, source ports, receiver ports, or of a specified MVR interface port.
|
show mvr interface
To display the details of all the Multicast VLAN Registration (MVR) member interfaces or a single MVR member interface, use the show mvr interface command in Privileged EXEC mode.
show mvr interface [type module/port]
Syntax Description
type
|
(Optional) Specifies the interface type.
|
module/port
|
(Optional) Specifies the module or port number.
|
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
15.1(3)S
|
This command was introduced on the Cisco 7600 routers.
|
Examples
This example displays the show mvr interface output:
Router# show mvr interface gigabitEthernet 1/20
Port VLAN Type Status Immediate Leave
---- ---- ---- ------ ---------------
Gi1/20 2 RECEIVER ACTIVE/UP DISABLED
Related Commands
Command
|
Description
|
mvr
|
Enables MVR on the router.
|
mvr group
|
Configures an MVR group on the router.
|
mvr max-groups
|
Configures the maximum number of MVR groups on the router.
|
mvr querytime
|
Configures the MVR query response time.
|
mvr vlan
|
Configures the VLAN in which multicast data is received.
|
mvr type
|
Configures a switch port as an MVR receiver or source port.
|
mvr immediate
|
Enables the immediate leave feature of MVR on the port.
|
show mvr
|
Displays the MVR details.
|
show mvr groups
|
Displays the MVR group configuration.
|
show mvr interface
|
Displays the details of all MVR member interfaces, or a single requested MVR member interface.
|
show mvr members
|
Displays the details of all MVR members and number of MVR members in all active MVR groups on a particular VLAN or port.
|
show mvr receiver-ports
|
Displays all receiver ports that are members of an IP multicast group or those on the specified interface port.
|
show mvr source-ports
|
Displays all source ports that are members of an IP multicast group or those on the specified interface port.
|
clear mvr counters
|
Clears the join counters of all the MVR ports, source ports, receiver ports, or of a specified MVR interface port.
|
show mvr members
To display details of all the Multicast VLAN Registration (MVR) members and number of MVR members in all active MVR groups on a particular VLAN or port, use the show mvr members command in Privileged EXEC mode.
show mvr members [vlan vlan-id] [type module/port] [count]
Syntax Description
vlan-id
|
Specifies the MVR multicast VLAN ID.
|
type
|
(Optional) Specifies the interface type.
|
module/port
|
(Optional) Specifies the module or port number.
|
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
15.1(3)S
|
This command was introduced on the Cisco 7600 routers.
|
Examples
This example displays the show mvr members command output:
Router# show mvr members vlan 2
MVR Group IP Status Members
------------ ------ -------
224.000.001.001 ACTIVE Gi1/20(u),Gi1/21(u)
224.000.001.002 ACTIVE Fa3/2(d),Gi1/12(u)
Router# show mvr members vlan 490 count
Count of active MVR groups on vlan 490 = 400
Related Commands
Command
|
Description
|
mvr
|
Enables MVR on the router.
|
mvr group
|
Configures an MVR group on the router.
|
mvr max-groups
|
Configures the MVR maximum number of groups on the router.
|
mvr querytime
|
Configures the MVR query response time.
|
mvr vlan
|
Configures the VLAN in which multicast data is received.
|
mvr type
|
Configures a switch port as an MVR receiver or source port.
|
mvr immediate
|
Enables the immediate leave feature of MVR on the port.
|
show mvr
|
Displays the MVR details.
|
show mvr groups
|
Displays the MVR group configuration.
|
show mvr interface
|
Displays the details of all MVR member interfaces, or a single requested MVR member interface.
|
show mvr receiver-ports
|
Displays all receiver ports that are members of an IP multicast group or those on the specified interface port.
|
show mvr source-ports
|
Displays all source ports that are members of an IP multicast group or those on the specified interface port.
|
clear mvr counters
|
Clears the join counters of all the MVR ports, source ports, receiver ports, or of a specified MVR interface port.
|
show mvr receiver ports
To display all receiver ports that are members of any IP multicast group or those on the specified interface port, use the show mvr receiver ports command in Privileged EXEC mode.
show mvr receiver ports [type module/port]
Syntax Description
type
|
(Optional) Specifies the interface type.
|
module/port
|
(Optional) Specifies the module or port number.
|
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
15.1(3)S
|
This command was introduced on the Cisco 7600 routers.
|
Examples
This example displays the show mvr receiver ports output:
Router# show mvr receiver ports GigabitEthernet 1/7
Joins: v1,v2,v3 counter shows total IGMP joins
v3 counter shows IGMP joins received with both MVR and non-MVR groups
Port VLAN Status Immediate Joins
---- ---- ------------- ---------- ---------- -----------
Gi1/7 202 INACTIVE/UP ENABLED 305336 0
Related Commands
Command
|
Description
|
mvr
|
Enables MVR on the router.
|
mvr group
|
Configures an MVR group on the router.
|
mvr max-groups
|
Configures the maximum number of MVR groups on the router.
|
mvr querytime
|
Configures the MVR query response time.
|
mvr vlan
|
Configures the VLAN in which multicast data is received.
|
mvr type
|
Configures a switch port as an MVR receiver or source port.
|
mvr immediate
|
Enables the immediate leave feature of MVR on the port.
|
show mvr
|
Displays the MVR details.
|
show mvr groups
|
Displays the MVR group configuration.
|
show mvr interface
|
Displays the details of all MVR member interfaces, or a single requested MVR member interface.
|
show mvr members
|
Displays details of all the MVR members and number of MVR members in all active MVR groups on a particular VLAN or port.
|
show mvr source-ports
|
Displays all source ports that are members of an IP multicast group or those on the specified interface port.
|
clear mvr counters
|
Clears the join counters of all the MVR ports, source ports, receiver ports, or of a specified MVR interface port.
|
show mvr source ports
To display all source ports that are members of any IP multicast group or those on the specified interface port, use the show mvr source ports command in Privileged EXEC mode.
show mvr souce ports [type module/port]
Syntax Description
type
|
(Optional) Specifies the Interface type.
|
module/port
|
(Optional) Specifies the module or port number.
|
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
15.1(3)S
|
This command was introduced on the Cisco 7600 routers.
|
Examples
This example displays the show mvr source ports output:
Router# show mvr source ports GigabitEthernet 1/7
Joins: v1,v2,v3 counter shows total IGMP joins
v3 counter shows IGMP joins received with both MVR and non-MVR groups
Port VLAN Status Immediate Joins
---- ---- ------------- ---------- ---------- -----------
Gi1/7 202 INACTIVE/UP DISABLED 305336 0
Related Commands
Command
|
Description
|
mvr
|
Enables Multicast VLAN Registration (MVR) on the router.
|
mvr group
|
Configures an MVR group on the router.
|
mvr max-groups
|
Configures the MVR maximum number of groups on the router.
|
mvr querytime
|
Configures the MVR query response time.
|
mvr vlan
|
Configures the VLAN in which multicast data is received.
|
mvr type
|
Configures a switch port as an MVR receiver or source port.
|
mvr immediate
|
Enables the immediate leave feature of MVR on the port.
|
show mvr
|
Displays the MVR details.
|
show mvr groups
|
Displays the MVR group configuration.
|
show mvr interface
|
Displays the details of all MVR member interfaces, or a single requested MVR member interface.
|
show mvr members
|
Displays details of all the MVR members and number of MVR members in all active MVR groups on a particular VLAN or port.
|
show mvr receiver-ports
|
Displays all receiver ports that are members of an IP multicast group or those on the specified interface port.
|
clear mvr counters
|
Clears the join counters of all the MVR ports, source ports, receiver ports, or of a specified MVR interface port.
|
show network-clocks
To display the current configured and active network clock sources, use the show network-clocks command in privileged EXEC mode.
show network-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 modified to display BITS clock information for the 7600-ES+ITU-2TG and the 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 show network-clocks command, you can display the clocking configuration status.
On the Cisco 7600 series routers, this command applies to the following:
•
The clock source from the POS SPAs on the SIP-200 and the SIP-400.
•
The 24-Port Channelized T1/E1 ATM CEoP SPA and the 1-Port Channelized OC-3 STM1 ATM CEoP SPA on the SIP-400.
•
The 7600-ES+ITU-2TG and 7600-ES+ITU-4TG line cards.
Examples
The following is sample output from the show network-clocks command:
Router# show network-clocks
Priority 1 clock source: ATM3/0/0
Priority 2 clock source: System clock
Priority 3 clock source: System clock
Priority 4 clock source: System clock
Current clock source:ATM3/0/0, priority:1
The following is sample output from the show network-clocks command on the Cisco MC3810:
Router# show network-clocks
Priority 1 clock source(inactive config): T1 0
Priority 1 clock source(active config) : T1 0
T1 0 is clocking system bus for 9319 seconds.
Run Priority Queue: controller0
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 an additional sample output from the show network-clocks command:
Router# show network-clocks
Priority 1 clock source(inactive config) : T1 0
Priority 2 clock source(inactive config) : T1 1
Priority 1 clock source(active config) : T1 0
T1 0 is clocking system bus for 9319 seconds.
Run Priority Queue: controller0
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) that is 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 show network-clocks command for the 7600-ES+ITU-2TG or 7600-ES+ITU-4TG:
Router# show network-clocks
Active source = Slot 1 BITS 0
Active source backplane reference line = Primary Backplane Clock
Standby source backplane reference line = Secondary Backplane Clock
(Standby source not driving backplane clock currently)
All Network Clock Configuration
---------------------------------
Priority Clock Source State Reason
1 POS3/0/1 Valid but not present
Current operating mode is Revertive
Current OOR Switchover mode is Switchover
There are no slots disabled from participating in network clocking
-------------------------
Slot Port Signal Type/Mode Line Build-Out Select
1 0 T1 ESF DSX-1 (533 to 655 feet)
Related Commands
Command
|
Description
|
clock source
|
Specifies the interface clock source type.
|
network-clock (BITS)
|
Configures BITS port signaling types.
|
network-clock select
|
Selects a source of network clock.
|
network-clock-select (ATM)
|
Establishes the sources and priorities of the requisite clocking signals for an ATM-CES port adapter.
|
show platform hardware network-clocks
|
Displays network clocks for an ES+ line card.
|
show pagp
To display port-channel information, use the show pagp command in user EXEC or privileged EXEC mode.
show pagp [group-number] {counters | internal | neighbor | pgroup}
Syntax Description
group-number
|
(Optional) Channel-group number; valid values are a maximum of 64 values from 1 to 282.
|
counters
|
Displays the traffic information.
|
internal
|
Displays the internal information.
|
neighbor
|
Displays the neighbor information.
|
pgroup
|
Displays the active port channels.
|
Defaults
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
You can enter any show pagp command to display the active port-channel information. To display the nonactive information, enter the show pagp command with a group.
The port-channel number values from 257 to 282 are supported on the CSM and the FWSM only.
Examples
This example shows how to display information about the PAgP counters:
Router# show pagp counters
--------------------------------------
This example shows how to display internal PAgP information:
Router# show pagp 1 internal
Flags: S - Device is sending Slow hello. C - Device is in Consistent state.
A - Device is in Auto mode.
Timers: H - Hello timer is running. Q - Quit timer is running.
S - Switching timer is running. I - Interface timer is running.
Hello Partner PAgP Learning
Port Flags State Timers Interval Count Priority Method
Fa5/4 SC U6/S7 30s 1 128 Any
Fa5/5 SC U6/S7 30s 1 128 Any
This example shows how to display PAgP-neighbor information for all neighbors:
Router# show pagp neighbor
Flags: S - Device is sending Slow hello. C - Device is in Consistent state.
A - Device is in Auto mode. P - Device learns on physical port.
Channel group 1 neighbors
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Fa5/4 JAB031301 0050.0f10.230c 2/45 2s SAC 2D
Fa5/5 JAB031301 0050.0f10.230c 2/46 27s SAC 2D
Channel group 2 neighbors
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Fa5/6 JAB031301 0050.0f10.230c 2/47 10s SAC 2F
Fa5/7 JAB031301 0050.0f10.230c 2/48 11s SAC 2F
Channel group 1023 neighbors
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Channel group 1024 neighbors
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Related Commands
Command
|
Description
|
pagp learn-method
|
Learns the input interface of the incoming packets.
|
pagp port-priority
|
Selects a port in hot standby mode.
|
show pas caim
To show debug information about the data compression Advanced Interface Module (CAIM) daughter card, use the show pas caim command in user EXEC or privileged EXEC mode.
show pas caim {rings | dma | coprocessor | stats | cnxt_table | page_table} element-number
Syntax Description
rings element-number
|
Displays current content of the Direct Memory Access (DMA) ring buffer.
|
dma element-number
|
Displays registers of the Jupiter DMA controller.
|
coprocessor element-number
|
Displays registers of the Hifn 9711 compression coprocessor.
|
stats element-number
|
Displays statistics that describes operation of the data compression Advanced Interface Module (AIM).
|
cnxt_table element-number
|
Displays the context of the specific data compression AIM element.
|
page_table element-number
|
Displays the page table for each CAIM element.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)T
|
This command was introduced.
|
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 displays performance statistics that describe the operation of the CAIM. This command is primarily intended for engineering debug, but it can also be useful to Cisco support personnel and to Cisco customers in troubleshooting network problems. Table 11 lists the output values for this command.
Table 11 show pas caim Output Values and Descriptions
Value
|
Description
|
uncomp paks in
|
Number of packets containing uncompressed data input to the CAIM for compression.
|
comp paks out
|
Number of packets containing uncompressed data that were successfully compressed.
|
comp paks in
|
Number of packets containing compressed data input to the CAIM for compression.
|
uncomp paks out
|
Number of packets containing compressed data that were successfully decompressed.
|
uncomp bytes in / comp bytes out
|
Summarizes the compression performance of the CAIM. The "uncomp bytes in" statistic gives the total number of uncompressed bytes submitted to the CAIM for compression. The "Comp bytes out" statistic gives the resulting number of compressed bytes output by the CAIM. If one forms the ratio of "uncomp bytes in" to "comp bytes out", one obtains the average compression ratio achieved by the CAIM.
|
comp bytes in / uncomp bytes out
|
Summarizes the decompression performance of the CAIM. The "comp bytes in" statistic gives the total number of compressed bytes submitted to the CAIM for decompression. The "uncomp bytes out" statistic gives the resulting number of uncompressed bytes output by the CAIM. The average decompression ratio achieved can be computed as the ratio of "uncomp bytes out" to "comp bytes in".
Note that each packet submitted for compression or decompression has a small header at the front which is always clear data and hence never compressed nor decompressed. The "comp bytes in / uncomp bytes out" and "uncomp bytes in / comp bytes out" statistics do not include this header.
|
uncomp paks/sec in
|
A time average of the number of packets per second containing uncompressed data submitted as input to the CAIM for compression. It is computed as the ratio of the "uncomp paks in" statistic to the "seconds since last clear" statistic.
|
comp paks/sec out
|
A time average of the number of packets per second containing uncompressed data which were successfully compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" compressed by the CAIM. It is computed as the ratio of the "comp paks out" statistic to the "seconds since last clear" statistic.
|
comp paks/sec in
|
A time average of the number of packets per second containing compressed data submitted as input to the CAIM for decompression. It is computed as the ratio of the "comp paks in" statistic to the "seconds since last clear" statistic.
|
uncomp paks/sec out
|
A time average of the number of packets per second containing compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp paks out" statistic to the "seconds since last clear" statistic.
Note that the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics are averages over the entire time since the last "clear count" command was issued. This means that as time progresses, these statistics become averages over an ever larger time interval. As time progresses, these statistics become ever less sensitive to current prevailing conditions. Note also that the "uncomp paks in", "comp paks out", "comp paks in", and "uncomp paks out" statistics are 32-bit counters and can roll over from 0xffff ffff to 0. When they do so, the "uncomp paks/sec in", "comp paks/sec out", "comp paks/sec in", and "uncomp paks/sec out" statistics can be rendered meaningless. It is therefore recommend that one issue a "clear count" command before sampling these statistics.
|
uncomp bits/sec in
|
A time average of the number of bits per second of uncompressed data which were submitted to the CAIM for compression. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
|
comp bits/sec out
|
A time average of the number of bits per second of uncompressed data which were successfully compressed by the CAIM. It is computed as the ratio of the "comp bytes out" statistic, times 8, to the "seconds since last clear" statistic.
|
comp bits/sec in
|
A time average of the number of bits per second of compressed data which were submitted to the CAIM for decompression. It is computed as the ratio of the "comp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
|
uncomp bits/sec out
|
A time average of the number of bits per second of compressed data which were successfully decompressed by the CAIM. It is computed as the ratio of the "uncomp bytes in" statistic, times 8, to the "seconds since last clear" statistic.
Note again that these "bits/sec" statistics are time averages over the "seconds since last clear" statistics, and therefore become less and less sensitive to current conditions as time progresses. Also, these "bits/sec" statistics are computed from 32-bit counters, and when the counters roll over from the maximum 32-bit value to 0, the "bits/sec" statistics become inaccurate. It is again recommended that one issue the "clear count" command before sampling the "bits/sec" statistics.
|
The remaining statistics summarize operational state and error conditions encountered by the CAIM, and have the following interpretations:
|
holdq
|
Gives the number of packets occupying the "hold queue" of the CAIM. The hold queue is a holding area, or "overflow" area, for packets to be processed by the CAIM. Normally, the CAIM is fast enough that no overflow into the hold queue occurs, and so normally this statistic should show zero.
|
hw_enable
|
Flag indicating if the CAIM is disabled or not. Zero implies disabled; one implies enabled. The CAIM can become disabled if certain fatal hardware error conditions are detected. It can be reenabled by issuing the clear aim element-number command.
|
src_limited
|
Flag indicating if the CAIM is in "source limited" mode. In source limited mode, the CAIM can only process a single command at a time. In non source limited mode, the CAIM can process several commands at a time using a pipeline built into the 9711 coprocessor. Note that the normal mode of operation is "non-source limited", and there is no command to place the CAIM in "source limited" mode. Hence, this statistic should always read zero.
|
num cnxts
|
Gives the number of "contexts" which are currently open on the CAIM. Each interface configured for compression opens two contexts, one for each direction of data transfer.
|
no data
|
Counts the number of times in which the CAIM performed either a compress or decompression operation, and the output data length was reported with a length of zero. In normal operation, this statistic should always read zero. A nonzero value is an indication of a malfunctioning CAIM.
|
drops
|
Counts the total number of times in which the CAIM was forced to drop a packet it was asked to compress or decompress. This can happen for a number of reasons, and the remaining statistics summarize these reasons. This statistic indicates that the CAIM is being overloaded with requests for compression/decompression.
|
nobuffers
|
Counts the total number of times the CAIM needed to allocate memory for buffers but could not obtain memory. The CAIM allocates memory for buffers for holding the results of compression or decompression operations. In normal operation, there is plenty of memory available for holding CAIM results. This statistic, if nonzero, indicates that there is a significant backup in memory, or perhaps a memory leak.
|
enc adj errs
|
Each packet compressed or decompressed involves an adjustment of the encapsulation of the packet between the LZS-DCP, FRF9, or MPPC encapsulation used to transport compressed packets to the standard encapsulation used to transport clear data. This statistic counts the number of times this encapsulation adjustment failed. In normal operation, this statistic should be zero. A nonzero value indicates that we are short in a specific memory resource referred to as "paktypes", and that packets are being dropped because of this shortage.
|
fallbacks
|
Number of times the data compression AIM card could not use its pre-allocated buffers to store compression results and had to "fallback" to using a common buffer pool.
|
no replace
|
Each time a compression or decompression operation is completed and the resultant data fill up a buffer, the CAIM software allocates a new buffer to replace the buffer filled. If no buffers are available, then the packet involved in this operation is dropped and the old buffer reused. This statistic thus represents the number of times such an allocation failure occurred. In normal operation there is plenty of memory available for these buffers. A nonzero value for this statistic is thus a serious indication of a memory leak or other backup in buffer usage somewhere in the system.
|
num seq errs
|
This statistic is incremented when the CAIM produces results in a different order than that in which the requests were submitted. Packets involved in such errors are dropped. A nonzero value in this statistic indicates a serious malfunction in the CAIM.
|
num desc errs
|
Incremented when the CAIM reports error in a compression or decompression operation. Such errors are most likely bus errors, and they indicate a serious malfunction in the CAIM.
|
cmds complete
|
Reports the number of compression/decompression commands completed. This statistic should steadily increase in normal operation (assuming that the CAIM is continuously being asked to perform compression or decompression). If this statistic is not steadily increasing or decreasing when a steady stream of compression/decompression is expected, this is an indication of a malfunctioning CAIM.
|
bad reqs
|
Reports the number of compression/decompression requests that the CAIM software determined it could not possibly handle. This occurs only if a severely scattered packet (with more than 64 "particles", or separate buffers of data) is handed to the CAIM to compress or decompress. This statistic should not increment during normal operation. A nonzero value indicates a software bug.
|
dead cntxts
|
Number of times a packet was successfully compressed or decompressed, only to find that the software "context", or stream sourcing the packet, was no longer around. In such a case the packet is dropped. This statistic can be incremented at times when a serial interface is administratively disabled. If the timing is right, the CAIM may be right in the middle of operating on a packet from that interface when the disable takes effect. When the CAIM operation completes, it finds that the interface has been disabled and all "compression contexts" pertaining to that interface have been deleted. Another situation in which this can occur is when a Frame Relay DLC goes down. This is a normal and tolerable. If this statistic is incrementing when no such situations exist, it is an indication of a software bug.
|
no paks
|
If a packet to be compressed or decompressed overflows into the hold queue, then it must undergo an operation called "reparenting". This involves the allocation of a "paktype" structure for the packet. If no paktype structures are available, then the packet is dropped and this statistic is incremented. A nonzero value of this statistic indicates that the CAIM is being overtaxed, that is, it is being asked to compress/decompress at a rate exceeding its capabilities.
|
enq errors
|
Closely related to the "no paks" statistic. The hold queue for the CAIM is limited in length, and if the hold queue grows to this length, no further packets may be placed on it. A nonzero value of this statistic therefore also indicates that the CAIM is being overtaxed.
|
rx pkt drops
|
Contains the total number of packets dropped because of "no paks" or "enq errors", which were destined to be decompressed.
|
tx pkt drops
|
Contains the total number of packets dropped because of "no paks" or "enq errors", which were destined to be compressed
|
dequeues
|
Indicates the total number of packets which were removed from the CAIM hold queue when the CAIM became available for servicing its hold queue.
|
requeues
|
Indicates the total number of packets that were removed from the hold queue, only to find that the necessary CAIM resources were not available (it is not possible to determine whether CAIM resources are available until the packet is dequeued). Such packets are requeued onto the hold queue, with order in the queue preserved.
|
drops disabled
|
Indicates the total number of packets which were submitted for compression or decompression, but that were dropped because the CAIM was disabled.
|
clears
|
Indicates the number of times the CAIM was reset using the clear aim element-number command.
|
# ints
|
Indicates the number of interrupts serviced by the CAIM software. This statistic should steadily increase (assuming that the CAIM workload is steady). If this statistic is not incremented when expected, it indicates a severe CAIM malfunction.
|
# purges
|
Indicates the total number of times the compression history for a session had to be purged. This statistic is incremented a couple of times at startup. Thereafter, any increase in this statistic is an indication that the other side of the serial link detected bad data or gaps in the compressed packets being passed to it, and hence signalled a request to purge compression history in order to get back in synchronization. This can indicate that the CAIM is being overtaxed or that the serial interface is overtaxed and being forced to drop output packets.
|
no cnxts
|
Indicates the total number of times a request was issued to open a context, but the CAIM could not support any more contexts. Recall that two contexts are required for each interface configured for compression.
|
bad algos
|
Indicates the total number of times a request was issued to open a context for a compression algorithm not supported by the CAIM. Recall that the CAIM supports the LZS and MPPC algorithms only.
|
no crams
|
Indicates the total number of times a request was issued to open a context but there was insufficient compression DRAM to open another context. The CAIM software is set up to run out of contexts before it runs out of compression DRAM, so this statistic should always be zero.
|
bad paks
|
Indicates the total number of times a packet was submitted for compression or decompression to the CAIM, but the packet had an invalid size.
|
# opens
|
Indicates the total number of times a context was opened.
|
# closes
|
Indicates the total number of times a context was closed.
|
# hangs
|
Indicates the total number of times a CAIM appeared hung up, necessitating a clear of the CAIM.
|
Examples
The show pas caim rings element-number command displays the current state of the DMA ring buffers maintained by the CAIM software. These rings feed the CAIM with data and commands. It is intended for an engineering debug of the compression AIM. It produces the following output:
Router# show pas caim rings 0
CAIM Command Ring: 0x01A2BC00 Stack: 0x01A2BE40 Shadow: 0x80F88BAC
Head: 0021 Tail: 0021 Count: 0000
CAIM Source Ring: 0x01A2C900 Shadow: 0x80F88BAC
Head: 0021 Tail: 0021 Num: 0000
CAIM Results Ring: 0x01A2C280 Stack: 0x01A2C4C0
CAIM Dest Ring: 0x01A2CB40 Shadow: 0x80F892D8 Head=021 Tail=000
Desc: 0x01A2CBE8 flags: 0x8000060C dptr: 0x019E7EB8 part: 0x80F84BE0
Desc: 0x01A2CBF0 flags: 0x8000060C dptr: 0x019FC63C part: 0x80F85240
Table 12 describes the significant fields shown in the display.
Table 12 show pas caim rings Field Descriptions
Field
|
Description
|
CAIM Command Ring
|
Feeds commands to the CAIM.
|
command ring address
|
Address of the command ring.
|
Command Ring Stack
|
Ring that feeds additional commands to the CAIM.
|
command ring stack address
|
Address of the command ring stack.
|
Command Ring Shadow
|
Software ring that stores additional information about each command.
|
command ring shadow address
|
Address of the command ring shadow.
|
Command Ring Head
|
Index into the Source Ring, specifying where the next entry will be extracted from.
|
Command Ring Tail
|
Index into the Source Ring, specifying where the next entry will be inserted.
|
CAIM Source Ring
|
Feeds information about input data to the CAIM.
|
source ring address
|
Address of the source ring.
|
Source Ring Shadow
|
Ring that contains additional information about each source buffer.
|
source ring shadow address
|
Address of the source ring shadow.
|
Source Ring Head
|
Specifies where the next entry will be extracted from.
|
Source Ring Tail
|
Specifies where the next entry will be inserted.
|
CAIM Results Ring
|
Receives information about each CAIM command as it is completed.
|
results ring address
|
Address of the results ring.
|
Results Ring Stack
|
Ring that receives additional information about each completed command.
|
results ring stack address
|
Address of the results ring stack.
|
Results Ring Head
|
Specifies where the next entry will be extracted from.
|
Results Ring Tail
|
Specifies where the next entry will be inserted.
|
CAIM Dest Ring
|
Holds information about the buffers available to the CAIM for output data.
|
dest ring address
|
Address of the dest ring.
|
Dest Ring Shadow
|
Ring that holds additional information about each output buffer.
|
dest ring shadow address
|
Address of the dest ring shadow.
|
Dest Ring Head
|
Index into the Source Ring, specifying where the next entry will be extracted from.
|
Dest Ring Tail
|
Index into the Source Ring, specifying where the next entry will be inserted.
|
The remaining fields describe each output data buffer.
|
dest
|
Address of a so-called descriptor, used by the Jupiter DMA engine.
|
flags
|
Contains flags describing attributes of the buffer.
|
dptr
|
Displays the actual address of the output buffer.
|
part
|
Displays the address of the corresponding particle type structure, a software-defined structure that describes a buffer when it is a component of a network data buffer.
|
The show pas caim dma element-number command displays the registers of the Jupiter DMA Controller. These registers control the operation of the Jupiter DMA Controller. This command is intended for Engineering debug of the CAIM. You can find detailed descriptions of the various fields in the Jupiter DMA Controller specification. It produces the following output:
Router# show pas caim dma 0
Jupiter DMA Controller Registers: (0x40200000
Cmd Ring: 0x01A2BCA8 Src Ring: 0x01A2C9A8
Res Ring: 0x01A2C328 Dst Ring: 0x01A2CBE8
Status/Cntl: present: 0x80808084 last int: 0x80808084
Inten: 0x10100000 config: 0x00100003
The show pas caim compressor element-number command displays the registers of the Hifn 9711 compression coprocessor. These registers control the operation of the Hifn 9711 part. This command is intended for engineering to debug the CAIM. Detailed descriptions of the various fields may be found in the Hifn 9711 data book. It produces the following output:
Router# show pas caim compressor 0
Hifn9711 Data Compression Coprocessor Registers (0x40201000):
Config: 0x000051D4 Inten: 0x00000E00
Status: 0x00004000 FIFO status: 0x00004000
Table 13 describes the fields shown in the preceding display.
Table 13 show pas caim compressor Field Descriptions
Field
|
Description
|
Hifn9711 Data Compression Coprocessor Registers
|
Controls the operation of the Hifn 9711 part.
|
registers address
|
Address of the registers in the address space of the processor.
|
Config
|
Displays the current contents of the 9711 configuration register.
|
Inten
|
Displays the contents of the 9711 interrupt enable register.
|
Status
|
Displays the contents of the 9711 status register.
|
FIFO status
|
Contents of the 9711 FIFO Status register.
|
FIFO config
|
Contents of the 9711 FIFO Config register.
|
The show pas caim cnxt_table element-number command displays the context table for the specified CAIM element. The context table is a table of information concerning each compression context. It produces the following output:
Router# show pas caim cnxt_table 0
Context: 0x8104F320 Type: Compr Algo: Stac
Hdrlen: 0006 History: 0x0000
Callback: 0x8011D68C Shutdown: x8011EBE4 Purge: N
Comp_db: 0x81034BC0 idb: 0x81038084 ds: 0x8104E514
Context: 0x8104F340 Type: Decomp Algo: Stac
Hdrlen: 0002 History: 0x0000
Callback: 0x8011E700 Shutdown: x8011EBE4 Purge: N
Comp_db: 0x81034BC0 idb: 0x81038084 ds: 0x8104E514
Table 14 describes the fields shown in the preceding display.
Table 14 show pas caim cnxt_table Fields Descriptions
Field
|
Description
|
Context
|
Numeric internal reference for the compression context.
|
Type
|
Gives the type of context:
• Compr—compression context
• Decomp—decompression context
|
Algo
|
Gives the compression algorithm used:
• Stac
• Mppc
|
Hdrlen
|
Gives the number of bytes in the compression header for each compressed packet.
|
History
|
Gives the 16-KB page number in compression RAM for the context.
|
Callback
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Shutdown
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Comp_db
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
idb
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
idb
|
Gives an internal numeric reference for a control structures or procedure to facilitate debugging.
|
Purge
|
Indicates whether the compression context has been flagged to have its history purged.
|
The show pas caim page_table element-number command displays the page table for the selected CAIM element. The page table is a table of entries describing each page in compression RAM. It produces the following output:
Router# show pas caim page_table 0
Page 0x0000 Comp cnxt: 8104F320 Decmp cnxt: 8104F340 Algo: Stac
Table 15 describes the fields shown in the preceding display.
Table 15 show pas caim page_table Field Descriptions
Field
|
Description
|
Page
|
16 KB page number of the page.
|
Comp cnxt
|
Contains an internal numeric reference to the context structures using this page.
|
Decmp cnxt
|
Contains an internal numeric reference to the context structures using this page.
|
Algo
|
Gives the compression algorithm used:
• Stac
• Mppc
|
The following example shows statistics of an active data compression AIM session:
Router# show pas caim stats 0
ds:0x80F56A44 idb:0x80F50DB8
422074 uncomp paks in --> 422076 comp paks out
422071 comp paks in --> 422075 uncomp paks out
633912308 uncomp bytes in--> 22791798 comp bytes out
27433911 comp bytes in --> 633911762 uncomp bytes out
974 uncomp paks/sec in--> 974 comp paks/sec out
974 comp paks/sec in --> 974 uncomp paks/sec out
11739116 uncomp bits/sec in--> 422070 comp bits/sec out
508035 comp bits/sec in --> 11739106 uncomp bits/sec out
433 seconds since last clear
holdq: 0 hw_enable: 1 src_limited: 0 num cnxts: 4
no data: 0 drops: 0 nobuffers: 0 enc adj errs: 0 fallbacks: 0
no Replace: 0 num seq errs: 0 num desc errs: 0 cmds complete: 844151
Bad reqs: 0 Dead cnxts: 0 No Paks: 0 enq errs: 0
rx pkt drops: 0 tx pkt drops: 0 dequeues: 0 requeues: 0
drops disabled: 0 clears: 0 ints: 844314 purges: 0
no cnxts: 0 bad algos: 0 no crams: 0 bad paks: 0
# opens: 0 # closes: 0 # hangs: 0
Related Commands
Command
|
Description
|
show compress
|
Displays compression statistics.
|
show pas eswitch address
To display the Layer 2 learned addresses for an interface, use the show pas eswitch address command in user EXEC or privileged EXEC mode.
show pas eswitch address [ethernet | fastethernet] [slot/port]
Syntax Description
ethernet | fastethernet
|
(Optional) Type of interface.
|
slot
|
(Optional) Slot number of the interface.
|
port
|
(Optional) Interface number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2P
|
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.
|
Examples
The following sample output shows that the first PA-12E/2FE interface (listed below as port 0) in port adapter slot 3 has learned the Layer 2 address 00e0.f7a4.5100 for bridge group 30 (listed below as BG 30):
Router# show pas eswitch address fastethernet 3/0
U 00e0.f7a4.5100, AgeTs 56273 s, BG 30 (vLAN 0), Port 0
show pas 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 show pas i82543 interface command in privileged EXEC mode.
show pas i82543 interface {fastethernet | gigabitethernet} slot/port [multicast-table |
receive-address | statistics]
Syntax Description
fastethernet
|
Displays i82543-specific information for Fast Ethernet interfaces.
|
gigabitethernet
|
Displays i82543-specific information for Gigabit Ethernet interfaces.
|
slot
|
Slot number.
|
/port
|
Port number. The slash mark is required between the slot argument and the port argument.
|
multicast-table
|
(Optional) Displays i82543-specific multicast address table information.
Note In Cisco IOS Release 12.2 S, this keyword is MTA.
|
receive-address
|
(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.
|
Use the show pas i82543 interface command with the statistics keyword to determine what types of packets are being processed. Similar statistical information is displayed by the show controllers fastethernet and show controllers gigabitethernet 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.
Router# show pas i82543 interface fastethernet 6/0 multicast-table
Multicast Table Entry #0 = 0x10000
Multicast Table Entry #1 = 0x1
Multicast Table Entry #84 = 0x8000
The following sample output shows the contents of the Receive Address High (RAH) and Receive Address Low (RAL) registers on the i82543 processor.
Router# show pas i82543 interface fastethernet 6/0 receive-address
#1 RAH 0x8000A8FC RAL 0x67B60900
#3 RAH 0x0003FFFF RAL 0xFF45F75B
#5 RAH 0x0003FFFF RAL 0xCBEE539A
#7 RAH 0x0003FFFF RAL 0x5ABDADEB
#9 RAH 0x0003FFFF RAL 0x365B5ACF
#11 RAH 0x0003FFFF RAL 0xB2D9B0CE
#13 RAH 0x0003FFFF RAL 0x12A91CF6
#15 RAH 0x0003FFFF RAL 0xEF4A3125
#17 RAH 0x0003FFFF RAL 0x1A07EB7D
#19 RAH 0x0003FFFF RAL 0xFF9B6EF8
#21 RAH 0x0003FFFF RAL 0xB7C2AFC9
#23 RAH 0x0003FFFF RAL 0x14F4FB0A
#25 RAH 0x0003FFFF RAL 0xC60D6706
#27 RAH 0x0003FFFF RAL 0x5E9DE230
#29 RAH 0x0003FFFF RAL 0x5FEF9FBE
#31 RAH 0x0003FFFF RAL 0xBBCCC57E
The following sample output shows packet statistics of the i82543 processor.
Router# show pas i82543 interface fastethernet 6/0 statistics
i82543 (Livengood) Statistics
CRC error 0 Symbol error 0
Missed Packets 0 Single Collision 0
Excessive Coll 0 Multiple Coll 0
Sequence Error 0 XON RX 0
XOFF TX 0 FC RX Unsupport 0
Packet RX (64) 0 Packet RX (127) 0
Packet RX (255) 0 Packet RX (511) 0
Packet RX (1023) 0 Packet RX (1522) 0
Good Packet RX 348 Broadcast RX 0
Multicast RX 319 Good Packet TX 0
Good Octets RX.H 0 Good Octets RX.L 0
Good Octets TX.H 0 Good Octets TX.L 0
RX No Buff 0 RX Undersize 0
RX Fragment 0 RX Oversize 0
RX Octets High 0 RX Octets Low 0
TX Octets High 0 TX Octets Low 0
TX Packet 0 RX Packet 348
TX Broadcast 0 TX Multicast 0
Packet TX (64) 0 Packet TX (127) 0
Packet TX (255) 0 Packet TX (511) 0
Packet TX (1023) 0 Packet TX (1522) 0
TX Underruns 0 TX No CRS 0
RX Error Count 0 RX DMA Underruns 0
TCP Segmentation 0 TCP Seg Failed 0
Table 16 describes significant fields shown in the display.
Table 16 show pas i82543 interface statistics Field Descriptions
Field
|
Description
|
CRC error
|
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
|
show compress
|
Displays compression statistics.
|
show controllers fastethernet
|
Displays information about Fast Ethernet controllers.
|
show controllers gigabitethernet
|
Displays information about Gigabit Ethernet controllers.
|
show interfaces
|
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 show pas isa controller EXEC command.
show pas isa controller
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
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.
|
Examples
The following is sample output from the show pas isa controller command:
Router# show pas isa controller
Addresses of Rings and instance structure:
TX: 0x4B0E97C0 TX Shadow:0x62060E00
RX: 0x4B0EB840 RX Pool:0x4B0EBC80 RX Pool Shadow:0x62068E58
TX: 0x4B0EA800 TX Shadow:0x62066E2C
RX: 0x4B0EC0C0, RX Shadow:0x62069284
Instance Structure address:0x620603D8
Firmware write head/tail offset:0x4B0EC900
Firmware read head/tail offset:0x3EA00000
Related Commands
Command
|
Description
|
show pas isa interface
|
Displays interface status information that is specific to the VPN accelerator card.
|
show pas isa interface
To display interface information that is specific to the Virtual Private Network (VPN) accelerator card when an Integrated Services Adapter (ISA) is installed, use the show pas isa interface command in privileged EXEC mode.
show pas isa interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
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.
|
Examples
The following is sample output from the show pas isa interface command:
Router# show pas isa interface
Statistics of packets and bytes through this interface:
2876894 packets in 2910021 packets out
420 paks/sec in 415 paks/sec out
2327 Kbits/sec in 2408 Kbits/sec out
632 commands out 632 commands acknowledged
low_pri_pkts_sent 1911 low_pri_pkts_rcvd: 1911
invalid_sa: 260 invalid_flow: 33127
invalid_dh: 0 ah_seq_failure: 0
ah_spi_failure: 0 esp_auth_failure: 0
esp_seq_failure: 0 esp_spi_failure: 0
esp_protocol_absent: 0 ah_protocol_absent: 0
bad_key_group: 0 no_shared_secret: 0
no_skeyids: 0 pad_size_error: 0
cmd_ring_full: 0 bulk_ring_full: 990
bad_peer_pub_len: 0 authentication_failure: 0
fallback: 1606642 no_particle: 0
6922 seconds since last clear of counters
Table 17 describes the significant fields shown in the display.
Table 17 show pas isa interface Field Descriptions
Field
|
Description
|
packets in/out
|
Number of data packets received from, or sent to, the Integrated Service Adapter (ISA).
|
paks/sec in/out
|
Number of packets received in, or sent out, with the total number of seconds that the ISA is active.
|
Kbits/sec in/out
|
Number of kilobits (Kbits) received in, or sent out, with the total number of seconds that the ISA is active.
|
commands out
|
Number of commands going to the ISA. Examples of commands include setting up encryption sessions and retrieving statistics or status from the ISA.
|
commands acknowledged
|
Number of commands returning from the ISA. Examples of commands include setting up encryption sessions and retrieving statistics or status from the ISA.
|
low_pri_pkts_sent
|
This is a summary counter for number of Internet Key Exchange (IKE) and IPSec commands submitted to ISA.
|
low_pri_pkts_rcvd
|
This is a summary counter for number of IKE & IPSEC command responses received from ISA.
|
invalid_sa
|
Reference to an unusable security association key pair.
|
invalid_flow
|
An invalid packet using an IPSec key is received for encryption or decryption.
Example: session has expired.
|
invalid_dh
|
Reference to an unusable Diffie-Hellman( DH) key pair.
|
ah_seq_failure
|
Unacceptably late Authentication Header (AH) header received.
|
ah_spi_failure
|
SPI specified in the AH header does not match the SPI associated with the IPSec AH key.
|
esp_auth_failure
|
Number of ESP packets received with authentication failures.
|
esp_seq_failure
|
Unacceptably late ESP packet received.
|
esp_spi_failure
|
SPI specified in the ESP header does not match the SPI associated with the IPSec ESP key.
|
esp_protocol_absent
|
Packet is missing expected ESP header.
|
ah_protocol_absent
|
Packet is missing expected AH header.
|
bad_key_group
|
Unsupported key group requested during a Diffie-Hellman generation.
|
no_shared_secret
|
Attempting to use a Diffie-Hellman shared secret that is not generated.
|
no_skeyids
|
Attempting to use a shared secret that is not generated.
|
pad_size_error
|
The length of the ESP padding is greater than the length of the entire packet.
|
cmd_ring_full
|
New IKE setup messages are not queued for processing until the previous queued requests are processed.
|
bulk_ring_full
|
New packets requiring IPSec functionality are not queued to the ISA until the ISA completes the processing of existing requests.
|
bad_peer_pub_len
|
Length of peer's DH public key does not match the length specified for the negotiated DH key group.
|
authentication_failure
|
Authentication failed.
|
fallback
|
The number of instances when the driver is successful in getting a replacement buffer from the global pool.
|
no_particle
|
The number of instances when the driver was unable to get a replacement buffer from the driver pool and the global (fallback) pool.
|
Related Commands
Command
|
Description
|
show pas isa controller
|
Displays controller status information that is specific to the VPN accelerator card.
|
show pas vam controller
To display controller information that is specific to the VPN Acceleration Module (VAM), use the show pas vam controller command in privileged EXEC mode.
show pas vam controller
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(9)E
|
This command was introduced.
|
12.2(9)YE
|
This command was integrated into Cisco IOS Release 12.2(9)YE.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Examples
The following is sample output from the show pas vam controller command:
Router# show pas vam controller
Addresses of Rings and instance structure:
OMQ=0xF2CB2E0, OMQ Shadow = 0x630E6638, {1, 1, 0, 256}
PKQ=0xF2CF320, PKQ Shadow = 0x630EBE64, {232, 232, 0, 256}
ERQ=0xF2D3360, ERQ Shadow = 0x630F1690, {0, 0, 0, 256}
TX: 0x0F2D73A0 TX Shadow:0x630F6EBC, {6, 6, queued=0}
RX: 0x7F2D93E0 {13, 0, 256}
RX Pool:0x7F2DA420 RX Pool Shadow:0x630FCAE8, {6, 0, 255}
Instance Structure address:0x630E5898
mini-omq=0xF2DB460, shdw=0x63102714
Group0=0x3D800000, Group1=0x3D801000
Heartbeat info:<Addr, Value> = <0xF2DB520, 0x2A55A>
Running default HSP (addr=0x629D36AC, size=294268)
Related Commands
Command
|
Description
|
show pas vam interface
|
Displays interface status information specific to the VPN accelerator module.
|
show pas vam interface
To display interface information that is specific to the VPN Acceleration Module (VAM), use the show pas vam interface command in privileged EXEC mode.
show pas vam interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(9)E
|
This command was introduced.
|
12.2(9)YE
|
This command was integrated into Cisco IOS Release 12.2(9)YE.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
Enter the show pas vam interface command to see if the VAM is currently processing crypto packets.
Examples
The following is sample output from the show pas vam interface command:
Router# show pas vam interface
ds: 0x621CE0D8 idb:0x621C28DC
Statistics of packets and bytes that through this interface:
1110 packets in 1110 packets out
123387 bytes in 100979 bytes out
0 paks/sec in 0 paks/sec out
0 Kbits/sec in 0 Kbits/sec out
3507 commands out 3507 commands acknowledged
ppq_full_err : 0 ppq_rx_err : 0
cmdq_full_err : 0 cmdq_rx_err : 0
no_buffer : 0 fallback : 0
dst_overflow : 0 nr_overflow : 0
sess_expired : 0 pkt_fragmented : 0
out_of_mem : 0 access_denied : 0
invalid_fc : 0 invalid_param : 0
invalid_handle : 0 output_overrun : 0
input_underrun : 0 input_overrun : 0
key_invalid : 0 packet_invalid : 0
decrypt_failed : 0 verify_failed : 0
attr_invalid : 0 attr_val_invalid : 0
attr_missing : 0 obj_not_wrap : 0
bad_imp_hash : 0 cant_fragment : 0
out_of_handles : 0 compr_cancelled : 0
rng_st_fail : 0 other_errors : 0
3420 seconds since last clear of counters
Table 18 describes the significant fields shown in the display.
Table 18 show pas vam interface Field Descriptions
Field
|
Description
|
packets in/out
|
Number of data packets received from, or sent to, the VAM.
|
bytes in/out
|
Number of data bytes received from, or sent to, the VAM.
|
paks/sec in/out
|
Number of packets received in, or sent out, with the total number of seconds that the VAM is active.
|
Kbits/sec in/out
|
Number of kilobits (Kbits) received in, or sent out, with the total number of seconds that the VAM is active.
|
commands out
|
Number of commands going to the VAM. Examples of commands include setting up encryption sessions and retrieving statistics or status from the VAM.
|
commands acknowledged
|
Number of commands returning from the VAM. Examples of commands include setting up encryption sessions and retrieving statistics or status from the VAM.
|
ppq_full_err
|
Number of packets dropped because of a lack of space in the packet processing queues for the VAM. This usually means that input traffic has reached VAM maximum throughput possible.
|
ppq_rx_err
|
Summary counter for all errors related to packet processing.
|
cmdq_full_err
|
Number of commands dropped because of a lack of space in the command processing queues for the VAM. This error indicates that the input tunnel setup rate has reached the VAM maximum setup rate. The Internet Key Exchange (IKE) process retries the tunnel creation and deletion when commands are dropped by VAM.
|
cmdq_rx_err
|
Summary counter for all errors related to command processing (for example, IKE, or IPSec session creation or deletion).
|
no_buffer
|
Errors related to the VAM running out of buffers. May occur with large packets. Although VAM buffers cannot be tuned, try tuning buffers for other interfaces.
|
fallback
|
Internal VAM buffer pool is completely used up and VAM has to fallback to global buffer pool. This may cause minor performance impact, however, packets are still processed so this error can be ignored.
|
dst_overflow
|
Counter that is incremented when the VAM has completed an operation, but there is no available space into which to place the result.
|
nr_overflow
|
Counter that is incremented when the VAM has completed an operation, but there is no available space into which to place the result.
|
sess_expired
|
Counter that is incremented if the session used to encrypt or decrypt the packet has expired because of time or space limit.
|
pkt_fragmented
|
Counter that is incremented when the input packet has to be fragmented after encryption. This counter should always be 0 as fragmentation by VAM is disabled.
|
out_of_mem
|
Counter that is incremented when the VAM runs out of memory.
|
access_denied
|
Counter that is incremented when the VAM is requested to perform an operation on an object that can not be modified.
|
invalid_fc
|
Counter that is incremented when the VAM has received a request that is illegal for the specified object type.
|
invalid_param
|
Counter that is incremented when the VAM has received invalid parameters within a command.
|
invalid_handle
|
Counter that is incremented when the VAM receives a request for an operation to be performed on an object that does not exist.
|
output_overrun
|
Counter that is incremented when the space allocated for a response is not large enough to hold the result posted by the VAM.
|
input_underrun
|
Counter that is incremented when the VAM receives a packet for which it finds a premature end to the data, for example, a truncated packet.
|
input_overrun
|
Counter that is incremented when the VAM receives a buffer that is too large for the requested operation.
|
key_invalid
|
Counter that is incremented when the VAM receives a request for an operation on a key where the key is invalid or of the wrong type.
|
packet_invalid
|
Counter that is incremented when the VAM receives a packet whose body is badly formed.
|
decrypt_failed
|
Counter that is incremented when the VAM receives a packet that cannot be decrypted because the decrypted data was not properly formatted (for example, padding is wrong).
|
verify_failed
|
Counter that is incremented when the VAM receives a packet which could not be verified because the verification of a signature or authentication value failed.
|
attr_invalid
|
Counter that is incremented when the VAM receives a packet which specifies an attribute that is not correct for the specified object or operation.
|
attr_val_invalid
|
Counter that is incremented when the VAM encounters errors during packet or command processing. The packets or commands are dropped in such cases.
|
attr_missing
|
Counter that is incremented when the VAM receives an operation request for which the value of a required attribute is missing.
|
obj_not_wrap
|
Counter that is incremented when the VAM receives an operation request to retrieve an object that is hidden or unavailable for export beyond the FIPS boundary of the VPN Module.
|
bad_imp_hash
|
Counter that is incremented when the VAM sees a hash miscompare on unwrap.
|
cant_fragment
|
Counter that is incremented when the VAM determines a need to fragment a packet, but cannot fragment because the "don't fragment" bit is set. This counter should always be zero because the fragmentation on the VAM is disabled.
|
out_of_handles
|
Counter that is incremented when the VAM has run out of available space for objects of the requested type.
|
comp_cancelled
|
Due to the operation of the compression algorithm, some data patterns cannot be compressed. Usually data that has already been compressed or data that does not have a sufficient number of repetitive patterns cannot be compressed and a compress operation would actually result in expansion of the data.
There are certain known data patterns which do not compress. In these cases, the compression engine cancels the compression of the data and returns the original, uncompressed data without an IPPCP header.
These counters are useful to determine if the content of the traffic on the network is actually benefiting from compression. If a large percentage of the network traffic is already compressed files, these counters may indicate that compression on these streams are not improving the performance of the network.
|
rng_st_fail
|
Counter that is incremented when the VAM detects a Random Number Generator self test failure.
|
pkt_replay_err
|
Counter that is incremented when a replay error is detected by the VAM.
|
other_errors
|
Counter that is incremented when the VAM encounters a packet or command error that is not listed in other error categories. An example could be if the packet IP header checksum is incorrect.
|
Related Commands
Command
|
Description
|
show pas vam controller
|
Displays controller status information that is specific to the VPN accelerator module.
|
show pas y88e8k interface
To display the y88e8k Port Adaptor Information (pas) message details of a Gigabit Ethernet interface, use the show pas y88e8k interface command in User EXEC or privileged EXEC mode.
show pas y88e8k interface type number{registers | rx_ring | statistics | tx_ring}
Syntax Description
type
|
(Optional) Displays the interface type.
|
number
|
(Optional) Displays the interface number.
|
registers
|
Displays register values.
|
rx-ring
|
Displays the receive ring entries of the interface.
|
statistics
|
Displays the y88e8k chip statistics values.
|
tx-ring
|
Displays the transmit ring entries of the interface.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.4(22)T
|
This command was introduced in a release earlier than Cisco IOS Release 12.4(22)T.
|
Examples
The following is sample output from the show pas y88e8k interface command:
Router# show pas y88e8k interface gigabit ethernet 1/0 rx-ring
ring size = 128, particle size = 2048
ring head = 0, tail = 127
rxr next_desc_addr buf_ctrl buf_addr_lo frame_sw rxr_shadow data_start
data_bytes
0 0x642AE918 0x2DD9F020 0xC8550800 0x0DDA3180 0x00000000 0x64525440 0x2DDA3180 0
1 0x642AE938 0x2DD9F040 0xC8550800 0x0DDA3A00 0x00000000 0x64525480 0x2DDA3A00 0
2 0x642AE958 0x2DD9F060 0xC8550800 0x0DDA4280 0x00000000 0x645254C0 0x2DDA4280 0
3 0x642AE978 0x2DD9F080 0xC8550800 0x0DDA4B00 0x00000000 0x64525500 0x2DDA4B00 0
4 0x642AE998 0x2DD9F0A0 0xC8550800 0x0DDA5380 0x00000000 0x64525540 0x2DDA5380 0
5 0x642AE9B8 0x2DD9F0C0 0xC8550800 0x0DDA5C00 0x00000000 0x64525580 0x2DDA5C00 0
6 0x642AE9D8 0x2DD9F0E0 0xC8550800 0x0DDA6480 0x00000000 0x645255C0 0x2DDA6480 0
7 0x642AE9F8 0x2DD9F100 0xC8550800 0x0DDA6D00 0x00000000 0x64525600 0x2DDA6D00 0
8 0x642AEA18 0x2DD9F120 0xC8550800 0x0DDA7580 0x00000000 0x64525640 0x2DDA7580 0
9 0x642AEA38 0x2DD9F140 0xC8550800 0x0DDA7E00 0x00000000 0x64525680 0x2DDA7E00 0
10 0x642AEA58 0x2DD9F160 0xC8550800 0x0DDA8680 0x00000000 0x645256C0 0x2DDA8680 0
11 0x642AEA78 0x2DD9F180 0xC8550800 0x0DDA8F00 0x00000000 0x64525700 0x2DDA8F00 0
12 0x642AEA98 0x2DD9F1A0 0xC8550800 0x0DDA9780 0x00000000 0x64525740 0x2DDA9780 0
13 0x642AEAB8 0x2DD9F1C0 0xC8550800 0x0DDAA000 0x00000000 0x64525780 0x2DDAA000 0
127 0x642AF8F8 0x2DD9F000 0xC8550800 0x0DDE6900 0x00000000 0x64527400 0x2DDE6900
0
Table 19 describes the significant fields shown in the display.
Table 19 show pas y88e8k interface Field Descriptions
Field
|
Description
|
ring size
|
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 show pci aim command in user EXEC or privileged EXEC mode.
show pci aim
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
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:
0x00: 04 FF 40 01 2D 41 01 00 FF FF FF FF FF FF FF FF
0x10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Related Commands
Command
|
Description
|
clear aim
|
Clears data compression AIM registers and resets the hardware.
|
test aim eeprom
|
Tests the data compression AIM after it is installed in a Cisco 2600 series router.
|
show platform
To display platform information, use the show platform command in privileged EXEC mode.
show platform {buffers | copp rate-limit {arp | dhcp | atm-oam | ethernet-oam | icmp | igmp |
pppoe-discovery | atom ether-vc | all} | np copp [ifnum] [detail] | dma | eeprom | fault |
hardware capacity | hardware pfc mode | internal-vlan | interrupts | netint | software
ipv6-multicast connected | stats | tech-support {ipmulticast [vrf vrf-name] group-ip-addr
src-ip-addr | unicast [vrf vrf-name] destination-ip-addr destination-mask [global]} | tlb | vfi
dot1q-transparency | vlans}
Cisco ASR 1000 Series Aggregation Services Routers
show platform
Syntax Description
buffers
|
Displays buffer-allocation information.
|
copp rate-limit
|
Displays Cisco Control Plane Policing (CoPP) rate-limit information on the Cisco 7600 SIP-400.
|
arp
|
Specifies Address Resolution Protocol (ARP) packet traffic.
|
dhcp
|
Specifies Dynamic Host Configuration Protocol (DHCP) packet traffic.
|
atm-oam
|
Specifies ATM Operation, Administration, and Maintenance (OAM) packet traffic.
|
ethernet-oam
|
Specifies Ethernet OAM packet traffic.
|
icmp
|
Specifies Internet Connection Management Protoocol Rate limiter.
|
igmp
|
Specifies Internet Group Management Potocol Rate limiter.
|
pppoe-discovery
|
Specifies Point-to-Point Protocol over Ethernet (PPPoE) discovery packet information.
|
atom ether-vc
|
Shows whether IP or routed mode interworking is configured.
|
all
|
Displays rate-limit information for all protocols.
|
np copp
|
Displays debug information for a given CoPP session ID or for all CoPP sessions.
|
ifnum
|
(Optional) A session ID.
|
detail
|
(Optional) Shows full rate-limited values.
|
dma
|
Displays Direct Memory Access (DMA) channel information.
|
eeprom
|
Displays CPU EEPROM information.
|
fault
|
Displays the fault date.
|
hardware capacity
|
Displays the capacities and utilizations for hardware resources; see the show platform hardware capacity command.
|
hardware pfc mode
|
Displays the type of installed Policy Feature Card (PFC).
|
internal-vlan
|
Displays the internal VLAN.
|
interrupts
|
Displays m8500 interrupt counters.
|
netint
|
Displays the platform network-interrupt information.
|
software ipv6-multicast connected
|
Displays all the IPv6 subnet Access Control List (ACL) entries on the Route Processor (RP); see the show platform software ipv6-multicast command.
|
stats
|
Displays Constellation WAN (CWAN) statistics.
|
tech-support ipmulticast
|
Displays IP multicast-related information for Technical Assistance Center (TAC).
|
vrf vrf-name
|
(Optional) Displays the Virtual Private Network (VPN) routing and forwarding (VRF) instance.
|
group-ip-addr
|
Group IP address.
|
src-ip-addr
|
Source IP address.
|
unicast
|
Displays IP unicast-related information for TAC.
|
destination-ip-addr
|
Destination IP address.
|
destination-mask
|
Destination mask.
|
global
|
(Optional) Displays global output.
|
tlb
|
Displays information about the translation look-aside buffer (TLB) register.
|
vfi
|
Displays CWAN virtual forwarding instance (VFI) commands.
|
dot1q-transparency
|
Displays the dot1q transparency setting.
|
vlans
|
Displays hidden VLAN-to-WAN interface mapping.
|
Command Modes
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. This command was changed to include the hardware pfc mode keywords.
|
12.2(18)SXD
|
This command was modified to include the software ipv6-multicast connected keywords.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRC
|
This command was modified to include additional keywords to support CoPP enhancements on the Cisco 7600 SIP-400 on the Cisco 7600 series router.
|
Cisco IOS XE Release 2.1
|
This command was integrated into Cisco IOS XE Release 2.1.
|
12.2(33)SRD
|
This command was modified. The atom ether-vc keyword was added.
|
Usage Guidelines
This command is similar to the show msfc command.
This command can be used to verify the existence of a second Cisco IOS process on a single Cisco ASR 1000 RP on a Cisco ASR 1002 router or Cisco ASR 1004 router.
When this command is used with the atom ether-vc keyword, it is used on the line-card console.
Examples
The following sample output from the show platform buffers command displays buffer-allocation information:
Router# show platform buffers
Vlan Sel Min Max Cnt Rsvd
Cisco ASR 1000 Series Routers
The following example displays online status information for the shared port adapters (SPAs), Cisco ASR 1000 SPA Interface Processor (SIP), Cisco ASR 1000 Embedded Services Processor (ESP), Cisco ASR 1000 RP, power supplies, and fans. The ESPs are shown as F0 and F1. The RPs are shown as R0 and R1.
The State column should display "ok" for SIPs, SPAs, power supplies, and fans. For RPs and ESPs, the State column should display "ok, active" or "ok, standby."
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 18:23:58
0/0 SPA-5X1GE-V2 ok 18:22:38
0/1 SPA-8X1FE-TX-V2 ok 18:22:33
0/2 SPA-2XCT3/DS0 ok 18:22:38
1 ASR1000-SIP10 ok 18:23:58
1/0 SPA-2XOC3-POS ok 18:22:38
1/1 SPA-8XCHT1/E1 ok 18:22:38
1/2 SPA-2XT3/E3 ok 18:22:38
R0 ASR1000-RP1 ok, active 18:23:58
R1 ASR1000-RP1 ok, standby 18:23:58
F0 ASR1000-ESP10 ok, active 18:23:58
F1 ASR1000-ESP10 ok, standby 18:23:58
P0 ASR1006-PWR-AC ok 18:23:09
P1 ASR1006-FAN ok 18:23:09
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Cisco ASR 1000 Series Routers—Verifying Dual Cisco IOS Processes on Single RP
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 show platform command is provided before and after the SSO configuration to verify that the second Cisco IOS process is enabled and active.
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:04:39
0/0 SPA-5X1GE-V2 ok 00:03:23
0/1 SPA-2XT3/E3 ok 00:03:18
R0 ASR1000-RP1 ok, active 00:04:39
F0 ASR1000-ESP10 ok, active 00:04:39
P0 ASR1004-PWR-AC ok 00:03:52
P1 ASR1004-PWR-AC ok 00:03:52
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# redundancy
Router(config-red)# mode sso
*May 27 19:43:43.539: %CMRP-6-DUAL_IOS_REBOOT_REQUIRED: R0/0: cmand: Configuration must
be saved and the chassis must be rebooted for IOS redundancy changes to take effect
*May 27 19:44:04.173: %SYS-5-CONFIG_I: Configured from console by user on console
Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
Proceed with reload? [confirm]
*May 27 19:45:16.917: %SYS-5-RELOAD: Reload requested by user on console. Reload Reason:
Reload command.
<reload output omitted for brevity>
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:29:34
0/0 SPA-5X1GE-V2 ok 00:28:13
0/1 SPA-2XT3/E3 ok 00:28:18
R0 ASR1000-RP1 ok 00:29:34
R0/1 ok, standby 00:27:49
F0 ASR1000-ESP10 ok, active 00:29:34
P0 ASR1004-PWR-AC ok 00:28:47
P1 ASR1004-PWR-AC ok 00:28:47
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Table 20 describes the significant fields shown in the display.
Table 20 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.
|
Cisco 7600 Series Routers with Cisco 7600 SIP-400
The following sample output from the show platform copp rate-limit arp 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:
Router# show platform copp rate-limit arp
Rate limiter Information for Protocol arp:
Rate Limiter Status: Enabled
Max Observation Period : 60 seconds
Per Interface Rate Limiter Information
Interface Conformed Pkts Exceeded Pkts Enabled Obs Period (Mts)
GigabitEthernet5/1 0 0 No -
GigabitEhternet5/1.1 14 0 No -
GigabitEthernet5/1.2 28 2 No -
GigabitEthernet5/2 0 0 No -
GigabitEthernet5/2.1 180 4 Yes 35
GigabitEthernet5/2.2 200 16 Yes Max
Table 21 describes the significant fields shown in the display.
Table 21 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 show platform eeprom command displays CPU EEPROM information:
Router# show platform eeprom
hexadecimal contents of block:
00: AB AB 02 9C 13 5B 02 00 00 02 60 03 03 E9 43 69 .....[....`...Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 00 00 00 00 00 sco Systems.....
20: 00 00 57 53 2D 58 36 4B 2D 53 55 50 33 2D 50 46 ..WS-X6K-SUP3-PF
30: 43 33 00 00 00 00 53 41 44 30 36 34 34 30 31 57 C3....SAD064401W
40: 4C 00 00 00 00 00 00 00 00 00 37 33 2D 37 34 30 L.........73-740
50: 34 2D 30 37 00 00 00 00 00 00 30 35 00 00 00 00 4-07......05....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 02 BD 00 00 00 00 00 09 00 05 00 01 ................
80: 00 03 00 01 00 01 00 02 03 E9 00 00 00 00 00 00 ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 ............
block-signature = 0xABAB, block-version = 2,
block-length = 156, block-checksum = 4955
IDPROM capacity (bytes) = 512 IDPROM block-count = 2
OEM String = 'Cisco Systems'
Product Number = 'WS-X6K-SUP3-PFC3'
Serial Number = 'SAD064401WL'
Manufacturing Assembly Number = '73-7404-07'
Manufacturing Assembly Revision = '05'
Hardware Revision = 0.701
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.5.1.3.1.1.2.1001
Power Consumption = 0 centiamperes RMA failure code = 0-0-0-0
*** end of common block ***
hexadecimal contents of block:
00: 60 03 02 67 0C 24 00 00 00 00 00 00 00 00 00 00 `..g.$..........
10: 00 00 00 00 00 00 00 51 00 05 9A 3A 7E 9C 00 00 .......Q...:~...
20: 02 02 00 01 00 01 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 14 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
50: 00 00 81 81 81 81 80 80 80 80 80 80 80 80 80 80 ................
60: 80 80 06 72 00 46 37 ...r.F7
block-signature = 0x6003, block-version = 2,
block-length = 103, block-checksum = 3108
*** linecard specific block ***
feature-bits = 00000000 00000000
hardware-changes-bits = 00000000 00000000
mac base = 0005.9A3A.7E9C
epld_versions = 0001 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000
pair #0: type=14, count=01
pair #1: type=00, count=00
pair #2: type=00, count=00
pair #3: type=00, count=00
pair #4: type=00, count=00
pair #5: type=00, count=00
pair #6: type=00, count=00
pair #7: type=00, count=00
sensor #0: critical = -127 oC (sensor present but ignored), warning = -127 oC (sensor
present but ignored)
sensor #1: critical = -127 oC (sensor present but ignored), warning = -127 oC (sensor
present but ignored)
sensor #2: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #3: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #4: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #5: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #6: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
sensor #7: critical = -128 oC (sensor not present), warning = -128 oC (sensor not
present)
max_connector_power = 1650
*** end of linecard specific block ***
The following sample output from the show platform fault command displays fault-date information:
Router# show platform fault
rsp72043_rp Software (rsp72043_rp-ADVENTERPRISEK9_DBG-M), Version 12.2(32.8.1)RE
C186 ENGINEERING WEEKLY BUILD, synced to V122_32_8_11_SR186
Compiled Wed 08-Apr-09 09:22 by abcd
Exception Vector: 0x1500 PC 0x0B13DD4C MSR 0x00029200 LR 0x0B13DD10
r0 0x0B13DD10 r1 0x1C58A1C8 r2 0xFFFCFFFC r3 0x189EDEF4
r4 0x00000000 r5 0x00000000 r6 0x1C58A1B0 r7 0x00029200
r8 0x00029200 r9 0x00000000 r10 0x00000001 r11 0x189EDEF0
r12 0x0000001B r13 0x04044000 r14 0x08736008 r15 0x115C0000
r16 0x00000000 r17 0x00000000 r18 0x00000000 r19 0x1B751358
r20 0x00000000 r21 0x00000000 r22 0x00000000 r23 0x00000000
r24 0x00000000 r25 0x00000000 r26 0x00000000 r27 0x00000001
r28 0x13255EC0 r29 0x1C59BD00 r30 0x13255EC0 r31 0x00000000
dec 0x00007333 tbu 0x00004660 tbl 0x594BBFC4 pvr 0x80210020
dear 0x00000000 dbcr0 0x41000000 dbcr1 0x00000000 dbcr2 0x00000000
iac1 0x00000000 iac2 0x00000000 dac1 0x00000000 dac2 0x00000000
The following sample output from the show platform hardware pfc mode command displays the PFC-operating mode:
Router# show platform hardware pfc mode
PFC operating mode : PFC3A
This example shows how to display platform network-interrupt information:
Router# show platform netint
Network IO Interrupt Throttling:
throttle count=0, timer count=0
netint usec=3999, netint mask usec=800
inband_throttle_mask_hi = 0x0
inband_throttle_mask_lo = 0x800000
This following sample output from the show platform tlb command displays the TLB-register information:
Router# show platform tlb
Virt Address range Phy Address range Attributes
0x10000000:0x1001FFFF 0x010000000:0x01001FFFF CacheMode=2, RW, Valid
0x10020000:0x1003FFFF 0x010020000:0x01003FFFF CacheMode=2, RW, Valid
0x10040000:0x1005FFFF 0x010040000:0x01005FFFF CacheMode=2, RW, Valid
0x10060000:0x1007FFFF 0x010060000:0x01007FFFF CacheMode=2, RW, Valid
0x10080000:0x10087FFF 0x010080000:0x010087FFF CacheMode=2, RW, Valid
0x10088000:0x1008FFFF 0x010088000:0x01008FFFF CacheMode=2, RW, Valid
0x18000000:0x1801FFFF 0x010000000:0x01001FFFF CacheMode=0, RW, Valid
0x19000000:0x1901FFFF 0x010000000:0x01001FFFF CacheMode=7, RW, Valid
0x1E000000:0x1E1FFFFF 0x01E000000:0x01E1FFFFF CacheMode=2, RW, Valid
0x1E880000:0x1E899FFF 0x01E880000:0x01E899FFF CacheMode=2, RW, Valid
0x1FC00000:0x1FC7FFFF 0x01FC00000:0x01FC7FFFF CacheMode=2, RO, Valid
0x30000000:0x3001FFFF 0x070000000:0x07001FFFF CacheMode=2, RW, Valid
0x40000000:0x407FFFFF 0x000000000:0x0007FFFFF CacheMode=3, RO, Valid
0x58000000:0x59FFFFFF 0x088000000:0x089FFFFFF CacheMode=3, RW, Valid
0x5A000000:0x5BFFFFFF 0x08A000000:0x08BFFFFFF CacheMode=3, RW, Valid
0x5C000000:0x5DFFFFFF 0x08C000000:0x08DFFFFFF CacheMode=3, RW, Valid
0x5E000000:0x5FFFFFFF 0x08E000000:0x08FFFFFFF CacheMode=3, RW, Valid
This example shows how use the atom ether-vc keyword to display line-card information for an ES20 line card in slot 3.
Router# show platform copp rate-limit atom ether-vc
AToM Ether VC Index(12902): segtype(3) seghandle(0x5ECF7F34)
Disposition : flags(97) vlanid(502) local_vc_label(22691)
ForwardingTable: oper(12) flags(0x2100) vlan(502) dest_index(0x9ED)
Imposition: flags(0x21) egress_idx(0x0) ifnum(28)
tx_tvc(0x7D83) rvclbl[0](3356) rigplbl[1](1011) label[2](0)
label[3](0) ltl(0x9ED) mac(0014.1c80.f600) qos_info(0x0)
loc_lbl acif_num fw_idx cword eg_ifnum ckt_idx vlan ac_hdl vc_hash
22691 615 0x0 0x3 28 0x8003 502 0x5ECF7F34 0x3266
Platform Index(0x81F68003) is_sw(1) is_vfi(0) vlan(502) pseudo_port_offset(3)
tx_tvc(0x7D83)
Statistics : Packets Bytes Drop Pkts Drop Bytes ID
Vlan func[1]: 502 (0x1F6) func(0:invalid) feat (0x0 )
idx ltl h pt cw vt efp adj v imp
x---- x-- d d- d- d- x--- x--- d x---
SIP10G EoMPLS disp detailed info:
t vclbl VLAN Type disp-idx
- d------- x---(d---) ------- x-------
0 00022691 01F6(0502) ether 00001692
SIP10G EoMPLS ipiw disp detailed info:
ipiw mac valid CE-MAC Address
b--- b-------- --------------
0001 000000001 0016.9c6e.7480
VC Summary: vlan(502) VC count(1)
Related Commands
Command
|
Description
|
platform copp
|
Turns on or off rate-limiting for an interface on the Cisco 7600 SIP-400.
|
platform copp observation period
|
Sets the observation period before automatically turning off the per-interface rate limiter on the Cisco 7600 SIP-400.
|
pseudowire class
|
Specifies the name of a Layer 2 pseudowire class.
|
show msfc
|
Displays MSFC information.
|
show platform acl software-switched
To display whether ACLs are enabled for software-switched WAN packets, use the show platform acl software-switched command in privileged EXEC mode.
show platform acl software-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(33)SXI2
|
This command was introduced.
|
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 show platform acl software-switched command.
Examples
This example shows how to display whether ACLs are enabled for software-switched WAN packets:
Router# show platform acl software-switched
CWAN: ACL treatment for software switched in INGRESS is enabled
CWAN: ACL treatment for software switched in EGRESS is disabled
Related Commands
Command
|
Description
|
platform cwan acl software-switched
|
Allows ACLs to be applied to WAN packets that are software-switched.
|
show platform atom disp-tbl backup
To display the disposition table on the line card for backup VCs, use the show platform atom disp-tbl backup command in privileged EXEC mode.
show platform atom disp-tbl backup pseudo-ckt-index
Syntax Description
pseudo-ckt-index
|
Defines the pseudo-circuit-index. The acceptable range is between 1 and 65537.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Usage Guidelines
The show platform atom disp-tbl backup command should be used while using the Hot-Standby Psuedo Wire (HSPW) feature.
Examples
The following example displays the disposition table on the Line Card for backup VCs.
Router# show platform atom disp-tbl backup
Pseudo Dlci or Local Outgoing IW Backup
Ckt Idx Vcd Label Interface Type VC
------- ------- ------- --------------------- ---- ------
Related Commands
Command
|
Description
|
show platform atom disp-tbl local-vc-label
|
Displays the disposition table on the line card for a VC based on the local label.
|
show platform atom tbl-summary
|
Displays the total number of PWs programmed on the Line Card.
|
show platform atom imp-tbl backup
|
Displays the imposition table on the line card for backup VCs.
|
show platform atom imp-tbl remote-vc-label
|
Displays the imposition table on the line card for a VC based on the remote label.
|
show platform atom disp-tbl local-vc-label
To display the disposition table on the line card for a VC based local label, use the show platform atom disp-tbl local-vc-label command in privileged EXEC mode.
show platform atom disp-tbl local-vc-label local-vc-label
Syntax Description
local-vc-label
|
Defines the VC based local label. The acceptable range is between 15 and 1048575.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Usage Guidelines
The show platform atom disp-tbl local-vc-label command should be used only if you know the Local VC Label for a VC.
Examples
The following example displays the disposition table on the Line Card for a VC based on the local label.
Router# show platform atom imp-tbl remote-vc-label 97
Pseudo Ckt Idx Dlci or Vcd Dest Vlanid LTL Index # Lbls Imposed Remote Label
-------------- ------------- ------------ ---------- --------------- --------------
Local Label Outgoing Interface IW Type Backup VC AC segment ssm id Segment Status
----------- -------------------- ------- --------- ------------------- --------------
57 Gi4/3/3 L2L No 20561 UP
Related Commands
Command
|
Description
|
show platform atom imp-tbl remote-vc-label
|
Displays the imposition table on the line card for a VC based on the remote label.
|
show platform atom tbl-summary
|
Displays the total number of PWs programmed on the line card.
|
show platform atom imp-tbl backup
|
Displays the imposition table on the line card for backup VCs.
|
show platform atom disp-tbl backup
|
Displays the disposition table on the line card for backup VCs.
|
show platform atom imp-tbl backup
To display the imposition table on the line card for backup VCs, use the show platform atom imp-tbl backup command in privileged EXEC mode.
show platform atom imp-tbl backup pseudo-ckt-index
Syntax Description
pseudo-ckt-index
|
Defines the pseudo circuit index. The acceptable range is between 1 and 65537.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Usage Guidelines
The show platform atom imp-tbl backup command should be used while using the Hot-Standby Psuedo Wire (HSPW) feature.
Examples
The following example displays the imposition table on the Line Card for backup VCs.
Router# show platform atom imp-tbl backup
Pseudo Ckt Idx Dlci or Vcd Dest Vlanid LTL Index # Lbls Imposed Remote Label
-------------- ------------- ------------ ---------- --------------- --------------
Local Label Outgoing Interface IW Type Backup VC AC segment ssm id Segment Status
----------- -------------------- ------- --------- ------------------- --------------
61 Gi4/0/1 L2L Yes 16464 STANDBY
Related Commands
Command
|
Description
|
show platform atom disp-tbl local-vc-label
|
Displays the disposition table on the line card for a VC based on the local label.
|
show platform atom tbl-summary
|
Displays the total number of PWs programmed on the Line Card.
|
show platform atom disp-tbl backup
|
Displays the disposition table on the line card for backup VCs.
|
show platform atom imp-tbl remote-vc-label
|
Displays the imposition table on the line card for a VC based on the remote label.
|
show platform atom imp-tbl remote-vc-label
To display the imposition table on the line card for a VC based remote label, use the show platform atom imp-tbl remote-vc-label command in privileged EXEC mode.
show platform atom imp-tbl remote-vc-label remote-vc-label
Syntax Description
remote-vc-label
|
Defines the remote VC based label. The acceptable range is between 15 and 1048575.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Usage Guidelines
The show platform atom imp-tbl remote-vc-label command should be used only if the Remote VC Label for a VC is known.
Examples
The following example displays the imposition table on the Line Card for a VC based on the remote label.
Router# show platform atom imp-tbl remote-vc-label 97
Pseudo Ckt Idx Dlci or Vcd Dest Vlanid LTL Index # Lbls Imposed Remote Label
-------------- ------------- ------------ ---------- --------------- --------------
Local Label Outgoing Interface IW Type Backup VC AC segment ssm id Segment Status
----------- -------------------- ------- --------- ------------------- --------------
57 Gi4/3/3 L2L No 20561 UP
Related Commands
Command
|
Description
|
show platform atom disp-tbl local-vc-label
|
Displays the disposition table on the line card for a VC based on the local label.
|
show platform atom tbl-summary
|
Displays the total number of PWs programmed on the Line Card.
|
show platform atom imp-tbl backup
|
Displays the imposition table on the line card for backup VCs.
|
show platform atom disp-tbl backup
|
Displays the disposition table on the line card for backup VCs.
|
show platform atom tbl-summary
To display the total number of pseudowires (PWs) programmed on the line card., use the show platform atom tbl-summary command in privileged EXEC mode.
show platform atom tbl-summary
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Usage Guidelines
The show platform atom tbl-summary command is used to determine the primaryPWs and backup PWs that are programmed.
Examples
This example displays the total number of PWs programmed on the Line Card.
Router# show platform atom tbl-summary
Total Number of entries(CWAN): 2, AToM Entries(LC): 2 Local Switching Entries(LC): 0
AToM Entries Primary: 1, Backup: 1
Related Commands
Command
|
Description
|
show platform atom imp-tbl local-vc-label
|
Displays the imposition table on the line card for a VC based on the remote label.
|
show platform atom disp-tbl local-vc-label
|
Displays the disposition table on the line card for a VC based on the local label.
|
show platform atom imp-tbl backup
|
Displays the imposition table on the line card for backup VCs.
|
show platform atom disp-tbl backup
|
Displays the disposition table on the line card for backup VCs.
|
show platform diag
To display diagnostic and debug information for individual platform components, use the show platform diag command in privileged EXEC mode.
show platform diag
Syntax Description
diag
|
Displays diagnostic and debug information for the platform components.
|
Command Default
This command has no default settings.
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.
|
Usage Guidelines
This command can be used to display debug and diagnostic information and indicate the status of field replaceable unit (FRU) components in any Cisco ASR 1000 Series Router.
Examples
The following example displays diagnostic information for the Cisco ASR 1000 SPA Interface Processor (SIP), shared port adapters (SPAs), Cisco ASR 1000 Embedded Services Processor (ESP), Cisco ASR 1000 Route Processors (RP), and power supplies. The ESP is shown as F0 or F1. The RPs are shown as R0 or R1. The power supplies are shown as P0 and P1
Router#show platform diag
Internal operational state : ok
Physical insert detect time : 00:00:48 (4d22h ago)
Software declared up time : 00:01:40 (4d22h ago)
Firmware version : 12.2(33r)XNB
Sub-slot: 0/0, SPA-5X1GE-V2
Internal state : inserted
Physical insert detect time : 00:00:36 (4d22h ago)
Logical insert detect time : 00:02:23 (4d22h ago)
Sub-slot: 0/1, SPA-2XT3/E3
Internal state : inserted
Physical insert detect time : 00:00:36 (4d22h ago)
Logical insert detect time : 00:02:23 (4d22h ago)
Internal operational state : ok
Physical insert detect time : 00:00:48 (4d22h ago)
Software declared up time : 00:00:48 (4d22h ago)
Firmware version : 12.2(33r)XNB
Running state : ok, active
Logical insert detect time : 00:00:48 (4d22h ago)
Became HA Active time : 00:04:56 (4d22h ago)
Running state : ok, standby
Logical insert detect time : 00:02:50 (4d22h ago)
Running state : ok, active
Internal operational state : ok
Physical insert detect time : 00:00:48 (4d22h ago)
Software declared up time : 00:01:40 (4d22h ago)
Hardware ready signal time : 00:00:49 (4d22h ago)
Packet ready signal time : 00:01:49 (4d22h ago)
Firmware version : 12.2(33r)XNB
Physical insert detect time : 00:01:40 (4d22h ago)
Physical insert detect time : 00:01:40 (4d22h ago)
Table 22 describes the significant fields shown in the display.
Table 22 show platform diag Field Descriptions
Field
|
Description
|
Running state
|
The current online running state of the FRU component.
|
Internal state
|
The internal debug state of the FRU component for diagnostic purposes.
|
Internal operational state
|
The internal operational state of the FRU component for diagnostic purposes.
|
Physical insert detect time
|
The time of the most recent physical insertion of the FRU component detected by the platform code.
|
Software declared up time
|
The time that the software on the FRU component was declared running by the platform code.
|
Hardware ready signal time
|
The time that the hardware ready signal was detected by the platform code.
|
Packet ready signal time
|
The time that the Embedded Service Processor (ESP) packet ready signal was detected by the platform code.
|
CPLD version
|
The Complex Programmable Logic Device version number.
|
Firmware version
|
The Firmware (ROMmon) version number.
|
Logical insert detect time
|
The time that the SPA was logically detected by the platform code.
|
Became HA Active time
|
The time that this FRU became High Availability (HA) active status.
|
Related Commands
Command
|
Description
|
show platform
|
Displays platform information.
|
show platform hardware
|
Displays platform hardware information.
|
show platform software
|
Displays platform software information
|
show platform discover-devices
To display PCI device information, use the show platform discover-devices command in privileged EXEC mode.
show platform discover-devices
Syntax Description
show platform discover-devices
|
Displays PCI device information.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)T
|
This command was introduced for Cisco 3925E and Cisco 3945E Integrated Services Routers.
|
Usage Guidelines
Use the show platform discover-devices command to display information about PCI devices on the router. The output shows the device name, interface slot and port, and detailed hardware information.
Examples
The following sample output shows PCI device information for Cisco 3925E ISR.
Router#show platform discover-devices
Discovered PCI device GE 0/0, GE 0/1
root_port=2, bus_no=1, device_no=0, func_no=0, root_device_id=2
DeviceID=0x10C9, VendorID=0x8086, Command=0x0146, Status=0x0010
Class=0x02/0x00/0x00, Revision=0x01, LatencyTimer=0x00, CacheLineSize=0x10
BaseAddr0=0xFD220000, BaseAddr1=0x00000000
Discovered PCI device GE 0/2, GE 0/3
root_port=3, bus_no=2, device_no=0, func_no=0, root_device_id=3
DeviceID=0x10C9, VendorID=0x8086, Command=0x0146, Status=0x0010
Class=0x02/0x00/0x00, Revision=0x01, LatencyTimer=0x00, CacheLineSize=0x10
BaseAddr0=0xFD120000, BaseAddr1=0x00000000
Discovered PCI device PLX:
root_port=6, bus_no=37, device_no=0, func_no=0, root_device_id=6
DeviceID=0x8509, VendorID=0x10B5, Command=0x0007, Status=0x0010
Class=0x06/0x04/0x00, Revision=0xAA, LatencyTimer=0x00, CacheLineSize=0x10
BaseAddr0=0xF8F00000, BaseAddr1=0x00000000
SecLat=0x00, SubBus=53, SecBus=38, PrimBus=37
MemLimit=0xF8F0, MemBase=0xF100, PrefMemLimit=0x0001, PrefMemBase=0xFFF1
Discovered PCI device PLX:
root_port=6, bus_no=38, device_no=1, func_no=0, root_device_id=6
DeviceID=0x8509, VendorID=0x10B5, Command=0x0007, Status=0x0010
Class=0x06/0x04/0x00, Revision=0xAA, LatencyTimer=0x00, CacheLineSize=0x10
BaseAddr0=0x00000000, BaseAddr1=0x00000000
SecLat=0x00, SubBus=40, SecBus=39, PrimBus=38
MemLimit=0xF2F0, MemBase=0xF100, PrefMemLimit=0x0001, PrefMemBase=0xFFF1
Table 23 describes the significant fields shown in the display.
Table 23
Field
|
Description
|
PCI Device
|
Identifies the PCI device on the router.
|
Root_port
|
Defines the root port address on the device.
|
Bus_no
|
Defines the bus number on the device.
|
Device_no
|
Defines the device number.
|
Func_no
|
Defines the function number.
|
Root_device_id
|
Defines the root device number.
|
DeviceID
|
Defines the device identifcation number.
|
VendorID
|
Defines the vendor identifcation number.
|
Operation Command
|
Defines the operation command.
|
Status of Device
|
Defines the status of device.
|
Class
|
Defines the class address.
|
Revision (type of device)
|
Defines type of device.
|
LatencyTimer
|
Defines the latency timer.
|
CacheLineSize
|
Defines cache line size.
|
Base Address
|
Address of Base.
|
Base Address 1
|
Address of Base 1.
|
Secondary Latency Timer
|
Defines secondary latency timer.
|
SubBus
|
Defines subordinate Bus number.
|
SecBus
|
Defines secondary Bus number.
|
PrimBus
|
Defines primary Bus number.
|
DeviceID
|
Defines the device identifcation number.
|
MemLimit
|
Defines the memory limit.
|
MemBase
|
Defines the memory base.
|
PrefMemLimit
|
Defines the pre-fetchable memory limit.
|
PrefMemBase
|
Defines the pre-fetchable memory base.
|
show platform discover-devices Field Descriptions
Related Commands
Command
|
Description
|
show platform cf
|
Shows CF support-related information.
|
show platform dma
|
Show DMA-related information.
|
show platform hw-module-power
|
Displays power settings of service modules.
|
show platform interrupt
|
Shows Interrupt-related information.
|
show platform io-controller
|
Displays IO-controller information.
|
show platform led
|
Shows LED-related information.
|
show platform nvram
|
Displays NVRAM-related information.
|
show platform versions
|
Displays versions/revisions of various modules.
|
show platform smbdev
|
Shows smbus slave devices.
|
show platform mgf
|
Shows multi-gigabit fabric information.
|
show platform dwdm alarm history
To display platform DWDM alarm history, use the show platform dwdm alarm history command in privileged EXEC mode.
show platform dwdm alarm history [port index]
Syntax Description
port index
|
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.
Router# show platform dwdm alarm history
---- LAST 32 ALARMS ----------
00. LOS declared , *Jan 7 2009 21:16:40.165 UTC
---- LAST 32 ALARMS ----------
00. LOS cleared , *Jan 7 2009 21:14:32.709 UTC
01. LOS declared , *Jan 7 2009 21:14:02.625 UTC
Router# show platform dwdm alarm history 1
---- LAST 32 ALARMS ----------
00. LOS declared , *Jan 7 2009 21:16:40.165 UTC
Router# how platform dwdm alarm history 2
Router# show platform dwdm alarm history 3
---- LAST 32 ALARMS ----------
00. LOS cleared , *Jan 7 2009 21:14:32.709 UTC
01. LOS declared , *Jan 7 2009 21:14:02.625 UTC
Related Commands
Command
|
Description
|
show controllers dwdm
|
Displays ITU-T G.709 alarms, alerts, and counters for a DWDM controller.
|
show platform hardware capacity
To display the capacities and utilizations for the hardware resources, use the show platform hardware capacity command in privileged EXEC mode.
show platform hardware capacity [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-limiter—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 show platform hardware capacity rewrite-engine command documentation.
•
system—Displays the capacities and utilizations for system resources.
•
vlan—Displays the capacities and utilizations for VLAN resources.
The show platform hardware capacity cpu command 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 show platform hardware capacity eobc command displays the following information:
•
Transmit and receive rate
•
Packets received and packets sent
•
Dropped received packets and dropped transmitted packets
The show platform hardware capacity forwarding 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 show platform hardware capacity interface 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 show platform hardware capacity monitor command displays the following SPAN information:
•
The maximum local SPAN sessions, maximum RSPAN sessions, maximum ERSPAN sessions, and maximum service module sessions.
•
The local SPAN sessions used/available, RSPAN sessions used/available, ERSPAN sessions used/available, and service module sessions used/available.
The show platform hardware capacity multicast command displays the following information:
•
Multicast Replication Mode: ingress and egress IPv4 and IPv6 modes.
•
The MET table usage that indicates the total used and the percentage used for each module in the system.
•
The bidirectional PIM DF table usage that indicates the total used and the percentage used.
The show platform hardware capacity system command displays the following information:
•
PFC operating mode (PFC Version: PFC3A, PFC3B, unknown, and so forth)
•
Supervisor redundancy mode (RPR, RPR+, SSO, none, and so forth)
•
Module-specific switching information, including the following information:
–
Part number (WS-SUP720-BASE, WS-X6548-RJ-45, and so forth)
–
Series (supervisor engine, fabric, CEF720, CEF256, dCEF256, or classic)
–
CEF Mode (central CEF, dCEF)
The show platform hardware capacity vlan command displays the following VLAN information:
•
Total VLANs
•
VTP VLANs that are used
•
External VLANs that are used
•
Internal VLANs that are used
•
Free VLANs
Examples
This example shows how to display CPU capacity and utilization information for the route processor, the switch processor, and the LAN module in the Catalyst 6500 series switch:
Router# show platform hardware capacity cpu
CPU utilization: Module 5 seconds 1 minute 5 minutes
Processor memory: Module Bytes: Total Used %Used
1 RP 176730048 51774704 29%
1 SP 192825092 51978936 27%
I/O memory: Module Bytes: Total Used %Used
1 RP 35651584 12226672 34%
1 SP 35651584 9747952 27%
This example shows how to display EOBC-related statistics for the route processor, the switch processor, and the DFCs in the Catalyst 6500 series switch:
Router# show platform hardware capacity eobc
Module Packets/sec Total packets Dropped packets
This example shows how to display the current and peak switching utilization:
Router# show platform hardware capacity fabric
Bus utilization: current is 100%, peak was 100% at 12:34 12mar45
Fabric utilization: ingress egress
Module channel speed current peak current peak
1 0 20G 100% 100% 12:34 12mar45 100% 100% 12:34 12mar45
1 1 20G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
4 0 20G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
13 0 8G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
This example shows how to display information about the total capacity, the bytes used, and the percentage that is used for the Flash/NVRAM resources present in the system:
Router# show platform hardware capacity flash
Usage: Module Device Bytes: Total Used %Used
1 RP bootflash: 31981568 15688048 49%
1 SP disk0: 128577536 105621504 82%
1 SP sup-bootflash: 31981568 29700644 93%
1 SP const_nvram: 129004 856 1%
1 SP nvram: 391160 22065 6%
7 dfc#7-bootflash: 15204352 616540 4%
8 dfc#8-bootflash: 15204352 0 0%
This example shows how to display the capacity and utilization of the EARLs present in the system:
Router# show platform hardware capacity forwarding
MAC Table usage: Module Collisions Total Used %Used
VPN CAM usage: Total Used %Used
FIB TCAM usage: Total Used %Used
72 bits (IPv4, MPLS, EoM) 196608 36 1%
144 bits (IP mcast, IPv6) 32768 7 1%
detail: Protocol Used %Used
Adjacency usage: Total Used %Used
Module pps peak-pps peak-time
6 8 1972 02:02:17 UTC Thu Apr 21 2005
TCAM utilization: Module Created Failed %Used
ICAM utilization: Module Created Failed %Used
Flowmasks: Mask# Type Features
IPv4: 1 Intf FulNAT_INGRESS NAT_EGRESS FM_GUARDIAN
CPU Rate Limiters Resources
Rate limiters: Total Used Reserved %Used
Key: ACLent - ACL TCAM entries, ACLmsk - ACL TCAM masks, AND - ANDOR,
QoSent - QoS TCAM entries, QOSmsk - QoS TCAM masks, OR - ORAND,
Lbl-in - ingress label, Lbl-eg - egress label, LOUsrc - LOU source,
LOUdst - LOU destination, ADJ - ACL adjacency
Module ACLent ACLmsk QoSent QoSmsk Lbl-in Lbl-eg LOUsrc LOUdst AND OR ADJ
6 1% 1% 1% 1% 1% 1% 0% 0% 0% 0% 1%
This example shows how to display the interboard communication resources:
Router# show platform hardware capacity ibc
Module Packets/sec Total packets Dropped packets
This example shows how to display the interface resources:
Router# show platform hardware capacity interface
Module Total drops: Tx Rx Highest drop port: Tx Rx
Module Bytes: Tx buffer Rx buffer
This example shows how to display SPAN information:
Router# show platform hardware capacity monitor
Source sessions: 2 maximum, 0 used
Destination sessions: 64 maximum, 0 used
ERSPAN destination (max 24) 0
This example shows how to display the capacity and utilization of resources for Layer 3 multicast functionality:
Router# show platform hardware capacity multicast
IPv4 replication mode: ingress
IPv6 replication mode: ingress
Bi-directional PIM Designated Forwarder Table usage: 4 total, 0 (0%) used
Replication capability: Module IPv4 IPv6
MET table Entries: Module Total Used %Used
This example shows how to display information about the system power capacities and utilizations:
Router# show platform hardware capacity power
Power supply redundancy mode: administratively combined
System power: 1922W, 0W (0%) inline, 1289W (67%) total allocated
This example shows how to display the capacity and utilization of QoS policer resources per EARL in the Catalyst 6500 series switch:
Router# show platform hardware capacity qos
Aggregate policers: Module Total Used %Used
Microflow policer configurations: Module Total Used %Used
This example shows how to display information about the key system resources:
Router# show platform hardware capacity system
PFC operating mode: PFC3BXL
Supervisor redundancy mode: administratively rpr-plus, operationally rpr-plus
Switching Resources: Module Part number Series CEF mode
5 WS-SUP720-BASE supervisor CEF
9 WS-X6548-RJ-45 CEF256 CEF
This example shows how to display VLAN information:
Router# show platform hardware capacity vlan
VLANs: 4094 total, 10 VTP, 0 extended, 0 internal, 4084 free
Related Commands
Command
|
Description
|
show msfc
|
Displays MSFC information.
|
show platform
|
Displays platform information.
|
show platform hardware capacity rewrite-engine
|
Displays the packet drop and performance counters of the central rewrite engine on supervisors and line cards.
|
show platform hardware interface
To display information about an interface, use the show platform hardware interface command in privileged EXEC or diagnostic mode.
show platform hardware interface type number plim qos input map
Channelized T3 Shared Port Adapters
show platform hardware interface serial slot/subslot/port/t1-number:channel-group plim qos
input map
Channelized T1/E1 Shared Port Adapters
show platform hardware interface serial slot/subslot/port:channel-group plim qos input map
Shared Port Adapters
show platform hardware interface type slot/subslot/port[.subint] plim qos input map
Syntax Description
type
|
Interface type. Table 24 in the "Usage Guidelines" contains a list of interface types.
|
number
|
Port number on the selected interface.
|
plim qos input map
|
Physical Line Interface Module (PLIM) QoS input mapping information.
|
serial
|
Serial interface.
|
slot/subslot/port/t1- number:channel-group
|
The following applies to Channelized T3 shared port adapters:
• slot/—Chassis slot where the Cisco ASR 1000 Series SPA interface processor (SIP) is installed.
• 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.
|
slot/subslot/port: channel-group
|
The following applies to Channelized T1/E1 shared port adapters:
• slot/—Chassis slot where the Cisco ASR 1000 Series SPA interface processor (SIP) is installed.
• 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.
• channel-group—Number 0 to 30 of the DS0 link on the T1 channel.
|
slot/subslot/port [.subint]
|
The following applies to shared port adapters other than the Channelized T3 or Channelized T1/E1 shared port adapters:
• slot/—Chassis slot where the Cisco ASR 1000 Series SPA interface processor (SIP) is installed.
• 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.
Table 24 lists the interface types.
Table 24 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:
Router# show platform hardware interface gigabitethernet 0/0/0 plim qos input map
Interface GigabitEthernet0/0/0
Low Latency Queue(High Priority):
IP PREC, 6, 7
IPv6 TC, 46
MPLS EXP, 6, 7
Related Commands
Command
|
Description
|
show platform hardware port
|
Displays information about an interface port on a shared port adapter (SPA).
|
show platform hardware slot
|
Displays information about the processor in a chassis slot.
|
show platform hardware subslot
|
Displays information about a shared port adapter (SPA).
|
show platform hardware network-clocks
To display network clocks for an ES+ line card, use the show platform hardware network-clocks command in privileged EXEC mode.
show platform hardware network-clocks [bits | zl30138]
Syntax Description
bits
|
Specifies uilding Integrated Timing Supply (BITS) element.
|
zl30138
|
Specifies ZL30138 SONET/SDH/10GbE System Synchronizer.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SRD1
|
This command was introduced on the Cisco 7600 series routers for ES+ line cards only.
|
Examples
The following example shows how the show platform hardware network-clocks command is used to display network clocks:
Router# show platform hardware network-clocks
Port 1: N Port 2: N Port 3: N Port 4: N
Backplane Bus Status and Source:
Primary : Disabled, Port 0 RX_DEMAP Clock
Secondary : Disabled, Port 0 RX_DEMAP Clock
BITS : Disabled, Port 0 RX_DEMAP Clock
ZL30138 Configuration and Status:
Mode of Operation : Manual Freerun
Ref0 Priority : 15 Ref1 Priority : 15
Ref2 Priority : 15 Ref3 Priority : 15
Ref4 Priority : 15 Ref5 Priority : 15
Ref6 Priority : 15 Ref7 Priority : 15
Reference Monitoring: Custom A frequency 25000 kHz
Ref# SCM CFM GST PFM Mode Detected
----------------------------------------------------------
0 1 1 1 1 CustA 38.88 MHz
1 1 1 1 1 CustA 19.44 MHz
3 1 1 1 1 CustA not detected
4 1 1 1 1 Auto not detected
5 1 1 1 1 Auto not detected
6 1 1 1 1 Auto not detected
7 1 1 1 1 Auto not detected
BITS Configuration and Status:
Signal Type : T1 ESF Framing
Clock Divider : 1.544 MHz
Related Commands
Command
|
Description
|
clock source
|
Specifies the interface clock source type.
|
network-clock select
|
Selects a source of network clock.
|
show network-clocks
|
Displays the current configured and active network clock sources.
|
show platform hardware slot
To display information about the processor in a chassis slot, use the show platform hardware slot command in privileged EXEC or diagnostic mode.
Cisco ASR 1000 Series SPA Interface Processors
show platform hardware slot sip
{dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| fan status
| io-port
| led status
| mcu status [raw]
| plim {buffer settings [detail] | cpu | qos input bandwidth | registers reg | statistics
[internal] | status [internal]}
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}
| spa {attributes | oir-statistics | status}}
Cisco ASR 1000 Series Embedded Services Processors
show platform hardware slot esp
{dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| io-port
| led status
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}}
Cisco ASR 1000 Series Route Processors
show platform hardware slot rp
{alarms {audible | visual}
| dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| io-port
| led status
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}}
Syntax Description
sip
|
Type of Cisco ASR 1000 Series SPA interface processor (SIP) with one of the following values:
• 0—SIP in chassis slot 0.
• 1—SIP in chassis slot 1.
• 2—SIP in chassis slot 2.
• P0—Power supply slot 0.
• P1—Power supply slot 1.
• P2—Power supply slot 2.
• P3—Power supply slot 3.
|
dram statistics
|
Provides Error-correcting code (ECC) error statistics (for Cisco Technical Support only).
|
eobc
|
Provides Ethernet out-of-band channel (EOBC) information.
|
interface
|
Provides EOBC interface information.
|
primary
|
Provides primary EOBC interface information.
|
standby
|
Provides standby EOBC interface information.
|
rmon
|
Provides EOBC interface remote monitoring (RMON) information (for Cisco Technical Support only).
|
status
|
Provides status information (Physical Line Interface Module [PLIM] status and serializer/deserializer [SerDes] status are for Cisco Technical Support only).
|
switch statistics
|
Provides EOBC switch statistics.
|
brief
|
Provides summary information.
|
detail
|
Provides detailed information (for Cisco Technical Support only). It is optional for PLIM buffer settings.
|
fan status
|
Provides Fan software status.
|
io-port
|
Provides I/O port information.
|
led status
|
Provides light emitting diode (LED) states.
|
mcu status
|
Provides Microcontroller unit (MCU) hardware status (for Cisco Technical Support only).
|
raw
|
(Optional) Provides MCU unparsed raw data (for Cisco Technical Support only).
|
plim
|
Provides PLIM information.
|
buffer settings
|
Provides PLIM buffer settings (for Cisco Technical Support only).
|
cpu
|
Provides CPU hyper threading (HT) bus information (for Cisco Technical Support only).
|
qos input bandwidth
|
Provides PLIM quality of service (QoS) input bandwidth information.
|
registers reg
|
It is the register name (for Cisco Technical Support only).
|
statistics
|
Provides Statistics information.
|
internal
|
(Optional) Provides Cisco internal information (for Cisco Technical Support only).
|
sensor
|
Provides sensor information (for Cisco Technical Support only).
|
consumer
|
Provides sensor information from the consumer process (for Cisco Technical Support only).
|
producer
|
Provides sensor information from the producer process (for Cisco Technical Support only).
|
id
|
Provides the sensor ID number (for Cisco Technical Support only).
|
all
|
Provides a brief view of all sensors (for Cisco Technical Support only).
|
serdes
|
Provides Serializer/deserializer (SerDes) information.
|
spa
|
Provides Cisco ASR 1000 Series SPA information.
|
attributes
|
Provides SPA attribute information (for Cisco Technical Support only).
|
oir-statistics
|
Provides SPA online insertion and removal (OIR) counters.
|
esp
|
Type of Cisco ASR 1000 Series Embedded Services Processor (ESP) with one of the following values:
• f0—ESP in ESP slot 0.
• f1—ESP in ESP slot 1.
|
rp
|
Type of Cisco ASR 1000 Series Route Processor (RP) with one of the following values:
• r0—RP in RP slot 0.
• r1—RP in RP slot 1.
|
alarms
|
Provides alarm states information (for Cisco Technical Support only). To display alarm status, use the show facility-alarm status command.
|
audible
|
Provides audible alarm states (for Cisco Technical Support only) information.
|
visual
|
Provides LED alarm states (for Cisco Technical Support only) information.
|
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 Aggregation Services 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 EOBC interface status for a SIP in chassis slot 0. This command provides the status of the EOBC in the indicated slot.
Router# show platform hardware slot 0 eobc interface primary status
EOBC : eth0, status : Active
Line State : Up, Speed : 1Gbps, Link mode : Full
Line Type : AUI, Autoneg : Disabled
Addr : 10.0.3.0, Netmask : 255.255.0.0, HW Addr : 0000.0300.0000
Rx pkts : 1292995, bytes : 316283357, dropped : 0 errors : 0
Tx pkts : 1124534, bytes : 270172949, dropped : 0 errors : 0
Table 37 describes the significant fields shown in the display.
Table 25 show platform hardware slot 0 eobc interface primary status Field Descriptions
Field
|
Description
|
EOBC eth0
|
Ethernet port.
|
EOBC status
|
Port status. "Active" or "Standby."
|
Line State
|
Line status. "Up" or "Down."
|
Line Speed
|
Bandwidth in gigabits per second (Gbps).
|
Link mode
|
Transmission mode. "Full" (full duplex) or "Half" (half duplex).
|
Line Type
|
Type of transceiver. "AUI" (attachment unit interface), "TP" (twisted pair), "MII" (media independent interface), "FIBER" (fiber optic), or "BNC" (Bayonette Neil-Concelman).
|
Autoneg
|
Autonegotiation. "Enabled" or "Disabled."
|
Addr
|
IP address of the port.
|
Netmask
|
IP addressing netmask of the port.
|
HW Addr
|
MAC address of the port.
|
Rx pkts/bytes
|
Number of packets and bytes received.
|
Tx pkts/bytes
|
Number of packets and bytes transmitted.
|
Rx dropped
|
Number of received packets that were dropped.
|
Tx dropped
|
Number of transmitted packets that were dropped.
|
Rx errors
|
Number of packets received with errors.
|
Tx errors
|
Number of packets transmitted with errors.
|
The following example displays brief EOBC switch statistics for a SIP in chassis slot 0:
Router# show platform hardware slot 0 eobc switch statistics brief
Port: 4, Link state: Up, Mode: Full Duplex, Speed: 1000 Mbps
Ingress bytes : 276915312 Egress bytes : 349585709
Ingress packets: 1151944 Egress packets: 1320618
Table 38 describes the significant fields shown in the display.
Table 26 show platform hardware slot 0 eobc switch statistics brief Field Descriptions
Field
|
Description
|
Port
|
Port on the EOBC switch.
|
Link state
|
Link status. "Up" or "Down."
|
Mode
|
Transmission mode. "Full Duplex" or "Half Duplex."
|
Speed
|
Bandwidth in megabits per second (Mbps).
|
Ingress bytes
|
Number of bytes received on this port.
|
Egress bytes
|
Number of bytes transmitted through this port.
|
Ingress packets
|
Number of packets received on this port.
|
Egress packets
|
Number of packets transmitted through this port.
|
The following example displays fan operation status for a SIP in chassis slot 0:
Router# show platform hardware slot 0 fan status
Table 39 describes the significant fields shown in the display.
Table 27 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 example displays the ingress arbiter settings for all PLIM buffers that are in use for a SIP in chassis slot 0:
Router# show platform hardware slot 0 plim qos input bandwidth
Ingress QOS Scheduling Mode: Strict Priority
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 100000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
Table 40 describes the significant fields shown in the display.
Table 28 show platform hardware slot 0 plim qos input bandwidth Field Descriptions
Field
|
Description
|
Ingress QOS Scheduling Mode
|
Current scheduler operation mode.
|
BW
|
Interface bandwidth in kilobits per second (kb/s).
|
Min BW
|
Guaranteed bandwidth assigned on this interface in Kbps.
|
Excessive Weight
|
Excessive bandwidth assigned on this interface in Kbps.
|
HP Policer BW
|
Bandwidth assigned for processing high-priority traffic on this interface in Kbps.
|
The following example 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).
Router# show platform hardware slot 0 plim statistics
RX IPC Pkts 739 Bytes 54564
TX IPC Pkts 739 Bytes 30752
Table 41 describes the significant fields shown in the display.
Table 29 show platform hardware slot 0 plim statistics Field Descriptions
Field
|
Description
|
RX Pkts
|
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 example displays the byte and packet counters associated with the Enhanced SerDes Interconnect (ESI) links for an ESP. It includes the 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 connected to it with active ESI links. A SIP or RP displays statistics from each ESP.
Router# show platform hardware slot f0 serdes statistics
Pkts High: 0 Low: 0 Bad: 0 Dropped: 0
Bytes High: 0 Low: 0 Bad: 0 Dropped: 0
Qstat count: 0 Flow ctrl count: 25671
Pkts High: 0 Low: 0 Bad: 0 Dropped: 0
Bytes High: 0 Low: 0 Bad: 0 Dropped: 0
Qstat count: 0 Flow ctrl count: 25674
Table 42 describes the significant fields shown in the display.
Table 30 show platform hardware slot f0 serdes statistics Field Descriptions
Field
|
Description
|
From Slot
|
Information on data passed from the indicated processor to the card where the command is run and over the SerDes.
|
To Slot
|
Information on data passed to the indicated processor from the card where the command is run and over the SerDes.
|
Pkts/Bytes High
|
Number of packets and bytes of high priority data payload.
|
Pkts/Bytes Low
|
Number of packets and bytes of low priority data payload.
|
Pkts/Bytes Bad
|
Number of packets received with packet length errors or cyclic redundacy check (CRC) errors.
|
Pkts/Bytes Dropped
|
Number of dropped packets and bytes due to first in, first out (FIFO) overflow.
|
Pkts/Bytes Looped
|
Number of packets looped back in loopback mode.
|
Pkts Error
|
Number of packets with errors.
|
Qstat count
|
Number of packets received in which an ESI link error is detected.
|
Flow ctrl count
|
Number of link-level flow control messages.
|
The following example displays the OIR statistics of SPAs installed in a SIP in chassis slot 0:
Router# show platform hardware slot 0 spa oir-statistics
Table 43 describes the significant fields shown in the display.
Table 31 show platform hardware slot 0 spa oir-statistics Field Descriptions
Field
|
Description
|
SPA OIR requests
|
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 example displays the MCU hardware status and power supply in the slot:
Note
If you use the show platform hardware slot sip mcu status command or the show platform hardware slot sip fan status command onthe Cisco ASR 1000 Series Router, Cisco recommends 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.
Router# show platform hardware slot P0 mcu status
Table 44 describes the significant fields shown in the display.
Table 32 show platform hardware slot mcu status Field Descriptions
Field
|
Description
|
Model ID
|
The 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 a SPA.
|
show platform hardware subslot
|
Displays information about a SPA.
|
show platform hardware qfp active feature cef-mpls prefix mpls
To display the interface name, along with the interface descriptor block (IDB) information, use the show platform hardware qfp active feature cef-mpls prefix mpls command in privileged EXEC mode.
show platform hardware qfp active feature cef-mpls prefix mpls label [vrf id] [exact] [brief]
Syntax Description
label
|
Multiprotocol Label Switching (MPLS) label. The range is from 0 to 1048575.
|
vrf
|
(Optional) Displays information about VPN Routing and Forwarding (VRF).
|
id
|
(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) Finds and displays the exact match of the prefix.
|
brief
|
(Optional) Displays a summary of prefix information.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)XNC
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Cisco IOS XE Release 3.4S
|
This command was integrated into Cisco IOS XE Release 3.4S.
|
Examples
The following is sample output from the show platform hardware qfp active feature cef-mpls prefix mpls command:
Router# show platform hardware qfp active feature cef-mpls prefix mpls 0
Gtrie Node Type: Tree Node
HW Content: : 89b00cad 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116085e8
Search Node Bitmap: 80 00 00 00 00 00 00 00
Gtrie Node Type: Tree Node
HW Content: : 89b00cbd 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116093d8
Search Node Bitmap: 80 00 00 00 00 00 00 00
Gtrie Node Type: Leaf Node
HW Content: : 0a000000 00000f00 00000000 895c97f0
QPPB QoS Precedence valid: 0
BGPPA Traffic Index valid: 0
TBLF application lf handle: 0
Lisp locator status bits: 0
OCE Type: EOS OCE, Number of children: 2
Next HW OCE Ptr: : 0x895c97d0, 0x895c97b0
OCE Type: Label OCE, Number of children: 1
Next HW OCE Ptr: : 0x895c9790
OCE Type: Lookup OCE, Number of children: 0
show platform hardware qfp active feature cef-mpls prefix ip
To display the interface name along with the interface descriptor block (IDB) information, use the show platform hardware qfp active feature cef-mpls prefix ip command in privileged EXEC.
show platform hardware qfp active feature cef-mpls prefix ip {ipv4 prefix | [vrf id] [exact]
[brief]}
Syntax Description
ipv4 prefix
|
The IPV4 address and the mask.
|
vrf id
|
(Optional) Displays the particular VPN Routing and Forwarding (VRF) instance. The VRF ID has the range from 0 to 1048575.
|
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.
|
Examples
The following is a sample output from the show platform hardware qfp active feature cef-mpls prefix ip command:
Router# show platform hardware qfp active feature cef-mpls prefix ip 0.0.0.0/1 vrf
Gtrie Node Type: Leaf Node
HW Content: : 00002000 00000000 897daf40 895db490
QPPB QoS Precedence valid: 0
BGPPA Traffic Index valid: 0
TBLF application lf handle: 0
Path list pointer: : 0x8b8414a0
Number of interfaces: : 1
Interface Name(s): GigabitEthernet0/3/1
OCE Type: Adjacency, Number of children: 0
Adj Type: : IPV4 Adjacency
Interface Name: GigabitEthernet0/3/1
Encap: : 00 14 f1 74 9c 1a 00 1a 30 44 3a 31 08 00
Next Hop Address: : 64000001 00000000 00000000 00000000
The following example shows the output with the names of each interface when there are multiple interfaces in the unicast reverse path forwarding (uRPF) path list:
Router# show platform hardware qfp active feature cef-mpls prefix ip 0.0.0.0/2 vrf
Gtrie Node Type: Leaf Node
HW Content: : 00001800 00000000 897dae00 895d8df0
QPPB QoS Precedence valid: 0
BGPPA Traffic Index valid: 0
TBLF application lf handle: 0
Path list pointer: : 0x8b8414a0
Number of interfaces: : 2
Interface Name(s): : GigabitEthernet0/0/4, GigabitEthernet0/3/1
show platform hardware qfp active feature cef-mpls prefix ipv6
To display the interface name, along with the interface descriptor block (IDB) information for IPv6 addressing, use the show platform hardware qfp active feature cef-mpls prefix ipv6 command in privileged EXEC mode.
show platform hardware qfp active feature cef-mpls prefix ipv6 ipv6-prefix [vrf [id]] [exact]
[brief]
Syntax Description
ipv6-prefix
|
IPv6 address and prefix. The IPv6 prefix is in the range from 0 to 128.
|
vrf id
|
(Optional) Displays the particular VPN Routing and Forwarding (VRF) instance. The VRF ID is in the range from 0 to 4294967295. If no VRF ID is specified, information about the global VRF (prefix in global routing table) is displayed.
|
exact
|
(Optional) Finds and displays the exact match of the IPv6 prefix.
|
brief
|
(Optional) Displays a summary of prefix information.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)XNC
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Cisco IOS XE Release 3.4S
|
This command was integrated into Cisco IOS XE Release 3.4S.
|
Examples
The following is sample output from the show platform hardware qfp active feature cef-mpls prefix ipv6 command:
Router# show platform hardware qfp active feature cef-mpls prefix ipv6 2001:DB8::/64
Gtrie Node Type: Tree Node
HW Content: : 89d000cd 00000004 60000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 1, TN skip 0
TA NNodes 2, TA INode Exists 1, TN TNRefs 0x11608698
Search Node Bitmap: 60 00 00 00 00 00 00 00
Gtrie Node Type: Leaf Node
HW Content: : 00004000 00000000 89995400 895c9420
QPPB QoS Precedence valid: 0
BGPPA Traffic Index valid: 0
TBLF application lf handle: 0
Prefix: cc 1e 00 00 00 00 00 00
Lisp locator status bits: 0
Path list pointer: : 0x895c9670
Number of interfaces: : 1
Interface Name(s): : GigabitEthernet0/2/0
OCE Type: Adjacency, Number of children: 0
Adj Type: : Glean Adjacency
Next Hop Address: : 00000000 00000000 00000000 00000000
Next HW OCE Ptr: : 00000000
show platform hardware qfp active feature cef-mpls prefix mpls
To display the interface name, along with the interface descriptor block (IDB) information, use the show platform hardware qfp active feature cef-mpls prefix mpls command in privileged EXEC mode.
show platform hardware qfp active feature cef-mpls prefix mpls label [vrf id] [exact] [brief]
Syntax Description
label
|
Multiprotocol Label Switching (MPLS) label. The range is from 0 to 1048575.
|
vrf
|
(Optional) Displays information about VPN Routing and Forwarding (VRF).
|
id
|
(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) Finds and displays the exact match of the prefix.
|
brief
|
(Optional) Displays a summary of prefix information.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)XNC
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Cisco IOS XE Release 3.4S
|
This command was integrated into Cisco IOS XE Release 3.4S.
|
Examples
The following is sample output from the show platform hardware qfp active feature cef-mpls prefix mpls command:
Router# show platform hardware qfp active feature cef-mpls prefix mpls 0
Gtrie Node Type: Tree Node
HW Content: : 89b00cad 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116085e8
Search Node Bitmap: 80 00 00 00 00 00 00 00
Gtrie Node Type: Tree Node
HW Content: : 89b00cbd 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116093d8
Search Node Bitmap: 80 00 00 00 00 00 00 00
Gtrie Node Type: Leaf Node
HW Content: : 0a000000 00000f00 00000000 895c97f0
QPPB QoS Precedence valid: 0
BGPPA Traffic Index valid: 0
TBLF application lf handle: 0
Lisp locator status bits: 0
OCE Type: EOS OCE, Number of children: 2
Next HW OCE Ptr: : 0x895c97d0, 0x895c97b0
OCE Type: Label OCE, Number of children: 1
Next HW OCE Ptr: : 0x895c9790
OCE Type: Lookup OCE, Number of children: 0
show platform hardware qfp active statistics drop
To display the statistics of packet drops on all the interfaces in a Packet Processor Engine (PPE), use the show platform hardware qfp active statistics drop command in privileged EXEC mode.
show platform hardware qfp active statistics drop
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.0S
|
This command was introduced.
|
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.
Examples
The following sample output from the show platform hardware qfp active statistics drop command shows the statistics of packet drops on all the interfaces in a PPE:
Router# show platform hardware qfp active statistics drop
Global Drop Stats Packets Octets
-------------------------------------------------------------------------
BadUidbSubIdx 40374 2860531
Ipv4NoRoute 52608 5482626
UnconfiguredIpv4Fia 2412 215692
Table 35 describes the significant fields shown in the display.
Table 33 show platform hardware qfp active statistics drop Field Descriptions
Field
|
Description
|
Global Drop Stats
|
Displays the reason for dropping packets.
|
Packets
|
Number of packets that are dropped.
|
Octets
|
Total number of bytes of the packets that are dropped.
|
Related Commands
Command
|
Description
|
show platform hardware qfp interface
|
Displays information about an interface in the target flow processor.
|
show platform hardware qfp interface
To display information about an interface in the target flow processor, use the show platform hardware qfp interface command in privileged EXEC mode.
show platform hardware qfp {active | standby} interface {all [summary | statistics
[drop_summary [subinterface]] [clear_drop]] | if-name name [info | statistics
[drop_summary [subinterface]] [clear_drop]] | atm if-name name statistics [clear_drop]}
Syntax Description
active
|
Specifies the active instance of the processor.
|
standby
|
Specifies the standby instance of the processor.
|
all
|
Specifies all the interfaces available on the processor.
|
summary
|
(Optional) Specifies the interface summary report.
|
statistics
|
(Optional) Specifies the statistics of the 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.
|
if-name name
|
Specifies the name of an interface, interface type, and port number of the selected interface.
|
info
|
(Optional) Specifies interface 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 on the Cisco ASR 1000 Series Aggregation Services Routers.
|
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.
|
Usage Guidelines
The show platform hardware qfp interface 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:
Router# show platform hardware qfp active interface if-name Port-channel1 info
General interface information
Interface Name: Port-channel1
Platform interface handle: 36
if_h Member Interface Name
Table 34 describes the significant fields shown in the display.
Table 34 show platform hardware qfp interface Field Descriptions
Field
|
Description
|
Interface Name
|
Name of the interface requested by the show platform hardware qfp interface command.
|
Platform interface handle
|
Number of platform interface handles displayed for the interface.
|
QFP interface handle
|
An internal identifier assigned by the quantum flow processor (QFP) software for this interface.
|
Rx uidb
|
An internal identifier for the receive side of the interface.
|
Tx uidb
|
An internal identifier for the transmit side of the interface.
|
Channel
|
An internal identifier for the transmit path to which the interface is connected.
|
The following sample output shows the summary of the drop status of the packets:
Router# show platform hardware qfp active statistics drop
Global Drop Stats Packets Octets
-------------------------------------------------------------------------
BadUidbSubIdx 40374 2860531
Ipv4NoRoute 52608 5482626
UnconfiguredIpv4Fia 2412 215692
Table 35 describes the significant fields shown in the display.
Table 35 show platform hardware qfp active statistics drop Field Descriptions
Field
|
Description
|
Global Drop Stats
|
Specifies the reason for dropping the packets.
|
Packets
|
Specifies the number of packets that are dropped.
|
Octets
|
Specifies the total number of bytes of the packets that are dropped.
|
The following sample output shows the statistics of the packets on an interface:
Router# show platform hardware qfp active interface if-name GigabitEthernet0/0/0.775
statistics
----------------------------------------------------------------
Receive Stats Packets Octets
----------------------------------------------------------------
----------------------------------------------------------------
Transmit Stats Packets Octets
----------------------------------------------------------------
----------------------------------------------------------------
Input Drop Stats Packets Octets
---------------------------------------------------------------
UnconfiguredIpv4Fia 550 49120
----------------------------------------------------------------
Output Drop Stats Packets Octets
---------------------------------------------------------------
----------------------------------------------------------------
note: 1) these drop stats are only updated when PAL
reads the interface stats.
2) the interface stats include the subinterface
Interface Rx Pkts Tx Pkts
---------------------------------------------------------------------------
GigabitEthernet0/0/0.775 3209 20
Table 36 describes the significant fields shown in the display.
Table 36 show platform hardware qfp active interface if-name statistics Field Descriptions
Field
|
Description
|
Receive Stats
|
Specifies the number of packets received through a protocol.
|
Packets
|
Specifies the number of packets transmitted through a protocol.
|
Octets
|
Specifies the total number of bytes of the packets that are dropped.
|
Transmit Stats
|
Specifies the number of packets that are transmitted on an interface.
|
Input Drop Stats
|
Specifies the drop cause and the number of incoming packets that are dropped.
|
Output Drop Stats
|
Specifies the drop cause and the number of outgoing packets that are dropped.
|
Interface
|
Specifies the name of the interface.
|
Rx Pkts
|
Specifies the number of packets received on an interface.
|
Tx Pkts
|
Specifies the number of packets transmitted on an interface.
|
Related Commands
Command
|
Description
|
show interfaces
|
Displays statistics for all interfaces configured on the router or access server.
|
show platform hardware slot
To display information about the processor in a chassis slot, use the show platform hardware slot command in privileged EXEC or diagnostic mode.
Cisco ASR 1000 Series SPA Interface Processors
show platform hardware slot sip
{dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| fan status
| io-port
| led status
| mcu status [raw]
| plim {buffer settings [detail] | cpu | qos input bandwidth | registers reg | statistics
[internal] | status [internal]}
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}
| spa {attributes | oir-statistics | status}}
Cisco ASR 1000 Series Embedded Services Processors
show platform hardware slot esp
{dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| io-port
| led status
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}}
Cisco ASR 1000 Series Route Processors
show platform hardware slot rp
{alarms {audible | visual}
| dram statistics
| eobc {interface {primary | standby} {rmon | status} | switch statistics {brief | detail}}
| io-port
| led status
| sensor {consumer | producer} {id | all}
| serdes {registers reg | statistics [internal] | status [brief]}}
Syntax Description
sip
|
Type of Cisco ASR 1000 Series SPA interface processor (SIP) with one of the following values:
• 0—SIP in chassis slot 0.
• 1—SIP in chassis slot 1.
• 2—SIP in chassis slot 2.
• P0—Power supply slot 0.
• P1—Power supply slot 1.
• P2—Power supply slot 2.
• P3—Power supply slot 3.
|
dram statistics
|
Provides Error-correcting code (ECC) error statistics (for Cisco Technical Support only).
|
eobc
|
Provides Ethernet out-of-band channel (EOBC) information.
|
interface
|
Provides EOBC interface information.
|
primary
|
Provides primary EOBC interface information.
|
standby
|
Provides standby EOBC interface information.
|
rmon
|
Provides EOBC interface remote monitoring (RMON) information (for Cisco Technical Support only).
|
status
|
Provides status information (Physical Line Interface Module [PLIM] status and serializer/deserializer [SerDes] status are for Cisco Technical Support only).
|
switch statistics
|
Provides EOBC switch statistics.
|
brief
|
Provides summary information.
|
detail
|
Provides detailed information (for Cisco Technical Support only). It is optional for PLIM buffer settings.
|
fan status
|
Provides Fan software status.
|
io-port
|
Provides I/O port information.
|
led status
|
Provides light emitting diode (LED) states.
|
mcu status
|
Provides Microcontroller unit (MCU) hardware status (for Cisco Technical Support only).
|
raw
|
(Optional) Provides MCU unparsed raw data (for Cisco Technical Support only).
|
plim
|
Provides PLIM information.
|
buffer settings
|
Provides PLIM buffer settings (for Cisco Technical Support only).
|
cpu
|
Provides CPU hyper threading (HT) bus information (for Cisco Technical Support only).
|
qos input bandwidth
|
Provides PLIM quality of service (QoS) input bandwidth information.
|
registers reg
|
It is the register name (for Cisco Technical Support only).
|
statistics
|
Provides Statistics information.
|
internal
|
(Optional) Provides Cisco internal information (for Cisco Technical Support only).
|
sensor
|
Provides sensor information (for Cisco Technical Support only).
|
consumer
|
Provides sensor information from the consumer process (for Cisco Technical Support only).
|
producer
|
Provides sensor information from the producer process (for Cisco Technical Support only).
|
id
|
Provides the sensor ID number (for Cisco Technical Support only).
|
all
|
Provides a brief view of all sensors (for Cisco Technical Support only).
|
serdes
|
Provides Serializer/deserializer (SerDes) information.
|
spa
|
Provides Cisco ASR 1000 Series SPA information.
|
attributes
|
Provides SPA attribute information (for Cisco Technical Support only).
|
oir-statistics
|
Provides SPA online insertion and removal (OIR) counters.
|
esp
|
Type of Cisco ASR 1000 Series Embedded Services Processor (ESP) with one of the following values:
• f0—ESP in ESP slot 0.
• f1—ESP in ESP slot 1.
|
rp
|
Type of Cisco ASR 1000 Series Route Processor (RP) with one of the following values:
• r0—RP in RP slot 0.
• r1—RP in RP slot 1.
|
alarms
|
Provides alarm states information (for Cisco Technical Support only). To display alarm status, use the show facility-alarm status command.
|
audible
|
Provides audible alarm states (for Cisco Technical Support only) information.
|
visual
|
Provides LED alarm states (for Cisco Technical Support only) information.
|
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 Aggregation Services 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 EOBC interface status for a SIP in chassis slot 0. This command provides the status of the EOBC in the indicated slot.
Router# show platform hardware slot 0 eobc interface primary status
EOBC : eth0, status : Active
Line State : Up, Speed : 1Gbps, Link mode : Full
Line Type : AUI, Autoneg : Disabled
Addr : 10.0.3.0, Netmask : 255.255.0.0, HW Addr : 0000.0300.0000
Rx pkts : 1292995, bytes : 316283357, dropped : 0 errors : 0
Tx pkts : 1124534, bytes : 270172949, dropped : 0 errors : 0
Table 37 describes the significant fields shown in the display.
Table 37 show platform hardware slot 0 eobc interface primary status Field Descriptions
Field
|
Description
|
EOBC eth0
|
Ethernet port.
|
EOBC status
|
Port status. "Active" or "Standby."
|
Line State
|
Line status. "Up" or "Down."
|
Line Speed
|
Bandwidth in gigabits per second (Gbps).
|
Link mode
|
Transmission mode. "Full" (full duplex) or "Half" (half duplex).
|
Line Type
|
Type of transceiver. "AUI" (attachment unit interface), "TP" (twisted pair), "MII" (media independent interface), "FIBER" (fiber optic), or "BNC" (Bayonette Neil-Concelman).
|
Autoneg
|
Autonegotiation. "Enabled" or "Disabled."
|
Addr
|
IP address of the port.
|
Netmask
|
IP addressing netmask of the port.
|
HW Addr
|
MAC address of the port.
|
Rx pkts/bytes
|
Number of packets and bytes received.
|
Tx pkts/bytes
|
Number of packets and bytes transmitted.
|
Rx dropped
|
Number of received packets that were dropped.
|
Tx dropped
|
Number of transmitted packets that were dropped.
|
Rx errors
|
Number of packets received with errors.
|
Tx errors
|
Number of packets transmitted with errors.
|
The following example displays brief EOBC switch statistics for a SIP in chassis slot 0:
Router# show platform hardware slot 0 eobc switch statistics brief
Port: 4, Link state: Up, Mode: Full Duplex, Speed: 1000 Mbps
Ingress bytes : 276915312 Egress bytes : 349585709
Ingress packets: 1151944 Egress packets: 1320618
Table 38 describes the significant fields shown in the display.
Table 38 show platform hardware slot 0 eobc switch statistics brief Field Descriptions
Field
|
Description
|
Port
|
Port on the EOBC switch.
|
Link state
|
Link status. "Up" or "Down."
|
Mode
|
Transmission mode. "Full Duplex" or "Half Duplex."
|
Speed
|
Bandwidth in megabits per second (Mbps).
|
Ingress bytes
|
Number of bytes received on this port.
|
Egress bytes
|
Number of bytes transmitted through this port.
|
Ingress packets
|
Number of packets received on this port.
|
Egress packets
|
Number of packets transmitted through this port.
|
The following example displays fan operation status for a SIP in chassis slot 0:
Router# show platform hardware slot 0 fan status
Table 39 describes the significant fields shown in the display.
Table 39 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 example displays the ingress arbiter settings for all PLIM buffers that are in use for a SIP in chassis slot 0:
Router# show platform hardware slot 0 plim qos input bandwidth
Ingress QOS Scheduling Mode: Strict Priority
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 100000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
Table 40 describes the significant fields shown in the display.
Table 40 show platform hardware slot 0 plim qos input bandwidth Field Descriptions
Field
|
Description
|
Ingress QOS Scheduling Mode
|
Current scheduler operation mode.
|
BW
|
Interface bandwidth in kilobits per second (kb/s).
|
Min BW
|
Guaranteed bandwidth assigned on this interface in Kbps.
|
Excessive Weight
|
Excessive bandwidth assigned on this interface in Kbps.
|
HP Policer BW
|
Bandwidth assigned for processing high-priority traffic on this interface in Kbps.
|
The following example 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).
Router# show platform hardware slot 0 plim statistics
RX IPC Pkts 739 Bytes 54564
TX IPC Pkts 739 Bytes 30752
Table 41 describes the significant fields shown in the display.
Table 41 show platform hardware slot 0 plim statistics Field Descriptions
Field
|
Description
|
RX Pkts
|
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 example displays the byte and packet counters associated with the Enhanced SerDes Interconnect (ESI) links for an ESP. It includes the 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 connected to it with active ESI links. A SIP or RP displays statistics from each ESP.
Router# show platform hardware slot f0 serdes statistics
Pkts High: 0 Low: 0 Bad: 0 Dropped: 0
Bytes High: 0 Low: 0 Bad: 0 Dropped: 0
Qstat count: 0 Flow ctrl count: 25671
Pkts High: 0 Low: 0 Bad: 0 Dropped: 0
Bytes High: 0 Low: 0 Bad: 0 Dropped: 0
Qstat count: 0 Flow ctrl count: 25674
Table 42 describes the significant fields shown in the display.
Table 42 show platform hardware slot f0 serdes statistics Field Descriptions
Field
|
Description
|
From Slot
|
Information on data passed from the indicated processor to the card where the command is run and over the SerDes.
|
To Slot
|
Information on data passed to the indicated processor from the card where the command is run and over the SerDes.
|
Pkts/Bytes High
|
Number of packets and bytes of high priority data payload.
|
Pkts/Bytes Low
|
Number of packets and bytes of low priority data payload.
|
Pkts/Bytes Bad
|
Number of packets received with packet length errors or cyclic redundacy check (CRC) errors.
|
Pkts/Bytes Dropped
|
Number of dropped packets and bytes due to first in, first out (FIFO) overflow.
|
Pkts/Bytes Looped
|
Number of packets looped back in loopback mode.
|
Pkts Error
|
Number of packets with errors.
|
Qstat count
|
Number of packets received in which an ESI link error is detected.
|
Flow ctrl count
|
Number of link-level flow control messages.
|
The following example displays the OIR statistics of SPAs installed in a SIP in chassis slot 0:
Router# show platform hardware slot 0 spa oir-statistics
Table 43 describes the significant fields shown in the display.
Table 43 show platform hardware slot 0 spa oir-statistics Field Descriptions
Field
|
Description
|
SPA OIR requests
|
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 example displays the MCU hardware status and power supply in the slot:
Note
If you use the show platform hardware slot sip mcu status command or the show platform hardware slot sip fan status command onthe Cisco ASR 1000 Series Router, Cisco recommends 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.
Router# show platform hardware slot P0 mcu status
Table 44 describes the significant fields shown in the display.
Table 44 show platform hardware slot mcu status Field Descriptions
Field
|
Description
|
Model ID
|
The 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 a SPA.
|
show platform hardware subslot
|
Displays information about a SPA.
|
show platform hardware subslot
To display information about a Cisco ASR 1000 Series shared port adapter (SPA), use the show platform hardware subslot command in privileged EXEC or diagnostic mode.
show platform hardware subslot slot/card plim
{buffer [settings detail] | qos input bandwidth | spa settings | statistics [internal]}
Syntax Description
slot/
|
Chassis slot where the Cisco ASR 1000 Series SPA interface processor (SIP) is installed.
|
card
|
Secondary slot number of the SIP where the SPA is installed.
|
plim
|
Provides Physical Line Interface Module (PLIM) information.
|
buffer
|
Provides PLIM buffer information (for Cisco Technical Support only).
|
settings detail
|
(Optional) Provides detailed PLIM buffer settings (for Cisco Technical Support only).
|
qos input bandwidth
|
Provides PLIM QoS input bandwidth information.
|
spa settings
|
Provides PLIM SPA settings (for Cisco Technical Support only).
|
statistics
|
Provides PLIM statistics.
|
internal
|
(Optional) Provides PLIM detailed statistics information (for Cisco Technical Support only).
|
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:
Router# show platform hardware subslot 1/0 plim qos input bandwidth
Ingress QOS Scheduling Mode: Strict Priority
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 100000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
BW: 155520 Kbps, Min BW: N/A , Excessive Weight: 155000 Kbps, HP Policer BW:
155520 Kbps
Table 45 describes the significant fields shown in the display.
Table 45 show platform hardware subslot 1/0 plim qos input bandwidth Field Descriptions
Field
|
Description
|
Ingress QOS Scheduling Mode
|
Current scheduler operation mode.
|
BW
|
Interface bandwidth in kilobits per second (kb/s).
|
Min Bw
|
Guaranteed bandwidth assigned on this interface in kb/s.
|
Excessive Weight
|
Excessive bandwidth assigned on this interface in kb/s.
|
HP Policer BW
|
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.
Router# show platform hardware subslot 1/0 plim statistics
RX IPC Pkts 739 Bytes 54564
TX IPC Pkts 739 Bytes 30752
Table 41 describes the significant fields shown in the display.
Table 46 show platform hardware subslot 1/0 plim statistics Field Descriptions
Field
|
Description
|
RX Pkts
|
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.
|
Related Commands
Command
|
Description
|
show platform hardware interface
|
Displays information about an interface.
|
show platform hardware port
|
Displays information about an interface port on a shared port adapter (SPA).
|
show platform hardware slot
|
Displays information about the processor in a chassis slot.
|
show platform hardware transceiver
To display transceiver information on a port, use the show platform hardware transceiver command in EXEC mode.
show platform hardware transceiver {brief | status | config | error | register} [port]
Syntax Description
brief
|
Brief device information.
|
status
|
Device status.
|
config
|
Device configuration.
|
error
|
Device error information.
|
register
|
Device register contents.
|
port
|
Optional. Specifies the port. If you do not select a port, this command will iterate through all ports.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(33)SRD
|
This command was introduced on the Cisco 7600 series routers.
Note This command applies only to the Cisco 7600 series Ethernet Services Plus (ES+) line card.
|
Usage Guidelines
Use this command with the remote command command in EXEC mode.
Examples
The following example shows brief information for port 1.
Router# remote command module 13 show platform hardware transceiver brief 1
Show brief info for port 1:
Vendor name: CISCO-FINISAR
Vendor part number: FTLF8519P2BCL-CS
The following example shows status information for port 1.
Router# remote command module 13 show platform hardware transceiver status 1
Show status info for port 1:
Environmental Information - raw values
Tx voltage: 0 in units of 100uVolt
Tx power: -2 dBm (5441 in units of 0.1 uW)
Rx power: 0 dBm (7712 in units of 0.1 uW)
(AUX1) Laser Temperature: 8704
(AUX2) +3.3V Supply Voltage: 32928
XFP is not soft power down.
XFP doesn't have interrupt(s).
XFP TX laser is not in fault condition.
XFP TX path CDR is locked.
XFP RX path CDR is locked.
Related Commands
Command
|
Description
|
remote command {module num | standby-rp | switch} command
|
Executes a Cisco 7600 series router command directly on the switch console or a specified module without having to log in to the Cisco 7600 series router first.
|
show platform isg memory
To display dynamically allocated memory usage information on the route processor (RP), use the show platform isg memory command in privileged EXEC mode.
show platform isg memory [detail]
Syntax Description
detail
|
(Optional) Displays detailed memory usage information.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(1)S
|
This command was introduced.
|
Examples
This is a sample output of the show platform isg memory command.
Router# show platform isg memory
Allocator-Name In-use/Allocated Count
----------------------------------------------------------------------------
CWAN VRF NODE : 0/65588 ( 0%) [ 0] Chunk
CWAN PLATFORM : 0/20052 ( 0%) [ 0] Chunk
CWAN PPPoE SB : 0/20052 ( 0%) [ 0] Chunk
CWAN PPPOE NOD : 0/65588 ( 0%) [ 0] Chunk
CWAN VRF Sess Cnt : 16384/16436 ( 99%) [ 1]
CWAN MSI Array : 16384/16436 ( 99%) [ 1]
CWAN MSI Elem : 98304/311296 ( 31%) [ 4096]
VRF Pend list Array : 16384/16436 ( 99%) [ 1]
VRF Pend list MSI : 98304/311296 ( 31%) [ 4096]
CWAN slot pid hdl : 60/112 ( 53%) [ 1]
CWAN sess per slot : 2880000/2880780 ( 99%) [ 15]
CWAN test lru hdl : 24/76 ( 31%) [ 1]
CWAN Container HWSB : 56/108 ( 51%) [ 1]
CW Cont swidb SB : 104/208 ( 50%) [ 2]
L4R Rules per : 0/32820 ( 0%) [ 0] Chunk
L4R Srv Grps p : 0/32820 ( 0%) [ 0] Chunk
L4R non-access : 0/65588 ( 0%) [ 0] Chunk
L4R Srv Info : 0/32820 ( 0%) [ 0] Chunk
Table 47 describes the fields shown in the show platform isg memory command display.
Table 47 show platform isg memory
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.
|
Field Descriptions
show platform mgf
To show the details of the multi-gigabit fabric, use the show platform mgf command in priviledged EXEC mode.
show platform mgf [module | statistics cpu]
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
Priviledged 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 show platform mgf command in priviledged EXEC mode. Or, enter the show platform mgf 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
VLAN1 is the default when no other VLAN are listed.
Router# show platform mgf
------------------------------------------------------------
1 ISM*, EHWIC-0*, EHWIC-1*, EHWIC-2*, EHWIC-3*
PVDM-0*, PVDM-1*, PVDM-2*, PVDM-3*, SM-1*
Examples
The following example displays the output for the show platform backplane module command when entered on a Cisco 3945 ISR. Table 48 displays the information code that appears in the output.
Router# show platform mgf module
Registered Module Information
Code: NR - Not Registered, TM - Trust Mode, SP - Scheduling Profile
BL - Buffer Level, TR - Traffic Rate, PT - Pause Threshold
slot vlan type/ID TM SP BL TR PT
---- ---- ---------- ------- --- ------ ----- ----
SM-1 1 SM/6 UP 1 high 1000 high
SM-2 1 SM/6 UP 1 high 1000 high
Table 48 Show Platform Backplane Module Information Code
Code
|
Description
|
NR
|
Not registered
|
TM
|
Trust mode
|
SP
|
Scheduling profile
|
BL
|
Buffer level
|
TR
|
Traffic rate
|
PT
|
Pause threshold
|
The following example displays output for the show platform backplane statistics command when entered on a Cisco 1941 ISR.
Router# show platform mgf statistics
Interface statistics for slot: ISM (port 1)
-----------------------------------------------------
30 second input rate 0 packets/sec
30 second output rate 0 packets/sec
0 packets input, 0 bytes, 0 overruns
Received 0 broadcasts, 0 multicast, 0 unicast 0 runts, 0 giants, 0 jabbers 0 input errors,
0 CRC, 0 fragments, 0 pause input 0 packets output, 0 bytes, 0 underruns 0 broadcast, 0
multicast, 0 unicast 0 late collisions, 0 collisions, 0 deferred 0 bad bytes received, 0
multiple, 0 pause output
Interface statistics for slot: EHWIC-0 (port 2)
-----------------------------------------------------
30 second input rate 13844 packets/sec
30 second output rate 13844 packets/sec
3955600345 packets input, 1596845471340 bytes, 26682 overruns Received 0 broadcasts, 0
multicast, 3955600345 unicast 0 runts, 0 giants, 0 jabbers 0 input errors, 0 CRC, 0
fragments, 0 pause input
3955738564 packets output, 1596886171288 bytes, 0 underruns 0 broadcast, 0 multicast,
3955738564 unicast 0 late collisions, 0 collisions, 0 deferred 0 bad bytes received, 0
multiple, 94883 pause output
Interface statistics for slot: EHWIC-1 (port 3)
-----------------------------------------------------
30 second input rate 13844 packets/sec
30 second output rate 13844 packets/sec
3955973016 packets input, 1598763291608 bytes, 26684 overruns Received 0 broadcasts, 0
multicast, 3955973016 unicast 0 runts, 0 giants, 0 jabbers 0 input errors, 0 CRC, 0
fragments, 0 pause input 3955781430 packets output, 1598708166660 bytes, 0 underruns 0
broadcast, 0 multicast, 3955781430 unicast 0 late collisions, 0 collisions, 0 deferred 0
bad bytes received, 0 multiple, 94987 pause output
The following example displays output for the show platform backplane statistics cpu command when entered on a Cisco 3945 ISR.
Router# show platform mgf statistics cpu
Backplane-GigabitEthernet0/3 is up, line protocol is up
Hardware is PQ3_TSEC, address is 001b.5428.d403 (bia 001b.5428.d403)
MTU 9600 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Full-duplex, 1000Mb/s, media type is internal
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out Interface statistics for CPU:
(port 0)
-----------------------------------------------------
30 second input rate 0 packets/sec
30 second output rate 0 packets/sec
0 packets input, 0 bytes, 0 overruns
Received 0 broadcasts, 0 multicast, 0 unicast 0 runts, 0 giants, 0 jabbers 0 input errors,
0 CRC, 0 fragments, 0 pause input 0 packets output, 0 bytes, 0 underruns 0 broadcast, 0
multicast, 0 unicast 0 late collisions, 0 collisions, 0 deferred 0 bad bytes received, 0
multiple, 0 pause output
Related Commands
Command
|
Description
|
show platform
|
To display platform information, use the show platform command in privileged EXEC mode.
|
show platform software memory
To display memory information for the specified process, use the show platform software memory command in privileged EXEC or diagnostic mode.
show platform software memory [database | messaging] {chassis-manager slot |
cpp-control-process process | cpp-driver process | cpp-ha-server process |
cpp-service-process process | forwarding-manager slot | host-manager slot |
interface-manager slot | ios slot | logger slot | pluggable-services slot | shell-manager slot}
[brief]
Syntax Description
database
|
(Optional) Displays database memory information for the specified process.
|
messaging
|
(Optional) Displays messaging memory information for specified process.
The information displayed is for internal debugging purposes only.
|
chassis-manager slot
|
Displays memory information for the Chassis Manager process in the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SPA Interface Processor (SIP) slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2—Cisco ASR 1000 Series SIP slot 2
• f0—Cisco ASR 1000 Series Embedded Services Processor (ESP) slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series Route Processor (RP) slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
cpp-control-process
|
Displays memory information for the specified Cisco Packet Processor (CPP) Client Control process. Possible process values are:
• cpp active—Active CPP Client Control process
• cpp standby—Standby CPP Client Control process
The information displayed is for internal debugging purposes only.
|
cpp-driver
|
Displays memory information for the specified CPP Driver process. Possible process values are:
• cpp active—Active CPPDriver process
• cpp standby—Standby CPP Driver process
The information displayed is for internal debugging purposes only.
|
cpp-ha-server
|
Displays memory information for the specified CPP High Availability (HA) Server process. Possible process values are:
• cpp active—Active CPP HA Server process
• cpp standby—Standby CPP HA Server process
The information displayed is for internal debugging purposes only.
|
cpp-service-process
|
Displays memory information for the specified CPP Client Service process. Possible process values are:
• cpp active—Active CPP Client Service process
• cpp standby—Standby CPP Client Service process
The information displayed is for internal debugging purposes only.
|
forwarding-manager slot
|
Displays memory information for the Forwarding Manager process in the specified slot. Possible slot values are:
• f0—Cisco ASR 1000 Series ESP slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
host-manager slot
|
Displays memory information for the Host Manager process in the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SIP slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2—Cisco ASR 1000 Series SIP slot 2
• f0—Cisco ASR 1000 Series ESP slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
interface-manager slot
|
Displays memory information for the Interface Manager process in the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SIP slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2— Cisco ASR 1000 Series SIP slot 2
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
ios slot
|
Displays memory information for the IOS process in the specified slot. Possible slot values are:
• 0/0—Cisco ASR 1000 Series SIP slot 0, bay 0
• 0/1—Cisco ASR 1000 Series SIP slot 0, bay 1
• 0/2—Cisco ASR 1000 Series SIP slot 0, bay 2
• 0/3—Cisco ASR 1000 Series SIP slot 0, bay 3
• 1/0—Cisco ASR 1000 Series SIP slot 1, bay 0
• 1/1—Cisco ASR 1000 Series SIP slot 1, bay 1
• 1/2—Cisco ASR 1000 Series SIP slot 1, bay 2
• 1/3—Cisco ASR 1000 Series SIP slot 1, bay 3
• 2/0—Cisco ASR 1000 Series SIP slot 2, bay 0
• 2/1—Cisco ASR 1000 Series SIP slot 2, bay 1
• 2/2—Cisco ASR 1000 Series SIP slot 2, bay 2
• 2/3—Cisco ASR 1000 Series SIP slot 2, bay 3
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
logger slot
|
Displays memory information for the logger process in the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SIP slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2—Cisco ASR 1000 Series SIP slot 2
• f0—Cisco ASR 1000 Series ESP slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
pluggable-services slot
|
Displays memory information for the pluggable-services process in the specified slot. Possible slot values are:
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
shell-manager slot
|
Displays memory information for the Shell Manager process in the specified slot. Possible slot values are:
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
brief
|
(Optional) Displays abbreviated memory information for the specified process.
|
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
The specification of the database and brief keywords are optional.
The specification of a process and slot are required.
Examples
The following example displays memory information for the Forwarding Manager process for Cisco ASR 1000 Series RP slot 0:
Router# show platform software memory forwarding-manager r0
allocated: 900, requested: 892, overhead: 8
Allocations: 2, failed: 0, frees: 1
allocated: 117379, requested: 117059, overhead: 320
Allocations: 46, failed: 0, frees: 6
allocated: 9264, requested: 9248, overhead: 16
Allocations: 3, failed: 0, frees: 1
allocated: 127543, requested: 127199, overhead: 344
Allocations: 51, failed: 0, frees: 8
Table 49 describes the significant fields shown in the display.
Table 49 show platform software memory Field Descriptions
Field
|
Description
|
Module:
|
Name of submodule.
|
allocated:
|
Memory, allocated in bytes.
|
requested:
|
Number of bytes requested by application.
|
overhead:
|
Allocation overhead.
|
Allocations:
|
Number of discrete allocation event attempts.
|
failed:
|
Number of allocation attempts that were attempted, but failed.
|
frees:
|
Number of free events.
|
The following example displays abbreviated (brief keyword) memory information for the Chassis Manager process for Cisco ASR 1000 Series ESP slot 0:
Router# show platform software memory chassis-manager f0 brief
module allocated requested allocs frees
------------------------------------------------------------------------
Summary 497816 495344 323 14
eventutil 68546 66146 312 12
Table 50 describes the significant fields shown in the brief keyword display.
Table 50 show platform software memory brief Field Descriptions
Field
|
Description
|
module
|
Name of submodule.
|
allocated
|
Memory, allocated in bytes.
|
requested
|
Number of bytes requested by application.
|
allocs
|
Number of discrete allocation event attempts.
|
frees
|
Number of free events.
|
show platform software mount
To display the mounted file systems, both physical and virtual, for a Cisco ASR 1000 Series SPA Interface Processor (SIP), Cisco ASR 1000 Series Embedded Services Processor (ESP), or Cisco ASR 1000 Series Route Processor (RP), use the show platform software mount command in privileged EXEC or diagnostic mode.
show platform software mount [slot [brief]]
Syntax Description
slot
|
(Optional) Displays mounted file systems for the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SIP slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2—Cisco ASR 1000 Series SIP slot 2
• f0—Cisco ASR 1000 Series ESP slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series RP slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
brief
|
(Optional) Displays abbreviated mounted file system information.
|
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
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:
Router# show platform software mount
Filesystem Used Available Use% Mounted on
/dev/bootflash1 298263 42410 88% /bootflash
/dev/harddisk1 609208 4025132 14% /misc/scratch
/dev/loop1 28010 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop2 26920 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop3 48236 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop4 6134 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop5 43386 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop6 30498 0 100% /tmp/sw/mount/2007-10-14_...
/dev/loop7 14082 0 100% /tmp/sw/mount/2007-10-14_...
/proc/bus/usb 0 0 - /proc/bus/usb
/dev/mtdblock1 460 1588 23% /obfl
automount(pid4165) 0 0 - /vol
The following example displays mounted file systems for the Cisco ASR 1000 Series ESP in ESP slot 0:
Router# show platform software mount f0
Filesystem Used Available Use% Mounted on
none 10864 507124 3% /dev
/dev/loop1 41418 0 100% /tmp/sw/fp/0/0/fp/mount
none 10864 507124 3% /dev
/proc/bus/usb 0 0 - /proc/bus/usb
/dev/mtdblock1 504 1544 25% /obfl
automount(pid3210) 0 0 - /misc1
The following example displays mounted file systems for the active Cisco ASR 1000 Series RP:
Router# show platform software mount rp active
Filesystem Used Available Use% Mounted on
/dev/bootflash1 256809 83864 76% /bootflash
/dev/harddisk1 252112 4382228 6% /misc/scratch
/dev/loop1 30348 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop2 28394 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop3 42062 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop4 8384 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop5 41418 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop6 21612 0 100% /tmp/sw/mount/2007-09-27_...
/dev/loop7 16200 0 100% /tmp/sw/mount/2007-09-27_...
/proc/bus/usb 0 0 - /proc/bus/usb
/dev/mtdblock1 484 1564 24% /obfl
automount(pid4004) 0 0 - /vol
Table 51 describes the significant fields shown in the SIP slot (0, 1, or 2) displays.
Table 51 show platform software mount SIP slot Field Descriptions
Field
|
Description
|
Filesystem
|
Logical name of the file system device.
|
Used
|
Number of 1Kb blocks used.
|
Available
|
Number of free 1Kb blocks available.
|
Use%
|
Percentage of 1Kb blocks used of the total available.
|
Mounted on
|
Canonical path to the mounted file system.
|
The following example displays abbreviated (brief keyword) mounted file system information for Cisco ASR 1000 Series SIP slot 0:
Router# show platform software mount 0 brief
Location : /tmp/sw/cc/0/0/cc/mount
Mount point: /proc/bus/usb
Mount point: /dev/mtdblock1
Options : rw,noatime,nodiratime
Mount point: automount(pid3199)
Options : rw,fd=5,pgrp=3199,timeout=60,minproto=2,maxproto=4,indirect
Table 52 describes the significant fields shown in the brief keyword display.
Table 52 show platform software mount brief Field Descriptions
Field
|
Description
|
Mount point:
|
Logical name of the file system device.
|
Type:
|
File system type.
|
Location:
|
Canonical path to the mounted file system.
|
Options:
|
Mount point type-specific flags and settings.
|
show platform software process list
To display a list of the processes running in a given slot, use the show platform software process list command in privileged EXEC or diagnostic mode.
show platform software process list slot [name process-name | process-id process-id | summary]
Syntax Description
slot
|
Displays running process information for the specified slot. Possible slot values are:
• 0—Cisco ASR 1000 Series SPA Interface Processor (SIP) slot 0
• 1—Cisco ASR 1000 Series SIP slot 1
• 2—Cisco ASR 1000 Series SIP slot 2
• f0—Cisco ASR 1000 Series Embedded Services Processor (ESP) slot 0
• f1—Cisco ASR 1000 Series ESP slot 1
• fp active—Active Cisco ASR 1000 Series ESP
• fp standby—Standby Cisco ASR 1000 Series ESP
• r0—Cisco ASR 1000 Series Route Processor (RP) slot 0
• r1—Cisco ASR 1000 Series RP slot 1
• rp active—Active Cisco ASR 1000 Series RP
• rp standby—Standby Cisco ASR 1000 Series RP
|
name process-name
|
(Optional) Displays information for the specified process name.
|
process-id process-id
|
(Optional) Displays information for the specified process ID.
|
summary
|
(Optional) Displays summary process information for the running host.
|
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
The name and process-id keywords can be used to narrow the process list display down to specific processes.
The summary keyword can be used to display summary information about running processes.
Examples
The following example displays information about running processes for Cisco ASR 1000 Series SIP slot 0:
Router# show platform software process list 0
Name Pid PPid Group Id Status Priority Size
------------------------------------------------------------------------------
portmap 1404 1 1404 S 20 2076672
portmap 1406 1 1406 S 20 2076672
udevd 2104 1 2104 S 16 1974272
jffs2_gcd_mtd1 2796 1 1 S 30 0
klogd 3093 1 3093 S 20 1728512
automount 3199 1 3199 S 20 2396160
xinetd 3214 1 3214 S 20 3026944
xinetd 3216 1 3216 S 20 3026944
pvp.sh 3540 1 3540 S 20 3678208
inotifywait 3575 3540 3575 S 20 1900544
pman.sh 3614 3540 3614 S 20 3571712
pman.sh 3714 3540 3714 S 20 3571712
btrace_rotate.s 3721 3614 3721 S 20 3133440
agetty 3822 1 3822 S 20 1720320
mcp_chvrf.sh 3823 1 3823 S 20 2990080
sntp 3824 1 3824 S 20 2625536
issu_switchover 3825 1 3825 S 20 3899392
xinetd 3827 3823 3823 S 20 3026944
cmcc 3862 3714 3862 S 20 26710016
pman.sh 3883 3540 3883 S 20 3571712
pman.sh 4014 3540 4014 S 20 3575808
hman 4020 3883 4020 R 20 19615744
imccd 4114 4014 4114 S 20 31539200
inotifywait 4196 3825 3825 S 20 1896448
pman.sh 4351 3540 4351 S 20 3575808
plogd 4492 4351 4492 S 20 22663168
inotifywait 4604 3721 4604 S 20 1900544
Table 53 describes the significant fields shown in the display.
Table 53 show platform software process list Field Descriptions
Field
|
Description
|
Name
|
Name of the process.
|
Pid
|
Process ID.
|
PPid
|
Parent Process ID.
|
Group Id
|
Process group ID.
|
Status
|
Process status.
|
Priority
|
Process priority.
|
Size
|
Virtual memory size (in bytes).
|
The following example displays information about a specific named process for Cisco ASR 1000 Series SIP slot 0:
Router# show platform software process list 0 name sleep
Resident limit : 4294967295
The following example displays information about a specific process identifier for Cisco ASR 1000 Series SIP slot 0:
Router# show platform software process list 0 process-id 1
Resident limit : 4294967295
Table 54 describes the significant fields shown in the name and process-id keyword displays.
Table 54 show platform software process list name and process-id Field Descriptions
Field
|
Description
|
Name
|
Name of the process.
|
Process id
|
Process ID.
|
Parent process id
|
Parent process ID.
|
Group id
|
Process group ID.
|
Status
|
Process status.
|
Session id
|
Process session ID.
|
User time
|
Time (in seconds) spent in user mode.
|
Kernel time
|
Time (in seconds) spent in kernel mode.
|
Priority
|
Process priority.
|
Virtual bytes
|
Virtual memory size (in bytes).
|
Resident pages
|
Resident page size.
|
Resident limit
|
Current limit on Resident pages.
|
Minor page faults
|
Number of minor page faults.
|
Major page faults
|
Number of major page faults.
|
The following example displays process summary information for Cisco ASR 1000 Series SIP slot 0:
Router# show platform software process list 0 summary
Total number of processes: 54
Virtual memory : 587894784
Minor page faults: 149098
Table 55 describes the significant fields shown in the summary keyword display.
Table 55 show platform software process list summary Field Descriptions
Field
|
Description
|
Total number of processes
|
Total number of processes in all possible states.
|
Running
|
Number of processes in the running state.
|
Sleeping
|
Number of processes in the sleeping state.
|
Disk sleeping
|
Number of processes in the disk-sleeping state.
|
Zombies
|
Number of processes in the zombie state.
|
Stopped
|
Number of processes in the stopped state.
|
Paging
|
Number of processes in the paging state.
|
Up time
|
System Up time (in seconds).
|
Idle time
|
System Idle time (in seconds).
|
User time
|
System time (in seconds) spent in user mode.
|
Kernel time
|
System time (in seconds) spent in kernel mode.
|
Virtual memory
|
Virtual memory size (in bytes).
|
Pages resident
|
Resident page size.
|
Major page faults
|
Number of major page faults.
|
Minor page faults
|
Number of minor page faults.
|
Architecture
|
System CPU architecture: PowerPC (ppc).
|
Memory (kB)
|
System memory heading.
|
Physical
|
Total physical memory (in kilobytes).
|
Total
|
Total available memory (in kilobytes). This value represents the physical memory available for kernel use.
|
Used
|
Used memory (in kilobytes).
|
Free
|
Free memory (in kilobytes).
|
Active
|
Most recently used memory (in kilobytes).
|
Inactive
|
Memory (in kilobytes) that has been less recently used. It is more eligible to be reclaimed for other purposes.
|
Inact-dirty
|
Memory (in kilobytes) that may need to be written to persistent store (cache or disk).
|
Inact-clean
|
Memory (in kilobytes) that is readily available for re-use.
|
Dirty
|
Memory (in kilobytes) that is waiting to get written back to the disk.
|
AnonPages
|
Memory (in kilobytes) that is allocated when a process requests memory from the kernel via the malloc() system call. This memory has no file backing on disk.
|
Bounce
|
Memory (in kilobytes) that is allocated to bounce buffers.
|
Cached
|
Amount of physical RAM (in kilobytes) used as cache memory.
|
Commit Limit
|
Total amount of memory (in kilobytes) currently available to be allocated on the system. This limit is only adhered to if strict overcommit accounting is enabled.
|
Committed As
|
Total amount of memory (in kilobytes) presently allocated on the system. The committed memory is a sum of all of the memory that has been allocated by processes, even if it has not been used by them as of yet.
|
High Total
|
Total amount of memory (in kilobytes) that is not directly mapped into kernel space. The High Total value can vary based on the type of kernel used.
|
High Free
|
Amount of free memory (in kilobytes) that is not directly mapped into kernel space. The High Free value can vary based on the type of kernel used.
|
Low Total
|
Total amount of memory (in kilobytes) that is directly mapped into kernel space. The Low Total value can vary based on the type of kernel used.
|
Low Free
|
Amount of free memory (in kilobytes) that is directly mapped into kernel space. The Low Free value can vary based on the type of kernel used.
|
Mapped
|
Total amount of memory (in kilobytes) that has been used to map devices, files, or libraries using the mmap command.
|
NFS Unstable
|
Total amount of memory (in kilobytes) used for unstable NFS pages. Unstable NFS pages are pages that have been written into the page cache on the server, but have not yet been synchronized to disk.
|
Page Tables
|
Total amount of memory (in kilobytes) dedicated to the lowest page table level.
|
Slab
|
Total amount of memory (in kilobytes) used by the kernel to cache data structures for its own use.
|
VMalloc Chunk
|
Largest contiguous block of available virtual address space (in kilobytes) that is free.
|
VMalloc Total
|
Total amount of memory (in kilobytes) of total allocated virtual address space.
|
VMalloc Used
|
Total amount of memory (in kilobytes) of used virtual address space.
|
Writeback
|
Memory (in kilobytes) that is actively being written back to the disk.
|
Swap (kB)
|
Swap memory heading.
|
Total
|
Total swap memory (in kilobytes).
|
Used
|
Used swap memory (in kilobytes).
|
Free
|
Free swap memory (in kilobytes).
|
Cached
|
Cached swap memory (in kilobytes).
|
Buffers (kB)
|
Buffers heading.
|
Load Average
|
Indicators of system load.
|
1-Min
|
Average number of processes running for the last minute.
|
5-Min
|
Average number of processes running for the last 5 minutes.
|
15-Min
|
Average number of processes running for the last 15 minutes.
|
show platform software status control-processor
To display status information for the control processors, use the show platform software status control-processor command in privileged EXEC or diagnostic mode.
show platform software status control-processor [brief]
Syntax Description
brief
|
(Optional) Displays summary status information for the control processors.
|
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.
|
Cisco IOS XE Release 2.2
|
This command was modified. The brief keyword was added.
|
Usage Guidelines
Control processes consist of Embedded Services Processors (ESPs), Route Processors (RPs), and SPA Interface Processors (SIPs).
Use the show platform software status control-processor command to provide a quick view of the health of the system as a whole with regards to memory and CPU usage on each processor.
The CPU usage output reflects the relative percentage of CPU usage during the latest two seconds instead of the cumulative percent usage over the entire up-time.
All control processors should show a status of Healthy. Other possible status values are Warning and Critical. Warning indicates that the router is operational but that the operating level should be reviewed. Critical implies that the router is near failure.
If you see a status of Warning or Critical, take the following actions:
•
Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services.
•
Reduce the number of routes and adjacencies, limit the number of ACLs and other rules, reduce the number of VLANs, and so on.
Examples
The following example displays status information for the control processors:
Router# show platform software status control-processor
RP0: online, statistics updated 7 seconds ago
1-Min: 0.16, status: healthy, under 5.00
5-Min: 0.16, status: healthy, under 5.00
15-Min: 0.12, status: healthy, under 5.00
Used: 1320804 (31%), status: healthy, under 90%
Free: 2412212 (58%), status: healthy, over 10%
Committed: 1889524 (45%), status: healthy, under 90%
ESP0: online, statistics updated 7 seconds ago
1-Min: 0.00, status: healthy, under 5.00
5-Min: 0.00, status: healthy, under 5.00
15-Min: 0.00, status: healthy, under 5.00
Used: 532492 (50%), status: healthy, under 90%
Free: 452504 (43%), status: healthy, over 10%
Committed: 1724096 (164%), status: healthy, under 300%
SIP0: online, statistics updated 10 seconds ago
1-Min: 0.00, status: healthy, under 5.00
5-Min: 0.00, status: healthy, under 5.00
15-Min: 0.00, status: healthy, under 5.00
Used: 434476 (82%), status: healthy, under 90%
Free: 45408 (8%), status: warning, under 10%
Committed: 202508 (38%), status: healthy, under 90%
SIP1: online, statistics updated 10 seconds ago
1-Min: 0.00, status: healthy, under 5.00
5-Min: 0.00, status: healthy, under 5.00
15-Min: 0.00, status: healthy, under 5.00
Used: 430384 (82%), status: healthy, under 90%
Free: 49500 (9%), status: warning, under 10%
Committed: 202512 (38%), status: healthy, under 90%
The following example displays summary status information for the control processors with brief keyword:
Router# show platform software status control-processor brief
Slot Status 1-Min 5-Min 15-Min
RP0 Healthy 0.25 0.30 0.44
RP1 Healthy 0.31 0.19 0.12
ESP0 Healthy 0.01 0.05 0.02
ESP1 Healthy 0.03 0.05 0.01
SIP1 Healthy 0.15 0.07 0.01
SIP2 Healthy 0.03 0.03 0.00
Slot Status Total Used (Pct) Free (Pct) Committed (Pct)
RP0 Healthy 3722408 2514836 (60%) 1207572 (29%) 1891176 (45%)
RP1 Healthy 3722408 2547488 (61%) 1174920 (28%) 1889976 (45%)
ESP0 Healthy 2025468 1432088 (68%) 593380 (28%) 3136912 (149%)
ESP1 Healthy 2025468 1377980 (65%) 647488 (30%) 3084412 (147%)
SIP1 Healthy 480388 293084 (55%) 187304 (35%) 148532 (28%)
SIP2 Healthy 480388 273992 (52%) 206396 (39%) 93188 (17%)
Slot CPU User System Nice Idle IRQ SIRQ IOwait
RP0 0 30.12 1.69 0.00 67.63 0.13 0.41 0.00
RP1 0 21.98 1.13 0.00 76.54 0.04 0.12 0.16
ESP0 0 13.37 4.77 0.00 81.58 0.07 0.19 0.00
ESP1 0 5.76 3.56 0.00 90.58 0.03 0.05 0.00
SIP1 0 3.79 0.13 0.00 96.04 0.00 0.02 0.00
SIP2 0 3.50 0.12 0.00 96.34 0.00 0.02 0.00
Table 56 describes the significant fields shown in the display.
Table 56 show platform software status control-processor Field Descriptions
Field
|
Description
|
processor-name: online
|
Name of the online control processor to which the statistics that follow apply.
|
statistics updated x seconds ago
|
Time (in seconds) when the statistics were last updated.
|
Load Average:
|
Summary status indicator of the overall control processor load average. This value is derived from the "5-Min" load average.
|
1-Min: / status:
|
One-minute load average on the control processor and status indicator.
|
5-Min: / status:
|
Five-minute load average on the control processor and status indicator.
|
15-Min: / status:
|
Fifteen-minute load average on the control processor and status indicator.
|
Memory (kb):
|
Summary status indicator of the overall control processor memory usage. This value signals if any of the individual memory values below are in critical or warning status.
|
Total:
|
Total memory (in kilobytes) on the control processor.
|
Used: xxxxxx (pp%) / status:
|
Total used memory (in kilobytes) on the control processor (xxxxxx), percentage of used memory on the control processor (pp%), and status indicator.
|
Free: xxxxxx (pp%) / status:
|
Total free memory (in kilobytes) on the control processor (xxxxxx), percentage of free memory on the control processor (pp%), and status indicator.
|
Committed: xxxxxx (pp%) / status:
|
Total committed memory (in kilobytes) on the control processor (xxxxxx), percentage of committed memory on the control processor (pp%), and status indicator.
|
CPU Utilization:
|
Percentage of time that the CPU is busy.
|
CPU:
|
Allocated processor.
|
User:
|
Non-Linux kernel processes.
|
System:
|
Linux kernel process.
|
Nice:
|
Low priority processes.
|
Idle:
|
Percentage of time that the CPU was inactive.
|
IRQ:
|
Interrupts.
|
SIRQ:
|
System interrupts.
|
IOwait:
|
Percentage of time that the CPU was waiting for I/O.
|
Related Commands
Command
|
Description
|
show platform software process list
|
Displays a list of the processes running in a given slot.
|
show platform software tech-support
To display system information or create a technical support information tar file for Cisco Technical Support, use the show platform software tech-support command in privileged EXEC or diagnostic mode.
show platform software tech-support [file {bootflash:filename.tgz | fpd:filename.tgz |
harddisk:filename.tgz | obfl:filename.tgz | stby-bootflash:filename.tgz |
stby-harddisk:filename.tgz | stby-obfl:filename.tgz | stby-usb0:filename.tgz |
stby-usb1:filename.tgz}]
Syntax Description
file
|
(Optional) Creates a technical support information tar file for the specified destination file path.
|
bootflash:filename.tgz
|
Creates a technical support information tar file for the boot flash memory file system on the active RP.
|
fpd:filename.tgz
|
Creates a technical support information tar file for the field-programmable device (FPD) image package on the active RP. The information displayed is for internal debugging puposes only.
|
harddisk:filename.tgz
|
Creates a technical support information tar file for the hard disk file system on the active RP.
|
obfl:filename.tgz
|
Creates a technical support information tar file for the file system for Onboard Failure Logging (obfl) files. The information displayed is for internal debugging puposes only.
|
stby-bootflash: filename.tgz
|
Creates a technical support information tar file for the boot flash memory file system on the standby RP. The information displayed is for internal debugging puposes only.
|
stby-harddisk: filename.tgz
|
Creates a technical support information tar file for the hard disk file system on the standby RP. The information displayed is for internal debugging puposes only.
|
stby-obfl:filename.tgz
|
Creates a technical support information tar file for the Onboard Failure Logging (obfl) files on the standby RP. The information displayed is for internal debugging puposes only.
|
stby-usb0:filename.tgz
|
Creates a technical support information tar file for Universal Serial Bus (USB) memory. The information displayed is for internal debugging puposes only.
|
stby-usb1:filename.tgz
|
Creates a technical support information tar file for Universal Serial Bus (USB) memory. The information displayed is for internal debugging puposes only.
|
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
If the file keyword is specified, the specification of the bootflash: or harddisk: keyword and filename is required.
The show platform software tech-support command without a destination file path specification returns a large volume of information in a short period of time. You should save the output of the show platform software tech-support command in a log file to send to Cisco Technical Support for analysis.
Examples
The following example displays system information for Cisco Technical Support:
Router# show platform software tech-support
---- show version installed -----
Type: provisioning file, Version: unknown
Provisioned on: RP0, Status: active
File: packages.conf.super
Modified: 2007-11-07 15:06:12.212303000 +0000
SHA1 (header): d929d995d5ba2d3dedf67137c3e0e321b1727d7b
SHA1 (calculated): d929d995d5ba2d3dedf67137c3e0e321b1727d7b
SHA1 (external): a16881b6a7e3a5593b63bf211f72b8af9c534063
instance address : 0X890DE9B4
fast failover address : 00000000
instance address : 0X890DE9B8
fast failover address : 00000000
instance address : 0X890DE9BC
fast failover address : 00000000
Note
The show platform software tech-support command returns a large volume of information in a short period of time. The example above has been abbreviated for the purposes of this description.
The following example creates a technical support information tar file for the boot flash memory file system on the active RP:
Router# show platform software tech-support file bootflash:tech_support_output.tgz
Running tech support command set; please wait...
Creating file 'bootflash:target_support_output.tgz.tgz' ...
File 'bootflash:target_support_output.tgz.tgz' created successfully
The following example creates a technical support information tar file for the hard disk file system on the active RP:
Router# show platform software tech-support file harddisk:tech_support_output.tgz
Running tech support command set; please wait...
Creating file 'harddisk:tech_support_ouput.tgz.tgz' ...
File 'harddisk:tech_support_ouput.tgz.tgz' created successfully
show platform time-source
To display the platform time-source details configured, use the show platform time-source command in the Privileged Exec mode.
show platform time-source
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.1(2)S
|
This command was introduced on the Cisco 7600 series routers.
|
Usage Guidelines
The show platform time-source command displays the platform time source configuration.
Examples
This example displays the show platform time source output:
Router#show platform time-source
Master IP Address : 200.1.1.2
Slave IP Address : 60.60.60.60
UDP Destination Port : 320
Control packets sent : 21
Related Commands
Command
|
Description
|
platform time-source
|
Initiates the Time of Day (ToD) synchroniztion on a line card.
|
show plim fpga
To display details gathered from the registers of the internal FPGA (Field Programmable Gate Array) located in the PLIM (Physical Layer Interface Module) section of the line card, use the show plim fpga command in privileged EXEC mode.
show plim fpga
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(33)S4
|
This command was introduced.
|
Usage Guidelines
This command helps you to troubleshoot datapath failures and get the datapath counters on Shiver FPGA.
The following information is available:
•
Rx packet counter
•
Tx packet counter
•
Rx Error Counter
•
Status and control register
•
Door bell register status
•
FPGA Binary image revision number
•
Whether loop back is enabled
•
Whether Ingress and Egress paths are enabled
Examples
The following example shows how to display the Shiver FPGA details:
FPGA Doorbell Register : 0x00
FGPA binary image Revsion : 0xDD
FPGA Datapath Ctrl Reg : 0x000B
FPGA is Enabled in Eggress Direction
FGPA is Enabled in Ingress Direction
======== Output from Tofab755 =======
FPGA Control and Status Register : 0x028104dd
FPGA Rx Packet Count : 0x000000cc
FPGA Tx Packet Count : 0x000000cb
FPGA Rx Packet Error Count : 0x0008ffff
Table 57 describes significant fields shown in the display.
Table 57 show plim fpga Field Descriptions
Field
|
Description
|
FPGA Doorbell Register
|
Line card's version of mailbox doorbell register.
|
FGPA binary image Revision
|
FPGA image version.
|
FPGA Datapath Ctrl Reg
|
Indicates whether the ingress and eggress paths are enabled or disabled.
|
Control and Status Register
|
A 32-bit read-write register that provides the MPC8260 processor with interrupt mask control, interrupt status, Rx Error status, and the FPGA revision ID.
|
Rx Packet Count
|
The number of packets received from the FREEDM-336 in the receive direction.
This 32-bit count value saturates at 0xFFFF_FFFF. The counter is cleared when a write cycle is detected.
|
Tx Packet Count
|
The number of packets transmitted to the FREEDM-336.
This 32-bit count value saturates at 0xFFFF_FFFF. The counter is cleared when a write cycle is detected.
|
Rx Packet Error Count
|
The number of packets with errors received from the FREEDM-336 in the receive direction.
In this 32-bit counter, the 16 bit MSB (Most Significant Bit) indicates the errors that saturate after the value reaches FFFF. The value of LSB (Least Significant Bit) 16 bits will always be FFFF.
|
show policy-map interface
To display the statistics and the configurations of the input and output policies that are attached to an interface, use the show policy-map interface command in user EXEC or privileged EXEC mode.
ATM Shared Port Adapters
show policy-map interface slot/subslot/port[.subinterface]
Cisco 3660, 3845, 7200, 7400, 7500, and Cisco ASR 1000 Series Routers
show policy-map interface [type access-control] type number [vc [vpi/] vci] [dlci dlci]
[input | output] [class class-name]
Cisco 6500 Series Switches
show policy-map interface [interface-type interface-number | vlan vlan-id] [detailed]
[{input | output} [class class-name]]
show policy-map interface [port-channel channel-number [class class-name]]
Cisco 7600 Series Routers
show policy-map interface [interface-type interface-number | null 0 | vlan vlan-id]
[input | output]
Cisco CMTS Routers
show policy-map interface interface-type slot/subslot/port
Syntax Description
slot
|
(CMTS and ATM shared port adapter only) Chassis slot number. See the appropriate hardware manual for slot information. For SIPs, see the platform-specific SPA hardware installation guide or the corresponding "Identifying Slots and Subslots for SIPs and SPAs" topic in the platform-specific SPA software configuration guide.
|
/subslot
|
(CMTS and ATM shared port adapter only) Secondary slot number on an SPA interface processor (SIP) where a SPA is installed. See the platform-specific SPA hardware installation guide and the corresponding "Specifying the Interface Address on an SPA" topic in the platform-specific SPA software configuration guide for subslot information.
|
/port
|
(CMTS and ATM shared port adapter only) Port or interface number. See the appropriate hardware manual for port information. For SPAs, see the corresponding "Specifying the Interface Address" topics in the platform-specific SPA software configuration guide.
|
.subinterface
|
(ATM shared port adapter only—Optional) Subinterface number. The number that precedes the period must match the number to which this subinterface belongs. The range is 1 to 4,294,967,293.
|
type access-control
|
(Optional) Displays class maps configured to determine the exact pattern to look for in the protocol stack of interest.
|
type
|
Type of interface or subinterface whose policy configuration is to be displayed.
|
number
|
Port, connector, or interface card number.
|
vc
|
(Optional) For ATM interfaces only, shows the policy configuration for a specified PVC.
|
vpi/
|
(Optional) ATM network virtual path identifier (VPI) for this permanent virtual circuit (PVC). On the Cisco 7200 and 7500 series routers, this value ranges from 0 to 255.
The vpi and vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.
The absence of both the forward slash (/) and a vpi value defaults the vpi value to 0. If this value is omitted, information for all virtual circuits (VCs) on the specified ATM interface or subinterface is displayed.
|
vci
|
(Optional) ATM network virtual channel identifier (VCI) for this PVC. This value ranges from 0 to 1 less than the maximum value set for this interface by the atm vc-per-vp command. Typically, the lower values 0 to 31 are reserved for specific traffic (F4 Operation, Administration, and Maintenance [OAM], switched virtual circuit [SVC] signaling, Integrated Local Management Interface [ILMI], and so on) and should not be used.
The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the ATM network, because it has local significance only.
The vpi and vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.
|
dlci
|
(Optional) Indicates a specific PVC for which policy configuration will be displayed.
|
dlci
|
(Optional) A specific data-link connection identifier (DLCI) number used on the interface. Policy configuration for the corresponding PVC will be displayed when a DLCI is specified.
|
input
|
(Optional) Indicates that the statistics for the attached input policy will be displayed.
|
output
|
(Optional) Indicates that the statistics for the attached output policy will be displayed.
|
class class-name
|
(Optional) Displays the QoS policy actions for the specified class.
|
interface-type
|
(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
|
interface-number
|
(Optional) Module and port number; see the "Usage Guidelines" section for valid values.
|
vlan vlan-id
|
(Optional) Specifies the VLAN ID; valid values are from 1 to 4094.
|
detailed
|
(Optional) Displays additional statistics.
|
port-channel channel-number
|
(Optional) Displays the EtherChannel port-channel interface.
|
null 0
|
(Optional) Specifies the null interface; the only valid value is 0.
|
Command Default
This command displays the packet statistics of all classes that are configured for all service policies on the specified interface or subinterface or on a specific permanent virtual circuit (PVC) on the interface.
The absence of both the forward slash (/) and a vpi value defaults the vpi value to 0. If this value is omitted, information for all virtual circuits (VCs) on the specified ATM interface or subinterface is displayed.
ATM Shared Port Adapter
When used with the ATM shared port adapter, this command has no default behavior or values.
Command Modes
Privileged EXEC (#)
ATM Shared Port Adapter
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.0(5)XE
|
This command was integrated into Cisco IOS Release 12.0(5)XE.
|
12.0(7)S
|
This command was integrated into Cisco IOS Release 12.0(7)S.
|
12.0(28)S
|
This command was modified for the QoS: Percentage-Based Policing feature to include milliseconds when calculating the committed (conform) burst (bc) and excess (peak) burst (be) sizes.
|
12.1(1)E
|
This command was integrated into Cisco IOS Release 12.1(1)E.
|
12.1(2)T
|
This command was modified to display information about the policy for all Frame Relay PVCs on the interface or, if a DLCI is specified, the policy for that specific PVC. This command was also modified to display the total number of packets marked by the quality of service (QoS) set action.
|
12.1(3)T
|
This command was modified to display per-class accounting statistics.
|
12.2(4)T
|
This command was modified for two-rate traffic policing and can display burst parameters and associated actions.
|
12.2(8)T
|
This command was modified for the Policer Enhancement—Multiple Actions feature and the WRED—Explicit Congestion Notification (ECN) feature.
For the Policer Enhancement—Multiple Actions feature, the command was modified to display the multiple actions configured for packets conforming to, exceeding, or violating a specific rate.
For the WRED—Explicit Congestion Notification (ECN) feature, the command displays ECN marking information.
|
12.2(13)T
|
The following modifications were made:
• This command was modified for the Percentage-Based Policing and Shaping feature.
• This command was modified for the Class-Based RTP and TCP Header Compression feature.
• This command was modified as part of the Modular QoS CLI (MQC) Unconditional Packet Discard feature. Traffic classes in policy maps can now be configured to discard packets belonging to a specified class.
• This command was modified to display the Frame Relay DLCI number as a criterion for matching traffic inside a class map.
• This command was modified to display Layer 3 packet length as a criterion for matching traffic inside a class map.
• This command was modified for the Enhanced Packet Marking feature. A mapping table (table map) can now be used to convert and propagate packet-marking values.
|
12.2(14)SX
|
This command was modified. Support for this command was introduced on Cisco 7600 series routers.
|
12.2(15)T
|
This command was modified to display Frame Relay voice-adaptive traffic-shaping information.
|
12.2(17d)SXB
|
This command was implemented on the Supervisor Engine 2 and integrated into Cisco IOS Release 12.2(17d)SXB.
|
12.3(14)T
|
This command was modified to display bandwidth estimation parameters.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE. This command was modified to display aggregate WRED statistics for the ATM shared port adapter. Note that changes were made to the syntax, defaults, and command modes. These changes are labelled "ATM Shared Port Adapter."
|
12.4(4)T
|
This command was modified. The type access-control keywords were added to support flexible packet matching.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB, and the following modifications were made:
• This command was modified to display either legacy (undistributed processing) QoS or hierarchical queueing framework (HQF) parameters on Frame Relay interfaces or PVCs.
• This command was modified to display information about Layer 2 Tunnel Protocol Version 3 (L2TPv3) tunnel marking.
|
12.2(31)SB2
|
The following modifications were made:
• This command was enhanced to display statistical information for each level of priority service configured and information about bandwidth-remaining ratios, and this command was implemented on the Cisco 10000 series router for the PRE3.
• This command was modified to display statistics for matching packets on the basis of VLAN identification numbers. As of Cisco IOS Release 12.2(31)SB2, matching packets on the basis of VLAN identification numbers is supported on Cisco 10000 series routers only.
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRC.
|
12.4(15)T2
|
This command was modified to display information about Generic Routing Encapsulation (GRE) tunnel marking.
Note As of this release, GRE-tunnel marking is supported on the Cisco MGX Route Processor Module (RPM-XF) platform only.
|
12.2(33)SB
|
This command was modified to display information about GRE-tunnel marking, and support for the Cisco 7300 series router was added.
|
Cisco IOS XE 2.1
|
This command was integrated into Cisco IOS XE Release 2.1 and was implemented on the Cisco ASR 1000 series router.
|
12.4(20)T
|
This command was modified. Support was added for hierarchical queueing framework (HQF) using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
|
12.2(33)SXI
|
This command was implemented on the Catalyst 6500 series switch and modified to display the strict level in the priority feature and the counts per level.
|
12.2(33)SRE
|
This command was modified to automatically round off the bc and be values, in the MQC police policy map, to the interface's MTU size.
|
Cisco IOS XE Release 2.6
|
The command output was modified to display information about subscriber QoS statistics.
|
12.2(54)SG
|
This command was modified to display only the the applicable count of policer statistics.
|
12.2(33)SCF
|
This command was integrated into Cisco IOS Release 12.2(33)SCF.
|
Usage Guidelines
Cisco 3660, 3845, 7200, 7400, 7500, and Cisco ASR 1000 Series Routers
The show policy-map interface command displays the packet statistics for classes on the specified interface or the specified PVC only if a service policy has been attached to the interface or the PVC.
The counters displayed after the show policy-map interface command is entered are updated only if congestion is present on the interface.
The show policy-map interface command displays policy information about Frame Relay PVCs only if Frame Relay Traffic Shaping (FRTS) is enabled on the interface.
The show policy-map interface command displays ECN marking information only if ECN is enabled on the interface.
To determine if shaping is active with HQF, check the queue depth field of the "(queue depth/total drops/no-buffer drops)" line in the show policy-map interface command output.
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and the bytes delayed counters were removed for traffic shaping classes.
Cisco 7600 Series Routers and Catalyst 6500 Series Switches
The pos, atm, and ge-wan interfaces are not supported on Cisco 7600 series routers or Catalyst 6500 series switches that are configured with a Supervisor Engine 720.
Cisco 7600 series routers and Catalyst 6500 series switches that are configured with a Supervisor Engine 2 display packet counters.
Cisco 7600 series routers and Catalyst 6500 series switches that are configured with a Supervisor Engine 720 display byte counters.
The output does not display policed-counter information; 0 is displayed in its place (for example, 0 packets, 0 bytes). To display dropped and forwarded policed-counter information, enter the show mls qos command.
On the Cisco 7600 series router, for OSM WAN interfaces only, if you configure policing within a policy map, the hardware counters are displayed and the class-default counters are not displayed. If you do not configure policing within a policy map, the class-default counters are displayed.
On the Catalyst 6500 series switch, the show policy-map interface command displays the strict level in the priority feature and the counts per level.
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.
HQF
When you configure HQF, the show policy-map interface command displays additional fields that include the differentiated services code point (DSCP) value, WRED statistics in bytes, transmitted packets by WRED, and a counter that displays packets output/bytes output in each class.
Examples
This section provides sample output from typical show policy-map interface commands. Depending upon the interface or platform in use and the options enabled, the output you see may vary slightly from the ones shown below.
•
Weighted Fair Queueing (WFQ) on Serial Interface: Example
•
Traffic Shaping on Serial Interface: Example
•
Precedence-Based Aggregate WRED on ATM Shared Port Adapter: Example
•
DSCP-Based Aggregate WRED on ATM Shared Port Adapter: Example
•
Frame Relay Voice-Adaptive Traffic-Shaping: Example
•
Two-Rate Traffic Policing: Example
•
Multiple Traffic Policing Actions: Example
•
Explicit Congestion Notification: Example
•
Class-Based RTP and TCP Header Compression: Example
•
Modular QoS CLI (MQC) Unconditional Packet Discard: Example
•
Percentage-Based Policing and Shaping: Example
•
Traffic Shaping: Example
•
Packet Classification Based on Layer 3 Packet Length: Example
•
Enhanced Packet Marking: Example
•
Traffic Policing: Example
•
Formula for Calculating the CIR: Example
•
Formula for Calculating the PIR: Example
•
Formula for Calculating the Committed Burst (bc): Example
•
Formula for Calculating the Excess Burst (be): Example
•
Bandwidth Estimation: Example
•
Shaping with HQF Enabled: Example
•
Packets Matched on the Basis of VLAN ID Number: Example
•
Cisco 7600 Series Routers: Example
•
Multiple Priority Queues on Serial Interface: Example
•
Bandwidth-Remaining Ratios: Example
•
Tunnel Marking: Example
•
Traffic Shaping Overhead Accounting for ATM: Example
•
HQF: Example
•
Account QoS Statistics for the Cisco ASR 1000 Series Aggregation Services Routers: Example
•
Cisco Catalyst 4000 Series Routers: Example
•
Cisco CMTS Routers: Example
Weighted Fair Queueing (WFQ) on Serial Interface: Example
The following sample output of the show policy-map interface command displays the statistics for the serial 3/1 interface, to which a service policy called mypolicy (configured as shown below) is attached. Weighted fair queueing (WFQ) has been enabled on this interface. See Table 58 for an explanation of the significant fields that commonly appear in the command output.
Router# show policy-map interface serial3/1 output
Service-policy output: mypolicy
Class-map: voice (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
Output Queue: Conversation 264
Bandwidth 128 (kbps) Burst 3200 (Bytes)
(pkts matched/bytes matched) 0/0
(total drops/bytes drops) 0/0
Class-map: gold (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
Output Queue: Conversation 265
Bandwidth 100 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Class-map: silver (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
Output Queue: Conversation 266
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
rsvp 0/0 0/0 0/0 36 40 1/10
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
Traffic Shaping on Serial Interface: Example
The following sample output from the show policy-map interface command displays the statistics for the serial 3/2 interface, to which a service policy called p1 (configured as shown below) is attached. Traffic shaping has been enabled on this interface. See Table 58 for an explanation of the significant fields that commonly appear in the command output.
Note
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for traffic shaping classes.
Router# show policy-map interface serial3/2 output
Service-policy output: p1
Class-map: c1 (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
Target Byte Sustain Excess Interval Increment Adapt
Rate Limit bits/int bits/int (ms) (bytes) Active
320000 2000 8000 8000 25 1000 -
Queue Packets Bytes Packets Bytes Shaping
Depth Delayed Delayed Active
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
Table 58 describes significant fields commonly shown in the displays. The fields in the table are grouped according to the relevant QoS feature.
Table 58 show policy-map interface Field Descriptions1
Field
|
Description
|
Fields Associated with Classes or Service Policies
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets and bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Note In distributed architecture platforms (such as the Cisco 7500 series platform), the value of the transfer rate, calculated as the difference between the offered rate and the drop rate counters, can sporadically deviate from the average by up to 20 percent or more. This can occur while no corresponding burst is registered by independent traffic analyser equipment.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as IP precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental (EXP) value, access groups, and QoS groups. For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
Fields Associated with Queueing (if Enabled)
|
Output Queue
|
The weighted fair queueing (WFQ) conversation to which this class of traffic is allocated.
|
Bandwidth
|
Bandwidth, in either kbps or percentage, configured for this class and the burst size.
|
pkts matched/bytes matched
|
Number of packets (also shown in bytes) matching this class that were placed in the queue. This number reflects the total number of matching packets queued at any time. Packets matching this class are queued only when congestion exists. If packets match the class but are never queued because the network was not congested, those packets are not included in this total. However, if process switching is in use, the number of packets is always incremented even if the network is not congested.
|
depth/total drops/no-buffer drops
|
Number of packets discarded for this class. No-buffer indicates that no memory buffer exists to service the packet.
|
Fields Associated with Weighted Random Early Detection (WRED) (if Enabled)
|
exponential weight
|
Exponent used in the average queue size calculation for a WRED parameter group.
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a fluctuating average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
class
|
IP precedence level.
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
Note If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as "no-buffer drops") are not taken into account by the WRED packet counter.
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value and the maximum threshold value for the specified IP precedence level.
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence level.
|
Minimum thresh
|
Minimum threshold. Minimum WRED threshold in number of packets.
|
Maximum thresh
|
Maximum threshold. Maximum WRED threshold in number of packets.
|
Mark prob
|
Mark probability. Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
Fields Associated with Traffic Shaping (if Enabled)
|
Target Rate
|
Rate used for shaping traffic.
|
Byte Limit
|
Maximum number of bytes that can be transmitted per interval. Calculated as follows:
((Bc+Be) /8) x 1
|
Sustain bits/int
|
Committed burst (Bc) rate.
|
Excess bits/int
|
Excess burst (Be) rate.
|
Interval (ms)
|
Time interval value in milliseconds (ms).
|
Increment (bytes)
|
Number of credits (in bytes) received in the token bucket of the traffic shaper during each time interval.
|
Queue Depth
|
Current queue depth of the traffic shaper.
|
Packets
|
Total number of packets that have entered the traffic shaper system.
|
Bytes
|
Total number of bytes that have entered the traffic shaper system.
|
Packets Delayed
|
Total number of packets delayed in the queue of the traffic shaper before being transmitted.
|
Bytes Delayed
|
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
|
Shaping Active
|
Indicates whether the traffic shaper is active. For example, if a traffic shaper is active, and the traffic being sent exceeds the traffic shaping rate, a "yes" appears in this field.
|
Precedence-Based Aggregate WRED on ATM Shared Port Adapter: Example
The following sample output of the show policy-map interface command displays the statistics for the ATM shared port adapter interface 4/1/0.10, to which a service policy called prec-aggr-wred (configured as shown below) is attached. Because aggregate WRED has been enabled on this interface, the class through Mark Prob statistics are aggregated by subclasses. See Table 59 for an explanation of the significant fields that commonly appear in the command output.
Router(config)# policy-map prec-aggr-wred
Router(config-pmap)# class class-default
Router(config-pmap-c)# random-detect aggregate
Router(config-pmap-c)# random-detect precedence values 0 1 2 3 minimum thresh 10
maximum-thresh 100 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 4 5 minimum-thresh 40
maximum-thresh 400 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 6 minimum-thresh 60 maximum-thresh
600 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 7 minimum-thresh 70 maximum-thresh
700 mark-prob 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM4/1/0.10 point-to-point
Router(config-if)# ip address 10.0.0.2 255.255.255.0
Router(config-if)# pvc 10/110
Router(config-if)# service-policy output prec-aggr-wred
Router# show policy-map interface atm4/1/0.10
Service-policy output: prec-aggr-wred
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
Exp-weight-constant: 9 (1/512)
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
0 1 2 3 0/0 0/0 0/0 10 100 1/10
4 5 0/0 0/0 0/0 40 400 1/10
6 0/0 0/0 0/0 60 600 1/10
7 0/0 0/0 0/0 70 700 1/10
DSCP-Based Aggregate WRED on ATM Shared Port Adapter: Example
The following sample output of the show policy-map interface command displays the statistics for the ATM shared port adapter interface 4/1/0.11, to which a service policy called dscp-aggr-wred (configured as shown below) is attached. Because aggregate WRED has been enabled on this interface, the class through Mark Prob statistics are aggregated by subclasses. See Table 59 for an explanation of the significant fields that commonly appear in the command output.
Router(config)# policy-map dscp-aggr-wred
Router(config-pmap)# class class-default
Router(config-pmap-c)# random-detect dscp-based aggregate minimum-thresh 1 maximum-thresh
10 mark-prob 10
Router(config-pmap-c)# random-detect dscp values 0 1 2 3 4 5 6 7 minimum-thresh 10
maximum-thresh 20 mark-prob 10
Router(config-pmap-c)# random-detect dscp values 8 9 10 11 minimum-thresh 10
maximum-thresh 40 mark-prob 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM4/1/0.11 point-to-point
Router(config-subif)# ip address 10.0.0.2 255.255.255.0
Router(config-subif)# pvc 11/101
Router(config-subif)# service-policy output dscp-aggr-wred
Router# show policy-map interface atm4/1/0.11
Service-policy output: dscp-aggr-wred
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
Exp-weight-constant: 0 (1/1)
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
default 0/0 0/0 0/0 1 10 1/10
4 5 6 7 0/0 0/0 0/0 10 20 1/10
8 9 10 11 0/0 0/0 0/0 10 40 1/10
Table 59 describes the significant fields shown in the display when aggregate WRED is configured for an ATM shared port adapter.
Table 59 show policy-map interface Field Descriptions—Configured for Aggregate WRED on ATM Shared Port Adapter
Field
|
Description
|
exponential weight
|
Exponent used in the average queue size calculation for a Weighted Random Early Detection (WRED) parameter group.
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a fluctuating average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
Note When Aggregate Weighted Random Early Detection (WRED) is enabled, the following WRED statistics will be aggregated based on their subclass (either their IP precedence or differentiated services code point (DSCP) value).
|
class
|
IP precedence level or differentiated services code point (DSCP) value.
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
Note If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as "no-buffer drops") are not taken into account by the WRED packet counter.
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value and the maximum threshold value for the specified IP precedence level or DSCP value.
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence level or DSCP value.
|
Minimum thresh
|
Minimum threshold. Minimum WRED threshold in number of packets.
|
Maximum thresh
|
Maximum threshold. Maximum WRED threshold in number of packets.
|
Mark prob
|
Mark probability. Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
Frame Relay Voice-Adaptive Traffic-Shaping: Example
The following sample output shows that Frame Relay voice-adaptive traffic shaping is currently active and has 29 seconds left on the deactivation timer. With traffic shaping active and the deactivation time set, this means that the current sending rate on DLCI 201 is minCIR, but if no voice packets are detected for 29 seconds, the sending rate will increase to CIR.
Note
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for traffic shaping classes.
Router# show policy interface Serial3/1.1
Service-policy output:MQC-SHAPE-LLQ1
Class-map:class-default (match-any)
1434 packets, 148751 bytes
30 second offered rate 14000 bps, drop rate 0 bps
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
63000/63000 1890 7560 7560 120 945
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
BECN 0 1434 162991 26 2704 yes
Voice Adaptive Shaping active, time left 29 secs
Table 60 describes the significant fields shown in the display. Significant fields that are not described in Table 60 are described in Table 58, "show policy-map interface Field Descriptions."
Table 60 show policy-map interface Field Descriptions—Configured for Frame Relay Voice-Adaptive Traffic Shaping
Field
|
Description
|
Voice Adaptive Shaping active/inactive
|
Indicates whether Frame Relay voice-adaptive traffic shaping is active or inactive.
|
time left
|
Number of seconds left on the Frame Relay voice-adaptive traffic shaping deactivation timer.
|
Two-Rate Traffic Policing: Example
The following is sample output from the show policy-map interface command when two-rate traffic policing has been configured. In the example below, 1.25 Mbps of traffic is sent ("offered") to a policer class.
Router# show policy-map interface serial3/0
Service-policy output: policy1
Class-map: police (match all)
148803 packets, 36605538 bytes
30 second offered rate 1249000 bps, drop rate 249000 bps
cir 500000 bps, conform-burst 10000, pir 1000000, peak-burst 100000
conformed 59538 packets, 14646348 bytes; action: transmit
exceeded 59538 packets, 14646348 bytes; action: set-prec-transmit 2
violated 29731 packets, 7313826 bytes; action: drop
conformed 499000 bps, exceed 500000 bps violate 249000 bps
Class-map: class-default (match-any)
30 seconds offered rate 0 bps, drop rate 0 bps
The two-rate traffic policer marks 500 kbps of traffic as conforming, 500 kbps of traffic as exceeding, and 250 kbps of traffic as violating the specified rate. Packets marked as conforming will be sent as is, and packets marked as exceeding will be marked with IP Precedence 2 and then sent. Packets marked as violating the specified rate are dropped.
Table 61 describes the significant fields shown in the display.
Table 61 show policy-map interface Field Descriptions—Configured for Two-Rate Traffic Policing
Field
|
Description
|
police
|
Indicates that the police command has been configured to enable traffic policing. Also, displays the specified CIR, conform burst size, peak information rate (PIR), and peak burst size used for marking packets.
|
conformed
|
Displays the action to be taken on packets conforming to a specified rate. Displays the number of packets and bytes on which the action was taken.
|
exceeded
|
Displays the action to be taken on packets exceeding a specified rate. Displays the number of packets and bytes on which the action was taken.
|
violated
|
Displays the action to be taken on packets violating a specified rate. Displays the number of packets and bytes on which the action was taken.
|
Multiple Traffic Policing Actions: Example
The following is sample output from the show policy-map command when the Policer Enhancement—Multiple Actions feature has been configured. The sample output from the show policy-map interface command displays the statistics for the serial 3/2 interface, to which a service policy called "police" (configured as shown below) is attached.
police cir 1000000 pir 2000000
exceed-action set-prec-transmit 4
exceed-action set-frde-transmit
violate-action set-prec-transmit 2
violate-action set-frde-transmit
Router# show policy-map interface serial3/2
Service-policy output: police
Class-map: class-default (match-any)
172984 packets, 42553700 bytes
5 minute offered rate 960000 bps, drop rate 277000 bps
cir 1000000 bps, bc 31250 bytes, pir 2000000 bps, be 31250 bytes
conformed 59679 packets, 14680670 bytes; actions:
exceeded 59549 packets, 14649054 bytes; actions:
violated 53758 packets, 13224468 bytes; actions:
conformed 340000 bps, exceed 341000 bps, violate 314000 bps
The sample output from show policy-map interface command shows the following:
•
59679 packets were marked as conforming packets (that is, packets conforming to the CIR) and were transmitted unaltered.
•
59549 packets were marked as exceeding packets (that is, packets exceeding the CIR but not exceeding the PIR). Therefore, the IP Precedence value of these packets was changed to an IP Precedence level of 4, the discard eligibility (DE) bit was set to 1, and the packets were transmitted with these changes.
•
53758 packets were marked as violating packets (that is, exceeding the PIR). Therefore, the IP Precedence value of these packets was changed to an IP Precedence level of 2, the DE bit was set to 1, and the packets were transmitted with these changes.
Note
Actions are specified by using the action argument of the police command. For more information about the available actions, see the police command reference page.
Table 62 describes the significant fields shown in the display.
Table 62 show policy-map interface Field Descriptions—Configured for Multiple Traffic Policing Actions
Field
|
Description
|
police
|
Indicates that the police command has been configured to enable traffic policing. Also, displays the specified CIR, conform burst size (BC), PIR, and peak burst size (BE) used for marking packets.
|
conformed, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as conforming to a specified rate and the actions taken on the packet. If there are multiple actions, each action is listed separately.
|
exceeded, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as exceeding a specified rate and the actions taken on the packet. If there are multiple actions, each action is listed separately.
|
violated, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as violating a specified rate and the actions taken on the packet. If there are multiple actions, each action is listed separately.
|
Explicit Congestion Notification: Example
The following is sample output from the show policy-map interface command when the WRED — Explicit Congestion Notification (ECN) feature has been configured. The words "explicit congestion notification" included in the output indicate that ECN has been enabled.
Router# show policy-map interface Serial4/1
Service-policy output:policy_ecn
Class-map:prec1 (match-all)
1000 packets, 125000 bytes
30 second offered rate 14000 bps, drop rate 5000 bps
Output Queue:Conversation 42
(pkts matched/bytes matched) 989/123625
(depth/total drops/no-buffer drops) 0/455/0
explicit congestion notification
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes threshold threshold probability
1 545/68125 0/0 0/0 22 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10
Table 63 describes the significant fields shown in the display.
Table 63 show policy-map interface Field Descriptions—Configured for ECN
Field
|
Description
|
explicit congestion notification
|
Indication that Explicit Congestion Notification is enabled.
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a moving average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
class
|
IP precedence value.
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
Note If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as "no-buffer drops") are not taken into account by the WRED packet counter.
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value and the maximum threshold value for the specified IP precedence value.
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence value.
|
Minimum threshold
|
Minimum WRED threshold in number of packets.
|
Maximum threshold
|
Maximum WRED threshold in number of packets.
|
Mark probability
|
Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
ECN Mark pkts/bytes
|
Number of packets (also shown in bytes) marked by ECN.
|
Class-Based RTP and TCP Header Compression: Example
The following sample output from the show policy-map interface command shows the RTP header compression has been configured for a class called "prec2" in the policy map called "p1".
The show policy-map interface command output displays the type of header compression configured (RTP), the interface to which the policy map called "p1" is attached (Serial 4/1), the total number of packets, the number of packets compressed, the number of packets saved, the number of packets sent, and the rate at which the packets were compressed (in bits per second (bps)).
In this example, User Datagram Protocol (UDP)/RTP header compressions have been configured, and the compression statistics are included at the end of the display.
Router# show policy-map interface Serial4/1
Class-map:class-default (match-any)
1005 packets, 64320 bytes
30 second offered rate 16000 bps, drop rate 0 bps
Sent:1000 total, 999 compressed,
41957 bytes saved, 17983 bytes sent
3.33 efficiency improvement factor
99% hit ratio, five minute miss rate 0 misses/sec, 0 max
Table 64 describes the significant fields shown in the display.
Table 64 show policy-map interface Field Descriptions—Configured for Class-Based RTP and TCP Header Compression1
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
UDP/RTP Compression
|
Indicates that RTP header compression has been configured for the class.
|
Sent total
|
Count of every packet sent, both compressed packets and full-header packets.
|
Sent compressed
|
Count of number of compressed packets sent.
|
bytes saved
|
Total number of bytes saved (that is, bytes not needing to be sent).
|
bytes sent
|
Total number of bytes sent for both compressed and full-header packets.
|
efficiency improvement factor
|
The percentage of increased bandwidth efficiency as a result of header compression. For example, with RTP streams, the efficiency improvement factor can be as much as 2.9 (or 290 percent).
|
hit ratio
|
Used mainly for troubleshooting purposes, this is the percentage of packets found in the context database. In most instances, this percentage should be high.
|
five minute miss rate
|
The number of new traffic flows found in the last five minutes.
|
misses/sec max
|
The average number of new traffic flows found per second, and the highest rate of new traffic flows to date.
|
rate
|
The actual traffic rate (in bits per second) after the packets are compressed.
|
Modular QoS CLI (MQC) Unconditional Packet Discard: Example
The following sample output from the show policy-map interface command displays the statistics for the Serial2/0 interface, to which a policy map called "policy1" is attached. The discarding action has been specified for all the packets belonging to a class called "c1." In this example, 32000 bps of traffic is sent ("offered") to the class and all of them are dropped. Therefore, the drop rate shows 32000 bps.
Router# show policy-map interface Serial2/0
Service-policy output: policy1
Class-map: c1 (match-all)
10184 packets, 1056436 bytes
5 minute offered rate 32000 bps, drop rate 32000 bps
Table 65 describes the significant fields shown in the display.
Table 65 show policy-map interface Field Descriptions—Configured for MQC Unconditional Packet Discard1
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Note In distributed architecture platforms (such as the Cisco 7500), the value of the transfer rate, calculated as the difference between the offered rate and the drop rate counters, can sporadically deviate from the average by up to 20 percent or more. This can occur while no corresponding burst is registered by independent traffic analyser equipment.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence, IP DSCP value, MPLS experimental value, access groups, and QoS groups. For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
drop
|
Indicates that the packet discarding action for all the packets belonging to the specified class has been configured.
|
Percentage-Based Policing and Shaping: Example
The following sample output from the show policy-map interface command shows traffic policing configured using a CIR based on a bandwidth of 20 percent. The CIR and committed burst (Bc) in milliseconds (ms) are included in the display.
Router# show policy-map interface Serial3/1
Service-policy output: mypolicy
Class-map: gold (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
cir 2000000 bps, bc 2500 bytes
pir 4000000 bps, be 10000 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
violated 0 packets, 0 bytes; actions:
conformed 0 bps, exceed 0 bps, violate 0 bps
Table 66 describes the significant fields shown in the display.
Table 66 show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping1
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
police
|
Indicates that traffic policing based on a percentage of bandwidth has been enabled. Also, displays the bandwidth percentage, the CIR, and the committed burst (Bc) size in ms.
|
conformed, actions
|
Displays the number of packets and bytes marked as conforming to the specified rates, and the action to be taken on those packets.
|
exceeded, actions
|
Displays the number of packets and bytes marked as exceeding the specified rates, and the action to be taken on those packets.
|
Traffic Shaping: Example
The following sample output from the show policy-map interface command (shown below) displays the statistics for the serial 3/2 interface. Traffic shaping has been enabled on this interface, and an average rate of 20 percent of the bandwidth has been specified.
Note
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for traffic shaping classes.
Router# show policy-map interface Serial3/2
Service-policy output: p1
Class-map: c1 (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
Target/Average Byte Sustain Excess Interval Increment Adapt
Rate Limit bits/int bits/int (ms) (bytes) Active
20 % 10 (ms) 20 (ms)
201500/201500 1952 7808 7808 38 976 -
Queue Packets Bytes Packets Bytes Shaping
Depth Delayed Delayed Active
Table 67 describes the significant fields shown in the display.
Table 67 show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping (with Traffic Shaping Enabled)1
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence, IP DSCP value, MPLS experimental value, access groups, and quality of service (QoS) groups. For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
Traffic Shaping
|
Indicates that traffic shaping based on a percentage of bandwidth has been enabled.
|
Target/Average Rate
|
Rate (percentage) used for shaping traffic and the number of packets meeting that rate.
|
Byte Limit
|
Maximum number of bytes that can be transmitted per interval. Calculated as follows:
((Bc+Be) /8 ) x 1
|
Sustain bits/int
|
Committed burst (Bc) rate.
|
Excess bits/int
|
Excess burst (Be) rate.
|
Interval (ms)
|
Time interval value in milliseconds (ms).
|
Increment (bytes)
|
Number of credits (in bytes) received in the token bucket of the traffic shaper during each time interval.
|
Adapt Active
|
Indicates whether adaptive shaping is enabled.
|
Queue Depth
|
Current queue depth of the traffic shaper.
|
Packets
|
Total number of packets that have entered the traffic shaper system.
|
Bytes
|
Total number of bytes that have entered the traffic shaper system.
|
Packets Delayed
|
Total number of packets delayed in the queue of the traffic shaper before being transmitted.
Note In Cisco IOS Release 12.4(20)T, this counter was removed.
|
Bytes Delayed
|
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
Note In Cisco IOS Release 12.4(20)T, this counter was removed.
|
Shaping Active
|
Indicates whether the traffic shaper is active. For example, if a traffic shaper is active, and the traffic being sent exceeds the traffic shaping rate, a "yes" appears in this field.
|
Packet Classification Based on Layer 3 Packet Length: Example
The following sample output from the show policy-map interface command displays the packet statistics for the Ethernet4/1 interface, to which a service policy called "mypolicy" is attached. The Layer 3 packet length has been specified as a match criterion for the traffic in the class called "class1".
Router# show policy-map interface Ethernet4/1
Service-policy input: mypolicy
Class-map: class1 (match-all)
500 packets, 125000 bytes
5 minute offered rate 4000 bps, drop rate 0 bps
Match: packet length min 100 max 300
Table 68 describes the significant fields shown in the display.
Table 68 show policy-map interface Field Descriptions—Configured for Packet Classification Based on Layer 3 Packet Length1
Field
|
Description
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
Note If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not reflected in the offered rate. Also, if the packets are classified before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec) tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending on the configuration, the offered rate may include no overhead, may include the overhead for only one tunnel encapsulation, or may include the overhead for all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE tunnel encapsulation only.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence, IP DSCP value, MPLS experimental value, access groups, and QoS groups.
|
QoS Set, qos-group, Packets marked
|
Indicates that class-based packet marking based on the QoS group has been configured. Includes the qos-group number and the number of packets marked.
|
Enhanced Packet Marking: Example
The following sample output of the show policy-map interface command shows the service policies attached to a FastEthernet subinterface. In this example, a service policy called "policy1" has been attached. In "policy1", a table map called "table-map1" has been configured. The values in "table-map1" will be used to map the precedence values to the corresponding class of service (CoS) values.
Router# show policy-map interface
Service-policy input: policy1
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
precedence cos table table-map1
Table 69 describes the fields shown in the display.
Table 69 show policy-map interface Field Descriptions—Configured for Enhanced Packet Marking1
Field
|
Description
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of the packets coming into the class.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as Precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) group (set). For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
QoS Set
|
Indicates that QoS group (set) has been configured for the particular class.
|
precedence cos table table-map1
|
Indicates that a table map (called "table-map1") has been used to determine the precedence value. The precedence value will be set according to the CoS value defined in the table map.
|
Packets marked
|
Total number of packets marked for the particular class.
|
Traffic Policing: Example
The following is sample output from the show policy-map interface command. This sample displays the statistics for the serial 2/0 interface on which traffic policing has been enabled. The committed (conform) burst (bc) and excess (peak) burst (be) are specified in milliseconds (ms).
Router# show policy-map interface serial2/0
Service-policy output: policy1 (1050)
Class-map: class1 (match-all) (1051/1)
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 0 (1052)
cir 409500 bps, bc 15360 bytes
pir 819000 bps, be 40960 bytes
conformed 0 packets, 0 bytes; actions:
exceeded 0 packets, 0 bytes; actions:
violated 0 packets, 0 bytes; actions:
conformed 0 bps, exceed 0 bps, violate 0 bps
Class-map: class-default (match-any) (1054/0)
5 minute offered rate 0 bps, drop rate 0 bps
In this example, the CIR and PIR are displayed in bps, and both the committed burst (bc) and excess burst (be) are displayed in bits.
The CIR, PIR bc, and be are calculated on the basis of the formulas described below.
Formula for Calculating the CIR: Example
When calculating the CIR, the following formula is used:
•
CIR percentage specified (as shown in the output from the show policy-map command) * bandwidth (BW) of the interface (as shown in the output from the show interfaces command) = total bits per second
According to the output from the show interfaces command for the serial 2/0 interface, the interface has a bandwidth (BW) of 2048 kbps.
Router# show interfaces serial2/0
Serial2/0 is administratively down, line protocol is down
Hardware is M4T
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255
The following values are used for calculating the CIR:
20 % * 2048 kbps = 409600 bps
Formula for Calculating the PIR: Example
When calculating the PIR, the following formula is used:
•
PIR percentage specified (as shown in the output from the show policy-map command) * bandwidth (BW) of the interface (as shown in the output from the show interfaces command) = total bits per second
According to the output from the show interfaces command for the serial 2/0 interface, the interface has a bandwidth (BW) of 2048 kbps.
Router# show interfaces serial2/0
Serial2/0 is administratively down, line protocol is down
Hardware is M4T
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255
The following values are used for calculating the PIR:
40 % * 2048 kbps = 819200 bps
Note
Discrepancies between this total and the total shown in the output from the show policy-map interface command can be attributed to a rounding calculation or to differences associated with the specific interface configuration.
Formula for Calculating the Committed Burst (bc): Example
When calculating the bc, the following formula is used:
•
The bc in milliseconds (as shown in the show policy-map command) * the CIR in bits per seconds = total number bytes
The following values are used for calculating the bc:
300 ms * 409600 bps = 15360 bytes
Formula for Calculating the Excess Burst (be): Example
When calculating the bc and the be, the following formula is used:
•
The be in milliseconds (as shown in the show policy-map command) * the PIR in bits per seconds = total number bytes
The following values are used for calculating the be:
400 ms * 819200 bps = 40960 bytes
Table 70 describes the significant fields shown in the display.
Table 70 show policy-map interface Field Descriptions
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets and bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) groups. For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
police
|
Indicates that traffic policing has been enabled. Display includes the CIR, PIR (in both a percentage of bandwidth and in bps) and the bc and be in bytes and milliseconds. Also displays the optional conform, exceed, and violate actions, if any, and the statistics associated with these optional actions.
|
Bandwidth Estimation: Example
The following sample output from the show policy-map interface command displays statistics for the Fast Ethernet 0/1 interface on which bandwidth estimates for quality of service (QoS) targets have been generated.
The Bandwidth Estimation section indicates that bandwidth estimates for QoS targets have been defined. These targets include the packet loss rate, the packet delay rate, and the timeframe in milliseconds. Confidence refers to the drop-one-in value (as a percentage) of the targets. Corvil Bandwidth means the bandwidth estimate in kilobits per second.
When no drop or delay targets are specified, "none specified, falling back to drop no more than one packet in 500" appears in the output.
Router# show policy-map interface FastEthernet0/1
Service-policy output: my-policy
Class-map: icmp (match-all)
30 second offered rate 0 bps, drop rate 0 bps
Quality-of-Service targets:
drop no more than one packet in 1000 (Packet loss < 0.10%)
delay no more than one packet in 100 by 40 (or more) milliseconds
Corvil Bandwidth: 1 kbits/sec
Class-map: class-default (match-any)
30 second offered rate 0 bps, drop rate 0 bps
Quality-of-Service targets:
<none specified, falling back to drop no more than one packet in 500
Corvil Bandwidth: 1 kbits/sec
Shaping with HQF Enabled: Example
The following sample output from the show policy-map interface command shows that shaping is active (as seen in the queue depth field) with HQF enabled on the serial 4/3 interface. All traffic is classified to the class-default queue.
Note
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for traffic shaping classes.
Router# show policy-map interface serial4/3
Service-policy output: shape
Class-map: class-default (match-any)
2203 packets, 404709 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
(queue depth/total drops/no-buffer drops) 64/354/0
(pkts output/bytes output) 1836/337280
shape (average) cir 128000, bc 1000, be 1000
lower bound cir 0, adapt to fecn 0
queue stats for all priority classes:
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: c1 (match-all)
30 second offered rate 0 bps, drop rate 0 bps
Priority: 32 kbps, burst bytes 1500, b/w exceed drops: 0
Class-map: class-default (match-any)
2190 packets, 404540 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
(queue depth/total drops/no-buffer drops) 63/417/0
(pkts output/bytes output) 2094/386300
Packets Matched on the Basis of VLAN ID Number: Example
Note
As of Cisco IOS Release 12.2(31)SB2, matching packets on the basis of VLAN ID numbers is supported on the Catalyst 1000 platform only.
The following is a sample configuration in which packets are matched and classified on the basis of the VLAN ID number. In this sample configuration, packets that match VLAN ID number 150 are placed in a class called "class1."
Class Map match-all class1 (id 3)
Class1 is then configured as part of the policy map called "policy1." The policy map is attached to Fast Ethernet subinterface 0/0.1.
The following sample output of the show policy-map interface command displays the packet statistics for the policy maps attached to Fast Ethernet subinterface 0/0.1. It displays the statistics for policy1, in which class1 has been configured.
Router# show policy-map interface
Service-policy input: policy1
! Class configured in the policy map.
Class-map: class1 (match-all)
5 minute offered rate 0 bps, drop rate 0 bps
! VLAN ID 150 is the match criterion for the class.
cir 8000000 bps, bc 512000000 bytes
conformed 0 packets, 0 bytes; actions:
exceeded 0 packets, 0 bytes; actions:
conformed 0 bps, exceed 0 bps
Class-map: class-default (match-any)
5 minute offered rate 0 bps, drop rate 0 bps
Table 71 describes the significant fields shown in the display.
Table 71 show policy-map interface Field Descriptions—Packets Matched on the Basis of VLAN ID Number1
Field
|
Description
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of the packets coming into the class.
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as VLAN ID number, precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) group (set). For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
Cisco 7600 Series Routers: Example
The following example shows how to display the statistics and the configurations of all the input and output policies that are attached to an interface on a Cisco 7600 series router:
Router# show policy-map interface
service-policy input: max-pol-ipp5
class-map: ipp5 (match-all)
police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action p
The following example shows how to display the input-policy statistics and the configurations for a specific interface on a Cisco 7600 series router:
Router# show policy-map interface fastethernet 5/36 input
service-policy input: max-pol-ipp5
class-map: ipp5 (match-all)
police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action p
Table 72 describes the significant fields shown in the display.
Table 72 show policy-map interface Field Descriptions—Cisco 7600 Series Routers
Field
|
Description
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
minute rate
|
Rate, in kbps, of the packets coming into the class.
|
match
|
Match criteria specified for the class of traffic. Choices include criteria such as VLAN ID number, precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) group (set). For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
class
|
Precedence value.
|
police
|
Indicates that the police command has been configured to enable traffic policing.
|
Cisco 7200 Series Routers: Example
The following example shows the automatic rounding-off of the bc and be values, in the MQC police policy-map, to the interface's MTU size in a Cisco 7200 series router. The rounding-off is done only when the bc and be values are lesser than the interface's MTU size.
Router# show policy-map interface
Service-policy output: p2
Service-policy output: p2
Class-map: class-default (match-any)
30 second offered rate 0000 bps, drop rate 0000 bps
cir 10000 bps, bc 4470 bytes
pir 20000 bps, be 4470 bytes
conformed 0 packets, 0 bytes; actions:
exceeded 0 packets, 0 bytes; actions:
violated 0 packets, 0 bytes; actions:
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Multiple Priority Queues on Serial Interface: Example
The following sample output from the show policy-map interface command shows the types of statistical information that displays when multiple priority queues are configured. Depending upon the interface in use and the options enabled, the output that you see may vary slightly from the output shown below.
Router# show policy-map interface
Service-policy output: P1
Queue statistics for all priority classes:
Class-map: Gold (match-all)
0 packets, 0 bytes /*Updated for each priority level configured.*/
5 minute offered rate 0 bps, drop rate 0 bps
Priority: 0 kbps, burst bytes 1500, b/w exceed drops: 0
Bandwidth-Remaining Ratios: Example
The following sample output from the show policy-map interface command indicates that bandwidth-remaining ratios are configured for class queues. As shown in the example, the classes precedence_0, precedence_1, and precedence_2 have bandwidth-remaining ratios of 20, 40, and 60, respectively.
Router# show policy-map interface GigabitEthernet1/0/0.10
Service-policy output: vlan10_policy
Class-map: class-default (match-any)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 1000000, bc 4000, be 4000
target shape rate 1000000
bandwidth remaining ratio 10
Service-policy : child_policy
Class-map: precedence_0 (match-all)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
bandwidth remaining ratio 20
Class-map: precedence_1 (match-all)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
bandwidth remaining ratio 40
Class-map: precedence_2 (match-all)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
bandwidth remaining ratio 60
Class-map: class-default (match-any)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Table 73 describes the significant fields shown in the display.
Table 73 show policy-map interface Field Descriptions—Configured for Bandwidth-Remaining Ratios
Field
|
Description
|
Service-policy output
|
Name of the output service policy applied to the specified interface.
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
bandwidth remaining ratio
|
Indicates the ratio used to allocate excess bandwidth.
|
Tunnel Marking: Example
In this sample output of the show policy-map interface command, the character string "ip dscp tunnel 3" indicates that L2TPv3 tunnel marking has been configured to set the DSCP value to 3 in the header of a tunneled packet.
Router# show policy-map interface
Service-policy input: tunnel
Class-map: frde (match-all)
30 second offered rate 0 bps, drop rate 0 bps
Class-map: class-default (match-any)
13736 packets, 1714682 bytes
30 second offered rate 0 bps, drop rate 0 bps
13736 packets, 1714682 bytes
Table 74 describes the significant fields shown in the display.
Table 74 show policy-map interface Field Descriptions—Configured for Tunnel Marking
Field
|
Description
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
match
|
Match criteria specified for the class of traffic. In this example, the Frame Relay Discard Eligible (DE) bit has been specified as the match criterion.
For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
ip dscp tunnel
|
Indicates that tunnel marking has been configured to set the DSCP in the header of a tunneled packet to a value of 3.
|
Traffic Shaping Overhead Accounting for ATM: Example
The following output from the show policy-map interface command indicates that ATM overhead accounting is enabled for shaping and disabled for bandwidth:
Router# show policy-map interface
Service-policy output:unit-test
Class-map: class-default (match-any)
30 second offered rate 800 bps, drop rate 0 bps
shape (average) cir 154400, bc 7720, be 7720
overhead accounting: enabled
overhead accounting: disabled
(queue depth/total drops/no-buffer drops) 0/0/0
(packets output/bytes output) 100/1000
Table 75 describes the significant fields shown in the display.
Table 75 show policy-map interface Field Descriptions—Configured for Traffic Shaping Overhead Accounting for ATM
Field
|
Description
|
service-policy output
|
Name of the output service policy applied to the specified interface.
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
match
|
Match criteria specified for the class of traffic. In this example, the Frame Relay Discard Eligible (DE) bit has been specified as the match criterion.
For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
target shape rate
|
Indicates that traffic shaping is enabled at the specified rate.
|
overhead accounting
|
Indicates whether overhead accounting is enabled or disabled for traffic shaping.
|
bandwidth
|
Indicates the percentage of bandwidth allocated for traffic queueing.
|
overhead accounting:
|
Indicates whether overhead accounting is enabled or disabled for traffic queueing.
|
HQF: Example
The following output from the show policy-map interface command displays the configuration for Fast Ethernet interface 0/0:
Note
In HQF images for Cisco IOS Releases 12.4(20)T and later releases, the packets delayed and bytes delayed counters were removed for traffic shaping classes.
Router# show policy-map interface FastEthernet0/0
Service-policy output: test1
Class-map: class-default (match-any)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 129/12562
shape (average) cir 1536000, bc 6144, be 6144
target shape rate 1536000
queue stats for all priority classes:
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: RT (match-all)
30 second offered rate 0 bps, drop rate 0 bps
Priority: 20% (307 kbps), burst bytes 7650, b/w exceed drops: 0
Class-map: BH (match-all)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: BL (match-all)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
af21 0/0 0/0 0/0 100 400 1/10
Class-map: class-default (match-any)
30 second offered rate 0 bps, drop rate 0 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 129/12562
Table 76 describes the significant fields shown in the display.
Table 76 show policy-map interface Field Descriptions—Configured for HQF
Field
|
Description
|
FastEthernet
|
Name of the interface.
|
service-policy output
|
Name of the output service policy applied to the specified interface.
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully transmitted packets from the offered rate.
|
Match
|
Match criteria specified for the class of traffic.
Note For more information about the variety of match criteria that are available, see the "Classifying Network Traffic" module in the Cisco IOS Quality of Service Solutions Configuration Guide.
|
Queueing
|
Indicates that queueing is enabled.
|
queue limit
|
Maximum number of packets that a queue can hold for a class policy configured in a policy map.
|
bandwidth
|
Indicates the percentage of bandwidth allocated for traffic queueing.
|
dscp
|
Differentiated services code point (DSCP). Values can be the following:
• 0 to 63—Numerical DSCP values. The default value is 0.
• af1 to af43—Assured forwarding (AF) DSCP values.
• cs1 to cs7—Type of service (ToS) precedence values.
• default—Default DSCP value.
• ef—Expedited forwarding (EF) DSCP values.
|
Account QoS Statistics for the Cisco ASR 1000 Series Aggregation Services Routers: Example
The following example shows the new output fields associated with the QoS: Policies Aggregation Enhancements feature beginning in Cisco IOS XE Release 2.6 for subscriber statistics. The new output fields begin with the label "Account QoS Statistics."
Router# show policy-map interface port-channel 1.1
Service-policy input: input_policy
Class-map: class-default (match-any)
5 minute offered rate 0000 bps, drop rate 0000 bps
No packet marking statistics available
Service-policy output: Port-channel_1_subscriber
Class-map: EF (match-any)
105233 packets, 6734912 bytes
5 minute offered rate 134000 bps, drop rate 0000 bps
Match: access-group name VLAN_REMARK_EF
Packets dropped 0 packets/0 bytes
No packet marking statistics available
No packet marking statistics available
Class-map: AF4 (match-all)
105234 packets, 6734976 bytes
5 minute offered rate 134000 bps, drop rate 0000 bps
Packets dropped 0 packets/0 bytes
No packet marking statistics available
Class-map: AF1 (match-any)
315690 packets, 20204160 bytes
5 minute offered rate 402000 bps, drop rate 0000 bps
Packets dropped 0 packets/0 bytes
No packet marking statistics available
Class-map: class-default (match-any) fragment Port-channel_BE
315677 packets, 20203328 bytes
5 minute offered rate 402000 bps, drop rate 0000 bps
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 315679/20203482
bandwidth remaining ratio 1
Cisco Catalyst 4000 Series Routers: Example
The following example shows how to display the policer statistics (the packet and byte count). The output displays only the applicable count (either packets or bytes) with the actual number.
Router# show policy-map interface GigabitEthernet 3/1 input
Service-policy input: in1
Class-map: p1 (match-all)
cir 200000000 bps, bc 6250000 bytes
conformed 0 bytes; actions:
exceeded 0 bytes; actions:
conformed 0000 bps, exceed 0000 bps
Class-map: class-default (match-any)
cir 200000000 bps, bc 6250000 bytes
conformed 174304448 bytes; actions:
exceeded 465695552 bytes; actions:
conformed 4287000 bps, exceed 11492000 bps
Cisco CMTS Routers: Example
The following example shows how to display the statistics and the configurations of the input and output service policies that are attached to an interface:
Router# show policy-map interface gigabitEthernet 1/2/0
Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *23:02:40.857 pst Thu Mar 3 2011
Service-policy input: policy-in
Class-map: class-exp-0 (match-all)
6647740 packets, 9304674796 bytes
30 second offered rate 3234000 bps, drop rate 0 bps
Match: mpls experimental topmost 0
Class-map: class-default (match-any)
1386487 packets, 1903797872 bytes
30 second offered rate 658000 bps, drop rate 0 bps
Service-policy output: policy-out
Class-map: class-pre-1 (match-all)
2041355 packets, 2857897000 bytes
30 second offered rate 986000 bps, drop rate 0 bps
mpls experimental topmost 1
Class-map: class-default (match-any)
6129975 packets, 8575183331 bytes
30 second offered rate 2960000 bps, drop rate 0 bps
Table 77 describes the significant fields shown in the display.
Table 77 show policy-map interface Field Descriptions—Cisco Catalyst 4000 Series Routers
Field
|
Description
|
class-map
|
Displays the class of traffic. Output is displayed for each configured class in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
conformed
|
Displays the action to be taken on packets conforming to a specified rate. Also displays the number of packets and bytes on which the action was taken.
|
drop
|
Indicates that the packet discarding action for all the packets belonging to the specified class has been configured.
|
exceeded
|
Displays the action to be taken on packets exceeding a specified rate. Displays the number of packets and bytes on which the action was taken.
|
match
|
Match criteria specified for the class of traffic.
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
police
|
Indicates that the police command has been configured to enable traffic policing. Also displays the specified CIR, conform burst size, peak information rate (PIR), and peak burst size used for marking packets.
|
QoS Set
|
Indicates that QoS group (set) has been configured for the particular class.
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
Related Commands
Command
|
Description
|
bandwidth remaining ratio
|
Specifies a bandwidth-remaining ratio for class queues and subinterface-level queues to determine the amount of unused (excess) bandwidth to allocate to the queue during congestion.
|
class-map
|
Creates a class map to be used for matching packets to a specified class.
|
compression header ip
|
Configures RTP or TCP IP header compression for a specific class.
|
drop
|
Configures a traffic class to discard packets belonging to a specific class.
|
match fr-dlci
|
Specifies the Frame Relay DLCI number as a match criterion in a class map.
|
match packet length (class-map)
|
Specifies the length of the Layer 3 packet in the IP header as a match criterion in a class map.
|
police
|
Configures traffic policing.
|
police (percent)
|
Configures traffic policing on the basis of a percentage of bandwidth available on an interface.
|
police (two rates)
|
Configures traffic policing using two rates, the CIR and the PIR.
|
policy-map
|
Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.
|
priority
|
Specifies that low-latency behavior must be given to a traffic class and configures multiple priority queues.
|
random-detect ecn
|
Enables ECN.
|
shape (percent)
|
Specifies average or peak rate traffic shaping on the basis of a percentage of bandwidth available on an interface.
|
show class-map
|
Display all class maps and their matching criteria.
|
show frame-relay pvc
|
Displays statistics about PVCs for Frame Relay interfaces.
|
show interfaces
|
Displays statistics for all interfaces configured on a router or access server.
|
show mls qos
|
Displays MLS QoS information.
|
show policy-map
|
Displays the configuration of all classes for a specified service policy map or all classes for all existing policy maps.
|
show policy-map class
|
Displays the configuration for the specified class of the specified policy map.
|
show table-map
|
Displays the configuration of a specified table map or of all table maps.
|
table-map (value mapping)
|
Creates and configures a mapping table for mapping and converting one packet-marking value to another.
|
show power
To display information about the power status, use the show power command in user EXEC or privileged EXEC mode.
show power [available | inline [interface number | module number] | redundancy-mode | status
{all | fan-tray fan-tray-number | module slot | power-supply pwr-supply-number} | total |
used]
Syntax Description
available
|
(Optional) Displays the available system power (margin).
|
inline
|
(Optional) Displays the inline power status.
|
interface number
|
(Optional) Specifies the interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, null, port-channel, and vlan. See the "Usage Guidelines" section for additional information.
|
module number
|
Displays the power status for a specific module.
|
redundancy-mode
|
(Optional) Displays the power-supply redundancy mode.
|
status
|
(Optional) Displays the power status.
|
all
|
Displays all the FRU types.
|
fan-tray fan-tray-number
|
Displays the power status for the fan tray.
|
module slot
|
Displays the power status for a specific module.
|
power-supply pwr-supply-number
|
Displays the power status for a specific power supply; valid values are 1 and 2.
|
total
|
(Optional) Displays the total power that is available from the power supplies.
|
used
|
(Optional) Displays the total power that is budgeted for powered-on items.
|
Defaults
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)SX1
|
The output was changed to include the total system-power information.
|
12.2(17b)SXA
|
This command was changed to include information about the inline power status for a specific module.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(18)SXF
|
The output was changed to include information about the high-capacity power supplies.
|
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.
Valid values for vlan-id are from 1 to 4094.
The Inline power field in the show power output displays the inline power that is consumed by the modules. For example, this example shows that module 9 has consumed 0.300 A of inline power:
Examples
This example shows how to display the available system power:
Router> show power available
system power available = 20.470A
This example shows how to display power-supply redundancy mode:
Router# show power redundancy-mode
system power redundancy mode = redundant
This command shows how to display the system-power status:
system power redundancy mode = combined
system power total = 3984.12 Watts (94.86 Amps @ 42V)
system power used = 1104.18 Watts (26.29 Amps @ 42V)
system power available = 2879.94 Watts (68.57 Amps @ 42V)
Power-Capacity PS-Fan Output Oper
PS Type Watts A @42V Status Status State
---- ------------------ ------- ------ ------ ------ -----
1 WS-CAC-3000W 2830.80 67.40 OK OK on
2 WS-CAC-1300W 1153.32 27.46 OK OK on
Note: PS2 capacity is limited to 2940.00 Watts (70.00 Amps @ 42V)
Fan Type Watts A @42V State
---- ------------------ ------- ------ -----
1 FAN-MOD-9 241.50 5.75 OK
Pwr-Requested Pwr-Allocated Admin Oper
Slot Card-Type Watts A @42V Watts A @42V State State
---- ------------------ ------- ------ ------- ------ ----- -----
1 WS-X6K-SUP2-2GE 145.32 3.46 145.32 3.46 on on
3 WS-X6516-GBIC 118.02 2.81 118.02 2.81 on on
5 WS-C6500-SFM 117.18 2.79 117.18 2.79 on on
7 WS-X6516A-GBIC 214.20 5.10 - - on off (insuff cooling capacity)
8 WS-X6516-GE-TX 178.50 4.25 178.50 4.25 on on
9 WS-X6816-GBIC 733.98 17.48 - - on off (connector rating
exceeded)
This example shows how to display the power status for all FRU types:
Router# show power status all
FRU-type # current admin state oper
power-supply 1 27.460A on on
module 2 4.300A - - (reserved)
This example shows how to display the power status for a specific module:
Router# show power status module 1
FRU-type # current admin state oper
This example shows how to display the power status for a specific power supply:
Router# show power status power-supply 1
FRU-type # current admin state oper
power-supply 1 27.460A on on
This example displays information about the high-capacity power supplies:
Router# show power status power-supply 2
Power-Capacity PS-Fan Output Oper
PS Type Watts A @42V Status Status State
---- ------------------ ------- ------ ------ ------ -----
1 WS-CAC-6000W 2672.04 63.62 OK OK on
2 WS-CAC-9000W-E 2773.68 66.04 OK OK on
This example shows how to display the total power that is available from the power supplies:
system power total = 27.460A
This example shows how to display the total power that is budgeted for powered-on items:
system power used = -6.990A
This command shows how to display the inline power status on the interfaces:
Router# show power inline
Interface Admin Oper Power ( mWatt ) Device
-------------------- ----- ---------- --------------- -----------
FastEthernet9/1 auto on 6300 Cisco 6500 IP Phone
FastEthernet9/2 auto on 6300 Cisco 6500 IP Phone
This command shows how to display the inline power status for a specific module:
Router# show power inline mod 7
Interface Admin Oper Power Device Class
---------- ----- ---------- ------- -------------- -----------
Gi7/1 auto on 6.3 Cisco IP Phone 7960 n/a
Gi7/2 static power-deny 0 Ieee PD 3
Related Commands
Command
|
Description
|
power enable
|
Turns on power for the modules.
|
power redundancy-mode
|
Sets the power-supply redundancy mode.
|
show power inline
To display the power status for a specified port or for all ports, use the show power inline command in privileged EXEC mode.
show power inline [interface-type slot/port] [actual | configured]
Syntax Description
interface-type
|
(Optional) Type of interface.
|
slot
|
(Optional) Slot number.
|
/port
|
(Optional) Port number.
|
actual
|
(Optional) Displays the present power status, which might not be the same as the configured power.
|
configured
|
(Optional) Displays the configured power status.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)XU
|
This command was introduced.
|
12.2(2)XT
|
This command was introduced on the Cisco 2600 series, the Cisco 3600 series, and the Cisco 3700 series routers to support switchport creation.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T to support switchport creation on Cisco 2600 series, the Cisco 3600 series, and Cisco 3700 series routers.
|
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
The show power inline command displays the amount of power used to operate a Cisco IP phone. To view the amount of power requested, use the show cdp neighbors command.
Examples
The following is sample output from the show power inline fa0/4 actual command asking for the actual status of each interface rather than what is configured for each:
Router# show power inline fastethernet 0/4 actual
-------------------- -----
Notice that the status shown for the FastEthernet interface 0/4, there is no power.
Related Commands
Command
|
Description
|
power inline
|
Determines how inline power is applied to devices on the specified Fast Ethernet port.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show ptp clock dataset
To display a summary of the Precision Time Protocol clock status, use the show ptp clock dataset command in privileged EXEC mode.
show ptp clock dataset [default | current]
Syntax Description
default
|
Displays the default PTP clock dataset.
|
current
|
Displays the current PTP clock dataset.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following examples show the output generated by this command:
Router# show ptp clock dataset default
CLOCK [Boundary Clock, domain 10]
Clock Identity: 0x2A:0:0:0:58:67:F3:4
Offset (log variance): 4252
router# show ptp clock dataset current
CLOCK [Boundary Clock, domain 10]
Offset From Master: 4661806827187470336
Mean Path Delay: 314023819427708928
Table 78 describes significant fields shown in the display.
Table 78 show ptp clock dataset Field Descriptions
Field
|
Description
|
Two Step Flag
|
Indicates whether the clock is sending timestamp information using a FOLLOW_UP message (a 2-step handshake) or not (a 1-step handshake).
|
Clock Identity
|
Unique identifier for the clock.
|
Number of Ports
|
Number of ports assigned to the PTP clock.
|
Priority1
|
Priority1 preference value of the PTP clock; the priority1 clock is considered first during clock selection.
|
Priority2
|
Priority2 preference value of the PTP clock; the priority2 clock is considered after all other clock sources during clock selection.
|
Domain number
|
PTP clocking domain number.
|
Slave only
|
Specifies whether the PTP clock is a slave-only clock.
|
Clock quality
|
Summarizes the quality of the grandmaster clock.
|
Class
|
Displays the time and frequency traceability of the grandmaster clock
|
Accuracy
|
Field applies only when the Best Master Clock algorithm is in use; indicates the expected accuracy of the master clock were the grandmaster clock.
|
Offset (log variance)
|
Offset between the local clock and an ideal reference clock.
|
Steps removed
|
Number of hops from the local clock to the grandmaster clock.
|
Offset From Master
|
Time offset between the slave and master clocks.
|
Mean Path Delay
|
Mean propagation time between the master and slave clocks.
|
show ptp clock dataset parent
To display a description of the Precision Time Protocol parent clock, use the show ptp dataset parent command in privileged EXEC mode.
show ptp clock dataset parent
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following example shows the output generated by this command:
Router# show ptp clock dataset parent
CLOCK [Boundary Clock, domain 10]
Observed Parent Offset (log variance): 0
Observed Parent Clock Phase Change Rate: 58087144
Identity: 0x3E:D3:D0:0:0:0:0:0
Offset (log variance): 4252
Table 79 describes significant fields shown in the display.
Table 79 show ptp clock dataset parent Field Descriptions
Field
|
Description
|
Parent Stats
|
Indicates the availability of parent statistics.
|
Observed Parent Offset (log variance)
|
The offset between the parent clock and the local clock.
|
Observed Parent Clock Phase Change Rate
|
This value indicates the parent clock speed relative to the slave clock. A positive value indicates that the parent clock is faster than the slaveclock ; a negative value indicates that the parent clock is slower than the slave clock.
|
Grandmaster clock
|
Summarizes the Grandmaster clock configuration.
|
Identity
|
The hardware address of the Grandmaster clock.
|
Priority1
|
The priority1 preference value of the PTP clock; the priority1 clock is considered first during clock selection.
|
Priority2
|
The priority2 preference value of the PTP clock; the priority2 clock is considered after all other clock sources during clock selection.
|
Clock Quality
|
Summarizes the quality of the Grandmaster clock.
|
Class
|
Displays the time and frequency traceability of the grandmaster clock
|
Accuracy
|
This field applies only when the Best Master Clock algorithm is in use; indicates the expected accuracy of the master clock were the grandmaster clock.
|
Offset (log variance)
|
The offset between the Grandmaster clock and the parent clock.
|
show ptp clock dataset time-properties
To display a summary of time properties for a Precision Time Protocol clock, use the show ptp dataset time-properties command in privileged EXEC mode.
show ptp clock dataset time-properties
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command HistoryGlobal configuration
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following example shows the output generated by this command:
Router# show ptp clock dataset time-properties
CLOCK [Boundary Clock, domain 10]
Current UTC Offset Valid: TRUE
Current UTC Offset: 10752
Frequency Traceable: TRUE
Table 80 describes significant fields shown in the display.
Table 80 show ptp clock dataset time-properties Field Descriptions
Field
|
Description
|
Current UTC Offset Valid
|
Indicates whether the current UTC offset is valid.
|
Current UTC Offset
|
Offset between the TAI and UTC in seconds.
|
Leap 59
|
Indicates whether the last minute of the current UTC day contains 59 seconds.
|
Leap 61
|
Indicates whether the last minute of the current UTC day contains 61 seconds.
|
Time Traceable
|
Indicates whether the value of the current UTC offset is traceable to a primary reference.
|
Frequency Traceable
|
Indicates whether the frequency used to determine the time scale is traceable to a primary reference.
|
PTP Timescale
|
Indicates whether the PTP grandmaster clock uses a PTP clock time scale.
|
Time Source
|
Time source used by the grandmaster clock.
|
show ptp clock running
To display a summary of the Precision Time Protocol clock status, use the show ptp clock running command in privileged EXEC mode.
show ptp clock running [domain]
Syntax Description
domain
|
Filters output by domain.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following example shows the output generated by this command:
Router# show ptp clock running
PTP Boundary Clock [Domain 1]
State Ports Pkts sent Pkts rcvd
Name Tx Mode Role Transport State Sessions
MASTER-1 unicast master Et0/0 - 5
MASTER-2 mcast master Et0/0 - 5
SLAVE unicast slave Et0/0 - 5
PTP Ordinary Clock [Domain 2]
State Ports Pkts sent Pkts rcvd
Name Tx Mode Role Transport State Sessions
MASTER unicast master Et0/0 - 5
Table 81 describes significant fields shown in the display.
Table 81 show ptp clock running Field Descriptions
Field
|
Description
|
State
|
State of the PTP clock.
|
Ports
|
Number of ports assigned to the PTP clock.
|
Pkts sent
|
Number of packets sent by the PTP clock.
|
Pkts rcvd
|
Number of packets received by the PTP clock.
|
Name
|
Name of the PTP clock port.
|
Tx Mode
|
Transmission mode of the PTP clock port (unicast or multicast).
|
Role
|
PTP role of the clock port (master or slave).
|
Transport
|
Physical port assigned to the clock port.
|
State
|
State of the clock port.
|
Sessions
|
Number of PTP sessions active on the clock port.
|
show ptp port dataset foreign-master
To display a summary of Precision Time Protocol foreign master records, use the show ptp port dataset foreign-master-record command in privileged EXEC mode.
show ptp port dataset foreign-master [domain]
Syntax Description
This command has no arguments or keywords.
Syntax Description
domain
|
Filters output by domain.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following example shows the output generated by this command.
Router# show ptp dataset foreign-master
PTP FOREIGN MASTER RECORDS
Number of foreign records 1, max foreign records 5
Foreign master port identity: clock id: 0x0:1E:4A:FF:FF:96:A2:A9
Foreign master port identity: port num: 1
Number of Announce messages: 8
Number of Current Announce messages: 6
Time stamps: 1233935406, 664274927
Table 82 describes significant fields shown in the display.
Table 82 show ptp port dataset foreign-master Field Descriptions
Field
|
Description
|
Interface
|
Currently foreign-master data is not displayed in the show command.
|
Number of foreign records
|
Number of foreign master records in router memory.
|
max foreign records
|
Maximum number of foreign records.
|
Best foreign record
|
Foreign record with the highest clock quality.
|
Foreign master port identity: clock id
|
Hardware address of the foreign master port.
|
Foreign master port identity: port number
|
Port number of the foreign master port.
|
Number of Announce messages
|
Number of Announce messages received from the foreign master clock.
|
Number of Current Announce messages
|
Number of current announcement messages.
|
Time stamps
|
Time stamps of current announcement messages.
|
show ptp port dataset port
To display a summary of Precision Time Protocol ports, use the show ptp port dataset port command in privileged EXEC mode.
show ptp dataset port
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command HistoryGlobal configuration
Release
|
Modification
|
15.0(1)S
|
This command was introduced.
|
Examples
The following example shows the output generated by this command.
Router# show ptp port dataset port
Clock Identity: 0x49:BD:D1:0:0:0:0:0
Min Delay Req Interval (log base 2): 42
Peer Mean Path Delay: 648518346341351424
Announce interval (log base 2): 0
Announce Receipt Timeout: 2
Sync Interval (log base 2): 0
Delay Mechanism: End to End
Peer Delay Request Interval (log base 2): 0
Table 83 describes significant fields shown in the display.
Table 83 show ptp port dataset port Field Descriptions
Field
|
Description
|
Clock Identity
|
Unique identifier for the clock.
|
Port Number
|
Port number on the PTP node.
|
Port State
|
State of the PTP port.
|
Min Delay Req Interval (log base 2)
|
Time interval permitted between Delay_Req messages.
|
Peer Mean Path Delay
|
One way propagation delay on the local port.
|
Announce interval (log base 2)
|
Mean interval between PTP announcement messages.
|
Announce Receipt Timeout
|
Number of intervals before a PTP announcement times out.
|
Sync Interval (log base 2)
|
Mean interval between PTP sync messages.
|
Delay Mechanism
|
Mechanism used for measuring propagation delay.
|
Peer Delay Request Interval (log base 2)
|
Interval permitted between Peer Delay Request messages.
|
PTP version
|
PTP version in use.
|
show pxf cpu access-lists
To display Parallel eXpress Forwarding (PXF) memory information for access control lists (ACLs), use the show pxf cpu access-lists command in privileged EXEC mode.
show pxf cpu access-lists [security | qos | pbr | compiled]
Cisco 10000 Series Router
show pxf cpu access-lists [security [ [tcam acl-name [detail] ] | flex-sum | children] | qos | pbr |
compiled]
Syntax Description
security
|
(Optional) Displays information about the security ACLs defined in Cisco IOS and compiled to the PXF. Also displays information about split ACLs, such as how much memory has been used.
|
tcam acl-name
|
(Optional) Displays information about the specified security ACL stored in ternary content addressable memory (TCAM).
This option is only available on the PRE3 for the Cisco 10000 series router.
|
detail
|
(Optional) Displays decoded information about the packet fields used for matching in the TCAM.
|
flex-sum
|
(Optional) Displays summary information describing the amount of memory allocated in the parallel express forwarding (PXF) engine for use by the flexible key construction microcode. This information is useful for design teams.
This option is only available on the PRE3 for the Cisco 10000 series router.
|
children
|
(Optional) Displays information for child policies. If an ACL is a template child, the output typically does not display the child information. Specifying the children keyword displays data for child policies, too, and shows the children and the parent policy of each child.
Use caution when using the children keyword as there might be thousands of child policies configured, which could have negative effects on the command output.
|
qos
|
(Optional) Displays information about the QoS ACLs defined in Cisco IOS and compiled to the PXF.
|
pbr
|
(Optional) Displays information about ACLs for policy-based routing (PBR).
|
compiled
|
(Optional) Displays information for all compiled Turbo-ACLs.
The PRE2 supports Turbo-ACLs and the compiled option. The PRE3 accepts the PRE2 compiled option, but does not implement Turbo-ACLs.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
12.3(7)XI1
|
This command was introduced on the PRE2 for the Cisco 10000 series router.
|
12.2(31)SB2
|
This command was introduced on the PRE3 for the Cisco 10000 series router.
|
Usage Guidelines
Cisco 10000 Series Router (PRE2)
Because memory is shared between TurboACLs and MiniACLs, they can interfere with each other's capacities. The Mini-ACL is automatically set up with space for 8191 Mini-ACLs at router start. If more than 8191 Mini-ACLs are created, another block of MiniACLs (4096) is allocated. This process is repeated as necessary until the router is out of External Column Memory (XCM) in any one bank that the Mini-ACLs need.
Cisco 10000 Series router (PRE3)
The PRE3 implements only TCAM ACLs. Turbo-ACLs and Mini-ACLs are not supported.
Examples
The sample output from the show pxf cpu access-lists security command (see Sample Output) is based on the configuration of the access control list (ACL) called test_list (see ACL Configuration). The sample output is divided into several sections with a description of the type of information displayed in each.
ACL Configuration
Router# show pxf cpu access-lists test_list
Extended IP access list test_list (Compiled)
10 permit ip any host 10.1.1.1
20 permit ip any host 10.1.1.2
30 permit ip any host 10.1.1.3
40 permit ip any host 10.1.1.4
50 permit ip any host 10.1.1.5
60 permit ip any host 10.1.1.6
70 permit ip any host 10.1.1.7
80 permit ip any host 10.1.1.8
90 permit ip any host 10.1.1.9
100 permit ip any host 10.1.1.11
110 permit ip any host 10.1.1.12
Sample Output
The following sample output describes the information displayed in the first section of the command output from the show pxf cpu access-lists security command:
Router# show pxf cpu access-lists security
PXF Security ACL statistics:
ACL State Tables Entries Config Fragment Redundant Memory ACL_index
1 Operational 1 - - - - 0Kb 1
sl_def_acl Operational 2 - - - - 0Kb 2
test Operational 3 - - - - 0Kb 3
test_list Operational 1 12 11 0 0 7Kb 1
Table 84, Part 1, describes the significant fields shown in the display.
Table 84, Part 1 show pxf cpu access-lists security Field Descriptions
Field
|
Description
|
ACL
|
Identifies the ACL by name or number.
|
State
|
Displays the current state of the ACL:
• Copying—ACL is in the process of being created or compiled.
• Operational—ACL is active and filtering packets.
• Out of acl private mem—ACL has run out of the private memory that was allocated exclusively to it.
• Out of shared mem—ACL has run out of the memory that it shares with other ACLs.
• Unknown Failure—ACL has failed because of an uncategorized reason.
• Unneeded—ACL was allocated but is not currently in use.
|
Tables
|
An indicator of whether the ACL has been split into more than one PXF pass. The first three ACLs in the output are MiniACLs, and have the ACL_index duplicated in the Tables column.
|
Entries
|
The count of ACL rules as seen by the Turbo compiler. This is the sum of the Config, Fragment, and Redundant columns plus 1.
|
Config
|
The count of rules for this ACL.
|
Fragment
|
The count of extra rules added to handle fragment handling, where Layer 4 information is needed but not available in a packet fragment.
|
Redundant
|
The count of rules that are not needed because they are covered by earlier rules.
|
Memory
|
The amount of PXF XCM in use for the ACL.
|
ACL_index
|
The index of the ACL in XCM.
|
The following sample output describes the information displayed in the next section of the command output from the show pxf cpu access-lists security command:
First level lookup tables:
Block Use Rows Columns Memory used
0 TOS/Protocol 1/128 1/32 16384
1 IP Source (MS) 1/128 1/32 16384
2 IP Source (LS) 1/128 1/32 16384
3 IP Dest (MS) 2/128 1/32 16384
4 IP Dest (LS) 12/128 1/32 16384
5 TCP/UDP Src Port 1/128 1/32 16384
6 TCP/UDP Dest Port 1/128 1/32 16384
7 TCP Flags/Fragment 1/128 1/32 16384
Table 84, Part 2, describes the significant fields shown in the display.
Table 84, Part 2 show pxf cpu access-lists security Field Descriptions
Field
|
Description
|
Block
|
Indicates the block number.
|
Use
|
Describes the IP packet field that is being matched.
|
Rows
|
An indication of where the largest variety of values are in use in the ACLs that are being applied. In the output, 12/128 means that there are 12 different values of significance in the field. If there are other rules added and the value exceeds 128, more memory will be needed to accommodate the new rules.
|
Columns
|
An indication of the number of TurboACLs in PXF memory. In the output, 1/32 means there is only one TurboACL in PXF memory. If there are more than 31 added, another chunk of memory is needed to accommodate the new ACLs.
|
Memory used
|
Displays the total amount of memory used for this particular lookup table.
|
The following sample output describes the information displayed in the next section of the command output from the show pxf cpu access-lists security command. There are 16 banks of XCM in each PXF column. This output section shows the usage level of each bank.
Banknum Heapsize Freesize %Free
Table 84, Part 3, describes the significant fields shown in the display.
Table 84, Part 3 show pxf cpu access-lists security Field Descriptions
Field
|
Description
|
Banknum
|
The block of memory used for this particular lookup table.
|
Heapsize
|
The total amount of memory, in bytes, allocated for this block.
|
Freesize
|
The amount of memory, in bytes, that is currently available for use by this block of memory.
|
%Free
|
The percentage of memory that is free and available for use for this block of memory. When the %Free drops to 0, the router cannot hold any more ACLs in PXF memory, and any new ACL will not pass traffic.
|
This section of the sample command output indicates the memory usage of the MiniACLs in the router. All of the rows state about the same thing. To determine the actual number of MiniACLs in play, divide the memory used in any of blocks 1 to 10 by 256, or blocks 11 to 14 by 16.
Block Use Memory Used %Free
10 TCP Flags/Fragment 768 99
13 Destination Port 2 48 99
14 Destination Port 2 48 99
The following describes the information displayed in the last section of the sample output from the show pxf cpu access-lists security command:
Available MiniACL count = 8191
Usable ranges(inclusive):
Table 84, Part 4, describes the significant fields shown in the display.
Table 84, Part 4 show pxf cpu access-lists security Field Descriptions
Field
|
Description
|
Available MiniACL
|
The number of ACLs currently available for allocation in XCM.
|
Usable ranges
|
The ACL indexes that will be assigned to MiniACLs.
|
PRE2 and PRE3 Security ACLs Examples (Cisco 10000 Series Router)
This section compares the output from the show pxf cpu access-lists security command when issued on the PRE2 and PRE3.
For the PRE2, the following sample output displays VMR (value, plus a mask and result) data for the ACL named ICMP_IGMP_MATCH:
Router# show pxf cpu access-lists security tcam ICMP_IGMP_MATCH detail
-------------------------------------------------------------
VMR Format - handle: 524607B4
Format has 5 fields, refcount = 1
Field: Format, FIXED, start_bit = 69, end_bit = 71
Field: ACL index, FIXED, start_bit = 54, end_bit = 68
Field: Flags, FIXED, start_bit = 43, end_bit = 53
Field: L4 proto, FIXED CNV, start_bit = 16, end_bit = 23
Field: L4 source port, FIXED CNV, start_bit = 0, end_bit = 15 Total bits = 53, format = 72
GMR used: 5 Col 2 LKBP Vector: 544
-------------------------------------------------------------
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00000B00/0000FFFF
L4 proto: 00000001/000000FF
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00000301/0000FFFF
L4 proto: 00000001/000000FF
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00001300/0000FF00
L4 proto: 00000002/000000FF
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00001400/0000FF00
L4 proto: 00000002/000000FF
For the PRE3, the following sample output displays for the show pxf cpu access-lists security command. Notice that the output does not include the columns shown above that are relevant to only the PRE2 and the output no longer displays first-level lookup tables.
Router# show pxf cpu access-lists security
PXF Security ACL statistics:
STANDARD_MATCH_PERMIT Operational 116
SRC_IP_MATCH144 Operational 102
DST_IP_MATCH Operational 113
DST_IP_MATCH144 Operational 112
PROTOCOL_MATCH Operational 104
PROTOCOL_MATCH144 Operational 103
FRAG_MATCH Operational 109
PRECEDENCE_TOS_MATCH Operational 106
PRECEDENCE_TOS_MATCH144 Operational 105
Related Commands
Command
|
Description
|
show pxf cpu statistics
|
Displays PXF CPU statistics.
|
show pxf statistics
|
Displays a chassis-wide summary of PXF statistics.
|
show pxf cpu iedge
To display parallel express forwarding (PXF) policy and template information, use the show pxf cpu iedge command in privileged EXEC mode.
show pxf cpu iedge [detail | policy policy-name | template]
Syntax Description
detail
|
(Optional) Displays detailed information about policies and templates.
|
policy policy-name
|
(Optional) Displays summary policy information.
|
template
|
(Optional) Displays summary template information.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
Examples
The following example shows PXF template information:
Router# show pxf cpu iedge template
Super ACL name OrigCRC Class Count CalcCRC
1sacl_2 4EA94046 2 00000000
Related Commands
Command
|
Description
|
show pxf statistics
|
Displays a summary of PXF statistics.
|
show pxf cpu qos
To display Parallel eXpress Forwarding (PXF) External Column Memory (XCM) contents related to a particular policy, use the show pxf cpu qos command in privileged EXEC mode.
show pxf cpu qos [policy-map policy-name | vcci]
Cisco 10000 Series Router
show pxf cpu qos [0-65535 | classifiers | flex-sum | policy-map policy-name | vcci-maps]
Syntax Description
0-65535
|
(Optional) Displays information for the Virtual Channel Circuit Identifier (VCCI) you specify.
|
classifiers
|
(Optional) Displays information about the criteria used to classify traffic.
|
flex-sum
|
(Optional) Displays summary information describing the amount of memory allocated in the PXF engine for use by the flexible key construction microcode.
Note This option is only available on the Cisco 10000 series router for the PRE3.
|
policy-map policy-name
|
(Optional) Displays per-policy map information.
|
vcci
|
(Optional) Displays VCCI map values.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
12.3(7)XI1
|
This command was introduced on the Cisco 10000 series router for the PRE2.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(31)SB2
|
This command was introduced on the PRE3 for the Cisco 10000 series router.
|
Usage Guidelines
This command is useful in verifying the presence of a policy on interfaces and indexes programmed in the PXF.
Examples
The following example shows XCM contents related to a policy called police_test, which is defined as follows:
Router# show pxf cpu qos police_test
Output Policymap: police_test
Vcci: A05 Flags: 4 Policymap_index: 6 Policymap_data_index: 12
OUT AT1/0/0.111 (0x71764660) ref_count 1
Output Action Table Contents for vcci 0xA05 - Policymap index: 6
class-name: high-priority class_index: 0 action_flags: 0x00
srp_class_id: 0x01 prec/dscp: 0x00 cos: 0
discard_class: 0x00 exp_value: 0
class-name: low-priority class_index: 1 action_flags: 0x10
srp_class_id: 0x00 prec/dscp: 0x00 cos: 0
discard_class: 0x00 exp_value: 0
class-name: class-default class_index: 2 action_flags: 0x00
srp_class_id: 0x00 prec/dscp: 0x00 cos: 0
discard_class: 0x00 exp_value: 0
Related Commands
Command
|
Description
|
show pxf cpu statistics qos
|
Displays match statistics for a service policy on an interface.
|
show pxf dma
To display the current state of direct memory access (DMA) buffers, error counters, and registers on the Parallel eXpress Forwarding (PXF), use the show pxf dma command in privileged EXEC mode.
show pxf dma [buffers | counters | reassembly | registers]
Cisco 10000 Series Router (PRE3 only)
show pxf dma [buffers | counters | reassembly | registers] [brief | config | errors | status]
Syntax Description
buffers
|
(Optional) Displays PXF DMA buffers information.
|
counters
|
(Optional) Displays packet and error counters for the PXF DMA engine.
|
reassembly
|
(Optional) Displays PXF reassembly table usage information.
|
registers
|
(Optional) Displays PXF DMA registers information.
|
brief
|
(Optional) Displays PXF DMA information, including the initialization state of each block in the PXF API and any errors that occurred.
Note This option is available on the PRE3 only.
|
config
|
(Optional) Displays a configuration summary of the registers in each of the PXF DMA blocks.
Note This option is available on the PRE3 only.
|
errors
|
(Optional) Displays the errors that occurred in each of the PXF DMA blocks.
Note This option is available on the PRE3 only.
|
status
|
(Optional) Displays the initialization state of each PXF DMA block. In normal operation, all blocks display the enabled state.
Note This option is available on the PRE3 only.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
12.3(7)XI
|
This command was integrated into Cisco IOS Release 12.3(7)XI and implemented on the Cisco 10000 series router for the PRE2.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2 and implemented on the Cisco 10000 series router for the PRE3.
|
Examples
The following example shows PXF DMA buffers information:
Router# show pxf dma buffers
PXF To-RP DMA Ring Descriptors & Buffers:
Descriptor Buffer Buffer Descriptor
Address Address Length(b) Flags
0 0x0CA06340 0x0AC097C0 512 0x0002
1 0x0CA06350 0x0AC088C0 512 0x0002
2 0x0CA06360 0x0AC07C40 512 0x0002
3 0x0CA06370 0x0AC0B5C0 512 0x0002
4 0x0CA06380 0x0AC0CC40 512 0x0002
5 0x0CA06390 0x0AC08640 512 0x0002
6 0x0CA063A0 0x0AC0C240 512 0x0002
7 0x0CA063B0 0x0AC08B40 512 0x0002
8 0x0CA063C0 0x0AC0AE40 512 0x0002
9 0x0CA063D0 0x0AC0BAC0 512 0x0002
10 0x0CA063E0 0x0AC0C9C0 512 0x0002
11 0x0CA063F0 0x0AC09CC0 512 0x0002
12 0x0CA06400 0x0AC0C740 512 0x0002
13 0x0CA06410 0x0AC0A6C0 512 0x0002
14 0x0CA06420 0x0AC0B0C0 512 0x0002
15 0x0CA06430 0x0AC09040 512 0x0002
16 0x0CA06440 0x0AC0A440 512 0x0002
17 0x0CA06450 0x0AC065C0 512 0x0002
18 0x0CA06460 0x0AC06FC0 512 0x0002
19 0x0CA06470 0x0AC06340 512 0x0002
20 0x0CA06480 0x0AC07240 512 0x0002
21 0x0CA06490 0x0AC092C0 512 0x0002
22 0x0CA064A0 0x0AC0D140 512 0x0002
23 0x0CA064B0 0x0AC0C4C0 512 0x0002
24 0x0CA064C0 0x0AC07740 512 0x0002
25 0x0CA064D0 0x0AC09540 512 0x0002
26 0x0CA064E0 0x0AC0A940 512 0x0002
27 0x0CA064F0 0x0AC06840 512 0x0002
28 0x0CA06500 0x0AC08140 512 0x0002
29 0x0CA06510 0x0AC06D40 512 0x0002
30 0x0CA06520 0x0AC07EC0 512 0x0002
31 0x0CA06530 0x0AC0ABC0 512 0x0003
PXF From-RP DMA Ring Descriptors & Buffers:
Descriptor Buffer Buffer Descriptor Context
Address Address Length(b) Flags Bit
0 0x0CA06580 0x00000000 0 0x0000 Not set
1 0x0CA06590 0x00000000 0 0x0000 Not set
2 0x0CA065A0 0x00000000 0 0x0000 Not set
3 0x0CA065B0 0x00000000 0 0x0000 Not set
4 0x0CA065C0 0x00000000 0 0x0000 Not set
5 0x0CA065D0 0x00000000 0 0x0000 Not set
6 0x0CA065E0 0x00000000 0 0x0000 Not set
7 0x0CA065F0 0x00000000 0 0x0000 Not set
8 0x0CA06600 0x00000000 0 0x0000 Not set
9 0x0CA06610 0x00000000 0 0x0000 Not set
10 0x0CA06620 0x00000000 0 0x0000 Not set
11 0x0CA06630 0x00000000 0 0x0000 Not set
12 0x0CA06640 0x00000000 0 0x0000 Not set
13 0x0CA06650 0x00000000 0 0x0000 Not set
14 0x0CA06660 0x00000000 0 0x0000 Not set
15 0x0CA06670 0x00000000 0 0x0001 Not set
Table 85 describes the fields shown in the display.
Table 85 show pxf dma Field Descriptions
Field
|
Description
|
Descriptor Address
|
Memory address pointing to the descriptor for this buffer.
|
Buffer Address
|
Address of this buffer in memory.
|
Buffer Length
|
Length, in bytes, of this particular buffer.
|
Descriptor Flags
|
Internal flags identifying this buffer's use and status.
|
Context Bit
|
State of the context bit which is set when the buffer is currently in use by a context (the basic unit of packet processing).
|
Related Commands
Command
|
Description
|
clear pxf
|
Clears PXF counters and statistics.
|
show pxf cpu
|
Displays PXF CPU statistics.
|
show pxf microcode
|
Displays the microcode version running on the PXF.
|
show pxf max-logical-interfaces
To display the configuration for the maximum number of classes permitted per QoS policy in PXF and the maximum number of PXF logical interfaces allowed on the router, use the show pxf max-logical-interfaces command in privileged EXEC mode.
show pxf max-logical-interfaces
Syntax DescriptionDisplays the configured maximum number of classes permitted per QoS policy in PXF and the maximum number of PXF logical interfaces.
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(20)S5
|
This command was introduced.
|
Usage Guidelines
The show pxf max-logical-interfaces command is used to verify if the pxf max-logical-interfaces configuration change was accepted by the router. The output from this command provides the settings for the maximum number of classes permitted per QoS policy in PXF and the number of PXF logical interfaces as set in both the running configuration file and the startup configuration file. The settings listed in the startup configuration file are the current settings on the router; the settings listed in the running configuration will be the settings on the router when the router is reloaded.
Examples
In the following example, the pxf max-logical-interfaces 16k command has been entered to change the setting from the previous setting of 4k. The router, however, has not been rebooted with the changes saved to the running configuration.
Router# show pxf max-logical-interfaces
PXF Max classes per interface: 23
PXF Max classes per interface: 64
Related Commands
Command
|
Description
|
pxf max-logical-interfaces
|
Configures the maximum number of PXF logical interfaces permitted on the router.
|
show qm-sp port-data
To display information about the QoS-manager switch processor, use the show qm-sp port-data command in privileged EXEC mode.
show qm-sp port-data mod port
Syntax Description
mod port
|
Module and port number; see the "Usage Guidelines" section for valid values.
|
Defaults
This command has no default settings.
Command Modes
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
This command is supported by the supervisor engine only and can be entered only from the Catalyst 6500 series switch console (see the remote login command).
The mod port arguments designate 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 module number are from 1 to 13 and valid values for the port number are from 1 to 48.
Enter the show qm-sp port-data command to verify the values that are programmed in the hardware.
Examples
This example shows how to display information about the QoS manager:
Router# show qm-sp port-data 1 2
-----------------------------------------------------------------------------
* Type: Tx[1p2q2t] Rx[1p1q4t] [0] Pinnacle
* Per-Port: [Untrusted] Default COS[0] force[0] [VLAN based]
-----------------------------------------------------------------------------
* COSMAP(C[Q/T]) TX: 0[1/1] 1[1/1] 2[1/2] 3[1/2] 4[2/1] 5[3/1] 6[2/1] 7[2/2]
RX: 0[1/1] 1[1/1] 2[1/2] 3[1/2] 4[1/3] 5[2/1] 6[1/3] 7[1/4]
-----------------------------------------------------------------------------
* WRR bandwidth: [7168 18432]
* TX queue limit(size): [311296 65536 65536]
* WRED queue[1]: failed (0x82)
-----------------------------------------------------------------------------
* TX drop thr queue[1]: type[2 QOS_SCP_2_THR] dropThr[311104 311104]
queue[2]: type[2 QOS_SCP_2_THR] dropThr[61504 61504]
* RX drop threshold: type[4 QOS_SCP_4_THR] dropThr[62259 62259 62259 62259]
* RXOvr drop threshold: type[0 UNSUPPORTED] dropThr[16843009 131589 61504 61504]
* TXOvr drop threshold: type[0 UNSUPPORTED] dropThr[67174656 260 16843009 131589]
Related Commands
Command
|
Description
|
rcv-queue queue-limit
|
Sets the size ratio between the strict-priority and standard receive queues.
|
remote login
|
Accesses the Catalyst 6500 series switch console or a specific module.
|
wrr-queue bandwidth
|
Allocates the bandwidth between the standard transmit queues.
|
wrr-queue queue-limit
|
Sets the transmit-queue size ratio on an interface.
|
wrr-queue threshold
|
Configures the drop-threshold percentages for the standard receive and transmit queues on 1q4t and 2q2t interfaces.
|
show rbscp
To display state and statistical information about Rate Based Satellite Control Protocol (RBSCP) tunnels, use the show rbscp command in user EXEC or privileged EXEC mode.
show rbscp {all | inbound | state | statistics} [tunnel tunnel-number]
Syntax Description
all
|
Displays both RBSCP state and RBSCP statistical information.
|
inbound
|
Displays all the RBSCP inbound queue dump information.
|
state
|
Displays the RBSCP state information.
|
statistics
|
Displays RBSCP statistical information.
|
tunnel tunnel-number
|
(Optional) Displays the RBSCP information for a specific tunnel interface in the range from 0 to 2147483647. If a tunnel interface is not specified, information for all RBSCP tunnels is displayed.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.3(7)T
|
This command was introduced.
|
12.4(22)T
|
This command was modified. The inbound keyword was added.
|
Cisco IOS 2.1 XE
|
This command was integrated into Cisco IOS XE Release 2.1.
|
Usage Guidelines
The output of this command is useful when you need to configure and monitor RBSCP tunnels. The output shows various state and statistical information about RBSCP tunnels.
Examples
The following is sample output from the show rbscp all command:
Tunnel0 is up, line protocol is up
RBSCP operational state: IS OPENING
RBSCP operating mode: (264h) ack_split window_stuffing inorder SCTP_report
RTT: 550 ms srtt_sa: 0 srtt_sv: 4
sentQ: num packets: 0, num bytes: 0
tmitQ: num packets: 0, num bytes: 0
RBSCP protocol statistics:
Init FWD-TSNs sent 0, received 0
TUNNEL-UPs sent 0, received 0
CLOSEDs sent 0, received 0
TSNs sent 0, resent 0, lost by sender 0
TSNs received 0 (duplicates 0)
FWD-TSNs sent 63 (heartbeats 0)
FWD-TSNs received 0 (ignored 0)
FWD-TSNs caused 0 packet drops, 0 whole window drops
SACKs sent 0, received 0 (ignored 0)
Failed sends into the: tunnel 1, network 0
Dropped due to: excess delay 0, tmit queue full 0
Max on any queue: num packets: 0, num bytes: 0
Table 86 describes the significant fields shown in the display.
Table 86 show rbscp all Field Descriptions
Field
|
Description
|
Tunneln is {up | down}
|
Interface is currently active (up) or inactive (down).
|
line protocol is {up | down | administratively down}
|
Shows line protocol up if a valid route is available to the tunnel destination. Shows line protocol down if no route is available or if the route would be recursive.
|
RBSCP operational state
|
Indicates the current RBSCP state.
|
RBSCP operating mode
|
Indicates the RBSCP operating mode.
|
window step
|
Step size for the window scale.
|
drop scale
|
Scale factor for the number of bytes that can be queued before packets are dropped on the output side.
|
Ack split size
|
Number of TCP acknowledgements to send for every acknowledgement received.
|
input drop scale
|
Scale factor for the number of bytes that can be queued before packets are dropped on the input side.
|
initial TSN
|
Transport Sequence Number (TSN) of the first outgoing RBSCP/IP packet sent to a peer. RBSCP uses sequence numbers to ensure a reliable service. Peers will send the TSN back in the acknowledgment packet.
|
fuzz factor
|
Value added to the RBSCP delay clock to pad the delay when large round-trip time (RTT) fluctuations occur.
|
next TSN
|
TSN of the next outgoing RBSCP/IP packet.
|
next sequence
|
Next sequence number to use, in hexadecimal format.
|
current outstanding
|
Current number of bytes that are in transit or are unacknowledged.
|
max out per RTT
|
Maximum number of bytes allowed to be sent out per RTT.
|
packets sent since SACK
|
Number of packets sent since an RBSCP Selective Acknowledgement (SACK).
|
cumulative ack
|
Cumulative acknowledgement point that is the highest in sequence TSN that was received from a peer.
|
TSN at SACK
|
Value of highest TSN for the last SACK that was received from a peer.
|
last cumulative ack
|
Last cumulative acknowledgement point that was received from the peer.
|
last delivered TSN
|
Last TSN received that was subsequently delivered to an upper level protocol.
|
next FWDTSN corr
|
Next FWD_TSN correlation entry to use.
|
RTO
|
Retransmission timeout, in milliseconds.
|
RTT
|
Round-trip time estimate, in milliseconds.
|
srtt_sa
|
Smoothed round-trip time average.
|
srtt_sv
|
Smoothed round-trip time variance.
|
sentQ
|
Number of packets and bytes sent but not yet acknowledged.
|
tmitQ
|
Number of packets and bytes ready to be sent.
|
Init FWD-TSNs
|
Number of TSNs sent and received for initializing the RBSCP tunnel.
|
TUNNEL-UPs
|
Number of TUNNEL_UP messages sent and received.
|
CLOSEDs
|
Number of CLOSED messages sent and received.
|
heartbeats
|
Heartbeats are equivalent to keepalive messages.
|
Recovered with RTX
|
Number of packets recovered using a retransmitted message.
|
Received with delay
|
Number of packets that included a delay value.
|
Most released at once
|
Maximum burst of packets sent in one interval.
|
Failed sends
|
Number of packets that were sent but failed because of an internal error, such as no route or the underlying interface is down.
|
The following is sample output from the show rbscp state command:
Tunnel0 is up, line protocol is up
RBSCP operational state: IS OPENING
RBSCP operating mode: (264h) ack_split window_stuffing inorder SCTP_report
RTT: 550 ms srtt_sa: 0 srtt_sv: 4
sentQ: num packets: 0, num bytes: 0
tmitQ: num packets: 0, num bytes: 0
The following is sample output from the show rbscp statistics command:
Router# show rbscp statistics tunnel 0
Tunnel0 is up, line protocol is up
RBSCP protocol statistics:
Init FWD-TSNs sent 0, received 0
TUNNEL-UPs sent 0, received 0
CLOSEDs sent 0, received 0
TSNs sent 0, resent 0, lost by sender 0
TSNs received 0 (duplicates 0)
FWD-TSNs sent 136 (heartbeats 0)
FWD-TSNs received 0 (ignored 0)
FWD-TSNs caused 0 packet drops, 0 whole window drops
SACKs sent 0, received 0 (ignored 0)
Failed sends into the: tunnel 1, network 0
Dropped due to: excess delay 0, tmit queue full 0
Max on any queue: num packets: 0, num bytes: 0
Related Commands
Command
|
Description
|
clear rbscp
|
Resets and restarts RBSCP tunnels.
|
show redundancy
To display current or historical status and related information on planned or logged handovers, use the show redundancy command in user EXEC or privileged EXEC mode.
Privileged EXEC Mode
show redundancy [clients | counters | debug-log | handover | history | inter-device | states | switchover | switchover history]
User EXEC Mode
show redundancy {clients | counters | history | states | switchover}
Syntax Description
clients
|
(Optional) Displays the redundancy-aware client-application list.
|
counters
|
(Optional) Displays redundancy-related operational measurements.
|
debug-log
|
(Optional) Displays up to 256 redundancy-related debug entries.
|
handover
|
(Optional) Displays details of any pending scheduled handover.
|
history
|
(Optional) Displays past status and related information about logged handovers. This is the only keyword supported on the Cisco AS5800.
|
inter-device
|
(Optional) Displays redundancy interdevice operational state and statistics.
|
states
|
(Optional) Displays redundancy-related states: disabled, initialization, standby, active (various substates for the latter two), client ID and name, length of time since the client was sent the progression, and event history for the progression that was sent to the client.
|
switchover
|
(Optional) Displays the switchover counts, the uptime since active, and the total system uptime.
|
switchover history
|
(Optional) Displays redundancy switchover history.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.3(6)AA
|
This command was introduced in privileged EXEC mode.
|
12.2(8)T
|
This command was integrated into Cisco IOS Release 12.2(8)T. Support for the Cisco AS5800 and Cisco AS5850 is not included in this release.
|
12.2(8)MC2
|
This command was modified. This command was made available in user EXEC mode.
|
12.2(11)T
|
The privileged EXEC mode form of this command was implemented on the Cisco AS5800 and Cisco AS5850.
|
12.2(14)SX
|
The user EXEC mode form of this command was implemented on the Supervisor Engine 720.
|
12.2(18)S
|
This command was implemented on Cisco 7304 routers running Cisco IOS Release 12.2S.
|
12.2(20)S
|
The states, counters, clients, history, and switchover history keywords were added.
|
12.2(17d)SXB
|
Support for the user EXEC mode form of this command was extended to the Supervisor Engine 2.
|
12.3(8)T
|
The inter-device keyword was added to the privileged EXEC form of the command.
|
12.3(11)T
|
The user EXEC form of this command was integrated into Cisco IOS Release 12.3(11)T.
|
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.
|
12.2(31)SGA
|
This command was integrated into Cisco IOS Release 12.2(31)SGA.
|
12.2(33)SRB
|
The clients keyword was enhanced to provide information about the status of each client.
|
12.2(33)SRB1
|
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.
|
12.2(31)SXH
|
This command was integrated into Cisco IOS Release 12.2(31)SXH.
|
12.2(33)SRE
|
This command was integrated into Cisco IOS Release 12.2(33)SRE.
|
Cisco IOS XE Release 3.1S
|
More information regarding the states keyword was added.
|
Usage Guidelines
Cisco AS5800
Use this command from the router-shelf console to determine when failover is enabled. Use this command with the history keyword to log failover events.
Cisco AS5850
To use this command, the router must have two route-switch-controller (RSC) cards installed and must be connected to one of them.
Examples
The following example shows how to display information about the RF client:
Router# show redundancy clients
clientID = 0 clientSeq = 0 RF_INTERNAL_MSG
clientID = 25 clientSeq = 130 CHKPT RF
clientID = 5026 clientSeq = 130 CHKPT RF
clientID = 5029 clientSeq = 135 Redundancy Mode RF
clientID = 5006 clientSeq = 170 RFS client
clientID = 6 clientSeq = 180 Const OIR Client
clientID = 7 clientSeq = 190 PF Client
clientID = 5008 clientSeq = 190 PF Client
clientID = 28 clientSeq = 330 Const Startup Config
clientID = 29 clientSeq = 340 Const IDPROM Client
clientID = 65000 clientSeq = 65000 RF_LAST_CLIENT
The output displays the following information:
•
clientID displays the client's ID number.
•
clientSeq displays the client's notification sequence number.
•
Current RF state.
The following example shows how to display information about the RF counters:
Router# show redundancy counters
tx msg length invalid = 0
client not rxing msgs = 0
rx peer msg routing errors = 0
tx buffers unavailable = 0
buffer release errors = 0
duplicate client registers = 0
failed to register client = 0
The following example shows information about the RF history:
Router# show redundancy history
00:00:00 client added: RF_INTERNAL_MSG(0) seq=0
00:00:00 client added: RF_LAST_CLIENT(65000) seq=65000
00:00:02 client added: Const Startup Config Sync Clien(28) seq=330
00:00:02 client added: CHKPT RF(25) seq=130
00:00:02 client added: PF Client(7) seq=190
00:00:02 client added: Const OIR Client(6) seq=180
00:00:02 client added: Const IDPROM Client(29) seq=340
00:00:02 *my state = INITIALIZATION(2) *peer state = DISABLED(1)
00:00:02 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=11
00:00:02 RF_PROG_INITIALIZATION(100) CHKPT RF(25) op=0 rc=11
00:00:02 RF_PROG_INITIALIZATION(100) Const OIR Client(6) op=0 rc=11
00:00:02 RF_PROG_INITIALIZATION(100) PF Client(7) op=0 rc=11
The following example shows information about the RF state:
Router# show redundancy states
Redundancy Mode (Operational) = Route Processor Redundancy
Redundancy Mode (Configured) = Route Processor Redundancy
Manual Swact = Disabled Reason: Simplex mode
Communications = Down Reason: Simplex mode
client_notification_TMR = 30000 milliseconds
keep_alive TMR = 4000 milliseconds
If you enter the show redundancy states command with stateful switchover (SSO) configured, the Redundancy Mode (Operational) and the Redundancy Mode (Configured) fields display stateful switchover.
The following example shows how to display the switchover counts, the uptime since active, and the total system uptime:
Router> show redundancy switchover
Switchovers this system has experienced : 1
Uptime since this supervisor switched to active : 1 minute
Total system uptime from reload : 2 hours, 47 minutes
Example: Setting the terminal length for the Cisco ASR 1006
The following example shows how to set the terminal length value to pause the multiple-screen output:
Router# terminal length 5
Router# show redundancy states
peer state = 8 -STANDBY HOT
Example: Cisco AS5850
The following is sample output from the show redundancy handover and show redundancy states commands on the Cisco AS5850:
Router# show redundancy handover
No busyout period specified
Handover pending at 23:00:00 PDT Wed May 9 2001
Router# show redundancy states
my state = 14 -ACTIVE_EXTRALOAD
peer state = 4 -STANDBY COLD
Redundancy Mode = Handover-split: If one RSC fails, the peer RSC will take over the
feature boards
Maintenance Mode = Disabled
Manual Swact = Disabled Reason: Progression in progress
client_notification_TMR = 30000 milliseconds
keep_alive TMR = 4000 milliseconds
Example: Cisco AS5800
The following is sample output from the show redundancy command on the Cisco AS5800:
Hub is in 'active' state.
Clock is in 'active' state.
Hub is in 'backup' state.
Clock is in 'backup' state.
Example: Cisco AS5800 with History
The following is sample output from the show redundancy history command on the Cisco AS5800:
Router# show redundancy history
DSC Redundancy Status Change History:
981130 18:56 Slot 12 DSC: Hub, becoming active - RS instruction
981130 19:03 Slot 12 DSC: Hub, becoming active - D13 order
Example: Cisco AS5800 Router Shelves as Failover Pair
The following is sample output from two Cisco AS5800 router shelves configured as a failover pair. The active router shelf is initially RouterA. The show redundancy history and show redundancy commands have been issued. The show redundancy command shows that failover is enabled, shows the configured group number, and shows that this router shelf is the active one of the pair. Compare this output with that from the backup router shelf (RouterB) that follows.
Note
When RouterA is reloaded, thereby forcing a failover, new entries are shown on RouterB when the
show redundancy history command is issued after failover has occurred.
Log from the First Router (RouterA)
RouterA# show redundancy history
DSC Redundancy Status Change History:
010215 18:17 Slot -1 DSC:Failover configured -> ACTIVE role by default.
010215 18:18 Slot -1 DSC:Failover -> BACKUP role.
010215 18:18 Slot 12 DSC:Failover -> ACTIVE role.
010215 18:18 Slot 12 DSC:Hub, becoming active - arb timeout
failover mode enabled, failover group = 32
Hub is in 'active' state.
Clock is in 'active' state.
Proceed with reload? [confirm] y
*Feb 15 20:19:11.059:%SYS-5-RELOAD:Reload requested
System Bootstrap, Version xxx
Copyright xxx by cisco Systems, Inc.
C7200 processor with 131072 Kbytes of main memory
Log from the Second Router (RouterB)
failover mode enabled, failover group = 32
Hub is in 'backup' state.
Clock is in 'backup' state.
*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Switching to DSC 13
*Feb 16 03:24:53.931:%DSC_REDUNDANCY-3-BICLINK:Failover:changing to active mode
*Feb 16 03:24:54.931:%DIAL13-3-MSG:
02:32:06:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC
*Feb 16 03:24:55.491:%OIR-6-INSCARD:Card inserted in slot 12, interfaces administratively
shut down
*Feb 16 03:24:58.455:%DIAL13-3-MSG:
02:32:09:%DSC_REDUNDANCY-3-EVENT:Redundancy event:LINK_FAIL from other DSC
*Feb 16 03:25:04.939:%DIAL13-0-MSG:
failover mode enabled, failover group = 32
Hub is in 'active' state.
Clock is in 'backup' state.
RouterB# show redundancy history
DSC Redundancy Status Change History:
010216 03:09 Slot -1 DSC:Failover configured -> BACKUP role.
010216 03:24 Slot 13 DSC:Failover -> ACTIVE role.
010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail
010216 03:24 Slot 13 DSC:Hub, becoming active - D12 linkfail
*Feb 16 03:26:14.079:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 1 Succeeded
*Feb 16 03:26:14.255:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 3 Succeeded
*Feb 16 03:26:14.979:%DSIPPF-5-DS_HELLO:DSIP Hello from shelf 47 slot 10 Succeeded
Example: Privileged EXEC Mode
The following is sample output generated by this command in privileged EXEC mode on router platforms that support no keywords for the privileged EXEC mode form of the command:
MWR1900 is the Active Router
Previous States with most recent at bottom
INITL_INITL Dec 31 19:00:00.000
LISTN_INITL Feb 28 19:00:15.568
LISTN_LISTN Feb 28 19:00:15.568
SPEAK_LISTN Feb 28 19:00:18.568
SPEAK_SPEAK Feb 28 19:00:18.568
STDBY_SPEAK Mar 19 08:54:26.191
ACTIV_SPEAK Mar 19 08:54:26.191
ACTIV_STDBY Mar 19 08:54:26.191
ACTIV_ACTIV Mar 19 08:54:26.191
INITL_ACTIV Mar 19 08:56:22.700
INITL_INITL Mar 19 08:56:22.700
INITL_LISTN Mar 19 08:56:28.544
LISTN_LISTN Mar 19 08:56:28.652
LISTN_SPEAK Mar 19 08:56:31.544
SPEAK_SPEAK Mar 19 08:56:31.652
SPEAK_STDBY Mar 19 08:56:34.544
SPEAK_ACTIV Mar 19 08:56:34.544
STDBY_ACTIV Mar 19 08:56:34.652
ACTIV_ACTIV Mar 19 08:56:34.652
INITL_ACTIV Mar 19 10:20:41.455
INITL_INITL Mar 19 10:20:41.455
INITL_LISTN Mar 19 10:20:49.243
LISTN_LISTN Mar 19 10:20:49.299
LISTN_SPEAK Mar 19 10:20:52.244
SPEAK_SPEAK Mar 19 10:20:52.300
SPEAK_STDBY Mar 19 10:20:55.244
STDBY_STDBY Mar 19 10:20:55.300
ACTIV_STDBY Mar 19 10:21:01.692
ACTIV_ACTIV Mar 19 10:21:01.692
Related Commands
Command
|
Description
|
debug redundancy
|
Displays information used for troubleshooting dual (redundant) router shelves (Cisco AS5800) or RSCs (Cisco AS5850).
|
hw-module
|
Enables the router shelf to stop a DSC or to restart a stopped DSC.
|
mode
|
Sets the redundancy mode.
|
mode y-cable
|
Invokes y-cable mode.
|
redundancy
|
Enters redundancy configuration mode.
|
redundancy force-switchover
|
Forces a switchover from the active to the standby supervisor engine.
|
show chassis
|
Displays, for a router with two RSCs, information about the mode (handover-split or classic-split), RSC configuration, and slot ownership.
|
show standby
|
Displays the standby configuration.
|
standalone
|
Specifies whether the MWR 1941-DC router is used in a redundant or standalone configuration.
|
standby
|
Sets HSRP attributes.
|
show redundancy (HSA redundancy)
To display the current redundancy mode, use the show redundancy command in user EXEC or privileged EXEC mode.
show redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced.
|
12.0(16)ST
|
This command was modified to display information about Route Processor Redundancy (RPR).
|
12.0(19)ST1
|
This command was modified to display information about RPR Plus (RPR+).
|
12.3(7)T
|
The command modifications to support RPR and RPR+ were integrated into Cisco IOS Release 12.3(7)T.
|
Usage Guidelines
Use this command to display the redundancy mode of a Cisco 7500 series router. The default redundancy mode is High System Availability (HSA). Use the redundancy configuration command to enter redundancy configuration mode. Use the mode rpr command in redundancy configuration mode to configure RPR as the high availability mode. HSA is the default high availability mode.
Examples
The following is sample output from the show redundancy command for a router with RPR configured:
hw-module slot 2 image slot0:rsp-pv-mz
hw-module slot 3 image slot0:rsp-pv-mz
Related Commands
Command
|
Description
|
hw-module sec-cpu reset
|
Resets and reloads the standby RSP with the specified Cisco IOS image and executes the image.
|
hw-module slot image
|
Specifies a high availability Cisco IOS image to run on a standby RSP.
|
mode (HSA redundancy)
|
Configures the redundancy mode.
|
redundancy
|
Enters redundancy configuration mode.
|
show redundancy interlink
To display interlink utilization, use the show redundancy interlink command in user EXEC or privileged EXEC mode.
show redundancy interlink [rx | tx [pps | bps]] [histogram]
Syntax Description
rx
|
(Optional) Receive interlink utilization histograms.
|
tx
|
(Optional) Transmit interlink utilization histograms.
|
pps
|
(Optional) Packets per second (pps) histograms.
|
bps
|
(Optional) Bytes per second (bps) histograms.
|
histogram
|
(Optional) Usage information.
|
Command Default
Interlink utilization information is not displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced on the Cisco AS5850.
|
12.2(31)SB
|
This command was introduced on the Cisco 10000 series Internet routers. Support for the Cisco AS5850 is not included in this release.
|
Usage Guidelines
Use the show redundancy interlink command to display the current or historical status on interlink utilization.
Examples
The following histogram displays receive BPS interlink information for the past minute, the past hour, and the past three days:
Router# show redundancy interlink rx bps histogram
1111111111111111111111111111111111111111111112222222222111
0....5....1....1....2....2....3....3....4....4....5....5....
Interlink Rx BPS (last 60 seconds)
# = Bits Per Second (x1000)
2111112111112121111121111111211111111111111111111111111111
0....5....1....1....2....2....3....3....4....4....5....5....
Interlink Rx BPS (last 60 minutes)
* = maximum BPS (x1000) # = average BPS (x1000)
1111222221111111112111111111111111211211111111111111121112111111111111
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
Interlink Rx BPS (last 72 hours)
* = maximum BPS (x1000) # = average BPS (x1000)
show rpc
To display remote procedure call (RPC) information, use the show rpc command in user EXEC or privileged EXEC mode.
show rpc {applications | counters | status}
Syntax Description
applications
|
Displays information about the RPC application.
|
counters
|
Displays the RPC counters.
|
status
|
Displays the RPC status.
|
Defaults
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.
|
Examples
This example shows how to display RPC applications:
Router# show rpc applications
ID Dest Callback Application
1 0011 <remote> rpc-master
2 0011 <remote> cygnus-oir
3 0021 60201708 rpc-slave-33
4 0021 6022A514 idprom-MP
6 0011 <remote> Nipcon-SP
7 0011 <remote> sw_vlan_sp
8 0011 <remote> stp_switch_api
10 0011 <remote> span_switch_rpc
11 0011 <remote> pf_rp_rpc
13 0011 <remote> mapping_sp
14 0011 <remote> logger-sp
17 0011 <remote> c6k_power_sp
18 0011 <remote> c6k_sp_environmental
19 0011 <remote> pagp_switch_rpc
21 0021 602675B0 Nipcon-RP
23 0021 601F2538 sw_vlan_rp
24 0021 601F77D0 span_switch_sp_rpc
25 0021 601F7950 idbman_fec
26 0021 601F7F30 logger-rp
27 0021 601F80D8 pagp_switch_l3_split
28 0021 601F81C0 pagp_switch_sp2mp
29 0021 6026F190 c6k_rp_environmental
This example shows how to display information about the RPC counters:
Router# show rpc counters
ID Dest Rcv-req Xmt-req Q size Application
2 0011 0 6221 0 cygnus-oir
7 0011 0 2024 0 sw_vlan_sp
8 0011 0 3 0 stp_switch_api
17 0011 0 2 0 c6k_power_sp
18 0011 0 66 0 c6k_sp_environmental
19 0011 0 109 0 pagp_switch_rpc
24 0021 14 0 0 span_switch_sp_rpc
25 0021 22 0 0 idbman_fec
27 0021 3 0 0 pagp_switch_l3_split
28 0021 3 0 0 pagp_switch_sp2mp
show scp
To display Switch-Module Configuration Protocol (SCP) information, use the show scp in privileged EXEC mode on the Switch Processor.
show scp {accounting | counters | linecards [details] | mcast {group group-id | inst} | process id
| status}
Syntax Description
accounting
|
Displays information about the SCP accounting.
|
counters
|
Displays information about the SCP counter.
|
linecards
|
Displays information about the Optical Services Module (OSM) wide area network (WAN) modules in the chassis.
|
details
|
(Optional) Displays detailed information about the OSM WAN module.
|
mcast
|
Displays information about the SCP multicast.
|
group group-id
|
(Optional) Displays information for a specific group and group ID; valid values are from 1 to 127.
|
inst
|
(Optional) Displays information for an instance.
|
process id
|
Displays all the processes that have registered an SAP with SCP.
|
status
|
Displays information about the local SCP server status.
|
Command Modes
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(18)SXE
|
The output of the show scp process command was changed to display all the processes that have registered an SAP with SCP on the Supervisor Engine 720 only.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
15.0(1)S
|
The output of the show scp status command was changed to additionally display the Flow Control State (FC-State) and the Flow Control Count (FC-Count)
|
Examples
The following example displays the SCP flow control status:
Rx 185, Tx 181, scp_my_addr 0x14
Id Sap Channel name current/peak/retry/dropped/totaltime(queue/process/ack)
FC-state FC-count
-------------------------------------------------------------- --------- ---- -------
0 18 SCP Unsolicited:18 801/ 0/ 0/ 0/ 0 0/ 0/ 0 off 0
1 80 SCP Unsolicited:80 0/ 0/ 0/ 0/ 0 0/ 0/ 0 off 0
2 23 SCP async: LCP#5 0/ 0/ 0/ 0/ 0 0/ 0/ 0 off 0
3 0 SCP Unsolicited:0 0/ 1/ 0/ 0/ 5 0/ 0/ 0 off 0
--------------------------------------------------------------------------------------------------------------------------
FC-state indicates the flow control state and FC-count indicates the number of times flow control has been turned on.
The following example shows how to display all the processes that have registered an SAP with SCP:
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 48-port 10/100 mb RJ45 WS-X6148-RJ-45 SAL091800RY
2 0 2 port adapter Enhanced FlexWAN WS-X6582-2PA JAE0940MH7Z
3 8 8 port 1000mb GBIC Enhanced QoS WS-X6408A-GBIC SAL09391KZH
5 2 Supervisor Engine 720 (Active) WS-SUP720-3BXL SAL09337UE6
6 2 Supervisor Engine 720 (Hot) WS-SUP720-3BXL SAL09148P59
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0013.c3f8.d2c4 to 0013.c3f8.d2f3 5.0 8.3(1) 8.6(0.366)TA Ok
2 0015.2bc3.5b40 to 0015.2bc3.5b7f 2.1 12.2(nightly 12.2(nightly Ok
3 0015.6324.ed48 to 0015.6324.ed4f 3.1 5.4(2) 8.6(0.366)TA Ok
5 0014.a97d.b0ac to 0014.a97d.b0af 4.3 8.4(2) 12.2(nightly Ok
6 0013.7f0d.0660 to 0013.7f0d.0663 4.3 8.4(2) 12.2(nightly Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3BXL SAL09337NVE 1.6 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL09327AU6 2.3 Ok
6 Policy Feature Card 3 WS-F6K-PFC3BXL SAL1033Y0YK 1.8 Ok
6 MSFC3 Daughterboard WS-SUP720 SAL09158XB3 2.3 Ok
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
Switch-sp# show scp process
0 180 CWAN-RP SCP Input Process
22 180 CWAN-RP SCP Input Process
Total number of SAP registered = 5