Additional Commands
Additional Commands
1
clear mac address-table
Usage Guidelines If the clear mac address-table command is invoked with no options, all dynamic addresses are removed.
If you specify an address but do not specify an interface, the address is deleted from all interfaces. If you
specify an interface but do not specify an address, all addresses on the specified interface are removed.
If a targeted address is not present in the MAC forwarding table, the following error message appears:
MAC address not found
Examples The following example shows how to clear all dynamic addresses in the MAC forwarding table:
Router# clear mac address-table dynamic
2
clear mac address-table
The following example shows how to clear the MAC-move notification counters on a specific VLAN:
Router# clear mac address-table notification mac-move counter 202
The following example shows the permanent address 0040.C80A.2F07 being cleared on Ethernet port 1:
Router# clear mac address-table permanent address 0040.C80A.2F07 interface ethernet 0/1
3
clear platform feature-manager
4
clear platform feature-manager
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
control-plane Specifies the control plane interface number. Range is 1–6.
number
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass-out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
async number Specifies the asynchronous interface number. Range is 1–999.
Defaults None.
Examples This example shows how to clear the platform-specific feature manager configuration that has an
asynchronous interface number of 4:
Router# clear platform feature-manager exception interface async 4
5
clear platform flow ip
Syntax Description destination This clears the entries with the destination address.
hostname The destination IP address.
instance It contains the earl instance.
module number The module number ranges from 1-6.
IP Address The destination IP address.
source The source IP address.
instance number This contains the earl instance which ranges from 0-0.
module number The module number ranges from 1-6.
Examples This example shows how to clear the platform IP destination host name module 4:
Router(config)# clear platform flow ip destination hostname module 4
6
clear platform flow ipv6
Examples This example shows how to clear platform flow IPv6 for module 4:
Router# clear platform flow ipv6 module 4
7
clear platform hardware acl
clear platform hardware acl {accounting-stats {module number} | hit-counts {all {module
number} | compaction {ipv6 {all {module}} | dest {module} | src {module}} | global_qos
{all {module} | in {ip {module} | ipv6 {module} | mac {module} | mpls {module}} | out {ip
{module} | ipv6 {module} | mac {module} | mpls {module}}} | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}} | rbacl {all {module number} | tcam
{A {index number} | B {index number}}}
8
clear platform hardware acl
Defaults None
9
clear platform hardware acl
Examples This example shows how to clear the hardware ACL accounting statistics for module 4:
Router# clear platform hardware acl accounting-stats module 4
10
clear platform hardware capacity rewrite-engine
Defaults None
Examples This example shows how to clear platform flow IPv6 for module 4:
Router# clear platform flow ipv6 module 4
11
clear platform hardware cef
clear platform hardware cef {ip {accounting {per-prefix {A.B.C.D | all}}} | ipv6 {accounting
{per-prefix}}}
Defaults None
Examples This example shows how to clear the hardware CEF IPv6 accounting prefix entry:
Router# clear platform hardware cef ipv6 accounting per-prefix 34
12
clear platform hardware ehc
Syntax
Description ids Performs a hardware IDS check.
rate-limiter Specifies the hardware rate limits.
xcpt Specifies the hardware exceptions.
Defaults None
Examples This example shows how to clear the platform hardware EHC exceptions:
Router# clear platform hardware ehc xcpt
13
clear platform hardware statistics
Syntax Description module number Specifies the module number. Range is 1–6.
Defaults None
Examples This example shows how to clear the platform hardware statistics for module 4:
Router# clear platform hardware statistics module 4
14
clear platform qos
clear platform qos [ip | mac | mpls | ipv6 | arp [interface-type interface-number |
null interface-number | port-channel number | vlan vlan-id]]
Usage Guidelines The interface-number argument designates the module and port number. Valid values for
interface-number depend on the specified interface type and the chassis and module that are used. For
example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module
that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values
for the port number are from 1 to 48.
If you enter the clear platform qos command with no arguments, the global and per-interface aggregate
QoS counters for all protocols are cleared.
If you do not enter an interface type, the protocol aggregate-QoS counters for all interfaces are cleared.
15
clear platform qos
Note Entering the clear platform qos command affects the policing token bucket counters and might briefly
allow traffic to be forwarded that would otherwise be policed.
Examples This example shows how to clear the global and per-interface aggregate-QoS counters for all protocols:
Router# clear platform qos
This example shows how to clear the specific protocol aggregate-QoS counters for all interfaces:
Router# clear platform qos ip
16
clear platform software acl accounting-stats
Syntax Description module number Specifies the module number. Range is 1–6.
Defaults None
Examples This example shows how to clear the platform software ACL accounting statistics for module 4:
Router# clear platform software acl accounting-stats module 4
17
clear platform software met
Defaults None
Examples This example shows how to clear platform software MET statistics:
Router# clear platform software met detail
18
debug netdr
debug netdr
To debug NetDriver activity, use the debug netdr command. Use the no form of this command to disable
debugging output.
Defaults None
Examples This example shows how to debug the NetDriver data flow:
Router# debug netdr data
NetDriver Receive Data on interrupt debugging is on
NetDriver Receive Data debugging is on
NetDriver Transmit Data debugging is on
NetDriver Relay Data debugging is on
Router#
2d21h: const_ether_vlan_vencap() Vlan1:
2d21h: src_vlan=0x1 src_indx=0x3 len=0xE9 bpdu=0
2d21h: index_dir=0 dest_indx=0x0 dont_lrn=0
2d21h: Dbus hdr: 00000000 00010000 00030000 E9000000
2d21h: 00000000 00000000 00000000 00000000
2d21h: MAC hdr: dmac=00801C.938040, smac=00503E.8D6400, typelen=0800
2d21h: IP hdr: 45C000DB 02F30000 FF066331 AC143412 AB45C8CC
2d21h: fx1000_process_receive_packet() Vlan1:
2d21h: src_vlan=0x1 src_indx=0x108 len=0x40 bpdu=0
2d21h: index_dir=0 dest_indx=0x3 dont_lrn=0
2d21h: Dbus hdr: 60000000 00010000 01080000 40100000
2d21h: 0006AC14 3412AB45 C8CC0000 00030000
2d21h: MAC hdr: dmac=00503E.8D6400, smac=00605C.865B28, typelen=0800
2d21h: IP hdr: 45000028 B5254000 7D06F471 AB45C8CC AC143412
<... output truncated ...>
Router#
Related Commands
19
debug netdr
Command Description
debug netdr capture Debugs NetDriver capture activity.
debug netdr capture and-filter Debugs added filters.
debug netdr capture continuous Debugs NetDriver continuously.
debug netdr capture Debugs all matching destination packets.
destination-ip-address
debug netdr capture dmac Debugs matching destination packets.
debug netdr capture dstindex Debugs packets matching destination index.
debug netdr capture ethertype Debugs packets matching the ethertype.
debug netdr capture interface Debugs packets related to an interface.
debug netdr capture or-filter Debugs or-filter function packets.
debug netdr capture rx Debugs incoming packets only.
debug netdr capture smac Debugs packets matching the source MAC address.
debug netdr capture source-ip-address Debugs packets matching the source IP address.
debug netdr capture srcindex Debugs packets matching the source index.
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
20
debug netdr capture
debug netdr capture [and-filter [destination-ip-address {ipaddr | ipv6 ipaddr}| dmac mac-addr
| dstindex index-value | ethertype ethertype | interface interface | smac smac |
source-ip-address {ipaddr | ipv6 ipaddr} | srcindex index-value | vlan vlan-num]
Defaults None
21
debug netdr capture
22
debug netdr capture
Router#
23
debug netdr capture and-filter
debug netdr capture and-filter [destination-ip-address {ipaddr | ipv6 ipaddr}| dmac mac-addr |
dstindex index-value | ethertype ethertype | interface interface | smac smac |
source-ip-address {ipaddr | ipv6 ipaddr} | srcindex index-value | vlan vlan-num]
Syntax Description destination-ip- (Optional) Captures all packets matching a destination IP address.
address
ipaddr Captures packets for a specific destination IP address.
ipv6 ipaddr Captures all packets matching the IPv6 destination IP address.
dmac mac-addr (Optional) Captures packets matching a destination MAC address index.
dstindex (Optional) Captures all packets matching a destination index; valid values
index-value are 0 to 1048575.
ethertype (Optional) Captures all packets matching an ethertype; ethertype must be
ethertype entered in hexidecimal format.
interface (Optional) Captures packets related to the interface. See Usage
interface Guidelines.
smac smac (Optional) Captures packets matching the source MAC address; smac
must be entered in hexidecimal format.
source-ip-addr (Optional) Captures all packets matching a source IP address.
ess
srcindex (Optional) Captures all packets matching a source index; valid values are
index-value 0 to 1048575.
vlan vlan-num (Optional) Captures packets matching the VLAN number; valid VLAN
numbers are 0 to 4095.
Defaults None
24
debug netdr capture and-filter
• Async
• Auto-template
• CTunnel
• Dialer
• EsconPhy
• Fcpa
• Filter
• Filtergroup
• GMPLS
• GigabitEthernet
• Group-Async
• LISP
• LongReachEthernet
• Looopback
• Lspvif
• MFR
• Multilink
• Null
• Port-channel
• Sysclock
• TenGigabitEthernet
• Tunnel
• Vif
• Virtual-Ethernet
• Virtual-Template
• Virtual-TokenRing
• VLAN
• VoaBypassIn
• VoaBypassOut
• VoaFilterIn
• VoaFilterOut
• VoaIn
• VoaOut
Router#
25
debug netdr capture and-filter
26
debug netdr capture continuous
27
debug netdr capture continuous
Defaults None
28
debug netdr capture continuous
• Tunnel
• Vif
• Virtual-Ethernet
• Virtual-Template
• Virtual-TokenRing
• VLAN
• VoaBypassIn
• VoaBypassOut
• VoaFilterIn
• VoaFilterOut
• VoaIn
• VoaOut
Router#
29
debug netdr capture destination-ip-address
Defaults None
Router#
30
debug netdr capture destination-ip-address
Command Description
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
31
debug netdr capture dmac
Syntax Description mac-addr (Optional) Captures packets matching a destination MAC address index.
Defaults None
Router#
32
debug netdr capture dmac
Command Description
debug netdr capture srcindex Debugs packets matching the source index.
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
33
debug netdr capture dstindex
Syntax Description index-value (Optional) Captures all packets matching a destination index; valid values
are 0 to 1048575.
Defaults None
Router#
34
debug netdr capture dstindex
Command Description
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
35
debug netdr capture ethertype
Syntax Description ethertype (Optional) Captures all packets matching an ethertype; ethertype must be
entered in hexidecimal format.
Defaults None
Router#
36
debug netdr capture ethertype
Command Description
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
37
debug netdr capture interface
Syntax Description interface (Optional) Captures packets related to the interface. See Usage
Guidelines.
Defaults None
38
debug netdr capture interface
• Multilink
• Null
• Port-channel
• Sysclock
• TenGigabitEthernet
• Tunnel
• Vif
• Virtual-Ethernet
• Virtual-Template
• Virtual-TokenRing
• VLAN
• VoaBypassIn
• VoaBypassOut
• VoaFilterIn
• VoaFilterOut
• VoaIn
• VoaOut
Examples This example shows how to debug the NetDriver interface activity:
Router# debug netdr capture interface
Router#
39
debug netdr capture interface
Command Description
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
40
debug netdr capture or-filter
debug netdr capture or-filter [destination-ip-address {ipaddr | ipv6 ipaddr}| dmac mac-addr |
dstindex index-value | ethertype ethertype | interface interface | smac smac |
source-ip-address {ipaddr | ipv6 ipaddr} | srcindex index-value | vlan vlan-num]
no debug netdr capture or-filter [destination-ip-address {ipaddr | ipv6 ipaddr}| dmac mac-addr
| dstindex index-value | ethertype ethertype | interface interface | smac smac |
source-ip-address {ipaddr | ipv6 ipaddr} | srcindex index-value | vlan vlan-num]
Syntax Description destination-ip- (Optional) Captures all packets matching a destination IP address.
address
ipaddr Captures packets for a specific destination IP address.
ipv6 ipaddr Captures all packets matching the IPv6 destination IP address.
dmac mac-addr (Optional) Captures packets matching a destination MAC address index.
dstindex (Optional) Captures all packets matching a destination index; valid values
index-value are 0 to 1048575.
ethertype (Optional) Captures all packets matching an ethertype; ethertype must be
ethertype entered in hexidecimal format.
interface (Optional) Captures packets related to the interface. See Usage
interface Guidelines.
smac smac (Optional) Captures packets matching the source MAC address; smac
must be entered in hexidecimal format.
source-ip-addr (Optional) Captures all packets matching a source IP address.
ess
srcindex (Optional) Captures all packets matching a source index; valid values are
index-value 0 to 1048575.
vlan vlan-num (Optional) Captures packets matching the VLAN number; valid VLAN
numbers are 0 to 4095.
Defaults None
41
debug netdr capture or-filter
• Async
• Auto-template
• CTunnel
• Dialer
• EsconPhy
• Fcpa
• Filter
• Filtergroup
• GMPLS
• GigabitEthernet
• Group-Async
• LISP
• LongReachEthernet
• Looopback
• Lspvif
• MFR
• Multilink
• Null
• Port-channel
• Sysclock
• TenGigabitEthernet
• Tunnel
• Vif
• Virtual-Ethernet
• Virtual-Template
• Virtual-TokenRing
• VLAN
• VoaBypassIn
• VoaBypassOut
• VoaFilterIn
• VoaFilterOut
• VoaIn
• VoaOut
Router#
42
debug netdr capture or-filter
43
debug netdr capture rx
Syntax Description dti-type value (Optional) Captures all packets matching the 3-bit dti type; valid values
are 0 to 7.
dti-value value (Optional) Captures all packets matching the 21-bit dti value; valid values
are 0 to 4096.
Defaults None
Examples This example shows how to debug the NetDrivers incoming packets:
Router# debug netdr capture rx
Router#
44
debug netdr capture rx
Command Description
debug netdr capture smac Debugs packets matching the source MAC address.
debug netdr capture source-ip-address Debugs packets matching the source IP address.
debug netdr capture srcindex Debugs packets matching the source index.
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
45
debug netdr capture smac
Syntax Description smac (Optional) Captures packets matching the source MAC address; smac
must be entered in hexidecimal format.
Defaults None
Examples This example shows how to debug the NetDriver by capturing the source MAC addresses:
Router# debug netdr capture smac
Router#
46
debug netdr capture smac
Command Description
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
47
debug netdr capture source-ip-address
Defaults None
Examples This example shows how to debug the NetDriver: source IP address
Router# debug netdr capture source-ip-address
Router#
48
debug netdr capture source-ip-address
Command Description
debug netdr capture srcindex Debugs packets matching the source index.
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
49
debug netdr capture srcindex
Syntax Description index-value (Optional) Captures all packets matching a source index; valid values are
0 to 1048575.
Defaults None
Examples This example shows how to debug the NetDriver by capturing all packets matching the source index:
Router# debug netdr capture srcindex
Router#
50
debug netdr capture srcindex
Command Description
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
51
debug netdr capture tx
Defaults None
52
debug netdr capture tx
53
debug netdr capture tx
• VoaOut
Router#
54
debug netdr capture vlan
Syntax Description vlan-num (Optional) Captures packets matching the VLAN number; valid VLAN
numbers are 0 to 4095.
Defaults None
Router#
55
debug netdr capture vlan
Command Description
debug netdr capture srcindex Debugs packets matching the source index.
debug netdr capture tx Debugs outgoing packets only.
debug netdr clear-capture Clears the capture buffer.
debug netdr copy-captured Copies the packets to a file.
56
debug netdr clear-capture
Defaults None
Router#
57
debug netdr clear-capture
Command Description
debug netdr capture tx Debugs outgoing packets only.
debug netdr capture vlan Debugs packets for a specific VLAN.
debug netdr copy-captured Copies the packets to a file.
58
debug netdr copy-captured
Defaults None
Usage Guidelines You can copy a captured file to the following sources:
• bootdisk:
• const_nvram:
• dfc#2-bootflash:
• dfc#3-bootflash:
• disk0:
• ftp:
• http:
• https:
• image:
• null:
• nvram:
• rcp:
• scp:
• syslog:
• tftp:
• tmpsys:
59
debug netdr copy-captured
Examples This example shows how to debug the NetDriver copied packets:
Router# debug netdr copy-captured
Router#
60
debug platform software multicast routing
debug platform software multicast routing {cmfib [all | error | event | stats] | hal [all | error
| event]}
no debug platform software multicast routing {cmfib [all | error | event | stats] | hal [all | error
| event]}
Syntax Description cmfib Enables dubugging multicast CMFIB (Constellation multicast forwarding
information base).
all (Optional) Enables debugging for all multicast routing, events, and errors.
error (Optional) Enables debugging multicast routing errors.
event (Optional) Enables debugging multicast routing events.
stats (Optional) Enables debugging multicast hardware statistics.
hal Enables debugging multicast hardware abstraction layer (HAL).
Examples The following example shows the multicast routing error output:
Router# debug platform software multicast routing cmfib error
CMFIB Error debugging is on
61
debug platform software multicast routing
62
disconnect-timeout
disconnect-timeout
To change the EXEC timeout value for the main console after the console cable is removed, use the
disconnect-timeout command in EXEC mode.
disconnect-timeout seconds
Syntax Description seconds Number of seconds until the console connection is to be disconnected; valid values
are 1 — 10 seconds.
Defaults 1 second
Usage Guidelines You cannot save the disconnect-timeout command to the configuration file.
The supervisor engine automatically detects the console cable removal from the front panel console port
and terminates the main console EXEC session after the specified timeout.
Examples The following example shows how to set the disconnect time to 3 seconds:
Switch# disconnect-timeout 3
63
fips
fips
To enable the Federal Information Processing Standards (FIPS) security requirements on the switch, use
the fips command in FIPS mode.
fips
no fips
Defaults None
64
flow hardware export
Examples The following example configures the NDE CPU and line card threshold percentages to 50:
Router(config)# flow hardware export threshold 50
The following example configures the NDE CPU threshold percentage to 50 and line card threshold
percentage to 70:
Router(config)# flow hardware export threshold 50 linecard 70
65
logging buffered
logging buffered
To enable system message logging to a local buffer, use the logging buffered command in global
configuration mode. To cancel the use of the buffer, use the no form of this command. To return the
buffer size to its default value, use the default form of this command.
no logging buffered
Syntax Description discriminator (Optional) Specifies a user-defined filter, via the logging discriminator, for syslog
messages.
discr-name (Optional) String of a maximum of eight alphanumeric, case-sensitive characters.
Blank spaces between characters are not allowed.
buffer-size (Optional) Size of the buffer, in bytes. The range is 4096 to 2147483647. The
default size varies by platform.
severity-level (Optional) The number or name of the desired severity level at which messages
should be logged. Messages at or numerically lower than the specified level are
logged. Severity levels are as follows (enter the number or the keyword):
[0 | emergencies]—System is unusable
[1 | alerts]—Immediate action needed
[2 | critical]—Critical conditions
[3 | errors]—Error conditions
[4 | warnings]—Warning conditions
[5 | notifications]—Normal but significant conditions
[6 | informational]—Informational messages
[7 | debugging]—Debugging messages
The default logging level varies by platform but is generally 7. Level 7 means that
messages at all levels (0–7) are logged to the buffer.
Command Default Varies by platform. For most platforms, logging to the buffer is disabled by default.
66
logging buffered
Release Modification
12.2SX This command is supported in the Cisco IOS Release 12.2SX train. Support
in a specific 12.2SX release of this train depends on your feature set,
platform, and platform hardware.
12.2(33)SB This command was integrated into Cisco IOS Release 12.2(33)SB.
12.2(50)SY This command was integrated into Cisco IOS Release 12.2(50)SY.
Usage Guidelines This command copies logging messages to an internal buffer. The buffer is circular in nature, so newer
messages overwrite older messages after the buffer is filled.
Specifying a severity-level causes messages at that level and numerically lower levels to be logged in an
internal buffer.
The optional discriminator keyword and discr-name argument provide another layer of filtering that
you can use to control the type and number of syslog messages that you want to receive.
When you resize the logging buffer, the existing buffer is freed and a new buffer is allocated. To prevent
the router from running out of memory, do not make the buffer size too large. You can use the show
memory EXEC command to view the free processor memory on the router; however, the memory value
shown is the maximum available and should not be approached. The default logging buffered command
resets the buffer size to the default for the platform.
On Catalyst 6500 standalone switches and Catalyst 6500 virtual switches, the default logging buffered
size is 8192.
To display messages that are logged in the buffer, use the show logging command. The first message
displayed is the oldest message in the buffer.
The show logging command displays the addresses and levels associated with the current logging setup
and other logging statistics.
Table 1 shows a list of levels and corresponding syslog definitions.
Examples The following example shows how to enable standard system logging to the local syslog buffer:
Router(config)# logging buffered
The following example shows how to use a message discriminator named buffer1 to filter critical
messages, meaning that messages at levels 0, 1, and 2 are filtered:
67
logging buffered
68
mac address-table aging-time
Syntax Description seconds MAC address table entry maximum age. Valid values are 0 and from 5 to
1000000 seconds. Aging time is counted from the last time that the switch
detected the MAC address. The default value is 300 seconds.
vlan vlan-id (Optional) Specifies the VLAN to apply the changed aging time; valid values
are from 1 to 4094.
Usage Guidelines If you do not enter a VLAN, the change is applied to all routed-port VLANs.
Enter 0 seconds to disable aging.
Examples The following example shows how to configure the aging time:
Router (config)# mac address-table aging-time 400
69
mac address-table aging-type
Command Default Dynamic addresses are not added to the MAC address table.
Examples The following example shows how to add a MAC address on port fa1/1 to VLAN 4:
Switch(config)# mac address-table aging-type 4
70
mac address-table learning
[default] mac address-table learning {vlan vlan-id | interface interface slot/port} [module num]
no mac address-table learning {vlan vlan-id | interface interface slot/port} [module num]
Defaults If you configure a VLAN on a port in a module, all of the supervisor engines and Distributed Forwarding
Cards (DFCs) in the Cisco 7600 series router are enabled to learn all the MAC addresses on the specified
VLAN.
Usage Guidelines You can use the module num keyword and argument to specify supervisor engines or DFCs only.
You can use the vlan vlan-id keyword and argument on switch port VLANs only. You cannot use the
vlan vlan-id keyword and argument to configure learning on routed interfaces.
You can use the interface interface slot/port keyword and arguments on routed interfaces, supervisor
engines, and DFCs only. You cannot use the interface interface slot/port keyword and arguments to
configure learning on switch port interfaces or non-DFC modules.
Examples This example shows how to enable MAC address learning on a switch port interface on all modules:
Router(config)# mac address-table learning vlan 100
Router(config)#
This example shows how to enable MAC address learning on a switch port interface on a specified
module:
Router(config)# mac address-table learning vlan 100 module 4
Router(config)#
71
mac address-table learning
This example shows how to disable MAC address learning on a specified switch-port interface for all
modules:
Router(config)# no mac address-table learning vlan 100
Router(config)#
This example shows how to enable MAC address learning on a routed interface on all modules:
Router(config)# mac address-table learning vlan 100
Router(config)#
This example shows how to enable MAC address learning on a routed interface for a specific module:
Router(config)# mac address-table learning interface FastEthernet 3/48 module 4
Router(config)#
This example shows how to disable MAC address learning for all modules on a specific routed interface:
Router(config)# no mac address-table learning interface FastEthernet 3/48
Router(config)#
72
mac address-table limit
mac address-table limit [action {warning | limit | shutdown}] [notification {syslog | trap |
both}] [interface type mod/port] [maximum num] [vlan vlan] [maximum num] [action
{warning | limit | shutdown}] [flood]
no mac address-table limit [action {warning | limit | shutdown}] [notification {syslog | trap |
both}] [interface type mod/port] [maximum num] [vlan vlan] [maximum num] [action
{warning | limit | shutdown}] [flood]
Syntax Description action (Optional) Specifies the type of action to be taken when the action is violated.
warning (Optional) Specifies that the one syslog message will be sent and no further action
will be taken when the action is violated.
limit (Optional) Specifies that the one syslog message will be sent and/or a
corresponding trap will be generated with the MAC limit when the action is
violated.
shutdown (Optional) Specifies that the one syslog message will be sent and/or the VLAN is
moved to the blocked state when the action is violated.
notification (Optional) Specifies the type of notification to be sent when the action is violated.
syslog (Optional) Sends a syslog message when the action is violated.
trap (Optional) Sends trap notifications when the action is violated.
both (Optional) Sends syslog and trap notifications when the action is violated.
interface type (Optional) Enables MAC limiting on a per-port basis.
mod/port
maximum num (Optional) Specifies the maximum number of MAC entries per-VLAN
per-Encoded Address Recognition Logic (EARL) allowed; valid values are from 5
to 32768 mac address entries.
vlan vlan (Optional) Enables MAC limiting on a per-VLAN basis.
flood (Optional) Enables unknown unicast flooding on a VLAN.
73
mac address-table limit
Usage Guidelines MAC limiting can be enabled on either a per-interface basis (by specifying an interface) or on a
per-VLAN basis (by specifying a VLAN). However, MAC limiting must first be enabled for the router
(a higher level) in global configuration mode (config).
Note This command enables the MAC limiting functionality for the router.
mac address-table limit [maximum num] [vlan vlan] [action {warning | limit | shutdown}]
[flood]
Note This command sets the specific limit and any optional actions to be imposed at the VLAN
level.
Note This command enables the MAC limiting functionality for the router.
mac address-table limit [interface type mod/port] [maximum num] [action {warning | limit |
shutdown}] [flood]
74
mac address-table limit
Note This command sets the specific limit and any optional actions to be imposed at the interface
level.
Examples This example shows how to enable per-VLAN MAC limiting. The first instance of the mac
address-table limit command enables MAC limiting. The second instance of the command sets the limit
and any optional actions to be imposed at the VLAN level.
Router# enable
Router# configure terminal
Router(config)# mac address-table limit
Router(config)# mac address-table limit vlan 501 maximum 50 action shutdown
Router(config)# end
This example shows how to enable per-interface MAC limiting. The first instance of the mac
address-table limit command enables MAC limiting. The second instance of the command sets the limit
and any optional actions to be imposed at the interface level.
Router# enable
Router# configure terminal
Router(config)# mac address-table limit
Router(config)# mac address-table limit fastethernet0/0 maximum 50 action shutdown
Router(config)# end
75
mac address-table notification change
Syntax Description history size (Optional) Sets the number of entries in the history buffer; valid values are
from 0 to 500 entries.
interval seconds (Optional) Sets the minimum change sending interval; valid values are
from 0 to 2147483647 seconds.
Examples This example shows how to configure the Simple Network Management Protocol (SNMP) notification
of dynamic additions to the MAC address table of addresses:
Router(config)# mac address-table notification change interval 5 history 25
76
mac address-table notification mac-move
Usage Guidelines MAC-move notification generates a syslog message whenever a MAC address or host moves between
different switch ports.
MAC-move notification does not generate a notification when a new MAC address is added to the
content-addressable memory (CAM) or when a MAC address is removed from the CAM.
MAC-move notification is supported on switch ports only.
The MAC-move counter notification generates a syslog message when the number of MAC moves in a
VLAN exceeds the maximum limit. The maximum limit is 1000 MAC moves.
The MAC-move counter syslog notification counts the number of times a MAC has moved within a
VLAN and the number of these instances that have occurred in the system.
77
mac address-table notification mac-move
78
mac address-table static
mac address-table static mac address vlan vlan-id {interface int | drop [disable-snooping]}
[dlci dlci | pvc vpi/vci] [auto-learn | disable-snooping] [protocol {ip | ipx | assigned}]
no mac address-table static mac address vlan vlan-id {interface int | drop [disable-snooping]}
[dlci dlci | pvc vpi/vci] [auto-learn | disable-snooping] [protocol {ip | ipx | assigned}]
Syntax Description mac address Address to add to the MAC address table.
vlan vlan-id Specifies the VLAN associated with the MAC address entry. The range is
from 2 to 100.
interface int Specifies the interface type and the slot and port to be configured. The int
argument should specify the interface type and the slot/port or
slot/subslot/port numbers (for example, interface pos 5/0 or interface atm
8/0/1).
drop Drops all traffic that is received from and going to the configured MAC
address in the specified VLAN.
disable-snooping (Optional) Disables IGMP snooping on the multicast MAC address.
dlci dlci (Optional) Specifies the data-link connection identifier (DLCI) to be mapped
to this MAC address. The valid range is from 16 to 1007.
Note This option is valid only if Frame Relay encapsulation has been
enabled on the specified interface.
pvc vpi/vci (Optional) Specifies the permanent virtual circuit (PVC) to be mapped to this
MAC address. You must specify both a virtual path identifier (VPI) and a
virtual circuit identifier (VCI), separated by a slash.
Note This option is valid only for ATM interfaces.
auto-learn (Optional) Specifies that if the router sees this same MAC address on a
different port, the MAC entry should be updated with the new port.
disable-snooping (Optional) Disables IGMP snooping on the Frame Relay DLCI or ATM
PVC.
protocol (Optional) Specifies the protocol associated with the entry.
ip (Optional) Specifies the IP protocol.
ipx (Optional) Specifies the Internetwork Packet Exchange (IPX) protocol.
assigned (Optional) Specifies assigned protocol bucket accounts for protocols such as
DECnet, Banyan VINES, and AppleTalk.
Command Default Static entries are not added to the MAC address table.
79
mac address-table static
Note Both the unicast MAC addresses and the multicast MAC addresses allow only one WAN interface.
In Cisco IOS Release 12.2(18)SXE, you must also specify the dlci option for Frame Relay interfaces, or
the pvc option for ATM interfaces, such as in the following example:
80
mac address-table static
Router(config)# mac address-table static 000C.0203.0405 vlan 101 interface ATM6/1 pvc6/101
Note If you omit the dlci option for Frame Relay interfaces, the MAC address is mapped to the first DLCI
circuit that is configured for the specified VLAN on that interface. Similarly, if you omit the pvc option
for ATM interfaces, the MAC address is mapped to the first PVC that is configured for the specified
VLAN on that interface. To ensure that the MAC address is configured correctly, we recommend always
using the dlci and pvc keywords on the appropriate interfaces.
Examples The following example shows how to add static entries to the MAC address table:
Router(config)# mac address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7
The following example shows how to configure a static MAC address with IGMP snooping disabled for
a specified address:
Router(config)# mac address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7
disable-snooping
The following example shows how to add static entries to the MAC address table for an ATM PVC circuit
and for a Frame Relay DLCI circuit:
Router(config)# mac address-table static 0C01.0203.0405 vlan 101 interface ATM6/1 pvc
6/101
Router(config)# mac address-table static 0C01.0203.0406 vlan 202 interface POS4/2 dlci 200
81
mac address-table synchronize
Syntax Description activity-time seconds (Optional) Specifies the activity timer interval: valid values are 160, 320,
and 640 seconds.
auto (Optional) Specifies that MAC address synchronization occur automatically.
Usage Guidelines We recommend that you configure the activity time so that at least two activity times exist within the
regular Layer 2 aging time (or within the aging time used for VLANs in distributed EtherChannels if this
feature is used only for distributed EtherChannels). If at least two activity times do not exist within the
aging time, then an error message is displayed.
Examples This example shows how to specify the activity timer interval:
Router(config)# mac address-table synchronization activity time 160
Router(config)#
82
mac address-table synchronize
This example shows how to specify the activity timer interval when out-of-band (OOB) synchronization
is enabled:
Router(config)# mac address-table synchronization activity time 160
% Current OOB activity time is [160] seconds
% Recommended aging time for all vlans is atleast three times the activity interval and
global aging time will be changed automatically if required
Router(config)#
This example shows how to display the timer interval when OOB synchronization is enabled:
Router(config)# mac address-table synchronization
% Current OOB activity time is [160] seconds
% Recommended aging time for all vlans is atleast three times the activity interval
Router(config)#
83
match l2 miss
match l2 miss
To match Layer 2 MAC miss in ingress policy, use the match l2 miss command.
match l2 miss
Examples The following example shows how to obtain information on match layer 2 MAC miss in ingress policy:
Router(config-cmap)# match l2 miss
84
mls ip multicast half-met
Defaults None
Usage Guidelines The mls ip multicast half-met command replaces the ipv6 mfib hardware-switching uplink
command.
The mls ip multicast half-met command is required for supporting IPv6 multicast on the redundant
Supervisor Engine 720 and Supervisor Engine 720-10GE. The command is applicable only on reload.
85
monitor session type
Syntax Description span-session-number Number of the local SPAN or ERSPAN session; valid values are from 1
to 66.
erspan-destination Specifies the ERSPAN destination-session configuration mode.
erspan-source Specifies the ERSPAN source-session configuration mode.
local Specifies the local SPAN session configuration mode.
local-tx Specifies the local egress-only SPAN session configuration mode.
rspan-destination Specifies the RSPAN destination-session configuration mode.
rspan-source Specifies the RSPAN source-session configuration mode.
Usage Guidelines Release 12.2(18)SXE and later releases support ERSPAN with the Supervisor Engine 720, hardware
revision 3.2 or higher. Enter the show module version | include WS-SUP720-BASE command to
display the hardware revision.
86
monitor session type
ERSPAN traffic is GRE-encapsulated SPAN traffic that can only be processed by an ERSPAN
destination session.
This command is not supported on Catalyst 6500 series switches that are configured with a Supervisor
Engine 2.
All ERSPAN source sessions on a switch must use the same source IP address. You enter the origin ip
address command to configure the IP address for the ERSPAN source sessions.
All ERSPAN destination sessions on a switch must use the same IP address. You enter the ip address
command to configure the IP address for the ERSPAN destination sessions. If the ERSPAN destination
IP address is not a PFC3 mode switch (for example, it is a network sniffer), the traffic arrives with the
GRE and RSPAN headers/encapsulation intact.
The ERSPAN source session destination IP address, which must be configured on an interface on the
destination switch, is the source of traffic that an ERSPAN destination session sends to the destination
ports. You configure the same address in both the source and destination sessions with the ip address
command.
The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from
different ERSPAN source sessions.
The local ERSPAN session limits are as follows:
• Total sessions—66
• Source sessions—2 (ingress or egress or both)
• Destination sessions—23
The monitor session type command creates a new ERSPAN session or allows you to enter the ERSPAN
session configuration mode. ERSPAN uses separate source and destination sessions. You configure the
source and destination sessions on different switches. The ERSPAN session configuration mode prompts
are as follows:
• Router(config-mon-erspan-src)—Indicates the ERSPAN source session configuration mode.
• Router(config-mon-erspan-src-dst)—Indicates the ERSPAN source session destination
configuration mode.
• Router(config-mon-erspan-dst)—Indicates the ERSPAN destination session configuration mode.
• Router(config-mon-erspan-dst-src)—Indicates the ERSPAN destination session source
configuration mode
Table 2 lists the ERSPAN destination session configuration mode syntaxes.
Syntax Description
Global Configuration Mode
monitor session erspan-destination-session-number | Enters ERSPAN or RSPAN destination session
rspan-destination-session-number type erspan-destination configuration mode and changes the prompt to the
| erspan-destination following:
Router(config-mon-erspan-dst)#
Router(config-mon-rspan-dst)#
Destination Session Configuration Mode
description session-description (Optional) Describes the ERSPAN or RSPAN destination
session.
87
monitor session type
Syntax Description
shutdown (Optional) (Default) Inactivates the ERSPAN destination
session.
no shutdown Activates the ERSPAN destination session.
destination {single-interface | interface-list | Associates the ERSPAN destination session number with
interface-range | mixed-interface-list} the destination ports.
source Enters ERSPAN destination session source configuration
mode and changes the prompt to the following:
Router(config-mon-erspan-dst-src)#
Destination Session Source Configuration Mode
ip address ip-address [force] Configures the ERSPAN flow destination IP address, which
must also be configured on an interface on the destination
switch and be entered in the ERSPAN destination session
configuration.
erspan-id erspan-flow-id Configures the ID number used by the destination and
destination sessions to identify the ERSPAN traffic.
vrf vrf-name (Optional) Configures the VRF name of the packets in the
ERSPAN traffic.
Syntax Description
Global Configuration Mode
monitor session erspan-source-session-number type Enters ERSPAN or RSPAN source session configuration
erspan-source | rspan-source mode and changes the prompt as appropriate to the
following:
Router(config-mon-erspan-src)#
Router(config-mon-rspan-src)#
Source Session Configuration Mode
description session-description (Optional) Describes the ERSPAN or RSPAN source
session.
shutdown (Optional) (Default) Inactivates the ERSPAN or RSPAN
source session.
no shutdown Activates the ERSPAN or RSPAN source session.
source {{single-interface | interface-list | interface-range | Associates the ERSPAN or RSPAN source session number
mixed-interface-list | single-vlan | vlan-list | vlan-range | with the source ports or VLANs, and selects the traffic
mixed-vlan-list} [rx | tx | both]} direction to be monitored.
filter {single-vlan | vlan-list | vlan-range | mixed-vlan-list} (Optional) Configures source VLAN filtering when the
ERSPAN or RSPAN source is a trunk port.
description session-description (Optional) Describes the ERSPAN or RSPAN source
session.
88
monitor session type
Syntax Description
Source Session Destination Configuration Mode
ip address ip-address Configures the ERSPAN or RSPAN flow destination IP
address, which must also be configured on an interface on
the destination switch and be entered in the ERSPAN or
RSPAN destination session configuration.
erspan-id erspan-flow-id Configures the ID number used by the source and
destination sessions to identify the ERSPAN or RSPAN
traffic.
origin ip address ip-address Configures the IP address used as the source of the
ERSPAN or RSPAN traffic.
ip {{ttl ttl-value} | {prec ipp-value} | {dscp dscp-value}} (Optional) Configures the following packet values in the
ERSPAN or RSPAN traffic:
• ttl ttl-value—IP time-to-live (TTL) value
• prec ipp-value—IP-precedence value
• dscp dscp-value—IP-precedence value
vrf vrf-name (Optional) Configures the VRF name of the packets in the
ERSPAN or RSPAN traffic.
When you configure the monitor sessions, follow these syntax guidelines:
• erspan-destination-span-session-number can range from 1 to 66.
• single-interface is interface type slot/port; type is fastethernet, gigabitethernet, or
tengigabitethernet.
• interface-list is single-interface , single-interface , single-interface ...
Note In lists, you must enter a space before and after the comma. In ranges, you must enter a space
before and after the dash.
Note When you enter the no monitor session range command, do not enter spaces before or after
the dash. If you enter multiple ranges, do not enter spaces before or after the commas.
Use the monitor session type local command to configure ingress, egress, or both ingress and egress
SPAN sessions.
89
monitor session type
Use the monitor session type local-tx command to configure egress-only SPAN sessions.
When you enter the local or the local egress-only SPAN session configuration mode, the prompt changes
accordingly to Router(config-mon-local)# or Router(config-mon-local-tx)#, and the following
commands are available:
• description—Describes the properties for this session using this syntax:
description description
The description can be up to 240 characters and cannot contain special characters or spaces.
• destination—Specifies the destination and the destination properties using this syntax:
source {cpu {rp | sp} | {interface type number} | {intrusion-detection-module num} | {vlan
vlan-id}} [, | - | rx | tx | both]
cpu rp Associates the local SPAN session number with the CPU on the route
processor.
cpu sp Associates the local SPAN session number with the CPU on the switch
processor.
90
monitor session type
interface type number Specifies the interface type and number as follows:
• FastEthernet mod/port
• GigabitEthernet mod/port
• Port-channel num—Ethernet Channel of interfaces; valid values are
from 1 to 496.
vlan vlan-id Specifies the VLAN; valid values are from 1 to 4094.
, (Optional) Specifies another range of interfaces.
- (Optional) Specifies a range of interfaces.
both (Optional) Monitors the received and the transmitted traffic.
rx (Optional) Monitors the received traffic only.
1
tx (Optional) Monitors the transmitted traffic only.
1. When you enter the local-tx keyword, the rx and both keywords are not available and the tx keyword is required.
Note Destination port channel interfaces must be configured with the channel-group group-num
mode on command and the no channel-protocol command.
91
monitor session type
Note In lists, you must enter a space before and after the comma. In ranges, you must enter a space
before and after the dash.
Note When you enter the no monitor session range command, do not enter spaces before or after
the dash. If you enter multiple ranges, do not enter spaces before or after the commas.
Examples This example shows how to configure an ERSPAN source session number and enter the ERSPAN source
session configuration mode for the session:
Router(config)# monitor session 55 type erspan-source
Router(config-mon-erspan-src)#
This example shows how to configure an ERSPAN destination session number and enter the ERSPAN
destination session configuration mode for the session:
Router(config)# monitor session 55 type erspan-destination
Router(config-mon-erspan-dst)#
This example shows how to associate the ERSPAN destination session number with the destination
ports:
Router(config-mon-erspan-dst) destination interface fastethernet 1/2 , 2/3
This example shows how to enter the ERSPAN destination session source configuration:
Router(config-mon-erspan-dst)# source
Router(config-mon-erspan-dst-src)#
This example shows how to enter the ERSPAN destination session source configuration mode:
Router(config-mon-erspan-dst)# source
Router(config-mon-erspan-dst-src)#
92
monitor session type
This example shows how to enter the ERSPAN source session destination configuration mode:
Router(config-mon-erspan-src)# destination
Router(config-mon-erspan-src-dst)#
This example shows how to configure the ID number that is used by the source and destination sessions
to identify the ERSPAN traffic:
Router(config-mon-erspan-src-dst)# erspan-id 1005
Router(config-mon-erspan-src-dst)#
This example shows how to configure session 1 to monitor ingress traffic from Gigabit Ethernet port 1/1
and configure Gigabit Ethernet port 1/2 as the destination:
Router(config)# monitor session 1 type local
Router(config-mon-local)# source interface gigabitethernet 1/1 rx
Router(config-mon-local)# destination interface gigabitethernet 1/2
This example shows how to configure session 1 to monitor egress-only traffic from Gigabit Ethernet
port 5/1 and configure Gigabit Ethernet port 5/2 as the destination:
Router(config)# monitor session 1 type local-tx
Router(config-mon-local)# source interface gigabitethernet 5/1 rx
Router(config-mon-local)# destination interface gigabitethernet 5/2
93
mvr (global configuration)
mvr [group ip-address [count] | mode [compatible | dynamic] | querytime value | vlan vlan-id]
no mvr [group ip-address | mode [compatible | dynamic] | querytime value | vlan vlan-id]
Syntax Description group ip-address (Optional) Statically configures an MVR group IP multicast address on the
switch.
Use the no form of this command to remove a statically configured IP
multicast address or contiguous addresses or, when no IP address is entered,
to remove all statically configured MVR IP multicast addresses.
count (Optional) Configures multiple contiguous MVR group addresses. The range
is 1 to 256; the default is 1.
mode (Optional) Specifies the MVR mode of operation.
The default is compatible mode.
compatible (Optional) Sets MVR mode to provide compatibility with Catalyst 2900 XL
and Catalyst 3500 XL switches. This mode does not allow dynamic
membership joins on source ports.
dynamic (Optional) Sets MVR mode to allow dynamic MVR membership on source
ports.
querytime value (Optional) Sets the maximum time to wait for IGMP report memberships on
a receiver port. This time applies only to receiver-port leave processing.
When an IGMP query is sent from a receiver port, the switch waits for the
default or configured MVR querytime for an IGMP group membership
report before removing the port from multicast group membership.
The value is the response time in units of tenths of a second. The range is 1
to 100; the default is 5 tenths or one-half second.
Use the no form of the command to return to the default setting.
vlan vlan-id (Optional) Specifies the VLAN on which MVR multicast data is expected to
be received. This is also the VLAN to which all the source ports belong. The
range is 1 to 4094; the default is VLAN 1.
94
mvr (global configuration)
Usage Guidelines Use the mvr command with keywords to set the MVR mode for a switch, configure the MVR IP
multicast address, set the maximum time to wait for a query reply before removing a port from group
membership, and to specify the MVR multicast VLAN. A maximum of 256 MVR multicast groups can
be configured on a switch.
Use the mvr group command to statically set up all the IP multicast addresses that will take part in
MVR. Any multicast data sent to a configured multicast address is sent to all the source ports on the
switch and to all receiver ports that have registered to receive data on that IP multicast address.
MVR supports aliased IP multicast addresses on the switch. However, if the switch is interoperating with
Catalyst 6500 Series switches, you should not configure IP addresses that create an alias between
themselves or with the reserved IP multicast addresses (in the range 224.0.0.xxx).
The mvr querytime command applies only to receiver ports.
If the switch MVR is interoperating with Catalyst 6500 Series switches, set the multicast mode to
compatible.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
MVR can coexist with IGMP snooping on a switch.
Multicast routing and MVR cannot coexist on a switch. If you enable multicast routing and a multicast
routing protocol while MVR is enabled, MVR is disabled and a warning message appears. If you try to
enable MVR while multicast routing and a multicast routing protocol are enabled, the operation to
enable MVR is cancelled and an Error message is displayed.
Use the show mvr privileged EXEC command to display the current setting for maximum multicast
groups.
This example shows how to configure 228.1.23.4 as an IP multicast address:
Switch(config)# mvr group 228.1.23.4
This example shows how to configure ten contiguous IP multicast groups with multicast addresses from
228.1.23.1 to 228.1.23.10:
Switch(config)# mvr group 228.1.23.1 10
Use the show mvr members privileged EXEC command to display the IP multicast group addresses
configured on the switch.
This example shows how to set the maximum query response time as one second (10 tenths):
Switch(config)# mvr querytime 10
95
mvr (global configuration)
You can verify your settings by entering the show mvr privileged EXEC command.
96
mvr (interface configuration)
Syntax Description immediate (Optional) Enables the Immediate Leave feature of MVR on a port. Use
the no mvr immediate command to disable the feature.
type (Optional) Configures the port as an MVR receiver port or a source port.
The default port type is neither an MVR source nor a receiver port. The
no mvr type command resets the port as neither a source or a receiver
port.
receiver Configures the port as a subscriber port that can only receive multicast
data. Receiver ports cannot belong to the multicast VLAN.
source Configures the port as an uplink port that can send and receive multicast
data for the configured multicast groups. All source ports on a switch
belong to a single multicast VLAN.
vlan vlan-id group (Optional) Adds the port as a static member of the multicast group with
the specified VLAN ID.
The no mvr vlan vlan-id group command removes a port on a VLAN
from membership in an IP multicast address group.
ip-address (Optional) Statically configures the specified MVR IP multicast group
address for the specified multicast VLAN ID. This is the IP address of the
multicast group that the port is joining.
97
mvr (interface configuration)
Usage Guidelines Configure a port as a source port if that port should be able to both send and receive multicast data bound
for the configured multicast groups. Multicast data is received on all ports configured as source ports.
Receiver ports cannot be trunk ports. Receiver ports on a switch can be in different VLANs, but should
not belong to the multicast VLAN.
A port that is not taking part in MVR should not be configured as an MVR receiver port or a source port.
A non-MVR port is a normal switch port, able to send and receive multicast data with normal switch
behavior.
When Immediate Leave is enabled, a receiver port leaves a multicast group more quickly. Without
Immediate Leave, when the switch receives an IGMP leave message from a group on a receiver port, it
sends out an IGMP MAC-based query on that port and waits for IGMP group membership reports. If no
reports are received in a configured time period, the receiver port is removed from multicast group
membership. With Immediate Leave, an IGMP MAC-based query is not sent from the receiver port on
which the IGMP leave was received. As soon as the leave message is received, the receiver port is
removed from multicast group membership, which speeds up leave latency.
The Immediate Leave feature should be enabled only on receiver ports to which a single receiver device
is connected.
The mvr vlan group command statically configures ports to receive multicast traffic sent to the IP
multicast address. A port statically configured as a member of group remains a member of the group until
statically removed. In compatible mode, this command applies only to receiver ports; in dynamic mode,
it can also apply to source ports. Receiver ports can also dynamically join multicast groups by using
IGMP join messages.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
An MVR port cannot be a private-VLAN port.
Examples This example shows how to configure a port as an MVR receiver port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr type receiver
Use the show mvr interface privileged EXEC command to display configured receiver ports and source
ports.
This example shows how to enable Immediate Leave on a port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr immediate
This example shows how to add a port on VLAN 1 as a static member of IP multicast group 228.1.23.4:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan1 group 230.1.23.4
You can verify your settings by entering the show mvr members privileged EXEC command.
98
mvr (interface configuration)
99
platform cts
platform cts
To configure Cisco Trusted Security (CTS) platform commands, use the platform cts command in
Global configuration mode. To disable this capability, use the no form of this command.
Examples The following example shows how to configure capturing CTS platform packets on the egress:
Router (onfig)# platform cts egress
The following example shows how to configure capturing CTS platform packets on the ingress:
Router# platform cts ingress
100
platform hardware cef maximum-routes
Command Default Each protocol has a default maximum route setup of 1000 hardware entries. Each protocol is allowed to
use the maximum routes from the shared area.
The defaults for the shared area are as follows:
• For XL-mode systems—512,000 routes
• For non-XL mode systems—248,000 routes
The maximum routes value is based on hardware entries. Different protocols use different numbers of
hardware (hw) entries per route:
• IPv4 and MPLS—1 hw entry
• IPv6, IPv4 multicast and Eom-v4 multicast—2 hw entries
• IPv6 multicast and Eom-v6 multicast—4 hw entries4 hw entries
Note See the “Usage Guidelines” section for information on XL and non-XL mode systems.
101
platform hardware cef maximum-routes
Usage Guidelines
Note If you copy a configuration file that contains the multilayer switching (MLS) Cisco Express Forwarding
maximum routes into the startup-config file and reload the Cisco 7600 series router, the Cisco 7600
series router reloads after it reboots.
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
System reboot is not required for the maximum routes to take effect. A newly configured maximum route
value is validated against the current usage of the hardware FIB. Once validated the new value takes
effect immediately.
The maximum routes value for each protocol is configured separately. The new protocols supported
include IPv4, IPv4 multicast, IPv6, IPv6 multicast, MPLS, EoMPLS, vpls-v4-multicast, and
vpls-v6-multicast. MPLS-VPN routes are counted with MPLS maximum routes setup.
Note Due to limited space usage, diags protocol entries are counted against IPv4-allocated maximum routes
value.
The concept of a flexible setting of maximum routes value has been introduced. In addition to a specific
maximum routes value per protocol, a single shared area is also defined. This shared area can be used
by selected protocols once their dedicated spaces are exhausted.
Combined with the flexible setting feature, the maximum routes value can be used to specify both the
minimum and the maximum values of entries to be allocated to a protocol. You can specify whether the
protocol is allowed to use the shared area or not.
The platform cef maximum-routes command limits the maximum number of the routes that can be
programmed in the hardware. If routes are detected that exceed the limit for that protocol, an exception
condition is generated.
The determination of XL and non-XL mode is based on the type of Policy Feature Card (PFC) or
Distributed Forwarding Card (DFC) modules that are installed in your system. For additional
information on systems running Cisco IOS Release 12.2SXF and earlier releases see:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/release/notes/OL_416
4.html#Policy_Feature_Card_Guidelines_and_Restrictions
For additional information on systems running Cisco IOS Release 12.2SXH and later releases see:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.html#
Policy_Feature_Card_Guidelines_and_Restrictions
The valid values for the maximum-routes argument depend on the system mode—XL mode or non-XL
mode. The valid values are as follows:
• XL mode
– IP and MPLS—Up to 1,007,000 routes
– IP multicast and IPv6—Up to 503,000 routes
• Non-XL mode
– IP and MPLS—Up to 239,000 routes
– IP multicast and IPv6—Up to 119,000 routes
102
platform hardware cef maximum-routes
Note The maximum values that you are permitted to configure is not fixed but varies depending on the values
that are allocated for other protocols.
Examples This example shows how to set the maximum number of routes that are allowed per protocol:
Router(config)# platform hardware cef maximum-routes ip 100
This example shows how to return to the default setting for a specific protocol:
Router(config)# no platform hardware cef maximum-routes ip
103
platform cts
platform cts
To enable Cisco Trusted Security (CTS) in egress or ingress mode, use the platform cts command.
Examples This example shows how to enable the CTS in egress mode:
Router(config)# platform cts egress
104
platform feature-manager
platform feature-manager
To configure the platform-specific feature manager, use the platform feature-manager command.
Defaults None.
Examples This example shows how to configure static region setup in TCAM for downloadable ACLs:
Router(config)# platform feature-manager acl downloadable setup static
105
platform feature-manager capture rate-limit
Syntax Description pps Specifies the rate limit in packets per second; valid values are 0 through
1000000 seconds.
Examples The following example shows how to set the rate-limit capture to 10000 seconds:
Router # platform feature-manager capture rate-limit pps 10000
106
platform hardware acl
platform hardware acl {cc {enable} | default-result {bridge | deny | permit} | other-protocols
{prot1 {range 1 | range 7 | range 8 | range 4 | range 2 | range 5 | range 6 | range 3} | prot2
{range 1 | range 7 | range 8 | range 4 | range 2 | range 5 | range 6 | range 3} | prot3 {range 1 |
range 7 | range 8 | range 4 | range 2 | range 5 | range 6 | range 3} | prot4 {range 1 | range 7 |
range 8 | range 4 | range 2 | range 5 | range 6 | range 3} | prot5 {range 1 | range 7 | range 8 |
range 4 | range 2 | range 5 | range 6 | range 3} | prot6 {range 1 | range 7 | range 8 | range 4 |
range 2 | range 5 | range 6 | range 3}} | reserve {qos-banks {num}| rbacl-tcam-percentage
{sgt-dgt {percentage}}} | update-mode hitless | downloadable setup static}
107
platform hardware acl
Defaults Release 15.0(1)SY no payload encryption (NPE) images do not support the hitless ACL update feature
or the [no] platform hardware acl update-mode hitless command.
Release 15.0(1)SY1 and later no payload encryption (NPE) images support hitless ACL update and the
platform hardware acl update-mode hitless command is configured by default.
In other releases and images, the platform hardware acl update-mode hitless command is configured
by default.
Examples This example shows how to configure the paltform hardware ACL protocol 6 with value 105:
Router(config)# platform hardware acl other-protocols prot6 105
108
platform hardware cef
Defaults None
Examples This example shows how to enable CEF with a per-protocol maximum routes configuration using IPv6
for five entries:
Router(config)# platform hardware cef maximum-routes ipv6 5
109
platform hardware vsl
Defaults None
Examples This example shows how to boot the virtual switch in non-XL mode:
Router(config)# platform hardware vsl pfc mode non-xl
110
platform ip
platform ip
To enable multilayer switching (MLS) IP for the internal router on the interface, use the platform ip
command in interface configuration mode. To disable MLS IP on the interface use the no form of this
command.
platform ip
no platform ip
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 720.
111
platform ip cef accounting per-prefix
Usage Guidelines Per-prefix accounting collects the adjacency counters used by the prefix. When the prefix is used for
accounting, the adjacency cannot be shared with other prefixes. You can use per-prefix accounting to
account for the packets sent to a specific destination.
112
platform ip cef load-sharing
Syntax Description dst-only (Optional) Sets the load-balancing algorithm to include destination to include
destination Layer 4 ports and destination IP addresses (Layer 3)
full (Optional) Sets the Cisco Express Forwarding load-balancing to include source and
destination Layer 4 ports and source and destination IP addresses (Layer 3).
ip-only (Optional) Sets the load-balancing algorithm to include source and destination IP
addresses.
Usage Guidelines The platform ip cef load-sharing command affects the IPv4, the IPv6, and the Multiprotocol Label
Switching (MPLS) forwardings.
The platform ip cef load-sharing command is structured as follows:
• platform ip cef load-sharing full—Uses Layer 3 and Layer 4 information with multiple
adjacencies.
For additional guidelines, refer to the Cisco 7600 Series Router Cisco IOS Software Configuration
Guide.
Examples This example shows how to set load balancing to include Layer 3 and Layer 4 ports with multiple
adjacencies:
Router(config)# platform ip cef load-sharing
This example shows how to set load balancing to exclude the destination Layer 4 ports and source and
destination IP addresses (Layer 3) from the load-balancing algorithm:
Router(config)# platform ip cef load-sharing full exclude-port destination
113
platform ip cef load-sharing
This example shows how to set load balancing to exclude the source Layer 4 ports and source and
destination IP addresses (Layer 3) from the load-balancing algorithm:
Router(config)# platform ip cef load-sharing full exclude-port source
114
platform ipv6 cef
Examples This example shows how to enable the MLF CEF accounting in IPv6 configuration:
Router(config)# platform ipv6 cef accounting
115
platform mpls gbte
platform mpls gbte {burst time | cir-ratio number | dscp number | global-pool}
Syntax Description burst time Specifies the burst duration for guaranteed bandwidth TE flows in
milliseconds. Range is 100–30000.
cir-ratio number Specifies the policing at the mentioned ratio with regard to CIR. Range is
1–100.
dscp number Specifies the DSCP map for guaranteed bandwidth TE flows. Range is 0–63.
global-pool Inspect TE flows using resources allocated from global pool.
Examples This example shows how to inspect the TE flows using resources allocated from global pool:
Router(config)# platform mpls gbte global-pool
116
platform multicast routing
117
platform multicast snooping
Examples This example shows how to enable LTL-sharing across VLANs in multicast snooping configuration:
Router(config)# platform multicast snooping ltl-share across
118
platform qos 10g-only
Usage Guidelines When you enter the platform qos 10g-only command, a supervisor engine with both 1-Gigabit and
10-Gigabit Ethernet uplink ports reallocates the interface queue capacity to improve the performance of
its 10-Gigabit Ethernet ports. The reallocation is possible only in 10g-only mode, in which the
supervisor engine’s 1-Gigabit Ethernet ports are not used. In the normal mode, when all supervisor
engine ports are active, the queue structure is 2q4t on receive and 1p3q4t on transmit. In 10g-only mode,
the queue structure is 8q4t on receive and 1p7q4t on transmit.
Note To display detailed information about the queues, use the show queueing interface command.
When you switch between normal and 10g-only modes, any existing QoS configuration on the uplink
ports is lost, and you must reconfigure QoS. In addition, service will be temporarily lost on the ports
during the transition.
If you do not shut down the 1-Gigabit Ethernet ports before entering the platform qos 10g-only
command, the platform qos 10g-only command shuts down the ports.
When you switch from 10g-only mode to normal mode, you must enter the no shutdown command on
each of the 1-Gigabit Ethernet ports to resume QoS service on those ports.
In 10g-only mode, the 1-Gigabit Ethernet ports are visible, but they remain in an administratively down
state.
The platform qos 10g-only command affects only active and standby supervisors, but if you have four
supervisors you must apply it to the in-chassis standby supervisors.
119
platform qos 10g-only
Examples The following example shows how to place the supervisor engine in the 10g-only mode:
Router# configure terminal
Router(config)# platform qos 10g-only
120
platform qos aggregate-policer
Syntax Description name Name of the aggregate policer. See the “Usage Guidelines” section for
naming conventions.
rate-bps Maximum bits per second. Range is 32000 to 10000000000.
normal-burst-bytes (Optional) Normal burst bytes. Range is 1000 to 31250000.
maximum-burst-bytes (Optional) Maximum burst bytes. Range is 1000 to 31250000 (if entered,
this value must be set equal to the normal-burst-bytes value).
pir peak-rate-bps (Optional) Keyword and argument that set the peak information rate
(PIR). Range is 32000 to 10000000000. Default is equal to the normal
committed information rate (cir) rate.
121
platform qos aggregate-policer
action-type action (Optional) Action type. This argument can include multiple action types
and corresponding actions to set several actions simultaneously. The
following are valid values:
• conform-action—Specifies the action to be taken when the rate is not
exceeded. Valid actions are as follows:
– drop—Drops the packet.
– set-dscp-transmit value—Sets the DSCP value and sends the
packet. Valid entries are 0 to 63 (differentiated code point value),
af11 to af43 (match packets with specified AF DSCP), cs1 to cs7
(match packets with specified CS DSCP), default, or ef (match
packets with the EF DSCP).
– set-mpls-exp-imposition-transmit number—Sets experimental
(exp) bits at the tag imposition. Valid range is 0 to 7.
– set-prec-transmit—Rewrites packet precedence and sends the
packet.
– transmit—Transmits the packet. This is the default.
• exceed-action—Specifies the action to be taken when QoS values are
exceeded. Valid actions are as follows:
– drop—Drops the packet. This is the default.
– policed-dscp-transmit—Changes the DSCP value according to
the policed-dscp map value and sends the packet.
– transmit—Transmits the packet.
• violate-action—Specifies the action to be taken when QoS values are
violated. Valid actions are as follows:
– drop—Drops the packet.
– policed-dscp-transmit—Changes the DSCP value according to
the policed-dscp map value and sends the packet.
– transmit—Transmits the packet.
122
platform qos aggregate-policer
Usage Guidelines This policer can be shared by different policy map classes and on different interfaces. The Cisco 7600
series router supports up to 1023 aggregates and 1023 policing rules.
The platform qos aggregate-policer command allows you to configure an aggregate flow and a policing
rule for that aggregate. When you enter the rate and burst parameters, the range for the average rate is
32 kbps to 10 Gbps (entered as 32000 and 10000000000) and the range for the burst size is 1 KB (entered
as 1000) to 31.25 MB (entered as 31250000). If you modify an existing aggregate rate limit entry, that
entry is modified in NVRAM and in the Cisco 7600 series router if that entry is currently being used.
Note Because of hardware granularity, the rate value is limited, so the burst that you configure may not be the
value that is used.
When you enter the aggregate policer name, follow these naming conventions:
• Can be a maximum of 31 characters and can include a to z, A to Z, 0 to 9, the dash character (-), the
underscore character (_), and the period character (.).
• Must start with an alphabetic character, and must be unique across all ACLs of all types.
• Case sensitive.
• Must not be a keyword; keywords to avoid are all, default-action, map, help, and editbuffer.
Aggregate policing works independently on each DFC-equipped switching module and independently
on the PFC2, which supports any non-DFC-equipped switching modules. Aggregate policing does not
combine flow statistics from different DFC-equipped switching modules. You can display aggregate
policing statistics for each DFC-equipped switching module, PFC2, and any non-DFC-equipped
switching modules that are supported by the PFC2 by entering the show platform qos aggregate policer
command.
Examples The following example shows how to configure a QoS aggregate policer to allow a maximum of 100000
bits per second with a normal burst byte size of 10000; to set DSCP to 48 when these rates are not
exceeded; and to drop packets when these rates are exceeded:
Router(config)# platform qos aggregate-policer micro-one 100000 10000 conform-action
set-dscp-transmit 48 exceed-action drop
123
platform qos aggregate-policer
124
platform qos marking statistics
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Use the show policy-map interface command to display policy-map statistics.
Examples This example shows how to disable allocation of the policer-traffic class identification with set actions:
Router(config)# platform qos marking statistics
This example shows how to allow allocation of the policer-traffic class identification with set actions:
Router(config)# no platform qos marking statistics
125
platform qos protocol
Syntax Description protocol-name Protocol name. Valid values include the following:
• arp
• bfd-ctrl
• bfd-echo
• bgp
• eigrp
• glbp
• igrp
• isis
• ldp
• nd
• ospf
• rip
• vrrp
pass-through Specifies the pass-through mode.
police rate Specifies the maximum bits per second (bps) to be policed. Valid values are from
32000 to 4000000000.
burst (Optional) Normal burst bytes. Valid values are from 1000 to 31250000.
precedence value Specifies the IP-precedence value of the protocol packets to rewrite. Valid values
are from 0 to 7.
126
platform qos protocol
Usage Guidelines This command does not support ARP, ISIS, or EIGRP on Cisco 7600 series routers or Catalyst 6500
switches that are configured with a Supervisor Engine 2.
If you enter the precedence value keyword and arguments without entering the police rate burst
keyword and arguments, only the packets from an untrusted port are marked.
You can make the protocol packets avoid the per-interface policy maps by entering the police rate,
pass-through, or precedence value keywords and arguments.
The platform qos protocol command allows you to define the routing-protocol packet policing as
follows:
• When you specify the pass-through mode, the DSCP value does not change and is not policed.
• When you set the police rate, the DSCP value does not change and is policed.
• When you specify the precedence value, the DSCP value changes for the packets that come from
an untrusted port, the class of service (CoS) value that is based on DSCP-to-CoS map changes, and
the traffic is not policed.
• When you specify the precedence value and the police rate, the DSCP value changes, the CoS value
that is based on DSCP-to-CoS map changes, and the DSCP value is policed. In this case, the DSCP
value changes are based on the trust state of the port; the DSCP value is changed only for the packets
that come from an untrusted port.
• If you do not enter a precedence value, the DSCP value is based on whether or not you have enabled
multilayer switching (MLS) QoS as follows:
– If you enabled MLS QoS and the port is untrusted, the internal DSCP value is overwritten to
zero.
– If you enabled MLS QoS and the port is trusted, the incoming DSCP value is maintained.
You can make the protocol packets avoid policing completely if you choose the pass-through mode. If
the police mode is chosen, the committed information rate (CIR) specified is the rate that is used to
police all the specified protocol’s packets, both entering or leaving the Cisco 7600 series router.
To protect the system by ARP broadcast, you can enter the platform qos protocol arp police bps
command.
Examples This example shows how to define the routing-protocol packet policing:
Router(config)# platform qos protocol arp police 43000
This example shows how to define the IP-precedence value of the protocol packets to rewrite:
Router(config)# platform qos protocol bgp precedence 4
This example shows how to define the IP-precedence value of the protocol packets to rewrite and police
the DSCP value:
Router(config)# platform qos protocol bgp precedence 4 police 32000 1200
127
platform qos protocol
128
platform qos rewrite ip dscp
Syntax Description slot slot (Optional) Specifies the slot number. Use the platform qos rewrite ip dscp slot
? command to determine the valid slots for your chassis.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
If you disable ToS-to-DSCP rewrite, and QoS is enabled globally, the following occurs:
• Final ToS-to-DSCP rewrite is disabled, and the DSCP packet is preserved.
• Policing and marking function according to the QoS configuration.
• Marked and marked-down class of service (CoS) is used for queueing.
• In QoS disabled mode, both ToS and CoS are preserved.
The no platform qos rewrite ip dscp command is incompatible with Multiprotocol Label Switching
(MPLS). The default platform qos rewrite ip dscp command must remain enabled in order for the
PFC3BXL or PFC3B to assign the correct MPLS Experimental (EXP) value for the labels that it
imposes. This restriction does not apply to PFC3C or PFC3CXL forward.
The platform qos rewrite ip dscp slot command can be used for disabling ToS-to-DSCP rewrite on
supervisors or DFC line cards. Although the command will be accepted for non-DFC line card slots, it
does not come into effect unless a DFC line card is inserted into that slot.
To disable rewrite on packets that are coming in on non-DFC line cards, disable the rewrite on the
supervisor slots. Note that this disables the rewrite on packets that are coming in on all non-DFC line
cards on the system.
Examples The following example shows how to enable ToS-to-DSCP rewrite in slot 4:
129
platform qos rewrite ip dscp
130
platform qos statistics-export delimiter
Usage Guidelines QoS statistics data export is not supported on Optical Service Module (OSM) interfaces.
You must enable data export globally to set up data export on your Cisco 7600 series router.
Examples This example shows how to set the QoS-statistics data-export field delimiter (a comma) and verify the
configuration:
Router(config)# platform qos statistics-export delimiter ,
131
platform qos statistics-export destination
Command Default The default is none unless syslog is specified. If syslog is specified, the defaults are as follows:
• port is 514.
• facility is local6.
• severity is debug.
Usage Guidelines QoS statistics data export is not supported on Optical Service Module (OSM) interfaces.
Valid facility values are as follows:
• authorization—Security and authorization messages
• cron—Clock daemon
• daemon—System daemon
• kernel—Kernel messages
132
platform qos statistics-export destination
• local0—Local use 0
• local1—Local use 1
• local2—Local use 2
• local3—Local use 3
• local4—Local use 4
• local5—Local use 5
• local6—Local use 6
• local7—Local use 7
• lpr—Line printer subsystem
• mail—Mail system
• news—Network news subsystem
• syslog—Messages that are generated internally by syslog
• user—User-level messages
• uucp—UNIX-to-UNIX Copy Program (UUCP) subsystem
Valid severity levels are as follows:
• alert—Action must be taken immediately
• critical—Critical conditions
• debug—Debug-level messages
• emergency—System is unusable
• error—Error conditions
• informational—Informational
• notice—Normal but significant conditions
• warning—Warning conditions
Examples This example shows how to specify the destination host address and syslog as the UDP port number:
Router(config)# platform qos statistics-export destination 172.20.52.3 syslog
133
platform qos statistics-export interval
Syntax Description interval Export time; valid values are from 30 to 65535 seconds.
Usage Guidelines QoS statistics data export is not supported on Optical Services Module (OSM) interfaces.
The interval valve needs to be short enough to avoid counter wraparound with the activity in your
configuration.
Caution Be careful when decreasing the interval because exporting QoS statistics imposes a significant load on
the Cisco 7600 series router.
Examples This example shows how to set the QoS statistics data-export interval:
Router(config)# platform qos statistics-export interval 250
134
platform rate-limit all
Syntax Description all Specifies rate limiting for unicast and multicast packets.
mtu-failure Enables and sets the rate limiters for MTU-failed packets.
ttl-failure Enables and sets the rate limiters for TTL-failed packets.
pps Packets per second; valid values are from 10 to 1000000 packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
Defaults None
Examples This example shows how to set the TTL-failure limiter for unicast and multicast packets:
Router(config)# platform rate-limit all ttl-failure 15
Router(config)#
135
platform rate-limit layer2
Syntax Description ip-admission pps Specifies the rate limit for IP admission on Layer 2 ports; valid values are from
10 to 1000000 packets per second.
l2pt pps Specifies the rate limit for control packets in Layer 2 with a protocol-tunneling
multicast-MAC address in Layer 2; valid values are from 10 to 1000000 packets
per second.
pdu pps Specifies the rate limit for Bridge Protocol Data Unit (BPDU), Cisco Discovery
Protocol (CDP), Protocol Data Unit (PDU), and VLAN Trunk Protocol (VTP)
PDU Layer 2 control packets; valid values are from 10 to 1000000 packets per
second.
port-security pps Specifies the rate limit for port security traffic; valid values are from 10 to
1000000 packets per second.
unknown pps Specifies the rate limit for unknown unicast flooding on Layer 2 ports; valid
values are from 10 to 1000000 packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
Examples This example shows how to enable and set the rate limiters for the PDU packets in Layer 2:
Router(config)# platform rate-limit layer2 pdu pkt 100 burst 100
136
platform rate-limit multicast
platform rate-limit multicast {flood {byte rate | pkt rate} | flood-ip {byte rate | pkt rate} |
flood-ip-control {byte rate | pkt rate} | ipv4 {connected {byte rate | pkt rate} | ipv6
{connected {byte rate | pkt rate} }
Examples This example shows how to configure the platform rate-limit multicast flood:
Router(config)# platform rate-limit multicast flood pkt 100 burst 100
137
platform rate-limit multicast ipv4
platform rate-limit multicast ipv4 {connected | fib-miss | igmp | ip-option | pim} pps
[packets-in-burst]
Syntax Description connected Enables and sets the rate limiters for multicast packets from directly connected
sources.
fib-miss Enables and sets the rate limiters for the FIB-missed multicast packets.
igmp Enables and sets the rate limiters for the IGMP packets.
ip-option Enables and sets the rate limiters for the multicast packets with IP options.
pim Enables and sets the rate limiters for the multicast packets with PIM options.
pps Packets per second; valid values are from 10 to 1000000 packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
Examples This example shows how to set the rate limiters for the multicast packets from directly connected
sources:
Router(config)# platform rate-limit multicast ipv4 connected pkt 100 burst 100
Router(config)#
138
platform rate-limit multicast ipv6
Syntax Description connected pps Enables and sets the rate limiters for the IPv6 multicast packets from a directly
connected source; valid values are from 10 to 1000000 packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
control-packet Enables and sets the rate limiters for the IPv6 multicast control packets
mld Enables and sets the rate limiters for the IPv6 multicast MLD packets
Examples This example shows how to set the rate limiters for the IPv6 multicast packets from a directly connected
source:
Router(config)#platform rate-limit multicast ipv6 connected pkt 100 burst 100
Router(config)#
139
platform rate-limit unicast acl
platform rate-limit unicast acl {input | mac-pbf | output | vacl-log} pps [packets-in-burst]
no platform rate-limit unicast acl {input | mac-pbf | output | vacl-log} pps [packets-in-burst]
Syntax Description input Specifies the rate limiters for the input ACL-bridged unicast packets.
mac-pbf Specifies the rate limiters for the MAC PBF.
output Specifies the rate limiters for the output ACL-bridged unicast packets.
vacl-log Specifies the rate limiters for the VACL log cases.
pps Packets per second; see the “Usage Guidelines” section for valid values.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
Usage Guidelines Some cases (or scenarios) share the same hardware register. These cases are divided into the following
two groups:
• Group 1:
– Egress ACL-bridged packets
– Ingress ACL-bridged packets
• Group 2:
– RPF failure
– ICMP unreachable for ACL drop
All the components of each group use or share the same hardware register. For example, ACL-bridged
ingress and egress packets use register A. ICMP-unreachable, no-route, and RPF failure use register B.
140
platform rate-limit unicast acl
In most cases, when you change a component of a group, all the components in the group are overwritten
to use the same hardware register as the first component changed. A warning message is printed out each
time that an overwriting operation occurs, but only if you enable the service internal mode.
Examples This example shows how to set the input ACL-bridged packet limiter for unicast packets:
Router(config)# platform rate-limit unicast acl input pkt 100 burst 100
Router(config)#
141
platform rate-limit unicast cef
Syntax Description receive Enables and sets the rate limiters for receive packets.
glean Enables and sets the rate limiters for ARP-resolution packets.
pps Packets per second; valid values are from 0 to 33554431 packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
142
platform rate-limit unicast cef
Examples This example shows how to set the CEF-glean limiter for the unicast packets:
Router(config)# platform rate-limit unicast cef glean 5000
Router(config)#
143
platform rate-limit unicast ip
platform rate-limit unicast ip icmp {redirect | unreachable acl-drop pps | no-route pps}
[packets-in-burst]
Syntax Description arp-inspection Specifies rate limiting for unicast packets with dynamic ARP inspection.
dhcp-snooping Specifies rate limiting for unicast packets with DHCP snooping.
errors Specifies rate limiting for unicast packets with IP checksum and length errors.
features Specifies rate limiting for unicast packets with software-security features in
Layer 3 (for example, authorization proxy, IPsec, and inspection).
options Specifies rate limiting for unicast IPv4 packets with options.
rpf-failure Specifies rate limiting for unicast packets with RPF failures.
pps Packets per second.
packets-in-burst (Optional) Packets in burst; valid values are from 1 to 255.
icmp redirect Specifies rate limiting for unicast packets requiring ICMP redirect.
icmp unreachable Enables and sets the rate limiters for the ICMP unreachables for the
acl-drop pps ACL-dropped packets.
icmp unreachable Enables and sets the rate limiters for the ICMP unreachables for the FIB-miss
no-route pps packets.
144
platform rate-limit unicast ip
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Note When you configure an ICMP rate limiter, and an ICMP redirect occurs, exiting data traffic is dropped
while the remaining traffic on the same interface is forwarded.
Some cases (or scenarios) share the same hardware register. These cases are divided into the following
two groups:
• Group 1:
– Egress ACL-bridged packets
– Ingress ACL-bridged packets
• Group 2:
– IP options
– ICMP unreachable for ACL drop
All the components of each group use or share the same hardware register. For example, ACL-bridged
ingress and egress packets use register A. ICMP-unreachable, no-route, and RPF failure use register B.
In most cases, when you change a component of a group, all the components in the group are overwritten
to use the same hardware register as the first component changed. A warning message is printed out each
time that an overwriting operation occurs, but only if you enable the service internal mode.
Examples This example shows how to set the ICMP-redirect limiter for unicast packets:
Router(config)# platform rate-limit unicast ip option pkt 100 burst 100
Router(config)#
145
platform redundancy bias
Syntax Description bias milliseconds Specifies the platform redundancy bias time in milliseconds. Range is
11–3600.
Examples This example shows the platform redundancy bias time in 20 milliseconds:
Router(config)# platform redundancy bias 20
146
platform software
platform software
To enable ACL or QoS configuration on the software platform, use the platform software command.
Defaults None
Examples This example shows how to enable syslog rate limiting for ACL:
Router(config)# platform software acl log-update rate-limit-msg enable
147
platform software met profile
Syntax Description value Sets the percentage allocation for each block size; valid values are 0 to 100
percent.
Defaults The default values are 10 30 50 10 for each of the block sizes.
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.
Examples This example shows how to set the block percentage for 4 blocks:
Router# platform software met profile 20 20 10 50
148
platform system-controller reset-threshold
Syntax Description threshold-num Specifies the threshold reset number; valid values are 1 to 100.
• If the system controller reset threshold has been reached, the supervisor engine reloads and this
message is displayed.
%SYSTEM_CONTROLLER-<>-ERROR
%SYSTEM_CONTROLLER-<>-FATAL
Examples This example shows how to configure the system controller reset threshold to 55:
Router(config)# platform system-controller reset-threshold 55
149
platform verify
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.
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.
Examples This example shows how to enable Layer 3 error checking in the hardware:
Router(config)# platform verify ip checksum
150
platform verify
Router(config)#
This example shows how to disable Layer 3 error checking in the hardware:
Router(config)# no platform verify ip checksum
Router(config)#
151
platform xconnect l2gre tunnel
Syntax Description interface-num Specifies the tunnel interface number; valid values are 0 to 2147483647.
Examples The following example shows the how to configure the l2gre tunnel to 6:
Router # platform xconnect l2gre tunnel 6
152
police
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 Description bps Average rate, in bits per second. Valid values are 8000 to 200000000.
burst-normal (Optional) Normal burst size in bytes. Valid values are 1000 to 51200000.
Default normal burst size is 1500.
burst-max (Optional) Maximum burst size, in bytes. Valid values are 1000 to 51200000.
Default varies by platform.
conform-action Specifies action to take on packets that conform to the rate limit.
exceed-action Specifies action to take on packets that exceed the rate limit.
violate-action (Optional) Specifies action to take on packets that violate the normal and
maximum burst sizes.
153
police
154
police
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
155
police
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.
156
police
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.
157
police
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.
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).
158
police
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.
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.
Router(config)# class-map match-all vlan-inner-100
Router(config-cmap)# match vlan inner 100
Router(config-cmap)# exit
Router(config)# policy-map vlan-inner-100
Router(config-pmap)# class vlan-inner-100
Router(config-pmap-c)# police 500000 1000 1500 conform-action set-cos-inner-transmit 3
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface atm3/0/0
Router(config-if)# pvc 100/100
Router(config-if-atm-vc)# bridge-domain 100 dot1q
Router(config-if-atm-vc)# service-policy output vlan-inner-100
Router(config-if-atm-vc)# end
159
police
160
port-channel hash-distribution
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.
Syntax Description adaptive Specifies selective distribution of the bundle select register among the
port-channel members.
fixed Specifies fixed distribution of the bundle select register among the port-channel
members.
default Specifies the default setting.
Command Default In Cisco IOS Release 12.2(50)SY or later releases, the hash distribution algorithm method is set to
adaptive. In earlier releases, the hash distribution algorithm method is set to fixed.
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.
Examples The following example shows how to set the hash distribution algorithm method to adaptive:
Router(config)# port-channel hash-distribution adaptive
161
priority-queue cos-map
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]]]]]]]
no priority-queue cos-map
Command Default The default mapping is queue 1 is mapped to CoS 5 for the following receive and transmit strict-priority
queues:
• 1p1q4t receive queues
• 1p1q0t receive queues
• 1p1q8t receive queues
• 1p2q2t transmit queues
• 1p3q8t transmit queues
• 1p7q8t transmit queues
• 1p3q1t transmit queues
• 1p2q1t transmit queues
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.
162
priority-queue cos-map
When mapping CoS values to the strict-priority queues, note the following information:
• The queue number is always 1.
• You can enter up to 8 CoS values to map to the queue.
Examples This example shows how to map CoS value 7 to the strict-priority queues on Gigabit Ethernet port 1/1:
Router(config-if)# priority-queue cos-map 1 7
Router(config-if)#
163
priority-queue queue-limit
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.
Syntax Description percent Priority-queue size in percent; valid values are from 1 to 100.
Command Default When global quality of service (QoS) is enabled the priority-queue size is 15. When global QoS is
disabled the priority-queue size is 0.
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.
1. 1p2q1t—One strict-priority queue, two standard queues with one WRED drop threshold and one
non-configurable (100%) tail-drop threshold per queue.
2. 1p3q8t—One strict-priority queue, three standard queues with eight WRED drop thresholds per queue.
3. 1p7q8t—One strict-priority queue, seven standard queues with eight WRED drop thresholds per queue.
4. 1p7q4t—One strict-priority queue, seven standard queues with four WRED drop thresholds per queue.
164
priority-queue queue-limit
• WS-SUP32-GB-3E—1p3q8t
• WS-X6708-10GE—1p7q4t
Examples The following example shows how to set the priority-queue size on an interface:
priority-queue queue-limit 15
165
queue-buffers ratio
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.
Syntax Description number Sets the size of the queue ratio; valid range is 0 to 100.
Examples The following example shows how to configure the buffer ratio to 6:
Router(config-pmap-c)# queue-buffers ratio 6
166
rcv-queue bandwidth
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.
no rcv-queue bandwidth
Syntax Description weight-1 ... weight-n WRR weights; valid values are from 0 to 255.
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.
This command is supported on 2q8t and 8q8t ports only.
You can configure up to seven queue weights.
167
rcv-queue bandwidth
168
rcv-queue cos-map
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.
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.
169
rcv-queue cos-map
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.
Use this command on trusted ports only.
Examples This example shows how to map the CoS values 0 and 1 to threshold 1 in the standard receive queue:
Router (config-if)# rcv-queue cos-map 1 1 0 1
cos-map configured on: Gi1/1 Gi1/2
170
rcv-queue queue-limit
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.
no rcv-queue queue-limit
Syntax Description q-limit-1 Standard queue weight; valid values are from 1 and 100 percent.
q-limit-2 Strict-priority queue weight; see the “Usage Guidelines” section for valid
values.
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 from 1 to 100 percent, except on 1p1q8t ingress LAN ports, where
valid values for the strict-priority queue are from 3 to 100 percent.
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.
171
rcv-queue queue-limit
Examples This example shows how to set the receive-queue size ratio for Gigabit Ethernet interface 1/2:
Router# configure terminal
Router(config)# interface gigabitethernet 1/2
Router(config-if)# rcv-queue queue-limit 75 15
Router(config-if)# end
172
rcv-queue random-detect
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.
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.
173
rcv-queue random-detect
For additional information on configuring receive-queue thresholds, refer to the QoS chapter in the
Cisco 7600 Series Router Cisco IOS Software Configuration Guide.
Examples This example shows how to configure the low-priority receive-queue thresholds:
Router (config-if)# rcv-queue random-detect max-threshold 1 60 100
174
rcv-queue threshold
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.
no rcv-queue threshold
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:
• 1p1q4t interfaces have this default drop-threshold configuration:
– 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.
• 1p1q0t interfaces have this default drop-threshold configuration:
– 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.
175
rcv-queue threshold
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.
Examples This example shows how to configure the receive-queue drop thresholds for Gigabit Ethernet
interface 1/1:
Router(config-if)# rcv-queue threshold 1 60 75 85 100
176
show fips
show fips
To display the FIPs information about the switch, use the show fips command in EXEC mode.
show fips
no show fips
Examples This example shows how to displays if FIPS modes if running on a switch:
Router# show fips
Router# The FIPS mode is on.
Router#
177
show interfaces
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
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}]
Syntax Description type (Optional) Interface type. Allowed values for type can be
atm, async, auto-template, bvi, bri0, ctunnel,
container, dialer, e1, esconPhy, ethernet, fastethernet,
fcpa, fddi, filter, filtergroup, gigabitethernet, ge-wan,
hssi, longreachethernet, loopback, mfr, module,
multilink, null, pos, port-channel, port-group,
pos-channel, sbc, sdcc, serial, sysclock, t1,
tengigabitethernet, token, tokenring, tunnel, vif, vmi,
virtual-access, virtual-ppp, virtual-template,
virtual-tokenring. voaBypassIn, voaBypassOut,
voaFilterIn, voaFilterOut, voaIn, voaOut.
Note The type of interfaces available is based on the
type of router used.
number (Optional) Port number on the selected interface.
178
show interfaces
first last (Optional) For Cisco 2500 series routers, ISDN Basic
Rate Interfae (BRI) only. The first argument can be either
1 or 2. The last argument can only be 2, indicating B
channels 1 and 2.
D-channel information is obtained by using the command
without the optional arguments.
accounting (Optional) Displays the number of packets of each
protocol type that have been sent through the interface.
counters protocol status (Optional) Displays the current status of the protocol
counters enabled.
crb (Optional) Displays interface routing or bridging
information.
dampening (Optional) Displays interface dampening information.
description (Optional) Displays the interface description.
dot1ad (Optional) Displays interface 802.1ad information.
etherchannel [module number] (Optional) Displays interface Ether Channel information.
• module—The module keyword limits the display to
interfaces available on the module.
fair-queue (Optional) Displays interface Weighted Fair Queueing
(WFQ) information.
irb (Optional) Displays interface routing or bridging
information.
mac-accounting (Optional) Displays interface MAC accounting
information.
mpls-exp (Optional) Displays interface Multiprotocol Label
Switching (MPLS) experimental accounting information.
precedence (Optional) Displays interface precedence accounting
information.
random-detect (Optional) Displays interface Weighted Random Early
Detection (WRED) information.
rate-limit (Optional) Displays interface rate-limit information.
stats (Optional) Displays interface packets and octets, in and
out, by using switching path.
summary (Optional) Displays an interface summary.
switching (Optional) Displays interface switching.
null interface-number (Optional) Specifies the null interface, that is 0.
slot (Optional) Slot number.
Refer to the appropriate hardware manual for slot
information.
/port (Optional) Port number.
Refer to the appropriate hardware manual for port
information.
/port-adapter (Optional) Port adapter number. Refer to the appropriate
hardware manual for information about port adapter
compatibility.
179
show interfaces
180
show interfaces
181
show interfaces
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE to
support SPAs on the Cisco 7600 series routers and Catalyst 6500 series
switches.
12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S to support
SPAs on the Cisco 12000 series routers, and the tengigabitethernet interface
type was added. 10-Gigabit Ethernet interfaces were introduced with the
release of the 1-Port 10-Gigabit Ethernet SPA.
12.2(18)SXF This command was integrated into Cisco IOS Release 12.2(18)SXF.
12.2(33)SXJ01 This command was integrated into Cisco IOS Release 12.2(33)SXJ01.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SRB1 This command was updated to display operational status for Gigabit Ethernet
interfaces that are configured as primary and backup interfaces (Cisco 7600
series routers).
12.2(31)SB This command was integrated in Cisco IOS Release 12.2(31)SB.
12.2(33)SB This command was modified. The default value of the command was modified
on the Cisco 10000 series router for the PRE3 and PRE4.
Cisco IOS XE This command was implemented on Cisco ASR 1000 Series Aggregation
Release 2.5 Services Routers.
12.2(50)SY This command was integrated in Cisco IOS Release 12.2(50)SY and the
dot1ad keyword was added.
15.0(01)SY This command was integrated in Cisco IOS Release 15.1(50)SY.
182
show interfaces
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.
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.
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.”
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.
183
show interfaces
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.
184
show interfaces
Table 2 describes the input queue and output queue fields shown in the preceding two displays.
Field Description
Input Queue
size Current size of the input queue.
max Maximum size of the queue.
drops Number of messages discarded in this interval.
Total output drops Total number of messages discarded in this session.
Output Queue
size Current size of the output queue.
threshold Congestive-discard threshold. Number of messages in the
queue after which new messages for high-bandwidth
conversations are dropped.
drops Number of dropped messages.
Conversations: active Number of currently active conversations.
Conversations: max active Maximum number of concurrent conversations allowed.
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.
185
show interfaces
• Novell
• Serial Tunnel Synchronous Data Link Control (SDLC)
• Spanning Tree
• SR Bridge
• Transparent Bridge
186
show interfaces
Field Description
Timers (msec) List of timers in milliseconds.
poll pause, fair poll, Poll limit Current values of these timers.
T1, N1, N2, K Current values for these variables.
187
show interfaces
Table 4 shows other data given for each SDLC secondary interface configured to be attached to this
interface.
Table 4 SDLC Field Descriptions
Field Description
addr Address of this secondary interface.
State Current state of this connection. The possible values follow:
• BOTHBUSY—Both sides have told each other that they are temporarily
unable to receive any more information frames.
• CONNECT—A normal connect state exists between this router and this
secondary.
• DISCONNECT—No communication is being attempted to this
secondary.
• DISCSENT—This router has sent a disconnect request to this secondary
and is awaiting its response.
• ERROR—This router has detected an error, and is waiting for a response
from the secondary acknowledging this.
• SNRMSENT—This router has sent a connect request (SNRM) to this
secondary and is awaiting its response.
• THEMBUSY—This secondary has told this router that it is temporarily
unable to receive any more information frames.
• USBUSY—This router has told this secondary that it is temporarily
unable to receive any more information frames.
VS Sequence number of the next information frame this station sends.
VR Sequence number of the next information frame from this secondary that this
station expects to receive.
RCNT Number of correctly sequenced I-frames received when the Cisco IOS
software was in a state in which it is acceptable to receive I-frames.
Remote VR Last frame transmitted by this station that has been acknowledged by the
other station.
Current retransmit Number of times the current I-frame or sequence of I-frames has been
count retransmitted.
Hold queue Number of frames in hold queue/Maximum size of hold queue.
IFRAMEs, RNRs, Sent and received count for these frames.
SNRMs, DISCs
Poll “Set” if this router has a poll outstanding to the secondary; “clear” if it does
not.
Poll count Number of polls, in a row, given to this secondary at this time.
chain Shows the previous (p) and next (n) secondary address on this interface in
the round-robin loop of polled devices.
188
show interfaces
Ethernet0
Protocol Pkts In Chars In Pkts Out Chars Out
IP 873171 735923409 34624 9644258
Novell 163849 12361626 57143 4272468
DEC MOP 0 0 1 77
ARP 69618 4177080 1529 91740
Interface Serial0 is disabled
Ethernet1
Protocol Pkts In Chars In Pkts Out Chars Out
IP 0 0 37 11845
Novell 0 0 4591 275460
DEC MOP 0 0 1 77
ARP 0 0 7 420
Fddi0
Protocol Pkts In Chars In Pkts Out Chars Out
Novell 0 0 183 11163
ARP 1 49 0 0
When the output indicates that an interface is “disabled,” the router has received excessive errors (over
5000 in a keepalive period).
Hardware is HD64570
Internet address is 10.1.2.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
Reliability 255/255, txload 237/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive not set
Last input 00:00:22, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:17:58
Input queue: 0/75/0 (size/max/drops); Total output drops: 2479
Queueing strategy: random early detection(RED)
flows (active/max active/max): 8/9/16
mean queue depth: 27
drops: class random tail min-th max-th mark-prob
0 946 0 20 40 1/10
189
show interfaces
1 488 0 22 40 1/10
2 429 0 24 40 1/10
3 341 0 26 40 1/10
4 235 0 28 40 1/10
5 40 0 31 40 1/10
6 0 0 33 40 1/10
7 0 0 35 40 1/10
rsvp 0 0 37 40 1/10
30 second input rate 1000 bits/sec, 2 packets/sec
30 second output rate 119000 bits/sec, 126 packets/sec
1346 packets input, 83808 bytes, 0 no buffer
Received 12 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
84543 packets output, 9977642 bytes, 0 underruns
0 output errors, 0 collisions, 6 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
190
show interfaces
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:
Router# show interfaces dialer0
At the end of the Dialer0 output, the show interfaces command is executed on each physical interface
bound to it.
191
show interfaces
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.
Router# show interfaces bri0:1
Any protocol configuration and states should be displayed from the Dialer0 interface.
192
show interfaces
Field Description
Fast Ethernet...is up Indicates whether the interface hardware is currently active and if it has
...is administratively down been taken down by an administrator.
line protocol is Indicates whether the software processes that handle the line protocol
consider the line usable or if it has been taken down by an
administrator.
Hardware Hardware type (for example, SPA-4FE-7304) and MAC address.
Description Alphanumeric string identifying the interface. This appears only if the
description interface configuration command has been configured on
the interface.
Internet address Internet address followed by subnet mask.
MTU Maximum transmission unit of the interface. The default is 1500 bytes
for the 4-Port 10/100 Fast Ethernet SPA.
BW Bandwidth of the interface in kilobits per second.
RxBW Receiver bandwidth of the interface, in kilobits per second. This value
is displayed only when an interface has asymmetric receiver and
transmitter rates.
DLY Delay of the interface in microseconds.
reliability Reliability of the interface as a fraction of 255 (255/255 is 100 percent
reliability), calculated as an exponential average over 5 minutes.
193
show interfaces
Field Description
txload, rxload Load on the interface (in the transmit “tx” and receive “rx” directions)
as a fraction of 255 (255/255 is completely saturated), calculated as an
exponential average over 5 minutes.
Encapsulation Encapsulation method assigned to the interface.
loopback Indicates whether loopback is set.
Keepalive Indicates whether keepalives are set, and the time interval.
Half-duplex, Full-duplex Indicates the duplex mode for the interface.
100Mb/s, 10Mb/s Speed of the interface in megabits per second.
100BaseTX/FX Media protocol standard.
ARP type: Type of ARP assigned and the timeout period.
Last input Number of hours, minutes, and seconds since the last packet was
successfully received by an interface and processed locally on the
router. Useful for knowing when a dead interface failed.
This field is not updated by fast-switched traffic.
output Number of hours, minutes, and seconds since the last packet was
successfully transmitted by the interface. Useful for knowing when a
dead interface failed.
output hang Number of hours, minutes, and seconds (or never) since the interface
was last reset because of a transmission that took too long. When the
number of hours in any of the “last” fields exceeds 24 hours, the
number of days and hours is displayed. If that field overflows, asterisks
are printed.
Note This field does not apply to SPA interfaces.
Last clearing Time at which the counters that measure cumulative statistics (such as
number of bytes transmitted and received) shown in this report were
last reset to zero. Note that variables that might affect routing (for
example, load and reliability) are not cleared when the counters are
cleared.
A series of asterisks (***) indicates the elapsed time is too large to be
displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less
than 232 ms) ago.
Input queue Packet statistics on the input queue reported as:
(size/max/drops/flushes)
• Size—Number of packets in the input queue.
• Max—Maximum size of the queue.
• Drops—Number of packets dropped because of a full input queue.
• Flushes—Number of packets dropped as part of selective packet
discard (SPD). SPD implements a selective packet drop policy on
the router’s IP process queue. Therefore, it applies only to
process-switched traffic.
Total output drops Total number of packets dropped because of a full output queue.
194
show interfaces
Field Description
Queueing strategy Type of Layer 3 queueing active on this interface. The default is
first-in, first-out (FIFO).
Output queue (size/max) Number of packets in the output queue (size), and the maximum size of
the queue (max).
5 minute input rate, Average number of bits and packets transmitted per second in the last
5 minute output rate 5 minutes. If the interface is not in promiscuous mode, it senses
network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an
approximation of traffic per second during a given 5-minute period.
These rates are exponentially weighted averages with a time constant
of 5 minutes. A period of four time constants must pass before the
average will be within two percent of the instantaneous rate of a
uniform stream of traffic over that period.
packets input Total number of error-free packets received by the system.
bytes Total number of bytes, including data and MAC encapsulation, in the
error-free packets received by the system.
Received...broadcasts Total number of broadcast or multicast packets received by the
interface.
runts Number of packets that are discarded because they are smaller than the
minimum packet size of the medium. For instance, any Ethernet packet
that is smaller than 64 bytes is considered a runt.
giants Number of packets that are discarded because they exceed the
maximum packet size of the medium. For example, any Ethernet packet
that is larger than 1536 bytes is considered a giant.
Note For the 4-Port 10/100 Fast Ethernet SPA, the default is that a
giant is any packet greater than 1536 bytes. However, if you
modify the maximum transmission unit (MTU) for the
interface, this counter increments when you exceed the
specified MTU for the interface.
throttles Number of times the receiver on the port was disabled, possibly
because of buffer or processor overload.
input errors Includes runts, giants, no buffer, cyclic redundancy check (CRC),
frame, overrun, and ignored counts. Other input-related errors can also
cause the input errors count to be increased, and some datagrams may
have more than one error; therefore, this sum may not balance with the
sum of enumerated input error counts.
CRC Cyclic redundancy check generated by the originating LAN station or
far-end device does not match the checksum calculated from the data
received. On a LAN, this usually indicates noise or transmission
problems on the LAN interface or the LAN bus itself. A high number
of CRCs is usually the result of collisions or a station transmitting bad
data.
195
show interfaces
Field Description
frame Number of packets received incorrectly having a CRC error and a
noninteger number of octets. On a LAN, this is usually the result of
collisions or a malfunctioning Ethernet device.
overrun Number of times the receiver hardware was unable to hand received
data to a hardware buffer because the input rate exceeded the receiver’s
ability to handle the data.
ignored Number of received packets ignored by the interface because the
interface hardware ran low on internal buffers. These buffers are
different than the system buffers. Broadcast storms and bursts of noise
can cause the ignored count to be increased.
watchdog Number of times the watchdog receive timer expired. Expiration
happens when receiving a packet with a length greater than 2048 bytes.
input packets with dribble Dribble bit error indicates that a frame is slightly too long. This frame
condition detected error counter is incremented for informational purposes only; the
router accepts the frame.
packets output Total number of messages transmitted by the system.
bytes Total number of bytes, including data and MAC encapsulation,
transmitted by the system.
underruns Number of times that the transmitter has been running faster than the
router can handle.
output errors Sum of all errors that prevented the final transmission of datagrams out
of the interface being examined. Note that this may not balance with
the sum of the enumerated output errors, because some datagrams may
have more than one error and others may have errors that do not fall
into any of the specifically tabulated categories.
collisions Number of messages retransmitted because of an Ethernet collision.
This is usually the result of an overextended LAN (Ethernet or
transceiver cable too long, more than two repeaters between stations,
or too many cascaded multiport transceivers). A packet that collides is
counted only once in output packets.
interface resets Number of times an interface has been completely reset. This can
happen if packets queued for transmission were not sent within several
seconds. Interface resets can occur when an interface is looped back or
shut down.
babbles Transmit jabber timer expired.
late collision Number of late collisions. Late collision happens when a collision
occurs after transmitting the preamble.
deferred Number of times that the interface had to defer while ready to transmit
a frame because the carrier was asserted.
lost carrier Number of times the carrier was lost during transmission.
196
show interfaces
Field Description
no carrier Number of times the carrier was not present during the transmission.
Note This field does not apply to SPA interfaces.
output buffer failures, output These counters are not used by the 4-Port 10/100 Fast Ethernet SPA on
buffers swapped out the 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:
Router# show interfaces gigabitEthernet 3/0/0
197
show interfaces
.
.
.
Table 6 describes the fields shown in the display for Gigabit Ethernet SPA interfaces.
Field Description
GigabitEthernet...is up Indicates whether the interface hardware is currently active and if it has
...is administratively down been taken down by an administrator.
line protocol is Indicates whether the software processes that handle the line protocol
consider the line usable or if it has been taken down by an
administrator.
Hardware Hardware type (for example, SPA-2GE-7304) and MAC address.
Backup interface Identifies the backup interface that exists for this, the primary interface.
Failure and secondary delay The period of time (in seconds) to delay bringing up the backup
interface when the primary goes down, and bringing down the backup
after the primary becomes active again. On the Cisco 7600 router, the
delay must be 0 (the default) to ensure that there is no delay between
when the primary goes down and the backup comes up, and vice versa.
Standby mode Indicates that this is a backup interface and that it is currently operating
in standby mode.
Description Alphanumeric string identifying the interface. This appears only if the
description interface configuration command has been configured on
the interface.
Internet address Internet address followed by subnet mask.
MTU Maximum transmission unit of the interface. The default is 1500 bytes
for the 2-Port 10/100/1000 Gigabit Ethernet SPA.
BW Bandwidth of the interface in kilobits per second.
DLY Delay of the interface in microseconds.
reliability Reliability of the interface as a fraction of 255 (255/255 is 100 percent
reliability), calculated as an exponential average over 5 minutes.
txload, rxload Load on the interface (in the transmit “tx” and receive “rx” directions)
as a fraction of 255 (255/255 is completely saturated), calculated as an
exponential average over 5 minutes.
Encapsulation Encapsulation method assigned to the interface.
loopback Indicates whether loopback is set.
Keepalive Indicates whether keepalives are set, and the time interval.
Half-duplex, Full-duplex Indicates the duplex mode for the interface.
1000Mb/s, 100Mb/s, 10Mb/s Speed of the interface in megabits per second.
link type Specifies whether autonegotiation is being used on the link.
media type Interface port media type: RJ45, SX, LX, or ZX.
100BaseTX/FX Media protocol standard.
ARP type: Type of ARP assigned and the timeout period.
198
show interfaces
Field Description
Last input Number of hours, minutes, and seconds since the last packet was
successfully received by an interface and processed locally on the
router. Useful for knowing when a dead interface failed.
This field is not updated by fast-switched traffic.
output Number of hours, minutes, and seconds since the last packet was
successfully transmitted by the interface. Useful for knowing when a
dead interface failed.
output hang Number of hours, minutes, and seconds (or never) since the interface
was last reset because of a transmission that took too long. When the
number of hours in any of the “last” fields exceeds 24 hours, the
number of days and hours is displayed. If that field overflows, asterisks
are printed.
Note This field does not apply to SPA interfaces.
Last clearing Time at which the counters that measure cumulative statistics (such as
number of bytes transmitted and received) shown in this report were
last reset to zero. Note that variables that might affect routing (for
example, load and reliability) are not cleared when the counters are
cleared.
A series of asterisks (***) indicates the elapsed time is too large to be
displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less
than 232 ms) ago.
Input queue Packet statistics on the input queue reported as:
(size/max/drops/flushes)
• Size—Number of packets in the input queue.
• Max—Maximum size of the queue.
• Drops—Number of packets dropped because of a full input queue.
• Flushes—Number of packets dropped as part of SPD. SPD
implements a selective packet drop policy on the router’s IP
process queue. Therefore, it applies only to process-switched
traffic.
Total output drops Total number of packets dropped because of a full output queue.
Queueing strategy Type of Layer 3 queueing active on this interface. The default is FIFO.
Output queue (size/max) Number of packets in the output queue (size), and the maximum size of
the queue (max).
5 minute input rate, Average number of bits and packets transmitted per second in the last
5 minute output rate 5 minutes. If the interface is not in promiscuous mode, it senses
network traffic it sends and receives (rather than all network traffic).
The 5-minute input and output rates should be used only as an
approximation of traffic per second during a given 5-minute period.
These rates are exponentially weighted averages with a time constant
of 5 minutes. A period of four time constants must pass before the
average will be within two percent of the instantaneous rate of a
uniform stream of traffic over that period.
199
show interfaces
Field Description
packets input Total number of error-free packets received by the system.
bytes Total number of bytes, including data and MAC encapsulation, in the
error-free packets received by the system.
Received...broadcasts Total number of broadcast or multicast packets received by the
interface.
runts Number of packets that are discarded because they are smaller than the
minimum packet size of the medium. For instance, any Ethernet packet
that is smaller than 64 bytes is considered a runt.
giants Number of packets that are discarded because they exceed the
maximum packet size of the medium. For example, any Ethernet packet
that is larger than 1536 bytes is considered a giant.
Note For the 2-Port 10/100/1000 Gigabit Ethernet SPA, the default is
that a giant is any packet greater than 1536 bytes. However, if
you modify the MTU for the interface, this counter increments
when you exceed the specified MTU for the interface.
throttles Number of times the receiver on the port was disabled, possibly
because of buffer or processor overload.
input errors Includes runts, giants, no buffer, CRC, frame, overrun, and ignored
counts. Other input-related errors can also cause the input errors count
to be increased, and some datagrams may have more than one error;
therefore, this sum may not balance with the sum of enumerated input
error counts.
CRC Cyclic redundancy check generated by the originating LAN station or
far-end device does not match the checksum calculated from the data
received. On a LAN, this usually indicates noise or transmission
problems on the LAN interface or the LAN bus itself. A high number
of CRCs is usually the result of collisions or a station transmitting bad
data.
frame Number of packets received incorrectly having a CRC error and a
noninteger number of octets. On a LAN, this is usually the result of
collisions or a malfunctioning Ethernet device.
overrun Number of times the receiver hardware was unable to hand received
data to a hardware buffer because the input rate exceeded the receiver’s
ability to handle the data.
ignored Number of received packets ignored by the interface because the
interface hardware ran low on internal buffers. These buffers are
different than the system buffers. Broadcast storms and bursts of noise
can cause the ignored count to be increased.
watchdog Number of times the watchdog receive timer expired. Expiration
happens when receiving a packet with a length greater than 2048 bytes.
input packets with dribble Dribble bit error indicates that a frame is slightly too long. This frame
condition detected error counter is incremented for informational purposes only; the
router accepts the frame.
packets output Total number of messages transmitted by the system.
200
show interfaces
Field Description
bytes Total number of bytes, including data and MAC encapsulation,
transmitted by the system.
underruns Number of times that the transmitter has been running faster than the
router can handle.
output errors Sum of all errors that prevented the final transmission of datagrams out
of the interface being examined. Note that this may not balance with
the sum of the enumerated output errors, because some datagrams may
have more than one error and others may have errors that do not fall
into any of the specifically tabulated categories.
collisions Number of messages retransmitted because of an Ethernet collision.
This is usually the result of an overextended LAN (Ethernet or
transceiver cable too long, more than two repeaters between stations,
or too many cascaded multiport transceivers). A packet that collides is
counted only once in output packets.
interface resets Number of times an interface has been completely reset. This can
happen if packets queued for transmission were not sent within several
seconds. Interface resets can occur when an interface is looped back or
shut down.
babbles Transmit jabber timer expired.
late collision Number of late collisions. Late collision happens when a collision
occurs after transmitting the preamble.
deferred Number of times that the interface had to defer while ready to transmit
a frame because the carrier was asserted.
lost carrier Number of times the carrier was lost during transmission.
no carrier Number of times the carrier was not present during the transmission.
Note This field does not apply to SPA interfaces.
output buffer failures, output These counters are not used by the 2-Port 10/100/1000 Gigabit
buffers swapped out Ethernet SPA on the Cisco 7304 router.
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):
Router# show interfaces pos 4/3/0
201
show interfaces
Field Description
POS4/3/0 is up, line protocol is up Indicates whether the interface hardware is currently active and
can transmit and receive or whether it has been taken down by
an administrator.
Hardware is. . . Hardware type:
• For POSIP—cyBus Packet over SONET
• For POS SPAs—Packet over SONET
Internet address is Internet address and subnet mask.
MTU Maximum transmission unit of the interface.
BW Bandwidth of the interface, in kilobits per second.
DLY Delay of the interface, in microseconds.
rely Reliability of the interface as a fraction of 255 (255/255 is
100 percent reliability), calculated as an exponential average
over 5 minutes.
load Load on the interface as a fraction of 255 (255/255 is completely
saturated), calculated as an exponential average over 5 minutes.
The calculation uses the value from the bandwidth interface
configuration command.
Encapsulation Encapsulation method assigned to the interface.
Loopback Indicates whether loopbacks are set.
Keepalive Indicates whether keepalives are set.
Scramble Indicates whether SONET payload scrambling is enabled.
SONET scrambling is disabled by default. For the POS SPAs on
the Cisco 12000 series routers, scrambling is enabled by default.
Last input Number of hours, minutes, and seconds since the last packet was
successfully received by an interface and processed locally on
the router. Useful for knowing when a dead interface failed. This
counter is updated only when packets are process-switched, not
when packets are fast-switched.
(Last) output Number of hours, minutes, and seconds since the last packet was
successfully transmitted by an interface. This counter is updated
only when packets are process-switched, not when packets are
fast-switched.
202
show interfaces
Field Description
(Last) output hang Number of hours, minutes, and seconds (or never) since the
interface was last reset because of a transmission that took too
long. When the number of hours in any of the “last” fields
exceeds 24 hours, the number of days and hours is printed. If
that field overflows, asterisks are printed.
Last clearing Time at which the counters that measure cumulative statistics
(such as number of bytes transmitted and received) shown in this
report were last reset to zero. Note that variables that might
affect routing (for example, load and reliability) are not cleared
when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 2231 ms
(and less than 232 ms) ago.
Queueing strategy FIFO queueing strategy (other queueing strategies you might see
are priority-list, custom-list, and weighted fair).
Output queue, drops Number of packets in output and input queues. Each number is
input queue, drops followed by a slash, the maximum size of the queue, and the
number of packets dropped because a queue was full.
5 minute input rate Average number of bits and packets received or transmitted per
5 minute output rate second in the last 5 minutes.
packets input Total number of error-free packets received by the system.
bytes (input) Total number of bytes, including data and MAC encapsulation,
in the error-free packets received by the system.
no buffer Number of received packets discarded because there was no
buffer space in the main system. Compare with number of
packets ignored. Broadcast storms on Ethernets and bursts of
noise on serial lines are often responsible for no input buffer
events.
broadcasts Total number of broadcast or multicast packets received by the
interface.
runts Number of packets that are discarded because they are smaller
than the minimum packet size of the medium.
giants Number of packets that are discarded because they exceed the
maximum packet size of the medium.
throttles Not supported for POS interfaces.
parity Report of the parity errors on the interface.
input errors Total number of no buffer, runts, giants, CRCs, frame, overrun,
ignored, and abort counts. Other input-related errors can also
increment the count, so that this sum might not balance with the
other counts.
203
show interfaces
Field Description
CRC Cyclic redundancy checksum generated by the originating LAN
station or far-end device does not match the checksum
calculated from the data received. On a LAN, this usually
indicates noise or transmission problems on the LAN interface
or the LAN bus itself. A high number of CRCs is usually the
result of collisions or a station transmitting bad data. On a serial
link, CRCs usually indicate noise, gain hits, or other
transmission problems on the data link.
frame Number of packets received incorrectly having a CRC error and
a noninteger number of octets. On a serial line, this is usually the
result of noise or other transmission problems.
overrun Number of times the serial receiver hardware was unable to hand
received data to a hardware buffer because the input rate
exceeded the receiver’s ability to handle the data.
ignored Number of received packets ignored by the interface because the
interface hardware ran low on internal buffers. These buffers are
different than the system buffers mentioned previously in the
buffer description. Broadcast storms and bursts of noise can
cause the ignored count to be incremented.
abort Illegal sequence of one bits on the interface.
packets output Total number of messages transmitted by the system.
bytes (output) Total number of bytes, including data and MAC encapsulation,
transmitted by the system.
underruns Number of times that the far-end transmitter has been running
faster than the near-end router’s receiver can handle.
output errors Sum of all errors that prevented the final transmission of
datagrams out of the interface being examined. Note that this
might not balance with the sum of the enumerated output errors,
because some datagrams can have more than one error, and
others can have errors that do not fall into any of the specifically
tabulated categories.
applique Indicates an unrecoverable error has occurred on the POSIP
applique. The system then invokes an interface reset.
interface resets Number of times an interface has been completely reset. This
can happen if packets queued for transmission were not sent
within a certain interval. If the system notices that the carrier
detect line of an interface is up, but the line protocol is down, it
periodically resets the interface in an effort to restart it. Interface
resets can also occur when an unrecoverable interface processor
error occurred, or when an interface is looped back or shut down.
output buffer failures Not supported for POS interfaces.
output buffers swapped out Not supported for POS interfaces.
carrier transitions Number of times the carrier detect signal of the interface has
changed state.
204
show interfaces
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/0
205
show interfaces
Field Description
SDCC1/1/0 is administratively Indicates whether the interface hardware is currently active and
down, line protocol is down can transmit and receive or whether it has been taken down by
an administrator.
Hardware is. . . Hardware type is SDCC—Section Data Communications
Channel.
Internet address is Internet address and subnet mask.
MTU Maximum transmission unit of the interface.
BW Bandwidth of the interface, in kilobits per second.
DLY Delay of the interface, in microseconds.
rely Reliability of the interface as a fraction of 255 (255/255 is
100 percent reliability), calculated as an exponential average
over 5 minutes.
load Load on the interface as a fraction of 255 (255/255 is completely
saturated), calculated as an exponential average over 5 minutes.
The calculation uses the value from the bandwidth interface
configuration command.
Encapsulation Encapsulation method assigned to the interface.
crc Cyclic redundancy check size (16 or 32 bits).
Loopback Indicates whether loopback is set.
Keepalive Indicates whether keepalives are set.
Last input Number of hours, minutes, and seconds since the last packet was
successfully received by an interface and processed locally on
the router. Useful for knowing when a dead interface failed. This
counter is updated only when packets are process-switched, not
when packets are fast-switched.
(Last) output Number of hours, minutes, and seconds since the last packet was
successfully transmitted by an interface. This counter is updated
only when packets are process-switched, not when packets are
fast-switched.
(Last) output hang Number of hours, minutes, and seconds (or never) since the
interface was last reset because of a transmission that took too
long. When the number of hours in any of the “last” fields
exceeds 24 hours, the number of days and hours is printed. If
that field overflows, asterisks are printed.
206
show interfaces
Field Description
Last clearing Time at which the counters that measure cumulative statistics
(such as number of bytes transmitted and received) shown in this
report were last reset to zero. Note that variables that might
affect routing (for example, load and reliability) are not cleared
when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 2231 ms
(and less than 232 ms) ago.
Queueing strategy FIFO queueing strategy (other queueing strategies you might see
are priority-list, custom-list, and weighted fair).
Output queue, drops Number of packets in output and input queues. Each number is
input queue, drops followed by a slash, the maximum size of the queue, and the
number of packets dropped because a queue was full.
5 minute input rate Average number of bits and packets received or transmitted per
5 minute output rate second in the last 5 minutes.
packets input Total number of error-free packets received by the system.
bytes (input) Total number of bytes, including data and MAC encapsulation,
in the error-free packets received by the system.
no buffer Number of received packets discarded because there was no
buffer space in the main system. Compare with number of
packets ignored. Broadcast storms on Ethernets and bursts of
noise on serial lines are often responsible for no input buffer
events.
broadcasts Total number of broadcast or multicast packets received by the
interface.
runts Number of packets that are discarded because they are smaller
than the minimum packet size of the medium.
giants Number of packets that are discarded because they exceed the
maximum packet size of the medium.
throttles Not supported for POS interfaces.
parity Report of the parity errors on the interface.
input errors Total number of no buffer, runts, giants, CRCs, frame, overrun,
ignored, and abort counts. Other input-related errors can also
increment the count, so that this sum might not balance with the
other counts.
CRC Cyclic redundancy checksum generated by the originating LAN
station or far-end device does not match the checksum
calculated from the data received. On a LAN, this usually
indicates noise or transmission problems on the LAN interface
or the LAN bus itself. A high number of CRCs is usually the
result of collisions or a station transmitting bad data. On a serial
link, CRCs usually indicate noise, gain hits, or other
transmission problems on the data link.
207
show interfaces
Field Description
frame Number of packets received incorrectly having a CRC error and
a noninteger number of octets. On a serial line, this is usually the
result of noise or other transmission problems.
overrun Number of times the serial receiver hardware was unable to hand
received data to a hardware buffer because the input rate
exceeded the receiver’s ability to handle the data.
ignored Number of received packets ignored by the interface because the
interface hardware ran low on internal buffers. These buffers are
different than the system buffers mentioned previously in the
buffer description. Broadcast storms and bursts of noise can
cause the ignored count to be incremented.
abort Illegal sequence of one bits on the interface.
packets output Total number of messages transmitted by the system.
bytes (output) Total number of bytes, including data and MAC encapsulation,
transmitted by the system.
underruns Number of times that the far-end transmitter has been running
faster than the near-end router’s receiver can handle.
output errors Sum of all errors that prevented the final transmission of
datagrams out of the interface being examined. Note that this
might not balance with the sum of the enumerated output errors,
because some datagrams can have more than one error, and
others can have errors that do not fall into any of the specifically
tabulated categories.
collisions Not supported for POS interfaces.
interface resets Number of times an interface has been completely reset. This
can happen if packets queued for transmission were not sent
within a certain interval. If the system notices that the carrier
detect line of an interface is up, but the line protocol is down, it
periodically resets the interface in an effort to restart it. Interface
resets can also occur when an unrecoverable interface processor
error occurred, or when an interface is looped back or shut down.
output buffer failures Not supported for POS interfaces.
output buffers swapped out Not supported for POS interfaces.
carrier transitions Number of times the carrier detect signal of the interface has
changed state.
208
show interfaces
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.
Field Description
Serial Name of the serial interface.
line protocol is If the line protocol is up, the local router has received
keepalive packets from the remote router. If the line protocol
is down, the local router has not received keepalive packets
form the remote router.
Hardware is Designates the specific hardware type of the interface.
Internet address is The IP address of the interface.
MTU The maximum packet size set for the interface.
BW Bandwidth in kilobits per second.
DLY Interface delay in microseconds.
reliability Reliability of the interface as a fraction of 255 (255/255 is
100 percent reliability), calculated as an exponential average
over 5 minutes.
txload Transmit load on the interface as a fraction of 255 (255/255
is completely saturated), calculated as an exponential average
over 5 minutes.
rxload Receive load on the interface as a fraction of 255 (255/255 is
completely saturated), calculated as an exponential average
over 5 minutes.
Encapsulation Encapsulation method.
crc CRC size in bits.
loopback Indicates whether loopback is set.
209
show interfaces
Field Description
keepalive Indicates whether keepalives are set.
Last input Number of hours, minutes, and seconds since the last packet
was successfully received by an interface and processed
locally on the router. Useful for knowing when a dead
interface failed. This counter is updated only when packets
are process-switched, not when packets are fast-switched.
Last output Number of hours, minutes, and seconds since the last packet
was successfully transmitted by an interface. Useful for
knowing when a dead interface failed. This counter is
updated only when packets are process-switched, not when
packets are fast-switched.
output hang Number of hours, minutes, and seconds (or never) since the
interface was last reset because of a transmission that took
too long. When the number of hours in any of the “last” fields
exceeds 24 hours, the number of days and hours is printed. If
that field overflows, asterisks are printed.
Last clearing of show interface Time at which the counters that measure cumulative statistics
counters (such as number of bytes transmitted and received) shown in
this report were last reset to zero. Note that variables that
might affect routing (for example, load and reliability) are not
cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231
milliseconds (and less than 232 ms) ago.
Input queue Packet statistics on the input queue reported as:
• Size—Current size of the input queue.
• Max—Maximum size of the input queue.
• Drops—Packets dropped because the queue was full.
• Flushes—Number of times that data on queue has been
discarded.
Total output drops Total number of dropped packets.
Queueing strategy FIFO queueing strategy (other queueing strategies you might
see are priority-list, custom-list, and weighted fair).
Output queue Number of packets in the output queue (size), and the
maximum size of the queue (max).
210
show interfaces
Field Description
5-minute input rate Average number of bits and packets received per second in
the last 5 minutes. If the interface is not in promiscuous
mode, it senses network traffic it sends and receives (rather
than all network traffic).
The 5-minute input and output rates should be used only as
an approximation of traffic per second during a given
5-minute period. These rates are exponentially weighted
averages with a time constant of 5 minutes. A period of four
time constants must pass before the average will be within
two percent of the instantaneous rate of a uniform stream of
traffic over that period.
5-minute output rate Average number of bits and packets transmitted per second in
the last 5 minutes. If the interface is not in promiscuous
mode, it senses network traffic it sends and receives (rather
than all network traffic).
The 5-minute input and output rates should be used only as
an approximation of traffic per second during a given
5-minute period. These rates are exponentially weighted
averages with a time constant of 5 minutes. A period of four
time constants must pass before the average will be within
two percent of the instantaneous rate of a uniform stream of
traffic over that period.
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/0
211
show interfaces
Field Description
TenGigabitEthernet...is up Indicates whether the interface hardware is currently active
...is administratively down and if it has been taken down by an administrator.
line protocol is Indicates whether the software processes that handle the line
protocol consider the line usable or if it has been taken down
by an administrator.
Hardware Hardware type and MAC address.
Description Alphanumeric string identifying the interface. This appears
only if the description interface configuration command has
been configured on the interface.
Internet address Internet address followed by subnet mask.
MTU Maximum transmission unit of the interface.
BW Bandwidth of the interface in kilobits per second.
DLY Delay of the interface in microseconds.
reliability Reliability of the interface as a fraction of 255 (255/255 is
100 percent reliability), calculated as an exponential average
over 5 minutes.
txload, rxload Load on the interface (in the transmit “tx” and receive “rx”
directions) as a fraction of 255 (255/255 is completely
saturated), calculated as an exponential average over
5 minutes.
Encapsulation Encapsulation method assigned to the interface.
loopback Indicates whether loopback is set.
Keepalive Indicates whether keepalives are set, and the time interval.
Half-duplex, Full-duplex Indicates the duplex mode for the interface.
10Gb/s Speed of the interface in Gigabits per second.
input flow control ... Specifies if input flow control is on or off.
ARP type: Type of ARP assigned and the timeout period.
Last input Number of hours, minutes, and seconds since the last packet
was successfully received by an interface and processed
locally on the router. Useful for knowing when a dead
interface failed.
This field is not updated by fast-switched traffic.
212
show interfaces
Field Description
output Number of hours, minutes, and seconds since the last packet
was successfully transmitted by the interface. Useful for
knowing when a dead interface failed.
output hang Number of hours, minutes, and seconds (or never) since the
interface was last reset because of a transmission that took
too long. When the number of hours in any of the “last” fields
exceeds 24 hours, the number of days and hours is displayed.
If that field overflows, asterisks are printed.
Last clearing Time at which the counters that measure cumulative statistics
(such as number of bytes transmitted and received) shown in
this report were last reset to zero. Note that variables that
might affect routing (for example, load and reliability) are not
cleared when the counters are cleared.
A series of asterisks (***) indicates the elapsed time is too
large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms
(and less than 232 ms) ago.
Input queue (size/max/drops/flushes) Packet statistics on the input queue reported as:
• Size—Number of packets in the input queue.
• Max—Maximum size of the queue.
• Drops—Number of packets dropped because of a full
input queue.
• Flushes—Number of packets dropped as part of SPD.
SPD implements a selective packet drop policy on the
router’s IP process queue. Therefore, it applies only to
process-switched traffic.
Total output drops Total number of packets dropped because of a full output
queue.
Queueing strategy Type of Layer 3 queueing active on this interface. The default
is FIFO.
Output queue (size/max) Number of packets in the output queue (size), and the
maximum size of the queue (max).
5 minute input rate, Average number of bits and packets transmitted per second in
5 minute output rate the last 5 minutes. If the interface is not in promiscuous
mode, it senses network traffic it sends and receives (rather
than all network traffic).
The 5-minute input and output rates should be used only as
an approximation of traffic per second during a given
5-minute period. These rates are exponentially weighted
averages with a time constant of 5 minutes. A period of four
time constants must pass before the average will be within
two percent of the instantaneous rate of a uniform stream of
traffic over that period.
213
show interfaces
Field Description
L2 Switched Provides statistics about Layer 2 switched traffic, including
unicast and multicast traffic.
L3 in Switched Provides statistics about received Layer 3 traffic.
L3 out Switched Provides statistics about sent Layer 3 traffic.
packets input Total number of error-free packets received by the system.
bytes Total number of bytes, including data and MAC
encapsulation, in the error-free packets received by the
system.
Received...broadcasts Total number of broadcast or multicast packets received by
the interface.
runts Number of packets that are discarded because they are
smaller than the minimum packet size of the medium.
giants Number of packets that are discarded because they exceed the
maximum packet size of the medium.
throttles Number of times the receiver on the port was disabled,
possibly because of buffer or processor overload.
input errors Includes runts, giants, no buffer, CRC, frame, overrun, and
ignored counts. Other input-related errors can also cause the
input errors count to be increased, and some datagrams may
have more than one error; therefore, this sum may not balance
with the sum of enumerated input error counts.
CRC Cyclic redundancy check generated by the originating LAN
station or far-end device does not match the checksum
calculated from the data received. On a LAN, this usually
indicates noise or transmission problems on the LAN
interface or the LAN bus itself. A high number of CRCs is
usually the result of collisions or a station transmitting bad
data.
frame Number of packets received incorrectly having a CRC error
and a noninteger number of octets. On a LAN, this is usually
the result of collisions or a malfunctioning Ethernet device.
overrun Number of times the receiver hardware was unable to hand
received data to a hardware buffer because the input rate
exceeded the receiver’s ability to handle the data.
ignored Number of received packets ignored by the interface because
the interface hardware ran low on internal buffers. These
buffers are different than the system buffers. Broadcast
storms and bursts of noise can cause the ignored count to be
increased.
watchdog Number of times the watchdog receive timer expired.
multicast Number of multicast packets.
pause input Number of pause packets received.
214
show interfaces
Field Description
input packets with dribble condition Dribble bit error indicates that a frame is slightly too long.
detected This frame error counter is incremented for informational
purposes only; the router accepts the frame.
packets output Total number of messages transmitted by the system.
bytes Total number of bytes, including data and MAC
encapsulation, transmitted by the system.
underruns Number of times that the transmitter has been running faster
than the router can handle.
output errors Sum of all errors that prevented the final transmission of
datagrams out of the interface being examined. Note that this
may not balance with the sum of the enumerated output
errors, because some datagrams may have more than one
error and others may have errors that do not fall into any of
the specifically tabulated categories.
collisions Number of messages retransmitted because of an Ethernet
collision. This is usually the result of an overextended LAN
(Ethernet or transceiver cable too long, more than two
repeaters between stations, or too many cascaded multiport
transceivers). A packet that collides is counted only once in
output packets.
interface resets Number of times an interface has been completely reset. This
can happen if packets queued for transmission were not sent
within several seconds. Interface resets can occur when an
interface is looped back or shut down.
babbles Transmit jabber timer expired.
late collision Number of late collisions. Late collision happens when a
collision occurs after transmitting the preamble.
deferred Number of times that the interface had to defer while ready
to transmit a frame because the carrier was asserted.
lost carrier Number of times the carrier was lost during transmission.
no carrier Number of times the carrier was not present during the
transmission.
pause output Number of pause packets transmitted.
output buffer failures, output buffers Number of output butters failures and output buffers swapped
swapped out out.
215
show interfaces
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.
216
show interfaces
Command Description
show controllers fastethernet Displays Fast Ethernet interface information, transmission statistics
and errors, and applicable MAC destination address and VLAN
filtering tables.
show controllers Displays Gigabit Ethernet interface information, transmission
gigabitethernet statistics and errors, and applicable MAC destination address and
VLAN filtering tables.
show controllers pos Displays information about the POS controllers.
show controllers serial Displays controller statistics.
217
show ip cef platform
Syntax Description ip-prefix [mask] The IP address prefix of the entries to display. You can also include an
optional subnet mask.
checksum (Optional) Displays FIB entry checksums information.
detail (Optional) Displays detailed FIB entry information.
internal {checksum} (Optional) Displays internal data structures. The checksum option includes FIB
entry checksums information in the output.
Examples The following example shows FIB entry information for IP address prefix 10.4.4.4:
Router# show ip cef 10.4.4.4 platform
10.4.4.4/32
Fib Entry: 0xD6680610 XCM leaf from 0x50805550(RP) 0xA0805550(FP):
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
Label object OCE Chain:
Label(0x12, real) Adjacency
c10k_label_data = 0x450467F8
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
218
show ip cef platform
219
show ipv6 cef platform
Usage Guidelines If none of the optional keywords are used, data for all of the platforms is displayed.
Examples The following example displays all platform-specific Cisco Express Forwarding data:
Router# show ipv6 cef platform
220
show mac address-table
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 number | 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 address mac-addr (Optional) Displays information about the MAC address table for a
specific MAC address. See the “Usage Guidelines” section for formatting
information.
all (Optional) Displays every instance of the specified MAC address in the
forwarding table.
interface type/number (Optional) Displays addresses for a specific interface; valid values are
atm, fastethernet, gigabitethernet, and port-channel.
module number (Optional) Displays information about the MAC address table for a
specific Distributed Forwarding Card (DFC) module.
vlan vlan-id (Optional) Displays addresses for a specific VLAN, valid values are from
1 to 4094.
count (Optional) Displays the number of entries that are currently in the MAC
address table.
limit Displays MAC-usage information.
multicast Displays information about the multicast MAC address table entries only.
igmp-snooping Displays the addresses learned by Internet Group Management Protocol
(IGMP) snooping.
mld-snooping Displays the addresses learned by Multicast Listener Discover version 2
(MLDv2) snooping.
user Displays the manually entered (static) addresses.
notification mac-move Displays the MAC-move notification status.
notification mac-move (Optional) Displays the number of times a MAC has moved and the
counter number of these instances that have occurred in the system.
notification threshold Displays the Counter-Addressable Memory (CAM) table utilization
notification status.
notification change Displays the MAC notification parameters and history table.
synchronize statistics Displays information about the statistics collected on the switch
processor or DFC.
unicast-flood Displays unicast-flood information.
221
show mac address-table
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:
• Number of messages processed at each time interval.
• Number of active entries sent for synchronization.
• Number of entries updated, created, ignored, or failed.
222
show mac address-table
Examples The following is sample output from the show mac address-table command:
Switch# show mac address-table
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:
Router# show mac address-table address 001.6441.60ca
This example shows how to display MAC address table information for a specific MAC address with a
Supervisor Engine 720:
Router# show mac address-table address 0100.5e00.0128
223
show mac address-table
This example shows how to display the currently configured aging time for all VLANs:
Router# show mac address-table aging-time
This example shows how to display the entry count for a specific slot:
Router# show mac address-table count module 1
This example shows how to display the information about the MAC address table for a specific interface
with a Supervisor Engine 720:
Router# show mac address-table interface fastethernet 6/45
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:
Router# show mac address-table limit vlan 1 module 1
The following example shows how to display the MAC-move notification status:
Router# show mac address-table notification mac-move
The following example shows how to display the MAC move statistics:
Router> show mac address-table notification mac-move counter
224
show mac address-table
-----------------------------------------------------------------------------------
Vlan Mac Address From Mod/Port To Mod/Port Count
---- ----------------- ----------------------- ----------------------- ------------
1 00-01-02-03-04-01 2/3 3/1 10
20 00-01-05-03-02-01 5/3 5/1 20
This example shows how to display the MAC notification parameters and history table:
Router# show mac address-table notification change
This example shows how to display the MAC notification parameters and history table for a specific
interface:
Router# show mac address-table notification change interface gigabitethernet5/2
225
show mac address-table
This example shows how to display the information about the MAC address table for a specific VLAN:
Router# show mac address-table vlan 1300
This example shows how to display the information about the MAC address table for MLDv2 snooping:
Router# show mac address-table multicast mld-snooping
226
show mac address-table aging-time
Syntax Description vlan vlan-id (Optional) Specifies a VLAN; valid values are from 1 to 1005.
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.
Router# show mac address-table aging-time
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.
Router# show mac address-table aging-time vlan 100
227
show mac address-table aging-time
Command Description
show mac address-table static Displays static MAC address table entries only.
show mac address-table vlan Displays the MAC address table information for a specific
VLAN.
228
show mac address-table dynamic
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 address mac-addr (Optional) Specifies a 48-bit MAC address; valid format is H.H.H.
interface interface (Optional) Specifies an interface to match. Valid type values are
interface-num FastEthernet and GigabitEthernet, valid number values are from 1 to 9.
all (Optional) Specifies that the output display all dynamic MAC address
table entries.
module num (Optional) Displays information about the MAC address table for a
specific Distributed Forwarding Card (DFC) module.
vlan vlan- (Optional) Displays entries for a specific VLAN; valid values are from 1
to 1005.
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.
Router# show mac address-table dynamic vlan 200 all
This example shows how to display all the dynamic MAC address entries.
Router# show mac address-table dynamic
229
show mac address-table dynamic
------+----------------+--------+-----+----------+--------------------------
* 10 0010.0000.0000 dynamic Yes n/a Gi4/1
* 3 0010.0000.0000 dynamic Yes 0 Gi4/2
* 1 0002.fcbc.ac64 dynamic Yes 265 Gi8/1
* 1 0009.12e9.adc0 static No - Router
Router#
230
show mac address-table learning
show mac address-table learning [vlan vlan-id | interface interface slot/port] [module num]
Syntax Description vlan vlan-id (Optional) Displays information about the MAC address learning state for the
specified switch port VLAN; valid values are from 1 to 4094.
interface (Optional) Displays information about the MAC address learning state for the
interface specified routed interface type, the slot number, and the port number.
slot/port
module num (Optional) Displays information about the MAC address learning state for the
specified module number.
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.
231
show mac address-table learning
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:
Router# show mac address-table learning
Router#
Field Description
VLAN/Interface1 VLAN ID or interface type, module, and port number.
Mod# Module number of a supervisor engine or DFC.
yes MAC address learning is enabled.
no MAC address learning is disabled.
1. The interfaces displayed are routed interfaces that have internal VLANs assigned to them.
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:
Router# show mac address-table learning module 4
VLAN/Interface Mod4
-------------------- -----
1 yes
100 yes
150 yes
200 yes
250 yes
1006 no
1007 no
1008 no
232
show mac address-table learning
1009 no
1010 no
1011 no
1012 no
1013 no
1014 no
GigabitEthernet6/1 no
GigabitEthernet6/2 no
GigabitEthernet6/4 no
FastEthernet3/4 no
FastEthernet3/5 no
GigabitEthernet4/1 no
GigabitEthernet4/2 no
GigabitEthernet7/1 no
GigabitEthernet7/2 no
Router#
This example shows how to display the status of MAC address learning for a specific VLAN on all the
supervisor engines and DFCs:
Router# show mac address-table learning vlan 100
This example shows how to display the status of MAC address learning for a specific VLAN on a specific
supervisor engine or DFC:
Router# show mac address-table learning vlan 100 module 7
VLAN Mod7
---- -----
100 yes
Router
This example shows how to display the status of MAC address learning for a specific supervisor engine
or DFC:
Router# show mac address-table learning interface FastEthernet 3/4
This example shows how to display the status of MAC address learning for a specific interface on a
specific supervisor engine or DFC:
Router# show mac address-table learning interface FastEthernet 3/4 module 1
Interface Mod1
--------- -----
Fa3/4 no
Router
233
show mac address-table static
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 address mac-address (Optional) Specifies a 48-bit MAC address to match; valid format is H.H.H.
aging-type routed-mac (Optional) Specifies the routed MAC address status.
detail (Optional) Specifies a detailed display of MAC address table information.
interface type number (Optional) Specifies an interface to match; valid type values are Ethernet,
FastEthernet, and Gigabit Ethernet and valid number values are from 1 to 9.
module number (Optional) Specifies a module to match; valid values are from 1 to 4.
notification change (Optional) Specifies the MAC address notification parameters and history
table.
notification mac-move (Optional) Specifies status for the MAC address move notifications.
synchornize statistics (Optional) Specifies the statistics for MAC address synchronzation.
vlan vlan (Optional) Displays entries for a specific VLAN; valid values are from 1 to
1005.
Usage Guidelines The keyword definitions for the protocol argument are:
• ip—Specifies IP protocol.
• ipx—Specifies Internetwork Packet Exchange (IPX) protocols.
• assigned—Specifies assigned protocol entries.
• other—Specifies other protocol entries.
Examples The followig examples shows how to display the static MAC address entries:
Router# show mac address-table static
234
show mac address-table static
The following example shows the detailed output for the previous example:
Router# show mac address-table static protocol assigned detail
STATIC NO NO NO NO NO assigned NO
Bit Not On 0 0050.3e8d.6400 254 100 1 0 0x3
STATIC NO NO NO NO NO assigned NO
Bit Not On 0 0050.3e8d.6400 254 5 1 0 0x3
235
show mac address-table static
Command Description
show mac address-table protocol Displays MAC address table information based on protocol.
show mac address-table vlan Displays the MAC address table information for a specific
VLAN.
236
show mvr
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.
show mvr
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).
237
show mvr interface
Syntax Description interface-id (Optional) Displays MVR type, status, and Immediate Leave setting for the
interface; valid interfaces include physical ports (including type, stack
member [stacking-capable switches only] module, and port number).
members (Optional) Displays all MVR groups to which the specified interface
belongs.
vlan vlan-id (Optional) Displays all MVR group members on this VLAN. The range is 1
to 4094.
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:
Switch# show mvr interface
Port Type Status Immediate Leave
---- ---- ------- ---------------
Gi1/0/1 SOURCE ACTIVE/UP DISABLED
Gi1/0/2 RECEIVER ACTIVE/DOWN DISABLED
This is an example of output from the show mvr interface command for a specified port:
Switch# show mvr interface gigabitethernet1/0/2
Type: RECEIVER Status: ACTIVE Immediate Leave: DISABLED
238
show mvr interface
This is an example of output from the show mvr interface interface-id members command:
Switch# show mvr interface gigabitethernet1/0/2 members
239.255.0.0 DYNAMIC ACTIVE
239.255.0.1 DYNAMIC ACTIVE
239.255.0.2 DYNAMIC ACTIVE
239.255.0.3 DYNAMIC ACTIVE
239.255.0.4 DYNAMIC ACTIVE
239.255.0.5 DYNAMIC ACTIVE
239.255.0.6 DYNAMIC ACTIVE
239.255.0.7 DYNAMIC ACTIVE
239.255.0.8 DYNAMIC ACTIVE
239.255.0.9 DYNAMIC ACTIVE
239
show mvr members
Syntax Description ip-address (Optional) The IP multicast address. If the address is entered, all receiver and
source ports that are members of the multicast group appear. If no address is
entered, all members of all Multicast VLAN Registration (MVR) groups are
listed. If a group has no members, the group is listed as Inactive.
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.
<output truncated>
This example shows the status of an IP address and the members of the IP multicast group with that IP
address:
Switch# show mvr members 239.255.0.2
239.255.003.--22 ACTIVE Gi1//1(d), Gi1/0/2(d), Gi1/0/3(d),
Gi1/0/4(d), Gi1/0/5(s)
240
show mvr members
Command Description
mvr (global configuration) Enables and configures multicast VLAN registration on the
switch.
mvr (interface configuration) Configures MVR ports.
show mvr Displays the global MVR configuration on the switch.
show mvr interface Displays the configured MVR interfaces, status of the specified
interface, or all multicast groups to which the interface belongs
when the members keyword is appended to the command.
241
show platform acl
Syntax
Description software-switched Displays the ACL software-switched setting.
Defaults None
242
show platform acl software-switched
Usage Guidelines By default, ACLs are not applied to packets that are software-switched between WAN cards and the route
processor. To determine whether ACLs are enabled for software-switched ingress or egress WAN
packets, use the show platform acl software-switched command.
Examples This example shows how to display whether ACLs are enabled for software-switched WAN packets:
Router# show platform acl software-switched
CWAN: ACL treatment for software switched in INGRESS is enabled
CWAN: ACL treatment for software switched in EGRESS is disabled
243
show platform bridge
Examples The following is sample output from the show platform bridge command:
Router# show platform bridge
244
show platform bridge
Field Description
VLAN The VLAN for which bridging is configured.
Interface The WAN interface on which bridging is configured. This can
be an ATM, Gigabit Ethernet, PoS, or serial interface.
CircuitId The circuit ID. The range is from 0 to 65536.
LTL The local target logic (LTL) of the interface. LTL is 13-bits
long.
The format is eee ssss pppppp (e=extended port bits, s=slot
bits, p=port bits).
Extended bits along with port bits identify the pseudoport and
slot bits identifies the slot.
PseudoPort In the case of FlexWAN, the port numbering is from 133 to
192 for Bay 0 and 197 to 256 for Bay 1. There are 60 ports
per packet processing engine (PPE). For the SIP200, the
pseudoports are in the range of 137 to 256.
State State indicates the status of the physical interface on which
bridging is configured. The state is either up or down. If the
state is down, then there is a problem and debugging needs to
be done.
Options Options specify whether split-horizon is enabled on the WAN
interface. This can be access, default, dot1q, or dot1q-tunnel.
245
show platform cfib
246
show platform cfm
Examples The following is sample output from the show platform cfm info command. The field descriptions are
self-explanatory.
Router# show platform cfm info
CFM is disabled
CFM unicast MAC 00d0.2b6c.b103, CFM multicast MAC 0180.c200.0030, AEB multicast MAC
0100.0ccc.ccc0
CFM Ingress Control Packet System Statistics:
Current software Rate Limit Setting: 1100 pkts/sec
Statistics are collected in intervals of 3 seconds.
Allow the first 3300 packets to pass each interval, drop thereafter
Current Ingress Count in this interval: 0 pkts
In this interval have we Exceeded Rate and Dropped pkts: NO
For the last 3 intervals the maximum sample had 0 packets in one interval.
247
show platform cts reflector interface
Examples This example shows how to display the platform CTS reflector interface configuration for
tengigabitethernet interface number 4:
Router(config)# show platform cts reflector interface tengigabitethernet 4
248
show platform datapath qos
show platform datapath qos {cos | ingress-interface | last | lif | packet-data | pkt-length | recirc
| src-index}
Examples This example shows how to display QoS packet data from the last data path capture:
Router# show platform datapath qos last
249
show platform eobc crs-delay
Examples This example shows how to display EOBC CRS delay on the platform:
Router# show platform eobc crs-delay
250
show platform feature-manager consistency-check
show platform feature-manager consistency-check {all | log | now {all |default-in | default-out
| dynamic | rbacl | static}
Syntax Description all Displays all of the logs in memory from the consistency checker.
log Displays logs from the most recent operation of consistency checker.
now Processes the consistency checker now and displays the logs.
default-in Processes it for the default non-permit results ingress direction.
default-out Processes it for the default non-permit results egress direction.
dynamic Processes it for the dynamic features.
rbacl Processes it for the RBACL feature.
static Processes it for the static features.
Defaults None.
Examples This example shows how to display the all of the platform-specific feature manager consistency checker
configurations:
Router# show platform feature-manager consistency-check all
251
show platform flow
show platform flow {aging | export {instance number | module number} | ip {count {instance
number | module number} | destination ip address | instance number | module number |
multicast | protocol number | source ip address} | ipv6 {count {instance number | module
number} | destination ip address | instance number | module number | multicast | protocol
number | source ip address} | layer2 {count {instance number | module number} | instance
number | module number} | multicast | protocol number | source ip address} | mpls {count
{instance number | module number} | instance number | module number} | table-contention
{aggregate {instance number | module number} | detailed {instance number | module
number} | summary {instance number | module number}} | usage {instance number | module
number}}
252
show platform flow
Examples This example shows how to display the NetFlow usage on module 4:
Router# show platform flow usage module 4
253
show platform flow export
Examples The following example displays the feature-related information for NDE:
Router(config)# show platform flow export module 4
Yielding NDE is enabled.
Supervisor CPU threshold = 50
Linecard CPU threshold = 70
Module/Instance 1 :
---------------------
No of flows read and exported = 1802384
No of flows discarded = 5230
No of capture+purge requests = 23049
No of purge-only requests = 120
Module/Instance 5 :
---------------------
No of flows read and exported = 1
No of flows discarded = 0
No of capture+purge requests = 13481
No of purge-only requests = 11
lionel#
lionel#
lionel#sh pla flow exp mod 1
Yielding NDE is enabled.
Supervisor CPU threshold = 50
Linecard CPU threshold = 70
Module/Instance 1 :
---------------------
No of flows read and exported = 1802384
No of flows discarded = 5230
254
show platform flow export
255
show platform hardware acl accounting
show platform hardware acl accounting {index {number | range number}} | interface {async
number | auto-template number | ctunnel number | dialer number | esconphy number | filter
number | filtergroup number | gigabitethernet number | longreachethernet number |
loopback number | mfr number | multilink number | null number | port-channel number |
portgroup number | pos-channel number | sysclock number | tengigabitethernet number |
tunnel number | vif number | virtual-template number | virtual-tokenring number | vlan
vlan_id | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
256
show platform hardware acl accounting
virtual-tokenring Specifies the virtual Token Ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the Fibre Channel interface number. Range is 1–6.
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass-out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
Defaults None
Examples This example shows how to display the ACL accounting statistics for VOA bypass-out interface number
4:
Router# show platform hardware acl accounting interface voabypassout 4
257
show platform hardware acl acct-xlt-tbl
show platform hardware acl acct-xlt-tbl {in {index {number | range number}} | out {index
{number | range number}}}
Syntax Description in Displays the accounting table entries that are available inside the ACL.
index Displays the accounting table.
number Displays the accounting table index.
range number Displays the particular accounting table. Range is 0–255.
out Displays the accounting table entries that are sent outside the ACL.
Defaults None
Examples This example shows how to display the accounting XLT entries that are sent outside the ACL:
Router# show platform hardware acl acct-xlt-tbl out index
258
show platform hardware acl adj-rit
show platform hardware acl adj-rit {interface {async number | auto-template number | ctunnel
number | dialer number | esconphy number | filter number | filtergroup number |
gigabitethernet number | longreachethernet number | loopback number | mfr number |
multilink number | null number | port-channel number | portgroup number | pos-channel
number | sysclock number | tengigabitethernet number | tunnel number | vif number |
virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane number |
fcpa number | voabypassin number | voabypassout number | voafilterin number | voafilterout
number | voain number | voaout number}}
259
show platform hardware acl adj-rit
Defaults None
Examples This example shows how to display the adjacency entries for ACL asynchronous interface 4:
Router# show platform hardware acl adj-rit interface async 4
260
show platform hardware acl capmap tcam
show platform hardware acl capmap tcam {A {index number | module number} | B {index
number | module number}}
Defaults None
Examples This example shows how to display the TCAM A cap map entry index number 20:
Router# show platform hardware acl capmap tcam A Index 20
261
show platform hardware acl config-registers
Defaults None
Examples This example shows how to display the hardware classify block register for module 4:
Router# show platform hardware acl config-registers module 4
262
show platform hardware acl destinfo
show platform hardware acl destinfo {in {index number | module number} | out {index number
| module number} | module number}
Defaults None
Examples This example shows how to display the ACL destination information for inbound entries in module 4:
Router# show platform hardware acl destinfo in module 4
263
show platform hardware acl diagnostics
Defaults None
Examples This example shows how to display the hardware ACL diagnostics for module 4:
Router# show platform hardware acl diagnostics module 4
264
show platform hardware acl entry
show platform hardware acl entry {compaction {module number}} | global-qos {in {arp {detail
| module number} | ip {detail | module number} | ipv6 {detail | module number} | mac {detail
| module number} | mpls {detail | module number}} | out {arp {detail | module number} | ip
{detail | module number} | ipv6 {detail | module number} | mac {detail | module number} |
mpls {detail | module number}} | interface {async number | auto-template number | ctunnel
number | dialer number | esconphy number | filter number | filtergroup number |
gigabitethernet number | longreachethernet number | loopback number | mfr number |
multilink number | null number | port-channel number | portgroup number | pos-channel
number | sysclock number | tengigabitethernet number | tunnel number | vif number |
virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane number |
cts-reflector number | fcpa number | voabypassin number | voabypassout number |
voafilterin number | voafilterout number | voain number | voaout number}} | rbacl {all
{module number} | default {ip {module number} | ipv6 {module number}} | tcam {A {all
{module number} | index number} | B {all {module number} | index number}}}
265
show platform hardware acl entry
mfr number Specifies the multilink Frame Relay bundle interface number. Range is
1–2147483647.
multilink number Specifies the multilink group interface number. Range is 1–2147483647.
null number Specifies the null interface number. Range is 0–0.
port-channel number Specifies the Ethernet channel of interfaces. Range is 1–496.
portgroup number Specifies the port group interface number.
pos-channel number Specifies the PoS channel of interfaces. Range is 1–4094.
sysclock number Specifies the telecom bus clock controller interface number.
tengigabitethernet Specifies the 10-Gigabit Ethernet interface number.
number
tunnel number Specifies the tunnel interface number. Range is 1–2147483647.
vif number Specifies the PGM multicast host interface number. Range is 1–1.
virtual-template Specifies the virtual template interface number. Range is 1–200.
number
virtual-tokenring Specifies the virtual Token Ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
control-plane Specifies the control plane interface number.
number
cts-reflector number Specifies the CTS reflector interface number.
fcpa number Specifies the Fibre Channel interface number.
voabypassin number Specifies the VOA bypass-in interface number.
voabypassout Specifies the VOA bypass-out interface number.
number
voafilterin number Specifies the VOA filter-in interface number.
voafilterout number Specifies the VOA filter-out interface number.
voain number Specifies the VOA in interface number.
voaout number Specifies the VOA out interface number.
rbacl Displays RBACL entries.
all Specifies all RBACL entries.
default Specifies the default RBACL entry.
tcam A, tcam B Displays entries by index for TCAM A, TCAM B.
index number Specifies the TCAM index number. Range is 0–131071.
Defaults None
266
show platform hardware acl entry
Examples This example shows how to display the global QoS inbound ACL detailed entries for ARP protocol
module 4:
Router# show platform hardware acl entry global-qos in arp detail module 4
267
show platform hardware acl ethertype-cam
Defaults None
Examples This example shows how to display the hardware ACL Ethertype CAM table for module 4:
Router# show platform hardware acl ethertype-cam module 4
268
show platform hardware acl hardware-hits
show platform hardware acl hardware-hits {clear {module number} | show {module number}}
Defaults None
Examples This example shows how to display the TCAM hardware hits cleared for module 4:
Router# show platform hardware acl hardware-hits clear 4
269
show platform hardware acl initiate-lookup
show platform hardware acl initiate-lookup {interface {async number | auto-template number
| ctunnel number | dialer number | esconphy number | filter number | filtergroup number |
gigabitethernet number | longreachethernet number | loopback number | mfr number |
multilink number | null number | port-channel number | portgroup number | pos-channel
number | sysclock number | tengigabitethernet number | tunnel number | vif number |
virtual-template number | virtual-tokenring number | vlan vlan_id | fcpa number |
voabypassin number | voabypassout number | voafilterin number | voafilterout number |
voain number | voaout number} | label value tcam {A {arp {arp-rarp | arp_rarp_vld |
global_acl_fmt_match | l2_miss | mac_da_bcast | mac_sa | ofe mode | req-rpl | sender_ip |
src_snd_mac_same | src_tar_mac_same | target_ip | test} | ipv4 {acos | dst_port | first_seen
[rp_bit] | frag_flag | ip_da | ip_frag | ip_sa | l4_proto | l4op | module | src_dst_as_num |
src_port} | ipv6 {acos | dst_port | first_seen [rp_bit] | frag_flag | ip_da | ip_frag | ip_sa |
l4_proto | l4op | module | src_dst_as_num | src_port} | l2 {acos | ce_vlan | dscp| enc |
first_seen [rp_bit] | gpid | l2_miss | mac_da | mac_sa | module | vlan vlan_id} | mpls {acos |
acos_gpid | exception | first_seen [rp_bit] | gpid_present | ip_hdr_vld | l2_miss | l4op |
module | mpls_exp | mpls_exp_from_null | mpls_exp_of_null | mpls_label | mpls_mcast |
mpls_stack | mpls_subtype | mpls_valid | u_key}} | B {arp {arp-rarp | arp_rarp_vld |
global_acl_fmt_match | l2_miss | mac_da_bcast | mac_sa | ofe mode | req-rpl | sender_ip |
src_snd_mac_same | src_tar_mac_same | target_ip | test} | ipv4 {acos | dst_port | first_seen
[rp_bit] | frag_flag | ip_da | ip_frag | ip_sa | l4_proto | l4op | module | src_dst_as_num |
src_port} | ipv6 {acos | dst_port | first_seen [rp_bit] | frag_flag | ip_da | ip_frag | ip_sa |
l4_proto | l4op | module | src_dst_as_num | src_port} | l2 {acos | ce_vlan | dscp| enc |
first_seen [rp_bit] | gpid | l2_miss | mac_da | mac_sa | module | vlan vlan_id} | mpls {acos |
acos_gpid | exception | first_seen [rp_bit] | gpid_present | ip_hdr_vld | l2_miss | l4op |
module | mpls_exp | mpls_exp_from_null | mpls_exp_of_null | mpls_label | mpls_mcast |
mpls_stack | mpls_subtype | mpls_valid | u_key}}}
Syntax Description interface Lists the various interfaces to choose ACL statistics for.
async number Specifies the asynchronous interface number. Range is 1–999.
auto-template Specifies the auto-template interface number. Range is 1–999.
number
ctunnel number Specifies the channel tunnel interface number. Range is 0–2147483647.
dialer number Specifies the dialer interface number. Range is 0–255.
esconphy number Specifies the EsconPhy interface number.
filter number Specifies the filter interface number.
filtergroup number Specifies the filter group interface number.
gigabitethernet Specifies the Gigabit Ethernet interface number.
number
longreachethernet Specifies the long-reach Ethernet interface number.
number
loopback number Specifies the loopback interface number. Range is 1–2147483647.
mfr number Specifies the multilink Frame Relay bundle interface number. Range is
1–2147483647.
270
show platform hardware acl initiate-lookup
multilink number Specifies the multilink group interface number. Range is 1–2147483647.
null number Specifies the null interface number. Range is 0–0.
port-channel number Specifies the Ethernet channel of interfaces. Range is 1–496.
portgroup number Specifies the port group interface number.
pos-channel number Specifies the PoS channel of interfaces. Range is 1–4094.
sysclock number Specifies the telecom bus clock controller interface number.
tengigabitethernet Specifies the 10-Gigabit Ethernet interface number.
number
tunnel number Specifies the tunnel interface number. Range is 1–2147483647.
vif number Specifies the PGM multicast host interface number. Range is 1–1.
virtual-template Specifies the virtual template interface number. Range is 1–200.
number
virtual-tokenring Specifies the virtual Token Ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the Fibre Channel interface number.
voabypassin number Specifies the VOA bypass-in interface number.
voabypassout Specifies the VOA bypass-out interface number.
number
voafilterin number Specifies the VOA filter-in interface number.
voafilterout number Specifies the VOA filter-out interface number.
voain number Specifies the VOA in interface number.
voaout number Specifies the VOA out interface number.
label value Specifies the label value. Range is 1–8191.
tcam A, tcam B Specifies TCAM A or TCAM B.
arp Specifies the ARP protocol.
arp-rarp Specifies ARP or RARP.
arp_rarp_vld Specifies whether ARP or RARP is valid or not.
global acl fmt match Specifies whether global ACL format matches or not.
l2_miss Specifies whether the Layer 2 is missed.
mac_da_bcast Specifies whether MAC destination address is broadcast.
mac_sa Specifies the MAC source address.
ofe-mode Specifies whether it is OFE mode.
req-rpl Specifies whether it is reply or response.
sender_ip Specifies the sender IP address.
src_snd_mac_same Specifies whether the sender MAC is equal to Hbus source MAC.
src_tar_mac_same Specifies whether the sender MAC is equal to Hbus target MAC.
target_ip Specifies the target IP address.
test Specifies test looping.
ipv4 Specifies the IPv4 protocol.
acos Specifies the exception cause.
dst_port Specifies the destination port.
271
show platform hardware acl initiate-lookup
Defaults None
272
show platform hardware acl initiate-lookup
Examples This example shows how to display the ACL TCAM entries matching a pattern on the asynchronous
interface 4:
Router# show platform hardware acl initiate-lookup interface async 4
273
show platform hardware acl label2sel tcam
show platform hardware acl label2sel tcam {A {index number} | B {index number}}
Defaults None
Examples This example shows how to display the TCAM A capmap entry index number 20:
Router# show platform hardware acl capmap tcam A Index 20
274
show platform hardware acl lou
Syntax Description index number Specifies the LOU index number. Range is 0–103.
module number Specifies the module number.
Defaults None
Examples This example shows how to display the ACL logical operator units for module 4:
Router# show platform hardware acl lou module 4
275
show platform hardware acl status
Defaults None
Examples This example shows how to display the hardware ACL status for module 4:
Router# show platform hardware acl status module 4
276
show platform hardware acl tcam
show platform hardware acl tcam {A {arp {accounting {module number} | module number | qos
{module number} | security {module number}} | index number | ip {accounting {module
number} | module number | qos {module number} | security {module number}} | ipv6
{accounting {module number} | module number | qos {module number} | security {module
number}} | l2v4 {accounting {module number} | module number | qos {module number} |
security {module number}} | mac {accounting {module number} | module number | qos
{module number} | security {module number}} | module number | mpls {accounting
{module number} | module number | qos {module number} | security {module number}}}
show platform hardware acl tcam {B {arp {accounting {module number} | module number | qos
{module number} | security {module number}} | index number | ip {accounting {module
number} | module number | qos {module number} | security {module number}} | ipv6
{accounting {module number} | module number | qos {module number} | security {module
number}} | l2v4 {accounting {module number} | module number | qos {module number} |
security {module number}} | mac {accounting {module number} | module number | qos
{module number} | security {module number}} | module number | mpls {accounting
{module number} | module number | qos {module number} | security {module number}}}
Defaults None
277
show platform hardware acl tcam
Examples This example shows how to display the TCAM A ARP accounting entries for module 4:
Router# show platform hardware acl tcam A arp accounting module 4
278
show platform hardware acl tcp-flags-tbl
show platform hardware acl tcp-flags-tbl {detail | index number | module number}
Defaults None
Examples This example shows how to display the ACL TCP flags for module 4:
Router# show platform hardware acl tcp-flags-tbl module 4
279
show platform hardware acl v6-extnhdr-tbl
show platform hardware acl v6-extnhdr-tbl {detail | index number | module number}
Defaults None
Examples This example shows how to display the hardware ACL v6 extension header table information for module
4:
Router# show platform hardware acl v6-extnhdr-tbl module 4
280
show platform hardware asicreg
show platform hardware asicreg {dhanush {slot number} | hyperion | medusa | mii-phy |
palladium {get virtual_address | set virtual_address | all} | pentamak | ppc {all} | qchip |
rchip | revati | santa-ana | sculptor | scuti | solano | supersantaana | vishakha}
Defaults None
281
show platform hardware asicreg
Examples This example shows how to display ASIC register information for the Dhanush ASIC, slot 4:
Router# show platform hardware asicreg dhanush slot 4
282
show platform hardware asic-versions
Defaults None
Examples This example shows how to display the hardware ASIC version for slot number 4:
Router# show platform hardware asic-versions slot 4
283
show platform hardware capacity
Syntax Description resource-type (Optional) Hardware resource type; see the “Usage Guidelines” section for
the valid values.
Defaults None
284
show platform hardware capacity
285
show platform hardware capacity
The show platform hardware capacity system command displays the following information:
• PFC operating mode (PFC version: PFC3A, PFC3B, unknown, and so forth)
• Supervisor engine redundancy mode (RPR, RPR+, SSO, none, and so forth)
• Module-specific switching information, including the following information:
– Part number (WS-SUP720-BASE, WS-X6548-RJ-45, and so forth)
– Series (supervisor engine, fabric, CEF720, CEF256, dCEF256, or classic)
– CEF mode (central CEF, dCEF)
The show platform hardware capacity vlan command displays the following VLAN information:
• Total VLANs
• VTP VLANs that are used
• External VLANs that are used
• Internal VLANs that are used
• Free VLANs
Examples This example shows how to display CPU capacity and utilization information for the route processor,
the switch processor, and the LAN module in the Cisco 7600 series router:
Router# show platform hardware capacity cpu
CPU Resources
CPU utilization: Module 5 seconds 1 minute 5 minutes
1 RP 0% / 0% 1% 1%
1 SP 5% / 0% 5% 4%
7 69% / 0% 69% 69%
8 78% / 0% 74% 74%
Processor memory: Module Bytes: Total Used %Used
1 RP 176730048 51774704 29%
1 SP 192825092 51978936 27%
7 195111584 35769704 18%
8 195111584 35798632 18%
I/O memory: Module Bytes: Total Used %Used
1 RP 35651584 12226672 34%
1 SP 35651584 9747952 27%
7 35651584 9616816 27%
8 35651584 9616816 27%
Router#
This example shows how to display EOBC-related statistics for the route processor, the switch processor,
and the DFCs in the Cisco 7600 series router:
Router# show platform hardware capacity eobc
EOBC Resources
Module Packets/sec Total packets Dropped packets
1 RP Rx: 61 108982 0
Tx: 37 77298 0
1 SP Rx: 34 101627 0
Tx: 39 115417 0
7 Rx: 5 10358 0
Tx: 8 18543 0
8 Rx: 5 12130 0
Tx: 10 20317 0
Router#
286
show platform hardware capacity
This example shows how to display the current and peak switching utilization:
Router# show platform hardware capacity fabric
Switch Fabric Resources
Bus utilization: current is 100%, peak was 100% at 12:34 12mar45
Fabric utilization: ingress egress
Module channel speed current peak current peak
1 0 20G 100% 100% 12:34 12mar45 100% 100% 12:34 12mar45
1 1 20G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
4 0 20G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
13 0 8G 12% 80% 12:34 12mar45 12% 80% 12:34 12mar45
Router#
This example shows how to display information about the total capacity, the bytes used, and the
percentage that is used for the flash or NVRAM resources present in the system:
Router# show platform hardware capacity flash
Flash/NVRAM Resources
Usage: Module Device Bytes: Total Used %Used
1 RP bootflash: 31981568 15688048 49%
1 SP disk0: 128577536 105621504 82%
1 SP sup-bootflash: 31981568 29700644 93%
1 SP const_nvram: 129004 856 1%
1 SP nvram: 391160 22065 6%
7 dfc#7-bootflash: 15204352 616540 4%
8 dfc#8-bootflash: 15204352 0 0%
Router#
This example shows how to display the capacity and utilization of the EARLs present in the system:
Router# show platform hardware capacity forwarding
L2 Forwarding Resources
MAC Table usage: Module Collisions Total Used %Used
6 0 65536 11 1%
VPN CAM usage: Total Used %Used
512 0 0%
L3 Forwarding Resources
FIB TCAM usage: Total Used %Used
72 bits (IPv4, MPLS, EoM) 196608 36 1%
144 bits (IP mcast, IPv6) 32768 7 1%
detail: Protocol Used %Used
IPv4 36 1%
MPLS 0 0%
EoM 0 0%
IPv6 4 1%
IPv4 mcast 3 1%
IPv6 mcast 0 0%
Adjacency usage: Total Used %Used
1048576 175 1%
Forwarding engine load:
Module pps peak-pps peak-time
6 8 1972 02:02:17 UTC Thu Apr 21 2005
Netflow Resources
TCAM utilization: Module Created Failed %Used
6 1 0 0%
ICAM utilization: Module Created Failed %Used
6 0 0 0%
Flowmasks: Mask# Type Features
IPv4: 0 reserved none
IPv4: 1 Intf FulNAT_INGRESS NAT_EGRESS FM_GUARDIAN
IPv4: 2 unused none
IPv4: 3 reserved none
IPv6: 0 reserved none
IPv6: 1 unused none
287
show platform hardware capacity
This example shows how to display the capacity and utilization of resources for Layer 3 multicast
functionality:
Router# show platform hardware capacity multicast
L3 Multicast Resources
IPv4 replication mode: ingress
IPv6 replication mode: ingress
Bi-directional PIM Designated Forwarder Table usage: 4 total, 0 (0%) used
Replication capability: Module IPv4 IPv6
5 egress egress
9 ingress ingress
MET table Entries: Module Total Used %Used
288
show platform hardware capacity
5 65526 6 0%
Router#
This example shows how to display information about the system power capacities and utilizations:
Router# show platform hardware capacity power
Power Resources
Power supply redundancy mode: administratively combined
operationally combined
System power: 1922W, 0W (0%) inline, 1289W (67%) total allocated
Powered devices: 0 total
Router#
This example shows how to display the capacity and utilization of QoS policer resources per EARL in
the Cisco 7600 series router:
Router# show platform hardware capacity qos
QoS Policer Resources
Aggregate policers: Module Total Used %Used
1 1024 102 10%
5 1024 1 1%
Microflow policer configurations: Module Total Used %Used
1 64 32 50%
5 64 1 1%
Router#
This example shows how to display information about the key system resources:
Router# show platform hardware capacity system
System Resources
PFC operating mode: PFC3BXL
Supervisor redundancy mode: administratively rpr-plus, operationally rpr-plus
Switching Resources: Module Part number Series CEF mode
5 WS-SUP720-BASE supervisor CEF
9 WS-X6548-RJ-45 CEF256 CEF
Router#
289
show platform hardware capacity rewrite-engine
Syntax Description drop Displays the central rewrite engine drop counter values.
performance Displays the central rewrite engine current performance counter values or
the performance rate.
slot number (Optional) Displays the counter values for the module in the specified slot. If
no slot is specified, the counters are displayed for each slot.
rate sample_interval (Optional) Displays the drop rate or rewrite rate for a sample interval in msec
between 1 and 1000. The default interval is 50 msec.
details (Optional) Displays each individual drop counter with its name and register
ID number. This keyword is not available with the performance keyword.
Defaults If the sample interval is not specified, the default interval is 50 msec.
Usage Guidelines In the show platform hardware capacity rewrite-engine performance command output, a value of
N/A indicates that the slot or channel has a rewrite engine, but does not support performance counters.
Examples This example shows how to display the packet drop counters of the central rewrite engine in all installed
supervisor engines and line cards:
Router# show platform hardware capacity rewrite-engine drop
290
show platform hardware capacity rewrite-engine
This example shows how to display a detailed report of the packet drop counters of the module in slot 1:
Router# show platform hardware capacity rewrite-engine drop slot 1 details
This example shows how to display the packet drop counters of the module in slot 5 over the default
sample interval of 50 msec:
Router# show platform hardware capacity rewrite-engine drop slot 5 rate
This example shows how to display the packet drop counters of the module in slot 5 over a sample
interval of 20 msec:
Router# show platform hardware capacity rewrite-engine drop slot 5 rate 20
This example shows how to display the performance counters of the central rewrite engine in all installed
supervisor engines and line cards:
Router# show platform hardware capacity rewrite-engine performance
291
show platform hardware capacity rewrite-engine
5 0 0xC0 FAB RX 1 0 0
5 0 0x112 FAB TX 0 992089 0
5 0 0x116 FAB TX 1 0 0
5 0 0x299 REPLICATION ML3 0 0
5 0 0x29A REPLICATION ML2 0 0
5 0 0x29B RECIRC L2 0 0
5 0 0x29C RECIRC L3 0 0
5 0 0x295 SPAN TX 0 91166 0
5 0 0x296 SPAN TX 1 91313 0
5 0 0x297 SPAN RX 0 1 0
5 0 0x298 SPAN RX 1 1 0
5 0 0x29D SPAN TERMINATION 0 0
This example shows how to display the performance counters of the module in slot 5:
Router# show platform hardware capacity rewrite-engine performance slot 5
This example shows how to display the performance counters of the module in slot 5 over the default
sample interval of 50 msec:
Router# show platform hardware capacity rewrite-engine performance slot 5 rate
292
show platform hardware cbl
Defaults None
Examples This example shows how to display the hardware CBL for slot 4:
Router# show platform hardware cbl slot 4
293
show platform hardware cef mpls detail
show platform hardware cef mpls detail [earl earl-id | module mod-num] group {ip-addr [detail
| verbose]}
Syntax Description earl earl-id (Optional) Displays the CEF detail for the EARL; valid values are 1 or 2.
module mod-num (Optional) Displays the CEF detail for a module; valid values are 1 through
6.
group Shows the hardware entries for a group.
ip-addr detail Shows the hardware entry details.
ip-addr verbose Shows the hardware entry verbose details.
Defaults None
Usage Guidelines The show platform hardware cef mpls detail command displays detailed information about MPLS
adjacency entries. For each adjacency, use the show platform hardware cef adjacencies entry
command to display the MPLS adjacency information.
Examples This example shows how to display the MPLS CEF hardware details for EARL 1:
Router# show platform hardware multicast routing ip group 226.1.1.1 detail
show platform hardware cef mpls detail earl 1
Codes: M - mask entry, V - value entry, A - adjacency index, NR- no_route bit
LS - load sharing count, RI - router_ip bit, DF: default bit
CP - copy_to_cpu bit, AS: dest_AS_number, DGTv - dgt_valid bit
DGT: dgt/others value, LS: load sharing count on eos condition
EE: EOS enable, NW: num swap paths, NP: num push paths
294
show platform hardware cef mpls detail
295
show platform hardware cef adjacencies entry
Syntax Description entry-num Displays the adjacency index; valid values are 0 through 1048575.
Defaults None
Examples This example shows how to display the index for CEF adjacency 45:
Router# show platform hardware cef adjacencies entry 45
Index: 45 -- Valid entry (valid = 1) --
Adjacency fields:
___________________________________________________
|adj_stats = EN | fwd_stats = EN | format = IP
|_________________|__________________|______________
|rdt = OFF | elif = 0x2D | vpn = 0x3FFF
|_________________|__________________|______________
Statistics: Packets = 0
Bytes = 0
Router#
296
show platform hardware cef adjacencies entry
Command Description
show platform hardware met read Displays platform hardware MET table entries.
show platform hardware multicast Matches and displays multicast routing group IP
routing addresses.
show platform software met detail Displays software routing for the MET.
297
show platform hardware cef tcam
show platform hardware cef tcam {ecc [detail [earl earl-id] | module module-num]| earl earl-id]|
module module-num]| hit [detail [earl earl-id] | module module-num]| earl earl-id]| module
module-num]| keys [count | exception ]| memory usage | segment [detail [earl earl-id] |
module module-num]| earl earl-id]| module module-num] | select [detail [earl earl-id] |
module module-num]| earl earl-id]| module module-num] | shadow [detail [earl earl-id] |
module module-num]| earl earl-id]| module module-num] | timing [detail [earl earl-id] |
module module-num]| earl earl-id]| module module-num] | utilization [detail [earl earl-id] |
module module-num]| earl earl-id]| module module-num]| earl earl-id] | module module-num]
Syntax Description ecc Displays error checking and correction (ECC) information.
detail (Optional) Displays detailed information.
earl earl-id (Optional) Displays earl-id content.
module module-num (Optional) Displays information for a specific module.
hit Displays last hit on the FIB TCAM information.
keys Displays keys information.
count (Optional) Displays keys count information.
exception (Optional) Displays keys exception iformation.
memory usage Displays memory usage.
segment Displays segment distribution.
select Displays bit-select information.
shadow Displays the shadow copy.
timing Displays timing ultilization.
utilization Displays segment ultilization.
Defaults None
298
show platform hardware cef tcam
Examples This example shows how to display the hardware CEF TCAM key exception:
Router(config)# show platform hardware cef tcam keys exception
Priorities in exception:
IPv4 0 16 35 35085
IPv4-Mcast 1 68 68 0
MPLS 2 17 17 0
EOMPLS 3 19 19 0
MPLS-VPN 4 9 9 0
Diags 5 5 5 0
VPLSv4-Mcast 9 69 69 0
IPv4 0 16 4096
. . 17 15507
. . 18 7753
. . 19 3876
. . 20 1939
. . 21 969
. . 22 484
. . 23 243
. . 24 121
. . 25 60
. . 26 34
. . 30 2
. . 34 1
. . 245 126
. . 246 118
. . 247 114
. . 248 111
. . 249 109
299
show platform hardware cef tcam
. . 250 109
. . 251 107
. . 252 64
. . 253 32
. . 254 16
. . 255 8
. . 256 4
. . 257 2
. . 389 1
. . 390 1
0 0 0 0 0 0 0 0 0 Void
1 80 80 0 0 0 0 0 0 Bsort
13 0 0 0 0 0 0 0 0 SE Pri
15 8 65536 0 0 0 0 0 0 Bit 64
19 24 24 0 0 0 0 0 0 Bit 192
20 28 28 0 0 0 0 0 0 Bit 224
300
show platform hardware cef tcam
24 44 44 0 0 0 0 0 0 Bit 352
25 48 48 0 0 0 0 0 0 Bit 384
26 52 52 0 0 0 0 0 0 Bit 416
27 56 56 0 0 0 0 0 0 Bit 448
29 64 64 0 0 0 0 0 0 Bit 512
30 68 68 0 0 0 0 0 0 Bit 544
31 72 72 0 0 0 0 0 0 Bit 576
32 76 76 0 0 0 0 0 0 Bit 608
34 84 84 0 0 0 0 0 0 Bit 672
35 88 88 0 0 0 0 0 0 Bit 704
This example shows how to display the hardware CEF TCAM timing information:
Router(config)# show platform hardware cef tcam timing
(0) Groom Clock: 182us (Min) << 71ms (Avg) << 404ms (Max) = 09.19s (Tot)
5.28ms 1.16ms 10ms 38ms 3.43ms 10ms 166ms 223ms
5.06ms 960us 9.34ms 37ms 1.79ms 96ms 110ms 155ms
4.72ms 1.06ms 8.90ms 34ms 813us 4.14ms 110ms 138ms
4.12ms 755us 6.81ms 32ms 305us 75ms 28ms 237ms
3.90ms 690us 6.13ms 30ms 228us 50ms 247ms 199ms
3.67ms 529us 5.81ms 28ms 274us 94ms 217ms 63ms
3.38ms 506us 3.68ms 25ms 1.73ms 269ms 218ms 96ms
3.14ms 400us 2.94ms 23ms 279us 119ms 277ms 66ms
2.94ms 351us 3.63ms 20ms 115ms 163ms 346ms 94ms
2.87ms 306us 2.75ms 18ms 46ms 404ms 316ms 35ms
2.76ms 291us 1.18ms 16ms 156ms 351ms 154ms 84ms
3.30ms 275us 794us 13ms 87ms 319ms 220ms 5.51ms
5.20ms 202us 736us 11ms 8.52ms 85ms 220ms 203ms
2.77ms 190us 39ms 9.58ms 112ms 229ms 189ms 191ms
1.58ms 182us 39ms 7.52ms 73ms 180ms 172ms 216ms
1.84ms 11ms 38ms 5.63ms 90ms 188ms 227ms 1.27ms
(1) Add Clock: 11us (Min) << 13us (Avg) << 107us (Max) = 1.78ms (Tot)
11us 11us 11us 12us 11us 12us 12us 12us
11us 12us 12us 11us 11us 11us 11us 12us
12us 11us 12us 12us 11us 12us 12us 12us
12us 12us 12us 12us 11us 12us 12us 13us
301
show platform hardware cef tcam
This example shows how to display the hardware CEF TCAM utilization information:
Router(config)# show platform hardware cef tcam utilization
Util summary for Pool 0: 524288 keys, 1024 segs, 36 Mb
302
show platform hardware cef adjacencies
show platform hardware cef adjacencies all {detail {module {module number}
show platform hardware cef adjacencies allocation-map {number | module {module number}}
show platform hardware cef adjacencies decap-tunnel {detail {module {module number}}}
show platform hardware cef adjacencies encap-tunnel {A.B.C.D | {detail {module {module
number}
303
show platform hardware cef adjacencies
Defaults None
Examples This example shows how to display the CEF adjacencies allocation map module number:
Router# show platform hardware cef adjacencies allocation-map module 4
This example shows how to display the CEF adjacencies status allocated or used starting at entry 100:
Router# show platform hardware cef adjacencies status 100
------------------------------------------------------
304
show platform hardware cef adjacencies
305
show platform hardware cef maximum-route
Syntax
Description usage Specifies the usage.
Defaults None
Examples This example shows how to display CEFv6 maximum routes configuration and the current usage of
entries within the dedicated area and the shared area:
Router# show platform hardware cef maximum-routes
306
show platform hardware cef maximum-route
Router#
307
show platform hardware database version
Syntax Description slot slot_number Specifies the slot number of a module that has hardware abstraction layer (HAL)
support.
Defaults None
Usage Guidelines The show platform hardware database command displays the following Supervisor Engine 2T
platform hardware database version:
• Bundled data
• Data from flash
• Currently used data
• Data information stored in region 1
• Data information stored in region 2
• Data information stored in golden region
The flash region has three states:
• APPROVED—The region is verified and can be used for building the hardware database.
• FIRST_RUN—The data in this region has not been verified yet, and reload is required to verify it.
• INVALID—The region is not valid.
Note It is normal for the command to display “INVALID” when the hardware database version
has not been upgraded.
The slot keyword is supported only on modules that have hardware abstraction layer (HAL) support.
308
show platform hardware database version
Examples This example shows how to display the platform hardware database version:
Router# show platform hardware database version
309
show platform hardware earl
show platform hardware earl {cc {table {agegrp {entry {entry number}} | bem {entry {entry
number}} | bpm {entry {entry number}} | glblvlan {entry {entry number}}}} | earl_db |
eureka | lamira | layer2 | wf-fpga}
Defaults None
Examples This example shows how to display the EARL consistency checker age group entry 4444:
Router(config)# show platform hardware earl cc table agegrp entry 4444
310
show platform hardware earl eureka
show platform hardware earl eureka config {all {file {word}} | module {ac {dbi | epp | ft | l2u
| l2ui | l3lu | l3lu312 | l3mg | lif | lm_rx | lm_tx | ntfy | pb1_rx | pb1_tx | pb2_rx | pb2_tx | pp
| rbi } | dbi | epp | ft | l2u | l2ui | l3lu | l3lu312 | l3mg | lif | lm_rx | lm_tx | ntfy | pb1_rx |
pb1_tx | pb2_rx | pb2_tx | pp | rbi}}
show platform hardware earl eureka ecc {configuration {all | table {eu-acl0 | eu-acl1 | ft | lb |
ldb | lifdb | lifstat | rbi}} | statistics {all | table {eu-acl0 | eu-acl1 | ft | lb | ldb | lifdb | lifstat
| rbi}}}
show platform hardware earl eureka interupts {all {file {word}} | clear {all {file} | module} |
module {ac | epp | ft | l2u | l2ui | l3lu | l3lu312 | l3mg | lif | lm_rx | lm_tx | ntfy | pb1_rx |
pb1_tx | pb2_rx | pb2_tx | pp | rbi | se}}
show platform hardware earl eureka statistics {all {file} | clear {all | module} | module {ac |
epp | ft | l2u | l2ui | l3lu | l3lu312 | l3mg | lif | lm_rx | lm_tx | ntfy | pb1_rx | pb1_tx | pb2_rx
| pb2_tx | pp | rbi | se}}
show platform hardware earl eureka vsl {mapping-tables {pb1 {dst-post-map | dst-pre-map |
src-pre-map}} | pb2} | registers}
311
show platform hardware earl eureka
Defaults None
Examples This example shows how to display all of EARL Eureka ASIC configurations:
Router# show platform hardware earl eureka config all
312
show platform hardware earl eureka
313
show platform hardware earl lamira
show platform hardware earl lamira {config {all {file {word}} | module {ci | cl1 | cl1_2 | cl2 |
gv | if | l3 | la0 | la1 | nf | nf2 | nf_se | pl | pl2 | po | ri | rp}} | ecc {configuration {all | table
{acct | aclsram-a | aclsram-b | acltcam-a | acltcam-b | acosseli | adj-dram | adjstats | agdpp
| cmtbla | cmtblb | dagram | egmtmap | elifmap | fib-dram | fibtcam | ife_dstinfo | iferdt |
ilifmap | infife | infofe | label2sela | label2selb | lcbcnt | nffl | nfhash0 | nfhash1 | nfstats |
nftable | nfvram | ofe_dstinfo | ofeff | oferdt | outff | plcbas | pmap | rit | rpfdram | rwsel |
sagram | smpl | srcdstas | vidmap | vlanmap}} | statistics {all | table {acct | aclsram-a |
aclsram-b | acltcam-a | acltcam-b | acosseli | adj-dram | adjstats | agdpp | cmtbla | cmtblb
| dagram | egmtmap | elifmap | fib-dram | fibtcam | ife_dstinfo | iferdt | ilifmap | infife |
infofe | label2sela | label2selb | lcbcnt | nffl | nfhash0 | nfhash1 | nfstats | nftable | nfvram |
ofe_dstinfo | ofeff | oferdt | outff | plcbas | pmap | rit | rpfdram | rwsel | sagram | smpl |
srcdstas | vidmap | vlanmap}}} | interrupts {all {file {word}} |clear {all {file} | module
{cl1 | cl1_2 | cl2 | gv | if | l3 | la0 | la1 | nf | nf2 | nf_se | pl | pl2 | po | ri | rp}} | module} |
statistics {all {file {word}} | clear {all | module {ci | cl1 | cl1_2 | cl2 | gv | if | l3 | la0 | la1 |
nf | nf2 | nf_se | pl | pl2 | po | ri | rp}} | module}}
314
show platform hardware earl lamira
315
show platform hardware earl lamira
Defaults None
Examples This example shows how to display all of the EARL Lamira ASIC configuration:
Router# show platform hardware earl lamira config all
316
show platform hardware earl layer2
show platform hardware earl layer2 {etherchannel {bem-table {number number} | bpm-table
{bridge-domain number} | config} | forwarding-table {dump {all | l2addr number} | l2addr
{H.H.H}} | redirections {protocol-filtering {dump {all | dot1ad | dot1q | vpls} |
profile-map}}}
Syntax Description etherchannel Specifies the Layer 2 and Layer 3 EtherChannel forwarding-related parameters.
bem-table number Specifies the Bundle Expansion Map table number. Range is 0–7.
number
bpm-table Specifies the Bundle Port Map table.
bridge-domain Specifies the bridge domain number. Range is 0–16383.
number
config Specifies all the EtherChannel-related hardware configuration.
forwarding-table Specifies the Layer 2 forwarding table-related parameters.
dump Specifies the valid entries to dump.
all Specifies that all the entries need to be dumped.
l2addr number Specifies the number of Layer 2 addresses that need to be dumped. Range is
0–131071.
l2addr Specifies the computation of the Layer 2 table address.
H.H.H Specifies the 48-bit MAC address.
redirections Specifies the Layer 2, Layer 3, and Layer 4 redirections-related parameters.
protocol-filtering Specifies the protocol filtering-related parameters.
dot1ad Specifies that dot1ad profile needs to be dumped.
dot1q Specifies that dot1q profile needs to be dumped.
vpls Specifies that VPLS profile needs to be dumped.
profile-map Specifies that the logical-to-physical (hardware) mapping of profiles needs to be
printed.
Defaults None
317
show platform hardware earl layer2
Examples This example shows how to display platform hardware EARL Layer 2 EtherChannel BPM table, bridge
domain 4:
Router# show platform hardware earl layer2 etherchannel bpm-table bridge-domain 4
318
show platform hardware efp
Defaults None
Examples This example shows how to display the hardware EFP configuration information for Gigabit Ethernet 4:
Router# show platform hardware efp config gigabitethernet 4
319
show platform hardware fan-tray
Syntax Description number Specifies the fan tray number. Range is 1–1.
status Specifies the fan tray status.
Defaults None
Examples This example shows how to display the hardware details for fan tray 1:
Router# show platform hardware fan-tray 1
320
show platform hardware flow table
show platform hardware flow table {copy-policy index | flowmask {index | ip index | ipv6 index
| l2 index | mpls index} | mark-en-map index | profile {index | ip index | ipv6 index | l2 index
| mpls index} | qos-ctrl index | redirect {ife index | ofe index | tcp index} | sampler index |
sampler-copy index | shadow {copy-policy index | flowmask {index | ip index | ipv6 index | l2
index | mpls index} | mark-en-map index | profile {index | ip index | ipv6 index | l2 index | mpls
index} | qos-ctrl index | redirect {ife index | ofe index | tcp index} | sampler index |
sampler-copy index}}
Syntax Description copy-policy index Specifies the copy policy entries by index number. Range is 0–31.
flowmask index Specifies the flow mask entries by index number. Range is 0–79.
ip index Specifies the IP entries by index number. Range is 0–31.
ipv6 index Specifies the IPv6 entries by index number. Range is 0–31.
l2 index Specifies the Layer 2 entries by index number. Range is 0–7.
mpls index Specifies the MPLS entries by index number. Range is 0–7.
mark-en-map index Specifies the mark encapsulation map entries by index number. Range is
0–63.
profile index Specifies the profile entries by index number. Range is 0–79.
qos-ctrl index Specifies the QoS CTRL entries by index number. Range is 0–63.
redirect Specifies the redirect tables.
ife index Specifies the IFE redirect by index number. Range is 0–511.
ofe index Specifies the OFE redirect by index number. Range is 0–511.
tcp index Specifies the TCP redirect by index number. Range is 0–7.
sampler index Specifies the sampler entry by index number. Range is 0–1023.
sampler-copy index Specifies the sampler copy entry by index number. Range is 0–7.
shadow Specifies the shadow extension tables.
Defaults None
321
show platform hardware flow table
Examples This example shows how to display the hardware flow table entries for IFE redirect index 4:
Router# show platform hardware flow table redirect ife 4
322
show platform hardware fpoe
Defaults None
Examples This example shows how to display the hardware FPoE for slot 4:
Router# show platform hardware fpoe slot 4
323
show platform hardware idprom
show platform hardware idprom {backplane number | clock number | earl number |
fabric-extension number | fan-tray number | module number | power-supply number | rp
number | supervisor number | vdb number | vtt number}
Syntax Description backplane number Displays the backplane EEPROM number. Range is 1–2.
clock number Specifies the clock EEPROM number. Range is 1–2.
earl number Specifies the EARL EEPROM number.
fabric-extension Specifies the fabric extension board’s EEPROM number.
number
fan-tray number Specifies the fan tray EEPROM number. Range is 1–1.
module number Specifies the module EEPROM number.
power-supply Specifies the power supply EEPROM number. Range is 1–2.
number
rp number Specifies the RP EEPROM.
supervisor number Specifies the supervisor EEPROM.
vdb number Specifies the VDB EEPROM number.
vtt number Specifies the VTT EEPROM number. Range is 1–4.
Defaults None
Examples This example shows how to display the information on the EEPROM for backplane 1:
Router# show platform hardware idprom backplane 1
324
show platform hardware image version slot
Defaults None
Usage Guidelines This command is useful only if a new hardware image version becomes available.
This command is supported only on modules that have hardware abstraction layer (HAL) support.
Examples This example shows how to display the HAL image version information for a module:
Router# show platform hardware image version slot 3
Image bundle version: 1.1
Note It is normal for the command to display “INVALID” when the version has not been upgraded.
325
show platform hardware lif l2
show platform hardware lif l2 {globalcfg | memory {memory detail} | region {adjacency {dti
{adjacency number | config} | replicated {adjacency | config}} | egresslif {config | lif {lif
number}} | flood{config | ltl} | globalvlan {config | vlan} | negative-mn {config | ltl} |
portgroup{config | ltl} | shim {config | lif}| swltl {config | ltl} | vb{config | vlan}} | table
{global-vlan vlan | lif-db {all | entry number | key} | port-map{all | interface
{gigabitethernet | longreachethernet | multilink | port-channel | tengigabitethernet} |
ltl-index number}}}
326
show platform hardware lif l2
Defaults None
Examples This example shows how to display platform hardware Layer 2 LIF global configuration:
Router# show platform hardware lif l2 globalcfg
327
show platform hardware lif l3
show platform hardware lif l3 {egress {features | handle | hierarchy | index | interface | ipv4 |
ipv6 | misc | module | mpls | qos} | info number | ingress { features | handle | hierarchy |
index | interface | ipv4 | ipv6 | misc | module | mpls | qos} | mtu { table {dump | index}} |
port-map{ index number | interface {gigabitethernet | port-channel | tengigabitethernet
tunnel | vlan} | module number}}
Defaults None
328
show platform hardware lif l3
Examples This example shows how to display platform hardware EARL Layer 3 LIF test number 4:
Router# show platform hardware lif l3 info 4
329
show platform hardware lif stats
show platform hardware lif stats {index number | interface {gigabitethernet | port-channel |
tengigabitethernet | tunnel | vlan} | profile {choice {all {module} | id number} |
read{module} | write number} | table {config {module} | egress {module} | fop {module} |
ingress {module} | no-stat {module} | status {module}}}
Syntax Description index number Specifies the LIF statistics for a particular index. Range is 0–131071.
interface Specifies the interface name.
gigabitethernet Specifies the Gigabit Ethernet IEEE 802.3z.
port-channel Specifies the Ethernet channel interface.
tengigabitethernet Specifies the 10-Gigabit Ethernet.
tunnel Specifies the tunnel interface.
vlan Specifies the VLANs.
profile Specifies the LIF statistic profile information.
choice Specifies the choice of LIF statistics profiles.
all Specifies that the summary of all the available LIF statiscics profiles need to be
printed.
module Specifies the module selected for the command.
id number Specifies that the details of the matching LIF statistics profile ID need to be
printed. Range is 0–6.
read Specifies that the current LIF statistics profile needs to be printed.
write number Sets the LIF statistics profile according to the given valid profile index. Range is
0–6.
table Specifies the LIF statistics input tables.
config Specifies that the LIF statistics config register values needs to be printed.
egress Specifies that the egress LIF statistics input table needs to be printed.
fop Specifies that the forwarding operation memory table needs to be printed.
ingress Specifies that the ingress LIF statistics input table needs to be printed.
no-stat Specifies that the LIF no-statistics register values need to be printed.
status Specifies that the status of the LIF statistics register values need to be printed.
Defaults None
330
show platform hardware lif stats
Examples This example shows how to display platform hardware LIF statistics for index 4:
Router# show platform hardware lif stats index 4
331
show platform hardware ltl
Syntax Description index number Displays the LTL hardware setting on an index. Range is 0–65535.
interface Specifies the type of interface.
gigabitethernet Specifies the Gigabit Ethernet number.
number
tengigabitethernet Specifies the 10-Gigabit Ethernet number.
number
slot number Specifies the slot number.
vlan vlan_id Specifies the VLAN number. Range is 0–4096.
Defaults None
Examples This example shows how to display the LTL information for Gigabit Ethernet 4:
Router# show platform hardware ltl interface gigabitethernet 4
332
show platform hardware multicast routing
show platform hardware multicast routing {ip | ipv6} group {ip-addr [detail | verbose]}
Defaults None
Usage Guidelines The show platform hardware multicast routing ip group command displays multicast OIFs.
Examples This example shows how to display the hardware detail entries:
Router# show platform hardware multicast routing ip group 226.1.1.1 detail
(10.1.1.1, 226.1.1.1/32)
FIBAddr: 0xB00 IOSVPN: 0 RpfType: SglRpfChk SrcRpf: Gi1/1
CPx: 0 s_star_pri: 1 non-rpf drop: 0
Packets: 0 Bytes: 0
MET offset: 0x19
OIF AdjPtr Elif CR
+-------------+----------+-----------+--------+
EDT-50001 0x50001 0x8400A 1T1 5T1/T2
MET offset: 0x20
333
show platform hardware multicast routing
334
show platform hardware multicast routing
Command Description
show platform hardware cef mpls detail Displays MPLS CEF detail information.
show platform hardware met read Displays platform hardware MET table entries.
show platform software met detail Displays software routing for the MET.
335
show platform hardware met read
show platform hardware met read {slot slot-num | port port-num {addr addr}}
Syntax Description slot slot-num Displays the hardware MET table for the corresponding slot.
port port-num Displays the hardware MET entries for a port.
addr addr Displays the hardware MET information for the address of the slot or port.
Defaults None
Usage Guidelines The show platform hardware met read command displays MET table entry information. For each
adjancency use the show platform hardware cef adjacencies entry command to display the MPLS
adjacency information.
Examples This example shows how to display the hardware MET table entries for slot 1 address 18:
Router# show platform hardware met read slot 1 addr 18
Starting Offset: 0x0018
V E C:3989 I:0x00000 (A: 0x0A8000)
Router#
336
show platform hardware statistics
Defaults None
Examples This example shows how to display platform hardware statistics for module 4:
Router# show platform hardware statistics module 4
337
show platform hardware transceiver xml version
Defaults None
Usage Guidelines This command is useful only if a new transceiver XML version becomes available.
Examples This example shows how to display the HAL transceiver XML version information:
Router# show platform hardware transceiver xml version
Transceiver image bundle version: INVALID
Transceiver disk version : INVALID
Transceiver runtime using image bundle version: INVALID
Note It is normal for the command to display “INVALID” when the transceiver XML version has not been
upgraded.
338
show platform hardware virtual-map
Defaults None
339
show platform hardware xml version
Defaults None
Usage Guidelines This command is useful only if a new XML version becomes available.
This command is supported only on modules that have hardware abstraction layer (HAL) support.
Examples This example shows how to display the HAL XML version information for a module:
Router# show platform hardware xml version slot 4
XML image bundle version: 1.1
Note It is normal for the command to display “INVALID” when the XML version has not been upgraded.
340
show platform idbhal
show platform idbhal {applications detail | conversion {fib {lif number | ltl-index number | mih
number} | lif number | mih number} | interface {gigabitethernet number | null | port-channel
number | tengigabitethernet number | tunnel number | vlan vlan_id | detail} | process}
Examples This example shows how to display information for IDB interface tengigabitethernet 4:
Router# show platform idbhal interface tengigabitethernet 4
341
show platform idbhal
342
show platform idbhal conversion
show platform idbhal conversion {fib {lif number | ltl-index number | mih number} | lif number
| mih number}
Examples This example shows how to view platform hardware IDBHAL conversion for LIF 4:
Router# show platform idbhal conversion lif 4
343
show platform ip rsvp
show platform ip rsvp {interface {async number | auto-template number | ctunnel number |
dialer number | esconphy number | filter number | filtergroup number | gigabitethernet
number | group-async number | longreachethernet number | loopback number | mfr number
| multilink number | null number | port-channel number | portgroup number | pos-channel
number | sysclock number | tengigabitethernet number | tunnel number | vif number |
virtual-template number | virtual-tokenring number | vlan vlan_id | fcpa number | statistics
| voabypassin number | voabypassout number | voafilterin number | voafilterout number |
voain number | voaout number}} | netflow identity-string | statistics identity-string}
Syntax Description interface Displays the RSVP information for a particular interface.
async number Specifies the asynchronous interface number. Range is 1–999.
auto-template Specifies the auto-template interface number. Range is 1–999.
number
ctunnel number Specifies the Ctunnel interface number. Range is 0–2147483647.
dialer number Specifies the dialer interface number. Range is 0–255.
esconphy number Specifies the esconPhy interface number.
filter number Specifies the filter interface number.
filtergroup number Specifies the filter group interface number.
gigabitethernet Specifies the gigabit ethernet interface number.
number
longreachethernet Specifies the long-reach Ethernet interface number.
number
loopback number Specifies the loopback interface number. Range is 1–2147483647.
mfr number Specifies the multilink Frame Relay bundle interface number. Range is
1–2147483647.
multilink number Specifies the multilink-group interface number. Range is 1–2147483647.
null number Specifies the null interface number. Range is 0–0.
port-channel number Specifies the ethernet channel of interfaces. Range is 1–496.
portgroup number Specifies the portgroup interface number.
pos-channel number Specifies the PoS channel of interfaces. Range is 1–4094.
sysclock number Specifies the telecom-bus Clock Controller interface number.
tengigabitethernet Specifies the 10-Gigabit Ethernet interface number.
number
tunnel number Specifies the tunnel interface number. Range is 1–2147483647.
vif number Specifies the PGM multicast host interface number. Range is 1–1.
virtual-template Specifies the virtual template interface number. Range is 1–200.
number
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
344
show platform ip rsvp
Examples This example shows how to display the RSVP information for the platform IP with asynchronous
interface 4:
Router# show platform ip rsvp interface async 4
345
show platform l2transport gre
show platform l2transport gre {nodes | summary tunnel _if _number | vlan vlan_id <peerrid>
clear-counter}
Examples This example shows how to display platform details of Layer 2 over GRE tunnel 4:
Router# show platform l2transport gre tunnel 4
346
show platform mrm info
347
show platform multicast routing
Examples This example shows how to display LTL-sharing across VLANs in multicast routing configuration:
Router# show platform multicast routing replication
348
show platform nvhmr
show platform nvhmr {current {all | entry number | summary} | previous{all | entry number |
summary}}
Syntax Description current Specifies NVHMR for the current running instance.
all Displays all information on specified NVHMR.
entry number Displays information on specified NVHMR for entry number. Range is 0–5.
summary Displays summary information for specified NVHMR.
previous Specifies NVHMR for the previously ran instance.
Examples This example shows how to display platform NVHMR of current entry number 4:
Router# show platform nvhmr current entry 4
349
show platform qos aggregate policer
Usage Guidelines Aggregate policing works independently on each Distributed Forwarding Card (DFC)-equipped
switching module and independently on the Policy Feature Card 2 (PFC2), which supports any
non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from
different DFC-equipped switching modules. You can display aggregate-policing statistics for each
DFC-equipped switching module, the PFC2, and any non-DFC-equipped switching modules that are
supported by the PFC2.
Examples This example shows how to display information about the aggregate policer for platform QoS:
Router# show platform qos aggregate-policer
ag1 (undefined)
AgId=0 [ pol1 pol2 ]
ag2 64000 64000 conform-action set-dscp-transmit 56 exceed-action drop
AgId=0 [ pol3 ]
ag3 32000 32000 conform-action set-dscp-transmit 34 exceed-action drop
350
show platform qos aggregate policer
351
show platform qos maps
Cisco 2600, 3660, 3700, 3845, 7200, 7400, and 7500 Series Routers
Syntax Description cos-dscp (Optional) Displays the class of service (CoS)-to-differentiated services
code point (DSCP) map.
dscp-cos (Optional) Displays the DSCP-to-CoS map.
cos-mutation (Optional) Displays the CoS-mutation map.
dscp-exp (Optional) Displays the DSCP-to-exp map.
dscp-mutation (Optional) Displays the DSCP-mutation map.
exp-dscp (Optional) Displays the exp-to-DSCP map.
exp-mutation (Optional) Displays the exp-mutation map.
ip-prec-dscp (Optional) Displays the IP-precedence-to-DSCP map.
policed-dscp (Optional) Displays the policed-DSCP map.
Usage Guidelines Maps are used to generate an internal DSCP value, which represents the priority of the traffic. Use the
show platform qos maps command without keywords to display all maps.
352
show platform qos maps
Examples The following is sample output from the show platform qos maps cos-dscp command displaying the
DSCP values to which each CoS value will be mapped:
Router# show platform qos maps cos-dscp
Cos-dscp map:
cos: 0 1 2 3 4 5 6 7
--------------------------------
dscp: 8 8 8 8 24 32 56 56
The following is sample output from the show platform qos maps dscp-cos command displaying the
CoS values to which each DSCP value will be mapped:
Router# show platform qos maps dscp-cos
Dscp-cos map:
dscp: 0 8 10 16 18 24 26 32 34 40 46 48 56
-----------------------------------------------
cos: 0 1 1 1 2 2 3 3 4 4 5 6 7
Policed-dscp map:
0 1 2 3 4 5 6 7 8 9
----------------------------------
00: 00 01 02 03 04 05 06 07 08 09
10: 10 11 12 13 14 15 16 17 18 19
20: 20 21 22 23 24 25 26 27 28 29
30: 30 31 32 33 34 35 36 37 38 39
40: 40 41 42 43 44 45 46 47 48 49
50: 50 51 52 53 54 55 56 57 58 59
60: 60 61 62 63
Dscp-cos map:
0 1 2 3 4 5 6 7 8 9
----------------------------------
00: 00 00 00 00 00 00 00 00 01 01
10: 01 01 01 01 01 01 02 02 02 02
20: 02 02 02 02 03 03 03 03 03 03
30: 03 03 04 04 04 04 04 04 04 04
40: 05 05 05 05 05 05 05 05 06 06
50: 06 06 06 06 06 06 07 07 07 07
60: 07 07 07 07
Cos-dscp map:
cos: 0 1 2 3 4 5 6 7
----------------------------------
dscp: 0 8 16 24 32 40 48 56
IpPrecedence-dscp map:
ipprec: 0 1 2 3 4 5 6 7
----------------------------------
dscp: 0 8 16 24 32 40 48 56
Router#
In the policed DSCP and DSCP-CoS map displays, the new DSCP or CoS values are shown in the body
of the table. The decade of the original DSCP value is shown in the left-side vertical column, and the
units digit is in the top row. For example, the DSCP-CoS map indicates that if the original DSCP value
is between 32 and 39, the CoS will be set to 4.
353
show platform qos maps
The CoS-DSCP and IP precedence-DSCP maps display the DSCP values to which each CoS or IP
precedence value will be mapped. For example, the IP precedence-DSCP map indicates that if the
original IP precedence value is 3, the DSCP will be set to 24.
This example shows how to verify the configuration of DSCP-mutation mapping:
Router# show platform qos maps | begin DSCP mutation
In the DSCP mutation map display, the marked-down DSCP values are shown in the body of the table.
The first digit (d1) of the original DSCP value is in the left-side vertical column labeled d1, and the
second digit (d2) is in the top row. For example, a DSCP value of 30 maps to a new DSCP value of 08.
354
show platform redundancy
show platform redundancy {atm | bias | ccb slot-number cpu-number | cwpa-ce3 | cwpa-ct3 |
cwpa-e1 | cwpa-stm1 | cwpa-t1 | frame-relay | hdlc | if-config {slot-number cpu-number
[bay-number] | default-retvals} | mlp | multilink-vc | osm-chocx | osm-ct3 | ppp | shadowstate
| spa-chocx | spa-ct3 | switchover}
355
show platform redundancy
Examples The following is sample output from the show platform redundancy command with the if-config
keyword. The fields are self-explanatory.
Router# show platform redundancy if-config 4 0
356
show platform software acl
show platform software acl {accounting-tbl {index number} | acct-xlt-tbl {in {index number} |
out {index number}} | appid {in number | out number} | capmap {tcam {A {index | module}
| B {index | module}}} | cm-readiness {module} | compaction {detail {module} | label
{tcam {A | B}} | module number} | entry {module} | label {tcam{A | B}} | lou {index number
| module number} | tcam {count {module}} | tcp-flags-tbl {detail {module} | index number
| module number} | v6-extnhdr-tbl {detail | index | module}}
Defaults None
357
show platform software acl
Examples This example shows how to display platform software ACL application ID Acct-Xlt in entry 4:
Router# show platform software acl appid in 4
358
show platform software debug
Defaults None
Examples This example shows how to display the platform software debug logging details:
Router# show platform software debug
359
show platform software e8-recovery
Defaults None
Examples This example shows how to display the platform EARL8 software print recovery patch settings:
Router# show platform software e8-recovery config
360
show platform software earl layer2
Defaults None
Examples This example shows how to display the cleared purged ports per counter in the platform software EARL
Layer 2 configuration:
Router# show platform software earl layer2 l2-opt_stp_purge clear
361
show platform software fabric
show platform software fabric {errors | serdes {info {module number} | supervisor slot} |
state-machine {channel {event_trace number | state number} | linecard {event_trace
number | state number}} | timeout}
Defaults None
Examples This example shows how to display the fabric timeout errors:
Router# show platform software fabric timeout
362
show platform software feature-manager acg-v4
show platform software feature-manager acg-v4 {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
363
show platform software feature-manager acg-v4
Defaults None.
Examples This example shows how to display the IPv4 access group information on all interfaces:
Router# show platform software feature-manager acg-v4 all
364
show platform software feature-manager arp-acl
Defaults None.
Examples This example shows how to display the ARP ACL information on all interfaces:
Router# show platform software feature-manager arp-acl all
365
show platform software feature-manager cm-requests
Defaults None.
Examples This example shows how to display the feature manager requests/responses sent to CM:
Router# show platform software feature-manager cm-requests
366
show platform software feature-manager cts-l3s
show platform software feature-manager cts-l3s {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
Syntax Description all Specifies feature manager CTS layer 3 simplified information on all
interfaces.
interface Specifies interface-related feature manager CTS Layer 3 simplified
information.
async number Specifies the asynchronous interface number. Range is 1–999.
auto-template number Specifies the auto-template interface number. Range is 1–999.
ctunnel number Specifies the Ctunnel interface number. Range is 0–2147483647.
dialer number Specifies the dialer interface number. Range is 0–255.
esconphy number Specifies the esconPhy interface number. Range is 1–6.
filter number Specifies the filter interface number. Range is 1–6.
filtergroup number Specifies the filter group interface number. Range is 1–6.
gigabitethernet Specifies the gigabit Ethernet interface number. Range is 1–6.
number
longreachethernet Specifies the long-reach Ethernet interface number. Range is 1–6.
number
loopback number Specifies the loopback interface number. Range is 1–2147483647.
mfr number Specifies the multilink Frame Relay bundle interface number. Range is
1–2147483647.
multilink number Specifies the multilink-group interface number. Range is 1–2147483647.
null number Specifies the null interface number. Range is 0–0.
port-channel number Specifies the Ethernet channel of interfaces. Range is 1–496.
portgroup number Specifies the portgroup interface number. Range is 1–6.
pos-channel number Specifies the PoS channel of interfaces. Range is 1–4094.
sysclock number Specifies the telecom-bus Clock Controller interface number. Range is 1–6.
tengigabitethernet Specifies the 10-Gigabit Ethernet interface number. Range is 1–6.
number
tunnel number Specifies the tunnel interface number. Range is 1–2147483647.
vif number Specifies the PGM multicast host interface number. Range is 1–1.
virtual-template Specifies the virtual template interface number. Range is 1–200.
number
367
show platform software feature-manager cts-l3s
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
control-plane number Specifies the control plane interface number. Range is 1–6.
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout number Specifies the VOA bypass-out interface number. Range is 1–6.
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
Defaults None.
Examples This example shows how to display the feature manager CTS Layer 3 simplified information on all
interfaces:
Router# show platform software feature-manager cts-l3s all
368
show platform software feature-manager dai
Defaults None.
Examples This example shows how to display the DAI information on all interfaces:
Router# show platform software feature-manager dai all
369
show platform software feature-manager dhcp-snooping
Defaults None.
Examples This example shows how to display the DHCP snooping information on all interfaces:
Router# show platform software feature-manager dhcp-snooping all
370
show platform software feature-manager features
Defaults None.
Examples This example shows how to display brief information about all interfaces:
Router# show platform software feature-manager features brief
Interface: Control Plane Interface IP is disabled; admin_state is up
hw_state[INGRESS] = not reduced, hw_state[EGRESS] = not reduced
mcast = 0
priority = 0
flags = 0x0
parent[INGRESS] = none
outbound label: 2
Feature IP_QOS_EGRESS:
Feature IPV6_QOS_EGRESS:
Feature OTHER_QOS_EGRESS:
Feature ARP_QOS_EGRESS:
Feature MPLS_QOS_EGRESS:
Interface: Control Plane Interface.1 IP is disabled; admin_state is up
hw_state[INGRESS] = not reduced, hw_state[EGRESS] = not reduced
mcast = 0
priority = 0
flags = 0x0
parent[INGRESS] = none
outbound label: 1
Feature GRE Tunnel Decapsulation:
Feature Tunnel Decapsulation:
Feature IPv6 GRE Tunnel Decapsulation:
Feature IPv6 Tunnel Decapsulation:
371
show platform software feature-manager features
372
show platform software feature-manager fie
show platform software feature-manager fie {all | app-req-state | appid {protocol | shadow
protocol} | feat-index | fidb | fie-shadow {feat-index | interface | nf-recirc {all | appid
number}} | flowmask {detail} | interface {async number | auto-template number | ctunnel
number | dialer number | esconphy number | filter number | filtergroup number |
gigabitethernet number | group-async number | longreachethernet number | loopback
number | mfr number | multilink number | null number | port-channel number | portgroup
number | pos-channel number | sysclock number | tengigabitethernet number | tunnel number
| vif number | virtual-template number | virtual-tokenring number | vlan vlan_id |
control-plane number | fcpa number | voabypassin number | voabypassout number |
voafilterin number | voafilterout number | voain number | voaout number} | label {number |
stats {all}} | mergetable | oir {module number} | profile {protocol | shadow protocol} |
shadowlabel number | summary}
373
show platform software feature-manager fie
Defaults None.
374
show platform software feature-manager fie
Examples This example shows how to display the platform feature manager FIE summary:
Router# show platform software feature-manager fie summary
375
show platform software feature-manager interface
Syntax Description async number Specifies the asynchronous interface number. Range is 1–999.
auto-template Specifies the auto-template interface number. Range is 1–999.
number
ctunnel number Specifies the Ctunnel interface number. Range is 0–2147483647.
dialer number Specifies the dialer interface number. Range is 0–255.
esconphy number Specifies the esconPhy interface number. Range is 1–6.
filter number Specifies the filter interface number. Range is 1–6.
filtergroup number Specifies the filter group interface number. Range is 1–6.
gigabitethernet Specifies the gigabit Ethernet interface number. Range is 1–6.
number
longreachethernet Specifies the long-reach Ethernet interface number. Range is 1–6.
number
loopback number Specifies the loopback interface number. Range is 1–2147483647.
mfr number Specifies the multilink Frame Relay bundle interface number. Range is
1–2147483647.
multilink number Specifies the multilink-group interface number. Range is 1–2147483647.
null number Specifies the null interface number. Range is 0–0.
port-channel number Specifies the Ethernet channel of interfaces. Range is 1–496.
portgroup number Specifies the portgroup interface number. Range is 1–6.
pos-channel number Specifies the PoS channel of interfaces. Range is 1–4094.
sysclock number Specifies the telecom-bus Clock Controller interface number. Range is 1–6.
tengigabitethernet Specifies the 10-Gigabit Ethernet interface number. Range is 1–6.
number
tunnel number Specifies the tunnel interface number. Range is 1–2147483647.
vif number Specifies the PGM multicast host interface number. Range is 1–1.
virtual-template Specifies the virtual template interface number. Range is 1–200.
number
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
376
show platform software feature-manager interface
Defaults None.
Examples This example shows how to display the feature manager information on all interfaces:
Router# show platform software feature-manager interface voaout 4
377
show platform software feature-manager ip-admission
show platform software feature-manager ip-admission layer2 {all | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
show platform software feature-manager ip-admission layer3 {all | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
378
show platform software feature-manager ip-admission
Defaults None.
Examples This example shows how to display the IP admission information on all Layer 2 interfaces:
Router# show platform software feature-manager ip-admission layer2 all
379
show platform software feature-manager ip-recirculate
380
show platform software feature-manager ip-recirculate
Defaults None.
Examples This example shows how to display the IP recirculate information on all interfaces:
Router# show platform software feature-manager ip-recirculate all
381
show platform software feature-manager ipv6
show platform software feature-manager ipv6 pacl {all | brief | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
show platform software feature-manager ipv6 rpf {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
show platform software feature-manager ipv6 traffic-filter {all | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
382
show platform software feature-manager ipv6
Defaults None.
383
show platform software feature-manager ipv6
Examples This example shows how to display the IPv6 PACL information on all interfaces:
Router# show platform software feature-manager ipv6 pacl all
384
show platform software feature-manager label
Syntax Description number Specifies the virtual label number. Range is 1–2000.
Defaults None.
385
show platform software feature-manager nat
show platform software feature-manager nat {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number} | netflow}
386
show platform software feature-manager nat
Defaults None.
Examples This example shows how to display the NAT information on all interfaces:
Router# show platform software feature-manager nat all
387
show platform software feature-manager netflow
Defaults None.
Examples This example shows how to display the NetFlow information for counters:
Router# show platform software feature-manager netflow counters
388
show platform software feature-manager pacl
show platform software feature-manager pacl {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
389
show platform software feature-manager pacl
Defaults None.
Examples This example shows how to display the PACL information on all interfaces:
Router# show platform software feature-manager pacl all
390
show platform software feature-manager pbr
show platform software feature-manager pbr {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
391
show platform software feature-manager pbr
Defaults None.
Examples This example shows how to display the PBR information on all interfaces:
Router# show platform software feature-manager pbr all
392
show platform software feature-manager private-hosts
393
show platform software feature-manager private-hosts
Defaults None.
Examples This example shows how to display the private hosts information on all interfaces:
Router# show platform software feature-manager private-hosts all
394
show platform software feature-manager rdt-indices
Defaults None.
Examples This example shows how to display the redirect LDL indices information on all interfaces:
Router# show platform software feature-manager rdt-indices
395
show platform software feature-manager rpf
show platform software feature-manager rpf {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
396
show platform software feature-manager rpf
Defaults None.
Examples This example shows how to display the RPF information on all interfaces:
Router# show platform software feature-manager rpf all
397
show platform software feature-manager scl
show platform software feature-manager scl {all | brief | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number} | netflow}
398
show platform software feature-manager scl
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
control-plane Specifies the control plane interface number. Range is 1–6.
number
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass-out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
Defaults None.
Examples This example shows how to display the SCL information on all interfaces:
Router# show platform software feature-manager scl all
399
show platform software feature-manager summary
Defaults None.
Examples This example shows how to display the feature manager summary information:
Router# show platform software feature-manager summary
400
show platform software feature-manager sve
show platform software feature-manager sve {all | brief | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number} | netflow}
401
show platform software feature-manager sve
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
control-plane Specifies the control plane interface number. Range is 1–6.
number
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass-out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
Defaults None.
Examples This example shows how to display the SVE information on all interfaces:
Router# show platform software feature-manager sve all
402
show platform software feature-manager tcp-mss
show platform software feature-manager tcp-mss {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
403
show platform software feature-manager tcp-mss
Defaults None.
Examples This example shows how to display the TCP-MSS information on all interfaces:
Router# show platform software feature-manager tcp-mss all
404
show platform software feature-manager vacl
show platform software feature-manager vacl {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
405
show platform software feature-manager vacl
Defaults None.
Examples This example shows how to display the VACLformation on all interfaces:
Router# show platform software feature-manager vacl all
406
show platform software feature-manager wccp
show platform software feature-manager wccp {all | inband | interface {async number |
auto-template number | ctunnel number | dialer number | esconphy number | filter number |
filtergroup number | gigabitethernet number | longreachethernet number | loopback number
| mfr number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | control-plane
number | fcpa number | voabypassin number | voabypassout number | voafilterin number |
voafilterout number | voain number | voaout number}}
407
show platform software feature-manager wccp
virtual-tokenring Specifies the virtual token ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the fibre channel interface number. Range is 1–6.
control-plane Specifies the control plane interface number. Range is 1–6.
number
voabypassin number Specifies the VOA bypass-in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass-out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter-in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter-out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
Defaults None.
Examples This example shows how to display the WCCP information on all interfaces:
Router# show platform software feature-manager wccp all
408
show platform software flow internal
show platform software flow internal {mgmt statistics | search statistics | fnf statistics | export
statistics | driver statistics | api statistics | em statistics | am statistics | tt statistics | yn
statistics | cli statistics | interrupt statistics | ehsa statistics}
Defaults None
Examples This example shows how to display platform software flow internal management statistics:
Router# show platform software flow internal mgmt statistics
409
show platform software flow internal
410
show platform software lif l2
Defaults None
Examples This example shows how to display platform software LIF Layer 2 API statistics that are cleared:
Router# show platform software lif l2 api_statistics clear
Related Commands
411
show platform software lif l2
Command Description
platform software lif l2 Configures the platform software for Layer 2 LIF.
412
show platform software lif l3
show platform software lif l3 {api_stats {display {module number} | reset {module}} | block
number | handle number | icc_stats {display {module} | reset{module}} | index number |
inheritance{egress {module} | ingress {module}} | mem_stats {display {module} | reset
{module}} | mtu{table {dump{module} | index number}} | region {all {module} | id number
| summary {module}} | special {module} | tml_stats {display {module}}}
Defaults None
413
show platform software lif l3
Examples This example shows how to display platform software LIF Layer 3 API statistics for module 4:
Router# show platform software lif l3 api_stats display module 4
414
show platform software lif stats
show platform software lif stats {agg {bdindex number | index number} | index number |
interface {gigabitethernet number | port-channel number | tengigabitethernet number |
tunnel number | vlan vlan_id}}
Syntax Description agg Specifies the software aggregate LIF statistics information.
bdindex number Specifies the LIF BD index. Range is 0–16383.
index number Specifies the LIF statistics index. Range is 0–131071.
index number Specifies the LIF index. Range is 0–131071.
interface Specifies the interface name.
gigabitethernet Specifies the Gigabit Ethernet IEEE 802.3z. Range is 1–6.
number
port-channel Specifies the Ethernet channel interface. Range is 1–496.
number
tengigabitethernet Specifies the 10-Gigabit Ethernet. Range is 1–6.
number
tunnel number Specifies the tunnel interface. Range is 0–2147483647.
vlan vlan_id Specifies the Catalyst VLANs. Range is 1–4094.
Defaults None
Examples This example shows how to display platform software aggregate LIF statistics information for BD index
4:
Router# show platform software lif stats agg bdindex 4
415
show platform software ltl
show platform software ltl {allocation | assigned | callback | regions | router | span |
well-known-index}
Defaults None
Examples This example shows how to display the platform software LTL regions information:
Router# show platform software ltl regions
416
show platform software met
Defaults None
Examples This example shows how to display platform software MET information in detail:
Router# show platform software met detail
417
show platform software met detail
Defaults None
Usage Guidelines
Examples This example shows how to display software routing for the MET:
Router# show platform software met detail
Replication Engine(s) in Slot : 5
MET start address: 0x4
MET end address: 0x7FFE
MET total entries: 32744
MET free entries: 14
MET allocation profile: [10% size 2, 30% size 4, 50% size 8, 10% size 16]
418
show platform software met detail
Command Description
show platform hardware cef Displays a single adjacency entry index.
adjacencies entry
show platform hardware cef mpls detail Displays MPLS CEF detail information.
show platform hardware multicast Matches and displays multicast routing group IP
routing addresses.
show platform hardware met read Displays platform hardware MET table entries.
419
show platform software oir
show platform software oir {debug {all number | mask number | oir_mask number | stdby_reset
| swover_data_path_mask number | swover_global_mask number | swover_time_mask
number} | pmb {registers number} | seq-sync-info number | state-machine number}
Defaults None
Examples This example shows how to display the platform software OIR debug information for mask 4:
Router# show platform software oir debug mask 4
420
show platform software oir
421
show platform software stub
show platform software stub {all | traceback {disable {stub-function-id number} | enable
{stub-function-id number}} | used}
Defaults None
Examples This example shows how to display the platform software stub disabled traceback with stub function ID
4:
Router# show platform software stub traceback disable stub-function-id 4
422
show platform software xconnect
show platform software xconnect {circuit-index {all | interface {async number | auto-template
number | ctunnel number | dialer number | esconphy number | filter number | filtergroup
number | gigabitethernet number | longreachethernet number | loopback number | mfr
number | multilink number | null number | port-channel number | portgroup number |
pos-channel number | sysclock number | tengigabitethernet number | tunnel number | vif
number | virtual-template number | virtual-tokenring number | vlan vlan_id | fcpa number |
voabypassin number | voabypassout number | voafilterin number | voafilterout number |
voain number | voaout number}} | mac-addr | pstats}
423
show platform software xconnect
virtual-tokenring Specifies the virtual Token Ring interface number. Range is 1–2147483647.
number
vlan vlan_id Specifies the VLAN interface number. Range is 1–4094.
fcpa number Specifies the Fibre Channel interface number. Range is 1–6.
voabypassin number Specifies the VOA bypass in interface number. Range is 1–6.
voabypassout Specifies the VOA bypass out interface number. Range is 1–6.
number
voafilterin number Specifies the VOA filter in interface number. Range is 1–6.
voafilterout number Specifies the VOA filter out interface number. Range is 1–6.
voain number Specifies the VOA in interface number. Range is 1–6.
voaout number Specifies the VOA out interface number. Range is 1–6.
mac-addr Specifies the proxy ARP MAC address.
pstats Specifies the packet statistics.
Defaults None
Examples This example shows how to display the platform software xConnect packet statistics:
Router# show platform software xconnect pstats
424
show platform supervisor
Syntax Description mtu Displays supervisor operating maximum tranmission unit (MTU).
slot slot-number Displays information for the specified slot.
port port-number Displays information for the specified port.
Examples The following is sample output from the show platform supervisor command. The fields are
self-explanatory.
Router# show platform supervisor mtu slot 5 port 1
425
show platform supervisor mtu
Syntax Description slot number Specifies the slot number. Range is 1–6.
Examples This example shows how to display information on platform supervisor operating MTU slot 4:
Router# show platform supervisor mtu slot 5
426
show vlan group
Syntax Description group-name (Optional) Displays the VLANs mapped to the specified VLAN group.
group-name
user-count (Optional) Displays the user count of the group’s VLANs.
Usage Guidelines The show vlan group command displays the existing VLAN groups and lists the VLANs and VLAN
ranges that are members of each VLAN group. If the group-name keyword is entered, only the members
of the VLAN group specified by the group-name argument are displayed.
Examples This example shows how to display the members of a specified VLAN group:
Router# show vlan group group-name ganymede
This example shows how to display the user count for a specified group:
Router# show vlan group group-name ganymede user-count
VLAN : Count
-------------------
3 : 0
4 : 0
5 : 0
Router#
427
snmp-server enable traps errdisable
Syntax Description notification-rate rate (Optional) Sets the number of notifications per minute.
Examples This example shows how to enable the SNMP errdisable notifications:
Router(config)# snmp-server enable traps errdisable
Router(config)#
This example shows how to set the SNMP errdisable notification rate to 500 per minute:
Router(config)# snmp-server enable traps errdisable notification-rate 500
Router(config)#
428
snmp-server enable traps power-ethernet
Syntax Description group number Sets the group number; valid values are 1 to 13.
Usage Guidelines This command enables SNMP traps only. It does not support inform requests.
Examples The following example shows how to set the notifications for power-ethernet group 3:
Router(config)# snmp-server enable traps power-ethernet group 3
429
snmp-server enable traps trustsec-sxp
Usage Guidelines SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
If you do not specify any of the optional keywords, all TrustSec SXP notifications are enabled.
The snmp-server enable traps snmp command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples The following example shows how to enable the router to enable ctsxSxpBindingConflictNotif
notifications:
430
snmp-server enable traps trustsec-sxp
The following example shows how to enable the router to enable ctsxSxpBindingErrNotif notifications:
Router(config)# snmp-server enable traps trustsec-sxp binding-err
The following example shows how to enable the router to enable ctsxSxpBindingExpnFailNotif
notifications:
Router(config)# snmp-server enable traps trustsec-sxp binding-expn-fail
The following example shows how to enable the router to enable ctsxSxpConnConfigErrNotif
notifications:
Router(config)# snmp-server enable traps trustsec-sxp conn-config-err
The following example shows how to enable the router to enable ctsxSxpConnDownNotif notifications:
Router(config)# snmp-server enable traps trustsec-sxp conn-down
The following example shows how to enable the router to enable ctsxSxpConnUpNotif notifications:
Router(config)# snmp-server enable traps trustsec-sxp conn-up
The following example shows how to enable the router to enable ctsxSxpMsgParseErrNotif
notifications:
Router(config)# snmp-server enable traps trustsec-sxp msg-parse-err
The following example shows how to enable the router to enable ctsxSxpConnConfigErrNotif
notifications:
Router(config)# snmp-server enable traps trustsec-sxp conn-config-err
The following example shows how to enable the router to enable ctsxSxpOperNodeIdChangeNotif
notifications:
Router(config)# snmp-server enable traps trustsec-sxp oper-nodeid-change
431
switch pmk
switch pmk
To enable VSL on the switch, use the switch pmk command in Privileged EXEC mode. To disable VSL
use the no form of the command.
Syntax Description hex-data Pairwise Master Key (PMK) without the leading 0x.
Defaults None
Usage Guidelines You must enter an even number of hexidecimal characters or prefix the last character with a zero.
432
switchport trunk
switchport trunk
To set the trunk characteristics when the interface is in trunking mode, use the switchport trunk
command in interface configuration mode. To reset all of the trunking characteristics back to the original
defaults, use the no form of this command.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
switchport trunk {encapsulation {isl | dot1q [ethertype value] | negotiate}} | { native vlan {tag
| vlan-id}} | {allowed vlan vlan-list} | {pruning vlan vlan-list}
no switchport trunk {encapsulation {isl | dot1q [ethertype value] | negotiate} | native vlan [tag]|
allowed vlan | pruning vlan}
Syntax Description encapsulation isl Sets the trunk encapsulation format to Inter-Switch Link (ISL).
encapsulation dot1q Sets the trunk encapsulation format to 802.1Q.
native vlan Sets the native VLAN for the trunk in 802.1Q trunking mode.
allowed vlan vlan-list Sets the list of allowed VLANs that transmit traffic from this interface in
tagged format when in trunking mode.
ethertype value (Optional) Sets the EtherType value; valid values are from 0x0 to
0x5EF-0xFFFF.
encapsulation Specifies that if the Dynamic Inter-Switch Link (DISL) protocol and
negotiate Dynamic Trunking Protocol (DTP) negotiation do not resolve the
encapsulation format, ISL is the selected format.
native vlan tag Enables the native VLAN tagging state on the interface.
native vlan vlan-id The particular native VLAN.
pruning vlan vlan-list Sets the list of VLANs that are enabled for VLAN Trunking Protocol (VTP)
pruning when the interface is in trunking mode. See the “Usage Guidelines”
section for the vlan-list argument formatting guidelines.
Defaults Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
• The default encapsulation type is dot1q.
• The default access VLAN and trunk interface native VLAN are default VLANs that correspond to
the platform or interface hardware.
• The default for all VLAN lists is to include all VLANs.
433
switchport trunk
434
switchport trunk
• Because Cisco switches transmit BPDUs to the SSTP multicast MAC address on VLANs other than
the native VLAN of the trunk, switches that are not Cisco switches do not recognize these frames as
BPDUs and flood them on all ports in the corresponding VLAN. Other Cisco switches connected to
the 802.1Q cloud receive these flooded BPDUs. This condition allows Cisco switches to maintain a
per-VLAN spanning-tree topology across a cloud of 802.1Q switches that are not Cisco switches.
The 802.1Q cloud of switches separating the Cisco switches is treated as a single broadcast segment
among all switches connected to the 802.1Q cloud of switches that are not Cisco switches through
802.1Q trunks.
• Make sure that the native VLAN is the same on all of the 802.1Q trunks that connect the Cisco
switches to the 802.1Q cloud of switches that are not Cisco switches.
• If you are connecting multiple Cisco switches to a 802.1Q cloud of switches that are not Cisco
switches, all of the connections must be through 802.1Q trunks. You cannot connect Cisco switches
to an 802.1Q cloud of switches that are not Cisco switches through ISL trunks or through access
ports. Doing so will cause the switch to place the ISL trunk port or access port into the spanning-tree
“port inconsistent” state and no traffic will pass through the port.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
The switchport trunk encapsulation command is supported only for platforms and interface hardware
that can support 802.1Q formats.
The vlan-list format is all | none | add | remove | except vlan-list[,vlan-list...] where:
• all—Specifies all VLANs from 1 to 1005. Beginning with Cisco IOS Release 12.4(15)T, the valid
VLAN ID range is from 1 to 4094.
• none—Indicates an empty list. This keyword is not supported in the switchport trunk allowed vlan
form of the command.
• add—Adds the defined list of VLANs to those currently set instead of replacing the list.
• remove—Removes the defined list of VLANs from those currently set instead of replacing the list.
• except—Lists the VLANs that should be calculated by inverting the defined list of VLANs.
• vlan-list—Is either a single VLAN number from 1 to 1005 or a continuous range of VLANs
described by two VLAN numbers, the lesser one first, separated by a hyphen that represents the
VLAN IDs of the allowed VLANs when this port is in trunking mode. Beginning with
Cisco IOS Release 12.4(15)T, the valid VLAN ID range is from 1 to 4094.
The switchport trunk encapsulation dot1q command is supported only for platforms and interface
hardware that can support both ISL and 802.1Q formats. Only 802.1Q encapsulation is supported by
shared port adapters (SPAs).
The switchport trunk encapsulation isl command is not supported in Cisco IOS Release 12.2(50)SY.
If you enter the switchport trunk encapsulation isl command on a port channel containing an interface
that does not support ISL-trunk encapsulation, the command is rejected.
You can enter the switchport trunk allowed vlan command on interfaces where the span destination
port is either a trunk or an access port.
435
switchport trunk
You can enter the switchport trunk native vlan tag command to enable the tagging of native VLAN
traffic on a per-port basis. When tagging is enabled, all the packets on the native VLAN are tagged and
all incoming untagged data packets are dropped, but untagged control packets are accepted. When
tagging is disabled, the native VLAN packets going out on trunk ports are not tagged and the incoming
untagged packets are allowed and assigned to the native VLAN. The no switchport trunk native vlan
tag command overrides the vlan dot1q tag native command for global tagging.
Note The switchport trunk native vlan tag interface configuration mode command does not enable native
VLAN tagging unless you first configure the switch to tag native VLAN traffic globally. To enable native
VLAN tagging globally, use the vlan dot1q tag native command in global configuration mode.
Note The switchport trunk pruning vlan vlan-list command does not support extended-range VLANs; valid
vlan-list values are from 1 to 1005.
The dot1q ethertype value keyword and argument are not supported on port-channel interfaces. You can
enter the command on the individual port interface only. Also, you can configure the ports in a channel
group to have different EtherType configurations.
The switchport trunk encapsulation negotiate command is not supported in Cisco IOS Release
12.2(50)SY.
Caution Be careful when configuring the custom EtherType value on a port. If you enter the negotiate keyword
and DISL and Dynamic Trunking Protocol (DTP) negotiation do not resolve the encapsulation format,
then ISL is the selected format and may pose as a security risk. The no form of this command resets the
trunk-encapsulation format to the default.
• The no form of the switchport trunk native vlan command resets the native mode VLAN to the
appropriate default VLAN for the device.
• The no form of the switchport trunk native vlan tag command configures the Layer 2 port not to
tag native VLAN traffic.
• The no form of the switchport trunk allowed vlan command resets the list to the default list, which
allows all VLANs.
• The no form of the switchport trunk pruning vlan command resets the list to the default list, which
enables all VLANs for VTP pruning.
• The no form of the switchport trunk encapsulation dot1q ethertype value command resets the
list to the default value.
The vlan-list format is all | none | add | remove | except [vlan-list[,vlan-list...]] where:
• all—Specifies all the appropriate VLANs. This keyword is not supported in the switchport trunk
pruning vlan command.
• none—Indicates an empty list. This keyword is not supported in the switchport trunk allowed vlan
command.
• add vlan-list[,vlan-list...]—Adds the defined list of VLANs to those currently set instead of
replacing the list.
436
switchport trunk
• remove vlan-list[,vlan-list...]—Removes the defined list of VLANs from those currently set instead
of replacing the list. You can remove VLAN 1. If you remove VLAN 1 from a trunk, the trunk
interface continues to send and receive management traffic (for example, Cisco Discovery Protocol,
version 3; VTP; Port Aggregation Protocol, version 4 (PAgP4); and DTP) in VLAN 1.
Note You can remove any of the default VLANs (1002 to 1005) from a trunk; this action is not allowed
in earlier releases.
• except vlan-list[,vlan-list...]—Excludes the specified list of VLANs from those currently set instead
of replacing the list.
• vlan-list[,vlan-list...]—Specifies a single VLAN number from 1 to 4094 or a continuous range of
VLANs that are described by two VLAN numbers from 1 to 4094. You can specify multiple VLAN
numbers or ranges of numbers using a comma-separated list.
To specify a range of VLANs, enter the smaller VLAN number first, separated by a hyphen and the
larger VLAN number at the end of the range.
Do not enable the reserved VLAN range (1006 to 1024) on trunks when connecting a Cisco 7600 series
router running the Cisco IOS software on both the supervisor engine and the Multilayer Switch Feature
Card (MSFC) to a Cisco 7600 series router running the Catalyst operating system. These VLANs are
reserved in Cisco 7600 series routers running the Catalyst operating system. If enabled, Cisco 7600
series routers running the Catalyst operating system may disable the ports if a trunking channel is
between these systems.
Examples The following example shows how to cause a port interface configured as a switched interface to
encapsulate in 802.1Q trunking format regardless of its default trunking format in trunking mode:
Router(config-if)# switchport trunk encapsulation dot1q
The following example shows how to configure the Layer 2 port to tag native VLAN traffic:
Router(config-if)# switchport trunk native vlan tag
437
test platform software console disconnect-timeout
Syntax Description time Specifies the time in seconds; valid values are 1 through 10.
Examples This example shows how to set the disconnect timeout test to 4 seconds:
Router# test platform software console disconnect-timeout 4
438
test snmp trap errdisable ifevent
Examples This example shows the output of test snmp trap errdisable ifevent when snmp-server enable traps
errdisable is not configured:
Router# test snmp trap errdisable ifevent
cErrDisableInterfaceEventRev1 notification is disabled.
Router#
This example shows the output of test snmp trap errdisable ifevent when snmp-server enable traps
errdisable is configured:
Router# test snmp trap errdisable ifevent
cErrDisableInterfaceEventRev1 notification was sent.
Router#
439
test snmp trap trustsec-server provision-secret
440
test snmp trap trustsec-server radius-server
441
test snmp trap trustsec-sxp
Usage Guidelines SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
If you do not specify any of the optional keywords, all TrustSec SXP notifications are enabled.
The snmp-server enable traps snmp command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples The following example shows how to test the binding conflict MIB:
Router# test snmp trap trustsec-sxp binding-conflict
ctsxSxpBindingConflictNotif notification is disabled.
Router#
The following example shows how to test the binding err MIB:
Router# test snmp trap trustsec-sxp binding-err
ctsxSxpBindingErrNotif notification is disabled.
442
test snmp trap trustsec-sxp
Router#
443
upgrade hardware database
Syntax Description file file_name Specifies the name of a hardware database file.
preference Specifies the hardware dateabase boot file.
invalidate Specifies the hardware database region to invalidate.
region1 Specifies the hardware database region1.
region2 Specifies the hardware database region2.
slot_number Specifies the slot number of a module that has hardware abstraction layer (HAL)
support.
Defaults None
Usage Guidelines This command is useful only if a new hardware database version becomes available.
Examples This example shows how to upgrade the platform hardware database version:
Router# upgrade hardware database file bootdisk:file_name
Router#
*date_and_time: Hardware database upgrade in progress
*date_and_time: Erasing flash
*date_and_time: Programming flash
*date_and_time: Verifying new hardware database
*date_and_time: Hardware database upgrade complete
444
upgrade hardware image
Syntax Description slot Specifies the slot number of a module that has hardware abstraction layer (HAL)
slot_number support.
file file_name Specifies the name of a hardware image file.
preference Specifies the hardware dateabase boot file.
invalidate Specifies the hardware database region to invalidate.
region_number Specifies the number of a hardware image region.
reset Specfies the slot to reset.
Defaults None
Usage Guidelines This command is useful only if a new hardware image version becomes available.
This command is supported only on modules that have hardware abstraction layer (HAL) support.
Examples This example shows how to upgrade the platform hardware database version:
Router# upgrade hardware image slot 4 file bootdisk:file_name
!!! {...} !!!
Linecard must be reset. Please use "upgrade hardware image slot 4 reset" command to reset
linecard.
Router# upgrade hardware image slot 4 reset
Router#
*date_and_time: %OIR-6-SP_REMCARD: Card removed from slot 4, interfaces disabled
*date_and_time: %DIAG-6-RUN_COMPLETE: Module 4: Running Complete Diagnostics..4
*date_and_time: %DIAG-6-DIAG_OK: Module 4: Passed Online Diagnostics
Upgrade XML file complete
Upgrade image file complete
Please wait for automatic linecard reset to make upgrade taking effect
*date_and_time: %OIR-6-SP_INSCARD: Card inserted in slot 4, interfaces are now online
*date_and_time: %OIR-6-SP_REMCARD: Card removed from slot 4, interfaces disabled
*date_and_time: %DIAG-6-RUN_COMPLETE: Module 4: Running Complete Diagnostics...
*date_and_time: %DIAG-6-DIAG_OK: Module 4: Passed Online Diagnostics
*date_and_time: %OIR-6-SP_INSCARD: Card inserted in slot 4, interfaces are now online
445
upgrade hardware image
446
upgrade hardware transceiver xml
Syntax Description file file_name Specifies the name of a transceiver xml file.
preference Specifies the hardware dateabase boot file.
invalidate Specifies the hardware database region to invalidate.
region_number Specifies the number of a transceiver xml region.
Defaults None
Usage Guidelines This command is useful only if a new hardware transceiver xml version becomes available.
Examples This example shows how to upgrade the platform hardware database version:
Router# upgrade hardware transceiver xml file bootdisk:file_name
Transceiver XML is upgraded successfully
Please unplug and replug supported transceiver
Router#
447
upgrade hardware xml slot
Syntax Description slot_number Specifies the slot number of a module that has hardware abstraction layer (HAL)
support.
file file_name Specifies the name of a transceiver xml file.
preference Specifies the hardware dateabase boot file.
invalidate Specifies the hardware database region to invalidate.
region_number Specifies the number of a transceiver xml region.
reset Specfies the slot to reset.
Defaults None
Usage Guidelines This command is useful only if a new hardware xml version becomes available.
This command is supported only on modules that have hardware abstraction layer (HAL) support.
Examples This example shows how to upgrade the platform hardware xml version:
Router# upgrade hardware xml slot 4 file bootdisk:file_name
Linecard must be reset. Please use "upgrade hardware xml slot 4 reset" command to reset
linecard.
Router# upgrade hardware xml slot 4 reset
448
upgrade hardware xml slot
449
vlan access-log
vlan access-log
To configure the VLAN access control list (VACL)-logging properties, including the log-table size,
redirect-packet rate, and logging threshold, use the vlan access-log command in global configuration.
To return to the default settings, use the no form of this command.
Syntax Description maxflow Specifies the maximum log-table size. Valid values are from 0 to 2048;
max-number 0 deletes the contents of the log table.
ratelimit pps Specifies the maximum redirect VACL-logging packet rate; valid values are
from 0 to 5000.
threshold pkt-count Specifies the logging-update threshold; valid values are from 0 to 2147483647.
0 means that the threshold is not set.
Usage Guidelines Due to the rate-limiting function for redirected packets, VACL-logging counters may not be accurate.
Only denied IP packets are logged.
When the log-table size is full, the logging packets from the new flows are dropped by the software.
The packets that exceed the maximum redirect VACL-logging packet rate limit are dropped by the
hardware.
A logging message is displayed if the flow threshold is reached before the 5-minute interval.
450
vlan access-log
If you do not configure the maximum log-table size, maximum packet rate, or threshold, or if you enter
the no form of the commands, the default values are assumed.
Examples This example shows how to set the maximum log-table size:
Router(config)# vlan access-log maxflow 500
Router(config)#
This example shows how to set the maximum redirect VACL-logging packet rate after which packets are
dropped:
Router(config)# vlan access-log ratelimit 200
Router(config)#
451
vsl-encryption
vsl-encryption
To configure VSL encryption on the switch, use the vsl-encryption command in Virtual switch domain
mode, use the no form of the command to disable VSL encryption.
vsl-encryption
no vsl-encryption
Defaults None
Usage Guidelines You do not need to enable FIPs before you enable VSL encryption; however if you intend to use FIPs
you should enable VSL encryption first.
452
wrr-queue bandwidth
wrr-queue bandwidth
To allocate the bandwidth between the standard transmit queues, use the wrr-queue bandwidth
command in interface configuration mode. To return to the default settings, use the no form of this
command.
no wrr-queue bandwidth
Syntax Description weight-1 ... weight-n WRR weights; valid values are from 1 to 255.
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.
You can configure up to seven queue weights on Cisco 7600 series routers that are configured with a
Supervisor Engine 720.
You can configure up to three queue weights on Cisco 7600 series routers that are configured with a
Supervisor Engine 2.
WRR allows bandwidth sharing at the egress port. This command defines the bandwidths for egress
WRR through scheduling weights. Four queues participate in the WRR unless you enable the
egress-expedite queue. The expedite queue is a strict-priority queue that is used until it is empty before
using one of the WRR queues.
453
wrr-queue bandwidth
There is no order of dependencies for the wrr-queue bandwidth command. If you enable the egress
priority, the weight ratio is calculated with the first two and the last parameters; otherwise, all four
parameters are used.
The WRR weights are used to partition the bandwidth between the queues if all queues are nonempty.
For example, entering weights of 1:3 means that one queue gets 25 percent of the bandwidth and the
other queue gets 75 percent as long as both queues have data.
454
wrr-queue cos-map
wrr-queue cos-map
To map CoS values to drop thresholds for a queue, use the wrr-queue cos-map command in interface
configuration mode. To return to the default settings, use the no form of this command.
no wrr-queue cos-map
Syntax Description queue-id Queue number; the valid values are from 1 to 2.
threshold-id Threshold ID; valid values are from 1 to 2.
cos-1 ... cos-n CoS value; valid values are from 0 to 7.
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.
455
wrr-queue cos-map
Examples This example shows how to map the CoS values 0 and 1 to standard transmit queue 1/threshold 1:
Router(config-if)# wrr-queue cos-map 1 1 0 1
456
wrr-queue dscp-map
wrr-queue dscp-map
To map the hardware Differentiated Services Code Point (DSCP) values to the drop threshold values for
a queue, use the wrr-queue dscp-map command in interface configuration mode. To return to the default
settings, use the no form of this command.
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.
Note To enter the wrr-queue dscp-map command, the interface must be in DSCP-queuing mode. Use the mls
qos queue-mode mode-dscp command to set the mode to DSCP.
Examples This example shows how to map the hardware DSCP values to the drop threshold values for a queue:
wrr-queue dscp-map 8 1 0 1 2 3
457
wrr-queue dscp-map
458
wrr-queue queue-limit
wrr-queue queue-limit
To set the transmit-queue size ratio on an interface, use the wrr-queue queue-limit command in
interface configuration mode. To return to the default settings, use the no form of this command.
no wrr-queue queue-limit
Syntax Description queue1-weight Ratio of the low-priority queue weight; valid values are from 1 and
100 percent.
queue2-weight (Optional) Ratio of the medium-priority queue weight; valid values are
from 1 and 100 percent.
queue3-weight Ratio of the high-priority queue weight; see the “Usage Guidelines”
section for valid values.
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 high-priority weight values are from 1 to 100 percent, except on 1p2q1t egress LAN ports, where
valid values for the high-priority queue are from 5 to 100 percent.
On 1p2q2t interfaces, QoS sets the strict-priority queue size equal to the high-priority queue size.
Estimate the mix of low priority-to-high priority traffic on your network (for example, 80 percent
low-priority traffic and 20 percent high-priority traffic). Use the estimated percentages as queue weights.
459
wrr-queue queue-limit
Due to the granularity of programming the hardware, the values that are set in the hardware are close
approximations of the provided values. For example, if you specify 0 percent, the actual value that is
programmed is not necessarily 0.
Examples This example shows how to configure the transmit-queue size ratio:
Router(config-if)# wrr-queue queue-limit 75 25
460
wrr-queue random-detect
wrr-queue random-detect
To enable WRED or specify the minimum and maximum WRED threshold for the specified queues on
1p2q2t and 1p3q1t interfaces, use the wrr-queue random-detect command in interface configuration
mode. To return to the default settings, use the no form of this command.
Defaults The default is that WRED is disabled. When WRED is enabled, the defaults are as follows:
• The maximum threshold is (low) 40 percent and (high) 100 percent.
• The minimum thresholds are both set to zero.
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.
1p2q1t and 1p3q1t interfaces have WRED-drop thresholds in their standard transmit queues. You can
configure 1p3q1t transmit queues to use a WRED-drop threshold or a tail-drop threshold.
461
wrr-queue random-detect
To enable WRED-drop thresholds on 1p2p1t interfaces, enter the wrr-queue random-detect queue-id
command. Use the no form of this command to disable WRED.
To enable WRED-drop thresholds on 1p3q1t interfaces, enter the wrr-queue random-detect queue-id
command. To return to the tail-drop threshold, enter the no wrr-queue random-detect queue-id
command.
The queue-id argument is 1 for the standard low-priority queue, 2 for the standard high-priority queue,
and 3 for strict priority.
The threshold in the strict-priority queue is not configurable.
Each queue on a 1p2q2t interface has two thresholds; 1p3q1t interfaces have one threshold.
Each threshold has a low and a high WRED value.
WRED values are a percentage of the queue capacity.
For additional information on configuring WRED thresholds, refer to the QoS chapter in the Cisco 7600
Series Router Cisco IOS Software Configuration Guide.
Examples This example shows how to configure the low-priority transmit-queue high-WRED drop thresholds:
Router(config-if)# wrr-queue random-detect max-threshold 1 60 100
462
wrr-queue threshold
wrr-queue threshold
To configure the drop-threshold percentages for the standard receive and transmit queues on 1q4t and
2q2t interfaces, use the wrr-queue threshold command in interface configuration mode. To return to the
default settings, use the no form of this command.
Defaults When you enable QoS, the default values are as follows:
• 100 percent for threshold 1
• 60 percent for threshold 2
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.
463
wrr-queue threshold
Examples This example shows how to configure receive queue 1/threshold 1 and transmit queue 1/threshold 1:
Router(config-if)# wrr-queue threshold 1 60 100
464