Cisco 10000 Series Router CLI Command Changes in Cisco IOS Release 12.2(33)SB
Available Languages
Table Of Contents
Cisco 10000 Series Router CLI Command Changes in Cisco IOS Release 12.2(33)SB
Restrictions for CLI Command Changes
Information About CLI Command Changes
debug ipv6 icmp Command Output for IPv6 ICMP
no Commands Removed from the Default Configuration
show controllers and Loopback CLI Commands
show controller and Line Code Information
show policy-map Command and Hierarchical Policies
show policy-map Command and Police Actions
show pxf cpu ipv6 table Command
show pxf cpu queue interface summary Command
show vpdn tunnel summary Command
snmp-server enable traps alarms Command
vpdn enable and vpdn-group Commands
show controllers (line card image)
show interfaces virtual-access
Feature Information for CLI Command Changes
Cisco 10000 Series Router CLI Command Changes in Cisco IOS Release 12.2(33)SB
First Published: April, 2008This feature guide describes changes in command line interface (CLI) command behavior in Cisco IOS Release 12.2(33)SB.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for CLI Command Changes" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Restrictions for CLI Command Changes
•
•
Restrictions for CLI Command Changes
Cisco IOS Release 12.2(33)SB or a later release must be running on the router.
Information About CLI Command Changes
Cisco IOS Release 12.2(33)SB introduces changes to the following CLI commands:
•
•
•
•
•
•
•
•
•
•
card Command
Cisco IOS Release 12.2(33)SB introduces the 4jacket-1 keyword and the spa-type option for the card command. The 4jacket-1 keyword enables you to preprovision a line card slot to accept a Cisco 10000 SIP-600. The spa-type option preprovisions a line card slot to accept a shared port adaptor (SPA) interface.
Use the following syntax to preprovision a line card slot to accept a Cisco 10000 SIP-600:
card slot subslot 4jacket-1Use the following syntax to preprovision a line card slot to accept a SPA interface:
card slot subslot spa-type
The following example preprovisions line card slot 3 to accept a Cisco 10000 SIP-600 and a 2-port Gigabit Ethernet SPA in subslot 0:
Router(config)# card 3 4jacket-1Router(config)# card 3/0 spa-2x1ge-v2CoPP-Related show Commands
The router supports the following CoPP-related show commands:
•
•
•
•
•
debug ipv6 icmp Command Output for IPv6 ICMP
In Cisco IOS Release 12.2(33)SB, output from the debug ipv6 icmp command displays information similar to the following:
ICMPv6: Received echo reply from 2010:1:1:1:1:1:1:2In Cisco IOS Release 12.2(31)SB, the debug ipv6 icmp command output displays information similar to the following:
ICMPv6: Received ICMPv6 packet from 2010:1:1:1:1:1:1:2, type 129frame-relay broadcast-queue
In Cisco IOS Release 12.2(33)SB, the default queue size for the frame-relay broadcast-queue is 256 packets.
In Cisco IOS Release 12.2(31)SB, the default queue size is 64 packets.
frame-relay switching Command
In Cisco IOS Release 12.2(33)SB, you do not need to configure the frame-relay switching command when configuring a Frame Relay interface as the DCE.
In Cisco IOS Release 12.2(31)SB, you must configure the frame-relay switching command when you configure a Frame Relay interface as the DCE.
hw-module slot
In Cisco IOS Release 12.2(33)SB, when you enter the hw-module slot slot-number reset command, the software asks you to confirm the command. In Cisco IOS Release 12.2(31)SB, the software does not ask you to confirm the command.
Cisco IOS Release 12.2(33)SB introduces the hw-module slot slot-number reload command on the router. The reload keyword enables a remote reload of an individual feature board without having to use manual online insertion and removal (OIR).
no Commands Removed from the Default Configuration
In Cisco IOS Release 12.2(33)SB, the router removes the following no commands from the default configuration:
•
•
•
no fair-queue Command
In Cisco IOS Release 12.2(33)SB, the router removes the no fair-queue command from serial interfaces.
plim qos input map Command
Cisco IOS Release 12.2(33)SB introduces the plim qos input map command on the router. This command configures a priority queue on Gigabit Ethernet SPAs, separating high-priority traffic from low-priority traffic and placing the traffic in the appropriate interface queue. The command separates priority and non-priority traffic at the SPA interface processor (SIP) to prevent the dropping of high priority traffic in an oversubscription case. Each shared port adaptor (SPA) supports one priority queue.
The command has the following syntax:
plim qos input map {cos {enable | cos-value queue low-latency} | ip {dscp-based | dscp dscp-value queue low-latency} | ip {precedence-based | precedence precedence-value queue low-latency} | ipv6 tc tc-value queue low-latency | mpls exp exp-value queue low-latency
The router supports the following classification types for the prioritization of ingress traffic on the Gigabit Ethernet SPAs:
•
•
•
•
•
police Command
Cisco IOS Release 12.2(33)SB supports a police submode and dual police actions.
The output from the show policy-map interface command displays the police actions in the police submode, displaying each action on a new line. Regardless of whether you configure a single action or dual actions for the colors, the police actions display on a new line as shown in the following sample output:
Router# show policy-map interface ATM1/0/0.131ATM1/0/0.131: VC 1/131 -Service-policy input: testClass-map: prec1 (match-any)0 packets, 00 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 10 packets, 0 bytes5 minute rate 0 bpsPolice:7504000 bps, 100 limit, 10 extended limitconformed 0 packets, 0 bytes; action:set-clp-transmitset-mpls-exp-imposition-transmit 1exceeded 0 packets, 0 bytes; action:set-clp-transmitviolated 0 packets, 0 bytes; action:set-clp-transmitClass-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes5 minute rate 0 bpsThe router supports only the following combinations of dual actions:
•
•
•
When configuring the police command, if you specify actions and then later modify the configured rate parameters, but not the actions, the specified actions change to the default values if only one action is specified for each conform, exceed, and violate color. However, if at least one color has dual actions configured, then modifying only the rate parameters does not change the actions to the default value, but instead preserves the previous actions.
For example, the following sample configuration configures the police rate parameters and only one action for each conform, exceed, and violate color:
Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 500000 100 0 conform-action set-clp-transmit exceed-action set-clp-transmit violate-action set-clp-transmitThe output from the show policy-map command displays the following police configuration:
Router# show policy-map testPolicy Map testClass prec1police 504000 100 0conform-action set-clp-transmitexceed-action set-clp-transmitviolate-action set-clp-transmitThe following configuration modifies the police rate parameters, but not the actions:
Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 750000 100 0
The following output from the show policy-map command indicates that the color values were changed to the default values. This is because only one action was configured for each color.
Router# show policy-map testPolicy Map testClass prec1police 752000 100 100conform-action transmitexceed-action dropviolate-action dropThe following output from the show policy-map command displays a police configuration in which the conform color has dual actions configured:
Router# show policy-map testPolicy Map testClass prec1police 504000 100 0conform-action set-clp-transmitconform-action set-mpls-exp-imposition-transmit 1exceed-action set-clp-transmitviolate-action set-clp-transmitThe following configuration modifies the police rate parameters, but not the actions:
Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 7500000 100 10The following output from the show policy-map command indicates that the color values did not change when the rate parameters were modified. Instead, the original values were preserved.
Router# show policy-map testPolicy Map testClass prec1police 7500000 100 10conform-action set-clp-transmitconform-action set-mpls-exp-imposition-transmit 1exceed-action set-clp-transmitviolate-action set-clp-transmitIn Cisco IOS Release 12.2(31)SB and later releases, if you modify the police rate parameters, but not the action parameters, the police actions default to conform-action transmit, exceed-action drop, and violate-action drop.
For example, the following sample configuration shows the police command configured in the policy map named test. The police actions are set to set-clp-transmit for conforming, exceeding, and violating traffic. The police rate parameters are then changed to 500000, 250, and 200, but no actions are modified. When you display the test policy map again, you can see that the police actions default to transmit, drop, and drop.
Router# show policy-map testPolicy Map testClass prec1police 248000 100 10 conform-action set-clp-transmit exceed-action set-clp-transmit violate-action set-clp-transmitRouter#Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 500000 250 200Router(config-pmap-c)# endRouter# show policy-map testPolicy Map testClass prec1police 504000 250 200 conform-action transmit exceed-action drop violate-action dropservice-policy Command
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the abbreviated form (ser) of the service-policy command. Instead, you must spell out the command name service- before the router accepts the command.
For example, when attaching a policy map the following error message displays when you attempt to use the abbreviated form of the service-policy command:
Router(config)# interface gigabit1/1/0Router(config-if)# ser out ?% Unrecognized commandRouter(config-if)# ser ?% Unrecognized commandWhen you enter the command as service-, the router accepts the command as shown in the following example:
Router(config-if)# service- ?input Assign policy-map to the input of an interfaceoutput Assign policy-map to the output of an interfacetype Configure CPL Service PolicyIn releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the service-policy command. For example, the router accepts the following commands:
Router(config)# interface gigabit1/1/0Router(config-if)# ser out testshow atm vp Command
In Cisco IOS Release 12.2(33)SB, the output from the show atm vp command nolonger displays "ATM" as the type of interface, as shown in the following sample output:
Router# show atm vpData CES PEAK CES Avg/Min Burst MCRInterface VPI SC VCs VCs Kbps Kbps Kbps Cells Kbps CDVT Status3/0/0 200 N/A 0 0 2000 0 NA NA NA 140.0 ACTIVEIn Cisco IOS Release 12.2(31)SB, the output from the show atm vp command displays the ATM interface type:
Router# show atm vpData CES PEAK CES Avg/Min Burst MCR CDVTInterface VPI SC VCs VCs Kbps Kbps Kbps Cells Kbps Usecs StatusATM3/0/0 200 0 0 2000 0 NA NA NA 140.0 ACTIVEshow controller Command
This section describes the following changes in the show controller command:
•
•
show controllers and Loopback CLI Commands
In releases prior to Cisco IOS Release 12.2(33)SB, when you configure the t1 loopback remote command on the local router, the command also displays in the running-config file of the far-end router. This is due to the route processor (RP) updating an incorrect parameter when it receives the loopback event message from the line card for loopback requests from the far end.
In Cisco IOS Release 12.2(33)SB, the RP updates the correct parameter and the show controllers command correctly displays the loopback CLI commands applied on the local end and displays the loopback events and status received from the line card in response to loopback requests from the far end.
This change in behavior affects the following line cards and is documented in the CSCsm84447 caveat:
•
•
•
•
show controller and Line Code Information
In Cisco IOS Release 12.2(33)SB, the output from the show controller command includes line code information for the 6-port channelized T3 line card and the 8-port E3/DS3 line card. However, because SONET line cards do not have a direct physical link at the T3 or E3 level, the output from the show controller t3 command does not include line code information.
In Cisco IOS Release 12.2(31)SB, the output from the show controller command displays line code information. The output of the show controller t3 command for SONET-based T3 also includes line code information.
The following examples from the show controller t3 command show the information that displays when the router is running Cisco IOS Release 12.2(33)SB and Cisco IOS Release 12.2(31)SB:
Cisco IOS Release 12.2(33)SB —No Line Code Information Displays
Router# show controller t3 5/0/0.1T3 5/0/0.1 is up. Hardware is C10K CHOC12 line cardApplique type is Channelized T3.Controller is in unchannelized mode.No alarms detected.MDL transmission is disabled.FEAC code received: No code is being received.Framing is C-BIT Parity (Configured), Clock Source is Internal.DSU mode is cisco, DSU bandwidth is 44210.Cisco IOS Release 12.2(31)SB —Line Code Information Displays
Router# show controller t3 5/0/0.1T3 5/0/0.1 is up. Hardware is C10K CHOC12 line cardApplique type is Channelized T3.Controller is in channelized mode.No alarms detected.MDL transmission is disabled.FEAC code received: No code is being receivedFraming is C-BIT Parity (Configured)Line Code is B3ZS, Clock Source is Internal.show diag Command
The show diag command has a new crashdump option to display any crashdump files collected on the SPA Interface Processor (SIP). The SIP stores the crashdump files by a reference number from 1 to 60.
To view a crashdump file, perform the following steps:
Step 1
a.
b.
Number of crashdumps : output numberStep 2
show diag slot/subslot crashdump number
Note
show interfaces Command
In Cisco IOS Release 12.2(33)SB, when a multilink PPP (MLPPP) interface is down/down, its default bandwidth rate is the sum of the serial interface bandwidths associated with the MLPPP interface.
In Cisco IOS Release 12.2(31)SB, the default bandwidth rate is 64 Kbps.
show policy-map Command and Hierarchical Policies
In Cisco IOS Release 12.2(33)SB, the output of the show policy-map command is slightly different from previous releases when the policy is an hierarchical policy.
For example, in Cisco IOS Release 12.2(33)SB output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Bronzepolicy-map bronzeclass class-defaultshape average 34386000service-policy ChildIn Cisco IOS Release 12.2(31)SB, output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Goldpolicy-map GoldClass class-defaultAverage Rate Traffic Shapingcir 34386000 (bps)service-policy Child2show policy-map Command and Police Actions
In Cisco IOS Release 12.2(33)SB, the output from the show policy-map command displays police actions on separate lines as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P1prioritypolice percent 50 25 ms 0 msconform-action transmitexceed-action transmitviolate-action dropIn Cisco IOS Release 12.2(31)SB, the output from the show policy-map command displays police actions on one line as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P1prioritypolice percent 50 25 ms 0 ms conform-action transmit exceed-action transmit violate- action dropshow pxf cpu ipv6 table Command
In Cisco IOS Release 12.2(33)SB, the show pxf cpu ipv6 table command displays the global table, but does not display the leafs that correspond to the IPv6 prefixes ::1/128 (Loopback) and ::/128 (All Zero). The microcode checks for these prefixes.
The show pxf cpu ipv6 table command replaces the show pxf cpu ipv6 command in Cisco IOS Release 12.2(31)SB.
show pxf cpu queue interface summary Command
In Cisco IOS Release 12.2(33)SB and later releases, the output from the show pxf cpu queue interface summary command displays only the physical interface and the number of logical links. The output does not display the number of priority queues, class queues, and so on. This modification applies to the PRE3 and PRE4.
show vpdn tunnel summary Command
In Cisco IOS Release 12.2(33)SB, the show vpdn tunnel summary command no longer displays the active PPPoE sessions. Instead, use the show pppoe sessions command to display the active sessions.
In Cisco IOS Release 12.2(31)SB, the show vpdn tunnel summary command does display the active PPPoE sessions.
snmp-server enable traps alarms Command
In releases prior to Cisco IOS Release 12.2(33)SB, the snmp-server enable traps alarms command displayed information about major, minor, critical, and informational alarms.
In Cisco IOS Release 12.2(33)SB, by default, the snmp-server enable traps alarms command displays information for informational alarms only. You can enable the following commands separately:
•
•
•
Virtual-Access show Commands
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer allows you to specify a virtual-access interface (VAI) as viX.Y in the show pxf cpu queue and show interfaces commands. Instead, you must spell out the VAI as virtual-access.
For example, when you enter the following commands, the router accepts the commands:
Router# show pxf cpu queue virtual-access2.1Router# show interface virtual-access 2.1In releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the VAI. For example, the router accepts the following commands:
Router# show pxf cpu queue vi2.1Router# show interface vi2.1virtual-template snmp Command
The virtual-template snmp command has a new default configuration in Cisco IOS Release 12.2(33)SB. The new default configuration was changed from enabled by default to disabled by default: no virtual-template snmp. This setting enhances scaling and prevents large numbers of entries in the MIB ifTable, thereby avoiding CPU Hog messages as SNMP uses the interfaces MIB and other related MIBs.
If you configure the no virtual-template snmp command, the router no longer accepts the snmp trap link-status command under a virtual-template interface. Instead, the router displays a configuration error message such as the following:
Router(config)# interface virtual-template 1Router(config-if)# snmp trap link-status%Unable set link-status enable/disable for interfaceIf your configuration already has the snmp trap link-status command configured under a virtual-template interface and you upgrade to Cisco IOS Release 12.2(33)SB, the configuration error occurs when the router reloads even though the virtual template interface is already registered in the interfaces MIB.
vpdn enable and vpdn-group Commands
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the vpdn-group command if you issue the command before you issue the vpdn enable command. Instead, the following warning message displays:
% VPDN configuration is not allowed until VPDN is enabled through `vpdn enable'.In releases prior to Cisco IOS Release 12.2(33)SB, if you issue the vpdn-group command before the vpdn enable command, the router accepts the command and displays the following warning message:
% VPDN is not enabledAdditional References
The following sections provide references related to the CLI command changes.
Related Documents
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
The following commands are modified in the feature documented in this module. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup.
•
•
•
•
•
card
To preprovision a router slot for a particular interface card so that you can configure the interface without that card being physically present in the slot, use the card command in global configuration mode. To remove the preprovisioning for a card so that the physical slot reports being empty, use the no form of this command.
card {slot/subslot | slot/subslot/bay} card-type
no card {slot/subslot | slot/subslot/bay}
Cisco 10000 Series Router
card slot/subslot {lchoc12-1 | lgigethernet-l | 1gigethernet-hh-1 | loc12atm-1 | loc12pos-1 | 1oc48dpt-pos-1 | 24che1t1-1 | 4chstm-1 | 4cht3-hh-1| 4oc3atm-1 | 4oc3atm_lr-1 | 4jacket-1 | 6cht3-1 | 6oc3pos-1 | 8e3ds3-1 | 8e3ds3atm-1 | 8fastethernet-1 [ mode {e1 | t1}] | spa-type}
no card slot/subslot
Cisco uBR10012 Universal Broadband Router - Cisco IOS Release 12.2(33)SCB
card {slot | slot/bay} card-type
no card {slot | slot/bay}
Syntax Description
slot/subslot
Identifies the chassis slot and subslot for the card. The following are the valid values:
•
•
slot/subslot/bay
(Cisco uBR100012 router) Identifies the chassis slot and subslot for the Cisco Wideband SIP, and the bay number in the SIP where the Cisco Wideband SPA is located. The following are the valid values:
•
•
•
card-type
Specifies the type of card for which to preprovision the slot. See Table 0-1 for a list of the supported cards, which varies by platform.
lchoc12-1
Preprovisions a line card slot for a 1-Port Channelized OC-12/STM-4 line card.
lgigethernet-l
Preprovisions a line card slot for a 1-Port Gigabit Ethernet line card.
1gigethernet-hh-1
Preprovisions a line card slot for a 1-Port Gigabit Ethernet Half-Height line card.
loc12atm-1
Preprovisions a line card slot for a 1-Port OC-12 ATM line card.
loc12pos-1
Preprovisions a line card slot for a 1-Port OC-12 Packet over SONET line card.
1oc48dpt-pos-1
Preprovisions a line card slot for a 1-Port OC-48/STM-16 Packet over SONET line card.
24che1t1-1
Preprovisions a line card slot for a 24-Port Channelized E1/T1 line card.
4chstm-1
Preprovisions a line card slot for a 4-Port Channelized OC-3/STM-1 line card.
4cht3-hh-1
Preprovisions a line card slot for a 4-port Channelized Half-Height line card.
4oc3atm-1
Preprovisions a line card slot for a 4-Port OC-3/STM-1 ATM line card with intermediate-reach optics.
4oc3atm_lr-1
Preprovisions a line card slot for a 4-Port OC-3/STM-1 ATM line card with long-reach optics.
4jacket-1
Preprovisions a line card slot in the Cisco 10000 series router to accept a Cisco 10000 SIP-600.
6cht3-1
Preprovisions a line card slot for a 6-Port Channelized T3 line card.
6oc3pos-1
Preprovisions a line card slot for a 6-Port OC-3/STM-1 Packet over SONET line card.
8e3ds3-1
Preprovisions a line card slot for an 8-Port Unchannelized E3/T3 line card.
8e3ds3atm-1
Preprovisions a line card slot for an 8-Port E3/DS3 ATM line card.
8fastethernet-1
Preprovisions a line card slot for an 8-Port Fast Ethernet Half-Height line card.
mode {e1 | t1}
Indicates the mode of operation of the 24-Port Channelized E1/T1 line card.
spa-type
Specifies the SPA type to preprovision a SPA interface.
Command Default
An empty card slot is not preprovisioned and cannot be configured or displayed.
The default mode of operation for the 24-Port Channelized E1/T1 line card is E1.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is supported on the Cisco uBR10012 Universal Broadband Router and the Cisco 10000 series routers. For platform-specific information about using this command, see the other platform-specific sections of this topic.
Use this command to preprovision a slot in the router to accept a particular line card, so that you can configure the interface without the card being physically present in the chassis. This command allows system administrators to plan for future configurations, without having to wait for the physical hardware to first arrive. When the line card does arrive, the installer can bring the card online by inserting the card into the chassis and connecting the necessary cables, without having to do any further configuration using the command-line interface.
The type of card must be appropriate for the slot being specified. The list of supported card types depends on the Cisco IOS software release in use and your platform. For the latest information about supported hardware for your platform, see the release notes that correspond to your Cisco IOS software release and platform.
Table 0-1 lists the types of cards that are supported as card-types for the card command:
Cisco uBR10012 Universal Broadband Router Usage Guidelines
On the Cisco uBR10012 router, you can use the card command to preprovision a router slot for a line card or to preprovision one or more slots for a SPA interface processor (SIP), such as the Cisco Wideband SIP. You can also use the card command to preprovision a SIP bay for a shared port adapter (SPA), such as the Cisco Wideband SPA.
The Cisco uBR10012 Universal Broadband Router has the following card slot requirements:
Note
•
•
•
•
Tip
When a line card is inserted in the Cisco uBR10012 chassis, the router performs the following actions, depending on whether the card slot is preprovisioned for the card:
•
•
•
Tip
The no version of the command removes the preprovisioning information from the given card slot. This also removes all configuration information for that card slot, as well as any information in the SNMP MIB database about the card and its card slot.
Cisco 10000 Series Router Usage Guidelines
You must specify a line card slot and subslot, and the line card for which you want to preprovision the line card slot.
If you insert a line card into a line card slot that has been preprovisioned for a different line card, the line card will fail.
You can specify a mode of operation for the 24-Port Channelized E1/T1 line card. If you do not, the line card operates in the E1 mode.
In Cisco IOS releases earlier than 12.0(28)S, 12.2(16)BX, and 12.3(7)XI1, you used only the card command to change the provisioning of a line card slot. It was not necessary to remove the old line card before using the card command to change the line card provisioning.
In Cisco IOS releases after 12.0(28)S, 12.2(16)BX, and 12.3(7)XI1, you must deactivate the installed line card using the hw-module and no card commands before using the card command to provision the line card slot for a different line card. This is a general best practice when using the card command.
Examples
Cisco uBR10012 Universal Broadband Router Examples
The following example shows a list of supported card types for Cisco IOS Release 12.2(8)BC1, and then shows that slot 8/0 is being preprovisioned for a Cisco uBR-LCP2-MC28C cable interface line card. The cable interface for slot 8/0 can then be configured.
Router# config tRouter(config)# card 5/0 ?1cable-mc16c create a uBR10000 line card with MC16C1cable-mc16e create a uBR10000 line card with MC16E1gigethernet-1 create a GE_1_PORT cardtype1oc12pos-1 create a OC12POS_1_PORT cardtype2cable-mc28bnc create a uBR10000 line card with MC28C, BNC connector2cable-mc28c create a uBR10000 line card with MC28C2oc12srp-sm-lr create a uBR10000 oc12 SRP card with SM LRRouter(config)# card 8/0 2cable-mc28cRouter(config)# int c8/0Router(config-if)#The following example shows how to preprovision a Cisco Wideband SIP in Cisco IOS Release 12.2(33)SCB:
Router# configure terminalRouter(config)# card 1 2jacket-1The following example shows how to preprovision a Cisco Wideband SPA on a Cisco Wideband SIP in Cisco IOS Release 12.2(33)SCB:
Router# configure terminalRouter(config)# card 1/0 24rfchannel-spa-1The following example shows how to preprovision a Cisco SIP-600 in Cisco IOS Release 12.2(33) SCB:
Router# configure terminalRouter(config)# card 3 4jacket-1The following example shows how to preprovision a Cisco Wideband SPA on a Cisco SIP-600 in Cisco IOS Release 12.2(33) SCB:
Router# configure terminalRouter(config)# card 3/0 24rfchannel-spa-1Cisco 10000 Series Router Examples
The following example preprovisions line card slot 2 to accept a 24-Port Channelized E1/T1 line card operating in E1 mode:
Router(config)# card 2/0 24che1t1-1 mode e1The following example shows how to change the provisioning for line card slot 5 from the 1-Port Gigabit Ethernet Half-Height line card to the 4-Port OC-3/STM-1 ATM line card.
Router(config)# hw-module subslot 5/0 shutAug 22 21:52:19.619 UTC: %IPCOIR-3-TIMEOUT: Timeout waiting for a response from slot 5/0.Aug 22 21:52:19.619 UTC: %IPCOIR-2-CARD_UP_DOWN: Card in slot 5/0 is down. Notifying 1gigethernet-hh-1 driver.Aug 22 21:52:21.627 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet5/0/0, changed state to downAug 22 21:52:22.627 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet5/0/0, changed state to downRouter(config)# no card 5/0 1gigethernet-hh-1Aug 22 21:53:20.008 UTC: %C10K-3-DEACTIVATED: card in slot [5/0] disabled.Router(config)# card 5/0 4oc3atm-1[ Remove the 1-Port Gigabit Ethernet Half-Height line card andinsert the 4-Port OC-3/STM-1 ATM line card ]Related Commands
show interface
Displays the current configuration and status for a specified interface type.
debug ipv6 icmp
To display debugging messages for IPv6 Internet Control Message Protocol (ICMP) transactions (excluding IPv6 ICMP neighbor discovery transactions), use the debug ipv6 icmp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ipv6 icmp
no debug ipv6 icmp
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging for IPv6 ICMP is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ipv6 icmp command is similar to the debug ip icmp command, except that it is IPv6-specific.
Note
This command helps you determine whether the router is sending or receiving IPv6 ICMP messages. Use it, for example, when you are troubleshooting an end-to-end connection problem.
Note
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, output from the debug ipv6 icmp command displays information similar to the following:
ICMPv6: Received echo reply from 2010:1:1:1:1:1:1:2In Cisco IOS Release 12.2(31)SB, the debug ipv6 icmp command output displays information similar to the following:
ICMPv6: Received ICMPv6 packet from 2010:1:1:1:1:1:1:2, type 129Examples
The following is sample output from the debug ipv6 icmp command:
Router# debug ipv6 icmp13:28:40:ICMPv6:Received ICMPv6 packet from 2000:0:0:3::2, type 13613:28:45:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 13513:28:50:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 13613:28:55:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 135Table 2 describes significant fields shown in the first line of the display.
Following are examples of the IPv6 ICMP messages types that can be displayed by the debug ipv6 icmp command:
•
1w4d:ICMPv6:Sending echo request to 2052::501w4d:ICMPv6:Received echo reply from 2052::50•
1w4d:Received ICMP too big from 2052::52 about 2052::50, MTU=1300•
1w4d:Received ICMP parameter problem from 2052::52•
1w4d:Received ICMP time exceeded from 2052::52•
1w4d:Received ICMP unreachable code 1 from 2052::521w4d:Sending ICMP unreachable code 1 to 2060::20 about 2062::20Table 3 lists the codes for ICMP unreachable messages.
Related Commands
debug ipv6 nd
Displays debugging messages for IPv6 ICMP neighbor discovery transactions.
fair-queue (WFQ)
To enable weighted fair queueing (WFQ), use the fair-queue command in interface configuration or policy-map class configuration mode. To disable WFQ, use the no form of this command.
fair-queue [congestive-discard-threshold [dynamic-queues [reservable-queues]]]
no fair-queue
Syntax Description
Command Default
Fair queueing is enabled by default for physical interfaces whose bandwidth is less than or equal to 2.048 Mbps and that do not use the following:
•
•
•
•
•
•
•
Fair queueing is not an option for the protocols listed above. However, if you enable custom queueing or priority queueing for a qualifying link, it overrides fair queueing, effectively disabling it. Additionally, fair queueing is automatically disabled if you enable the autonomous or silicon switching engine mechanisms.
Note
The number of dynamic queues is derived from the interface or ATM permanent virtual circuit (PVC) bandwidth. See Table 4 in the fair-queue (class-default) command for the default number of dynamic queues that WFQ and class-based WFQ (CBWFQ) use when they are enabled on an interface. See Table 4 in the fair-queue (class-default) command for the default number of dynamic queues used when WFQ and CBWFQ are enabled on an ATM PVC.
Command Modes
Interface configuration (config-if)
Policy-map class configuration (config-pmap-c)Command History
Usage Guidelines
High-Level Overview
This command enables WFQ. With WFQ, packets are classified by flow. For example, packets with the same source IP address, destination IP address, source TCP or User Datagram Protocol (UDP) port, destination TCP or UDP port, and protocol belong to the same flow; see Table 4 for a full list of protocols and traffic stream discrimination fields.
When you enable WFQ on an interface, WFQ provides traffic priority management that automatically sorts among individual traffic streams without requiring that you first define access lists. Enabling WFQ requires use of this command only.
When you enable WFQ on an interface, new messages for high-bandwidth traffic streams are discarded after the configured or default congestive discard threshold has been met. However, low-bandwidth conversations, which include control message conversations, continue to enqueue data. As a result, the fair queue may occasionally contain more messages than its configured threshold number specifies.
WFQ uses a traffic data stream discrimination registry service to determine which traffic stream a message belongs to. For each forwarding protocol, Table 4 shows the message attributes that are used to classify traffic into data streams.
IP Precedence
IP Precedence, congestion in Frame Relay switching, and discard eligible (DE) flags affect the weights used for queueing.
IP Precedence, which is set by the host or by policy maps, is a number in the range from 0 to 7. Data streams of precedence number are weighted so that they are given an effective bit rate of number+1 times as fast as a data stream of precedence 0, which is normal.
FECN and BECN
In Frame Relay switching, message flags for forward explicit congestion notification (FECN), backward explicit congestion notification (BECN), and DE message flags cause the algorithm to select weights that effectively impose reduced queue priority. The reduced queue priority provides the application with "slow down" feedback and sorts traffic, giving the best service to applications within their committed information rate (CIR).
Fair Queueing, Custom Queueing, and Priority Queueing
Fair queueing is supported for all LAN and line (WAN) protocols except X.25, including LAPB and SDLC; see the notes in the section "Command Default." Because tunnels are software interfaces that are themselves routed over physical interfaces, fair queueing is not supported for tunnels. Fair queueing is on by default for interfaces with bandwidth less than or equal to 2 Mbps.
Note
RSVP
When you configure Resource Reservation Protocol (RSVP) on an interface that supports fair queueing or on an interface that is configured for fair queueing with the reservable queues set to 0 (the default), the reservable queue size is automatically configured using the following method: interface bandwidth divided by 32 kbps. You can override this default by specifying a reservable queue other than 0. For more information on RSVP, refer to the chapter "Configuring RSVP" in the Cisco IOS Quality of Service Solutions Configuration Guide.
Cisco 10000 Series Routers
In Cisco IOS Release 12.2(33)SB, the router removes the no fair-queue command from serial interfaces.
HQF
Beginning with Cisco IOS Release 12.4(20)T, if your image has HQF support, the fair-queue command is not enabled automatically under class default. You should enable the fair-queue command and any other supported queueing features before using an HQF-capable image.
Examples
The following example enables WFQ on serial interface 0, with a congestive threshold of 300. This threshold means that messages are discarded from the queueing system only when 300 or more messages have been queued and the message is in a data stream that has more than one message in the queue. The transmit queue limit is set to 2, based on the 384-kilobit (Kb) line set by the bandwidth command:
interface serial 0bandwidth 384fair-queue 300Unspecified parameters take the default values.
The following example requests a fair queue with a congestive discard threshold of 64 messages, 512 dynamic queues, and 18 RSVP queues:
interface serial 3/0ip unnumbered ethernet 0/0fair-queue 64 512 18You can apply the fair-queue command to a user-defined class as shown in the following example:
policy-map p1class c1bandwidth 1000fair-queueRelated Commands
frame-relay broadcast-queue
To create a special queue for a specified interface to hold broadcast traffic that has been replicated for transmission on multiple data-link connection identifiers (DLCIs), use the frame-relay broadcast-queue command in interface configuration mode.
frame-relay broadcast-queue size byte-rate packet-rate
Syntax Description
size
Number of packets to hold in the broadcast queue.
byte-rate
Maximum number of bytes to be sent per second.
packet-rate
Maximum number of packets to be sent per second.
Defaults
size: 64 packets
byte-rate: 256000 bytes per second
packet-rate: 36 packets per secondCommand Modes
Interface configuration
Command History
Usage Guidelines
For purposes of the Frame Relay broadcast queue, broadcast traffic is defined as packets that have been replicated for transmission on multiple DLCIs. However, the broadcast traffic does not include the original routing packet or service access point (SAP) packet, which passes through the normal queue. Because of timing sensitivity, bridged broadcasts and spanning-tree packets are also sent through the normal queue. The Frame Relay broadcast queue is managed independently of the normal interface queue. It has its own buffers and a configurable service rate.
A broadcast queue is given a maximum transmission rate (throughput) limit measured in bytes per second and packets per second. The queue is serviced to ensure that only this maximum is provided. The broadcast queue has priority when transmitting at a rate below the configured maximum, and hence has a guaranteed minimum bandwidth allocation. The two transmission rate limits are intended to avoid flooding the interface with broadcasts. The actual limit in any second is the first rate limit that is reached.
Given the transmission rate restriction, additional buffering is required to store broadcast packets. The broadcast queue is configurable to store large numbers of broadcast packets.
The queue size should be set to avoid loss of broadcast routing update packets. The exact size will depend on the protocol being used and the number of packets required for each update. To be safe, set the queue size so that one complete routing update from each protocol and for each DLCI can be stored. As a general rule, start with 20 packets per DLCI. Typically, the byte rate should be less than both of the following:
•
•
The packet rate is not critical if you set the byte rate conservatively. Set the packet rate at 250-byte packets.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the default queue size for the frame-relay broadcast-queue is 256 packets.
In Cisco IOS Release 12.2(31)SB, the default queue size is 64 packets.
Examples
The following example specifies a broadcast queue to hold 80 packets, to have a maximum byte transmission rate of 240000 bytes per second, and to have a maximum packet transmission rate of 160 packets per second:
frame-relay broadcast-queue 80 240000 160frame-relay switching
To enable permanent virtual switching (PVC) switching on a Frame Relay DCE device or a Network-to-Network Interface (NNI), use the frame-relay switching command in global configuration mode. To disable switching, use the no form of this command.
frame-relay switching
no frame-relay switching
Syntax Description
This command has no arguments or keywords.
Defaults
Switching is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You must add this command to the configuration file before configuring the routes.
Cisco 10000 Serie Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, you do not need to configure the frame-relay switching command when configuring a Frame Relay interface as the DCE.
In Cisco IOS Release 12.2(31)SB, you must configure the frame-relay switching command when you configure a Frame Relay interface as the DCE.
Examples
The following example shows the command that is entered in the configuration file before the Frame Relay configuration commands to enable switching:
frame-relay switchinghw-module slot
To enable the router shelf to restart a stopped Dial Shelf Controller (DSC) card, to stop a DSC card, or to cause a shutdown, reset, or reload of any specified dial shelf feature board, use the hw-module slot command in privileged EXEC mode.
hw-module slot shelf-id/slot-number {reload | reset | shutdown | start | stop}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The stop form of this command is issued from the router shelf console instead of by pressing the attention (ATTN) button on the target DSC. Confirmation of when the start or stop took place is displayed. Warnings are issued and confirmation input is required if a stop command will result in a loss of service when backup functionality is not available.
When a DSC card is stopped, removed, and then reinstalled, there is no need to restart the card (whether the card is the original or a replacement) because a freshly installed card reboots as the backup DSC automatically. However, if a DSC is stopped, either by using the ATTN button or by issuing the hw-module slot stop command, it must be restarted by using the start form of the same command, or the DSC must be removed and reinstalled in order to reboot.
Press the ATTN button on the DSCs to shut down a card manually before removing the card. This is equivalent to issuing a hw-module slot command for that card at the router command prompt. Use the ATTN button to shut down the card before it is swapped out or tested in place, or to restart it, if the card has not been removed after having been shut down.
Tip
OIR event in the case of a feature board failure when physical access to the feature board card is restricted.
Entering the hw-module slot shelf-id/slot-number reload command initiates the feature board reload process through power cycling. The hw-module slot shelf-id/slot-number reload command cannot be used to reload DSCs.
Use the reset form of this command to reset the specified feature card and drop all active calls.
Use the shutdown form of this command to shut down the specified feature card and drop all active calls.
Cisco 10000 Series Router Usage Guidelines,
In Cisco IOS Release 12.2(33)SB, when you enter the hw-module slot slot-number reset command, the software asks you to confirm the command.
In Cisco IOS Release 12.2(31)SB, the software does not ask you to confirm the hw-module slot slot-number reset command.
Examples
The following example shows how to stop the DSC in slot 13 and start the other DSC in slot 12 (which was previously stopped):
Router# hw-module slot 1/13 stopRouter# hw-module slot 1/12 startThe following example shows how to reload the dial shelf feature board in slot 6:
Router# hw-module slot 1/6 reloadThe following example shows how to reset the card in slot 3:
Router# hw-module slot 1/3 resetThe following example shows how to shut down the PRE card located in slot 3:
Router# hw-module slot 1/3 shutdownRelated Commands
plim qos input map
To configure a priority queue on Gigabit Ethernet SPAs, use the plim qos input map command in interface or subinterface configuration mode. To remove a priority queue, use the no form of this command.
plim qos input map {cos {enable | cos-value queue low-latency} | ip {dscp-based | dscp dscp-value queue low-latency} | ip {precedence-based | precedence precedence-value queue low-latency} | ipv6 tc tc-value queue low-latency | mpls exp exp-value queue low-latency
Syntax Description
Defaults
Disabled
Command Modes
Interface or subinterface configuration
Command History
Usage Guidelines
The plim qos input map command separates high-priority traffic from low-priority traffic and places the traffic in the appropriate interface queue. The command separates priority and non-priority traffic at the SPA interface processor (SIP) to prevent the dropping of high priority traffic in an oversubscription case. Each shared port adaptor (SPA) supports one priority queue.
The router supports the following classification types for the prioritization of ingress traffic on the Gigabit Ethernet SPAs:
•
•
•
•
•
For the plim qos input map ip dscp dscp-value queue low-latency command, valid values for dscp-value are one of the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For the plim qos input map ipv6 tc tc-value queue low-latency command, valid values for tc-value are one of the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following example enables DSCP-based classification on the SPA that is located in subslot 0 of the SIP in slot 1 of the Cisco 10000 series router:
Router(config)# interface gigabitethernet 3/0/1
Router(config-if)# plim qos input map ip dscp-based
Related Commands
police (policy map)
To create a per-interface policer and configure the policy-map class to use it, use the police command in policy-map class configuration mode. To delete the per-interface policer from the policy-map class, use the no form of this command.
police
police bps [[bc] normal-burst-bytes [maximum-burst-bytes | [be] [burst-bytes]]] [pir bps [be burst-bytes]] [conform-action action [exceed-action action [violate-action action]]]
no police bps
police aggregate
police aggregate name
no police aggregate name
police cir
police cir bps [[bc] normal-burst-bytes [maximum-burst-bytes | [be] [burst-bytes]]] [pir bps [be burst-bytes]] [conform-action action [exceed-action action [violate-action action]]]
no police cir bps
police cir percent
police cir percent percent [burst ms [be] [burst ms]] [pir percent percent [be burst ms]] [conform-action action [exceed-action action [violate-action action]]]
no police cir percent
police flow
police flow bps [normal-burst-bytes] [conform-action action [exceed-action action]]
police flow mask {dest-only | full-flow | src-only} bps [normal-burst-bytes] [conform-action action [exceed-action action]]
no police flow
Syntax Description
Command Default
No policing is performed.
Command Modes
Policy-map class configuration (config-pmap-c)
Command History
Usage Guidelines
In Cisco IOS Release 12.2(17d)SXB3, valid values for the bps argument for the FlexWAN interfaces only are from 8,000 to 4,000,000,000 bps.
Use the mls qos aggregate-policer name command to create a named aggregate policer.
You can create two types of aggregate policers: named and per-interface. Both types can be attached to more than one port as follows:
•
•
Use the no police aggregate name command to clear the use of the named aggregate policer.
Enter the police flow command to define a microflow policer (you cannot apply microflow policing to ARP traffic).
Enter the police command to define per-interface (not named) aggregate policers.
If the traffic is both aggregate and microflow policed, the aggregate and the microflow policers must both be in the same policy-map class and each must use the same conform-action and exceed-action keywords.
Values for the action Argument
The valid values for the action argument are as follows:
•
•
•
•
•
•
–
–
–
–
•
•
•
Note
•
•
•
If the following keywords are not specified, the default actions are as follows:
•
•
•
Cisco 10000 Series Router
In releases earlier than Cisco IOS Release 12.2(31)SB, if you modify the police rate parameters, but not the action parameters, the action parameters revert to the default actions.
For example, the following sample configuration shows the police command configured in the policy map named test. The police actions are set to set-clp-transmit for conforming, exceeding, and violating traffic. The police rate parameters are then changed to 500000, 250, and 200, respectively, but no actions are modified. When you display the test policy map again, you can see that the police actions default to transmit, drop, and drop, respectively.
Router# show policy-map testPolicy Map testClass prec1police 248000 100 10 conform-action set-clp-transmit exceed-action set-clp-transmit violate-action set-clp-transmitRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 500000 250 200Router(config-pmap-c)# endRouter# show policy-map testPolicy Map testClass prec1police 500000 250 200 conform-action transmit exceed-action drop violate-action dropCisco IOS Release 12.2(33)SB and later releases support dual police actions and a police submode; therefore, if you use the police command to modify only the rate parameters, the police actions do not default to the default actions and the previous actions are preserved.
For example, the following sample configuration shows the police command configured under the traffic class named prec1 in the policy map named test. The police rate is specified and the police actions are then specified in police submodes. After you change only the police rate parameters, the police actions do not default, but rather they retain their original settings.
Router# show policy-map testPolicy Map testClass prec1police 248000 1000 100conform-action set-clp-transmitexceed-action set-clp-transmitviolate-action set-clp-transmitRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map testRouter(config-pmap)# class prec1Router(config-pmap-c)# police 500000 100 200Router(config-pmap-c)# endRouter# show policy-map testPolicy Map testClass prec1police 500000 100 200conform-action set-clp-transmitexceed-action set-clp-transmitviolate-action set-clp-transmitExamples
This example shows how to specify a previously defined aggregate-policer name and configure the policy-map class to use the specified aggregate policer:
Router(config-pmap-c)# police aggregate agg1This example shows how to create a policy map named police-setting that uses the class map access-match, which is configured to trust received IP-precedence values and is configured with a maximum-capacity aggregate policer and a microflow policer:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map police-settingRouter(config-pmap)# class access-matchRouter(config-pmap-c)# trust ip-precedenceRouter(config-pmap-c)# police 1000000000 200000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmitRouter(config-pmap-c)# police flow 10000000 10000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmitRouter(config-pmap-c)# exitRelated Commands
scripting tcl encdir
To specify the default location of external encoding files used by the Tool Command Language (Tcl) shell, use the scripting tcl encdir command in global configuration mode. To remove the default location, use the no form of this command.
scripting tcl encdir location-url
no scripting tcl encdir
Syntax Description
Defaults
Tcl does not use external encoding files.
Command Modes
Global configuration
Command History
Usage Guidelines
Character strings in Tcl are encoded using 16-bit Unicode characters. Different operating system interfaces or applications can generate character strings using other encoding methods. Use the scripting tcl encdir command to configure a location URL for the external Tcl character encoding files to support the Tcl encoding command.
Tcl contains only a few character sets within the Tcl shell. Additional characters sets are loaded, as needed, from external files.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the router removes the no scripting tcl encdir command from the default configuration.
Examples
The following example shows how to specify a default location for external encoding files to be used by Tcl:
Router# configure terminalRouter(config)# scripting tcl encdir tftp://10.18.117.23/file2/Related Commands
scripting tcl init
Specifies an initialization script for the Tcl shell.
tclsh
Enables the Tcl shell and enters Tcl configuration mode.
scripting tcl init
To specify an initialization script for the Tool Command Language (Tcl) shell, use the scripting tcl init command in global configuration mode. To remove the initialization script, use the no form of this command.
scripting tcl init init-url
no scripting tcl init
Syntax Description
Defaults
Tcl does not run an initialization script.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the scripting tcl init command when you want to predefine Tcl procedures to run in an initialization script. The initialization script runs when the Tcl shell is entered and saves manual sourcing of the individual scripts.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the router removes the no scripting tcl init command from the default configuration.
Examples
The following example shows how to specify an initialization script to run when the Tcl shell is enabled:
Router# configure terminalRouter(config)# scripting tcl init ftp://user:password@172.17.40.3/tclscript/initfile3.tclRelated Commands
scripting tcl encdir
Specifies the default location of external encoding files used by the Tcl shell.
tclsh
Enables the Tcl shell and enters Tcl configuration mode.
service-policy
To attach a policy map to an input interface, a virtual circuit (VC), an output interface, or a VC that will be used as the service policy for the interface or VC, use the service-policy command in the appropriate configuration mode. To remove a service policy from an input or output interface or from an input or output VC, use the no form of this command.
service-policy [type access-control] {input | output} policy-map-name
no service-policy [type access-control] {input | output} policy-map-name
Cisco 10000 Series and Cisco 7600 Series Routers
service-policy [history | {input | output} policy-map-name | type control control-policy-name]
no service-policy [history | {input | output} policy-map-name | type control control-policy-name]
Syntax Description
Command Default
No service policy is specified.
A control policy is not applied to a context.
No policy map is attached.Command Modes
ATM bundle-VC configuration (config-atm-bundle)
ATM PVP configuration (config-if-atm-l2trans-pvp)
ATM VC mode (config-if-atm-vc)
Global configuration (config)
Interface configuration (config-if)
Map-class configuration (config-map-class)
PVC-in-range configuration (cfg-if-atm-range-pvc)
PVC range subinterface configuration (config-subif)Command History
Usage Guidelines
Choose the command mode according to the intended use of the command, as follows:
You can attach a single policy map to one or more interfaces or to one or more VCs to specify the service policy for those interfaces or VCs.
A service policy specifies class-based weighted fair queueing (CBWFQ). The class policies that make up the policy map are then applied to packets that satisfy the class map match criteria for the class.
To successfully attach a policy map to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent (99 percent on the Cisco 10008 router) of the interface bandwidth or the bandwidth allocated to the VC.
To enable Low Latency queueing (LLQ) for Frame Relay (priority queueing [PQ]/CBWFQ), you must first enable Frame Relay Traffic Shaping (FRTS) on the interface using the frame-relay traffic-shaping command in interface configuration mode. You then attach an output service policy to the Frame Relay VC using the service-policy command in map-class configuration mode.
For a policy map to be successfully attached to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC. For a Frame Relay VC, the total amount of bandwidth allocated must not exceed the minimum committed information rate (CIR) configured for the VC less any bandwidth reserved by the frame-relay voice bandwidth or frame-relay ip rtp priority map-class commands. If these values are not configured, the minimum CIR defaults to half of the CIR.
Configuring CBWFQ on a physical interface is possible only if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use weighted fair queueing (WFQ) by default. Other interfaces use first-in first-out (FIFO) by default. Enabling CBWFQ on a physical interface overrides the default interface queueing method. Enabling CBWFQ on an ATM permanent virtual circuit (PVC) does not override the default queueing method.
When you attach a service policy with CBWFQ enabled to an interface, commands related to fancy queueing such as those pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED) are available using the modular quality of service command-line interface (MQC). However, you cannot configure these features directly on the interface until you remove the policy map from the interface.
You can modify a policy map attached to an interface or VC, changing the bandwidth of any of the classes that make up the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amount for all classes that make up the policy map, including the modified class bandwidth, is less than or equal to 75 percent of the interface bandwidth or the VC bandwidth. If the new aggregate bandwidth amount exceeds 75 percent of the interface bandwidth or VC bandwidth, the policy map is not modified.
After you apply the service-policy command to set a class of service (CoS) bit to an Ethernet interface, the policy is set in motion as long as there is a subinterface that is performing 8021.Q or Inter-Switch Link (ISL) trunking. Upon reload, however, the service policy is removed from the configuration with the following error message:
Process `set' action associated with class-map voip failed: Set cos supported only with IEEE 802.1Q/ISL interfaces.Cisco 10000 Series Router Usage Guidelines
The Cisco 10000 series router does not support applying CBWFQ policies to unspecified bit rate (UBR) VCs.
For a policy map to be successfully attached to an interface or a VC, the aggregate of the configured minimum bandwidth of the classes that make up the policy map must be less than or equal to 99 percent of the interface bandwidth or the bandwidth allocated to the VC. If you attempt to attach a policy map to an interface when the sum of the bandwidth assigned to classes is greater than 99 percent of the available bandwidth, the router logs a warning message and does not allocate the requested bandwidth to all of the classes. If the policy map is already attached to other interfaces, it is removed from them.
The total bandwidth is the speed (rate) of the ATM layer of the physical interface. The router converts the minimum bandwidth that you specify to the nearest multiple of 1/255 (ESR-PRE1) or 1/65535 (ESR-PRE2) of the interface speed. When you request a value that is not a multiple of 1/255 or 1/65535, the router chooses the nearest multiple.
The bandwidth percentage is based on the interface bandwidth. In a hierarchical policy, the bandwidth percentage is based on the nearest parent shape rate.
By default, a minimum bandwidth guaranteed queue has buffers for up to 50 milliseconds of 256-byte packets at line rate, but not less than 32 packets.
For Cisco IOS Release 12.0(22)S and later releases, to enable LLQ for Frame Relay (priority queueing (PQ)/CBWFQ) on the Cisco 10000 series router, first create a policy map and then assign priority to a defined traffic class using the priority command. For example, the following sample configuration shows how to configure a priority queue with a guaranteed bandwidth of 8000 kbps. In the example, the Business class in the policy map named "map1" is configured as the priority queue. The map1 policy also includes the Non-Business class with a minimum bandwidth guarantee of 48 kbps. The map1 policy is attached to serial interface 2/0/0 in the outbound direction.
class-map Businessmatch ip precedence 3policy-map map1class Businessprioritypolice 8000class Non-Businessbandwidth 48interface serial 2/0/0frame-relay encapsulationservice-policy output map1On the PRE2, you can use the service-policy command to attach a QoS policy to an ATM subinterface or to a PVC. However, on the PRE3, you can attach a QoS policy only to a PVC.
Cisco 7600 Series Routers
The output keyword is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
Do not attach a service policy to a port that is a member of an EtherChannel.
Although the CLI allows you to configure QoS based on policy feature cards (PFCs) on the WAN ports on the OC-12 ATM optical services modules (OSM) and on the WAN ports on the channelized OSMs, PFC-based QoS is not supported on the WAN ports on these OSMs. OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
PFC QoS supports the optional output keyword only on VLAN interfaces. You can attach both an input policy map and an output-policy map to a VLAN interface.
Cisco 10000 Series Routers Control Policy Maps
A control policy map must be activated by applying it to a context. A control policy map can be applied to one or more of the following types of contexts, which are listed in order of precedence:
1.
2.
3.
4.
5.
6.
In general, control policy maps that are applied to more specific contexts take precedence over policy maps applied to more general contexts. In the list, the context types are numbered in order of precedence. For example, a control policy map that is applied to a permanent virtual circuit (PVC) takes precedence over a control policy map that is applied to an interface.
Control policies apply to all sessions hosted on the context. Only one control policy map can be applied to a given context.
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the abbreviated form (ser) of the service-policy command. Instead, you must spell out the command name service- before the router accepts the command.
For example, the following error message displays when you attempt to use the abbreviated form of the service-policy command:
interface GigabitEthernet1/1/0ser out ?% Unrecognized commandser ?% Unrecognized commandAs shown in the following example, when you enter the command as service- followed by a space, the router parses the command as service-policy. Entering the question mark causes the router to display the command options for the service-policy command.
service- ?input Assign policy-map to the input of an interfaceoutput Assign policy-map to the output of an interfacetype Configure CPL Service PolicyIn releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the service-policy command. For example, the router accepts the following commands:
interface GigabitEthernet1/1/0ser out testExamples
The following example shows how to attach a policy map to a Fast Ethernet interface:
interface fastethernet 5/20service-policy input pmap1The following example shows how to attach the service policy map named "policy9" to DLCI 100 on output serial interface 1 and enables LLQ for Frame Relay:
interface Serial1/0.1 point-to-pointframe-relay interface-dlci 100class fragmentmap-class frame-relay fragmentservice-policy output policy9The following example shows how to attach the service policy map named "policy9" to input serial interface 1:
interface Serial1service-policy input policy9The following example attaches the service policy map named "policy9" to the input PVC named "cisco":
pvc cisco 0/34 service-policy input policy9vbr-nt 5000 3000 500 precedence 4-7The following example shows how to attach the policy named "policy9" to output serial interface 1 to specify the service policy for the interface and enable CBWFQ on it:
interface serial1service-policy output policy9The following example attaches the service policy map named "policy9" to the output PVC named "cisco":
pvc cisco 0/5 service-policy output policy9 vbr-nt 4000 2000 500 precedence 2-3Cisco 10000 Series Router Examples
The following example shows how to attach the service policy named "userpolicy" to DLCI 100 on serial subinterface 1/0/0.1 for outbound packets:
interface serial 1/0/0.1 point-to-pointframe-relay interface-dlci 100service-policy output userpolicy
Note
The following example shows how to attach a QoS service policy named "map2" to PVC 0/101 on the ATM subinterface 3/0/0.1 for inbound traffic:
interface atm 3/0/0atm pxf queuinginterface atm 3/0/0.1pvc 0/101service-policy input map2
Note
The following example shows how to attach a service policy named "myQoS" to physical Gigabit Ethernet interface 1/0/0 for inbound traffic. VLAN 4, configured on Gigabit Ethernet subinterface 1/0/0.3, inherits the service policy of physical Gigabit Ethernet interface 1/0/0.
interface GigabitEthernet 1/0/0service-policy input myQoSinterface GigabitEthernet 1/0/0.3encapsulation dot1q 4The following example shows how to apply the policy map named "policy1" to the virtual template named "virtual-template1" for all inbound traffic. In this example, the virtual template configuration also includes Challenge Handshake Authentication Protocol (CHAP) authentication and PPP authorization and accounting.
interface virtual-template1ip unnumbered Loopback1no peer default ip addressppp authentication chap vpn1ppp authorization vpn1ppp accounting vpn1service-policy input policy1The following example shows how to attach the service policy map named "voice" to ATM VC 2/0/0 within a PVC range of a total of three PVCs and enable PVC range configuration mode where a point-to-point subinterface is created for each PVC in the range. Each PVC created as part of the range has the voice service policy attached to it.
configure terminalinterface atm 2/0/0range pvc 1/50 1/52service-policy input voiceThe following example shows how to attach the service policy map named "voice" to ATM VC 2/0/0 within a PVC range, where every VC created as part of the range has the voice service policy attached to it. The exception is PVC 1/51, which is configured as an individual PVC within the range and has a different service policy named "data" attached to it in PVC-in-range configuration mode.
configure terminalinterface atm 2/0/0range pvc 1/50 1/52service-policy input voicepvc-in-range 1/51service-policy input dataThe following example shows how to configure a service group named "PREMIUM-SERVICE" and apply the input policy named "PREMIUM-MARK-IN" and the output policy named "PREMIUM-OUT" to the service group:
policy-map type service PREMIUM-SERVICEservice-policy input PREMIUM-MARK-INservice-policy output PREMIUM-OUTRelated Commands
show atm vp
To display the statistics for all virtual paths (VPs) on an interface or for a specific VP, use the show atm vp command in privileged EXEC mode.
show atm vp [vpi]
Syntax Description
vpi
(Optional) ATM network virtual path identifier (VPI) of the permanent virtual path. The range is from 0 to 255. The VPI is an 8-bit field in the header of the ATM cell.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cisco 10000 Series Router
In Cisco IOS Release 12.2(33)SB, the output from the show atm vp command nolonger displays "ATM" as the type of interface, as shown in the following sample output:
Router# show atm vpData CES PEAK CES Avg/Min Burst MCRInterface VPI SC VCs VCs Kbps Kbps Kbps Cells Kbps CDVT Status3/0/0 200 N/A 0 0 2000 0 NA NA NA 140.0 ACTIVEIn Cisco IOS Release 12.2(31)SB, the output from the show atm vp command displays the ATM interface type:
Router# show atm vpData CES PEAK CES Avg/Min Burst MCR CDVTInterface VPI SC VCs VCs Kbps Kbps Kbps Cells Kbps Usecs StatusATM3/0/0 200 0 0 2000 0 NA NA NA 140.0 ACTIVEExamples
The following is sample output from the show atm vp command. This output shows the interface name, the status of the interface, the administrative status of the interface, the port type, and the number of channels in use on the interface. The status of the interface can be UP (in operation) or DOWN (not in operation).
Router# show atm vp 1ATM6/0 VPI: 1, PeakRate: 155000, CesRate: 1742, DataVCs: 1, CesVCs:1, Status: ACTIVEVCD VCI Type InPkts OutPkts AAL/Encap Status1 100 PVC n/a n/a CES-AAL1 ACTIVE13 13 PVC 0 0 AAL5-SNAP ACTIVE409 3 PVC 0 0 F4 OAM ACTIVE410 4 PVC 0 0 F4 OAM ACTIVETotalInPkts: 0, TotalOutPkts: 0, TotalInFast: 0, TotalOutFast: 0, TotalBroadcasts: 0Table 6 describes the fields shown in the display.
Related Commands
atm pvp
Creates a PVP used to multiplex (or bundle) one or more VCs (especially CES and data VCs).
show controllers (line card image)
To display information that is specific to the hardware on a line card, use the attach command in privileged EXEC mode to connect to the line card and then use the show controllers command in privileged EXEC mode or the execute-on command in privileged EXEC mode.
show controllers atm [[port-number] [all | sar | summary]]
show controllers fia [register]
show controllers {frfab | tofab} {bma {microcode | ms-inst | register} | qelem start-queue-element [end-queue-element] | qnum start-queue-number [end-queue-number] | queues | statistics}
show controllers io
show controllers l3
show controllers pos {framers | queues | registers | rxsram port-number queue-start-address [queue-length] | txsram port-number queue-start-address [queue-length]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This information displayed by this command is of use only to technical support representatives in analyzing unexpected system failures in the field. It is documented here in case you need to provide the displayed statistics to an technical support engineer.
Cisco 10000 Series Router Usage Guidelines
In releases prior to Cisco IOS Release 12.2(33)SB, when you configure the t1 loopback remote command on the local router, the command also displays in the running-config file of the far-end router. This is due to the route processor (RP) updating an incorrect parameter when it receives the loopback event message from the line card for loopback requests from the far end.
In Cisco IOS Release 12.2(33)SB, the RP updates the correct parameter and the show controllers command correctly displays the loopback CLI commands applied on the local end and displays the loopback events and status received from the line card in response to loopback requests from the far end.
This change in behavior affects the following line cards and is documented in the CSCsm84447 caveat:
•
•
•
•
In Cisco IOS Release 12.2(33)SB, the output from the show controller command includes line code information for the 6-port channelized T3 line card and the 8-port E3/DS3 line card. However, because SONET line cards do not have a direct physical link at the T3 or E3 level, the output from the show controller t3 command does not include line code information.
In Cisco IOS Release 12.2(31)SB, the output from the show controller command displays line code information. The output of the show controller t3 command for SONET-based T3 also includes line code information.
Examples
Because you are executing this command on the line card, you must use the execute-on command to use the show command, or you must connect to the card using the attach command. All examples in this section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 0TX SAR (Beta 1.0.0) is Operational;RX SAR (Beta 1.0.0) is Operational;Interface Configuration Mode:STS-12cActive Maker Channels: total # 6VCID ChnnlID Type OutputInfo InPkts InOAMs MacString1 0888 UBR 0C010010 0 0 08882000AAAA0300000008002 0988 VBR 04010020 0 0 098820003 8BC8 UBR 0C010030 0 0 8BC82000AAAA0300000008004 0E08 UBR 0C010040 0 0 0E082000AAAA03000000080010 1288 VBR 040100A0 0 0 1288200011 8BE8 VBR 0C0100B0 0 0 8BE82000AAAA030000000800SAR Total Counters:total_tx_idle_cells 215267 total_tx_paks 0 total_tx_abort_paks 0total_rx_paks 0 total_rx_drop_paks 0 total_rx_discard_cells 15Switching Code Counters:total_rx_crc_err_paks 0 total_rx_giant_paks 0total_rx_abort_paks 0 total_rx_crc10_cells 0total_rx_tmout_paks 0 total_rx_unknown_paks 0total_rx_out_buf_paks 0 total_rx_unknown_vc_paks 0BATMAN Asic Register Values:hi_addr_reg 0x8000, lo_addr_reg 0x000C, boot_msk_addr 0x0780,rmcell_msk_addr 0x0724, rmcnt__msk_addr 0x07C2, txbuf_msk_addr 0x070C,...CM622 SAR Boot Configuration:txind_q_addr 0x14000 txcmd_q_addr 0x20000...SUNI-622 Framer Register Values:Master Rst and Ident/Load Meters Reg (#0x0): 0x10Master Configuration Reg (#0x1): 0x1FMaster Interrupt Status Reg (#0x2): 0x00PISO Interrupt Reg (#0x3): 0x04Master Auto Alarm Reg (#0x4): 0x03Master Auto Alarm Reg (#0x5): 0x07Parallel Output Port Reg (#0x6): 0x02...BERM Line BIP Threshold LSB Reg (#0x74): 0x00BERM Line BIP Threshold MSB Reg (#0x75): 0x00Router#The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllersInterface POS0Hardware is BFLC POSlcpos_instance struct 60311B40RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000400SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loopInterface POS1Hardware is BFLC POSlcpos_instance struct 603142E0RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000600SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loop...Router#The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framersFramer 0, addr=0x12000400:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00Framer 1, addr=0x12000600:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00Framer 2, addr=0x12000800:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00...Router#The following is partial sample output from the show controllers fia command:
Router# execute-on slot 7 show controllers fia========= Line Card (Slot 7) =======Fabric configuration: Full bandwidth redundantMaster Scheduler: Slot 17From Fabric FIA Errors-----------------------redund fifo parity 0 redund overflow 0 cell drops 0crc32 lkup parity 0 cell parity 0 crc32 00 1 2 3 4-------- -------- -------- -------- --------los 0 0 0 0 0crc16 0 0 0 0 0To Fabric FIA Errors-----------------------sca not pres 0 req error 0 uni fifo overflow 0grant parity 0 multi req 0 uni fifo undrflow 0cntrl parity 0 uni req 0 crc32 lkup parity 0multi fifo 0 empty dst req 0 handshake error 0Related Commands
show controllers t3
To display information about the T3 links and to display the hardware and software driver information for the T3 controller, use the show controllers t3 command in privileged EXEC mode.
Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 Series, Cisco 3725, and Cisco 3745 Routers
show controllers t3 slot/port [brief | tabular]
Cisco 7200 Series Routers
show controllers t3 [bay/port[/t1-channel]] [brief | errors | tabular | remote performance [brief | tabular]]
Cisco 7500 Series Routers
show controllers t3 [slot/bay/port[/t1-channel]] [brief | errors | tabular | remote performance [brief | tabular]]
Cisco AS5800 Access Servers
show controllers t3 dial-shelf/slot/t3-port
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cisco 7500 Series Routers
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
By using the errors keyword, this command displays history that identifies which alarm events caused a T3 or T1 controller of a T3 to go down for the Cisco 7500 and Cisco 7200 series routers.
Note
numbering scheme (0 to 27) used with other Cisco products. This is to ensure consistency with
telco numbering schemes for T1 channels within channelized T3 equipment.
The show controllers t3 command also displays Maintenance Data Link (MDL) information (received strings) if MDL is configured and framing is set to C-bit.
Cisco 10000 Series Router Usage Guidelines
In releases prior to Cisco IOS Release 12.2(33)SB, when you configure the t1 loopback remote command on the local router, the command also displays in the running-config file of the far-end router. This is due to the route processor (RP) updating an incorrect parameter when it receives the loopback event message from the line card for loopback requests from the far end.
In Cisco IOS Release 12.2(33)SB, the RP updates the correct parameter and the show controllers command correctly displays the loopback CLI commands applied on the local end and displays the loopback events and status received from the line card in response to loopback requests from the far end.
This change in behavior affects the following line cards and is documented in the CSCsm84447 caveat:
•
•
•
•
In Cisco IOS Release 12.2(33)SB, the output from the show controller command includes line code information for the 6-port channelized T3 line card and the 8-port E3/DS3 line card. However, because SONET line cards do not have a direct physical link at the T3 or E3 level, the output from the show controller t3 command does not include line code information.
In Cisco IOS Release 12.2(31)SB, the output from the show controller command displays line code information. The output of the show controller t3 command for SONET-based T3 also includes line code information.
Examples
Cisco 7200 Series Routers
The following is partial output from the show controllers t3 errors command for Cisco IOS Release 12.2(19c) for a specific T1 controller of a T3 on a Cisco 7200 series router with a bay/port of 4/1, displaying the T1 1 alarm event of OOF:
Router# show controllers t3 4/1/1 errorsT3 4/1: Error Log Informationpresent alarm: NONEError: AIS17:28:08-17:29:18T1 1 Error Log Informationpresent alarm: OOFSince 17:30:55Error: OOF17:30:09-17:30:46The following is partial output from the show controllers t3 errors command from Cisco IOS Release 12.2(19c) for a T3 controller on a Cisco 7200 series router with a bay/port of 4/1, displaying a history of all alarm events on all 28 T1 channels:
Router# show controllers t3 4/1 errorsT3 4/1: Error Log Informationpresent alarm: NONEError: AIS17:28:08-17:29:18T1 1 Error Log Informationpresent alarm: OOFSince 17:30:55Error: OOF17:30:09-17:30:46T1 2 Error Log Informationpresent alarm: NONET1 3 Error Log Informationpresent alarm: NONET1 4 Error Log Informationpresent alarm: NONET1 5 Error Log Informationpresent alarm: NONET1 6 Error Log Informationpresent alarm: NONET1 7 Error Log Informationpresent alarm: NONET1 8 Error Log Informationpresent alarm: NONET1 9 Error Log Informationpresent alarm: NONET1 10 Error Log Informationpresent alarm: NONET1 11 Error Log Informationpresent alarm: NONE....Cisco 7500 Series Routers
The following is partial output from the show controllers t3 errors command from Cisco IOS Release 12.2(19c) for a T3 controller with a slot/bay/port of 1/4/1, displaying a history of all alarm events on all 28 T1 channels:
Router# show controllers t3 1/4/1 errorsT3 1/4/1: Error Log Informationpresent alarm: NONEError: AIS17:28:08-17:29:18T1 1 Error Log Informationpresent alarm: OOFSince 17:30:55Error: OOF17:30:09-17:30:46T1 2 Error Log Informationpresent alarm: NONET1 3 Error Log Informationpresent alarm: NONET1 4 Error Log Informationpresent alarm: NONET1 5 Error Log Informationpresent alarm: NONET1 6 Error Log Informationpresent alarm: NONET1 7 Error Log Informationpresent alarm: NONE...The following is partial output from the show controllers t3 errors command from Cisco IOS Release 12.2(19c) for a specific T1 controller of a T3 on a Cisco 7200 series router with a bay/port of 4/1, displaying the T1 1 alarm event of OOF:
Router# show controllers t3 4/1/1 errorsT3 4/1: Error Log Informationpresent alarm: NONEError: AIS17:28:08-17:29:18T1 1 Error Log Informationpresent alarm: OOFSince 17:30:55Error: OOF17:30:09-17:30:46...Table 7 describes the error field shown in the display.
The following is partial output from the show controllers t3 command from Cisco IOS Release 12.2(19c):
Router# show controllers t3 2/1/0T3 2/1/0 is down. Hardware is 2CT3 single wide port adapterCT3 H/W Version:0.2.2, CT3 ROM Version:1.0, CT3 F/W Version:2.5.1FREEDM version:1, reset 0 resurrect 0Applique type is Channelized T3Transmitter is sending remote alarm.Receiver has loss of signal.FEAC code received:No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is InternalRx-error throttling on T1's ENABLEDRx throttle total 0, equipment customer loopbackData in current interval (545 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs545 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 1:0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs900 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 2:<snip>The following is partial output from the show controllers t3 command from Cisco IOS Release 12.2(19c) for the T1 channel of the T3 controller:
Router# show controllers t3 2/1/0 /1T3 2/1/0 is down. Hardware is 2CT3 single wide port adapterCT3 H/W Version:0.2.2, CT3 ROM Version:1.0, CT3 F/W Version:2.5.1FREEDM version:1, reset 0 resurrect 0T1 1 is downtimeslots:1-24FDL per AT&T 54016 spec.Receiver has loss of signal.Framing is ESF, Clock Source is InternalData in current interval (0 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs, 0 Stuffed SecsThe following is partial output from the show controllers t3 command:
Router# show controllers t3 3/0/0T3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0Mx H/W version: 2, Mx ucode ver: 1.24Applique type is Channelized T3No alarms detected.FEAC code received: No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is Internal.Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OKData in current interval (39 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation0 P-bit Err Secs, 0 P-bit Severely Err Secs0 Severely Err Framing Secs, 0 Unavailable Secs0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 1 15 minute intervals):0 Line Code Violations, 0 P-bit Coding Violation,0 C-bit Coding Violation,0 P-bit Err Secs, 0 P-bit Severely Err Secs,0 Severely Err Framing Secs, 0 Unavailable Secs,0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs...T1 1 is down, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per ANSI T1.403 and AT&T 54016 spec.Configured for FDL Remotely Line LoopedNo alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal.BERT test result (running)Test Pattern: All 0's, Status: Sync, Sync Detected: 1Interval: 4 minute(s), Tim Remain: 4 minute(s)Bit Errors (Sync BERT Started): 0 bitsBit Errors (Sync last Sync): 0 bits, Bits Received: 7 MbitsThe following is partial output from the show controllers t3 brief command:
Router# show controllers t3 3/0/0 briefT3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0Mxt H/W version: 2, Mxt ucode ver: 1.24Applique type is Channelized T3No alarms detected.FEAC code received: No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is Internal.Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OKT1 1 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per ANSI T1.403 and AT&T 54016 spec.Configured for FDL Remotely Line LoopedNo alarms detected.Framing is ESF, LineCode is B8ZS, Clock Source is Internal.BERT test result (done)Test Pattern: All 0's, Status: Not Sync, Sync Detected: 1Interval: 4 minute(s), Tim Remain: 0 minute(s)Bit Errors(Sync BERT Started): 0 bitsBit Errors(Sync last Sync): 0 bits, Bits Received: 368 Mbits...The following is partial output from the show controllers t3 tabular command:
Router# show controllers t3 3/0/0 tabularT3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 1.2, CT3 F/W Version: 2.1.0Mx H/W version: 2, Mx ucode ver: 1.25Applique type is Channelized T3No alarms detected.MDL transmission is disabledFEAC code received: No code is being receivedFraming is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.Ext1: AIS, Ext2: LOS, Ext3: LOS, Test: LOSINTERVAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES08:56-09:11 0 0 0 0 0 0 0 0 0 008:41-08:56 0 0 0 0 0 0 0 0 0 008:26-08:41 0 0 0 0 0 0 0 0 0 0Total 0 0 0 0 0 0 0 0 0 0...T1 2 is up, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Line Code is B8ZS, Clock Source is Internal.INTERVAL LCV PCV CSS SELS LES DM ES BES SES UAS SS08:56-09:11 0 0 0 0 0 0 0 0 0 0 008:41-08:56 0 0 0 0 0 0 0 0 0 0 008:26-08:41 0 0 0 0 0 0 0 0 0 0 0Total 0 0 0 0 0 0 0 0 0 0 0The following output shows a controller with a high number of errors on the line, thus showing a throttle count (RX throttles).
Router# show controllers t3 6/0/0 tabularT1 2 is uptimeslots: 1-24FDL per AT&T 54016 spec.No alarms detected.Framing is ESF, Clock Source is Line, Rx throttles 47INTERVAL LCV PCV CSS SELS LES DM ES BES SES UAS SS07:48-07:53 0 0 0 0 0 0 0 0 0 0The following is partial output from the show controllers t3 remote performance command. This information is available if the t1 fdl ansi controller configuration command is enabled for a T1 channel on a CT3IP.
Router# show controllers t3 3/0/0 remote performanceT3 3/0/0 is up.CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 20.2.0Mx H/W version: 2, Mx ucode ver: 1.25T1 1 - Remote Performance DataData in current interval (356 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail SecsData in Interval 1:1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail SecsData in Interval 2:0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail SecsTotal Data (last 2 15 minute intervals):1 Path Code Violations1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs0 Unavail Secs...Table 8 describes the fields shown in the display.
Cisco AS5800 Access Servers
The following example shows the summary status of the T3 controller located in shelf 1, slot 4, port 0:
Router# show controllers t3 1/4/0 briefT3 1/4/0 is up.Applique type is Channelized T3No alarms detected.MDL transmission is disabledFEAC code received: Multiple DS1 LOS/HBERFraming is C-BIT Parity, Line Code is B3ZS, Clock Source is Line.Data in current interval (491 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 80 15 minute intervals):3 Line Code Violations, 4 P-bit Coding Violation,2 C-bit Coding Violation, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,2 Unavailable Secs, 0 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored SecsThe following example shows the detailed status of the T3 controller connected to the Cisco AS5800 in shelf 1, slot 4, port 0. Notice that the detailed information shows the last eighty-six 15-minute time periods.
Router# show controllers t3 1/4/0T3 1/4/0 is up.Applique type is Channelized T3No alarms detected.MDL transmission is disabledFEAC code received: Multiple DS1 LOS/HBERFraming is C-BIT Parity, Line Code is B3ZS, Clock Source is Line.Data in current interval (91 seconds elapsed):0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 1:0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 2:0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 3:0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsData in Interval 4:0 Line Code Violations, 0 P-bit Coding Violation0 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs0 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored Secs...Data in Interval 86:3 Line Code Violations, 4 P-bit Coding Violation2 C-bit Coding Violation, 0 P-bit Err Secs0 P-bit Severely Err Secs, 0 Severely Err Framing Secs2 Unavailable Secs, 0 Line Errored Secs0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTotal Data (last 86 15 minute intervals):3 Line Code Violations, 4 P-bit Coding Violation,2 C-bit Coding Violation, 0 P-bit Err Secs,0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,2 Unavailable Secs, 0 Line Errored Secs,0 C-bit Errored Secs, 0 C-bit Severely Errored SecsTable 9 describes the fields shown in the display.
Cisco 10000 Series Router Examples
The following examples from the show controller t3 command show the information that displays when the router is running Cisco IOS Release 12.2(33)SB and Cisco IOS Release 12.2(31)SB:
Cisco IOS Release 12.2(33)SB —No Line Code Information
Router# show controller t3 5/0/0.1T3 5/0/0.1 is up. Hardware is C10K CHOC12 line cardApplique type is Channelized T3.Controller is in unchannelized mode.No alarms detected.MDL transmission is disabled.FEAC code received: No code is being received.Framing is C-BIT Parity (Configured), Clock Source is Internal.DSU mode is cisco, DSU bandwidth is 44210.Cisco IOS Release 12.2(31)SB —Line Code Information
Router# show controller t3 5/0/0.1T3 5/0/0.1 is up. Hardware is C10K CHOC12 line cardApplique type is Channelized T3.Controller is in channelized mode.No alarms detected.MDL transmission is disabled.FEAC code received: No code is being receivedFraming is C-BIT Parity (Configured)Line Code is B3ZS, Clock Source is Internal.show diag
To display hardware and diagnostic information for a networking device, a line card, a processor, a jacket card, a chassis, or a network module, use the show diag command in privileged EXEC configuration mode.
show diag [slot-number] [details | summary]
Cisco 7304 Router
show diag [slot-number | chassis | subslot slot/subslot] [details | summary]
Shared Port Adapters
show diag [subslot slot/subslot] [details | summary]
Network Module
show diag [slot-number]
Cisco 10000 Series Router
show diag [slot/subslot] [details | summary] [crashdump]
Syntax Description
Defaults
None
Privileged EXEC
Command History
Usage Guidelines
Use this command to determine the type of hardware installed in your router, and to show detailed hardware information and EEPROM version information.
This command displays information for the motherboard, WAN interface cards (WICs), voice interface cards (VICs), high-speed WICs (HWICs), ATM interface cards (AICs), advanced integration modules (AIMs), port adapters, shared port adapters (SPAs), modular services cards (MSCs), SPA interface processors (SIPs), and enhanced network modules (NME).
Cisco 7304 Router Usage Guidelines
For the Cisco 7304 router, this command applies to NEs, line cards, MSCs, and SPAs.
•
•
Shared Port Adapter Usage Guidelines
•
•
Cisco 10000 Series Router Usage Guidelines
The crashdump option of the show diag command enables you to display any crashdump files collected on the SPA Interface Processor (SIP). The SIP stores the crashdump files by a reference number from 1 to 60.
To view a crashdump file, do the following:
Step 1
a.
b.
Number of crashdumps : output numberStep 2
show diag slot/subslot crashdump number
Note
Examples
1-Port T3 Serial Port Adapter: Example
The following is sample output from the show diag command for a 1-port T3 serial port adapter in chassis slot 1 on a Cisco 7200 series router:
Router# show diag 1Slot 1:Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0Microcode Status 0x4Master Enable, LED, WCS LoadedBoard is analyzedPending I/O Status: NoneEEPROM format version 1VIP2 controller, HW rev 2.4, board revision D0Serial number: 04372053 Part number: 73-1684-03Test history: 0x00 RMA number: 00-00-00Flags: cisco 7000 board; 7500 compatibleEEPROM contents (hex):0x20: 01 15 02 04 00 42 B6 55 49 06 94 03 00 00 00 000x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Slot database information:Flags: 0x4 Insertion time: 0x14A8 (5d02h ago)Controller Memory Size: 16 MBytes DRAM, 1024 KBytes SRAMPA Bay 0 Information:T3 Serial PA, 1 portsEEPROM format version 1HW rev FF.FF, Board revision UNKNOWNSerial number: 4294967295 Part number: 255-65535-255Cisco 12000 Series Internet Router: Example
The following is sample output from the show diag command on a Cisco 12000 series Internet router:
Router# show diag 3SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi ModeMAIN: type 33, 00-0000-00 rev 70 dev 0HW config: 0x01 SW key: 00-00-00PCA: 73-2147-02 rev 94 ver 2HW version 1.0 S/N 04499695MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0HW version 1.1 S/N 04494882Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00DIAG: Test count: 0x05000001 Test results: 0x00000000MBUS Agent Software version 01.27 (RAM) using CAN Bus AROM Monitor version 00.0DFabric Downloader version used 00.0D (ROM version is 00.0D)Board is analyzedBoard State is Line Card Enabled (IOS RUN )Insertion time: 00:00:10 (00:04:51 ago)DRAM size: 33554432 bytesFrFab SDRAM size: 67108864 bytesToFab SDRAM size: 16777216 bytesThe following is sample output from the show diag command with the summary keyword:
Router# show diag summarySLOT 0 (RP/LC 0 ): Route ProcessorSLOT 2 (RP/LC 2 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 4 (RP/LC 4 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 7 (RP/LC 7 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 9 (RP/LC 9 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 11 (RP/LC 11): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 16 (CSC 0 ): Clock Scheduler CardSLOT 17 (CSC 1 ): Clock Scheduler CardSLOT 18 (SFC 0 ): Switch Fabric CardSLOT 19 (SFC 1 ): Switch Fabric CardSLOT 20 (SFC 2 ): Switch Fabric CardSLOT 24 (PS A1 ): AC Power SupplySLOT 26 (PS B1 ): AC Power SupplySLOT 28 (TOP FAN ): Blower ModuleSLOT 29 (BOT FAN ): Blower ModuleThe following is sample output from the show diag command with the details keyword:
Router# show diag 4 detailsSLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeMAIN: type 33, 800-2389-01 rev 71 dev 16777215HW config: 0x00 SW key: FF-FF-FFPCA: 73-2275-03 rev 75 ver 3HW version 1.1 S/N 04529465MBUS: MBUS Agent (1) 73-2146-06 rev 73 dev 0HW version 1.1 S/N 04541395Test hist: 0xFF RMA#: FF-FF-FF RMA hist: 0xFFDIAG: Test count: 0x05000001 Test results: 0x00000000EEPROM contents (hex):00: 01 00 01 00 49 00 08 62 06 03 00 00 00 FF FF FF10: 30 34 35 34 31 33 39 35 FF FF FF FF FF FF FF FF20: 01 01 00 00 00 00 00 FF FF FF FF FF FF FF FF FF30: A5 FF A5 A5 A5 A5 FF A5 A5 A5 A5 A5 A5 A5 A5 A540: 00 21 01 01 00 49 00 08 E3 03 05 03 00 01 FF FF50: 03 20 00 09 55 01 01 FF FF FF 00 FF FF FF FF FF60: 30 34 35 32 39 34 36 35 FF FF FF FF FF FF FF FF70: FF FF FF FF FF FF FF FF 05 00 00 01 00 00 00 00MBUS Agent Software version 01.24 (RAM)Fabric Downloader version 00.0DBoard is analyzedFlags: 0x4Board State is Line Card Enabled (IOS RUN)Insertion time: 00:00:10 (00:04:51 ago)DRAM size: 33554432 bytesFrFab SDRAM size: 67108864 bytesToFab SDRAM size: 16777216 bytesATM SAR AIM in a Cisco 3660: Example
The following is sample output from the show diag command for one ATM Segmentation and Reassembly (SAR) AIM in a Cisco 3660 router:
Router# show diag 03660 Chassis type: ENTERPRISEc3600 Backplane EEPROM:Hardware Revision : 1.0Top Assy. Part Number : 800-04740-02...ATM AIM: 1ATM AIM module with SAR only (no DSPs)Hardware Revision : 1.0Top Assy. Part Number : 800-03700-01Board Revision : A0Deviation Number : 0-0Fab Version : 02PCB Serial Number : JAB9801ABCDNM-AIC-64 Installed in a Cisco 2611: Example
The following is sample output from the show diag command for a Cisco 2611 router with the NM-AIC-64 installed.
Router# show diagSlot 0: C2611 2E Mainboard Port adapter, 2 ports Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 2.3 PCB Serial Number : JAD044808SG (1090473337) Part Number : 73-2840-13 RMA History : 00 RMA Number : 0-0-0-0 Board Revision : C0 Deviation Number : 0-0 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 00 92 41 02 03 C1 18 4A 41 44 30 34 34 0x10: 38 30 38 53 47 20 28 31 30 39 30 34 37 33 33 33 0x20: 37 29 82 49 0B 18 0D 04 00 81 00 00 00 00 42 43 0x30: 30 80 00 00 00 00 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 Slot 1: NM_AIC_64 Port adapter, 3 ports Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 1.0 Part Number : 74-1923-01 Board Revision : 02 PCB Serial Number : DAN05060012 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 02 55 41 01 00 82 4A 07 83 01 42 30 32 0x10: C1 8B 44 41 4E 30 35 30 36 30 30 31 32 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 FFTable 10 describes significant fields shown in the display.
AIM-VPN in a Cisco 2611XM: Example
The following example shows how to obtain hardware information about an installed AIM-VPN on the Cisco 2611XM router.
Router# show diag 0
Encryption AIM 1:
Hardware Revision :1.0
Top Assy. Part Number :800-03700-01
Board Revision :A0
Deviation Number :0-0
Fab Version :02
PCB Serial Number :JAB9801ABCD
RMA Test History :00
RMA Number :0-0-0-0
RMA History :00
EEPROM format version 4
EEPROM contents (hex):
0x00:04 FF 40 03 0B 41 01 00 C0 46 03 20 00 0E 74 01
0x10:42 41 30 80 00 00 00 00 02 02 C1 8B 4A 41 42 39
0x20:38 30 31 41 42 43 44 03 00 81 00 00 00 00 04 00
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 FFTable 11 describes significant fields shown in the display.
MSC-100 on the Cisco 7304 Router: Example
The following is sample output from the show diag slot-number version of the command for an MSC-100 located in slot number 4 on a Cisco 7304 router. Information about the MSC is followed by information for its associated SPAs:
Router# show diag 4Slot 4:7304-MSC-100 SPA Carrier Card Line CardLine Card state: ActiveInsertion time: 00:08:49 agoBandwidth points: 4000000EEPROM contents at hardware discovery:Hardware Revision : 0.18Boot Time out : 0000PCB Serial Number : CSJ07288905Part Number : 73-8789-01Board Revision : A0Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0-0Product Number : 7304-MSC-100Top Assy. Part Number : 68-1163-04Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 50 41 00 12 46 00 00 C1 8B 43 53 4A0x10: 30 37 32 38 38 39 30 35 82 49 22 55 01 42 41 300x20: 02 02 03 00 81 00 00 00 00 04 00 80 00 00 00 000x30: CB 94 37 33 30 34 2D 4D 53 43 2D 31 30 30 20 200x40: 20 20 20 20 20 20 87 44 04 8B 04 C4 08 00 00 000x50: 00 00 00 00 00 C5 08 00 00 00 00 00 00 00 00 C80x60: 09 00 00 00 00 00 00 00 00 00 C7 7C F6 44 3F 300x70: 00 00 00 00 00 00 00 00 00 00 00 00 02 EE FF C80x80: C8 37 26 05 DC 64 28 1E 37 26 09 C4 64 32 28 320x90: DD 0C E4 64 32 28 43 24 2E E0 AA 82 64 F4 24 000xA0: 00 00 00 00 00 00 F0 2E FF FF FF FF FF FF FF FF0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x100: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x110: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x120: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x140: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFFPGA information:Current FPGA version : 00.23IOS bundled FPGA version : 00.23CPLD version : 01.02Subslot 4/1:Shared port adapter: SPA-4FE-7304, 4 portsState: okInsertion time: 00:15:13 agoBandwidth: 400000 kbpsEEPROM contents:NSE-100 on the Cisco 7304 Router: Example
The following example displays diagnostic information about the NSE-100 in slot 0 of a Cisco 7304 router:
Router# show diag 0Slot 0/1:NSE Card state:PrimaryInsertion time:00:03:47 agoC7300 NSE Mainboard EEPROM:Hardware Revision :2.3PCB Serial Number :CAB0532JYYTPart Number :73-5198-02Board Revision :A0Fab Version :02RMA Test History :00RMA Number :0-0-0-0RMA History :00Deviation Number :0-0Product Number :7300-NSE-100Top Assy. Part Number :68-1002-02Manufacturing Test Data :00 00 00 00 00 00 00 00Field Diagnostics Data :00 00 00 00 00 00 00 00Calibration Data :Minimum:0 dBmV, Maximum:0 dBmVCalibration values :EEPROM format version 4EEPROM contents (hex):0x00:04 FF 40 02 8B 41 02 03 C1 8B 43 41 42 30 35 330x10:32 4A 59 59 54 82 49 14 4E 02 42 41 30 02 02 030x20:00 81 00 00 00 00 04 00 80 00 00 00 00 CB 94 370x30:33 30 30 2D 4E 53 45 2D 31 30 30 20 20 20 20 200x40:20 20 20 87 44 03 EA 02 C4 08 00 00 00 00 00 000x50:00 00 C5 08 00 00 00 00 00 00 00 00 C8 09 00 000x60:00 00 00 00 00 00 00 C7 7C F6 44 3F 30 F6 44 3F0x70:30 F6 44 3F 30 00 00 00 00 07 08 64 32 28 37 260x80:09 C4 5A 32 28 32 DD 0C E4 5A 2D 23 43 24 13 880x90:64 32 28 65 BA 2E E0 AA 82 64 F4 24 00 00 00 000xA0:00 00 00 EF 1C FF FF FF FF FF FF FF FF FF FF FF0xB0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xC0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xD0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xE0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xF0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFC7300 NSE Daughterboard EEPROM:Hardware Revision :2.0PCB Serial Number :CAB0533K3PPPart Number :73-5673-03Board Revision :A0Fab Version :03RMA Test History :00RMA Number :0-0-0-0RMA History :00Deviation Number :0-0Product Number :7300-NSE-100Top Assy. Part Number :68-1002-02Manufacturing Test Data :00 00 00 00 00 00 00 00Field Diagnostics Data :00 00 00 00 00 00 00 00Calibration Data :Minimum:0 dBmV, Maximum:0 dBmVCalibration values :EEPROM format version 4EEPROM contents (hex):0x00:04 FF 40 02 8C 41 02 00 C1 8B 43 41 42 30 35 330x10:33 4B 33 50 50 82 49 16 29 03 42 41 30 02 03 030x20:00 81 00 00 00 00 04 00 80 00 00 00 00 CB 94 370x30:33 30 30 2D 4E 53 45 2D 31 30 30 20 20 20 20 200x40:20 20 20 87 44 03 EA 02 C4 08 00 00 00 00 00 000x50:00 00 C5 08 00 00 00 00 00 00 00 00 C8 09 00 000x60:00 00 00 00 00 00 00 C7 7C F6 44 3F 30 00 00 000x70:00 00 00 00 00 00 00 00 00 06 72 64 1E 1C 37 260x80:07 08 64 32 28 37 26 00 00 00 00 00 00 00 00 000x90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xA0:00 00 00 FB BA FF FF FF FF FF FF FF FF FF FF FF0xB0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xC0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xD0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xE0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xF0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFFPGA information:Current NSE MB FPGA version :0.3IOS bundled NSE MB FPGA version :0.12Current NSE DB FPGA version :0.3IOS bundled NSE DB FPGA version :0.10Fault History Buffer:7300 Software (C7300-IS-M), Experimental Version 12.1(20011206:191841) [user-ws1 179]Compiled Tue 29-Jan-02 08:10 bySignal = 22, Code = 0x0, Uptime 00:00:48$0 :FFFFFFFF, AT :47001098, v0 :10020028, v1 :0000006Fa0 :A0000000, a1 :00000005, a2 :00000001, a3 :10020028t0 :00000028, t1 :3401E101, t2 :34018100, t3 :FFFF00FFt4 :40332E68, t5 :43204650, t6 :70646174, t7 :69707065s0 :FFFFFFFF, s1 :FFFFFFFF, s2 :FFFFFFFF, s3 :FFFFFFFFs4 :FFFFFFFF, s5 :FFFFFFFF, s6 :FFFFFFFF, s7 :FFFFFFFFt8 :00000000, t9 :00000000, k0 :3041D001, k1 :30410000gp :FFFFFFFF, sp :41AA8F20, s8 :FFFFFFFF, ra :4036B6A4EPC :4036B69C, SREG :3401E103, Cause :FFFFFFFFError EPC :FFFFFFFF, BadVaddr :FFFFFFFFROMMON Last Error Info:count:19, reason:resetpc:0x4020BFBC, error address:0x00000000Stack Trace:FP:0x00000000, PC:0x00000000FP:0x00000000, PC:0x00000000Shared Port Adapters on the Cisco 7304 Router: Example
The following is sample output from the show diag subslot command for a 4-Port 10/100 Fast Ethernet SPA located in the bottom subslot (1) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/1Subslot 4/1:Shared port adapter: SPA-4FE-7304, 4 portsInfo: hw-ver=0x100, sw-ver=0x0 fpga-ver=0x0State: okInsertion time: 23:20:42 agoBandwidth: 400000 kbpsEEPROM contents:Hardware Revision : 1.0Boot Time out : 0190PCB Serial Number : JAB073204G5Part Number : 73-8717-0373/68 Level Revision : 01Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Number : SPA-4FE-7304Product Version Id : V01Top Assy. Part Number : 68-2181-0173/68 Level Revision : A0CLEI Code : CNS9420AAABase MAC Address : 0000.0000.0000MAC Address block size : 1024Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 160000mW maxMode 1 : 0mWMode 2 : 0mWMode 3 : 0mWEEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 35 41 01 00 46 01 90 C1 8B 4A 41 420x10: 30 37 33 32 30 34 47 35 82 49 22 0D 03 8A 30 310x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00 000x30: 00 00 CB 94 53 50 41 2D 34 46 45 2D 37 33 30 340x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44 080x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32 300x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4 080x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00 000x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00 000x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 000xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 000x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 04 B0 B40x110: A0 8C 00 00 05 DC 64 46 32 00 00 07 08 64 46 320x120: 00 00 09 C4 64 46 32 00 00 0C E4 64 46 32 00 000x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 020x140: F2 A6 FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 000x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 000x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FPGA version:Software version : 04.17Hardware version : 04.17The following is sample output from the show diag subslot command for a 2-Port 10/100/1000 Gigabit Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/0Subslot 4/0:Shared port adapter: SPA-2GE-7304, 2 portsInfo: hw-ver=0x17, sw-ver=0x0 fpga-ver=0x0State: okInsertion time: 00:08:47 agoBandwidth: 2000000 kbpsEEPROM contents:Hardware Revision : 0.23Boot Time out : 0190PCB Serial Number : JAB073406YHPart Number : 73-8792-0273/68 Level Revision : 01Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Number : SPA-2GE-7304Product Version Id : V01Top Assy. Part Number : 68-2181-0173/68 Level Revision : A0CLEI Code : CNS9420AAABase MAC Address : 0000.0000.0000MAC Address block size : 1024Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 160000mW maxMode 1 : 0mWMode 2 : 0mWMode 3 : 0mWEEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 36 41 00 17 46 01 90 C1 8B 4A 41 420x10: 30 37 33 34 30 36 59 48 82 49 22 58 02 8A 30 310x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00 000x30: 00 00 CB 94 53 50 41 2D 32 47 45 2D 37 33 30 340x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44 080x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32 300x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4 080x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00 000x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00 000x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 000xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 000x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 03 E8 B40x110: A0 8C 37 26 05 DC 64 46 32 37 26 07 08 64 46 320x120: 37 26 09 C4 64 46 32 32 DD 0C E4 64 46 32 43 240x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 020x140: EF E2 FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 000x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 000x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FPGA version:Software version : 04.17Hardware version : 04.17Shared Port Adapter on a Cisco 12000 Series Router: Example
The following is sample output from the show diag subslot command for the 1-Port OC-192c/STM-64c POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port AdapterProduct Identifier (PID) : SPA-OC192POS-XFPVersion Identifier (VID) : V01PCB Serial Number : PRTA1304061Top Assy. Part Number : 68-2190-01Top Assy. Revision : A0Hardware Revision : 2.0CLEI Code : UNASSIGNEDInsertion Time : 00:00:10 (13:14:17 ago)Operational Status : okTable 12 describes the significant fields shown in the display.
The following is sample output from the show diag subslot details command for the 1-Port OC-192c/STM-64c POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1 detailsSUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port AdapterEEPROM version : 4Compatible Type : 0xFFController Type : 1100Hardware Revision : 2.0Boot Timeout : 400 msecsPCB Serial Number : PRTA1304061PCB Part Number : 73-8546-01PCB Revision : A0 Fab Version : 01RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Identifier (PID) : SPA-OC192POS-XFPVersion Identifier (VID) : V01Top Assy. Part Number : 68-2190-01Top Assy. Revision : A0 IDPROM Format Revision : 36System Clock Frequency : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00CLEI Code : UNASSIGNEDBase MAC Address : 00 00 00 00 00 00MAC Address block size : 0Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 11000 mWatts (Maximum)Environment Monitor Data : 03 30 04 B0 46 32 07 0846 32 09 C4 46 32 0C E446 32 13 88 46 32 07 0846 32 EB B0 50 3C 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 FE 02 F6 ACProcessor Label : 00 00 00 00 00 00 00Platform features : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00Asset ID :Asset Alias :Insertion Time : 00:00:10 (13:14:24 ago)Operational Status : okSPA Interface Processor on a Cisco 12000 Series Router: Example
The following is sample output from the show diag command for a SIP located in chassis slot 2 on a Cisco 12000 series router:
Router# show diag 2SLOT 2 (RP/LC 2 ): Modular 10G SPA Interface CardMAIN: type 149, 800-26270-01 rev 84Deviation: 0HW config: 0x00 SW key: 00-00-00PCA: 73-9607-01 rev 91 ver 1Design Release 1.0 S/N SAD08460678MBUS: Embedded AgentTest hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00DIAG: Test count: 0x00000000 Test results: 0x00000000FRU: Linecard/Module: 12000-SIP-650FRU: Linecard/Module: 12000-SIP-650Processor Memory: MEM-LC5-1024=(Non-Replaceable)Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)L3 Engine: 5 - ISE OC192 (10 Gbps)MBUS Agent Software version 1.114 (RAM) (ROM version is 3.4)ROM Monitor version 255.255Fabric Downloader version used 3.7 (ROM version is 255.255)Primary clock is CSC 1Board is analyzedBoard State is Line Card Enabled (IOS RUN )Insertion time: 1d00h (2d08h ago)Processor Memory size: 1073741824 bytesTX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytesRX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes0 crashes since restartSPA Information:subslot 2/0: SPA-OC192POS-XFP (0x44C), status is oksubslot 2/1: Emptysubslot 2/2: Emptysubslot 2/3: EmptyADSL HWICs: Example
The following is sample output from the show diag command for a Cisco 2811 router with HWIC-1ADSL installed in slot 1 and HWIC-1ADSLI installed in slot 2. Each HWIC has a daughtercard as part of its assembly. The command results below give the output from the HWIC followed by the output from its daughtercard.
Router# show diag 0
Slot 0:C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 portsPort adapter is analyzedPort adapter insertion time unknownOnboard VPN : v2.2.0EEPROM contents at hardware discovery:PCB Serial Number : FOC09052HHAHardware Revision : 2.0Top Assy. Part Number : 800-21849-02Board Revision : B0Deviation Number : 0Fab Version : 06RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Processor type : 87Hardware date code : 20050205Chassis Serial Number : FTX0908A0B0Chassis MAC Address : 0013.1ac2.2848MAC Address block size : 24CLEI Code : CNMJ7N0BRAProduct (FRU) Number : CISCO2811Part Number : 73-7214-09Version Identifier : NAEEPROM format version 4EEPROM contents (hex):0x00: 04 FF C1 8B 46 4F 43 30 39 30 35 32 48 48 41 400x10: 03 E7 41 02 00 C0 46 03 20 00 55 59 02 42 42 300x20: 88 00 00 00 00 02 06 03 00 81 00 00 00 00 04 000x30: 09 87 83 01 31 F1 1D C2 8B 46 54 58 30 39 30 380x40: 41 30 42 30 C3 06 00 13 1A C2 28 48 43 00 18 C60x50: 8A 43 4E 4D 4A 37 4E 30 42 52 41 CB 8F 43 49 530x60: 43 4F 32 38 31 31 20 20 20 20 20 20 82 49 1C 2E0x70: 09 89 20 20 4E 41 D9 02 40 C1 FF FF FF FF FF FFWIC Slot 1:ADSL over POTSHardware Revision : 7.0Top Assy. Part Number : 800-26247-01Board Revision : 01Deviation Number : 0Fab Version : 07PCB Serial Number : FHH093600D4RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Product (FRU) Number : HWIC-1ADSLVersion Identifier : V01CLEI Code :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 C8 41 07 00 C0 46 03 20 00 66 87 010x10: 42 30 31 88 00 00 00 00 02 07 C1 8B 46 48 48 300x20: 39 33 36 30 30 44 34 03 00 81 00 00 00 00 04 000x30: CB 94 48 57 49 43 2D 31 41 44 53 4C 20 20 20 200x40: 20 20 20 20 20 20 89 56 30 31 20 D9 02 40 C1 C60x50: 8A FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFEM Slot 0:ADSL over POTS non-removable daughtercardHardware Revision : 5.0Part Number : 73-9307-05Board Revision : 03Deviation Number : 0Fab Version : 05PCB Serial Number : FHH0936006ERMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Fab Part Number : 28-6607-05Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Connector Type : 01Version Identifier : V01Product (FRU) Number :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 7A 41 05 00 82 49 24 5B 05 42 30 330x10: 88 00 00 00 00 02 05 C1 8B 46 48 48 30 39 33 360x20: 30 30 36 45 03 00 81 00 00 00 00 04 00 85 1C 190x30: CF 05 C4 08 00 00 00 00 00 00 00 00 C5 08 00 000x40: 00 00 00 00 00 00 05 01 89 56 30 31 20 FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFWIC Slot 2:ADSL over ISDNHardware Revision : 7.0Top Assy. Part Number : 800-26248-01Board Revision : 01Deviation Number : 0Fab Version : 07PCB Serial Number : FHH093600DARMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Product (FRU) Number : HWIC-1ADSLIVersion Identifier : V01CLEI Code :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 C9 41 07 00 C0 46 03 20 00 66 88 010x10: 42 30 31 88 00 00 00 00 02 07 C1 8B 46 48 48 300x20: 39 33 36 30 30 44 41 03 00 81 00 00 00 00 04 000x30: CB 94 48 57 49 43 2D 31 41 44 53 4C 49 20 20 200x40: 20 20 20 20 20 20 89 56 30 31 20 D9 02 40 C1 C60x50: 8A FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFEM Slot 0:ADSL over ISDN non-removable daughtercardHardware Revision : 5.0Part Number : 73-9308-05Board Revision : 03Deviation Number : 0Fab Version : 05PCB Serial Number : FHH0936008MRMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Fab Part Number : 28-6607-05Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Connector Type : 01Version Identifier : V01Product (FRU) Number :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 7B 41 05 00 82 49 24 5C 05 42 30 330x10: 88 00 00 00 00 02 05 C1 8B 46 48 48 30 39 33 360x20: 30 30 38 4D 03 00 81 00 00 00 00 04 00 85 1C 190x30: CF 05 C4 08 00 00 00 00 00 00 00 00 C5 08 00 000x40: 00 00 00 00 00 00 05 01 89 56 30 31 20 FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFNME-AON-K9= Installed in a Cisco 3845: Example
The following is sample output of the show diag command for an integrated-service-engine port adapter in slot 2 on a Cisco 3845 router:
Slot 2:Integrated Service Engine Port adapter, 1 portPort adapter is analyzedPort adapter insertion time unknownEEPROM contents at hardware discovery:Hardware Revision : 1.0Top Assy. Part Number : 800-28152-01Board Revision : 03Deviation Number : 0Fab Version : 01PCB Serial Number : FOC101430NKRMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Version Identifier : NACLEI Code : TDBProduct (FRU) Number : NME-AON-K9EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 05 5B 41 01 00 C0 46 03 20 00 6D F8 010x10: 42 30 33 88 00 00 00 00 02 01 C1 8B 46 4F 43 310x20: 30 31 34 33 30 4E 4B 03 00 81 00 00 00 00 04 000x30: 89 4E 41 00 00 D9 02 40 C1 C6 8A 54 44 42 00 000x40: 00 00 00 00 00 CB 88 4E 4D 45 2D 52 56 50 4E FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Table 13 describes the significant fields shown in the display.
Related Commands
show interfaces
To display statistics for all interfaces configured on the router or access server, use the show interfaces command in privileged EXEC mode. The resulting output varies, depending on the network for which an interface has been configured.
Cisco 2500 Series, Cisco 2600 Series, Cisco 4700 Series, and Cisco 7000 Series
show interfaces [type interface-number] [first] [last] [accounting]
Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor
show interfaces [type slot/port] [accounting]
Cisco 7500 Series with Ports on VIPs
show interfaces [type slot/port-adapter/port]
Cisco 7600 Series
show interfaces [type interface-number | null interface-number | vlan vlan-id]
Channelized T3 Shared Port Adapters
show interfaces serial [slot/subslot/port/t1-num:channel-group]
Shared Port Adapters
show interfaces type [slot/subslot/port[/sub-int]]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Display Interpretation
The show interfaces command displays statistics for the network interfaces. The resulting display on the Cisco 7200 series routers shows the interface processors in slot order. If you add interface processors after booting the system, they will appear at the end of the list, in the order in which they were inserted.
Information About Specific Interfaces
The interface-number argument designates the module and port number. If you use the show interfaces command on the Cisco 7200 series routers without the slot/port arguments, information for all interface types will be shown. For example, if you type show interfaces you will receive information for all ethernet, serial, Token Ring, and FDDI interfaces. Only by adding the type slot/port argument can you specify a particular interface.
Cisco 7600 Series Routers
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 channels from 257 to 282 are internally allocated and are supported on the CSM and the FWSM only.
Statistics are collected on a per-VLAN basis for Layer 2-switched packets and Layer 3-switched packets. Statistics are available for both unicast and multicast traffic. The Layer 3-switched packet counts are available for both ingress and egress directions. The per-VLAN statistics are updated every 5 seconds.
In some cases, you might see a difference in the duplex mode that is displayed between the show interfaces command and the show running-config commands. In this case, the duplex mode that is displayed in the show interfaces command is the actual duplex mode that the interface is running. The show interfaces command shows the operating mode for an interface, while the show running-config command shows the configured mode for an interface.
If you do not enter any keywords, all counters for all modules are displayed.
Command Variations
You will use the show interfaces command frequently while configuring and monitoring devices. The various forms of the show interfaces commands are described in detail in the sections that follow.
Dialer Interfaces Configured for Binding
If you use the show interfaces command on dialer interfaces configured for binding, the display will report statistics on each physical interface bound to the dialer interface; see the following examples for more information.
Removed Interfaces
If you enter a show interfaces command for an interface type that has been removed from the router or access server, interface statistics will be displayed accompanied by the following text: "Hardware has been removed."
Weighted Fair Queueing Information
If you use the show interfaces command on a router or access server for which interfaces are configured to use weighted fair queueing through the fair-queue interface command, additional information is displayed. This information consists of the current and high-water mark number of flows.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, when a multilink PPP (MLPPP) interface is down/down, its default bandwidth rate is the sum of the serial interface bandwidths associated with the MLPPP interface.
In Cisco IOS Release 12.2(31)SB, the default bandwidth rate is 64 Kbps.
Examples
The following is sample output from the show interfaces command. Because your display will depend on the type and number of interface cards in your router or access server, only a portion of the display is shown.
Note
Router# show interfacesEthernet 0 is up, line protocol is upHardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)Internet address is 10.108.28.8, subnet mask is 255.255.255.0MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, ARP Timeout 4:00:00Last input 0:00:00, output 0:00:00, output hang neverLast clearing of "show interface" counters 0:00:00Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 2000 bits/sec, 4 packets/sec1127576 packets input, 447251251 bytes, 0 no bufferReceived 354125 broadcasts, 0 runts, 0 giants, 57186* throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort5332142 packets output, 496316039 bytes, 0 underruns0 output errors, 432 collisions, 0 interface resets, 0 restarts...Example with Custom Output Queueing
The following shows partial sample output when custom output queueing is enabled:
Router# show interfacesLast clearing of "show interface" counters 0:00:06Input queue: 0/75/0 (size/max/drops); Total output drops: 21Output queues: (queue #: size/max/drops)0: 14/20/14 1: 0/20/6 2: 0/20/0 3: 0/20/0 4: 0/20/0 5: 0/20/06: 0/20/0 7: 0/20/0 8: 0/20/0 9: 0/20/0 10: 0/20/0...When custom queueing is enabled, the drops accounted for in the output queues result from bandwidth limitation for the associated traffic and leads to queue length overflow. Total output drops include drops on all custom queues as well as the system queue. Fields are described with the Weighted Fair Queueing output in Table 14.
Example Including Weighted-Fair-Queueing Output
For each interface on the router or access server configured to use weighted fair queueing, the show interfaces command displays the information beginning with Input queue: in the following display:
Router# show interfacesEthernet 0 is up, line protocol is upHardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)Internet address is 10.108.28.8, subnet mask is 255.255.255.0MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, ARP Timeout 4:00:00Last input 0:00:00, output 0:00:00, output hang neverLast clearing of "show interface" counters 0:00:00Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 2000 bits/sec, 4 packets/sec1127576 packets input, 447251251 bytes, 0 no bufferReceived 354125 broadcasts, 0 runts, 0 giants, 57186* throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort5332142 packets output, 496316039 bytes, 0 underruns0 output errors, 432 collisions, 0 interface resets, 0 restarts Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Output queue: 7/64/0 (size/threshold/drops) Conversations 2/9 (active/max active)Table 14 describes the input queue and output queue fields shown in the preceding two displays.
Example with Accounting Option
To display the number of packets of each protocol type that have been sent through all configured interfaces, use the show interfaces accounting command. When you use the accounting option, only the accounting statistics are displayed.
Note
accounting option also shows the total bytes sent and received, including the MAC header. For
example, it totals the size of the Ethernet packet or the size of a packet that includes High-Level
Data Link Control (HDLC) encapsulation.
Per-packet accounting information is kept for the following protocols:
•
•
•
•
The routers use MOP packets to advertise their existence to Digital Equipment Corporation machines that use the MOP protocol. A router periodically broadcasts MOP packets to identify itself as a MOP host. This results in MOP packets being counted, even when DECnet is not being actively used.
•
•
•
•
•
•
•
•
•
Example with DWRED
The following is sample output from the show interfaces command when distributed weighted RED (DWRED) is enabled on an interface. Notice that the packet drop strategy is listed as "VIP-based weighted RED."
Router# show interfaces hssi 0/0/0Hssi0/0/0 is up, line protocol is upHardware is cyBus HSSIDescription: 45Mbps to R1Internet address is 10.200.14.250/30MTU 4470 bytes, BW 45045 Kbit, DLY 200 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)Last input 00:00:02, output 00:00:03, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoPacket Drop strategy: VIP-based weighted REDOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec1976 packets input, 131263 bytes, 0 no bufferReceived 1577 broadcasts, 0 runts, 0 giants0 parity4 input errors, 4 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort1939 packets output, 130910 bytes, 0 underruns0 output errors, 0 applique, 3 interface resets0 output buffers copied, 0 interrupts, 0 failuresExample with ALC
The following is sample output from the show interfaces command for serial interface 2 when ALC is enabled:
Router# show interfaces serial 2Serial2 is up, line protocol is upHardware is CD2430MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation ALC, loopback not setFull-duplex enabled.ascus in UP state: 42, 46ascus in DOWN state:ascus DISABLED:Last input never, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 3 interface resets0 output buffer failures, 0 output buffers swapped outDCD=down DSR=down DTR=down RTS=down CTS=downExample with SDLC
The following is sample output from the show interfaces command for a Synchronous Data Link Control (SDLC) primary interface supporting the SDLC function:
Router# show interfacesSerial 0 is up, line protocol is upHardware is MCI SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation SDLC-PRIMARY, loopback not setTimers (msec): poll pause 100 fair poll 500. Poll limit 1[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: noneSDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10largest token ring frame 2052]SDLC addr C1 state is CONNECTVS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0Poll: clear, Poll count: 0, chain: p: C1 n: C1SDLLC [largest SDLC frame: 265, XID: disabled]Last input 00:00:02, output 00:00:01, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 517 bits/sec, 30 packets/secFive minute output rate 672 bits/sec, 20 packets/sec357 packets input, 28382 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort926 packets output, 77274 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restarts2 carrier transitionsTable 15 shows the fields relevant to all SDLC connections.
Table 16 shows other data given for each SDLC secondary interface configured to be attached to this interface.
Sample show interfaces accounting Display
The following is sample output from the show interfaces accounting command:
Router# show interfaces accountingInterface TokenRing0 is disabledEthernet0Protocol Pkts In Chars In Pkts Out Chars OutIP 873171 735923409 34624 9644258Novell 163849 12361626 57143 4272468DEC MOP 0 0 1 77ARP 69618 4177080 1529 91740Interface Serial0 is disabledEthernet1Protocol Pkts In Chars In Pkts Out Chars OutIP 0 0 37 11845Novell 0 0 4591 275460DEC MOP 0 0 1 77ARP 0 0 7 420Interface Serial1 is disabledInterface Ethernet2 is disabledInterface Serial2 is disabledInterface Ethernet3 is disabledInterface Serial3 is disabledInterface Ethernet4 is disabledInterface Ethernet5 is disabledInterface Ethernet6 is disabledInterface Ethernet7 is disabledInterface Ethernet8 is disabledInterface Ethernet9 is disabledFddi0Protocol Pkts In Chars In Pkts Out Chars OutNovell 0 0 183 11163ARP 1 49 0 0When the output indicates that an interface is "disabled," the router has received excessive errors (over 5000 in a keepalive period).
Example with Flow-Based WRED
The following is sample output from the show interfaces command issued for the Serial interface 1 for which flow-based weighted RED (WRED) is enabled. The output shows that there are 8 active flow-based WRED flows, that the maximum number of flows active at any time is 9, and that the maximum number of possible flows configured for the interface is 16:
Router# show interfaces serial 1Serial1 is up, line protocol is upHardware is HD64570Internet address is 10.1.2.1/24MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,Reliability 255/255, txload 237/255, rxload 1/255Encapsulation HDLC, loopback not setKeepalive not setLast input 00:00:22, output 00:00:00, output hang neverLast clearing of "show interface" counters 00:17:58Input queue: 0/75/0 (size/max/drops); Total output drops: 2479Queueing strategy: random early detection(RED)flows (active/max active/max): 8/9/16mean queue depth: 27drops: class random tail min-th max-th mark-prob0 946 0 20 40 1/101 488 0 22 40 1/102 429 0 24 40 1/103 341 0 26 40 1/104 235 0 28 40 1/105 40 0 31 40 1/106 0 0 33 40 1/107 0 0 35 40 1/10rsvp 0 0 37 40 1/1030 second input rate 1000 bits/sec, 2 packets/sec30 second output rate 119000 bits/sec, 126 packets/sec1346 packets input, 83808 bytes, 0 no bufferReceived 12 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort84543 packets output, 9977642 bytes, 0 underruns0 output errors, 0 collisions, 6 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upExample with DWFQ
The following is sample output from the show interfaces command when distributed weighted fair queueing (DWFQ) is enabled on an interface. Notice that the queueing strategy is listed as "VIP-based fair queueing."
Router# show interfaces fastethernet 1/1/0Fast Ethernet 1/1/0 is up, line protocol is upHardware is cyBus Fast Ethernet Interface, address is 0007.f618.4448 (bia 00e0)Description: pkt input i/f for WRL tests (to pagent)Internet address is 10.0.2.70/24MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive not set, fdx, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input never, output 01:11:01, output hang neverLast clearing of "show interface" counters 01:12:31Queueing strategy: VIP-based fair queueingOutput queue 0/40, 0 drops; input queue 0/75, 0 drops30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 watchdog, 0 multicast0 input packets with dribble condition detected1 packets output, 60 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffers copied, 0 interrupts, 0 failuresExample with DNIS Binding
When the show interfaces command is issued on an unbound dialer interface, the output looks as follows:
Router# show interfaces dialer0Dialer0 is up (spoofing), line protocol is up (spoofing)Hardware is UnknownInternet address is 10.1.1.2/8MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 3/255Encapsulation PPP, loopback not setDTR is pulsed for 1 seconds on resetLast input 00:00:34, output never, output hang neverLast clearing of "show interface" counters 00:05:09Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 1000 bits/sec, 0 packets/sec18 packets input, 2579 bytes14 packets output, 5328 bytesBut when the show interfaces command is issued on a bound dialer interface, you will get an additional report that indicates the binding relationship. The output is shown here:
Router# show interfaces dialer0Dialer0 is up, line protocol is upHardware is UnknownInternet address is 10.1.1.2/8MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation PPP, loopback not setDTR is pulsed for 1 seconds on resetInterface is bound to BRI0:1Last input 00:00:38, output never, output hang neverLast clearing of "show interface" counters 00:05:36Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec38 packets input, 4659 bytes34 packets output, 9952 bytesBound to:BRI0:1 is up, line protocol is upHardware is BRIMTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation PPP, loopback not set, keepalive not setInterface is bound to Dialer0 (Encapsulation PPP)LCP Open, multilink OpenLast input 00:00:39, output 00:00:11, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec78 packets input, 9317 bytes, 0 no bufferReceived 65 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort93 packets output, 9864 bytes, 0 underruns0 output errors, 0 collisions, 7 interface resets0 output buffer failures, 0 output buffers swapped out4 carrier transitionsAt the end of the Dialer0 output, the show interfaces command is executed on each physical interface bound to it.
Example with BRI
In this example, the physical interface is the B1 channel of the BRI0 link. This example also illustrates that the output under the B channel keeps all hardware counts that are not displayed under any logical or virtual access interface. The line in the report that states "Interface is bound to Dialer0 (Encapsulation LAPB)" indicates that this B interface is bound to Dialer0 and the encapsulation running over this connection is LAPB, not PPP, which is the encapsulation configured on the D interface and inherited by the B channel.
Router# show interfaces bri0:1BRI0:1 is up, line protocol is upHardware is BRIMTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation PPP, loopback not set, keepalive not setInterface is bound to Dialer0 (Encapsulation LAPB)LCP Open, multilink OpenLast input 00:00:31, output 00:00:03, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 1 packets/sec110 packets input, 13994 bytes, 0 no bufferReceived 91 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort135 packets output, 14175 bytes, 0 underruns0 output errors, 0 collisions, 12 interface resets0 output buffer failures, 0 output buffers swapped out8 carrier transitionsAny protocol configuration and states should be displayed from the Dialer0 interface.
Example with a Fast Ethernet SPA on a Cisco 7304 Router
The following is sample output from the show interfaces fastethernet command for the second interface (port 1) in a 4-Port 10/100 Fast Ethernet SPA located in the bottom subslot (1) of the MSC that is installed in slot 2 on a Cisco 7304 router:
Router# show interfaces fastethernet 2/1/1FastEthernet2/1/1 is up, line protocol is upHardware is SPA-4FE-7304, address is 00b0.64ff.5d80 (bia 00b0.64ff.5d80)Internet address is 192.168.50.1/24MTU 9216 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full-duplex, 100Mb/s, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:22, output 00:00:02, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec5 packets input, 320 bytesReceived 1 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog0 input packets with dribble condition detected8 packets output, 529 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 babbles, 0 late collision, 0 deferred2 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outExample for an Interface with an Asymmetric Receiver and Transmitter Rates
Router# show interfaces e4/0Ethernet4/0 is up, line protocol is upHardware is AmdP2, address is 000b.bf30.f470 (bia 000b.bf30.f470)Internet address is 10.1.1.9/24MTU 1500 bytes, BW 10000 Kbit, RxBW 5000 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 254/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)ARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:00, output 00:00:01, output hang neverLast clearing of "show interface" counters 00:03:36Input queue: 34/75/0/819 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 7138000 bits/sec, 14870 packets/sec30 second output rate 0 bits/sec, 0 packets/sec3109298 packets input, 186557880 bytes, 0 no bufferReceived 217 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected22 packets output, 1320 bytes, 0 underruns11 output errors, 26 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outTable 17 describes the fields shown in the display.
Example with a Gigabit Ethernet SPA on a Cisco 7304 Router
The following is sample output from the show interfaces gigabitethernet command for the first interface (port 0) in a 2-Port 10/100/1000 Gigabit Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show interfaces gigabitethernet 4/0/0GigabitEthernet4/0/0 is up, line protocol is downHardware is SPA-2GE-7304, address is 00b0.64ff.5a80 (bia 00b0.64ff.5a80)MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Half-duplex, 1000Mb/s, link type is auto, media type is RJ45output flow-control is unsupported, input flow-control is unsupportedARP type: ARPA, ARP Timeout 04:00:00Last input never, output 00:00:09, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input109 packets output, 6540 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 babbles, 0 late collision, 0 deferred1 lost carrier, 0 no carrier, 0 PAUSE output0 output buffer failures, 0 output buffers swapped outExample with Gigabit Ethernet SPAs Configured as Primary and Backup Interfaces on a Cisco 7600 Router
The following examples show the additional lines included in the display when the command is issued on two Gigabit Ethernet interfaces that are configured as a primary interface (gi3/0/0) and as a backup interface (gi3/0/11) for the primary:
Router# show interfaces gigabitEthernet 3/0/0GigabitEthernet3/0/0 is up, line protocol is up (connected)Hardware is GigEther SPA, address is 0005.dc57.8800 (bia 0005.dc57.8800)Backup interface GigabitEthernet3/0/11, failure delay 0 sec, secondary disable delay 0 sec,...Router# show interfaces gigabitEthernet 3/0/11GigabitEthernet3/0/11 is standby mode, line protocol is down (disabled)...Table 18 describes the fields shown in the display for Gigabit Ethernet SPA interfaces.
Example with a POS SPA on a Cisco 7600 Series Router and Catalyst 6500 Series Switch
The following is sample output from the show interfaces pos command on a Cisco 7600 series router or Catalyst 6500 series switch for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot 4):
Router# show interfaces pos 4/3/0POS4/3/0 is up, line protocol is up (APS working - active)Hardware is Packet over SONETInternet address is 10.0.0.1/8MTU 4470 bytes, BW 622000 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation HDLC, crc 16, loopback not setKeepalive not setScramble disabledLast input 00:00:34, output 04:09:06, output hang neverLast clearing of "show interface" counters neverQueueing strategy:fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsAvailable Bandwidth 622000 kilobits/sec5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec782 packets input, 226563 bytes, 0 no bufferReceived 0 broadcasts, 1 runts, 0 giants, 0 throttles0 parity1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort271 packets output, 28140 bytes, 0 underruns0 output errors, 0 applique, 2 interface resets0 output buffer failures, 0 output buffers swapped out2 carrier transitionsTable 19 describes the significant fields shown in this display.
Example with a POS SPA on a Cisco 12000 Series Router
The following is sample output from the show interfaces pos command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):
Router# show interfaces pos 1/1/0POS1/1/0 is up, line protocol is upHardware is Packet over SONETInternet address is 10.41.41.2/24MTU 4470 bytes, BW 9952000 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation HDLC, crc 32, loopback not setKeepalive not setScramble enabledLast input 00:00:59, output 00:00:11, output hang neverLast clearing of "show interface" counters 00:00:14Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsAvailable Bandwidth 9582482 kilobits/sec5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 parity0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort1 packets output, 314 bytes, 0 underruns0 output errors, 0 applique, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsTable 19 describes the significant fields shown in this display.
Example with a POS SPA SDCC Interface on a Cisco 12000 Series Router
The following is sample output from the show interfaces sdcc command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):
Router# show interfaces sdcc 1/1/0SDCC1/1/0 is administratively down, line protocol is downHardware is SDCCMTU 1500 bytes, BW 192 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, crc 32, loopback not setKeepalive set (10 sec)Last input never, output never, output hang neverLast clearing of "show interface" counters 00:01:55Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsTable 20 describes the significant fields shown in these displays.
Example with a T3/E3 Shared Port Adapter
The following example shows the interface serial statistics on the first port of a T3/E3 SPA installed in subslot 0 of the SIP located in chassis slot 5.
Router# show interfaces serial 5/0/0Serial5/0/0 is up, line protocol is upHardware is SPA-4T3E3Internet address is 10.1.1.2/24MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,reliability 255/255, txload 234/255, rxload 234/255Encapsulation HDLC, crc 16, loopback not setKeepalive set (10 sec)Last input 00:00:05, output 00:00:00, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 40685000 bits/sec, 115624 packets/sec5 minute output rate 40685000 bits/sec, 115627 packets/sec4653081241 packets input, 204735493724 bytes, 0 no bufferReceived 4044 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 parity0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort4652915555 packets output, 204728203520 bytes, 0 underruns0 output errors, 0 applique, 4 interface resets0 output buffer failures, 0 output buffers swapped out2 carrier transitionsTable 21 describes the fields shown in the show interfaces serial output for a T3/E3 SPA.
Note
Example with a 1-Port 10-Gigabit Ethernet SPA on a Cisco 12000 Series Router
The following is sample output from the show interfaces tengigabitethernet command for the only interface (port 0) in a 1-Port 10 Gigabit Ethernet SPA located in the top subslot (0) of the carrier card that is installed in slot 7 on a Cisco 12000 series router:
Router# show interfaces tengigabitethernet 7/0/0TenGigabitEthernet7/0/0 is up, line protocol is up (connected)Hardware is TenGigEther SPA, address is 0000.0c00.0102 (bia 000f.342f.c340)Internet address is 10.1.1.2/24MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive not supportedFull-duplex, 10Gb/sinput flow-control is on, output flow-control is onARP type: ARPA, ARP Timeout 04:00:00Last input never, output 00:00:10, output hang neverLast clearing of "show interface" counters 20:24:30Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secL2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytesL3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcastL3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes237450882 packets input, 15340005588 bytes, 0 no bufferReceived 25 broadcasts (0 IP multicasts)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input0 input packets with dribble condition detected1676 packets output, 198290 bytes, 0 underruns0 output errors, 0 collisions, 4 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier, 0 PAUSE output0 output buffer failures, 0 output buffers swapped outTable 22 describes the fields shown in the display.
Displaying Traffic for a Specific Interface Example
This example shows how to display traffic for a specific interface:
Router# show interfaces GigabitEthernet9/5GigabitEthernet9/5 is up, line protocol is upHardware is C6k 1000Mb 802.3, address is 0001.64f8.3fa5 (bia 0001.64f8.3fa5)Internet address is 172.20.20.20/24MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full-duplex, 100Mb/sDual-mode port configured as RJ45ARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:00, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 1000 bits/sec, 2 packets/sec5 minute output rate 0 bits/sec, 0 packets/secL2 Switched: ucast: 8199 pkt, 1362060 bytes - mcast: 6980 pkt, 371952 bytesL3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcastL3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes300114 packets input, 27301436 bytes, 0 no bufferReceived 43458 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected15181 packets output, 1955836 bytes, 0 underruns0 output errors, 0 collisions, 3 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outRouter#This example shows how to display traffic for a FlexWAN module:
Router# show interfaces pos 6/1/0.1POS6/1/0.1 is up, line protocol is upHardware is Packet over SonetInternet address is 10.1.2.2/24MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation FRAME-RELAY <<<+++ no packets info after this lineArches#sh mod 6Mod Ports Card Type Model Serial No.--- ----- -------------------------------------- ------------------ -----------6 0 2 port adapter FlexWAN WS-X6182-2PA SAD04340JY3Mod MAC addresses Hw Fw Sw Status--- ---------------------------------- ------ ------------ ------------ -------6 0001.6412.a234 to 0001.6412.a273 1.3 12.2(2004022 12.2(2004022 OkMod Online Diag Status--- -------------------6 PassRouter#Related Commands
show interfaces virtual-access
To display status, traffic data, and configuration information about a specified virtual access interface, use the show interfaces virtual-access command in privileged EXEC mode.
show interfaces virtual-access number [configuration]
Syntax Description
number
Number of the virtual access interface.
configuration
(Optional) Restricts output to configuration information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To identify the number of the vty on which the virtual access interface was created, enter the show users EXEC command.
The counts of output packet bytes as reported by the L2TP access server (LAC) to the RADIUS server in the accounting record do not match those of a client. The following paragraphs describe how the accounting is done and how you can determine the correct packet byte counts.
Packet counts for client packets in the input path are as follows:
•
•
PPPoE payload length + PPP address&control bytes = = PPPoE payload length + 2
•
IP len + PPP encapbytes (4) = = PPPoE payload length + 2
Packet counts for client packets in the output path are as follows:
•
Size = PPPoE payload + PPPoE hdr (6) + Eth hdr (14) + SNAP hdr (10) + media hdr (4 for ATM)
•
PPP payload size + 4 bytes of PPP hdr
•
Accounting is done for PPPoE, PPPoA PTA and L2X as follows:
•
•
•
•
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer allows you to specify a virtual access interface (VAI) as viX.Y in the show pxf cpu queue and show interfaces commands. Instead, you must spell out the VAI as virtual-access.
For example, when you enter the following commands, the router accepts the commands:
Router# show pxf cpu queue virtual-access2.1Router# show interface virtual-access 2.1In releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the VAI. For example, the router accepts the following commands:
Router# show pxf cpu queue vi2.1Router# show interface vi2.1Examples
The following is sample output from the show interfaces virtual-access command:
Router# show interfaces virtual-access 3Virtual-Access3 is up, line protocol is upHardware is Virtual Access interfaceMTU 1500 bytes, BW 149760 Kbit, DLY 100000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation PPP, LCP Open, multilink OpenLink is a member of Multilink bundle Virtual-Access4PPPoATM vaccess, cloned from Virtual-Template1Vaccess status 0x44Bound to ATM4/0.10000 VCD:16, VPI:15, VCI:200, loopback not setDTR is pulsed for 5 seconds on resetLast input never, output never, output hang neverLast clearing of "show interface" counters 00:57:37Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue:0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec676 packets input, 12168 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort676 packets output, 10140 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsTable 23 describes the significant fields shown in the display.
Related Commands
interface virtual-template
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.
show policy-map
To display the configuration of all classes for a specified service policy map or of all classes for all existing policy maps, use the show policy-map command in user EXEC or privileged EXEC mode.
show policy-map [policy-map]
Syntax Description
policy-map
(Optional) Name of the service policy map whose complete configuration is to be displayed. The name can be a maximum of 40 characters.
Command Default
All existing policy map configurations are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show policy-map command displays the configuration of a policy map created using the policy-map command. You can use the show policy-map command to display all class configurations comprising any existing service policy map, whether or not that policy map has been attached to an interface. The command displays:
•
•
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the output of the show policy-map command is slightly different from previous releases when the policy is an hierarchical policy.
For example, in Cisco IOS Release 12.2(33)SB output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Bronzepolicy-map bronzeclass class-defaultshape average 34386000service-policy ChildIn Cisco IOS Release 12.2(31)SB, output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Goldpolicy-map GoldClass class-defaultAverage Rate Traffic Shapingcir 34386000 (bps)service-policy Child2In Cisco IOS Release 12.2(33)SB, the output from the show policy-map command displays police actions on separate lines as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P1prioritypolice percent 50 25 ms 0 msconform-action transmitexceed-action transmitviolate-action dropIn Cisco IOS Release 12.2(31)SB, the output from the show policy-map command displays police actions on one line as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P2prioritypolice percent 50 25 ms 0 ms conform-action transmit exceed-action transmit violate- action dropExamples
This section provides sample output from typical show policy-map commands. Depending upon the interface or platform in use and the options enabled (for example, Weighted Fair Queueing [WFQ]), the output you see may vary slightly from the ones shown below.
•
•
•
•
•
•
•
•
•
•
Weighted Fair Queueing: Example
The following example displays the contents of the service policy map called po1. In this example, WFQ is enabled.
Router# show policy-map po1Policy Map po1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class7 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class8 Bandwidth 937 (kbps) Max thresh 64 (packets)The following example displays the contents of all policy maps on the router. Again, WFQ is enabled.
Router# show policy-mapPolicy Map poH1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class7 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class8 Bandwidth 937 (kbps) Max thresh 64 (packets)Policy Map policy2 Weighted Fair Queueing Class class1 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 300 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 300 (kbps) Max thresh 64 (packets)Table 24 describes the significant fields shown in the display.
Frame Relay Voice-Adaptive Traffic-Shaping: Example
The following sample output for the show-policy map command indicates that Frame Relay voice-adaptive traffic-shaping is configured in the class-default class in the policy map "MQC-SHAPE-LLQ1" and that the deactivation timer is set to 30 seconds.
Router# show policy-mapPolicy Map VSD1Class VOICE1Strict PriorityBandwidth 10 (kbps) Burst 250 (Bytes)Class SIGNALS1Bandwidth 8 (kbps) Max Threshold 64 (packets)Class DATA1Bandwidth 15 (kbps) Max Threshold 64 (packets)Policy Map MQC-SHAPE-LLQ1Class class-defaultTraffic ShapingAverage Rate Traffic ShapingCIR 63000 (bps) Max. Buffers Limit 1000 (Packets)Adapt to 8000 (bps)Voice Adapt Deactivation Timer 30 Secservice-policy VSD1Table 25 describes the significant fields shown in the display.
Traffic Policing: Example
The following is sample output from the show policy-map command. This sample output displays the contents of a policy map called "policy1." In policy 1, traffic policing on the basis of a committed information rate (CIR) of 20 percent has been configured, and the bc and be have been specified in milliseconds. As part of the traffic policing configuration, optional conform, exceed, and violate actions have been specified.
Router# show policy-map policy1Policy Map policy1Class class1police cir percent 20 bc 300 ms pir percent 40 be 400 msconform-action transmitexceed-action dropviolate-action dropTable 26 describes the significant fields shown in the display.
Two-Rate Traffic Policing: Example
The following is sample output from the show policy-map command when two-rate traffic policing has been configured. As shown below, two-rate traffic policing has been configured for a class called "police." In turn, the class called police has been configured in a policy map called "policy1." Two-rate traffic policing has been configured to limit traffic to an average committed rate of 500 kbps and a peak rate of 1 Mbps.
Router(config)# class-map policeRouter(config-cmap)# match access-group 101Router(config-cmap)# policy-map policy1Router(config-pmap)# class policeRouter(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action transmit exceed-action set-prec-transmit 2 violate-action dropRouter(config-pmap-c)# interface serial3/0Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface serial3/0Router(config-if)# service-policy output policy1Router(config-if)# endThe following sample output shows the contents of the policy map called "policy1":Router# show policy-map policy1Policy Map policy1Class policepolice cir 500000 conform-burst 10000 pir 1000000 peak-burst 10000 conform-actiontransmit exceed-action set-prec-transmit 2 violate-action dropTraffic marked as conforming to the average committed rate (500 kbps) will be sent as is. Traffic marked as exceeding 500 kbps, but not exceeding 1 Mbps, will be marked with IP Precedence 2 and then sent. All traffic exceeding 1 Mbps will be dropped. The burst parameters are set to 10000 bytes.
Table 27 describes the significant fields shown in the display.
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 following sample output from the show policy-map command displays the configuration for a service policy called "police." In this service policy, traffic policing has been configured to allow multiple actions for packets marked as conforming to, exceeding, or violating the CIR or the PIR shown in the example.
Router# show policy-map policePolicy Map policeClass class-defaultpolice cir 1000000 bc 31250 pir 2000000 be 31250conform-action transmitexceed-action set-prec-transmit 4exceed-action set-frde-transmitviolate-action set-prec-transmit 2violate-action set-frde-transmitPackets conforming to the specified CIR (1000000 bps) are marked as conforming packets. These are transmitted unaltered.
Packets exceeding the specified CIR (but not the specified PIR, 2000000 bps) are marked as exceeding packets. For these packets, the IP Precedence level is set to 4, the discard eligibility (DE) bit is set to 1, and the packet is transmitted.
Packets exceeding the specified PIR are marked as violating packets. For these packets, the IP Precedence level is set to 2, the DE bit is set to 1, and the packet is transmitted.
Note
Table 28 describes the significant fields shown in the display.
Explicit Congestion Notification: Example
The following is sample output from the show policy-map command when the WRED—Explicit Congestion Notification (ECN) feature has been configured. The words "explicit congestion notification" (along with the ECN marking information) included in the output indicate that ECN has been enabled.
Router# show policy-mapPolicy Map pol1Class class-defaultWeighted Fair QueueingBandwidth 70 (%)exponential weight 9explicit congestion notificationclass min-threshold max-threshold mark-probability--------------------------------------------------------------------------------------------------------------------0 - - 1/101 - - 1/102 - - 1/103 - - 1/104 - - 1/105 - - 1/106 - - 1/107 - - 1/10rsvp - - 1/10Table 29 describes the significant fields shown in the display.
Modular QoS CLI (MQC) Unconditional Packet Discard: Example
The following example displays the contents of the policy map called "policy1." All the packets belonging to the class called "c1" are discarded.
Router# show policy-map policy1Policy Map policy1Class c1dropTable 30 describes the significant fields shown in the display.
Percentage-Based Policing and Shaping: Example
The following example displays the contents of two service policy maps—one called "policy1" and one called "policy2." In policy1, traffic policing based on a CIR of 50 percent has been configured. In policy 2, traffic shaping based on an average rate of 35 percent has been configured.
Router# show policy-map policy1Policy Map policy1 class class1 police cir percent 50Router# show policy-map policy2Policy Map policy2 class class2 shape average percent 35The following example displays the contents of the service policy map called "po1":
Router# show policy-map po1Policy Map po1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3
Bandwidth 937 (kbps) Max thresh 64 (packets)
Class class4
Bandwidth 937 (kbps) Max thresh 64 (packets)
The following example displays the contents of all policy maps on the router:Router# show policy-mapPolicy Map poH1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Policy Map policy2 Weighted Fair Queueing Class class1 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 300 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 300 (kbps) Max thresh 64 (packets)Table 31 describes the significant fields shown in the display.
Enhanced Packet Marking: Example
The following sample output from the show policy-map command displays the configuration for policy maps called "policy1" and "policy2".
In "policy1", a table map called "table-map-cos1" has been configured to determine the precedence based on the class of service (CoS) value. Policy map "policy 1" converts and propagates the packet markings defined in the table map called "table-map-cos1".
The following sample output from the show policy-map command displays the configuration for service polices called "policy1" and "policy2". In "policy1", a table map called "table-map1" has been configured to determine the precedence according to the CoS value. In "policy2", a table map called "table-map2" has been configured to determine the CoS value according to the precedence value.
Router# show policy-map policy1Policy Map policy1Class class-defaultset precedence cos table table-map1Router# show policy-map policy2Policy Map policy2Class class-defaultset cos precedence table table-map2Table 32 describes the fields shown in the display.
Bandwidth-Remaining Ratio: Example
The following sample output for the show policy-map command indicates that the class-default class of the policy map named vlan10_policy has a bandwidth-remaining ratio of 10. When congestion occurs, the scheduler allocates class-default traffic 10 times the unused bandwidth allocated in relation to other subinterfaces.
Router# show policy-map vlan10_policyPolicy Map vlan10_policyClass class-defaultAverage Rate Traffic Shapingcir 1000000 (bps)bandwidth remaining ratio 10service-policy child_policyTable 33 describes the fields shown in the display.
ATM Overhead Accounting: Example
The following sample output for the show policy-map command indicates that ATM overhead accounting is enabled for the class-default class. The BRAS-DSLAM encapsulation is dot1q and the subscriber encapsulation is snap-rbe for the AAL5 service.
Policy Map unit-testClass class-defaultAverage Rate Traffic Shapingcir 10% account dot1q aal5 snap-rbeTable 34 describes the significant fields shown in the display.
Tunnel Marking: Example
In this sample output of the show policy-map command, the character string "ip precedence tunnel 4" indicates that tunnel marking (either L2TPv3 or GRE) has been configured to set the IP precedence value to 4 in the header of a tunneled packet.
Note
Router# show policy-mapPolicy Map TUNNEL_MARKINGClass MATCH_FRDEset ip precedence tunnel 4Table 35 describes the fields shown in the display.
Related Commands
show pxf cpu ipv6
To display Parallel eXpress Forwarding (PXF) IPv6 statistics, use the show pxf cpu ipv6 command in privileged EXEC mode.
show pxf cpu ipv6 [ipv6: address [prefix] | acl-prefixes | hash | summary]
Cisco 10000 Series Router
show pxf cpu ipv6 [acl-prefixes | address | hash | summary | table | vrf ]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cisco 10000 Series Router
In Cisco IOS Release 12.2(33)SB, the show pxf cpu ipv6 table command displays the global table, but does not display the leafs that correspond to the IPv6 prefixes ::1/128 (Loopback) and ::/128 (All Zero). The microcode checks for these prefixes.
The show pxf cpu ipv6 table command replaces the show pxf cpu ipv6 command in Cisco IOS Release 12.2(31)SB.
Examples
The following example shows the PXF IPv6 statistics:
Router# show pxf cpu ipv6Mtrie Leaf Data: Prefix/LengthLeaf prefix ::/0,ACL Index = 0Leaf elt_addr: 0x70D20001 SW_OBJ_FIB_ENTRY: 0x20A6E404 acl_index: 0Refcount: 514 Flags: 0x2 Parent: NoneFirst Covered: NoneRight Peer: None========================================0 routes in Mtrie with less specific overlapping parent routeHash Table Leaf Data: Prefix/LengthLeaf prefix ::1/128,ACL Index = 0Leaf elt_addr: 0x70D20011 SW_OBJ_FIB_ENTRY: 0x0 acl_index: 0128-bit Table Hash Value: 0xC7F7Refcount: 3 Flags: 0x2 Parent: NoneFirst Covered: NoneRight Peer: NoneLeaf prefix ::/128,ACL Index = 0Leaf elt_addr: 0x70D20009 SW_OBJ_FIB_ENTRY: 0x0 acl_index: 0128-bit Table Hash Value: 0xC2719Refcount: 3 Flags: 0x2 Parent: NoneFirst Covered: NoneRight Peer: None========================================0 routes in Hash Table with less specific overlapping parent routeRelated Commands
show pxf cpu queue
To display parallel express forwarding (PXF) queueing and link queue statistics, use the show pxf cpu queue command in privileged EXEC mode.
show pxf cpu queue [interface | QID | summary]
Cisco uBR10012 Universal Broadband Router
show pxf cpu queue [interface | QID]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
When neither the interface or QID is specified, the command displays queuing statistics for the route processors (RPs).
Cisco 10000 Series Router
The Cisco 10000 series router high-speed interfaces work efficiently to spread traffic flows equally over the queues. However, using single traffic streams in a laboratory environment might result in less-than-expected performance. To ensure accurate test results, test the throughput of the Gigabit Ethernet, OC-48 POS, or ATM uplink with multiple source or destination addresses. To determine if traffic is being properly distributed, use the show pxf cpu queue command.
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer allows you to specify a virtual access interface (VAI) as viX.Y in the show pxf cpu queue command. Instead, you must spell out the VAI as virtual-access.
For example, the router accepts the following command:
Router# show pxf cpu queue virtual-access2.1In releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the VAI. For example, the router accepts the following command:
Router# show pxf cpu queue vi2.1In Cisco IOS Release 12.2(33)SB and later releases, the output from the show pxf cpu queue interface summary command displays only the physical interface and the number of logical links. The output does not display the number of priority queues, class queues, and so on. This modification applies to the PRE3 and PRE4.
Cisco uBR10012 Universal Broadband Router
If dynamic bandwidth sharing (DBS) is enabled, the link queue information that is displayed refers to the specific type of interface that is configured—modular cable or wideband cable. The summary keyword option is not supported for the Cisco uBR10012 universal broadbandrRouter for wideband cable or modular cable interfaces. The ATM interface output is not available for this router.
See Table 1 for descriptions of the interface keyword fields.
Examples
The following example shows PXF queueing statistics for an ATM interface when a QID is not specified. The sample output includes the dropped and dequeued packets for the VCs, and for classes associated with sessions that inherit queues from VCs.
Router# show pxf cpu queue atm 5/0/2VCCI 2517: ATM non-aggregated VC 1/229, VCD 1, Handle 1, Rate 500 kbpsVCCI/ClassID ClassName QID Length/Max Res Dequeues Drops0 2517/0 class-default 269 0/4096 11 3 00 2517/31 pak-priority 268 0/32 11 4 0Queues Owned but Unused by VC (inheritable by sessions)ClassID ClassName QID Length/Max Res Dequeues Drops0 class-default 275 0/32 11 100 031 pak-priority 268 0/32 11 4 0VCCI 2517: ATM non-aggregated VC 1/233, VCD 4, Handle 4, Rate 50 kbpsVCCI/ClassID ClassName QID Length/Max Res Dequeues Drops0 2517/0 class-default 269 0/4096 11 3 00 2517/31 pak-priority 268 0/32 11 4 0Queues Owned but Unused by VC (inheritable by sessions)ClassID ClassName QID Length/Max Res Dequeues Drops0 class-default 274 0/32 11 0 031 pak-priority 268 0/32 11 4 0VCCI 2520: ATM non-aggregated VC 1/232, VCD 3, Handle 3, Rate 500 kbpsVCCI/ClassID ClassName QID Length/Max Res Dequeues Drops0 2520/0 class-default 273 0/32 11 0 00 2520/31 pak-priority 268 0/32 11 4 0VCCI 2519: ATM non-aggregated VC 1/231, VCD 2, Handle 2, Rate 500 kbpsVCCI/ClassID ClassName QID Length/Max Res Dequeues Drops0 2519/0 class-default 272 0/32 11 0 00 2519/31 pak-priority 268 0/32 11 4 0The following example displays PXF queuing statistics for QID 267:
Router# show pxf cpu queue 267ID : 267Priority : LoCIR (in-use/configured) : 0/65535EIR (in-use/configured) : 0/0MIR (in-use/configured) : 0/65535Maximum Utilization configured : noLink : 2Flowbit (period/offset) : 32768/32768Burst Size : 1024 bytesBandwidth : 133920 KbpsChannel : 0Packet Descriptor Base : 0x00000100ML Index : 0Length/Average/Alloc : 0/0/32Enqueues (packets/octets) : 293352/9280610Dequeues (packets/octets) : 293352/9280610Drops (tail/random/max_threshold) : 0/0/0Drops (no_pkt_handle/buffer_low) : 0/0WRED (weight/avg_smaller) : 0/0WRED (next qid/drop factor) : 0/0WRED (min_threshold/max_threshold/scale/slope):precedence 0 : 0/0/0/0precedence 1 : 0/0/0/0precedence 2 : 0/0/0/0precedence 3 : 0/0/0/0precedence 4 : 0/0/0/0precedence 5 : 0/0/0/0precedence 6 : 0/0/0/0precedence 7 : 0/0/0/0Cisco uBR10012 Universal Broadband Router
The following examples show link queue information for specific wideband cable and modular cable interfaces when dynamic bandwidth sharing is enabled.
Modular Cable Interface
Router(config)# interface modular-cable 1/0/0:1...Router(config-if)# cable dynamic-bw-sharing...Router# show pxf cpu queue modular-cable 1/0/0:1Link Queues :QID CIR(act/conf) EIR MIR RF Chan. Status420 19661/19661 1/1 65535/65535 0 InactiveWideband Cable Interface
Router(config)# interface wideband-cable 1/0/0:0...Router(config-if)# cable dynamic-bw-sharing...Router# show pxf cpu queue wideband-cable 1/0/0:0Link Queues :QID CIR(act/conf) EIR MIR RF Chan. Status419 32768/32768 1/1 65535/65535 0 Inactive566 19661/19661 1/1 65535/65535 1 InactiveThe following example shows service flow queue information for modular cable interfaces.
Router# show pxf cpu queue modular-cable 1/2/0:0Cable Interface Queues:QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131147 0/255 190 0 0 1/240 0 58131148 0/255 33820 0 0 1/10000 0 32824Cable Service Flow Queues:* Best Effort QueuesQID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131241 0/255 0 0 0 1/240 0 32881* CIR QueuesQID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)2049 254/255 131018 485751 99 1/1920 0 32880* Low Latency QueuesQID Len/Max Dequeues TailDropsRelated Commands
show pxf cpu statistics
To display Parallel eXpress Forwarding (PXF) CPU statistics, use the show pxf cpu statistics command in privileged EXEC mode.
show pxf cpu statistics [atom | backwalk | clear | diversion | drop [interface | vcci] | ip | ipv6 | l2tp | mlp | qos [interface] | queue | rx [vcci] | security | arp-filter | drl [ cable-wan-ip | wan-non-ip ]]
Cisco 10000 Series Router
show pxf cpu statistics diversion [ pxf [interface {interface | vcci}] | top number]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Cisco 10000 Series Router Usage Guidelines
•
•
•
•
•
Examples
The following example shows PXF queueing counters information. These are aggregate counters for all interfaces. The Total column is the total for all columns.
Note
If you are troubleshooting overall PXF throughput issues, look at the High Next Time, Low Next Time, High Wheel Slot, and Low Wheel Slot counters.
Router# show pxf cpu statistics queueColumn 6 Enqueue/Dequeue Counters by Rows:dbg Counters 0 1 2 3 4 5 6 7 Total============= ========== ========== ========== ========== ========== ========== ========== ========== ==========enq_pkt 0x0000FD9B 0x0000FC77 0x0000FE4A 0x0000FF81 0x0000FC53 0x0000FD2E 0x0000FF19 0x0000FDDE 0x0007EE55tail_drop_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000deq_pkt 0x0000FD47 0x0000FEF2 0x0000FCB3 0x0000FF65 0x0000FCE7 0x0000FC45 0x0000FEE7 0x0000FDF1 0x0007EE55deq_vtp_req 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000deq_flow_off 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000deq_ocq_off 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000enqdeq_conflict 0x0000003A 0x00000043 0x0000004A 0x00000039 0x0000003A 0x0000004F 0x00000036 0x00000031 0x000001F0bndl_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000frag_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg_frag_drop 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg_bndl_sem 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000context_inhibit 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000bfifo_enq_fail 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg1 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg2 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg3 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000dbg6 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000dbg7 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00Column 7 Rescheduling State Counters by Rows:dbg Counters 0 1 2 3 4 5 6 7 Total============= ========== ========== ========== ========== ========== ========== ========== ========== ==========High Next Time 0x524E1100 0x524E1140 0x524E1140 0x524E1180 0x524E11C0 0x524E11C0 0x524E1200 0x524E1240 -Low Next Time 0x524E1100 0x524E1140 0x524E1140 0x524E1180 0x524E11C0 0x524E1200 0x524E1200 0x524E1240 -High Wheel Slot 0x00000844 0x00000845 0x00000846 0x00000846 0x00000847 0x00000848 0x00000848 0x00000849 -Low Wheel Slot 0x00000844 0x00000845 0x00000846 0x00000846 0x00000847 0x00000848 0x00000848 0x00000849 -DEQ_WHEEL 0x0001F5D0 0x0001F4BD 0x0001F56B 0x0001F6BF 0x0001F396 0x0001F3E8 0x0001F6BF 0x0001F4A7 0x000FA99BDQ-lock Fails 0x0000039F 0x000003FD 0x000003B2 0x000003E1 0x000003CB 0x000003E2 0x000003FD 0x000003CD 0x00001EA6TW ENQ Fails 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000Q_SCHED 0x0000FACD 0x0000FC6B 0x0000FA38 0x0000FCE4 0x0000FA66 0x0000F994 0x0000FC62 0x0000FB8B 0x0007DA3BFAST_SCHED 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000Q_DEACT 0x0000FB03 0x0000F852 0x0000FB33 0x0000F9DB 0x0000F930 0x0000FA54 0x0000FA5D 0x0000F91C 0x0007CF60Q_ACTIVATE 0x0000F9B6 0x0000F8D4 0x0000FA6C 0x0000FBA9 0x0000F87E 0x0000F95B 0x0000FB0A 0x0000F9DE 0x0007CF60Q_CHANGE 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000DEBUG1 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000DEBUG2 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000DEBUG3 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000DEBUG4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000DEBUG5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000Table 37 describes the significant fields shown in the display.
The following example displays PXF L2TP packet statistics.
Note
Router# show pxf cpu statistics l2tpLAC Switching Global Debug Statistics:PPP Packets 51648PPP Control Packets 51647PPP Data Packets 1Not IPv4 Packets 1IP Short Hdr Packets 1IP Valid Packets 0IP Invalid Packets 1DF Cleared Packets 0Path MTU Packets 0No Path MTU Packets 0Within PMTU Packets 0Fraggable Packets 0PMTU Pass Packets 0PMTU Fail Packets 0Encapped Packets 51648L2TP Classification Global Debug Statistics:LAC or Multihop Packets 151341Multihop Packets 0PPP Control Packets 51650PPP Data Packets 99691PPP Station Packets 151341The following example displays match statistics for the police_test policy on an ATM interface. The Classmap Index differentiates classes within a policy while the Match Number differentiates match statements within a class.
Router# show pxf cpu statistics qos atm 6/0/0.81801Classmap Match Pkts BytesIndex Number Matched Matched------------ ----------- ------------ ----------police_test (Output) service-policy :police_class (0) 0 0 01 0 02 0 03 0 0class-default (1) 0 0 0Cisco 10000 Series Router
The following example displays the top 10 packet types diverted to the RP. The output displays the top punters by interface and by Layer 2 packet flow.
Router# show pxf cpu statistics diversion top 10Top 10 punters by interface are:Rate (pps) Packets (diverted/dropped) vcci Interface1 10/0 2606 Virtual-Access2.1Last diverted packet type is none.Top 10 punters by Layer 2 flow are:Rate (pps) Packets (diverted/dropped) Interface Layer 2 info1 15/0 ATM2/0/3 vpi 128/vci 4096/vcci 2591Last diverted packet type is oam_f4.1 15/0 ATM2/0/3 vpi 128/vci 4096/vcci 2593Last diverted packet type is oam_f4.Related Commands
platform c10k divert- policer
Configures the rate and burst size of the divert-policer.
show pxf statistics
Displays a summary of statistics in the PXF.
show vpdn tunnel
To display information about active Layer 2 tunnels for a virtual private dialup network (VPDN), use the show vpdn tunnel command in privileged EXEC mode.
show vpdn tunnel [l2f | l2tp | pptp] [all [filter] | packets [filter] | state [filter] | summary [filter] | transport [filter]]
Syntax Description
l2f
(Optional) Specifies that only information about Layer 2 Forwarding (L2F) tunnels will be displayed.
l2tp
(Optional) Specifies that only information about Layer 2 Tunnel Protocol (L2TP) tunnels will be displayed.
pptp
(Optional) Specifies that only information about Point-to-Point Tunnel Protocol (PPTP) tunnels will be displayed.
all
(Optional) Displays summary information about all active tunnels.
filter
(Optional) One of the filter parameters defined in Table 38.
packets
(Optional) Displays packet numbers and packet byte information.
state
(Optional) Displays state information for a tunnel.
summary
(Optional) Displays a summary of tunnel information.
transport
(Optional) Displays tunnel transport information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show vpdn tunnel command to display detailed information about L2TP, L2F, and PPTP VPDN tunnels.
Table 38 defines the filter parameters available to refine the output of the show vpdn tunnel command. You may use any one of the filter parameters in place of the filter argument.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the show vpdn tunnel summary command no longer displays the active PPPoE sessions. Instead, use the show pppoe sessions command to display the active sessions.
In Cisco IOS Release 12.2(31)SB, the show vpdn tunnel summary command does display the active PPPoE sessions.
Examples
The following is sample output from the show vpdn tunnel command for L2F and L2TP sessions:
Router# show vpdn tunnelL2TP Tunnel Information (Total tunnels=1 sessions=1)LocID RemID Remote Name State Remote Address Port Sessions2 10 router1 est 172.21.9.13 1701 1L2F TunnelNAS CLID HGW CLID NAS Name HGW Name State9 1 nas1 HGW1 open172.21.9.4 172.21.9.232%No active PPTP tunnelsTable 39 describes the significant fields shown in the display.
The following example shows L2TP tunnel activity, including information about the L2TP congestion avoidance:
Router# show vpdn tunnel l2tp allL2TP Tunnel Information Total tunnels 1 sessions 1Tunnel id 30597 is up, remote id is 45078, 1 active sessionsTunnel state is established, time since change 00:08:27Tunnel transport is UDP (17)Remote tunnel name is LAC1Internet Address 172.18.184.230, port 1701Local tunnel name is LNS1Internet Address 172.18.184.231, port 1701Tunnel domain unknownVPDN group for tunnel is 1L2TP class for tunnel is4 packets sent, 3 received194 bytes sent, 42 receivedLast clearing of "show vpdn" counters neverControl Ns 2, Nr 4Local RWS 500, Remote RWS 500Control channel Congestion Control is enabledCongestion Window size, Cwnd 3Slow Start threshold, Ssthresh 500Mode of operation is Slow StartTunnel PMTU checking disabledRetransmission time 1, max 2 secondsUnsent queuesize 0, max 0Resend queuesize 0, max 1Total resends 0, ZLB ACKs sent 2Current nosession queue check 0 of 5Retransmit time distribution: 0 0 0 0 0 0 0 0 0Sessions disconnected due to lack of resources 0Control message authentication is disabledTable 40 describes the significant fields shown in the display.
Related Commands
snmp trap link-status
To enable Simple Network Management Protocol (SNMP) link trap generation, use the snmp trap link-status command in either interface configuration mode or service instance configuration mode. To disable SNMP link traps, use the no form of this command.
snmp trap link-status [permit duplicates]
no snmp trap link-status [permit duplicates]
Syntax Description
.
Command Default
SNMP link traps are sent when an interface goes up or down.
Command Modes
Interface configuration (config-if)
Service instance configuration (config-if-srv)Command History
Usage Guidelines
By default, SNMP link traps are sent when an interface goes up or down. For interfaces expected to go up and down during normal usage, such as ISDN interfaces, the output generated by these traps may not be useful. The no form of this command disables these traps.
The permit and duplicates keywords are used together and cannot be used individually. Use the permit duplicates keyword pair when an interface is not generating SNMP linkup traps, linkdown traps, or both. When the snmp trap link-status permit duplicates command is configured, more than one trap may be sent for the same linkup or linkdown transition.
The permit duplicates keyword pair does not guarantee that SNMP link traps will be generated nor should configuring these keywords be required to receive traps.
By default, in service instance configuration mode SNMP link traps are not sent. Also, the permit duplicates keyword pair is not available in service instance configuration mode.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the virtual-template snmp command has a new default configuration. Instead of being enabled by default, no virtual-template snmp is the default configuration. This setting enhances scaling and prevents large numbers of entries in the MIB ifTable, thereby avoiding CPU Hog messages as SNMP uses the interfaces MIB and other related MIBs.
If you configure the no virtual-template snmp command, the router no longer accepts the snmp trap link-status command under a virtual-template interface. Instead, the router displays a configuration error message such as the following:
Router(config)# interface virtual-template 1Router(config-if)# snmp trap link-status%Unable set link-status enable/disable for interfaceIf your configuration already has the snmp trap link-status command configured under a virtual-template interface and you upgrade to Cisco IOS Release 12.2(33)SB, the configuration error occurs when the router reloads even though the virtual template interface is already registered in the interfaces MIB.
Examples
The following example shows how to disable SNMP link traps related to the ISDN BRI 0 interface:
Router(config)# interface bri 0Router(config-if)# no snmp trap link-statusThe following example shows how to enable SNMP link traps for service instance 50 on Ethernet interface 0/1:
Router(config)# interface ethernet 0/1Router(config-if)# service instance 50 ethernetRouter(config-if-srv)# snmp trap link-status
Router(config-if-srv)#exitRelated Commands
virtual-template snmp
Allows virtual access interfaces to register with SNMP when they are created or reused.
virtual-template
To specify which virtual template will be used to clone virtual access interfaces, use the virtual-template command in VPDN group configuration mode. To remove the virtual template from a virtual private dial-up network (VPDN) group, use the no form of this command.
virtual-template template-number
no virtual-template
Syntax Description
template-number
Number of the virtual template that will be used to clone virtual access interfaces.
Defaults
No virtual template is enabled.
Command Modes
VPDN group configuration (config-vpdn)
Command History
Usage Guidelines
You must first enable a tunneling protocol on the VPDN group using the protocol (VPDN) command before you can enable the virtual-template command. Removing or modifying the protocol command will remove the virtual-template command from the VPDN group.
Each VPDN group can clone only virtual access interfaces using one virtual template. If you enter a second virtual-template command on a VPDN group, it will replace the first virtual-template command.
Table 41 lists the VPDN group commands under which the virtual-template command can be entered. Entering the VPDN group command starts VPDN group configuration mode. The table includes the command-line prompt for the VPDN group configuration mode and the type of service configured.
When the virtual-template command is entered under a request-dialout VPDN subgroup, IP and other per-user attributes can be applied to an L2TP dial-out session from an LNS. Before this command was enhanced, IP per-user configurations from authentication, authorization, and accounting (AAA) servers were not supported; the IP configuration would come from the dialer interface defined on the router.
The enhanced virtual-template command works in a way similar to configuring virtual profiles and L2TP dial-in. The L2TP virtual access interface is first cloned from the virtual template, which means that configurations from the virtual template interface will be applied to the L2TP virtual access interface. After authentication, the AAA per-user configuration is applied to the virtual access interface. Because AAA per-user attributes are applied only after the user has been authenticated, the LNS must be configured to authenticate the dial-out user (configuration authentication is needed for this command).
With the enhanced virtual-template command, all software components can now use the configuration present on the virtual access interface rather than what is present on the dialer interface. For example, IP Control Protocol (IPCP) address negotiation uses the local address of the virtual access interface as the router address while negotiating with the peer.
Cisco 10000 Series Router Usage Guidelines
In Cisco IOS Release 12.2(33)SB, the virtual-template snmp command has a new default configuration. Instead of being enabled by default, no virtual-template snmp is the default configuration. This setting enhances scaling and prevents large numbers of entries in the MIB ifTable, thereby avoiding CPU Hog messages as SNMP uses the interfaces MIB and other related MIBs.
If you configure the no virtual-template snmp command, the router no longer accepts the snmp trap link-status command under a virtual-template interface. Instead, the router displays a configuration error message such as the following:
Router(config)# interface virtual-template 1Router(config-if)# snmp trap link-status%Unable set link-status enable/disable for interfaceIf your configuration already has the snmp trap link-status command configured under a virtual-template interface and you upgrade to Cisco IOS Release 12.2(33)SB, the configuration error occurs when the router reloads even though the virtual template interface is already registered in the interfaces MIB.
Examples
The following example enables the LNS to accept an L2TP tunnel from an L2TP access concentrator (LAC) named LAC2. A virtual access interface will be cloned from virtual template 1.
vpdn-group 1accept-dialinprotocol l2tpvirtual-template 1terminate-from hostname LAC2The following example enables PPPoE on ATM to accept dial-in PPPoE sessions. A virtual access interface for the PPP session is cloned from virtual template 1.
vpdn-group 1accept-dialinprotocol pppoevirtual-template 1The following partial example shows how to configure an LNS to support IP per-user configurations from a AAA server:
!vpdn enablevpdn search-order domain!vpdn-group 1...request-dialoutprotocol l2tprotary-group 1virtual-template 1initiate-to ip 10.0.1.194.2local name lnsl2tp tunnel password 7094F3$!5^3source-ip 10.0.194.53!The previous configuration requires a AAA profile such as the following example to specify the per-user attributes:
5300-Router1-out Password = "cisco"Service-Type = Outboundcisco-avpair = "outbound:dial-number=5550121"7200-Router1-1 Password = "cisco"Service-Type = Outboundcisco-avpair = "ip:route=10.17.17.1 255.255.255.255 Dialer1 100 name 5300-Router1"5300-Router1 Password = "cisco"Service-Type = FramedFramed-Protocol = PPPcisco-avpair = "lcp:interface-config=ip unnumbered loopback 0"cisco-avpair = "ip:outacl#1=deny ip host 10.5.5.5 any log"cisco-avpair = "ip:outacl#2=permit ip any any"cisco-avpair = "ip:inacl#1=deny ip host 10.5.5.5 any log"cisco-avpair = "ip:inacl#2=permit ip any any"cisco-avpair = "multilink:min-links=2"Framed-Route = "10.5.5.6/32 Ethernet4/0"Framed-Route = "10.5.5.5/32 Ethernet4/0"Idle-Timeout = 100Related Commands
vpdn enable
To enable virtual private dialup networking (VPDN) on the router and inform the router to look for tunnel definitions in a local database and on a remote authorization server (home gateway), if one is present, use the vpdn enable command in global configuration mode. To disable, use the no form of this command.
vpdn enable
no vpdn enable
Syntax Description
This command has no arguments or keywords.
Command Default
VPDN is disabled.
Command Modes
Global configuration
Command History
11.2
This command was introduced.
12.2(33)SB
This command's behavior was modified and implemented on the Cisco 10000 series router as described in the Usage Guidelines below.
Usage Guidelines
The no vpdn enable command does not automatically disable a VPDN tunnel.
To shut down a VPDN tunnel, use the clear vpdn tunnel command or the vpdn softshut command.
Cisco 10000 Series Usage Guidelines
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the vpdn-group command if you issue the command before you issue the vpdn enable command. Instead, the following warning message displays:
% VPDN configuration is not allowed until VPDN is enabled through `vpdn enable'.In releases prior to Cisco IOS Release 12.2(33)SB, if you issue the vpdn-group command before the vpdn enable command, the router accepts the command and displays the following warning message:
% VPDN is not enabledExamples
The following example enables VPDN on the router:
vpdn enableRelated Commands
vpdn group
To associate a virtual private dialup network (VPDN) group with a customer or VPDN profile, use the vpdn group command in customer profile or VPDN profile configuration mode. To disassociate a VPDN group from a customer or VPDN profile, use the no form of this command.
vpdn group name
no vpdn group name
Syntax Description
name
Name of the VPDN group.
Note
Defaults
No default behavior or values.
Command Modes
Customer profile configuration
VPDN profile configurationCommand History
Usage Guidelines
Use the vpdn group command in customer profile configuration mode or VPDN profile configuration mode to associate a VPDN group with a customer profile or a VPDN profile, respectively.
VPDN groups are created using the vpdn-group command in global configuration mode.
Cisco 10000 Series Usage Guidelines
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the vpdn-group command if you issue the command before you issue the vpdn enable command. Instead, the following warning message displays:
% VPDN configuration is not allowed until VPDN is enabled through `vpdn enable'.In releases prior to Cisco IOS Release 12.2(33)SB, if you issue the vpdn-group command before the vpdn enable command, the router accepts the command and displays the following warning message:
% VPDN is not enabledExamples
The following example creates the VPDN groups named l2tp and l2f, and associates both VPDN groups with the VPDN profile named profile32:
Router(config)# vpdn-group l2tpRouter(config-vpdn)#!Router(config)# vpdn-group l2fRouter(config-vpdn)#!Router(config)# resource-pool profile vpdn profile32Router(config-vpdn-profile)# vpdn group l2tpRouter(config-vpdn-profile)# vpdn group l2fThe following example creates two VPDN groups and configures them under a customer profile named company2:
Router(config)# vpdn-group mygroupRouter(config-vpdn)#!Router(config)# vpdn-group yourgroupRouter(config-vpdn)#!Router(config)# resource-pool profile vpdn company2Router(config-vpdn-profile)# vpdn group mygroupRouter(config-vpdn-profile)# vpdn group yourgroupRelated Commands
Feature Information for CLI Command Changes
Table 42 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 42 Feature Information for CLI Command Changes
CLI command changes
12.2(33)SB
Modifies command behavior on the Cisco 10000 series router.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0812R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
Feedback