Published On: August 5ᵗʰ, 2019 19:04
Cisco IOS Additional Commands for Supervisor Engine 2T
platform software through show platform eobc crs-delay
platform software
To enable ACL or QoS configuration on the software platform, use the platform software command.
platform software {acl { log_update { rate-limit-msg { disable | enable }}} | qos { logging { bootup }}}
platform software met profile
To configure allocation percentages for each block size of the mmulticast expansion, use the platform software met profile command. To disable allocation percentages, use the no form of this command.
platform software met profile { value | value | value | value }
Command Modes
Usage Guidelines
The new profile will take affect on the switch after reload.
You must configure all four of the profile blocks, and the total block percentages cannot exceed 100 percent.
platform system-controller reset-threshold
To configure the system controller reset threshold, use the platform system-controller reset-threshold command.
platform system-controller reset-threshold { threshold-num }
Command Modes
Usage Guidelines
If you have a redundant supervisor engine and a TM_DATA_PARITY_ERROR, TM_LINK_ERR_INBAND, or TM_NPP_PARITY_ERROR error occurs, the affected supervisor engine reloads. When you do not have a redundant supervisor engine and a TM_DATA_PARITY_ERROR, TM_LINK_ERR_INBAND, or TM_NPP_PARITY_ERROR error occurs, one of the following happens:
platform verify
To enable Layer 3 error checking in the hardware, use the platform verify command in global configuration mode. To disable Layer 3 error checking in the hardware, use the no form of this command.
platform verify ipv4 {checksum | length {consistent | minimum} | same-address | tiny-frag}
Command Modes
Usage Guidelines
The minimum-length packets are the packets with an IP header length or IP total length field that is smaller than 20 bytes.
When entering the minimum keyword, follow these guidelines:
- When enabling the IP "too short" check using the platform verify ip length minimum command, valid IP packets with an IP protocol field of ICMP(1), IGMP(2), IP(4), TCP(6), UDP(17), IPv6(41), GRE(47), or SIPP-ESP(50) will be hardware switched. All other IP protocol fields are software switched.
- When entering the no platform verify ip length minimum command, minimum-length packets are hardware switched. The packets that have IP protocol = 6 (TCP) are sent to the software.
platform xconnect l2gre tunnel
To configure the Layer 2 generic routing encapsulation (l2gre) tunnel interface, use the platform xconnect l2gre tunnel command in VLAN interface mode.
Command Modes
police
To configure traffic policing, use the police command in policy-map class configuration mode or policy-map class police configuration mode. To remove traffic policing from the configuration, use the no form of this command.
Syntax for Packets per Second (pps)
police rate units pps [ burst-normal ] [ burst-max ] conform-action action exceed-action action [ violate-action action ]
no police bps [ burst-normal ] [ burst-max ] conform-action action exceed-action action [ violate-action action ]
Syntax for Bytes per Second (pps)
police bps [ burst-normal ] [ burst-max ] conform-action action exceed-action action [ violate-action action ]
no police bps [ burst-normal ] [ burst-max ] conform-action action exceed-action action [ violate-action action ]
Syntax Description
Command Modes
Policy-map class configuration (config-pmap-c) when specifying a single action to be applied to a marked packet
Policy-map class police configuration (config-pmap-c-police) when specifying multiple actions to be applied to a marked packet
Command History
Usage Guidelines
Use the police command to mark a packet with different quality of service (QoS) values based on conformance to the service-level agreement.
Traffic policing will not be executed for traffic that passes through an interface.
In Cisco IOS release 12.2(50)SY, when you apply the set-mpls-experimental-topmost action in the egress direction the set-mpls-experimental-imposition action is blocked.
The police command allows you to specify multiple policing actions. When specifying multiple policing actions when configuring the police command, note the following points:
- You can specify a maximum of four actions at one time.
- You cannot specify contradictory actions such as conform-action transmit and conform-action drop.
Using the Police Command with the Traffic Policing Feature
The police command can be used with the Traffic Policing feature. The Traffic Policing feature works with a token bucket algorithm. Two types of token bucket algorithms are in Cisco IOS Release 12.1(5)T: a single-token bucket algorithm and a two-token bucket algorithm. A single-token bucket system is used when the violate-action option is not specified, and a two-token bucket system is used when the violate-action option is specified.
The token bucket algorithm for the police command that was introduced in Cisco IOS Release 12.0(5)XE is different from the token bucket algorithm for the police command that was introduced in Cisco IOS Release 12.1(5)T. For information on the token bucket algorithm introduced in Release 12.0(5)XE, see the Traffic Policing document for Release 12.0(5)XE. This document is available on the New Features for 12.0(5)XE documentation index (under Modular QoS CLI-related feature modules) at www.cisco.com.
The following are explanations of how the token bucket algorithms introduced in Cisco IOS Release 12.1(5)T work.
Token Bucket Algorithm with One Token Bucket
The one-token bucket algorithm is used when the violate-action option is not specified in the police command CLI.
The conform bucket is initially set to the full size (the full size is the number of bytes specified as the normal burst size).
When a packet of a given size (for example, “B” bytes) arrives at specific time (time “T”), the following actions occur:
- Tokens are updated in the conform bucket. If the previous arrival of the packet was at T1 and the current time is T, the bucket is updated with (T - T1) worth of bits based on the token arrival rate. The token arrival rate is calculated as follows:
(time between packets (which is equal to T - T1) * policer rate)/8 bytes
- If the number of bytes in conform bucket B is greater than or equal to the packet size, the packet conforms and the conform action is taken on the packet. If the packet conforms, B bytes are removed from the conform bucket and the conform action is completed for the packet.
- If the number of bytes in conform bucket B (minus the packet size to be limited) is fewer than 0, the exceed action is taken.
Token Bucket Algorithm with Two Token Buckets
The two-token bucket algorithm is used when the violate-action option is specified in the police command.
The conform bucket is initially full (the full size is the number of bytes specified as the normal burst size).
The exceed bucket is initially full (the full exceed bucket size is the number of bytes specified in the maximum burst size).
The tokens for both the conform and exceed token buckets are updated based on the token arrival rate, or committed information rate (CIR).
When a packet of given size (for example, “B” bytes) arrives at specific time (time “T”) the following actions occur:
- Tokens are updated in the conform bucket. If the previous arrival of the packet was at T1 and the current arrival of the packet is at T, the bucket is updated with T -T1 worth of bits based on the token arrival rate. The refill tokens are placed in the conform bucket. If the tokens overflow the conform bucket, the overflow tokens are placed in the exceed bucket.
The token arrival rate is calculated as follows:
(time between packets (which is equal to T-T1) * policer rate)/8 bytes
- If the number of bytes in conform bucket B is greater than or equal to the packet size, the packet conforms and the conform action is taken on the packet. If the packet conforms, B bytes are removed from the conform bucket and the conform action is taken. The exceed bucket is unaffected in this scenario.
- If the number of bytes in conform bucket B is less than the packet size, the excess token bucket is checked for bytes by the packet. If the number of bytes in exceed bucket B is greater than or equal to 0, the exceed action is taken and B bytes are removed from the exceed token bucket. No bytes are removed from the conform bucket.
- If the number of bytes in exceed bucket B is less than the packet size, the packet violates the rate and the violate action is taken. The action is complete for the packet.
Using the set-cos-inner-transmit Action for SIPs and SPAs on the Cisco 7600 Series Router
The set-cos-inner-transmit keyword action was introduced in Cisco IOS Release 12.2(33)SRA to support marking of the inner CoS value as a policing action when using MPB features on the Enhanced FlexWAN module and when using MPB features on SPAs with the Cisco 7600 SIP-200 and Cisco 7600 SIP-400 on the Cisco 7600 series router.
This command is not supported on the Cisco 7600 SIP-600.
For more information about QoS and the forms of police commands supported by the SIPs on the Cisco 7600 series router, see the Cisco 7600 Series SIP, SSC, and SPA Software Configuration Guide.
Examples
Token Bucket Algorithm with One Token Bucket: Example
The following example shows how to define a traffic class (using the class-map command) and associate the match criteria from the traffic class with the traffic policing configuration, which is configured in the service policy (using the policy-map command). The service-policy command is then used to attach this service policy to the interface.
In this particular example, traffic policing is configured with the average rate at 8000 bits per second and the normal burst size at 1000 bytes for all packets leaving Fast Ethernet interface 0/0:
In this example, the initial token buckets starts full at 1000 bytes. If a 450-byte packet arrives, the packet conforms because enough bytes are available in the conform token bucket. The conform action (send) is taken by the packet and 450 bytes are removed from the conform token bucket (leaving 550 bytes).
If the next packet arrives 0.25 seconds later, 250 bytes are added to the token bucket ((0.25 * 8000)/8), leaving 800 bytes in the token bucket. If the next packet is 900 bytes, the packet exceeds and the exceed action (drop) is taken. No bytes are taken from the token bucket.
Token Bucket Algorithm with Two Token Buckets: Example
In this example, traffic policing is configured with the average rate at 8000 bits per second, the normal burst size at 1000 bytes, and the excess burst size at 1000 bytes for all packets leaving Fast Ethernet interface 0/0.
In this example, the initial token buckets starts full at 1000 bytes. If a 450-byte packet arrives, the packet conforms because enough bytes are available in the conform token bucket. The conform action (send) is taken by the packet, and 450 bytes are removed from the conform token bucket (leaving 550 bytes).
If the next
packet arrives 0.25 seconds later, 250 bytes are added to the
conform token bucket
((0.25 * 8000)/8), leaving 800 bytes in the conform token bucket.
If the next packet is 900 bytes, the packet does not conform
because only 800 bytes are available in the conform token
bucket.
The exceed token bucket, which starts full at 1000 bytes (as specified by the excess burst size), is then checked for available bytes. Because enough bytes are available in the exceed token bucket, the exceed action (set the QoS transmit value of 1) is taken and 900 bytes are taken from the exceed bucket (leaving 100 bytes in the exceed token bucket).
If the next packet arrives 0.40 seconds later, 400 bytes are added to the token buckets ((.40 * 8000)/8). Therefore, the conform token bucket now has 1000 bytes (the maximum number of tokens available in the conform bucket) and 200 bytes overflow the conform token bucket (because only 200 bytes were needed to fill the conform token bucket to capacity). These overflow bytes are placed in the exceed token bucket, giving the exceed token bucket 300 bytes.
If the arriving packet is 1000 bytes, the packet conforms because enough bytes are available in the conform token bucket. The conform action (transmit) is taken by the packet, and 1000 bytes are removed from the conform token bucket (leaving 0 bytes).
If the next packet arrives 0.20 seconds later, 200 bytes are added to the token bucket ((.20 * 8000)/8). Therefore, the conform bucket now has 200 bytes. If the arriving packet is 400 bytes, the packet does not conform because only 200 bytes are available in the conform bucket. Similarly, the packet does not exceed because only 300 bytes are available in the exceed bucket. Therefore, the packet violates and the violate action (drop) is taken.
Conforming to the MPLS EXP Value: Example
The following example shows that if packets conform to the rate limit, the MPLS EXP field is set to 5. If packets exceed the rate limit, the MPLS EXP field is set to 3.
Setting the Inner CoS Value as an Action for SIPs and SPAs on the Cisco 7600 Series Router: Example
The following example shows configuration of a QoS class that filters all traffic for virtual LAN (VLAN) 100 into a class named “vlan-inner-100” and establishes a traffic shaping policy for the vlan-inner-100 class. The service policy limits traffic to an average rate of 500 kbps, with a normal burst of 1000 bytes and a maximum burst of 1500 bytes, and sets the inner CoS value to 3. Since setting of the inner CoS value is supported only with bridging features, the configuration also shows the service policy being applied as an output policy for an ATM SPA interface permanent virtual circuit (PVC) that bridges traffic into VLAN 100 using the bridge-domain command.
Related Commands
police rate
To configure packet-based or byte-based traffic policing, use the police rate command in policy-map class configuration mode or policy-map class police configuration mode. To remove traffic policing from the configuration, use the no form of this command.
Syntax for Bytes per Second (bps)
police rate units bps [ burst burst_bytes bytes ] [ peak-rate peak_rate_bps bps ] [ peak-burst peak_burst_bytes bytes ] [ conform-action selected_action ] [ exceed-action selected_action ] [ violate-action selected_action ]
no police rate units bps [ burst burst_bytes bytes ] [ peak-rate peak_rate_bps bps ] [ peak-burst peak_burst_bytes bytes ] [ conform-action selected_action ] [ exceed-action selected_action ] [ violate-action selected_action ]
Syntax for Packets per Second (pps)
police rate units pps [ burst burst_packets packets ] [ conform-action selected_action ] [ exceed-action selected_action ] [ violate-action selected_action ]
no police rate units pps [ burst burst_packets packets ] [ conform-action selected_action ] [ exceed-action selected_action ] [ violate-action selected_action ]
Syntax Description
Command Modes
Policy-map class configuration (config-pmap-c) when specifying a single action to be applied to a marked packet
Policy-map class police configuration (config-pmap-c-police) when specifying multiple actions to be applied to a marked packet
port-channel hash-distribution
To set the hash distribution algorithm method, use the port-channel hash-distribution command in global configuration mode. To return to the default settings, use the no or default form of this command.
port-channel hash-distribution { adaptive | fixed }
Command Modes
Usage Guidelines
The EtherChannel load distribution algorithm uses the bundle select register in the port ASIC to determine the port for each outgoing packet. When you use the adaptive algorithm, it does not require the bundle select register to be changed for existing member ports. When you use the fixed algorithm and you either add or delete a port from the EtherChannel, the switch updates the bundle select register for each port in the EtherChannel. This update causes a short outage on each port.
Note
When you change the
algorithm, the change is applied at the next member link event.
Example events include link down, up, addition, deletion, no
shutdown, and shutdown. When you enter the command to change the
algorithm, the command console issues a warning that the command
does not take effect until the next member link event.
priority-queue cos-map
To map CoS values to the receive and transmit strict-priority queues in interface configuration command mode, use the priority-queue cos-map command. To return to the default mapping, use the no form of this command.
priority-queue cos-map queue-id cos1 [ cos2 [ cos3 [ cos4 [ cos5 [ cos6 [ cos7 [ cos8 ]]]]]]]
Command Modes
Command History
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
When mapping CoS values to the strict-priority queues, note the following information:
priority-queue queue-limit
To set the priority-queue size on an interface, use the priority-queue queue-limit command in interface configuration mode. To return to the default priority-queue size, use the no form of this command.
Command Modes
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
queue-buffers ratio
To set the buffer ratio for a queue, use the queue-buffers ratio command in QoS policy-map class configuration mode. To remove the queue buffer ratio, use the no form of the command.
rcv-queue bandwidth
To define the bandwidths for ingress (receive) WRR queues through scheduling weights in interface configuration command mode, use the rcv-queue bandwidth command. To return to the default settings, use the no form of this command.
Command Modes
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
rcv-queue cos-map
To map the class of service (CoS) values to the standard receive-queue drop thresholds, use the rcv-queue cos-map command in interface configuration mode. To remove the mapping, use the no form of this command.
rcv-queue cos-map queue-id threshold-id cos-1... cos-n
Command Modes
Command History
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
The cos-n value is defined by the module and port type. When you enter the cos-n value, note that the higher values indicate higher priorities.
rcv-queue queue-limit
To set the size ratio between the strict-priority and standard receive queues, use the rcv-queue queue-limit command in interface configuration mode. To return to the default settings, use the no form of this command.
Command Modes
Command History
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
Valid strict-priority weight values are fro m 1 to 100 percent, excep t on 1p1q8t ingress LAN ports, where valid values for the strict-priority queue are from 3 to 100 perce nt.
The rcv-queue queue-limit command configures ports on a per-ASIC basis.
Estimate the mix of strict-priority-to-standard traffic on your network (for example, 80-percent standard traffic and 20-percent strict-priority traffic) and use the estimated percentages as queue weights.
rcv-queue random-detect
To specify the minimum and maximum threshold for the specified receive queues, use the rcv-queue random-detect command in interface configuration mode. To return to the default settings, use the no form of this command.
rcv-queue random-detect { max-threshold | min-threshold } queue-id threshold-percent-1... threshold-percent-n
no rcv-queue random-detect { max-threshold | min-threshold } queue-id
Command Modes
Command History
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
This command is supported on 1p1q8t and 8q8t ports only.
The 1p1q8t interface indicates one strict queue and one standard queue with eight thresholds. The 8q8t interface indicates eight standard queues with eight thresholds. The threshold in the strict-priority queue is not configurable.
Each threshold has a low- and a high-threshold value. The threshold values are a percentage of the receive-queue capacity.
For additional information on configuring receive-queue thresholds, refer to the QoS chapter in the Cisco 7600 Series Router Cisco IOS Software Configuration Guide.
rcv-queue threshold
To configure the drop-threshold percentages for the standard receive queues on 1p1q4t and 1p1q0t interfaces, use the rcv-queue threshold command in interface configuration mode. To return the thresholds to the default settings, use the no form of this command.
rcv-queue threshold queue-id threshold-percent-1... threshold-percent-n
Command Default
The defaults for the 1p1q4t and 1p1q0t configurations are as follows:
- Quality of service (QoS) assigns all traffic with class of service (CoS) 5 to the strict-priority queue.
- QoS assigns all other traffic to the standard queue.
The default for the 1q4t configuration is that QoS assigns all traffic to the standard queue.
If you enable QoS, the following default thresholds apply:
– Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the
standard receive queue.
– Using standard receive-queue drop threshold 1, the
Cisco 7600 series router drops incoming frames with CoS 0 or 1 when
the receive-queue buffer is 50 percent or more full.
– Using standard receive-queue drop threshold 2, the
Cisco 7600 series router drops incoming frames with CoS 2 or 3 when
the receive-queue buffer is 60 percent or more full.
– Using standard receive-queue drop threshold 3, the
Cisco 7600 series router drops incoming frames with CoS 4 when the
receive-queue buffer is 80 percent or more full.
– Using standard receive-queue drop threshold 4, the
Cisco 7600 series router drops incoming frames with CoS 6 or 7 when
the receive-queue buffer is 100 percent full.
– Frames with CoS 5 go to the strict-priority receive
queue (queue 2), where the Cisco 7600 series router drops incoming
frames only when the strict-priority receive-queue buffer is 100
percent full.
– Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the
standard receive queue. The Cisco 7600 series router drops incoming
frames when the receive-queue buffer is 100 percent full.
– Frames with CoS 5 go to the strict-priority receive
queue (queue 2), where the Cisco 7600 series router drops incoming
frames only when the strict-priority receive-queue buffer is 100
percent full.
Note The 100-percent
threshold may be actually changed by the module to 98 percent to
allow Bridge Protocol Data Unite (BPDU) traffic to proceed. The
BPDU threshold is factory set at 100 percent.
Command Modes
Command History
Usage Guidelines
Note In Cisco IOS Release
12.2(50)SY and later releases, you can enable this command only if
either the platform qos queueing-only command
or the auto qos default command is
configured.
The queue - id value is always 1.
A value of 10 indicates a threshold when the buffer is 10 percent full.
Always set threshold 4 to 100 percent.
Receive thresholds take effect only on ports whose trust state is trust cos.
Configure the 1q4t receive-queue tail-drop threshold percentages with the wrr-queue threshold command.
show fips
To display the FIPs information about the switch, use the show fips command in EXEC mode.
show interfaces
To display statistics for all interfaces configured on the router or access server, use the show interfaces command in privileged EXEC mode.
Cisco 2500 Series, Cisco 2600 Series, Cisco 4700 Series, and Cisco 7000 Series
show interfaces [ type number ] [ first ] [ last ] [ accounting ]
Catalyst 6500 Series, Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor
show interfaces [ type slot / port ] [ accounting | counters protocol status | crb | dampening | description | dot1ad | etherchannel [ module number ] | fair-queue | irb | mac-accounting | mpls-exp | precedence | random-detect | rate-limit | stats | summary | switching | utilization { type number }]
Cisco 7500 Series with Ports on VIPs
show interfaces [ type slot / port-adapter / port ]
show interfaces [ type number | null interface-number | vlan vlan-id ]
Channelized T3 Shared Port Adapters
show interfaces serial [ slot / subslot / port / t1-num : channel-group ]
show interfaces type [ slot / subslot / port [ / sub-int ]]
Syntax Description
Command Modes
User EXEC
(>)
Privileged EXEC (#)
Command History
Usage Guidelines
The show interfaces command displays statistics for the network interfaces. The resulting output varies, depending on the network for which an interface has been configured. 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 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 you can specify a particular interface.
Valid values for the number argument 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 Content Switching Module (CSM) and the Firewall Services Module (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, and 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.
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.
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.
In Cisco IOS Release 12.2(33)SB, when a multilink PPP (MLP) interface is down/down, its default bandwidth rate is the sum of the serial interface bandwidths associated with the MLP 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 If an asterisk (*)
appears after the throttles counter value, it means that the
interface was throttled at the time the command was run.
Example with Custom Output Queueing
The following shows partial sample output when custom output queueing is enabled:
When custom queueing is enabled, the drops accounted for in the output queues result from bandwidth limitation for the associated traffic and lead to queue length overflow. Total output drops include drops on all custom queues and the system queue. Fields are described with the weighted fair queueing output in Table 2 .
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:
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 2 describes the input queue and output queue fields shown in the preceding two displays.
Table 2 Weighted-Fair-Queueing Output Field Descriptions
|
Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped. |
|
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 Except for protocols
that are encapsulated inside other protocols, such as IP over X.25,
the
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:
- AppleTalk
- Address Resolution Protocol (ARP) (for IP, Frame Relay, Switched Multimegabit Data Service (SMDS))
- Connectionless Network Service (CLNS)
- Digital Equipment Corporation (DEC) Maintenance Operations Protocol (MOP)
The routers use MOP packets to advertise their existence to Digital Equipment Corporation machines that use the MOP. A router periodically broadcasts MOP packets to identify itself as a MOP host. This results in MOP packets being counted, even when DECnet is not being actively used.
- DECnet
- HP Probe
- IP
- LAN Manager (LAN Network Manager and IBM Network Manager)
- Novell
- Serial Tunnel Synchronous Data Link Control (SDLC)
- Spanning Tree
- SR Bridge
- Transparent Bridge
The following is sample output from the show interfaces command when distributed WRED (DWRED) is enabled on an interface. Notice that the packet drop strategy is listed as “VIP-based weighted RED.”
The following is sample output from the show interfaces command for serial interface 2 when Airline Control (ALC) Protocol is enabled:
The following is sample output from the show interfaces command for an SDLC primary interface supporting the SDLC function:
Table 3 shows the fields relevant to all SDLC connections.
Table 4 shows other data given for each SDLC secondary interface configured to be attached to this interface.
Table 4 SDLC Field Descriptions
Sample show interfaces accounting Display
The following is sample output from the show interfaces accounting command:
When the output indicates that an interface is “disabled,” the router has received excessive errors (over 5000 in a keepalive period).
The following is sample output from the show interfaces command issued for the serial interface 1 for which flow-based 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:
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.”
When the show interfaces command i s issued on an unbound dialer interface, the output looks as follows:
But when the show interfaces command is issued on a bound dialer interface, you will get an additional report that indicates the binding relationship. The output is shown here:
At the end of the Dialer0 output, the show interfaces command is executed on each physical interface bound to it.
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 Link Access Procedure, Balanced (LAPB), not PPP, which is the encapsulation configured on the D interface and inherited by the B channel.
Any 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 Modular Service Cards (MSC) that is installed in slot 2 on a Cisco 7304 router:
Example for an Interface with an Asymmetric Receiver and Transmitter Rates
Table 5 describes the significant fields shown in the display.
Table 5 show interfaces fastethernet Field Descriptions—Fast Ethernet SPA
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:
Example 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:
Table 6 describes the fields shown in the display for Gigabit Ethernet SPA interfaces.
Table 6 show interfaces gigabitethernet Field Descriptions—Gigabit Ethernet SPA
Example with a Packet over SONET/SDH (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):
Table 7 show interfaces pos Field Descriptions—POS SPA
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):
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):
Table 8 describes the significant fields shown in the display.
Table 8 show interfaces sdcc Field Descriptions—POS SPA
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:
Table 9 describes the fields shown in the show interfaces serial output for a T3/E3 SPA.
Note The fields appearing
in the ouput will vary depending on card type, interface
configuration, and the status of the interface.
Table 9 show interfaces serial Field Descriptions—T3/E3 SPA
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:
Table 10 describes the significant fields shown in the display.
Table 10 show interfaces tengigabitethernet Field Descriptions—10-Gigabit Ethernet SPA
Displaying Traffic for a Specific Interface Example
This example shows how to display traffic for a specific interface:
Note The unknown protocol
drops field displayed in the above example refers to the total
number of packets dropped due to unknown or unsupported types of
protocol. This field occurs on several platforms such as the Cisco
3725, 3745, 3825, and 7507 series routers.
This example shows how to display traffic for a FlexWAN module:
Related Commands
show ip cef platform
To display entries in the Forwarding Information Base (FIB) or to display a summary of the FIB, use the show ip cef platform command in privileged EXEC mode.
show ip cef ip-prefix [mask] platform [checksum | detail | internal checksum]
Syntax Description
Examples
The following example shows FIB entry information for IP address prefix 10.4.4.4:
load_bal_or_adj[0] 0x0 load_bal_or_adj[1] 0x18 load_bal_or_adj[2] 0x1C
leaf points to an adjacency, index 0x607
ip_mask 0x0 as_number 0x0 precedence_num_loadbal_intf 0xF0 qos_group 0x0
tag_elt_addr = 0x50003038
ipv6_tag_elt_addr = 0x0
tag_index = 0x607
tt_tag_rew = 0x45046800
Tag Rewrite: vcci = 0x9DA, fib_root = 0x0
mac_rewrite_index = 0x395, flags = 0x9
pktswitched = 0 byteswitched = 0
XCM Tag Rewrite: vcci = 0x9DA, fib_root = 0x0
mac_rewrite_index = 0x395, flags = 0x9
mac_index_extension = 0x0
XCM mac rewrite from index 0x395
mtu from 0x53800E54(RP) 0xA3800E54(FP)
frag_flags = 0x0
mtu = 1496
mac length 0x12 encap length 0x16 upd_offset=0x02FF
mac string start from bank4 0x32001CA8(RP)
0x82001CA8(FP)
mac string end from bank9 0x50801CA8(RP)
0xA0801CA8(FP)
Encap String: 0005DC387B180003A011A57881000002884700012000
show ipv6 cef platform
To display platform-specific Cisco Express Forwarding (CEF) data, use the show ipv6 cef platform command in user EXEC or privileged EXEC mode.
Command Modes
show mac address-table
To display the MAC address table, use the show mac address - table command in privileged EXEC mode.
show mac address-table [ address mac-addr [ all | interface type / number | module number | vlan vlan-id ] | [ count [ module number | vlan vlan-id ]] | [ interface type / number ] | [ limit [ vlan vlan-id | module nu mber | interface interface-type ]] | [ module number ] | [ multicast [ count | { igmp-snooping | mld-snooping [ count ] | user [ count ] | vlan vlan-id }]] | [ notification { mac-move [ counter [ vlan ] | threshold | change } [ interface [ interface-number ]]] | [ synchronize statistics ] | [ unicast-flood ] | vlan vlan-id [ module number ]]
Syntax Description
Command Modes
Usage Guidelines
If you do not specify a module number, the output of the show mac address-table command displays information about the supervisor engine. To display information about the MAC address table of the DFCs, you must enter the module number or the all keyword.
The mac-addr value is a 48-bit MAC address. The valid format is H.H.H.
The interface-number argument designates the module and port number. Valid values 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 optional module number keyword and argument are supported only on DFC modules. The module number keyword and argument designate the module number.
Valid values for the mac-group-address argument are from 1 to 9.
The optional count keyword displays the number of multicast entries.
The optional multicast keyword displays the multicast MAC addresses (groups) in a VLAN or displays all statically installed or IGMP snooping-learned entries in the Layer 2 table.
The information that is displayed in the show mac address-table unicast-flood command output is as follows:
- Up to 50 flood entries, shared across all the VLANs that are not configured to use the filter mode, can be recorded.
- The output field displays are defined as follows:
– ALERT—Information is updated approximately every 3
seconds.
– SHUTDOWN—Information is updated approximately every 3
seconds.
Note The information
displayed on the destination MAC addresses is deleted as soon as
the floods stop after the port shuts down.
– Information is updated each time that you install the
filter. The information lasts until you remove the filter.
The dynamic entries that are displayed in the Learn field are always set to Yes.
The show mac address-table limit command output displays the following information:
- The current number of MAC addresses.
- The maximum number of MAC entries that are allowed.
- The percentage of usage.
The show mac address-table synchronize statistics command output displays the following information:
Examples
The following is sample output from the show mac address-table command:
Note In a distributed
Encoded Address Recognition Logic (EARL) switch, the asterisk (*)
indicates a MAC address that is learned on a port that is
associated with this EARL.
This example shows how to display the information about the MAC address table for a specific MAC address with a Supervisor Engine 720:
This example shows how to display MAC address table information for a specific MAC address with a Supervisor Engine 720:
This example shows how to display the currently configured aging time for all VLANs:
This example shows how to display the entry count for a specific slot:
This example shows how to display the information about the MAC address table for a specific interface with a Supervisor Engine 720:
Note A leading asterisk
(*) indicates entries from a MAC address that was learned from a
packet coming from an outside device to a specific module.
This example shows how to display the limit information for a specific slot:
The following example shows how to display the MAC-move notification status:
The following example shows how to display the MAC move statistics:
This example shows how to display the CAM-table utilization-notification status:
This example shows how to display the MAC notification parameters and history table:
This example shows how to display the MAC notification parameters and history table for a specific interface:
This example shows how to display unicast-flood information:
This example shows how to display the information about the MAC address table for a specific VLAN:
This example shows how to display the information about the MAC address table for MLDv2 snooping:
show mac address-table aging-time
To display the MAC address aging time, use the show mac address - table aging - time command in privileged EXEC mode.
Command Modes
Examples
The following example shows how to display the current configured aging time for all VLANs. The fields shown in the display are self-explanatory.
The following example shows how to display the current configured aging time for a specific VLAN. The fields shown in the display are self-explanatory.
show mac address-table dynamic
To display dynamic MAC address table entries only, use the show mac address - table dynamic command in privileged EXEC mode.
show mac address-table dynamic [{ address mac-addr } | { interface interface interface-num [ all | module number ]} | { module num } | { vlan vlan-id [ all | module number ]}]
Syntax Description
Command Modes
Usage Guidelines
The mac-address is a 48-bit MAC address and the valid format is H.H.H.
The optional module num keyword and argument are supported only on DFC modules. The module num keyword and argument designate the module number.
Examples
This example shows how to display all the dynamic MAC address entries for a specific VLAN.
This example shows how to display all the dynamic MAC address entries.
show mac address-table learning
To display the MAC address learning state, use the show mac address-table learning command in user EXEC mode.
show mac address-table learning [ vlan vlan-id | interface interface slot / port ] [ module num ]
Syntax Description
Command Modes
Usage Guidelines
The module num keyword and argument can be used to specify supervisor engines or Distributed Forwarding Cards (DFCs) only.
The interface interface slot / port keyword and arguments can be used on routed interfaces only. The interface interface slot / port keyword and arguments cannot be used to configure learning on switch port interfaces.
If you specify the vlan vlan-id, the state of the MAC address learning of the specified VLAN on all modules, including router interfaces, is displayed.
If you specify the vlan vlan-id and the module num, the state of the MAC address learning of a specified VLAN on a specified module is displayed.
If you specify the interface interface slot / port keyword and arguments, the state of the MAC address learning of the specified interface on all modules is displayed.
If you specify the interface interface slot / port keyword and arguments, the state of the MAC address learning of the specified interface on the specified module is displayed.
If you enter the show mac address-table learning command with no arguments or keywords, the status of MAC learning on all the existing VLANs on all the supervisor engines or DFCs configured on a Cisco 7600 series router is displayed.
Examples
This example shows how to display the MAC address learning status on all the existing VLANs on all of the supervisor engines or DFCs configured on a Cisco 7600 series router:
Table 11 describes the fields that are shown in the example.
Table 11 show mac address-table learning Field Descriptions
|
VLAN/Interface5 |
|
This example shows how to display the status of MAC address learning on all the existing VLANs on a single supervisor engine or a DFC:
This example shows how to display the status of MAC address learning for a specific VLAN on all the supervisor engines and DFCs:
This example shows how to display the status of MAC address learning for a specific VLAN on a specific supervisor engine or DFC:
This example shows how to display the status of MAC address learning for a specific supervisor engine or DFC:
This example shows how to display the status of MAC address learning for a specific interface on a specific supervisor engine or DFC:
show mac address-table static
To display static MAC address table entries only, use the show mac address - table static command in privileged EXEC mode.
show mac address-table static [ address mac - address | aging-time routed-mac | interface type number | module number | notification { change | mac-move } | synchronize statistics | vlan vlan-id ]
Syntax Description
Command Modes
Examples
The followig examples shows how to display the static MAC address entries:
The following example shows how to display static MAC address entries with a specific protocol type (in this case, assigned):
The following example shows the detailed output for the previous example:
show mvr
To display the current Multicast VLAN Registration (MVR) global parameter values, including whether or not MVR is enabled, the MVR multicast VLAN, the maximum query response time, the number of multicast groups, and the MVR mode (dynamic or compatible), use the show mvr privileged EXEC command.
Command Modes
Examples
This is an example of output from the show mvr command:
In the preceding display, the maximum number of multicast groups is fixed at 256. The MVR mode is either compatible (for interoperability with Catalyst 2900 XL and Catalyst 3500 XL switches) or dynamic (where operation is consistent with IGMP snooping operation and dynamic MVR membership on source ports is supported).
Related Commands
show mvr interface
To display the Multicast VLAN Registration (MVR) receiver and source ports, use the show mvr interface privileged EXEC command without keywords. Use the command with keywords to display MVR parameters for a specific receiver port.
show mvr interface [ interface-id [ members [ vlan vlan-id ]]]
Syntax Description
Command Modes
Usage Guidelines
If the entered port identification is a non-MVR port or a source port, the command returns an error message. For receiver ports, it displays the port type, per port status, and Immediate-Leave setting.
If you enter the members keyword, all MVR group members on the interface appear. If you enter a VLAN ID, all MVR group members in the VLAN appear.
Examples
This is an example of output from the show mvr interface command:
In the preceding display, Status is defined as follows:
- Active means the port is part of a VLAN.
- Inactive means that the port is not yet part of any VLAN.
- Up/Down means that the port is forwarding/nonforwarding.
This is an example of output from the show mvr interface command for a specified port:
This is an example of output from the show mvr interface interface-id members command:
show mvr members
To display all receiver and source ports that are currently members of an IP multicast group, use the show mvr members privileged EXEC command.
show mvr member s [ ip-address ]
Syntax Description
Command Modes
Usage Guidelines
The show mvr members command applies to receiver and source ports. For MVR-compatible mode, all source ports are members of all multicast groups.
Examples
This example shows the status of all mvr members:
This example shows the status of an IP address and the members of the IP multicast group with that IP address:
show platform acl software-switched
To display whether ACLs are enabled for software-switched WAN packets, use the show platform acl software-switched command in privileged EXEC mode.
Command Modes
Usage Guidelines
By default, ACLs are not applied to packets that are software-switched between WAN cards and the route processor. To determine whether ACLs are enabled for software-switched ingress or egress WAN packets, use the show platform acl software-switched command.
show platform bridge
To display distributed or hardware-based bridging information, use the show platform bridge command in privileged EXEC mode.
show platform bridge [ interface-type interface-number ] [ vlan vlan-id ] [ summary ]
Command Modes
Examples
The following is sample output from the show platform bridge command:
Table 12 describes the significant fields shown in the display.
Table 12 show platform bridge Field Descriptions
show platform cfm
To display connectivity fault management (CFM) commands, use the show platform cfm command in privileged EXEC mode.
show platform cfm { db | info | interface { gigabitethernet | port-channel | tengigabitethernet } number }
Command Modes
show platform cts reflector interface
To display platform Cisco Trusted Security (CTS) reflector interface configuration, use the show platform cts reflector interface command.
show platform cts reflector interface {gigabitethernet number | tengigabitethernet number | summary}
Command Modes
show platform datapath qos
To display QoS packet data path trace on the platform, use the show platform datapath qos command.
show platform datapath qos {cos | ingress-interface | last | lif | packet-data | pkt-length | recirc | src-index}
Command Modes
show platform eobc crs-delay
To display Ethernet out-of-band channel (EOBC) Carrier Router Service (CRS) delay on the platform, use the show platform eobc crs-delay command.