Cisco IOS IP Switching Command Reference
Cisco IOS IP Switching Command Reference
Reference
March 2011
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Introduction ISW-1
ip cache-invalidate-delay ISW-42
ip cef ISW-44
ip load-sharing ISW-64
ip route-cache ISW-66
This document describes the commands used to configure IP switching features such as Cisco Express
Forwarding, Distributed Cisco Express Forwarding, and Fast Switching in Cisco IOS software.
Note Prior to Cisco IOS Release 12.3(14)T, the commands for configuring IP switching features were
presented in the Cisco IOS Switching Services Command Reference.
cef table consistency-check {ipv4 | ipv6} [type {lc-detect | scan-lc-rp | scan-rp-lc | scan-rib-ios
| scan-ios-rib} [count count-number [period seconds] | period seconds] | error-message |
auto-repair [delay seconds [holddown seconds] | holddown seconds] | data-checking]
count count-number (Optional) Specifies the maximum number of prefixes to check per scan. The
range is from 2 to 10000. The default count number is 1000 prefixes per scan
for the scan-rib-ios and scan-ios-rib keywords. The default count number
is 0 for the lc-detect, scan-lc-rp, and scan-rp-lc keywords.
period seconds (Optional) Period between scans. Valid values are from 30 to 3600 seconds.
The default is 60 seconds.
error-message (Optional) Enables the consistency checker to generate an error message
when it detects an inconsistency. By default, this function is disabled.
auto-repair (Optional) Enables the auto repair function. By default, this function is
enabled. You can enter the no form of the command to disable auto repair or
enter the default form of the command to return the auto repair settings to a
10-second delay and 300-second holddown.
delay seconds (Optional) Specifies how long the consistency checker waits to fix an
inconsistency. The range is 10 to 300 seconds. The default delay is
10 seconds.
holddown seconds (Optional) Specifies how long the consistency checker waits to reenable auto
repair after auto repair runs. The range is from 300 to 3000 seconds. The
default delay is 300 seconds.
data-checking (Optional) Enables the consistency checker data-checking utility. By
default, this function is disabled.
Examples The following example enables the Cisco Express Forwarding consistency checker to check IPv4
addresses:
Router(config)# cef table consistency-check ipv4
The following example enables the Cisco Express Forwarding consistency checker to check IPv4
addresses and specifies the scan-rp-lc checker to run every 60 seconds for 5000 prefixes:
Router(config)# cef table consistency-check ipv4 type scan-rp-lc count 5000 period 60
The following example enables the Cisco Express Forwarding consistency checker to check IPv4
addresses and display an error message when it finds an inconsistency:
Router(config)# cef table consistency-check ipv4 error-message
Syntax Description catch-all Any route not matched, which include Internet routes. The default priority
is 4.
connected-route Route directly connected to the router. The default priority is 2.
default-route Default route, 0.0.0.0/0 or ::/0. The default priority is 1.
receive-route Receive route, local address on router. The default priority is 2.
recursive-dependents Route with recursive dependents, matches next-hop of other recursive
routes. The default priority is 1.
route-in-vrf Route in a Virtual Private Network (VPN) routing and forwarding (VRF)
table. The default priority is 3.
priority Sets the table download priority.
priority-number Select one of the following as the priority number:
11st priority
22nd priority
33rd priority
44th priority
Command Default The default download characteristics apply to routes and prefixes downloaded from the Route Processor
(RP) to the line cards.
Usage Guidelines Use this command to change the priority of how prefixes and routes in the Cisco Express Forwarding
table are downloaded from the RP to the line cards.
Default download priorities are set up to improve convergence when topology changes occur in
networks of distributed platform, such as the Cisco 7600 series routers and the Cisco Catalyst 6000
series switches.
Prefixes and routes are categorized and downloaded at four different priorities. Table 1 lists the
download priority and the associated prefix or route type.
In a typical network, a small number of IGP prefixes have many iBGP prefixes recursing through them.
When an IGP topology change occurs, the key to updating the forwarding of the iBGP prefixes is to
update the IGP prefix through which they recurse. If these prefixes with recursing dependents are
downloaded before other prefixes, convergence will be faster. Therefore, the default priority for routes
with recursive dependents is P1.
Prioritizing the download of directly connected prefixes and their associated local interface address
allows for faster and more deterministic failure detection when an interface goes down. In addition,
traffic is received at the local interface addresses as soon as possible, which allows for faster Layer 3
protocol convergence. The default priority for directly connected and receive routes is set at P2.
VRF routes over global table routes or Internet routes have a default priority of P3, and all other routes
are prioritized at P4.
The cef table download command allows you to override a default priority so you can customize prefix
and route downloads from the RP to the line cards. To display the configured download priority, use the
show cef table download priority command.
Examples The following example shows how to change the download priority of the default route from P1 to P2:
Router(config)# cef table download default-route priority 2
General Characteristics
Individual Overrides
Syntax Description convergence-speed Configures a faster convergence speed for table output chain building.
memory-utilization Configures less memory use for table output chain building.
default Removes any table output chain building characteristic.
indirection Enables insertion of indirection objects for table output chain building.
non-recursive-prefix (Optional) Enables insertion of indirection objects for nonrecursive prefixes.
recursive-prefix (Optional) Enables insertion of indirection objects for recursive prefixes.
inplace-modify Enables in-place modification of objects in the forwarding chain.
load-sharing (Optional) Enables in-place modification of load-balancing objects in the
forwarding chain.
push-counter (Optional) Enables in-place modification of packet counters in the output
chain.
Command Default Convergence speed and indirection characteristics are enabled by default for the building of
Cisco Express Forwarding table output chains.
Individual Overrides
This command is used for troubleshooting purposes only.
Note Use this command only on the advice of field personnel from Cisco.
The use of the cef table output-chain build command with either the indirection or inplace-modify
keyword overrides specific Cisco Express Forwarding table output chain-building behavior. Indirection
characteristics are installed by default if the platform supports or permits their use.
The indirection keyword enables or disables the insertion of indirection objects for recursive or
nonrecursive prefixes or for both recursive and nonrecursive prefixes. Inserting an indirection object
into the forwarding chain allows the handling of any aggregate event that affects multiple prefixes by
the modification of the indirection object. For example, if a number of recursive prefixes all share the
same recursive nexthop, and the route to the recursive nexthop changes, a single update to an indirection
object can restore forwarding for those recursive prefixes.
If you configure the cef table output-chain build indirection command without a prefix type, recursive
and nonrecursive prefixes are explicitly enabled. This command would override any preference
configured with the existing cef table output-chain build favor command.
The inplace-modify keyword enables or disables the ability to modify certain objects in the forwarding
chain by modifying the data that an object holds. The alternative is a complete replacement of the object
and the relinking of all links to the object.
To return to system default settings for Cisco Express Forwarding table output chain building, use the
default form of the command.
The output of the show cef table command displays the current configuration and operational state of
the Cisco Express Forwarding table.
Examples The following example shows how to configure the use of less memory for table output chain building:
Router(config)# cef table output-chain build favor memory
Use this command if your priority is to save memory and your network does not require a faster
convergence speed for table output chain building for forwarding of network traffic.
Syntax Description minutes The time period, in minutes, over which to calculate the rate of route updates
to Cisco Express Forwarding tables. The range is from 1 to 60. The
default is 5.
Command Default If the command is not configured, the sampling rate is every 5 minutes.
Usage Guidelines Use this command to change the sampling rate period over which to monitor route updates from the RIB
to the Cisco Express Forwarding IPv4 and IPv6 FIB tables. Changing the sampling period allows you to
calculate the rate of route insertion into the FIB at any interval length from 1 minute to 60 minutes.
Examples The following example shows how to set the time period to 1 minute over which to calculate the rate of
route updates from the RIB to the IPv4 FIB and IPv6 FIB:
Router(config)# cef table rate-monitor-period 1
clear adjacency
To clear the Cisco Express Forwarding adjacency table, use the clear adjacency command in privileged
EXEC mode.
clear adjacency
Usage Guidelines Using the clear adjacency command repopulates adjacencies from sources. Any remaining stale
adjacencies (meaning those that fail to repopulate on request) are then purged. Layer 2 next hop
information is reevaluated.
Clearing adjacencies cause the adjacency table to repopulate from the Layer 2 to Layer 3 mapping tables.
To reevaluate the mappings, clear the source information by using a Cisco IOS command, such as the
clear arp-cache command.
To begin a new epoch and increment the epoch number of the Cisco Express Forwarding adjacency table,
use the clear adjacency epoch command in privileged EXEC mode.
Usage Guidelines The clear adjacency epoch command increments the epoch and flushes entries with the old epoch. This
command clears inconsistencies.
Use the clear adjacency epoch command when you want to rebuild the adjacency table. A new
adjacency table might be required because the user wants to remove inconsistencies from the table.
Examples The following example shows how to begin a new epoch and increments the epoch number of the
adjacency table:
Router# clear adjacency epoch
Syntax Description interface-type Type of interface to clear the policy statistics for
interface-number Port, connector, or interface card number
policy-statistics Policy statistics for the specified interface.
Usage Guidelines This command clears the Cisco Express Forwarding Border Gateway Protocol (BGP) traffic policy
statistics counters for an interface.
If you do not specify an interface type and interface number the policy statistics for all interfaces are
cleared.
Examples The following example clears the Cisco Express Forwarding BGP traffic policy statistics counters:
Router# clear cef interface ethernet 0/0 policy-statistics
Router#
Syntax Description slot-number (Optional) Line card slot number to clear. When you omit this argument,
all line card slots are cleared.
adjacency (Optional) Clears line card adjacency tables and rebuilds adjacency for the
specified line card.
interface (Optional) Clears line card interface information and recreates the interface
information for the specified line card.
prefix (Optional) Clears line card prefix tables and starts rebuilding the
Forwarding Information Base (FIB) table.
Usage Guidelines This command is available only on distributed platforms (such as the Cisco 7500 series) running
distributed Cisco Express Forwarding.
Cisco Express Forwarding information on the line cards is cleared; however, Cisco Express Forwarding
information on the Route Processor (RP) is not affected.
After you clear Cisco Express Forwarding information from line cards, the corresponding information
from the RSP is propagated to the line cards. Interprocess communications (IPC) ensures that
Cisco Express Forwarding information on the Route Switch Processor (RSP) matches the Cisco Express
Forwarding information on the line cards.
Because this command might require significant processing resources and can cause dropped traffic or
system error messages about excessive CPU use, its use is recommended only as a last resort for
debugging or mitigating serious problems.
Note Cisco 10000 series routers do not support the clear cef linecard command.
Examples The following example clears the Cisco Express Forwarding information from the line cards:
clear cef linecard
Command Default Cisco Express Forwarding load balancing information is not cleared.
Usage Guidelines Cisco Express Forwarding load balancing is based on a combination of source and destination packet
information; it allows you to optimize resources by distributing traffic over multiple paths for transferring
data to a destination. You can use the clear cef load-balance statistics command to clear Cisco Express
Forwarding load balancing information. To select and configure the load balancing algorithm and to record
the statistics, use the ip cef load-sharing algorithm command.
Examples The following example shows how to clear CEF load balancing information:
Router# clear cef load-balance statistics
Syntax Description ipv4 Clears the Cisco Express Forwarding tables for IPv4 addresses.
ipv6 Clears the Cisco Express Forwarding tables for IPv6 addresses.
Note On the Cisco 10000 series routers IPv6 is supported on Cisco IOS
Release 12.2(28)SB and later releases.
vrf (Optional) Specifies all VPN routing and forwarding (VRF) instance tables or a specific
VRF table for an IPv4 or IPv6 address.
vrf-name (Optional) Clears the specific VRF table for IPv4 or IPv6 addresses.
* (Optional) Clears all the VRF tables for IPv4 or IPv6 addresses.
Usage Guidelines The clear cef table command clears the selected table or address family of tables (for IPv4 or IPv6) and
updates (refreshes) them throughout the router (including the Route Processor and line cards). The
command increments the table epoch, updates the tables, distributes the updated information to the line
cards, and performs a distributed purge of any stale entries in the tables based on the noncurrent epoch
number. This ensures that any inconsistencies that occurred over time are removed.
Because this command might require significant processing resources and can cause dropped traffic or
system error messages about excessive CPU use, its use is recommended only as a last resort for
debugging or mitigating serious problems.
Cisco Express Forwarding tables are also cleared automatically during bootup or online insertion and
removal (OIR) of line cards.
Note On the Cisco 10000 series routers, IPv6 is supported on Cisco IOS Release 12.2(28)SB or later
releases.
Examples The following example clears the Cisco Express Forwarding tables for the IPv6 address family:
Router# clear cef table ipv6 vrf *
The following example clears the Cisco Express Forwarding tables for a VRF table named vrf1 in the
IPv4 address family:
Router# clear cef table ipv4 vrf vrf1
The following example clears the Cisco Express Forwarding tables for all VRF tables in the IPv4 address
family. This example shows output with Cisco Express Forwarding table debugging enabled:
Router# clear cef table ipv4 vrf *
clear ip cache
To delete entries in the routing table cache used to fast switch IP traffic, use the clear ip cache command
in privileged EXEC mode.
Syntax Description prefix mask (Optional) Deletes only the entries in the cache that match the prefix and
mask combination.
Usage Guidelines Use this command to clear routes from the routing table cache. You can remove all entries in the routing
cache or you can remove only those entries associated with a specified prefix and mask.
Note IPv4 fast switching is not supported in Cisco IOS 12.4(20)T and later releases.
Examples The following command shows how to delete the all of the entries in the routing table cache:
Router# clear ip cache
The following command show how to delete entries in the router table associated with the prefix and
mask 192.168.32.0 255.255.255.0:
Router# clear ip cache 192.168.32.0 255.255.255.0
To begin a new epoch and increment the epoch number for one or all Cisco Express Forwarding tables,
use the clear ip cef epoch command in privileged EXEC mode.
Syntax Description all-vrfs (Optional) Begins a new epoch for all Forwarding Information Base (FIB)
tables.
full (Optional) Begins a new epoch for all tables, including adjacency tables.
vrf (Optional) Begins a new epoch for the specified FIB table.
table (Optional) Virtual Private Network (VPN) routing and forwarding (VRF)
instance name.
Usage Guidelines Use the clear ip cef epoch command when you want to rebuild a table. This command increments the
epoch number and flushes entries with the old epoch number. This command clears any inconsistencies
that might exist, so if everything in the system is working correctly, this command does not affect the
Cisco Express Forwarding forwarding tables other than changing the current epoch values.
Examples The following example shows the output before and after you clear the epoch table and increment the
epoch number:
Router# show ip cef epoch
Table: Default-table
Table epoch: 2 (43 entries at this epoch)
Adjacency table
Table epoch: 2 (5 entries at this epoch)
Adjacency table
Table epoch: 3 (5 entries at this epoch)
Usage Guidelines Use the clear ip cef epoch full command when you want to rebuild a table. This command allows old
and new table entries to be distinguished within the same data structure and allows you to retain the old
Cisco Express Forwarding database table while constructing the new table.
These show commands display epoch information:
show ip cef summaryDisplays the table epoch for a specific Forwarding Information Base (FIB)
table.
show ip cef detailDisplays the epoch value for each entry of a specific FIB table.
show adjacency summaryDisplays the adjacency table epoch.
show adjacency detailDisplays the epoch value for each entry of the adjacency table.
Examples This example shows the output before and after you clear the epoch table and increment the epoch
number:
Router# show ip cef epoch
Table:Default-table
Table epoch:2 (164 entries at this epoch)
Adjacency table
Table epoch:1 (33 entries at this epoch)
Table:Default-table
Table epoch:3 (164 entries at this epoch)
Adjacency table
Table epoch:2 (33 entries at this epoch)
To clear the Cisco Express Forwarding event-log buffer, use the clear ip cef event-log command in
privileged EXEC mode.
Usage Guidelines This command clears the entire Cisco Express Forwarding table event log that holds Forwarding
Information Base (FIB) and adjacency events.
Examples The following example shows how to clear the Cisco Express Forwarding event-log buffer:
Router# clear ip cef event-log
Usage Guidelines This command clears the Cisco Express Forwarding inconsistency checker statistics and records that
accumulate when the cef table consistency-check command is enabled.
Examples The following example shows how to clear all Cisco Express Forwarding inconsistency checker
statistics and records:
Router# clear ip cef inconsistency
Syntax Description network Forwarding Information Base (FIB) entry specified by network.
mask (Optional) FIB entry specified by network and mask.
Usage Guidelines When the clear statistics flag is set, statistics are cleared as the FIB table is scanned. The time period is
up to 60 seconds for all statistics to clear. However, clearing a specific prefix is completed immediately.
Examples The following example shows how to reset the packet and byte counts to zero for Cisco Express
Forwarding entries on the 172.17.10.10 network:
Router# clear ip cef 172.17.10.10 prefix-statistics
clear ip mds
To clear multicast distributed switching (MDS) information from the router, use the clear ip mds
command in privileged EXEC mode.
Examples The following example clears all line card routes in an MFIB table on a Cisco 12000 series Internet
router:
Router# attach 1
LC-Slot1> enable
LC-Slot1# clear ip mds forwarding
The following example clears all line card routes in an MFIB table on a Cisco 7500 series router:
Syntax Description linecard-slot-number Slot number containing the line card to be reset.
* Indicates that the reset should be executed on all line cards.
Usage Guidelines When the * keyword is specified instead of the linecard-slot-number argument, all MDS information on
all line cards is cleared and reset.
Examples The following example clears and resets all MDS line card information on the router:
Router# clear ip mds linecard *
clear ip traffic
To clear the global or system-wide IP traffic statistics for one or more interfaces, use the clear ip traffic
command in privileged EXEC mode.
Syntax Description interface type number (Optional) Clears the global or system-wide IP traffic statistics for a specific
interface. If the interface keyword is used, the type and number arguments
are required.
Command Default Using the clear ip traffic command with no keywords or arguments clears the global or system-wide IP
traffic statistics for all interfaces.
Usage Guidelines Using the clear ip traffic command with the optional interface keyword clears the ipIfStatsTable
counters displayed for the specified interface and also clears the counters displayed by the show ip
traffic interface command.
Examples The following example clears the global or system-wide IP traffic statistics on all interfaces:
Router# clear ip traffic
The following example shows how to clear the IP traffic statistics on Ethernet interface 0/0:
Router# clear ip traffic interface ethernet 0/0
The following is sample output from the show ip traffic command for Ethernet interface 0/0 after
clearing the traffic using the clear ip traffic command:
Router# show ip traffic
Examples This example shows how to clear all information about the per-prefix accounting statistics:
Router# clear mls cef ip accounting per-prefix all
clear pxf
To clear Parallel eXpress Forwarding (PXF) counters and statistics, use the clear pxf command in
privileged EXEC mode.
clear pxf [dma counters | interface interface | statistics {context | diversion | drop | ip | ipv6} |
xcm counters]
Syntax Description dma counters (Optional) Clears the direct memory access (DMA) PXF counters.
interface interface (Optional) Clears the PXF counters on the specified interface.
statistics (Optional) Type of PXF statistics to clear. The options are:
contextCurrent and historical loads on the PXF.
diversionTraffic diverted from the PXF.
dropDropped packets and bytes.
ip IP and ICMP statistics.
ipv6IPv6 statistics.
xcm counters Clears the PXF Error Code Correction (ECC) counters.
Usage Guidelines If no interface is specified, the command clears PXF counters on all interfaces. The clear pxf command
clears counters associated with the show pxf dma, show pxf interface, show pxf statistics, and show
pxf xcm commands.
Examples The following example clears PXF statistics for serial interface 1/0/0:
Router# clear pxf interface serial 1/0/0
ip cache-invalidate-delay
To control the invalidation rate of the IP route cache, use the ip cache-invalidate-delay command in
global configuration mode. To allow the IP route cache to be immediately invalidated, use the no form
of this command.
no ip cache-invalidate-delay
Syntax Description minimum (Optional) Minimum time (in seconds) between invalidation request and
actual invalidation. The default is 2 seconds.
maximum (Optional) Maximum time (in seconds) between invalidation request and
actual invalidation. The default is 5 seconds.
quiet (Optional) Length of quiet period (in seconds) before invalidation. The
default is 3 seconds with no more than zero invalidation requests.
threshold (Optional) Maximum number of invalidation requests considered to be quiet.
Command Default The invalidation rate of the IP route cache is not controlled.
Usage Guidelines After you enter the ip cache-invalidate-delay command all cache invalidation requests are honored
immediately.
Caution This command should only be used under the guidance of technical support personnel. Incorrect settings
can seriously degrade network performance. The command-line-interface (CLI) will not allow you to
enter the ip cache-invalidate-delay command until you configure the service internal command in
global configuration mode.
The IP fast-switching and autonomous-switching features maintain a cache of IP routes for rapid access.
When a packet is to be forwarded and the corresponding route is not present in the cache, the packet is
process switched and a new cache entry is built. However, when routing table changes occur (such as
when a link or an interface goes down), the route cache must be flushed so that it can be rebuilt with
up-to-date routing information.
This command controls how the route cache is flushed. The intent is to delay invalidation of the cache
until after routing has settled down. Because route table changes tend to be clustered in a short period
of time, and the cache may be flushed repeatedly, a high CPU load might be placed on the router.
When this feature is enabled, and the system requests that the route cache be flushed, the request is held
for at least minimum seconds. Then the system determines whether the cache has been quiet (that is,
less than threshold invalidation requests in the last quiet seconds). If the cache has been quiet, the cache
is then flushed. If the cache does not become quiet within maximum seconds after the first request, it is
flushed unconditionally.
Manipulation of these parameters trades off CPU utilization versus route convergence time. Timing of
the routing protocols is not affected, but removal of stale cache entries is affected.
Examples The following example shows how to set a minimum delay of 5 seconds, a maximum delay of 30
seconds, and a quiet threshold of no more than 5 invalidation requests in the previous 10 seconds:
Router(config)# service internal
Router(config)# ip cache-invalidate-delay 5 30 10 5
ip cef
To enable Cisco Express Forwarding on the route processor card, use the ip cef command in global
configuration mode. To disable Cisco Express Forwarding, use the no form of this command.
Cisco IAD2420 Series Routers, Cisco 2600 Series Routers, Cisco 3600 Series Routers, Cisco 3700 Series Routers,
Cisco 7200 Series Routers
ip cef [distributed]
no ip cef [distributed]
ip cef distributed
no ip cef distributed
Syntax Description distributed (Optional) Enables distributed Cisco Express Forwarding operation.
Distributes Cisco Express Forwarding information to line cards. Line cards
perform express forwarding.
Command Default Cisco Express Forwarding is enabled by default on most platforms. To find out if Cisco Express
Forwarding is enabled by default on your platform, enter the show ip cef command.
Usage Guidelines The ip cef command is not available on the Cisco 12000 series because that router series operates only
in distributed Cisco Express Forwarding mode. Distributed Cisco Express Forwarding is enabled also
on the Cisco 6500 series router.
Cisco Express Forwarding is advanced Layer 3 IP switching technology. Cisco Express Forwarding
optimizes network performance and scalability for networks with dynamic, topologically dispersed
traffic patterns, such as those associated with web-based applications and interactive sessions.
If you enable Cisco Express Forwarding and then create an access list that uses the log keyword, the
packets that match the access list are not Cisco Express Forwarding switched. They are fast switched.
Logging disables Cisco Express Forwarding.
The following example shows how to enable standard Cisco Express Forwarding operation:
Router(config)# ip cef
The following example shows how to enable distributed Cisco Express Forwarding operation:
Router(config)# ip cef distributed
ip cef accounting
To enable Cisco Express Forwarding network accounting, use the ip cef accounting command in global
configuration mode or interface configuration mode. To disable network accounting of Cisco Express
Forwarding, use the no form of this command.
Specific Cisco Express Forwarding Accounting Information Through Interface Configuration Mode
Syntax Description accounting-types The accounting-types argument must be replaced with at least one of
the following keywords. Optionally, you can follow this keyword by
any or all of the other keywords, but you can use each keyword only
once.
load-balance-hashEnables load balancing hash bucket
counters.
non-recursiveEnables accounting through nonrecursive
prefixes.
per-prefixEnables express forwarding of the collection of the
number of packets and bytes to a destination (or prefix).
prefix-lengthEnables accounting through prefix length.
non-recursive Enables accounting through nonrecursive prefixes.
This keyword is optional when used in global configuration mode
after another keyword is entered. See the accounting-types argument.
external Counts input traffic in the nonrecursive external bin.
internal Counts input traffic in the nonrecursive internal bin.
Release Modification
12.2(2)T The ip cef accounting non-recursive command in interface configuration
mode was added.
12.2(25)S The load-balance-hash keyword was added.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines Collecting statistics can help you better understand Cisco Express Forwarding patterns in your network.
When you enable network accounting for Cisco Express Forwarding from global configuration mode,
accounting information is collected at the Route Processor (RP) when Cisco Express Forwarding mode
is enabled and at the line cards when distributed Cisco Express Forwarding mode is enabled. You can
then display the collected accounting information using the show ip cef privileged EXEC command.
For prefixes with directly connected next hops, the non-recursive keyword enables express forwarding
of the collection of packets and bytes through a prefix. This keyword is optional when this command is
used in global configuration mode.
This command in interface configuration mode must be used in conjunction with the global
configuration command. The interface configuration command allows a user to specify two different
bins (internal or external) for the accumulation of statistics. The internal bin is used by default. The
statistics are displayed through the show ip cef detail command.
Per-destination load balancing uses a series of 16 hash buckets into which the set of available paths are
distributed. A hash function operating on certain properties of the packet is applied to select a bucket
that contains a path to use. The source and destination IP addresses are the properties used to select the
bucket for per-destination load balancing. Use the load-balance-hash keyword with the ip cef
accounting command to enable per-hash-bucket counters. Enter the show ip cef prefix internal
command to display the per-hash-bucket counters.
Examples The following example shows how to enable the collection of Cisco Express Forwarding accounting
information for prefixes directly connected to the next hops:
Router(config)# ip cef accounting non-recursive
Syntax Description kbps Kilobytes of line card memory allocated. Range is 0 to 12800. The default
IPC memory allocation is 25 messages. However, this value depends on the
switching platform.
Command Default If you do not configure a line card memory pool for the Cisco Express Forwarding queuing messages,
the default is the IPC memory allocation for the switching platform.
Examples The following example shows how to configure the Cisco Express Forwarding line card memory queue
to 128000 kilobytes per second:
Router(config)# ip cef linecard ipc memory 128000
ip cef load-sharing algorithm {original | tunnel [id] | universal [id] | include-ports {source [id]
| [destination] [id] | source [id] destination [id]}}
Syntax Description original Sets the load-balancing algorithm to the original algorithm based on a
source and destination hash.
tunnel Sets the load-balancing algorithm for use in tunnel environments or in
environments where there are only a few IP source and destination
address pairs.
id (Optional) Fixed identifier.
universal Sets the load-balancing algorithm to the universal algorithm that uses
a source and destination and an ID hash.
include-ports source Sets the load-balancing algorithm to the include-ports algorithm that
uses a Layer 4 source port.
include-ports destination Sets the load-balancing algorithm to the include-ports algorithm that
uses a Layer 4 destination port.
include-ports source Sets the load balancing algorithm to the include-ports algorithm that
destination uses Layer 4 source and destination ports.
Command Default The universal load-balancing algorithm is selected. If you do not configure the fixed identifier for a
load-balancing algorithm, the router automatically generates a unique ID.
Usage Guidelines The original Cisco Express Forwarding load-balancing algorithm produced distortions in load sharing
across multiple routers because of the use of the same algorithm on every router. When the
load-balancing algorithm is set to universal mode, each router on the network can make a different load
sharing decision for each source-destination address pair, and that resolves load-balancing distortions.
The tunnel algorithm is designed to share the load more fairly when only a few source-destination pairs
are involved.
The include-ports algorithm allows you to use the Layer 4 source and destination ports as part of the
load-balancing decision. This method benefits traffic streams running over equal-cost paths that are not
loadshared because the majority of the traffic is between peer addresses that use different port numbers,
such as Real-Time Protocol (RTP) streams. The include-ports algorithm is available in Cisco IOS
Release 12.4(11)T and later releases.
Examples The following example shows how to enable the Cisco Express Forwarding load-balancing algorithm
for tunnel environments:
configure terminal
!
ip cef load-sharing algorithm tunnel
exit
Command Default If this command is not configured, Cisco Express Forwarding does not optimize the address resolution
of directly connected neighbors for IPv4.
Usage Guidelines The ip cef optimize neighbor resolution command is very similar to the ipv6 cef optimize neighbor
resolution command, except that it is IPv4-specific.
Use this command to trigger Layer 2 address resolution of neighbors directly from Cisco Express
Forwarding for IPv4.
Examples The following example shows how to optimize address resolution from Cisco Express Forwarding for
directly connected neighbors:
Router(config)# ip cef optimize neighbor resolution
Syntax Description override (Optional) Enables Cisco Express Forwarding adjacency prefixes to override
static host glean routes.
validate (Optional) Enables the periodic validation of Cisco Express Forwarding
adjacency prefixes.
Defaults All Cisco Express Forwarding adjacency prefix management is disabled by default.
Usage Guidelines When Cisco Express Forwarding is configured, the forwarding information base (FIB) table may
conflict with static host routes that are specified in terms of an output interface or created by a Layer 2
address resolution protocols such as Address Resolution Protocol (ARP), map lists, and so on.
The Layer 2 address resolution protocol adds adjacencies to Cisco Express Forwarding, which in turn
creates a corresponding host route entry in the FIB table. This entry is called an adjacency prefix.
override
If the Cisco Express Forwarding adjacency prefix entries are also configured by a static host route, a
conflict occurs.
This command ensures that adjacency prefixes can override static host glean routes, and correctly restore
routes when the adjacency prefix is deleted.
validate
When you add a /31 netmask route, the new netmask does not overwrite an existing /32 Cisco Express
Forwarding entry. This problem is resolved by configuring the validate keyword to periodically validate
prefixes derived from adjacencies in the FIB against prefixes originating from the RIB.
Examples override
The following example shows how to enable Cisco Express Forwarding table adjacency prefix override:
Router(config)# ip cef table adjacency-prefix override
validate
The following example shows how to enable Cisco Express Forwarding table adjacency prefix
validation:
Router(config)# ip cef table adjacency-prefix validate
To enable consistency checker types and parameters for Cisco Express Forwarding tables, use the ip cef
table consistency-check command in global configuration mode. To disable consistency checkers, use
the no form of this command.
Syntax Description type (Optional) Specifies the type of consistency check to configure.
lc-detect (Optional) Specifies that the line card or the module detects a missing prefix.
On the line card, a missing prefix is confirmed by Route Processor (RP).
scan-lc (Optional) Specifies a passive scan check of tables on the line card or
module.
scan-rib (Optional) Specifies a passive scan check of tables on the RP against the
Routing Information Base (RIB). For the Cisco 7600 series router, the
scan-rib keyword specifies a passive scan check of tables on the rendezvous
point against the RIB.
scan-rp (Optional) Specifies a passive scan check of tables on the RP or on the
rendezvous point for the Cisco 7600 series router.
count count-number (Optional) Specifies the maximum number of prefixes to check per scan.
Valid values are from 1 to 225.
period seconds (Optional) Specifies the period of time between scans. Valid values are from
30 to 3600 seconds.
settle-time seconds (Optional) Specifies the amount of time that elapsed during which updates
for a candidate prefix are ignored as inconsistencies. Valid values are from
1 to 3600 seconds. This keyword is used during route updates.
Usage Guidelines This command configures Cisco Express Forwarding table consistency checkers and parameters for the
detection mechanism types that are listed in Table 2.
Examples The following example shows how to enable the Cisco Express Forwarding consistency checkers:
Router(config)# ip cef table consistency-check
To control Cisco Express Forwarding table event-log characteristics, use the ip cef table event-log
command in global configuration mode.
ip cef table event-log [size event-number] [vrf vrf-name] [match ip-prefix mask]
no ip cef table event-log [size event-number] [vrf vrf-name] [match ip-prefix mask]
Syntax Description size event-number (Optional) Number of event entries. The range is from 1 to 4294967295. The
default is 10000.
match (Optional) Log events matching specified prefix and mask.
ip-prefix (Optional) IP prefixes matched, in dotted decimal format (A.B.C.D).
mask (Optional) Network mask written as A.B.C.D.
vrf vrf-name (Optional) Virtual Private Network (VPN) routing and forwarding instance
(VRF) Cisco Express Forwarding table and VRF name.
Release Modification
12.2(33)SXH This command was removed. It is not available in Cisco IOS
Release 12.2(33)SXH and later Cisco IOS 12.2SX releases.
12.4(20)T This command was removed. It is not available in Cisco IOS
Release 12.4(20)T and later Cisco IOS 12.4T releases.
Usage Guidelines This command is used to troubleshoot inconsistencies that occur in the Cisco Express Forwarding event
log between the routes in the Routing Information Base (RIB), Route Processor (RP) Cisco Express
Forwarding tables, and line card Cisco Express Forwarding tables.
The Cisco Express Forwarding event log collects Cisco Express Forwarding events as they occur
without debugging enabled. This process allows the tracing of an event immediately after it occurs.
Cisco technical personnel may ask for information from this event log to aid in resolving problems with
the Cisco Express Forwarding feature.
When the Cisco Express Forwarding table event log has reached its capacity, the oldest event is written
over by the newest event until the event log size is reset using this command or cleared using the clear
ip cef event-log command.
Examples The following example shows how to set the Cisco Express Forwarding table event log size to 5000
entries:
Router(config)# ip cef table event-log size 5000
To change the Cisco Express Forwarding background resolution timer, use the ip cef table
resolution-timer command in global configuration mode.
Syntax Description seconds Timer value in seconds. Range is from 0 to 30 seconds; 0 is for the automatic
exponential backoff scheme.
Defaults The default configuration value is 0 seconds for automatic exponential backoff.
Usage Guidelines The Cisco Express Forwarding background resolution timer can use either a fixed time interval or an
exponential backoff timer that reacts to the amount of resolution work required. The exponential backoff
timer starts at 1 second, increasing to 16 seconds when a network flap is in progress. When the network
recovers, the timer returns to 1 second.
The default is used for the exponential backoff timer. During normal operation, the default configuration
value set to 0 results in re-resolution occurring much sooner than when the timer is set at a higher fixed
interval.
Examples The following example show how to set the Cisco Express Forwarding background resolution timer to
3 seconds:
Router(config)# ip cef table resolution-timer 3
ip cef traffic-statistics
To change the time interval that controls when Next Hop Resolution Protocol (NHRP) sets up or tears
down a switched virtual circuit (SVC), use the ip cef traffic-statistics command in global configuration
mode. To restore the default values, use the no form of this command.
no ip cef traffic-statistics
Syntax Description load-interval seconds (Optional) Length of time (in 30-second increments) during which the
average trigger-threshold and teardown-threshold intervals are
calculated before an SVC setup or teardown action is taken. (These
thresholds are configured in the ip nhrp trigger-svc command.) The
load-interval range is from 30 seconds to 300 seconds, in 30-second
increments. The default value is 30 seconds.
update-rate seconds (Optional) Frequency that the port adapter sends the accounting statistics
to the Route Processor (RP). When the route processor is using NHRP in
distributed Cisco Express Forwarding switching mode, this value must be
set to 5 seconds. The default value is 10 seconds.
Usage Guidelines The ip nhrp trigger-svc command sets the threshold by which NHRP sets up and tears down a
connection. The threshold is the Cisco Express Forwarding traffic load statistics. The thresholds in the
ip nhrp trigger-svc command are measured during a sampling interval of 30 seconds, by default. To
change that interval over which that threshold is determined, use the load-interval seconds option of the
ip cef traffic-statistics command.
When NHRP is configured on a Cisco Express Forwarding switching node with a Versatile Interface
Processor (VIP2) adapter, you must make sure the update-rate keyword is set to 5 seconds.
Other Cisco IOS features could also use the ip cef traffic-statistics command; this NHRP feature relies
on it.
Examples In the following example, the triggering and teardown thresholds are calculated based on an average over
120 seconds:
ip cef traffic-statistics load-interval 120
ip load-sharing
To enable load balancing for Cisco Express Forwarding on an interface, use the ip load-sharing
command in interface configuration mode. To disable load balancing for Cisco Express Forwarding on
the interface, use the no form of this command.
no ip load-sharing per-packet
Syntax Description per-packet Enables per-packet load balancing for Cisco Express Forwarding on
the interface. This functionality and keyword are not supported on all
platforms. See Usage Guidelines for more information.
per-destination Enables per-destination load balancing for Cisco Express
Forwarding on the interface.
Command Default Per-destination load balancing is enabled by default when you enable Cisco Express Forwarding.
Usage Guidelines Per-packet load balancing allows the router to send data packets over successive equal-cost paths
without regard to individual destination hosts or user sessions. Path utilization is good, but packets
destined for a given destination host might take different paths and might arrive out of order.
Note Per-packet load balancing via Cisco Express Forwarding is not supported on Engine 2 Cisco 12000
series Internet router line cards (LCs).
Per-destination load balancing allows the router to use multiple, equal-cost paths to achieve load
sharing. Packets for a given source-destination host pair are guaranteed to take the same path, even if
multiple, equal-cost paths are available. Traffic for different source-destination host pairs tends to take
different paths.
Note If you want to enable per-packet load sharing to a particular destination, then all interfaces that can
forward traffic to the destination must be enabled for per-packet load sharing.
Note Per-packet load balancing can result in out-of-sequence (OOS) packet delivery errors on some routers,
which can cause applications such as VoIP to malfunction. Therefore, per-packet load balancing is not
recommended. For more information, see the release notes and caveats for your platform and software
release.
Examples The following example shows how to enable per-packet load balancing:
Router(config)# interface E0
Router(config-if)# ip load-sharing per-packet
ip route-cache
To control the use of switching methods for forwarding IP packets, use the ip route-cache command in
interface configuration mode. To disable any of these switching methods, use the no form of this
command.
Syntax Description cef (Optional) Enables Cisco Express Forwarding operation on an interface.
distributed (Optional) Enables distributed switching on the interface. (This keyword is
not supported on the Cisco 7600 routers.) Distributed switching is disabled
by default.
flow (Optional) Enables NetFlow accounting for packets that are received by the
interface. The default is disabled.
policy (Optional) Enables fast-switching for packets that are forwarded using
policy-based routing (PBR). Fast Switching for PBR (FSPBR) is disabled by
default.
same-interface (Optional) Enables fast-switching of packets onto the same interface on
which they arrived.
Note The Cisco 10000 series routers do not support the ip route-cache command.
Using the route cache is often called fast switching. The route cache allows outgoing packets to be
load-balanced on a per-destination basis rather than on a per-packet basis. The ip route-cache command
with no additional keywords enables fast switching.
Entering the ip route-cache command has no effect on a subinterface. Subinterfaces accept the no form
of the command; however, this disables Cisco Express Forwarding or distributed Cisco Express
Forwarding on the physical interface and all subinterfaces associated with the physical interface
The default behavior for Fast Switching varies by interface and media.
Note IPv4 fast switching is removed with the implementation of the Cisco Express Forwarding infrastructure
enhancements for Cisco IOS 12.2(25)S-based releases and Cisco IOS Release 12.4(20)T. For these and
later Cisco IOS releases, switching path are Cisco Express Forwarding switched or process switched.
Note The ip route-cache flow command has the same functionality as the ip flow ingress command, which
is the preferred command for enabling NetFlow. If either the ip route-cache flow command or the
ip flow ingress command is configured, both commands will appear in the output of the
show running-config command.
Note On the Cisco 12000 series Internet router, you must not disable distributed Cisco Express Forwarding
on an interface.
Note Not all switching methods are available on all platforms. Refer to the Cisco Product Catalog for
information about features available on the platform you are using.
Examples Configuring Fast Switching and Disabling Cisco Express Forwarding Switching
The following example shows how to enable fast switching and disable Cisco Express Forwarding
switching:
Router(config)# interface ethernet 0/0/0
Router(config-if)# ip route-cache
The following example shows that Cisco Express Forwarding switching is disabled:
Router# show cef interface fastEthernet 0/0/0
FastEthernet0/0/0 is up (if_number 3)
Corresponding hwidb fast_if_number 3
Corresponding hwidb firstsw->if_number 3
Internet address is 10.1.1.254/24
ICMP redirects are always sent
Per packet load-sharing is disabled
IP unicast RPF check is disabled
Inbound access list is not set
Outbound access list is not set
IP policy routing is disabled
Hardware idb is FastEthernet0/0/0
Fast switching type 1, interface type 18
IP CEF switching disabled
IP Feature Fast switching turbo vector
IP Null turbo vector
Input fast flags 0x0, Output fast flags 0x0
ifindex 1(1)
Slot 0 Slot unit 0 VC -1
Transmit limit accumulator 0x48001A02 (0x48001A02)
IP MTU 1500
The following example shows the configuration information for FastEthernet interface 0/0/0:
Router# show running-config
.
.
!
interface FastEthernet0/0/0
ip address 10.1.1.254 255.255.255.0
no ip route-cache cef
no ip route-cache distributed
!
The following example shows how to enable Cisco Express Forwarding (and to disable distributed
Cisco Express Forwarding if it is enabled):
Router(config-if)# ip route-cache cef
The following example shows how to enable VIP distributed Cisco Express Forwarding and per-flow
accounting on an interface (regardless of the previous switching type enabled on the interface):
Router(config)# interface e0
Router(config-if)# ip address 10.252.245.2 255.255.255.0
Router(config-if)# ip route-cache distributed
Router(config-if)# ip route-cache flow
The following example shows how to enable Cisco Express Forwarding on the router globally (which
also disables distributed Cisco Express Forwarding on any interfaces that are running distributed
Cisco Express Forwarding), and disable Cisco Express Forwarding (which enables process switching)
on Ethernet interface 0:
Router(config)# ip cef
Router(config)# interface e0
Router(config-if)# no ip route-cache cef
The following example shows how to enable distributed Cisco Express Forwarding operation on the
router (globally), and disable Cisco Express Forwarding operation on Ethernet interface 0:
Router(config)# ip cef distributed
Router(config)# interface e0
Router(config-if)# no ip route-cache cef
The following example shows how to reenable distributed Cisco Express Forwarding operation on
Ethernet interface 0:
Router(config)# ip cef distributed
Router(config)# interface e0
Router(config-if)# ip route-cache distributed
Configuring Fast Switching for Traffic That Is Received and Transmitted over the Same Interface
The following example shows how to enable fast switching and disable Cisco Express Forwarding
switching:
Router(config)# interface ethernet 0/0/0
Router(config-if)# ip route-cache same-interface
The following example shows that fast switching on the same interface is enabled for interface
fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0
The following example shows the configuration information for FastEthernet interface 0/0/0:
Router# show running-config
.
.
!
interface FastEthernet0/0/0
ip address 10.1.1.254 255.255.255.0
ip route-cache same-interface
no ip route-cache cef
no ip route-cache distributed
!
The following example shows that NetFlow accounting is enabled for FastEthernet interface 0/0/0:
Router# show ip interface fastEthernet 0/0/0
The following example shows that distributed Cisco Express Forwarding switching is for FastEthernet
interface 0/0/0:
Router# show cef interface fastEthernet 0/0/0
FastEthernet0/0/0 is up (if_number 3)
Corresponding hwidb fast_if_number 3
Corresponding hwidb firstsw->if_number 3
Internet address is 10.1.1.254/24
ICMP redirects are always sent
Per packet load-sharing is disabled
IP unicast RPF check is disabled
Inbound access list is not set
Outbound access list is not set
IP policy routing is disabled
Hardware idb is FastEthernet0/0/0
Fast switching type 1, interface type 18
IP Distributed CEF switching enabled
IP Feature Fast switching turbo vector
IP Feature CEF switching turbo vector
Input fast flags 0x0, Output fast flags 0x0
ifindex 1(1)
Slot 0 Slot unit 0 VC -1
Transmit limit accumulator 0x48001A02 (0x48001A02)
IP MTU 1500
Router(config-route-map)# exit
Router(config)# interface fastethernet 0/0/0
Router(config-if)# ip route-cache policy
Router(config-if)# ip policy route-map mypbrtag
The following example shows that FSPBR is enabled for FastEthernet interface 0/0/0:
Router# show ip interface fastEthernet 0/0/0
ip route-cache policy
The policy keyword for the ip route-cache command is no longer documented as a separate command.
The information for using the policy keyword for the ip route-cache command has been incorporated
into the ip route-cache command documentation. See the ip route-cache command documentation for
more information.
Syntax Description packets-per-second Threshold value, in packets per second, used to determine whether to send a
Unicast RPF drop rate notification. The range is from 0 to 4294967295. The
default is 1000.
Usage Guidelines This command configures the threshold Unicast RPF drop rate which, when exceeded, triggers a
notification. Configuring a value of 0 means that any Unicast RPF packet drop triggers a notification.
Examples The following example shows how to configure a notification threshold value of 900 on Ethernet
interface 3/0:
Router> enable
Router# configure terminal
Router(config# interface ethernet 3/0
Router(config-if)# ip verify unicast notification threshold 900
To enable Unicast Reverse Path Forwarding (Unicast RPF), use the ip verify unicast reverse-path
command in interface configuration mode. To disable Unicast RPF, use the no form of this command.
Syntax Description list (Optional) Specifies a numbered access control list (ACL) in the following
ranges:
1 to 99 (IP standard access list)
100 to 199 (IP extended access list)
1300 to 1999 (IP standard access list, expanded range)
2000 to 2699 (IP extended access list, expanded range)
Release Modification
12.2(14)SX The ip verify unicast reverse-path command was integrated into
Cisco IOS Release 12.2(14)SX.
12.2(33)SRA The ip verify unicast reverse-path command was integrated into
Cisco IOS Release 12.2(33)SRA.
Usage Guidelines Use the ip verify unicast reverse-path interface command to mitigate problems caused by malformed
or forged (spoofed) IP source addresses that are received by a router. Malformed or forged source
addresses can indicate denial of service (DoS) attacks on the basis of source IP address spoofing.
When Unicast RPF is enabled on an interface, the router examines all packets that are received on that
interface. The router checks to ensure that the source address appears in the Forwarding Information
Base (FIB) and that it matches the interface on which the packet was received. This look backwards
ability is available only when Cisco Express Forwarding is enabled on the router because the lookup
relies on the presence of the FIB. Cisco Express Forwarding generates the FIB as part of its operation.
To use Unicast RPF, enable Cisco Express Forwarding switching or distributed Cisco Express
Forwarding switching in the router. There is no need to configure the input interface for Cisco Express
Forwarding switching. As long as Cisco Express Forwarding is running on the router, individual
interfaces can be configured with other switching modes.
Note It is very important for Cisco Express Forwarding to be configured globally in the router. Unicast RPF
will not work without Cisco Express Forwarding.
Note Unicast RPF is an input function and is applied on the interface of a router only in the ingress direction.
The Unicast Reverse Path Forwarding feature checks to determine whether any packet that is received
at a router interface arrives on one of the best return paths to the source of the packet. The feature does
this by doing a reverse lookup in the Cisco Express Forwarding table. If Unicast RPF does not find a
reverse path for the packet, Unicast RPF can drop or forward the packet, depending on whether an ACL
is specified in the Unicast Reverse Path Forwarding command. If an ACL is specified in the command,
then when (and only when) a packet fails the Unicast RPF check, the ACL is checked to determine
whether the packet should be dropped (using a deny statement in the ACL) or forwarded (using a permit
statement in the ACL). Whether a packet is dropped or forwarded, the packet is counted in the global IP
traffic statistics for Unicast RPF drops and in the interface statistics for Unicast RPF.
If no ACL is specified in the Unicast Reverse Path Forwarding command, the router drops the forged or
malformed packet immediately and no ACL logging occurs. The router and interface Unicast RPF
counters are updated.
Unicast RPF events can be logged by specifying the logging option for the ACL entries used by the
Unicast Reverse Path Forwarding command. Log information can be used to gather information about
the attack, such as source address, time, and so on.
Internet service provider (ISP) are likely to have symmetrical reverse paths. Unicast RPF may still be
applicable in certain multi-homed situations, provided that optional Border Gateway Protocol (BGP)
attributes such as weight and local preference are used to achieve symmetric routing.
With Unicast RPF, all equal-cost best return paths are considered valid. This means that Unicast RPF
works in cases where multiple return paths exist, provided that each path is equal to the others in terms
of the routing cost (number of hops, weights, and so on) and as long as the route is in the FIB. Unicast
RPF also functions where Enhanced Internet Gateway Routing Protocol (EIGRP) variants are being used
and unequal candidate paths back to the source IP address exist.
For example, routers at the edge of the network of an ISP are more likely to have symmetrical reverse
paths than routers that are in the core of the ISP network. Routers that are in the core of the ISP network
have no guarantee that the best forwarding path out of the router will be the path selected for packets
returning to the router. In this scenario, you should use the new form of the command, ip verify unicast
source reachable-via, if there is a chance of asymmetrical routing.
Examples The following example shows that the Unicast Reverse Path Forwarding feature has been enabled on a
serial interface:
ip cef
! or "ip cef distributed" for RSP+VIP based routers
!
interface serial 5/0/0
ip verify unicast reverse-path
The following example uses a very simple single-homed ISP to demonstrate the concepts of ingress and
egress filters used in conjunction with Unicast RPF. The example illustrates an ISP-allocated classless
interdomain routing (CIDR) block 192.168.202.128/28 that has both inbound and outbound filters on the
upstream interface. Be aware that ISPs are usually not single-homed. Hence, provisions for
asymmetrical flows (when outbound traffic goes out one link and returns via a different link) need to be
designed into the filters on the border routers of the ISP.
ip cef distributed
!
interface Serial 5/0/0
description Connection to Upstream ISP
ip address 192.168.200.225 255.255.255.255
no ip redirects
no ip directed-broadcast
no ip proxy-arp
ip verify unicast reverse-path
ip access-group 111 in
ip access-group 110 out
!
access-list 110 permit ip 192.168.202.128 10.0.0.31 any
access-list 110 deny ip any any log
access-list 111 deny ip host 10.0.0.0 any log
access-list 111 deny ip 172.16.0.0 255.255.255.255 any log
access-list 111 deny ip 10.0.0.0 255.255.255.255 any log
access-list 111 deny ip 172.16.0.0 255.255.255.255 any log
access-list 111 deny ip 192.168.0.0 255.255.255.255 any log
access-list 111 deny ip 209.165.202.129 10.0.0.31 any log
access-list 111 permit ip any any
The following example demonstrates the use of ACLs and logging with Unicast RPF. In this example,
extended ACL 197 provides entries that deny or permit network traffic for specific address ranges.
Unicast RPF is configured on Ethernet interface 0 to check packets arriving at that interface.
For example, packets with a source address of 192.168.201.10 arriving at Ethernet interface 0 are
dropped because of the deny statement in ACL 197. In this case, the ACL information is logged (the
logging option is turned on for the ACL entry) and dropped packets are counted per-interface and
globally. Packets with a source address of 192.168.201.100 arriving at Ethernet interface 0 are
forwarded because of the permit statement in ACL 197. ACL information about dropped or suppressed
packets is logged (the logging option is turned on for the ACL entry) to the log server.
ip cef distributed
!
int eth0/1/1
ip address 192.168.200.1 255.255.255.255
ip verify unicast reverse-path 197
!
int eth0/1/2
ip address 192.168.201.1 255.255.255.255
!
access-list 197 deny ip 192.168.201.0 10.0.0.63 any log-input
access-list 197 permit ip 192.168.201.64 10.0.0.63 any log-input
access-list 197 deny ip 192.168.201.128 10.0.0.63 any log-input
access-list 197 permit ip 192.168.201.192 10.0.0.63 any log-input
access-list 197 deny ip host 10.0.0.0 any log-input
access-list 197 deny ip 172.16.0.0 255.255.255.255 any log-input
access-list 197 deny ip 10.0.0.0 255.255.255.255 any log-input
access-list 197 deny ip 172.16.0.0 255.255.255.255 any log-input
access-list 197 deny ip 192.168.0.0 255.255.255.255 any log-input
Syntax Description any Examines incoming packets to determine whether the source address is in
the Forwarding Information Base (FIB) and permits the packet if the source
is reachable through any interface (sometimes referred to as loose mode).
rx Examines incoming packets to determine whether the source address is in
the FIB and permits the packet only if the source is reachable through the
interface on which the packet was received (sometimes referred to as strict
mode).
l2-src (Optional) Enables source IPv4 and source MAC address binding.
allow-default (Optional) Allows the use of the default route for RPF verification.
allow-self-ping (Optional) Allows a router to ping its own interface or interfaces.
Release Modification
12.0(15)S This command replaced the ip verify unicast reverse-path command, and
the following keywords were added: allow-default, allow-self-ping, rx, and
any.
12.1(8a)E This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(14)S This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(14)SX Support for this command was introduced on the Supervisor Engine 720.
12.2(17d)SXB Support for this command was introduced on the Supervisor Engine 2.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SRC This command was modified. The l2-src keyword was added to support the
source IPv4 and source MAC address binding feature on platforms that
support the Cisco Express Forwarding software switching path.
15.0(1)M This command was integrated into Cisco IOS Release 15.0(1)M.
Usage Guidelines Use the ip verify unicast source reachable-via interface command to mitigate problems caused by
malformed or forged (spoofed) IP source addresses that pass through a router. Malformed or forged
source addresses can indicate DoS attacks based on source IP address spoofing.
To use Unicast RPF, enable Cisco Express Forwarding or distributed Cisco Express Forwarding in the
router. There is no need to configure the input interface for Cisco Express Forwarding. As long as
Cisco Express Forwarding is running on the router, individual interfaces can be configured with other
switching modes.
Note It is important for Cisco Express Forwarding to be configured globally on the router. Unicast RPF does
not work without Cisco Express Forwarding.
Note Unicast RPF is an input function and is applied on the interface of a router only in the ingress direction.
When Unicast RPF is enabled on an interface, the router examines all packets that are received on that
interface. The router checks to make sure that the source address appears in the FIB. If the rx keyword
is selected, the source address must match the interface on which the packet was received. If the any
keyword is selected, the source address must be present only in the FIB. This ability to look backwards
is available only when Cisco Express Forwarding is enabled on the router because the lookup relies on
the presence of the FIB. Cisco Express Forwarding generates the FIB as part of its operation.
Note If the source address of an incoming packet is resolved to a null adjacency, the packet will be dropped.
The null interface is treated as an invalid interface by the new form of the Unicast RPF command. The
older form of the command syntax did not exhibit this behavior.
Unicast RPF checks to determine whether any packet that is received at a router interface arrives on one
of the best return paths to the source of the packet. If a reverse path for the packet is not found, Unicast
RPF can drop or forward the packet, depending on whether an ACL is specified in the Unicast RPF
command. If an ACL is specified in the command, when (and only when) a packet fails the Unicast RPF
check, the ACL is checked to determine whether the packet should be dropped (using a deny statement
in the ACL) or forwarded (using a permit statement in the ACL). Whether a packet is dropped or
forwarded, the packet is counted in the global IP traffic statistics for Unicast RPF drops and in the
interface statistics for Unicast RPF.
If no ACL is specified in the ip verify unicast source reachable-via command, the router drops the
forged or malformed packet immediately, and no ACL logging occurs. The router and interface Unicast
RPF counters are updated.
Unicast RPF events can be logged by specifying the logging option for the ACL entries that are used by
the ip verify unicast source reachable-via command. Log information can be used to gather
information about the attack, such as source address, time, and so on.
allow-default
Normally, sources found in the FIB but only by way of the default route will be dropped. Specifying the
allow-default keyword option will override this behavior. You must specify the allow-default keyword
in the command to permit Unicast RPF to successfully match on prefixes that are known through the
default route to pass these packets.
allow-self-ping
This keyword allows the router to ping its own interface or interfaces. By default, when Unicast RPF is
enabled, packets that are generated by the router and destined to the router are dropped, thereby, making
certain troubleshooting and management tasks difficult to accomplish. Issue the allow-self-ping
keyword to enable self-pinging.
Caution Caution should be used when enabling the allow-self-ping keyword because this option opens a
potential DoS hole.
Note With Unicast RPF, all equal-cost best return paths are considered valid. This means that Unicast RPF
works in cases where multiple return paths exist, provided that each path is equal to the others in terms
of the routing cost (number of hops, weights, and so on) and as long as the route is in the FIB. Unicast
RPF also functions where Enhanced Internet Gateway Routing Protocol (EIGRP) variants are being used
and unequal candidate paths back to the source IP address exist.
Use Unicast RPF loose mode on interfaces where asymmetric paths allow packets from valid source
networks (networks contained in the FIB). Routers that are in the core of the ISP network have no
guarantee that the best forwarding path out of the router will be the path selected for packets returning
to the router.
Note The l2-src keyword cannot be used with the loose uRPF command, ip verify unicast source
reachable-via any command.
Not all platforms support the l2-src keyword. Therefore, not all the possible keyword combinations for
strict Unicast RPF in the following list will apply to your platform:
Possible keyword combinations for strict Unicast RPF include the following:
allow-default
allow-self-ping
l2-src
<ACL-number>
allow-default allow-self-ping
allow-default l2-src
allow-default <ACL-number>
allow-self-ping l2-src
allow-self-ping <ACL-number>
l2-src <ACL-number>
allow-default allow-self-ping l2-src
allow-default allow-self-ping <ACL-number>
allow-default l2-src <ACL-number>
allow-self-ping l2-src <ACL-number>
allow-default allow-self-ping l2-src <ACL-number>
MAC Address Binding on Software Switching Platforms Like the Cisco 7200 Series Routers
The following example shows how to enable source IPv4 and source MAC address binding on
Ethernet 0/0:
Router# configure terminal
Router(config)# interface Ethernet0/0
Router(config-if)# ip address 10.0.0.1 255.255.255.0
Router(config-if)# ip verify unicast source reachable-via rx l2-src
Syntax Description vrf-name Virtual Private Network (VPN) routing and forwarding (VRF) instance
name.
deny Specifies that traffic associated with the specified VRF is dropped after it
passes the Unicast RPF verification.
permit Specifies that traffic associated with the specified VRF is forwarded after it
passes the Unicast RPF verification.
Usage Guidelines Unicast RPF is configured to verify that the source address is in the Forwarding Information Base (FIB).
The ip verify unicast vrf command is configured in interface configuration mode and is enabled for
each VRF. This command has permit and deny keywords that are used to determine if traffic is
forwarded or dropped after Unicast RPF verification.
Examples The following example configures Unicast RPF verification for VRF1 and VRF2. VRF1 traffic is
forwarded. VRF2 traffic is dropped.
Router(config)# interface Ethernet 0
Router(config-if)# ip verify unicast vrf vrf1 permit
Router(config-if)# ip verify unicast vrf vrf2 deny
Router(config-if)# end
ipv6 cef
To enable Cisco Express Forwarding for IPv6, use the ipv6 cef command in global configuration mode.
To disable Cisco Express Forwarding for IPv6, use the no form of this command.
ipv6 cef
no ipv6 cef
Usage Guidelines The ipv6 cef command is similar to the ip cef command, except that it is IPv6-specific.
The ipv6 cef command is not available on the Cisco 12000 series Internet routers because this distributed
platform operates only in distributed Cisco Express Forwarding for IPv6 mode.
Note The ipv6 cef command is not supported in interface configuration mode.
Note Some distributed architecture platforms, such as the Cisco 7500 series routers, support both Cisco
Express Forwarding for IPv6 and distributed Cisco Express Forwarding for IPv6. When Cisco Express
Forwarding for IPv6 is configured on distributed platforms, Cisco Express Forwarding switching is
performed by the Route Processor (RP).
Note You must enable Cisco Express Forwarding for IPv4 by using the ip cef global configuration command
before enabling Cisco Express Forwarding for IPv6 by using the ipv6 cef global configuration
command.
Cisco Express Forwarding for IPv6 is advanced Layer 3 IP switching technology that functions the same
and offer the same benefits as Cisco Express Forwarding for IPv4. Cisco Express Forwarding for IPv6
optimizes network performance and scalability for networks with dynamic, topologically dispersed
traffic patterns, such as those associated with web-based applications and interactive sessions.
Examples The following example enables standard Cisco Express Forwarding for IPv4 operation and then standard
Cisco Express Forwarding for IPv6 operation globally on the router.
ip cef
ipv6 cef
Specific Cisco Express Forwarding Accounting Information Through Interface Configuration Mode
Syntax Description accounting-types The accounting-types argument must be replaced with at least one of
the following keywords. Optionally, you can follow this keyword by
any or all of the other keywords, but you can use each keyword only
once.
load-balance-hashEnables load balancing hash bucket
counters.
non-recursiveEnables accounting through nonrecursive
prefixes.
per-prefixEnables express forwarding of the collection of the
number of packets and bytes to a destination (or prefix).
prefix-lengthEnables accounting through prefix length.
non-recursive Enables accounting through nonrecursive prefixes.
This keyword is optional when used in global configuration mode
after another keyword is entered. See the accounting-types argument.
external Counts input traffic in the nonrecursive external bin.
internal Counts input traffic in the nonrecursive internal bin.
Command Default Cisco Express Forwarding for IPv6 network accounting is disabled by default.
Release Modification
12.2(25)S The non-recursive and load-balance-hash keywords were added.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
Cisco IOS XE This command was introduced on Cisco ASR 1000 Series Routers.
Release 2.1
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines The ipv6 cef accounting command is similar to the ip cef accounting command, except that it is
IPv6-specific.
Configuring Cisco Express Forwarding for IPv6 network accounting enables you to collect statistics on
Cisco Express Forwarding for IPv6 traffic patterns in your network.
When you enable network accounting for Cisco Express Forwarding for IPv6 by using the ipv6 cef
accounting command in global configuration mode, accounting information is collected at the Route
Processor (RP) when Cisco Express Forwarding for IPv6 mode is enabled and at the line cards when
distributed Cisco Express Forwarding for IPv6 mode is enabled. You can then display the collected
accounting information using the show ipv6 cef EXEC command.
For prefixes with directly connected next hops, the non-recursive keyword enables express forwarding
of the collection of packets and bytes through a prefix. This keyword is optional when this command is
used in global configuration mode after you enter another keyword on the ipv6 cef accounting
command.
This command in interface configuration mode must be used in conjunction with the global
configuration command. The interface configuration command allows a user to specify two different
bins (internal or external) for the accumulation of statistics. The internal bin is used by default. The
statistics are displayed through the show ipv6 cef detail command.
Per-destination load balancing uses a series of 16 hash buckets into which the set of available paths are
distributed. A hash function operating on certain properties of the packet is applied to select a bucket
that contains a path to use. The source and destination IP addresses are the properties used to select the
bucket for per-destination load balancing. Use the load-balance-hash keyword with the ipv6 cef
accounting command to enable per-hash-bucket counters. Enter the show ipv6 cef prefix internal
command to display the per-hash-bucket counters.
Examples The following example enables the collection of Cisco Express Forwarding for IPv6 accounting
information for prefixes with directly connected next hops:
Router(config)# ipv6 cef accounting non-recursive
Command Default Distributed Cisco Express Forwarding for IPv6 is disabled on the Cisco 7500 series routers and enabled
on the Cisco 12000 series Internet routers.
Usage Guidelines The ipv6 cef distributed command is similar to the ip cef distributed command, except that it is
IPv6-specific.
Enabling distributed Cisco Express Forwarding for IPv6 globally on the router by using the ipv6 cef
distributed in global configuration mode distributes the Cisco Express Forwarding processing of IPv6
packets from the Route Processor (RP) to the line cards of distributed architecture platforms.
Note The ipv6 cef distributed command is not supported on the Cisco 12000 series Internet routers because
distributed Cisco Express Forwarding for IPv6 is enabled by default on this platform.
Note To forward distributed Cisco Express Forwarding for IPv6 traffic on the router, configure the forwarding
of IPv6 unicast datagrams globally on your router by using the ipv6 unicast-routing global
configuration command, and configure an IPv6 address and IPv6 processing on an interface by using the
ipv6 address interface configuration command.
Note You must enable distributed Cisco Express Forwarding for IPv4 by using the ip cef distributed global
configuration command before enabling distributed Cisco Express Forwarding for IPv6 by using the
ipv6 cef distributed global configuration command.
Cisco Express Forwarding is advanced Layer 3 IP switching technology. Cisco Express Forwarding
optimizes network performance and scalability for networks with dynamic, topologically dispersed
traffic patterns, such as those associated with web-based applications and interactive sessions.
Examples The following example enables distributed Cisco Express Forwarding for IPv6 operation:
ipv6 cef distributed
ipv6 cef load-sharing algorithm {original | universal [id] | include-ports {source [id] |
[destination] [id] | source [id] destination [id]}}
Syntax Description original Sets the load-balancing algorithm to the original algorithm based on a
source and destination hash.
universal Sets the load-balancing algorithm to the universal algorithm that uses
a source and destination and an ID hash.
id (Optional) Fixed identifier in hexadecimal format.
include-ports source Sets the load-balancing algorithm to the include-ports algorithm that
uses a Layer 4 source port.
include-ports destination Sets the load-balancing algorithm to the include-ports algorithm that
uses a Layer 4 destination port.
include-ports source Sets the load balancing algorithm to the include-ports algorithm that
destination uses Layer 4 source and destination ports.
Command Default The universal load-balancing algorithm is selected. If you do not configure the fixed identifier for a
load-balancing algorithm, the router automatically generates a unique ID.
Usage Guidelines The ipv6 cef load-sharing algorithm command is similar to the ip cef load-sharing algorithm
command, except that it is IPv6-specific.
When the Cisco Express Forwarding for IPv6 load-balancing algorithm is set to universal mode, each
router on the network can make a different load-sharing decision for each source-destination address
pair.
The include-ports algorithm allows you to use the Layer 4 source and destination ports as part of the
load-balancing decision. This method benefits traffic streams running over equal-cost paths that are not
load-shared because the majority of the traffic is between peer addresses that use different port numbers,
such as Real-Time Protocol (RTP) streams.
Examples The following example shows how to enable the Cisco Express Forwarding load-balancing algorithm
for IPv6 for Layer-4 source and destination ports:
Router(config)# ipv6 cef load-sharing algorithm include-ports source destination
Command Default If this command is not configured, Cisco Express Forwarding for IPv6 does not optimize the address
resolution of directly connected neighbors.
Usage Guidelines The ipv6 cef optimize neighbor resolution command is very similar to the ip cef optimize neighbor
resolution command, except that it is IPv6-specific.
Use this command to trigger Layer 2 address resolution of neighbors directly from Cisco Express
Forwarding for IPv6.
Examples The following example shows how to optimize address resolution from Cisco Express Forwarding for
IPv6 for directly connected neighbors:
Router(config)# ipv6 cef optimize neighbor resolution
Syntax Description access-list name (Optional) Specifies the name of the access list.
Note This keyword and argument are not supported on the Cisco 12000
series Internet router.
Usage Guidelines The ipv6 verify unicast reverse-path command is used to enable Unicast RPF for IPv6 in strict
checking mode. The Unicast RPF for IPv6 feature requires that Cisco Express Forwarding for IPv6 is
enabled on the router.
Note Beginning in Cisco IOS Release 12.0(31)S, the Cisco 12000 series Internet router supports both the
ipv6 verify unicast reverse-path and ipv6 verify unicast source reachable-via rx commands to
enable Unicast RPF to be compatible with the Cisco IOS Release 12.3T and 12.2S software trains.
Use the ipv6 verify unicast reverse-path command to mitigate problems caused by malformed or
forged (spoofed) IP source addresses that pass through a router. Malformed or forged source addresses
can indicate denial-of-service (DoS) attacks based on source IP address spoofing.
When Unicast RPF is enabled on an interface, the router examines all packets received on that interface.
The router checks to make sure that the source IPv6 address appears in the routing table and that it is
reachable by a path through the interface on which the packet was received. Unicast RPF is an input
feature and is applied only on the input interface of a router at the upstream end of a connection.
The Unicast RPF feature performs a reverse lookup in the CEF table to check if any packet received at
a router interface has arrived on a path identified as a best return path to the source of the packet. If a
reverse path for the packet is not found, Unicast RPF can drop or forward the packet, depending on
whether an ACL is specified in the Unicast RPF command. If an ACL is specified in the command, then
when (and only when) a packet fails the Unicast RPF check, the ACL is checked to determine whether
the packet should be dropped (using a deny statement in the ACL) or forwarded (using a permit
statement in the ACL). Whether a packet is dropped or forwarded, the packet is counted in the global IP
traffic statistics for Unicast RPF drops and in the interface statistics for Unicast RPF.
If no ACL is specified in the Unicast RPF command, the router drops the forged or malformed packet
immediately and no ACL logging occurs. The router and interface Unicast RPF counters are updated.
Unicast RPF events can be logged by specifying the logging option for the ACL entries used by the
Unicast RPF command. Log information can be used to gather information about the attack, such as
source address, time, and so on.
Note When you configure Unicast RPF for IPv6 on the Cisco 12000 series Internet router, the most recently
configured checking mode is not automatically applied to all interfaces as on other platforms. You must
enable Unicast RPF for IPv6 separately on each interface.
When you configure a SPA on the Cisco 12000 series Internet router, the interface address is in the
format slot/subslot/port.
The optional access-list keyword for the ipv6 verify unicast reverse-path command is not supported
on the Cisco 12000 series Internet router. For information about how Unicast RPF can be used with
ACLs on other platforms to mitigate the transmission of invalid IPv4 addresses (perform egress filtering)
and to prevent (deny) the reception of invalid IPv4 addresses (perform ingress filtering), refer to the
Configuring Unicast Reverse Path Forwarding chapter in the Other Security Features section of the
Cisco IOS Security Configuration Guide.
Note When using Unicast RPF, all equal-cost best return paths are considered valid. This means that
Unicast RPF works in cases where multiple return paths exist, provided that each path is equal to the
others in terms of the routing cost (number of hops, weights, and so on).
Do not use Unicast RPF on core-facing interfaces that are internal to the network. Internal interfaces are
likely to have routing asymmetry, meaning that there are multiple routes to the source of a packet. Apply
Unicast RPF only where there is natural or configured symmetry.
For example, routers at the edge of the network of an Internet service provider (ISP) are more likely to
have symmetrical reverse paths than routers that are in the core of the ISP network. Routers that are in
the core of the ISP network have no guarantee that the best forwarding path out of the router will be the
path selected for packets returning to the router. Hence, it is not recommended that you apply Unicast
RPF where there is a chance of asymmetric routing. It is simplest to place Unicast RPF only at the edge
of a network or, for an ISP, at the customer edge of the network.
Syntax Description rx Source is reachable through the interface on which the packet was
received.
any Source is reachable through any interface.
allow-default (Optional) Allows the lookup table to match the default route and use
the route for verification.
allow-self-ping (Optional) Allows the router to ping a secondary address.
access-list-name (Optional) Name of the IPv6 access list. Names cannot contain a
space or quotation mark, or begin with a numeral.
Usage Guidelines The ipv6 verify unicast reverse-path command is used to enable Unicast RPF for IPv6 in loose
checking mode.
Use the ipv6 verify unicast source reachable-via command to mitigate problems caused by malformed
or forged (spoofed) IP source addresses that pass through an IPv6 router. Malformed or forged source
addresses can indicate denial-of-service (DoS) attacks based on source IPv6 address spoofing.
The URPF feature checks to see if any packet received at a router interface arrives on one of the best
return paths to the source of the packet. The feature does this by doing a reverse lookup in the CEF table.
If URPF does not find a reverse path for the packet, U RPF can drop or forward the packet, depending
on whether an access control list (ACL) is specified in the ipv6 verify unicast source reachable-via
command. If an ACL is specified in the command, then when (and only when) a packet fails the URPF
check, the ACL is checked to see if the packet should be dropped (using a deny statement in the ACL)
or forwarded (using a permit statement in the ACL). Whether a packet is dropped or forwarded, the
packet is counted in the global IP traffic statistics for U RPF drops and in the interface statistics for
Unicast RPF.
If no ACL is specified in the ipv6 verify unicast source reachable-via command, the router drops the
forged or malformed packet immediately and no ACL logging occurs. The router and interface Unicast
RPF counters are updated.
U RPF events can be logged by specifying the logging option for the ACL entries used by the ipv6 verify
unicast source reachable-via command. Log information can be used to gather information about the
attack, such as source address, time, and so on.
Note See the Usage Guidelines section for information on XL and non-XL mode systems.
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.
The mls 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 software release 12.2SXF and earlier releases see:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/release/notes/OL_41
64.html#Policy_Feature_Card_Guidelines_and_Restrictions
For additional information on systems running Cisco IOS software 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 modeXL mode or non-XL
mode. The valid values are as follows:
XL mode
IP and MPLSUp to 1,007,000 routes
IP multicast and IPv6Up to 503,000 routes
Non-XL mode
IP and MPLSUp to 239,000 routes
IP multicast and IPv6Up to 119,000 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)# mls cef maximum-routes ip 100
This example shows how to return to the default setting for a specific protocol:
Router(config)# no mls cef maximum-routes ip
Usage Guidelines When you enable tunnel fragmentation, if the size of the packets that are going into a tunnel interface
exceed the MTU, the packet is fragmented. The packets that are fragmented are reassembled at the
destination point.
Note The mls erm priority command is not available in Cisco IOS Release 12.2(33)SXJ and later Cisco IOS
12.2SX releases.
Syntax Description ipv4 Prioritizes the IPv4 protocol. The default priority is 1.
value Priority value; valid values are from 1 to 3.
ipv6 Prioritizes the IPv6 protocol. The default priority is 2.
mpls Prioritizes the Multiprotocol Label Switching (MPLS) protocol. The default
priority is 3.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
A lower value indicates a higher priority.
When a protocol sees a Forwarding Information Base (FIB) table exception, the protocol notifies the FIB
Embedded Resource Manager (ERM). The FIB ERM periodically polls the FIB table exception status
and decides which protocol gets priority over another protocol when multiple protocols are running
under the exception. Only one protocol can attempt to recover from an exception at any time.
If there is sufficient FIB space, the protocol with the highest priority tries to recover first. Other protocols
under the exception do not start to recover until the previous protocol completes the recovery process by
reloading the appropriate FIB table.
Examples This example shows how to set the ERM exception-recovery priority:
Router(config)# mls erm priority ipv4 2 ipv6 1 mpls 3
mls ip
To enable multilayer switching (MLS) IP for the internal router on the interface, use the mls ip command
in interface configuration mode. To disable MLS IP on the interface use the no form of this command.
mls ip
no mls ip
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 720.
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.
Syntax Description 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).
exclude-port (Optional) Excludes the destination Layer 4 ports and source and destination IP
destination addresses (Layer 3) from the load-balancing algorithm.
exclude-port (Optional) Excludes the source Layer 4 ports and source and destination IP
source addresses (Layer 3) from the load-balancing algorithm.
simple (Optional) Sets the Cisco Express Forwarding load balancing for single-stage load
sharing.
Usage Guidelines The mls ip cef load-sharing command affects the IPv4, the IPv6, and the Multiprotocol Label Switching
(MPLS) forwardings.
The mls ip cef load-sharing command is structured as follows:
mls ip cef load-sharing fullUses Layer 3 and Layer 4 information with multiple adjacencies.
mls ip cef load-sharing full simpleUses Layer 3 and Layer 4 information without multiple
adjacencies.
mls ip cef load-sharing simpleUses Layer 3 information without 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)# mls ip cef load-sharing full
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)# mls ip cef load-sharing full exclude-port destination
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)# mls ip cef load-sharing full exclude-port source
Syntax Description packets-per-second Number of data packets per second; see the Usage Guidelines section for the
valid values.
Usage Guidelines The valid values for the number of data packets per second are as follows:
For Cisco 7600 series routers that are configured with a Supervisor Engine 2, the valid values are
from 1 to 1000000.
For Cisco 7600 series routers that are configured with a Supervisor Engine 720, the valid values are
from 0 to 1000000.
Certain denial-of-service attacks target the route processing engines of routers. Certain packets that
cannot be forwarded by the Policy Feature Card (PFC) are directed to the Multilayer Switch Feature
Card (MSFC) for processing. Denial-of-service attacks can overload the route processing engine and
cause routing instability when running dynamic routing protocols. You can use the mls ip cef rate-limit
command to limit the amount of traffic that is sent to the MSFC to prevent denial-of-service attacks
against the route processing engine.
This command rate limits all Cisco Express Forwarding-punted data packets including the following:
Data packets going to the local interface IP address
Data packets requiring Address Resolution Protocol (ARP)
Setting the rate to a low value could impact the packets that are destined to the IP addresses of the local
interfaces and the packets that require ARP.
You should use this command to limit these packets to a normal rate and to avoid abnormal incoming
rates.
For additional guidelines, see the Cisco 7600 Series Router Cisco IOS Software Configuration Guide.
Examples This example shows how to enable and set rate limiting:
Router(config)# mls ip cef rate-limit 50000
Usage Guidelines This command is supported on systems configured with a PFC3 (Supervisor Engine 720 and Supervisor
Engine 32) only.
If you do not enter the mls ip cef rpf hw-enable-rpf-acl command, when the uRPF with ACL is
specified, packets that are permitted by the uRPF ACL are forwarded in hardware and the denied packets
are sent to the Multilayer Switching Feature Card (MSFC) for the uRPF check. This command enables
hardware forwarding with the uRPF check for the packets that are denied by the uRPF ACL. However,
in this case packets permitted by the uRPF ACL are sent to the MSFC for forwarding.
Examples This example shows how to enable hardware uRPF when RPF and ACL are enabled:
mls ip cef rpf hw-enable-rpf-acl
This example shows how to disable hardware uRPF when RPF and ACL are enabled:
no mls ip cef rpf hw-enable-rpf-acl
Syntax Description group-number Interface group number; valid values are from 1 to 4.
interface Interface number; see the Usage Guidelines section for formatting guidelines.
... (Optional) Additional interface numbers; see the Usage Guidelines section for
additional information.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
A single interface group contains three to six interfaces. You can configure up to four interface groups.
For each interface group, the first four entries are installed in the hardware RPF-VLAN table.
Enter the interface as interface-typemod/port.
Separate each interface entry with a space. You do not have to include a space between the interface-type
and the mod/port arguments. See the Examples section for a sample entry.
Syntax Description interface-group Disables the RPF check for packets coming from multiple path routes; see the
Usage Guidelines section for additional information.
punt Redirects the RPF-failed packets to the route processor for multiple path prefix
support.
pass Disables the RPF check for packets coming from multiple path routes.
Defaults punt
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
The interface-group mode is similar to the pass mode but utilizes the RPF_VLAN global table for the
RPF check. Packets from other multiple path prefixes always pass the RPF check.
You enter the mls ip cef rpf multipath interface-group command to define an RPF_VLAN table
interface group. One interface group contains from three to six interfaces, and you can configure up to
four interface groups. For each interface group, the first four entries are installed in the hardware
RPF_VLAN table. For the prefix that has more than three multiple paths, and all paths except two are
part of that interface group, the FIB entry of that prefix uses this RPF_VLAN entry.
Examples This example shows how to redirect the RPF-failed packets to the route processor for multiple path
prefix support:
Router(config)# mls ip cef rpf multipath interface-group
Syntax Description position-percentage The position of the trigger in the buffer expressed in percentage.
Examples The following example shows how to monitor 50 percent of the system events using event-logging
control and trigger control parameters:
Router# monitor elog trigger position 50
monitor event-trace component {clear | continuous | disable | dump [pretty] | enable | one-shot}
monitor event-trace l3 {clear | continuous [cancel] | disable | dump [pretty] | enable | interface
type mod/port | one-shot}
monitor event-trace spa {clear | continuous [cancel] | disable | dump [pretty] | enable |
one-shot}
monitor event-trace subsys {clear | continuous [cancel] | disable | dump [pretty] | enable |
one-shot}
Syntax Description component Name of the Cisco IOS software subsystem component that is the subject of
the event trace. To get a list of components that support event tracing, use
the monitor event-trace ? command.
clear Clears existing trace messages for the specified component from memory
on the networking device.
continuous Continuously displays the latest event trace entries.
disable Turns off event tracing for the specified component.
dump Writes the event trace results to the file configured using the monitor
event-trace command in global configuration mode. The trace messages
are saved in binary format.
pretty (Optional) Saves the event trace message in ASCII format.
enable Turns on event tracing for the specified component.
one-shot Clears any existing trace information from memory, starts event tracing
again, and disables the trace when the trace reaches the size specified using
the monitor event-trace command in global configuration mode.
size Sets the number of messages that can be written to memory for a single
instance of a trace.
Note Some Cisco IOS software subsystem components set the size by
default. To display the size parameter, use the show monitor
event-trace component parameters command.
When the number of event trace messages in memory exceeds the size, new
messages will begin to overwrite the older messages in the file.
stacktrace Enables the stack trace at tracepoints.
all-traces Displays the configured merged-event traces.
merged (Optional) Dumps the entries in all event traces sorted by time.
l3 Displays information about the Layer 3 trace.
spa Displays information about the Shared Port Adapter (SPA) trace.
interface type mod/port Specifies the interface to be logged.
cancel (Optional) Cancels the continuous display of latest trace entries.
subsys Displays information about the subsystems initial trace.
Usage Guidelines Use the monitor event-trace command to control what, when, and how event trace data is collected.
Use this command after you have configured the event trace functionality on the networking device
using the monitor event-trace command in global configuration mode.
Note The amount of data collected from the trace depends on the trace message size configured using
the monitor event-trace command in global configuration mode for each instance of a trace.
The Cisco IOS software allows for the subsystem components to define whether support for event
tracing is enabled or disabled at boot time. You can enable or disable event tracing in two ways: using
the monitor event-trace command in privileged EXEC mode or using the monitor event-trace
command in global configuration mode. To disable event tracing, you would enter either of these
commands with the disable keyword. To enable event tracing again, you would enter either of these
commands with the enable keyword.
To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ?
command to get a list of software components that support event tracing. To determine whether event
tracing is enabled by default for the subsystem, use the show monitor event-trace command to display
trace messages.
Use the show monitor event-trace command to display trace messages. Use the monitor event-trace
component dump command to save trace message information for a single event. By default, trace
information is saved in binary format. If you want to save trace messages in ASCII format, possibly for
additional application processing, use the monitor event-trace component dump pretty command.
To write the trace messages for all events currently enabled on a networking device to a file, enter the
monitor event-trace dump command.
To configure the file where you want to save trace information, use the monitor event-trace command
in global configuration mode. The trace messages are saved in a binary format.
Examples The following example shows the privileged EXEC commands to stop event tracing, clear the current
contents of memory, and reenable the trace function for the interprocess communication (IPC)
component. This example assumes that the tracing function is configured and enabled on the networking
device.
Router# monitor event-trace ipc disable
Router# monitor event-trace ipc clear
Router# monitor event-trace ipc enable
The following example shows how the monitor event-trace one-shot command accomplishes the same
function as the previous example except in one command. In this example, once the size of the trace
message file has been exceeded, the trace is terminated.
Router# monitor event-trace ipc one-shot
The following example shows the command for writing trace messages for an event in binary format. In
this example, the trace messages for the IPC component are written to a file.
Router# monitor event-trace ipc dump
The following example shows the command for writing trace messages for an event in ASCII format. In
this example, the trace messages for the MBUS component are written to a file.
Router# monitor event-trace mbus dump pretty
Catalyst 6500 Series Switches and Cisco 7600 Series Routers Examples Only
This example shows how to stop event tracing, clear the current contents of memory, and reenable the
trace function for the SPA component. This example assumes that the tracing function is configured and
enabled on the networking device.
Router# monitor event-trace spa disable
Router# monitor event-trace spa clear
Router# monitor event-trace spa enable
monitor event-trace component {disable | dump-file filename | enable | size number | stacktrace
number} timestamps [datetime [localtime] [msec] [show-timezone] | uptime]
Syntax Description component Name of the Cisco IOS software subsystem component that is the object of
the event trace. To get a list of components that support event tracing, use
the monitor event-trace ? command.
disable Turns off event tracing for the specified component.
dump-file filename Specifies the file where event trace messages are written from memory on
the networking device. The maximum length of the filename (path and
filename) is 100 characters, and the path can point to flash memory on the
networking device or to a TFTP or FTP server.
enable Turns on event tracing for the specified component provided that the
component has been configured using the monitor event-trace command.
size number Sets the number of messages that can be written to memory for a single
instance of a trace. Valid values are from1 to 65536.
Note Some Cisco IOS software subsystem components set the size by
default. To display the size parameter, use the show monitor
event-trace component parameters command.
Command Default Event tracing is enabled or disabled depending on the software component.
Usage Guidelines Use the monitor event-trace command to enable or disable event tracing and to configure event trace
parameters for Cisco IOS software subsystem components.
Note Event tracing is intended for use as a software diagnostic tool and should be configured only under the
direction of a Technical Assistance Center (TAC) representative. In Cisco IOS software images that do
not provide subsystem support for the event trace function, the monitor event-trace command is not
available.
The Cisco IOS software allows the subsystem components to define whether support for event tracing
is enabled or disabled by default. The command interface for event tracing allows you to change the
default two ways: using the monitor event-trace command in privileged EXEC mode or using the
monitor event-trace command in global configuration mode.
Additionally, default settings do not show up in the configuration file. If the subsystem software enables
event tracing by default, the monitor event-trace component enable command will not show up in the
configuration file of the networking device; however, disabling event tracing that has been enabled by
default by the subsystem will create a command entry in the configuration file.
Note The amount of data collected from the trace depends on the trace message size configured using the
monitor event-trace command for each instance of a trace.
To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ?
command to get a list of software components that support event tracing.
To determine whether event tracing is enabled by default for the subsystem, use the show monitor
event-trace command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer.
Examples The following example shows how to enable event tracing for the interprocess communication (IPC)
subsystem component in Cisco IOS software and configure the size to 4096 messages. The trace
messages file is set to ipc-dump in slot0 (flash memory).
configure terminal
!
monitor event-trace ipc enable
monitor event-trace ipc dump-file slot0:ipc-dump
monitor event-trace ipc size 4096
When you select Cisco Express Forwarding as the component for which to enable event tracing, you can
use the following additional arguments and keywords: monitor event-trace cef [events | interface |
ipv6 | ipv4][all]. The following example shows how to enable event tracing for IPv4 or IPv6 events of
the Cisco Express Forwarding component in Cisco IOS software:
configure terminal
!
monitor event-trace cef ipv4 enable
configure terminal
!
monitor event-trace cef ipv6 enable
exit
The following example shows what happens when you try to enable event tracing for a component (in
this case, adjacency events) when it is already enabled:
configure terminal
!
monitor event-trace adjacency enable
monitor event-trace cef {dump [merged pretty | pretty] | {events | interface | ipv4 | ipv6} {clear
| continuous [cancel] | disable | dump [pretty] | enable | one-shot}}
Syntax Description dump Writes the event trace results to the file configured with the global
configuration monitor event-trace cef command. The trace messages are
saved in binary format.
merged pretty (Optional) Sorts all event trace entries by time and writes the entries to a file
in ASCII format.
pretty (Optional) Saves the event trace message in ASCII format.
events Monitors Cisco Express Forwarding events.
interface Monitors Cisco Express Forwarding interface events.
ipv4 Monitors Cisco Express Forwarding IPv4 events.
ipv6 Monitors Cisco Express Forwarding IPv6 events.
clear Clears existing trace messages for Cisco Express Forwarding from memory
on the networking device.
continuous Continuously displays the latest event trace entries.
cancel (Optional) Cancels the continuous display of the latest trace entries.
disable Turns off Cisco Express Forwarding event tracing.
enable Turns on Cisco Express Forwarding event tracing.
one-shot Clears any existing trace information from memory, starts event tracing
again, and disables the trace when the size of the trace message file
configured in the global configuration command is exceeded.
Command Default Event tracing for Cisco Express Forwarding is enabled by default.
Release Modification
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Cisco IOS XE This command was integrated into Cisco IOS XE Release 2.1 and
Release 2.1 implemented on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines Use the monitor event-trace cef command to control what, when, and how Cisco Express Forwarding
event trace data is collected. Use this command after you have configured the event trace functionality
on the networking device using the monitor event-trace cef command in global configuration mode.
Note The amount of data collected from the trace depends on the trace message size configured using
the monitor event-trace cef command in global configuration mode for each instance of a trace.
You can enable or disable Cisco Express Forwarding event tracing in one of two ways: using the
monitor event-trace cef command in privileged EXEC mode or using the monitor event-trace cef
command in global configuration mode. To disable event tracing, you would enter either of these
commands with the disable keyword. To enable event tracing again, you would enter either of these
commands with the enable keyword.
Use the show monitor event-trace cef command to display trace messages. Use the monitor
event-trace cef dump command to save trace message information for a single event. By default, trace
information is saved in binary format. If you want to save trace messages in ASCII format, possibly for
additional application processing, use the monitor event-trace cef dump pretty command.
To configure the file in which you want to save trace information, use the monitor event-trace cef
command in global configuration mode. The trace messages are saved in a binary format.
Examples The following example shows the privileged EXEC commands that stop event tracing, clear the current
contents of memory, and reenable the trace function for Cisco Express Forwarding events. This example
assumes that the tracing function is configured and enabled on the networking device.
Router# monitor event-trace cef events disable
Router# monitor event-trace cef events clear
Router# monitor event-trace cef events enable
The following example shows how to configure the continuous display of the latest Cisco Express
Forwarding event trace entries for IPv4 events:
Router# monitor event-trace cef ipv4 continuous
The following example shows how to stop the continuous display of the latest trace entries:
Router# monitor event-trace cef ipv4 continuous cancel
Syntax Description dump-file Specifies the file to which event trace messages are written from memory on
dump-file-name the networking device. The maximum length of the filename (path and
filename) is 100 characters, and the path can point to flash memory on the
networking device or to a TFTP or FTP server.
events Turns on event tracing for Cisco Express Forwarding events.
interface Turns on event tracing for Cisco Express Forwarding interface events.
disable Turns off event tracing for Cisco Express Forwarding events.
enable Turns on event tracing for Cisco Express Forwarding events if it had been
enabled with the monitor event-trace cef command.
size number Sets the number of messages that can be written to memory for a single
instance of a trace. Range: 1 to 65536.
Note Some Cisco IOS software subsystem components set the size by
default. To display the size parameter, use the show monitor
event-trace cef parameters command.
When the number of event trace messages in memory exceeds the configured
size, new messages will begin to overwrite the older messages in the file.
stacktrace Enables the stack trace at tracepoints.
depth (Optional) Specifies the depth of the stack trace stored. Range: 1 to 16.
Command Default Event tracing for Cisco Express Forwarding is enabled by default.
Release Modification
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Cisco IOS XE This command was integrated into Cisco IOS XE Release 2.1 and
Release 2.1 implemented on the Cisco ASR 1000 Series Aggregation Services Routers.
Usage Guidelines Use the monitor event-trace cef command to enable or disable event tracing and to configure event
trace parameters for Cisco Express Forwarding.
The Cisco IOS software allows Cisco Express Forwarding to define whether support for event tracing is
enabled or disabled by default. The command interface for event tracing allows you to change the default
value in one of two ways: using the monitor event-trace cef command in privileged EXEC mode or
using the monitor event-trace cef command in global configuration mode.
Additionally, default settings do not appear in the configuration file. If Cisco Express Forwarding
enables event tracing by default, the monitor event-trace cef enable command does not appear in the
configuration file of the networking device; however, disabling event tracing that has been enabled by
default by the subsystem creates a command entry in the configuration file.
Note The amount of data collected from the trace depends on the trace message size configured using the
monitor event-trace cef command for each instance of a trace.
To determine whether event tracing is enabled by default for Cisco Express Forwarding, use the show
monitor event-trace cef command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer.
Examples The following example shows how to enable event tracing for Cisco Express Forwarding and configure
the buffer size to 5000 messages. The trace messages file is set to cef-dump in slot0 (flash memory).
Router(config)# monitor event-trace cef events enable
The following example shows what happens when you try to enable event tracing for Cisco Express
Forwarding events when it is already enabled:
Router(config)#
00:04:33: %EVENT_TRACE-6-ENABLE: Trace already enabled.
monitor event-trace cef ipv4 {disable | distribution | dump-file dump-file-name | enable | match
{global | ip-address mask} | size number | stacktrace [depth] | vrf vrf-name [distribution |
match {global | ip-address mask}]}
Syntax Description disable Turns off event tracing for Cisco Express Forwarding IPv4 events.
distribution Logs events related to the distribution of Cisco Express Forwarding
Forwarding Information Base (FIB) tables to the line cards.
dump-file Specifies the file to which event trace messages are written from memory on
dump-file-name the networking device. The maximum length of the filename (path and
filename) is 100 characters, and the path can point to flash memory on the
networking device or to a TFTP or FTP server.
enable Turns on event tracing for Cisco Express Forwarding IPv4 events if it had
been enabled with the monitor event-trace cef command.
match Turns on event tracing for Cisco Express Forwarding IPv4 that matches
global events or events that match a specific network address.
global Specifies global events.
ip-address mask Specifies an IP address in A.B.C.D format and a subnet mask in A.B.C.D
format.
size number Sets the number of messages that can be written to memory for a single
instance of a trace. Range: 1 to 65536.
Note Some Cisco IOS software subsystem components set the size by
default. To display the size parameter, use the show monitor
event-trace cef parameters command.
When the number of event trace messages in memory exceeds the configured
size, new messages will begin to overwrite the older messages in the file.
stacktrace Enables the stack trace at tracepoints.
depth (Optional) Specifies the depth of the stack trace stored. Range: 1 to 16.
vrf vrf-name Turns on event tracing for a Cisco Express Forwarding IPv4 Virtual Private
Network (VPN) routing and forwarding (VRF) table. The vrf-name argument
specifies the name of the VRF.
Command Default Event tracing for Cisco Express Forwarding IPv4 events is enabled by default.
Usage Guidelines Use the monitor event-trace cef ipv4 command to enable or disable event tracing for Cisco Express
Forwarding IPv4 events.
The Cisco IOS software allows Cisco Express Forwarding to define whether support for event tracing is
enabled or disabled by default. The command interface for event tracing allows you to change the default
value in one of two ways: using the monitor event-trace cef ipv4 command in privileged EXEC mode
or using the monitor event-trace cef ipv4 command in global configuration mode.
Note The amount of data collected from the trace depends on the trace message size configured using the
monitor event-trace cef ipv4 command for each instance of a trace.
To determine whether event tracing is enabled by default for Cisco Express Forwarding, use the show
monitor event-trace cef ipv4 command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer.
Examples The following example shows how to enable event tracing for Cisco Express Forwarding IPv4 events
and configure the buffer size to 5000 messages:
Router(config)# monitor event-trace cef ipv4 enable
The following example shows how to enable event tracing for events that match Cisco Express
Forwarding IPv4 VRF vpn1:
monitor event-trace cef ipv6 {disable | distribution | dump-file dump-file-name | enable | match
{global | ipv6-address/n} | size number | stacktrace [depth] | vrf vrf-name [distribution |
match {global | ipv6-address/n}]}
Syntax Description disable Turns off event tracing for Cisco Express Forwarding IPv6 events.
distribution Logs events related to the distribution of Cisco Express Forwarding
Forwarding Information Base (FIB) tables to the line cards.
dump-file Specifies the file to which event trace messages are written from memory on
dump-file-name the networking device. The maximum length of the filename (path and
filename) is 100 characters, and the path can point to flash memory on the
networking device or to a TFTP or FTP server.
enable Turns on event tracing for Cisco Express Forwarding IPv6 events if it had
been enabled with the monitor event-trace cef ipv6 command.
match Turns on event tracing for Cisco Express Forwarding IPv6 that matches
global events or events that match a specific network address.
global Specifies global events.
ipv6-address/n Specifies an IPv6 address. This address must be in the form documented in
RFC 2373: the address is specified in hexadecimals using 16-bit values
between colons. The slash followed by a number (/n) indicates the number of
bits that do not change. Range: 0 to 128.
size number Sets the number of messages that can be written to memory for a single
instance of a trace. Range: 1 to 65536.
Note Some Cisco IOS software subsystem components set the size by
default. To display the size parameter, use the show monitor
event-trace cef parameters command.
When the number of event trace messages in memory exceeds the configured
size, new messages will begin to overwrite the older messages in the file.
stacktrace Enables the stack trace at tracepoints.
depth (Optional) Specifies the depth of the stack trace stored. Range: 1 to 16.
vrf vrf-name Turns on event tracing for a Cisco Express Forwarding IPv6 Virtual Private
Network (VPN) routing and forwarding (VRF) table. The vrf-name argument
specifies the name of the VRF.
Command Default Event tracing for Cisco Express Forwarding IPv6 events is enabled by default.
Usage Guidelines Use the monitor event-trace cef ipv6 command to enable or disable event tracing for Cisco Express
Forwarding IPv6 events.
The Cisco IOS software allows Cisco Express Forwarding to define whether support for event tracing is
enabled or disabled by default. The command interface for event tracing allows you to change the default
value in one of two ways: using the monitor event-trace cef ipv6 command in privileged EXEC mode
or using the monitor event-trace cef ipv6 command in global configuration mode.
Note The amount of data collected from the trace depends on the trace message size configured using the
monitor event-trace cef ipv6 command for each instance of a trace.
To determine whether event tracing is enabled by default for Cisco Express Forwarding IPv6 events, use
the show monitor event-trace cef ipv6 command to display trace messages.
To specify the trace call stack at tracepoints, you must first clear the trace buffer.
Examples The following example shows how to enable event tracing for Cisco Express Forwarding IPv6 events
and configure the buffer size to 10000 messages.
Router(config)# monitor event-trace cef ipv6 enable
show adjacency
To display information about the Cisco Express Forwarding adjacency table or the hardware
Layer 3-switching adjacency table, use the show adjacency command in user EXEC or privileged
EXEC mode.
Usage Guidelines The show adjacency command is used to verify that an adjacency exists for a connected device, that the
adjacency is valid, and that the MAC header rewrite string is correct.
For line cards, you must specify the line card if_number (interface number). Use the show cef interface
command to obtain line card if_numbers.
You can use any combination of the ip-address, interface-type, and other keywords and arguments (in
any order) as a filter to display a specific subset of adjacencies.
On Cisco 7600 series routers, hardware Layer 3-switching adjacency statistics are updated every
60 seconds.
Note On the Cisco 10000 series routers, Pv6 is supported on Cisco IOS Release 12.2(28)SB or later releases.
The following example shows how to display adjacency information for a specific interface:
Router# show adjacency fastethernet 0/0
AABBCC019002AABBCC012C0286DD
IPv6 ND never
Epoch: 0
Field Description
Protocol Type of Internet protocol.
Interface Outgoing interface.
Address Next hop IP address.
The following examples show how to display protocol detail and timer information:
000500506C08000500509C080800
ARP
The following examples show how to display protocol detail and timer adjacency information for IP
links for a specific interface:
show cef
To display information about packets forwarded by Cisco Express Forwarding, use the show cef
command in privileged EXEC mode.
show cef {accounting | background [detail] | broker broker-name [detail] | error | fib |
hardware vectors | idb | loadinfo | non-ip | nsf | path [list [walk] | sets [detail | id path-set-id
| summary] | switching background [detail] | walks [process | queue]}
Usage Guidelines Use this command to display and monitor information about traffic forwarded by Cisco Express
Forwarding.
A line card might drop packets because of encapsulation failure, absence of route information, or
absence of adjacency information.
A packet is punted (sent to another switch path) because Cisco Express Forwarding may not support a
specified encapsulation or feature, the packet may be destined for the router, or the packet may have IP
options (such as time stamp and record route). IP options are process switched.
Examples The following example shows how to display Cisco Express Forwarding accounting information:
Router# show cef accounting
Field Description
Enabled accounting Type or types of Cisco Express Forwarding accounting that are
enabled: load-balance-hash, non-recursive, per-prefix,
prefix-length, or none.
per-prefix Indicates that Cisco Express Forwarding accounting is enabled
for the collection of the number of packets and bytes
express-forwarded to a destination (or prefix).
non-recursive Indicates that Cisco Express Forwarding accounting is enabled
through nonrecursive prefixes.
prefix-length Indicates that Cisco Express Forwarding accounting is enabled
through prefix length.
The following example shows how to display Cisco Express Forwarding background information:
Router# show cef background
Field Description
boolean The background process is waiting for a true or false flag to be
set.
FIB malloc failed, 0 occurences No instances of memory allocation failure have occurred for the
FIB.
FIB assert failed, 0 occurences No instances of assertion failure have occurred for the FIB.
FIB hw_api_failure failed; 0 No failures are reported during the programming of hardware
occurences forwarding.
timer The background process is waiting for a timer to be triggered.
Once the timer is triggered, the operation begins. In the FIB
checkers cases that follow, the timer is linked to Cisco Express
Forwarding consistency checkers.
FIB checkers: auto-repair delay, init, FIB auto repair timer is initialized, but the timer is not running
!run, 0 occurences and has not been running (0 occurences).
FIB checkers: IPv4 scan-rib-ios FIB IPv4 scan-rib-ios timer is initialized and running. The
scanner, init, !run, 2 occurences timer has been triggered twice.
Field Description
FIB checkers: IPv4 scan-ios-rib FIB IPv4 scan-ios-rib timer is initialized and running. The
scanner, init, run, 2 occurences timer has been triggered twice.
FIB table: rate monitor, init, run, 0 FIB table rate monitor timer is initialized and running, but has
occurences yet to be triggered.
The following example shows how to display information about Cisco Express Forwarding FIB entries:
Router# show cef fib
Field Description
9 allocated IPv4 entries, 0 failed Number of successfully allocated and failed IPv4 entries.
allocations
1 allocated IPv6 entry, 0 failed allocations Number of successfully allocated and failed IPv6 entries.
The following example shows how to display information about Cisco Express Forwarding loadinfo:
Router# show cef loadinfo
Field Description
0 allocated loadinfos, 0 failed Number of successfully allocated and failed allocated
allocations loadinfos.
0 allocated loadinfo hash usage gsbs Number of allocated subblocks for per-hash bucket accounting
when load balancing is used.
0 inplace modifies (enabled) In-place modification is enabled. No in-place modifications
have occurred.
0 identical modifies Number of in-place modifications that were skipped because
the replacement was identical to the target.
The following example shows how to display information for Cisco Express Forwarding paths:
Router# show cef path
Field Definition
28 allocated IPv4 paths Number of successfully allocated and failed IPv4 paths.
4 allocated IPv6 paths Number of successfully allocated and failed IPv4 paths.
32 Total Paths, 587 Recursive Paths, Information on all Cisco Express Forwarding paths.
0 Unresolved Paths
The following example shows how to display information about Cisco Express Forwarding background
switching processes:
Router# show cef switching background
Field Description
0 events awaiting registration on Number of events waiting to be registered on the background
background process process.
1 event registered on background Number of events registered on the background process.
process
boolean OCE unlock queue, 0 Number of output chain element (OCE) unlock queue events.
occurences
The following example shows how to display information about Cisco Express Forwarding:
Router# show cef walks
Calling process:
----------------
started
mode / priority low high very high
sync 3 0 0
atomic 0 0 0
finished
mode / priority low high very high
sync 3 0 0
atomic 0 0 0
restarted
mode / priority low high very high
sync 0 0 0
atomic 0 0 0
started
mode / priority low high very high
sync 0 0 0
atomic 0 0 0
finished
mode / priority low high very high
sync 0 0 0
atomic 0 0 0
Field Description
mode Indicates the mode of the Cisco Express Forwarding infrastructure walk:
syncThe walk takes place in the current process context and completes
before the start function returns. Other processes are allowed to run.
atomicThe walk takes place in the current process context and completes
before the start function returns. No other processes are allowed to run.
priority Indicate the priority of the infrastructure walk: low, medium, or high.
To display a list of which packets each line card dropped, use the show cef drop command in user EXEC
or privileged EXEC mode.
Usage Guidelines A line card might drop packets because of encapsulation failure, absence of route information, or
absence of adjacency information.
A packet is sent to a different switching path (punted) because Cisco Express Forwarding does not
support the encapsulation or feature, the packet is destined for the router, or the packet has IP options,
such as time stamp and record route. IP options are process switched.
Note If Cisco Express Forwarding for IPv6 or distributed Cisco Express Forwarding for IPv6 is enabled
globally on the router, the show cef drop command displays IPv6 Cisco Express Forwarding counter
information and IPv4 Cisco Express Forwarding counter information. If Cisco Express Forwarding for
IPv6 or distributed Cisco Express Forwarding for IPv6 is not enabled globally on the router, the
command displays only IPv4 Cisco Express Forwarding counter information.
Examples The following is sample output from the show cef drop command:
Router# show cef drop
Field Description
Slot The slot number on which the packets were received.
Encap_fail Indicates the number of packets dropped after exceeding the limit for
packets punted to the processor due to missing adjacency information
(Cisco Express Forwarding throttles packets passed up to the process
level at a rate of one packet every two seconds).
Unresolved Indicates the number of packets dropped due to an unresolved prefix
in the Forwarding Information Base (FIB) table.
Unsupported Indicates the number of packets fast-dropped by Cisco Express
Forwarding (drop adjacency).
No_route Indicates the number of packets dropped due to a missing prefix in
the FIB table.
No_adj Indicates the number of packets dropped due to incomplete
adjacency.
ChksumErr Indicates the number of IPv4 packets received with a checksum error.
Note This field is not supported for IPv6 packets.
To display a list of events internal to the Cisco Express Forwarding process, use the show cef events
command in user EXEC or privileged EXEC mode.
Examples The following is sample output from the show cef events command:
Router# show cef events
Field Description
Time Time that the event occurred.
Event Type of event that occurred.
Details Detailed description of the event.
Usage Guidelines This command is used to determine if Cisco Express Forwarding is enabled for all interfaces.
Examples The following is sample output from the show cef features global command:
Router# show cef features global
Field Description
Input FNF Flexible NetFlow (FNF) feature.
SPD Classify Flexible NetFlow (FNF) feature.
This output shows the global drop feature, Flexible NetFlow (Input FNF), and two global punt features,
Input FNF and SPD Classify. SPD Classify is present by default. The punt features are invoked for all
punted packets regardless of the interface upon which they are received.
show cef interface [type number] [statistics | detail | internal | brief | policy-statistics [input |
output]]
Release Modification
12.3(4)T The input and output keywords were added.
The display output was modified to include support for Cisco Express Forwarding
for IPv6 and distributed Cisco Express Forwarding interface information. Output
fields that support BGP policy accounting were added for the Cisco 7200 series and
Cisco 7500 series platforms.
12.2(14)S This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(25)S The internal keyword was added.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines You can use this command to display the detailed Cisco Express Forwarding status for all interfaces.
Values entered for the type and number arguments display Cisco Express Forwarding status information
for the specified interface type and number.
The policy-statistics, input, and output keywords are available only on distributed switching platforms.
Examples The following example shows how to display a summary of Cisco Express Forwarding information for
an interface named Ethernet 3/0:
Router# show cef interface ethernet 3/0 brief
The following is sample output from the show cef interface command for Fast Ethernet interface 1/0/0
with BGP policy accounting configured for input traffic:
Router# show cef interface fastethernet 1/0/0
FastEthernet1/0/0 is up (if_number 6)
Corresponding hwidb fast_if_number 6
Corresponding hwidb firstsw->if_number 6
Internet address is 10.1.1.1/24
ICMP redirects are always sent
Per packet load-sharing is disabled
IP unicast RPF check is disabled
Inbound access list is not set
Outbound access list is not set
IP policy routing is disabled
BGP based policy accounting on input is enabled
BGP based policy accounting on output is disabled
Hardware idb is FastEthernet1/0/0 (6)
Software idb is FastEthernet1/0/0 (6)
Fast switching type 1, interface type 18
IP Distributed CEF switching enabled
IP Feature Fast switching turbo vector
IP Feature CEF switching turbo vector
Input fast flags 0x100, Output fast flags 0x0, Flags 0x0
ifindex 7(7)
Slot 1 Slot unit 0 VC -1
Transmit limit accumulator 0xE8001A82 (0xE8001A82)
IP MTU 1500
The following is sample output from the show cef interface detail command for Ethernet
interface 1/0/0:
Router# show cef interface ethernet 1/0/0 detail
FastEthernet1/0/0 is up (if_number 6)
Corresponding hwidb fast_if_number 6
Corresponding hwidb firstsw->if_number 6
Internet address is 10.1.1.1/24
ICMP redirects are always sent
Per packet load-sharing is disabled
IP unicast RPF check is disabled
Inbound access list is not set
Outbound access list is not set
IP policy routing is disabled
BGP based policy accounting on input is enabled
BGP based policy accounting on output is disabled
Hardware idb is FastEthernet1/0/0 (6)
Software idb is FastEthernet1/0/0 (6)
Fast switching type 1, interface type 18
IP Distributed CEF switching enabled
IP Feature Fast switching turbo vector
IP Feature CEF switching turbo vector
Input fast flags 0x100, Output fast flags 0x0, Flags 0x0
ifindex 7(7)
Slot 1 Slot unit 0 VC -1
Transmit limit accumulator 0xE8001A82 (0xE8001A82)
IP MTU 1500
The following is sample output from the show cef interface Null 0 detail command:
Router# show cef interface null 0 detail
Null0 is up (if_number 1)
Corresponding hwidb fast_if_number 1
Corresponding hwidb firstsw->if_number 1
Internet Protocol processing disabled
Interface is marked as nullidb
Packets switched to this interface on linecard are dropped to next slow path
Hardware idb is Null0
Fast switching type 13, interface type 0
IP CEF switching enabled
IP Feature CEF switching turbo vector
Input fast flags 0x0, Output fast flags 0x0
ifindex 0(0)
Slot -1 Slot unit -1 VC -1
Transmit limit accumulator 0x0 (0x0)
IP MTU 1500
The following is sample output for internal Cisco Express Forwarding interface status and configuration
for the Ethernet 3/1 interface:
Router# show cef interface ethernet 3/1 internal
Field Description
FastEthernet1/0/0 is up Indicates type, number, and status of the interface.
Internet address is Internet address of the interface.
ICMP redirects are always sent Indicates how packet forwarding is configured.
Per packet load-sharing is disabled Indicates status of load sharing on the interface.
IP unicast RPF check is disabled Indicates status of IP unicast Reverse Path
Forwarding (RPF) check on the interface.
Inbound access list is not set Indicates the number or name of the inbound access
list if one is applied to this interface. Also indicates
whether the list is set.
Outbound access list is not set Indicates the number or name of the outbound
access list if one is applied to this interface. Also
indicates whether the list is set.
IP policy routing is disabled Indicates the status of IP policy routing on the
interface.
BGP based policy accounting on input is enabled Indicates the status of BGP policy accounting on
the input interface.
BGP based policy accounting on output is Indicates the status of BGP policy accounting on
disabled the output interface.
Hardware idb is Ethernet1/0/0 Interface type and number configured.
Field Description
Fast switching type Used for troubleshooting; indicates switching
mode in use.
Interface type Indicates interface type.
IP Distributed CEF switching enabled Indicates whether distributed Cisco Express
Forwarding is enabled on this interface.
(Cisco 7500 and 12000 series Internet routers
only.)
IP Feature Fast switching turbo vector Indicates IP fast switching type configured.
IP Feature CEF switching turbo vector Indicates IP feature Cisco Express Forwarding
switching type configured.
Input fast flags Indicates the input status of various switching
features:
0x0001 (input Access Control List [ACL]
enabled)
0x0002 (policy routing enabled)
0x0004 (input rate limiting)
0x0008 (MAC/Prec accounting)
0x0010 (DSCP/PREC/QOS GROUP)
0x0020 (input named access lists)
0x0040 (NAT enabled on input)
0x0080 (crypto map on input)
0x0100 (QPPB classification)
0x0200 (inspect on input)
0x0400 (input classification)
0x0800 (1casa input enable)
0x1000 (Virtual Private Network [VPN]
enabled on a 2swidb)
0x2000 (input idle timer enabled)
0x4000 (unicast Reverse Path Forwarding
[RPF] check)
0x8000 (per-address ACL enabled)
0x10000 (deaggregating a packet)
0x20000 (3GPRS enabled on input)
0x40000 (URL RenDezvous)
0x80000 (QoS classification)
0x100000 (FR switching on interface)
0x200000 ( 4WCCP redirect on input)
0x400000 (input classification)
Field Description
Output fast flags Indicates the output status of various switching
features, as follows:
0x0001 (output ACL enabled)
0x0002 (IP accounting enabled)
0x0004 (WCC redirect enabled interface)
0x0008 (rate limiting)
0x0010 (MAC/Prec accounting)
0x0020 (DSCP/PREC/QOS GROUP)
0x0040 (D-QOS classification)
0x0080 (output named access lists)
0x0100 (NAT enabled on output)
0x0200 (TCP intercept enabled)
0x0400 (crypto map set on output)
0x0800 (output firewall)
0x1000 (5RSVP classification)
0x2000 (inspect on output)
0x4000 (QoS classification)
0x8000 (QoS preclassification)
0x10000 (output stile)
ifindex 7/(7) Indicates a Cisco IOS internal index or identifier
for this interface.
Slot 1 Slot unit 0 VC -1 The slot number and slot unit.
Transmit limit accumulator Indicates the maximum number of packets allowed
in the transmit queue.
IP MTU The MTU size set on the interface.
1. Cisco applications and services architecture (CASA)
2. Software interface descriptor block (SWIDB)
3. General packet radio system (GPRS)
4. Web cache communication protocol (WCCP)
5. Resource reservation protocol (RSVP)
The following is sample output from the show cef interface command using the policy-statistics
keyword:
Router# show cef interface policy-statistics
POS7/0 is up (if_number 8)
Index Packets Bytes
1 0 0
2 0 0
3 50 5000
4 100 10000
5 100 10000
6 10 1000
7 0 0
8 0 0
The following is sample output from the show cef interface command using the policy-statistics
keyword. It shows policy statistics for Ethernet interface 1/0.
Router# show cef interface ethernet 1/0 policy-statistics
Ethernet1/0 is up (if_number 3)
Corresponding hwidb fast_if_number 3
Corresponding hwidb firstsw->if_number 3
Index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
The following is sample output from the show cef interface command using the policy-statistics
keyword. It shows policy statistics for Fast Ethernet interface 1/0/0 with the policy accounting based on
input traffic.
Router# show cef interface fastethernet 1/0/0 policy-statistics input
FastEthernet1/0/0 is up (if_number 6)
Corresponding hwidb fast_if_number 6
Corresponding hwidb firstsw->if_number 6
BGP based Policy accounting on input is enabled
Index Packets Bytes
1 9999 999900
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
11 0 0
12 0 0
13 0 0
14 0 0
15 0 0
16 0 0
17 0 0
18 0 0
19 0 0
20 0 0
21 0 0
22 0 0
23 0 0
24 0 0
25 0 0
26 0 0
27 0 0
28 0 0
29 0 0
30 0 0
31 0 0
32 0 0
33 0 0
34 1234 123400
35 0 0
36 0 0
37 0 0
38 0 0
39 0 0
40 0 0
41 0 0
42 0 0
43 0 0
44 0 0
45 1000 100000
46 0 0
47 0 0
48 0 0
49 0 0
50 0 0
51 0 0
52 0 0
53 0 0
54 5123 1198782
The following is sample output from the show cef interface command using the policy-statistics
keyword. It shows policy statistics for serial interface 1/1/2 with the policy accounting based on output
traffic.
Router# show cef interface serial 1/1/2 policy-statistics output
Serial1/1/2 is up (if_number 9)
Corresponding hwidb fast_if_number 9
Corresponding hwidb firstsw->if_number 9
BGP based Policy accounting on output is enabled
Index Packets Bytes
1 9999 999900
2 0 0
.
.
.
18 0 0
19 0 0
20 0 0
.
.
.
34 1234 123400
35 0 0
.
.
.
44 0 0
45 1000 100000
46 0 0
47 0 0
48 0 0
49 0 0
50 0 0
51 0 0
52 0 0
53 0 0
54 5123 1198782
55 0 0
56 0 0
57 0 0
58 0 0
59 0 0
60 0 0
61 0 0
62 0 0
63 0 0
64 0 0
Field Description
Index Traffic index set with the route-map command.
Packets Number of packets switched that match the index definition.
Bytes Number of bytes switched that match the index definition.
Syntax Description type number (Optional) Interface type and number. A space is not required
between the interface type and number.
input (Optional) Displays Border Gateway Protocol (BGP) policy
accounting statistics for traffic that is traveling through an input
interface.
output (Optional) Displays BGP policy accounting statistics for traffic that
is traveling through an output interface.
Command Default By default, this command displays the input statistics only.
Usage Guidelines This command is available on all software switching platforms, such as the Cisco 7200 series router, and
distributed switched platforms, such as the Route Switch Processor (RSP), Gigabit Switch Router
(GSR), and the Catalyst 6000 series router.
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Two sets of counters are displayed for BGP policy accounting: input counters and output counters. If you
enter the show cef interface policy-statistics command without an optional keyword, the command
displays only input counters. If you want to display the output counters, you must enter the command
with the output keyword. You can also display the input counters by entering the input keyword with
the command.
The number of lines in the output of the show cef interface policy-statistics command varies from
platform to platform. The software switched platforms support 64 input and 64 output counters and thus
64 lines of output. The Catalyst 6000 family switches and Cisco 7600 series routers support seven input
and seven output counters and seven lines of output.
You enable BGP policy accounting on a particular interface when you enter the bgp-policy accounting
command in interface configuration mode. To define the conditions for BGP policy accounting, you use
the set traffic-index command in route-map configuration mode, the route-map command in global
configuration mode, the table-map command in route-map configuration mode, and the match
command in route-map configuration mode. The table-map command adds the named route map to the
BGP routing table. BGP uses the route map name to set traffic indexes for routes in the IP routing table.
The match commands specify the match criteriathe conditions under which policy routing occurs. The
set traffic-index command sets the traffic indexes for matching prefixes. The show ip cef detail
command displays the traffic index for any particular route.
Examples The following is sample output from the show cef interface policy-statistics command:
Router# show cef interface policy-statistics
POS7/0 is up (if_number 8)
Index Packets Bytes
1 0 0
2 0 0
3 50 5000
4 100 10000
5 100 10000
6 10 1000
7 0 0
8 0 0
The following is sample output from the show cef interface policy-statistics command showing policy
statistics for Ethernet interface 1/0:
Router# show cef interface ethernet 1/0 policy-statistics
Ethernet1/0 is up (if_number 3)
Corresponding hwidb fast_if_number 3
Corresponding hwidb firstsw->if_number 3
Index Packets Bytes
1 0 0
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
The following is sample output from the show cef interface policy-statistics command showing policy
statistics for Fast Ethernet interface 1/0/0 with the policy accounting based on input traffic:
Router# show cef interface fastethernet 1/0/0 policy-statistics input
FastEthernet1/0/0 is up (if_number 6)
Corresponding hwidb fast_if_number 6
Corresponding hwidb firstsw->if_number 6
BGP based Policy accounting on input is enabled
Index Packets Bytes
1 9999 999900
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
11 0 0
12 0 0
13 0 0
14 0 0
15 0 0
16 0 0
17 0 0
18 0 0
19 0 0
20 0 0
21 0 0
22 0 0
23 0 0
24 0 0
25 0 0
26 0 0
27 0 0
28 0 0
29 0 0
30 0 0
31 0 0
32 0 0
33 0 0
34 1234 123400
35 0 0
36 0 0
37 0 0
38 0 0
39 0 0
40 0 0
41 0 0
42 0 0
43 0 0
44 0 0
45 1000 100000
46 0 0
47 0 0
48 0 0
49 0 0
50 0 0
51 0 0
52 0 0
53 0 0
54 5123 1198782
55 0 0
56 0 0
57 0 0
58 0 0
59 0 0
60 0 0
61 0 0
62 0 0
63 0 0
64 0 0
The following is sample output from the show cef interface policy-statistics command showing policy
statistics for serial interface 1/1/2 with the policy accounting based on output traffic:
Router# show cef interface serial 1/1/2 policy-statistics output
Serial1/1/2 is up (if_number 9)
Corresponding hwidb fast_if_number 9
Corresponding hwidb firstsw->if_number 9
BGP based Policy accounting on output is enabled
Index Packets Bytes
1 9999 999900
2 0 0
3 0 0
4 0 0
5 0 0
6 0 0
7 0 0
8 0 0
9 0 0
10 0 0
11 0 0
12 0 0
13 0 0
14 0 0
15 0 0
16 0 0
17 0 0
18 0 0
19 0 0
20 0 0
21 0 0
22 0 0
23 0 0
24 0 0
25 0 0
26 0 0
27 0 0
28 0 0
29 0 0
30 0 0
31 0 0
32 0 0
33 0 0
34 1234 123400
35 0 0
36 0 0
37 0 0
38 0 0
39 0 0
40 0 0
41 0 0
42 0 0
43 0 0
44 0 0
45 1000 100000
46 0 0
47 0 0
48 0 0
49 0 0
50 0 0
51 0 0
52 0 0
53 0 0
54 5123 1198782
55 0 0
56 0 0
57 0 0
58 0 0
59 0 0
60 0 0
61 0 0
62 0 0
63 0 0
64 0 0
Field Description
Index Traffic index set with the route-map command.
Packets Number of packets switched that match the index definition.
Bytes Number of bytes switched that match the index definition.
Syntax Description slot-number (Optional) Slot number for the line card about which to display
Cisco Express Forwarding-related information. When you omit this
argument, information about all line cards is displayed.
detail (Optional) Displays detailed Cisco Express Forwarding information
for the specified line card.
internal (Optional) Displays internal Cisco Express Forwarding information
for the specified line card.
Examples The following is sample output from the show cef linecard command. The command displays
information for all line cards in table format.
Router# show cef linecard
The following is sample output from the show cef linecard detail command for all line cards:
Router# show cef linecard detail
The following is sample output from the show cef linecard internal command for all line cards:
Router# show cef linecard internal
table 2
time 4484
flow features deactivate 2
flow cache config 2
flow export config 2
dss 2
isl 2
mpls atm vc remove 2
mpls atm vc set label 2
2
2
3
1
4574 elements packed in 4495 messages(90286 bytes) sent
115 elements cleared
Total elements cleared:
prefix 2
adjacency 1
interface 63
address 1
policy routing 1
hw interface 29
state 2
control 5
table 1
flow features deactivate 1
flow cache config 1
flow export config 1
dss 1
isl 1
mpls atm vc remove 1
mpls atm vc set label 1
1
1
1
linecard disabled - failed a reload
0/0/0 xdr elements in LowQ/MediumQ/HighQ
Input packets 0, bytes 0
Output packets 0, bytes 0, drops 0
Field Description
Table name Name of the Cisco Express Forwarding table.
Version Number of the Forwarding Information Base (FIB) table version.
Prefix-xdr Number of prefix IPC information elements external data
representation (XDRs) processed.
Status State of the Cisco Express Forwarding table.
Slot Slot number of the line card.
MsgSent Number of interprocess communications (IPC) messages sent.
XDRSent XDRs packed into IPC messages sent from the Route Processor (RP)
to the line card.
Field Description
Window Size of the IPC window between the line card and the RP.
LowQ/MedQ/HighQ Number of XDR elements in the Low, Medium, and High priority
queues.
Flags Indicates the status of the line card. States are:
upLine card is up.
syncLine card is in synchronization with the main FIB.
FIB is repopulated on the line card.
resetLine card FIB is reset.
reloadingLine card FIB is being reloaded.
disabledLine card is disabled.
CEF-XDR Number of Cisco Express Forwarding XDR messages processed.
I/Fs Interface numbers.
Syntax Description changes Displays Cisco Express Forwarding memory usage changes since the last
snapshot.
chunk-utilisation Displays Cisco Express Forwarding chunk memory utilization.
summary Displays a summary of Cisco Express Forwarding memory usage.
snapshot Displays Cisco Express Forwarding memory information and takes a
snapshot.
Usage Guidelines Use this command to monitor the memory usage of Cisco Express Forwarding processes. You can
display a summary of Cisco Express Forwarding memory usage, display a snapshot of memory use, and
display changes to memory use since the last snapshot was taken.
Examples The following is sample output from the show cef memory command:
Router# show cef memory
Field Description
Memory The type of Cisco Express Forwarding process that is using memory.
in use/allocated Number of bytes in use by Cisco Express Forwarding and the number of
bytes allocated for use by Cisco Express Forwarding.
Count Number of blocks in use.
ADJ Indicates a Cisco Express Forwarding adjacency process.
CEF Indicates a Cisco Express Forwarding process.
The following is sample output from the show cef memory summary command:
Router# show cef memory summary
This example shows that Cisco Express Forwarding allocated 502888 bytes of memory. The difference
between the amount of memory in use and the amount of memory allocated is 7904 bytes.
The following is sample output from the show cef memory snapshot command:
Router# show cef memory snapshot
This example shows when you last took a snapshot of Cisco Express Forwarding memory.
The following is sample output from the show cef memory changes command:
Router# show cef memory changes
This examples shows the Cisco Express Forwarding memory changes, if any, that have occurred since
the last memory snapshot was taken.
To display which packets were sent to a different switching path, use the show cef not-cef-switched
command in user EXEC or privileged EXEC mode.
Usage Guidelines If packets are not being cef switched and you want to determine why, enter the show cef not-cef
switched command.
Note If Cisco Express Forwarding for IPv6 or distributed Cisco Express Forwarding for IPv6 is enabled
globally on the router, the show cef not-cef-switched command displays IPv6 Cisco Express
Forwarding counter information and IPv4 Cisco Express Forwarding counter information. If Cisco
Express Forwarding for IPv6 or distributed Cisco Express Forwarding for IPv6 is not enabled globally
on the router, the command displays only IPv4 Cisco Express Forwarding counter information.
Examples The following is sample output from the show cef not-cef-switched command:
Router# show cef not-cef-switched
Field Meaning
Slot The slot number on which the packets were received.
No_adj Indicates the number of packets sent to the processor due to
incomplete adjacency.
No_encap Indicates the number of packets sent to the processor for Address
Resolution Protocol (ARP) resolution.
Unsuppted Indicates the number of packets punted to the next switching level
due to unsupported features.
Redirect Records packets that are ultimately destined to the router, and
packets destined to a tunnel endpoint on the router. If the
decapsulated tunnel is IP, it is Cisco Express Forwarding switched;
otherwise, packets are process switched.
Receive Indicates the number of packets ultimately destined to the router, or
packets destined to a tunnel endpoint on the router. If the
decapsulated tunnel packet is IP, the packet is Cisco Express
Forwarding switched. Otherwise, packets are process switched.
Options Indicates the number of packets with options. Packets with IP options
are handled only at the process level.
Access Indicates the number of packets punted due to an access list failure.
Field Meaning
Frag Indicates the number of packets punted due to fragmentation failure.
Note This field is not supported for IPv6 packets.
MTU Indicates the number of packets punted due to maximum
transmission unit (MTU) failure.
Note This field is not supported for IPv4 packets.
Related
Commands Command Description
show cef drop Displays a list of which packets each line card dropped.
show cef interface Displays Cisco Express Forwarding-related interface information.
show ipv6 cef Displays entries in the IPv6 FIB.
Examples Example for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12,2(33)SRA, 12,2(33)SXH, 12.4(20T, and Later Releases
The following example shows the state of Cisco Express Forwarding on the active Route Processor (RP):
Router# show cef state
CEF Status:
RP instance
common CEF enabled
IPv4 CEF Status:
CEF enabled/running
dCEF disabled/not running
CEF switching enabled/running
universal per-destination load sharing algorithm, id A189DD49
IPv6 CEF Status:
CEF enabled/running
dCEF disabled/not running
original per-destination load sharing algorithm, id A189DD49
Field Description
RP instance Cisco Express Forwarding status is for the RP.
common CEF enabled Common Cisco Express Forwarding is enabled.
IPv4 CEF Status Cisco Express Forwarding mode and status is for IPv4.
universal per-destination load sharing IPv4 is using the universal per-destination load sharing
algorithm algorithm for Cisco Express Forwarding traffic.
IPv6 CEF Status Cisco Express Forwarding mode and status is for IPV6.
original per-destination load sharing IPv6 is using the original per-destination load sharing
algorithm algorithm for Cisco Express Forwarding traffic.
RRP state:
I am standby RRP: no
RF Peer Presence: yes
RF PeerComm reached: yes
Redundancy mode: SSO(7)
CEF NSF: enabled/running
Field Description
I am standby RRP: no This RP is not the standby.
RF Peer Presence: yes This RP does have RF peer presence.
RF PeerComm reached: yes This RP has reached RF peer communication.
Redundancy mode: SSO(&) Type of redundancy mode on this RP.
CEF NSF: enabled/running States whether Cisco Express Forwarding nonstop forwarding (NSF) is
running or not.
The following example shows the state of Cisco Express Forwarding on the standby RP:
Router# show cef state
RRP state:
I am standby RRP: yes
My logical slot: 0
RF Peer Presence: yes
RF PeerComm reached: yes
CEF NSF: running
Syntax Description all Displays all Cisco Express Forwarding clients that provide prefix subtree
context.
ip-session Displays Cisco Express Forwarding IP sessions that provide prefix subtree
context.
test Tests all Cisco Express Forwarding applications that provide prefix subtree
context.
Usage Guidelines
Note This command is for debugging purposes only. Do not use it unless instructed to do so by a Cisco service
engineer.
Examples The following example shows how to display information about all clients that provide subtree context:
Router# show cef subtree context client all
Field Description
FIB_SC: Test Identifies the name of the client. This is useful information for the
Cisco service engineer.
instances: 0 Number of instances of the subtree context.
app space: 0 Amount of extra space requested by the application for each instance
of the subtree context.
platform space: 0 Amount of extra space requested by the platform for each instance of
the subtree context.
show cef table [consistency-check | detail | internal | [ipv4 | ipv6] [vrf {* | Default | vrf-name}]
[topology {* | base | topology-name}] [detail | internal]]
show cef table [consistency-check | detail | internal | [ipv4 | ipv6] {Default | vrf-name} [detail |
internal]]
Syntax Description consistency-check (Optional) Displays the status of consistency checkers in the FIB.
detail (Optional) Displays detailed Cisco Express Forwarding operational status
and configuration.
internal (Optional) Displays internal Cisco Express Forwarding operational status
and configuration.
ipv4 (Optional) Displays operational status for IPv4 from the IPv4 FIB.
ipv6 (Optional) Displays operational status for IPv6 from the IPv6 FIB.
vrf (Optional) Specifies a Virtual Private Network (VPN) routing and
forwarding (VRF) instance for the specified address family.
* Displays operational status for all configured VRFs (vrf *) or all topologies
(topology *), respectively.
Default Displays operational status for the default VRF for the specified address
family.
vrf-name Displays operational status for the named VRF configured for the specified
address family.
topology (Optional) Specifies a topology for the selected address family.
base Displays operational status for the base topology for the specified address
family.
topology-name Displays operational status for the identified topology-specific table.
Usage Guidelines Use this command to display information about the configuration and operational statistics for
Cisco Express Forwarding IPv4 FIB and IPv6 FIB.
Examples The following is sample output from the show cef table command:
Router# show cef table
Global information:
Output chain build favors:
platform: not configured
CLI: not configured
operational: convergence-speed
Output chain build characteristics:
Inplace modify
operational for: load-sharing
Collapse
operational for: load-sharing
Indirection
operational for: recursive-prefix
MTRIE information:
TAL: node pools:
pool[C/8 bits]: 12 allocated (0 failed), 12480 bytes {1 refcount}
Field Description
Output chain build favors: Indicates table output chain building operational preferences.
Platform: not configured Output chain building characteristics are not explicitly set or
supported by the platform. The default output chain building
characteristics are used.
CLI: not configured Output chain building characteristics are not explicitly
configured. The default is used.
operational: convergence speed Output chain building favors convergence. This is the default
operational behavior.
Field Description
Output chain build characteristics Indicates the output chain building characteristics.
Inplace modify operational for: Indicates that the load sharing information in effect can be
load-sharing changed if the output information of the Interior Gateway
Protocol (IGP) changes.
Collapse operational for: load-sharing Indicates that the load-sharing tree is collapsed if load
balancing is not affected.
Indirection operational for: Indicates that the use of indirection objects is enabled for
recursive-prefix recursive prefixes.
MTRIE information: Indicates that information about the multi-array retrieval
(MTRIE) follows.
TAL: node pools: Indicates that node pool information for the Tree Abstraction
Layer (TAL) follows.
pool (C/8 bits): Indicates the memory management technique for the pool and
the stride size (8 bits). The C indicates the use of a chunk
pool. An M would indicate the use of a malloc.
The following is sample output from the show cef table internal command:
Router# show cef table internal
Subblocks:
Field Description
Table: IPv4: Default (id 0) The FIB table, IPv4 or IPv6, for which operation statistics
follow.
sources: Default table The source of the information comes from the Default table.
ref count: 3 The number of internal pointers to the VRF table structure.
flags (0x00): none No flags are configured.
smp allowed: yes Symmetrical Multi-Processing (SMP) is allowed.
default network: none A default network is not configured.
route count: 9 Total number of routes is 9.
route count (fwd): 9 The number of routes forwarded is 9.
route count (non-fwd): 0 The number of routes not forwarded is 0.
Database epoch: 0 (9 entries at this Epoch number (table version) is 0 and contains 9 entries.
epoch)
Subblocks: No subblocks are defined.
RIB update rate: 0 No update rate is configured for the RIB.
RIB update peak rate 0 No peak update rate is defined for the RIB.
Internal: Identification for Cisco Express Forwarding internal
operations.
The following is sample output from the show cef table consistency-check command:
Router# show cef table consistency-check
IPv4:
Table consistency checker state:
scan-rib-ios: disabled
0/0/0/0 queries sent/ignored/checked/iterated
scan-ios-rib: disabled
0/0/0/0 queries sent/ignored/checked/iterated
full-scan-rib-ios: enabled [1000 prefixes checked every 60s]
0/0/0/0 queries sent/ignored/checked/iterated
full-scan-ios-rib: enabled [1000 prefixes checked every 60s]
0/0/0/0 queries sent/ignored/checked/iterated
Checksum data checking disabled
IPv6:
Table consistency checker state:
scan-ios-rib: disabled
0/0/0/0 queries sent/ignored/checked/iterated
full-scan-rib-ios: enabled [1000 prefixes checked every 60s]
0/0/0/0 queries sent/ignored/checked/iterated
full-scan-ios-rib: enabled [1000 prefixes checked every 60s]
0/0/0/0 queries sent/ignored/checked/iterated
Checksum data checking disabled
Inconsistency error messages are disabled
Inconsistency auto-repair is enabled (10s delay, 300s holddown)
Inconsistency auto-repair runs: 0
Inconsistency statistics: 0 confirmed, 0/16 recorded
Field Description
scan-rib-ios: disabled The consistency checker that compares the Routing
Information Base (RIB) to the FIB table and provides the
number of entries missing from the FIB table is disabled.
scan-ios-rib: disabled The consistency checker that compares the FIB table to the
RIB and provides the number of entries missing from the RIB
is disabled.
full-scan-rib-ios: enabled A full scan is enabled that compares the RIB to the FIB table.
Every 60 seconds, 1000 prefixes are checked.
full-scan-ios-rib: enabled A full scan is enabled that compares the FIB table to the RIB.
Every 60 seconds, 1000 prefixes are checked.
Checksum data checking disabled The data-checking function is disabled.
Inconsistency error messages are The consistency checker to generate inconsistency error
disabled messages is disabled.
Inconsistency auto-repair is enabled The auto repair function is enabled with the default settings
(10s delay, 300s holddown) of a 10-second delay and a 300-second holddown.
The following is sample output from the show cef table IPv4 Default command:
Router# show cef table ipv4 Default
For a description of significant fields shown in the display, see Table 24.
The following is sample output from the show cef table IPv6 Default internal command:
Router# show cef table ipv6 Default internal
For a description of significant fields shown in the display, see Table 24.
Usage Guidelines Use this command to display the configured priority for Cisco Express Forwarding routes that are
downloaded from the Route Processor (RP) to the line cards.
You can change the default priority for a route type with the cef table download configuration
command. If you change the default priority for a route type, the show cef table download priority
command displays the user-configured priority followed by the default priority in parentheses.
Examples The following sample output shows the configured download priority of the routes and prefixes from the
Cisco Express Forwarding table on the RP to the line cards:
Router# show cef table download priority
This example shows that the default download priorities are in effect.
Table 26 describes the significant fields shown in the display.
Field Description
Route type Type of route in the Cisco Express Forwarding table downloaded from the
RP to the line cards.
priority Order in which the route type is downloaded from the RP to the line cards.
In the following example, the default priority of a default route and a receive route was changed with the
cef table download command:
Router# configure terminal
The following show cef table download priority command displays the newly configured download
priority and the default priority (in parentheses) for the default route and the receive route:
Router# show cef table download priority
See Table 26 for a description of the significant fields shown in the display.
Examples Example for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12,2(33)SRA, 12,2(33)SXH, 12.4(20)T, and Later Releases
The following is sample output from the show cef timer command:
Router# show cef timers
Field Description
Experation Seconds in which the timers will expire
Type Identification of the counter
Example for Cisco IOS Releases Before Cisco IOS Release 12.2(25)S
The following is sample output from the show cef timers command:
Router# show cef timers
Field Description
Expiration Seconds in which the timers will expire
Type Identification of the timer
Syntax Description ipv4 (Optional) Displays IPv4 address-family type VRF instances.
ipv6 (Optional) Displays IPv6 address-family type VRF instances.
Default (Optional) Default VRF for the specified address family.
vrf-name (Optional) Name assigned to a VRF.
Command Default If you do not specify any arguments or keywords, the command displays information about all VRFs in
the Cisco Express Forwarding Forwarding Information Base (FIB).
Usage Guidelines Use this command to display information about specified VRF instances or all VRF instances in the
Cisco Express Forwarding FIB. To display information about all VRF instances in the FIB, omit
arguments and keywords.
Examples The following is sample output from the show cef vrf command:
Router# show cef vrf
Field Description
AF: IPv4 The address-family type is IPv4.
VRF: Default (0) Identifies the default VRF.
AF: IPv6 The address-family type is IPv6.
The following is sample output from the show cef vrf ipv4 command:
Router# show cef vrf ipv4
The following is sample output from the show cef vrf ipv6 command:
Router# show cef vrf ipv6
Syntax Description type number Interface type and number about which to display statistics.
Note When fast switching is configured on the outbound interface, and RSP optimum, RSP flow, and VIP DFS
switching modes are all specified on the incoming interface, the interface on which RSP optimum, RSP
flow, and VIP DFS switching modes is not enabled can still show packets switched out via those
switching paths when packets are received from other interfaces with RSP optimum, RSP flow, and VIP
DES switching modes enabled.
Examples The following sample output is from Cisco IOS Release 12.3(14)YM2 and shows counters for both
Multi-Processor Forwarding (MPF) switched packets on native GigabitEthernet interfaces and for
non-MPF FastEthernet interfaces:
Router# show interface stats
GigabitEthernet0/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 0 0 225 77625
Route cache 0 0 0 0
Multi-Processor Fwding 950 221250 500 57000
Total 950 221250 725 134625
GigabitEthernet0/1
Switching path Pkts In Chars In Pkts Out Chars Out
Fddi3/0/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 3459994 1770812197 4141096 1982257456
Route cache 10372326 3693920448 439872 103743545
Distributed cache 19257912 1286172104 86887377 1184358085
Total 33090232 2455937453 91468345 3270359086
Field Description
Fddi3/0/0 Interface for which information is shown
Switching path Column heading for the various switching paths below it
Pkts In Number of packets received in each switching mechanism
Chars In Number of characters received in each switching mechanism
Pkts Out Number of packets sent out each switching mechanism
Chars Out Number of characters sent out each switching mechanism
Syntax Description type number Interface type and number about which to display packet switching path
information.
Usage Guidelines Use the show interfaces switching command to show which path the router uses and how the traffic is
switched. This command is also useful for troubleshooting CPU utilization.
Statistics for packets in, bytes in, packets out, and bytes out are displayed for the available protocols.
The statistics are arranged by process, cache misses, fast-path, and autonomous path. All values
displayed by the show interfaces switching command are absolute. The clear interface counters
command has no effect on these values.
You must enter at least seven characters of the switching keyword (switchi) when you use the show
interfaces switching command.
Examples The following shows sample output from the show interfaces switching command:
Router# show interfaces switching
FastEthernet0/0
Throttle count 0
Drops RP 0 SP 0
SPD Flushes Fast 0 SSE 0
SPD Aggress Fast 0
SPD Priority Inputs 0 Drops 0
Protocol IP
Switching path Pkts In Chars In Pkts Out Chars Out
Process 24 8208 0 0
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
Protocol DECnet
Switching path Pkts In Chars In Pkts Out Chars Out
Process 0 0 0 0
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
.........
........
Protocol IPv6
Switching path Pkts In Chars In Pkts Out Chars Out
Process 0 0 0 0
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
Protocol Other
Switching path Pkts In Chars In Pkts Out Chars Out
Process 2 120 3 180
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
NOTE: all counts are cumulative and reset only after a reload.
The following shows sample output from the show interfaces switching command for the interface
FastEthernet 0/0:
Router> show interfaces FastEthernet 0/0 switching
FastEthernet0/0
Throttle count 0
Drops RP 0 SP 0
SPD Flushes Fast 218 SSE 0
SPD Aggress Fast 0
SPD Priority Inputs 0 Drops 0
Protocol IP
Switching path Pkts In Chars In Pkts Out Chars Out
Process 239 23422 237 23226
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
Protocol ARP
Switching path Pkts In Chars In Pkts Out Chars Out
Process 4 240 3 180
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
Protocol CDP
Switching path Pkts In Chars In Pkts Out Chars Out
Process 8 2632 15 5477
Cache misses 0 - - -
Fast 0 0 0 0
Auton/SSE 0 0 0 0
NOTE: all counts are cumulative and reset only after a reload.
Field Description
Throttle count Number of times input packet processing was throttled on this interface.
Drops RPNumber of packets dropped for input congestion.
SPNumber of packets flushed by external throttling.
SPD Flushes FastNumber of packets flushed by selective packet discard on RP.
SSENumber of packets flushed by external selective packet discard.
SPD Aggress FastInput packets dropped by aggressive selective packet discard.
SPD Priority InputsNumber of priority packets received.
DropsNumber of priority packets dropped.
Protocol Name of the protocol for which packet switching information is displayed.
Switching Path Indicates the traffic switching path.
Pkts In Number of incoming packets.
Chars In Number of incoming bytes.
Pkts Out Number of outgoing packets.
Chars Out Number of outgoing bytes.
Process Process switching. With this type of switching, an incoming packet is associated
with a destination network or subnet entry in the routing table located in main
memory. Process switching is performed by the system processor.
Cache misses Packets that were forwarded through the process level (for which there was no
entry in fast switching cache).
Fast Fast switching. With this type of switching, an incoming packet matches an entry
in the fast-switching cache located in main memory. Fast switching is done via
asynchronous interrupts, which are handled in real time. Fast switching allows
higher throughput by switching a packet using a cache created by previous
packets.
Auton Autonomous switching. With this type of switching, an incoming packet matches
an entry in the autonomous-switching cache located on the interface processor.
Autonomous switching provides faster packet switching by allowing the ciscoBus
controller to switch packets independently without having to interrupt the system
processor. It is available only on Cisco 7000 series routers and in AGS+ systems
with high-speed network controller cards.
SSE Silicon switching engine switching. With this type of switching, an incoming
packet matches an entry in the silicon-switching cache located in the silicon
switching engine (SSE) of the Silicon Switch Processor (SSP) module. This
module is available only on Cisco 7000 series routers. Silicon switching provides
very fast, dedicated packet switching by allowing the SSE to switch packets
independently without having to interrupt the system processor.
show ip cache
To display the routing table cache used to fast switch IP traffic, use the show ip cache command in user
EXEC or privileged EXEC mode.
Syntax Description prefix mask (Optional) Displays only the entries in the cache that match the prefix and
mask combination.
type number (Optional) Displays only the entries in the cache that match the interface type
and number combination.
Usage Guidelines The show ip cache display shows MAC headers up to 92 bytes.
Examples The following is sample output from the show ip cache command:
Router# show ip cache
IP routing cache version 4490, 141 entries, 20772 bytes, 0 hash overflows
Minimum invalidation interval 2 seconds, maximum interval 5 seconds,
quiet interval 3 seconds, threshold 0 requests
Invalidation rate 0 in last 7 seconds, 0 in last 3 seconds
Last full cache invalidation occurred 0:06:31 ago
Field Description
IP routing cache version Version number of this table. This number is incremented any time
the table is flushed.
entries Number of valid entries.
bytes Number of bytes of processor memory for valid entries.
hash overflows Number of times autonomous switching cache overflowed.
Minimum invalidation interval Minimum time delay between cache invalidation request and actual
invalidation.
maximum interval Maximum time delay between cache invalidation request and actual
invalidation.
quiet interval Length of time between cache flush requests before the cache will
be flushed.
threshold <n> requests Maximum number of requests that can occur while the cache is
considered quiet.
Invalidation rate <n> in last Number of cache invalidations during the last <m> seconds.
<m> seconds
0 in last 3 seconds Number of cache invalidation requests during the last quiet interval.
Last full cache invalidation Time since last full cache invalidation was performed.
occurred <hh:mm:ss> ago
Prefix/Length Network reachability information for cache entry.
Age Age of cache entry.
Interface Output interface type and number.
MAC Header Layer 2 encapsulation information for cache entry.
The following is sample output from the show ip cache command with a prefix and mask specified:
Router# show ip cache 131.108.5.0 255.255.255.0
IP routing cache version 4490, 119 entries, 17464 bytes, 0 hash overflows
Minimum invalidation interval 2 seconds, maximum interval 5 seconds,
quiet interval 3 seconds, threshold 0 requests
Invalidation rate 0 in last second, 0 in last 3 seconds
Last full cache invalidation occurred 0:11:56 ago
The following is sample output from the show ip cache command with an interface specified:
Router# show ip cache e0/2
IP routing cache version 4490, 141 entries, 20772 bytes, 0 hash overflows
Minimum invalidation interval 2 seconds, maximum interval 5 seconds,
quiet interval 3 seconds, threshold 0 requests
Invalidation rate 0 in last second, 0 in last 3 seconds
Last full cache invalidation occurred 0:06:31 ago
show ip cef
To display entries in the Cisco Express Forwarding Forwarding Information Base (FIB) or to display a
summary of the FIB, use the show ip cef command in user EXEC or privileged EXEC mode.
Syntax Description network (Optional) Network number for which to display a FIB entry.
network-mask (Optional) Network mask to be used with the specified network
value.
network/mask (Optional) The network number assigned to the interface and the
length of the prefix.
longer-prefixes (Optional) Displays FIB entries for more specific destinations.
interface-type (Optional) Interface type. For more information, use the question
mark (?) online help function.
number (Optional) Interface or subinterface number. For more information
about the numbering syntax for your networking device, use the
question mark (?) online help function.
platform (Optional) Displays platform-specific data structure only.
detail (Optional) Displays detailed FIB entry information.
internal (Optional) Displays the FIB internal data structure. The internal
keyword is available in privileged EXEC mode only.
checksum (Optional) Displays FIB entry checksum values. The checksum
keyword is available in privileged EXEC mode only.
dependents (Optional) Displays all prefixes recursing through the FIB.
same-routing (Optional) Displays all prefixes with the same routing.
prefix-statistics (Optional) Displays nonzero prefix statistics.
Release Modification
12.0(5)T This command was integrated into Cisco IOS Release12.0(5)T.
12.0(17)ST This command was modified. The display of a message indicating support
for Border Gateway Protocol (BGP) policy accounting was added.
12.0(26)S This command was integrated into Cisco IOS Release 12.0(26)S.
12.2(25)S This command was modified. The checksum, internal, platform, and
prefix-statistics keywords were added. Output was changed to show IPv4
output only.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(24)T This command was modified. The dependents, longer-prefixes, and
same-routing keywords were added.
15.0(1)S This command was integrated into Cisco IOS Release 15.0(1)S.
Usage Guidelines Use of the show ip cef command without any keywords or arguments shows a brief display of all FIB
entries.
The show ip cef detail command shows detailed FIB entry information for all FIB entries.
Examples The following is sample output from the show ip cef detail command for Ethernet interface 0. It shows
all the prefixes resolving through adjacency pointing to next hop Ethernet interface 0/0 and next hop
interface IP address 192.0.2.233.
Router# show ip cef Ethernet 0/0 detail
Field Description
routes Total number of entries in the Cisco Express Forwarding table.
unresolved routes Number of entries in the Cisco Express Forwarding table that do not
have resolved recursions categorized by old and new routes.
leaves, nodes, bytes Number of elements in the Cisco Express Forwarding table and how
much memory they use.
inserts Number of nodes inserted.
Field Description
invalidations Number of entries that have been invalidated.
load sharing elements, Information about load sharing elements: how many, number of
bytes, references associated bytes, and number of associated references.
CEF resets Number of times the Cisco Express Forwarding table has reset.
revisions of existing leaves Number of revisions of the existing elements in the Cisco Express
refcounts Forwarding table.
version Version of the Cisco Express Forwarding table.
cached adjacency Type of adjacency to which this Cisco Express Forwarding table entry
points.
packets, bytes Number of packets and bytes switched through the name entry.
dependencies Number of table entries that point to the named entry.
next hop Type of adjacency or the next hop toward the destination.
The following is sample output from the show ip cef detail command for the prefix 192.0.2.1, showing
that the BGP policy accounting bucket number 4 (traffic_index 4) is assigned to this prefix:
Router# show ip cef 192.0.2.1 detail
show ip cef [vrf vrf-name] adjacency interface-type interface-number ip-prefix [checksum | detail
| epoch epoch-number | internal | platform | source]
show ip cef [vrf vrf-name] adjacency {discard | drop | glean | null | punt} [detail] [checksum |
detail | epoch epoch-number | internal | platform | source]
show ip cef [vrf vrf-name] adjacency interface-type interface-number ip-prefix [detail | internal |
platform]
Special Adjacency Types Representing Nonstandard Switching Paths (Cisco 10000 Series Routers)
show ip cef [vrf vrf-name] adjacency {discard | drop | glean | null | punt} [detail] [internal]
[platform]
Syntax Description vrf (Optional) Specifies a Virtual Private Network (VPN) routing and forwarding
(VRF) instance.
vrf-name (Optional) Name assigned to the VRF.
interface-type Interface type and number for which to display Forwarding Information Base
interface-number (FIB) entries.
ip-prefix Next-hop IP prefix, in dotted decimal format (A.B.C.D).
checksum (Optional) Displays FIB entry checksums.
detail (Optional) Displays detailed information for each Cisco Express Forwarding
adjacency type entry.
epoch (Optional) Displays adjacency type entries filtered by epoch number. The epoch
epoch-number number range is from 0 to 255.
internal (Optional) Displays data for adjacency type entries.
platform (Optional) Displays platform-specific adjacency information.
source (Optional) Displays source-specific adjacency information.
discard Discards adjacency. Sets up the adjacency for loopback interfaces. Loopback IP
addresses receive entries in the FIB table.
drop Drops the packets that are forwarded to this adjacency.
glean Represents destinations on a connected interface for which no Address
Resolution Protocol (ARP) cache entry exists.
null Drops the packets forwarded to the adjacency formed for the null 0 interface.
punt Represents destinations that cannot be switched in the normal path and that are
punted to the next-fastest switching vector.
Usage Guidelines An adjacency is a node that can be reached by one Layer 2 hop.
Distributed Cisco Express Forwarding is not supported on Cisco 10000 series routers.
Examples The following is sample output from the show ip cef adjacency command when the glean keyword is
specified:
Router# show ip cef adjacency glean
The following is sample output from the show ip cef adjacency drop command with the detail keyword
specified:
Router# show ip cef adjacency drop detail
10.0.0.0/4, version 3
0 packets, 0 bytes, Precedence routine (0)
via 0.0.0.0, 0 dependencies
next hop 0.0.0.0
valid drop adjacency
The following sample output shows the direct IP prefix when the next hop Gigabit Ethernet interface 3/0
is specified:
Router# show ip cef adjacency GigabitEthernet 3/0 172.20.26.29
The following is sample output from the show ip cef adjacency drop command with the detail keyword
specified:
Router# show ip cef adjacency drop detail
10.0.0.0/4, epoch 3
Special source: drop
drop
The following sample output shows the direct IP prefix when the next hop Gigabit Ethernet interface
3/0/0 is specified (before Cisco IOS Release 12.2(25)S):
Router# show ip cef adjacency GigabitEthernet 3/0/0 172.20.26.29
Table 34 show ip cef adjacency Field Descriptions (Before Cisco IOS Release 12.2(25)S)
Field Description
Prefix Destination IP prefix.
Next Hop Next hop IP address.
Interface Next hop interface.
For Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, and later
releases the information in the output is the same, but the format of the output is changed.
Router# show ip cef adjacency FastEthernet 0/1 172.17.22.1
10.10.1.2/32
nexthop 172.17.22.1 FastEthernet0/1
10.20.12.0/24
nexthop 172.17.22.1 FastEthernet0/1
Field Description
10.10.1.2/32 Destination IP prefix.
nexthop 172.17.22.1 Next hop IP address.
FastEthernet0/1 Next hop interface.
Usage Guidelines These show commands also display the epoch information for the following:
show ip cef summaryDisplays the table epoch for a specific FIB table.
show ip cef detailDisplays the epoch value for each entry of a specific FIB table.
show adjacency summaryDisplays the adjacency table epoch.
show adjacency detailDisplays the epoch value for each entry of the adjacency table.
Examples Sample Output for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, and Later Releases
This example shows how to display epoch information. The fields shown in the display are
self-explanatory.
Router# show ip cef epoch
VRF: Default
Database epoch: 0 (12 entries at this epoch)
For adjacency table epoch information, see the show adjacency prefix command.
Sample Output for Cisco IOS Releases Before Cisco IOS Release 12.2(25)S
This example shows how to display epoch information. The fields shown in the display are
self-explanatory.
Router# show ip cef epoch
Table:Default-table
Table epoch:2 (164 entries at this epoch)
Adjacency table
Table epoch:1 (33 entries at this epoch)
This example shows the output after you clear the epoch table and increment the epoch number. The
fields shown in the display are self-explanatory.
Router# show ip cef epoch
Table:Default-table
Table epoch:2 (164 entries at this epoch)
Adjacency table
Table epoch:1 (33 entries at this epoch)
Router# clear ip cef epoch full
Router# show ip cef epoch
Table:Default-table
Table epoch:3 (164 entries at this epoch)
Adjacency table
Table epoch:2 (33 entries at this epoch)
To display all recorded Cisco Express Forwarding Forwarding Information Base (FIB) and adjacency
events, use the show ip cef events command in user EXEC or privileged EXEC mode.
show ip cef [vrf vrf-name] events [ip-prefix] [new | within seconds] [detail] [summary]
Syntax Description vrf (Optional) A Virtual Private Network (VPN) routing and forwarding (VRF)
instance.
vrf-name (Optional) Name assigned to the VRF.
ip-prefix (Optional) Next hop IP prefix, in dotted decimal format (A.B.C.D).
new (Optional) Displays new Cisco Express Forwarding events not previously
shown.
within seconds (Optional) Displays Cisco Express Forwarding events that occurred within a
specified number of seconds.
detail (Optional) Displays detailed information for each Cisco Express Forwarding
event entry.
summary (Optional) Displays a summary of the Cisco Express Forwarding event log.
Usage Guidelines This command shows the state of the table event log and must be enabled for events to be recorded.
The ip cef table event-log command controls parameters such as event log size.
Examples The following is sample output from the show ip cef events command with summary specified:
Router# show ip cef events summary
The following is sample output from the show ip cef events command displaying events that occurred
within 1 second:
Router# show ip cef events within 1
Field Description
+00:00:00.000 Time stamp of the IP Cisco Express Forwarding event.
[Default-table] Type of VRF table for this event entry.
*.*.*.*/* All IP prefixes.
9.1.80.194/32 IP prefix associated with the event.
FIB insert in mtrie IP prefix insert in the FIB table event.
NBD up IP prefix up event.
FIB remove FIB entry remove event.
[Ignr] Cisco Express Forwarding ignored event.
[OK] Cisco Express Forwarding processed event.
Syntax Description vrf (Optional) A Virtual Private Network (VPN) routing and forwarding (VRF)
instance.
vrf-name (Optional) Name assigned to the VRF.
source-address The network source address.
src-port (Optional) Specifies a source port.
port-number (Optional) The Layer 4 port number of the source IP address, if configured.
The port number can be from 0 to 65535.
destination-address The network destination address.
dest-port (Optional) Specifies a destination port.
port-number (Optional) The Layer 4 port number of the destination IP address, if
configured. The port number can be from 0 to 65535.
Usage Guidelines When you are load balancing per destination, this command shows the exact next hop that is used for a
given IP source-destination pair.
If you configured the ip cef load-sharing algorithm include-ports command and the source,
destination, or source destination keywords, you can use the source port number or the destination port
number or both port numbers to see the load-balancing decision for a source and destination address.
These options are available only if the include-ports algorithm is enabled.
Examples Sample Output for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, and Later Releases
The following is sample output from the show ip cef exact-route command:
Router# show ip cef exact-route 172.16.1.3 172.16.1.2
Field Description
172.16.1.3 -> 172.16.1.2 From source 172.16.1.3 to destination 172.16.1.2.
FastEthernet0/1, Next hop is out interface FastEthernet0/1.
addr 172.17.25.1 IP address of the next hop is 172.17.25.1.
Sample Output for Cisco IOS Releases Before Cisco IOS Release 12.2(25)S
The following is sample output from the show ip cef exact-route command:
Router# show ip cef exact-route 10.1.1.1 172.17.249.252
Field Description
10.1.1.1 -> 172.17.249.252 From source 10.1.1.1 to destination 172.17.249.252.
Ethernet2/0/0 (next hop Next hop is 10.1.104.1 on Ethernet 2/0/0.
10.1.104.1)
To display Cisco Express Forwarding IP prefix inconsistencies, use the show ip cef inconsistency
command in user EXEC or privileged EXEC mode.
Syntax Description vrf (Optional) A Virtual Private Network (VPN) routing and forwarding (VRF)
instance.
vrf-name (Optional) Name assigned to the VRF.
records (Optional) Displays all recorded inconsistencies.
detail (Optional) Displays detailed information for each Cisco Express Forwarding
table entry.
Usage Guidelines This command is available only on routers with line cards.
This command displays recorded IP Cisco Express Forwarding inconsistency records found by the
lc-detect, scan-rp, scan-rib, and scan-lc detection mechanisms.
You can configure the IP Cisco Express Forwarding prefix consistency-detection mechanisms using the
cef table consistency-check command.
Examples The following is sample output from the show ip cef inconsistency command:
Router# show ip cef inconsistency
Field Description
settle time Time after a recorded inconsistency is confirmed.
lc-detect running Consistency checker lc-detect is running.
0/0/0 queries Number of queries sent, ignored, and received.
Inconsistencies:0 confirmed, Number of inconsistencies confirmed, and recorded. Sixteen is the
0/16 recorded maximum number of inconsistency records to be recorded.
Syntax Description detail (Optional) Displays detailed nonrecursive route entry information.
epoch epoch-number (Optional) Displays adjacency type entries filtered by epoch number.
The epoch number range is from 0 to 255.
internal (Optional) Displays data for nonrecursive route entries.
platform (Optional) Displays platform-specific nonrecursive route entries.
source (Optional) Displays source-specific nonrecursive route entry
information.
Usage Guidelines The show ip cef non-recursive detail command shows detailed FIB entry information for all
nonrecursive routes.
Examples The following is sample output from the show ip cef non-recursive detail command:
Router# show ip cef non-recursive detail
Field Description
8 prefixes Indicates the total number of prefixes in the Cisco Express Forwarding
table.
2001:xx::/35 Indicates the prefix of the remote network.
2001:zzz:500::/40 Indicates that prefix 2001:zzz:500::/40 is reachable through this
next-hop address and interface.
nexthop FE80::nnnn:801A
Tunnel32
attached to Tunnel37 Indicates that this prefix is a connected network on Tunnel interface 37.
Receive Indicates that this prefix is local to the router.
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
mac string start from bank4 0x32001CA8(RP)
0x82001CA8(FP)
mac string end from bank9 0x50801CA8(RP)
0xA0801CA8(FP)
Encap String: 0005DC387B180003A011A57881000002884700012000
Examples Sample Output for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, and Later Releases
This is sample output for the show ip cef summary command for IPv4 information:
Router# show ip cef summary
Field Description
IPv4 CEF is enabled and running Status of IPv4 Cisco Express Forwarding on the router.
22 prefixes (22/0 fwd/non-fwd) Number of prefixes forwarded and not forwarded.
Field Description
Table id 0, 1 resets Forwarding table version and the number of times the table was
reset.
Database epoch: 0 (22 entries at Database version and the number of entries in the database.
this epoch)
In Cisco IOS 12.2(25)S, IPv4 and IPv6 output was separated. To display Cisco Express Forwarding
summary information for IPv6, use the show ipv6 cef summary command, for example:
Router# show ipv6 cef summary
Sample Output for Cisco IOS Releases Before Cisco IOS Release 12.2(25)S
This example shows how to display a summary of the IP Cisco Express Forwarding table:
Router# show ip cef summary
Field Description
routes Total number of entries in the Cisco Express Forwarding table.
unresolved Number of entries in the Cisco Express Forwarding table that do not
have resolved recursions categorized by old and new routes.
peak Highest number of unresolved recursions.
leaves, nodes, bytes Number of elements in the Cisco Express Forwarding table and how
much memory they use.
load sharing algorithm, id Type of load sharing, whether the router is configured for per
destination or per packet and the identifier.
Table epoch Number indicating the version of a Cisco Express Forwarding table
from 0 to 255.
Usage Guidelines If the optional feature keyword is not used, all switching statistics are displayed, without regard for
feature order.
Examples The following is sample output from the show ip cef switching statistics command:
Router# show ip cef switching statistics
The following example shows how to display switching statistics for all features in a common format:
Router# show ip cef switching statistics feature
The following example shows how to display switching statistics for all features in a common format:
Router# show ip cef switching statistics feature
Field Description
Path Switch path where the feature was executed. Available switch paths are
platform-dependent.
Following are example switch paths for the Cisco 7200 series router:
RIBprocess switching with Cisco Express Forwarding assistance
(low-end switching [LES])Cisco Express Forwarding switch path
PASCisco Express Forwarding turbo switch path
Following are example switch paths for the Cisco 7500 series router:
RIBcentralized process switching with Cisco Express Forwarding assistance
LEScentralized Cisco Express Forwarding switch path on the Route/Switch
Processor (RSP)
RSPcentralized Cisco Express Forwarding turbo switch path on the RSP
Slot NNdistributed Cisco Express Forwarding turbo switch path on the Versatile
Interface Processor (VIP) in the indicated slot number
Feature Feature that returned the statistics.
Reason Packet description.
Consume Number of packets that the feature removed from the switch path (and will probably
reintroduce to the switch path later). For example, with crypto with hardware acceleration,
the feature might queue the packets to encryption and decryption; because hardware (and
software) encryption is time-consuming, these packets are queued so the main processor
can begin handling the next packet while the crypto module processes the removed packet.
Also, for example, the feature might queue the packets for process switching through a
private queue for that feature.
Drop Number of packets dropped.
Punt Number of packets that could not be switched in the normal path and were punted to the
next-fastest switching vector.
Punt2Host Number of packets that could not be switched in the normal path and were punted to the
host.
For switch paths other than a centralized turbo switch path, punt and punt2host function
the same way. With punt2host from a centralized turbo switch path (PAS and RSP), punt
will punt the packet to LES, but punt2host will bypass LES and punt directly to process
switching.
New i/f Number of packets for which the feature provided Cisco Express Forwarding with
forwarding information (that is, bypassed the normal route lookup).
Syntax Description vrf (Optional) A Virtual Private Network (VPN) routing and forwarding (VRF)
instance.
vrf-name (Optional) Name assigned to the VRF.
Usage Guidelines This command is used to display Cisco Express Forwarding switched traffic statistics by destination
prefix length. The ip cef accounting prefix-length command must be enabled for the counters to
increment.
Examples The following is sample output from the show ip cef traffic prefix-length command:
Router# show ip cef traffic prefix-length
31 0 0
32 0 0
Field Description
Prefix Length Destination IP prefix length for Cisco Express Forwarding
switched traffic.
Number of Packets Number of packets forwarded for the specified IP prefix length.
Number of Bytes Number of bytes transmitted for the specified IP prefix length.
Usage Guidelines If none of the optional keywords or argument is used, all summary information on the default tree in the
IP FIB is shown.
Examples The following is sample output from the show ip cef tree command:
Table 45 describes the significant fields shown in the display for a Cisco 7500 series router.
Field Description
RTRIE storing IPv6 addresses Indicates the tree type as RTRIE.
6 entries (6/0 fwd/non-fwd) Indicates total number of prefix entries as
6 forwarding and 0 nonforwarding entries.
Forwarding & Non-forwarding tree Same tree is used for forwarding and
nonforwarding.
6 inserts, 0 delete Indicates that 6 entries were inserted and 0 entries
were deleted from the tree.
8 nodes using 288 bytes Indicates a total of 8 nodes using a total of
288 bytes of memory.
*calloc failures: number node This line is not present in the example output.
If this line is present in output, it indicates a
memory allocation error at the indicated node.
Table 46 describes the significant fields shown in the display for a Cisco 10000 series router.
Field Description
MTRIE storing IPv4 addresses Indicates the tree type as MTRIE.
42 entries (42/0 fwd/ non-fwd) Indicates total number of prefix entries as
42 forwarding and 0 nonforwarding entries.
Forwarding & Non-forwarding tree Same tree is used for forwarding and
nonforwarding.
82 inserts, 40 delete Indicates that 82 entries were inserted and
40 entries were deleted from the tree.
76 nodes using 15744 bytes Indicates a total of 76 nodes using a total of
15744 bytes of memory.
*calloc failures: number node This line is not present in the example output.
If this line is present in output, it indicates a
memory allocation error at the indicated node.
Usage Guidelines The show ip cef unresolved detail command displays detailed information for all unresolved FIB
entries.
Examples Sample Output for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, and Later Releases
The following is sample output for the show ip cef unresolved command:
Router# show ip cef unresolved detail
Nothing is displayed if no unresolved adjacencies exist. For information about unresolved prefixes for
IPv6, use the show ipv6 unresolved command.
Sample Output for Cisco IOS Releases Before Cisco IOS Release 12.2(25)S
The following is sample output from the show ip cef unresolved command:
Router# show ip cef unresolved
Syntax Description vlan-id VLAN number; valid values are from 1 to 4094.
detail (Optional) Displays the detailed information about the IP Cisco Express
Forwarding VLAN interface.
Examples This example shows how to display the prefixes for a specific VLAN. The fields shown in the display
are self-explanatory.
Router> show ip cef vlan 1003
This example shows how to display detailed IP Cisco Express Forwarding information for a specific
VLAN. The fields shown in the display are self-explanatory.
Router> show ip cef vlan 1003 detail
show ip cef vrf vrf-name [ip-prefix [mask [longer-prefixes]] [detail] [output-modifiers]] [interface
interface-number] [adjacency [interface interface-number] [detail] [discard] [drop] [glean]
[null] [punt] [output-modifiers]] [detail [output-modifiers]] [non-recursive [detail]
[output-modifiers]] [summary [output-modifiers]] [traffic [prefix-length] [output-modifiers]]
[unresolved [detail] [output-modifiers]]
Release Modification
12.2(14)S This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX This command is supported in the Cisco IOS Release 12.2SX train. Support
in a specific 12.2SX release of this train depends on your feature set,
platform, and platform hardware.
12.2(33)SRE This command was modified. Support for the BGP best external and BGP
additional path features was added.
12.2(33)XNE This command was integrated into Cisco IOS Release 12.2(33)XNE.
Cisco IOS XE This command was integrated into Cisco IOS XE Release 2.5.
Release 2.5
Usage Guidelines Used with only the vrf-name argument, the show ip cef vrf command shows a shortened display of the
Cisco Express Forwarding table.
Used with the detail keyword, the show ip cef vrf command shows detailed information for all
Cisco Express Forwarding table entries.
Examples This example shows the forwarding table associated with the VRF called vrf1:
Router# show ip cef vrf vrf1
The following sample output from the show ip cef vrf vrf-name ip-prefix detail command shows the
recursive-via-host and recursive-via-connected flags:
Router# show ip cef vrf vpn1 10.51.10.1 detail
Field Description
Prefix Specifies the network prefix.
Next Hop Specifies the Border Gateway Protocol (BGP) next hop address.
Interface Specifies the VRF interface.
show ip cef with epoch epoch-number [checksum | detail | internal [checksum] | platform
[checksum | detail | internal [checksum]]]
Usage Guidelines Use this command to display information about prefix properties for a specified epoch in the
Cisco Express Forwarding FIB. This command is similar to the show ipv6 cef with epoch command,
except that it is IPv4 specific. Use the show ip cef epoch command to display the epoch number.
Examples The following is sample output from the show ip cef with epoch command:
Router# show ip cef with epoch 0
Field Description
Prefix IP addresses in the FIB associated with the specified epoch.
Next Hop What happens to the packet at the next hop.
Interface Either the egress interface for the forwarded packet or the interface on which
the packet is received.
The following is sample output from the show ip cef with epoch detail command:
Router# show ip cef with epoch 15 detail
Field Description
IPv4 CEF is enabled and running States whether Cisco Express Forwarding is enabled and
running.
VRF Default VRF table, in this instance, the default VRF.
9 prefixes ((9/0 fwd/non-fwd) Number of prefixes in the VRF, how many of them are
forwarded, and how many are not forwarded.
Table id 0 Table identification number.
Database epoch: 0 (9 entries at this Value of the database epoch and number of entries in the
epoch) epoch.
The following is sample output from the show ip cef with epoch checksum command:
Router# show ip cef with epoch 0 checksum
0.0.0.0/0
FIB checksum: 0x353023B8
0.0.0.0/8
FIB checksum: 0x6AAA2DEF
0.0.0.0/32
FIB checksum: 0xC9136D79
10.1.1.1/32
FIB checksum: 0x2DD79A12
127.0.0.0/8
FIB checksum: 0x06E2709F
224.0.0.0/4
FIB checksum: 0xC59D5F03
224.0.0.0/24
FIB checksum: 0x9A64B149
240.0.0.0/4
FIB checksum: 0x891B2D02
255.255.255.255/32
FIB checksum: 0x72C832F4
Field Description
10.1.1.1/32 Prefix in epoch 0.
FIB checksum: 0x2DD79A12 FIB checksum associated with the named prefix.
The following is sample output from the show ip cef with epoch platform command:
Router# show ip cef with epoch 0 platform
0.0.0.0/0
0.0.0.0/8
0.0.0.0/32 receive
10.1.1.1/32 receive
127.0.0.0/8
224.0.0.0/4 multicast
224.0.0.0/24 multicast
240.0.0.0/4
255.255.255.255/32 receive
Field Description
10.1.1.1/32 receive Receive prefix in the specified database epoch.
224.0.0./4 multicast Multicast address in the specified database epoch.
show ip cef with source source-type [checksum | detail | epoch | internal [checksum] | platform
[checksum | detail | internal [checksum]]]
Syntax Description source-type The source-type argument must be replaced by one of the following
keywords that are supported for your release.
Keywords for all supported Cisco IOS Releases:
aliasDisplays alias address prefix sources in the Cisco Express
Forwarding FIB.
broadbandDisplays broadband receive prefix sources in the
Cisco Express Forwarding FIB.
fallbackDisplays fallback lookup prefix sources in the Cisco Express
Forwarding FIB.
interfaceDisplays interface configuration prefix sources in the
Cisco Express Forwarding FIB.
NATDisplays Network Address Translation (NAT) prefix sources in
the Cisco Express Forwarding FIB.
ribDisplays Routing Information Base (RIB) prefix sources in the
Cisco Express Forwarding FIB.
specialDisplays special prefix sources in the Cisco Express
Forwarding FIB.
testDisplays test command prefix sources in the Cisco Express
Forwarding FIB.
virtualDisplays virtual address prefix sources in the Cisco Express
Forwarding FIB, for example, Virtual Router Redundancy Protocol
(VRRP) and Hot Standby Router Protocol (HSRP) addresses.
Additional keywords for Cisco IOS Releases 12.2(25)S, 12,2(28)SB,
12.2(33)SRA, and later releases:
adjacencyDisplays adjacency prefix sources in the Cisco Express
Forwarding FIB.
default-routeDisplays default route handler prefix sources in the
Cisco Express Forwarding FIB.
inherited-path-listDisplays inherited path list prefix source in the
Cisco Express Forwarding FIB.
Additional keywords for Cisco IOS Releases 12.2(33)SXH, 12.4(20)T, and
later SX and T releases:
adjDisplays adjacency prefix sources in the Cisco Express orwarding
FIB.
Usage Guidelines Use this command to filter on a specified type of source prefix in the Cisco Express Forwarding FIB.
Examples The following is sample output from the show ip cef with source rib command:
Router# show ip cef with source rib
Field Description
Prefix List of prefixes in the Cisco Express Forwarding FIB whose source is the
Routing Information Base (RIB).
Next Hop Next-hop address, in general.
Interface Either an egress interface or receive interface.
The following is sample output from the show ip cef with source fib detail command:
Router# show ip cef with source rib detail
Field Description
VRF Default Default VRF table.
9 prefixes (9/0 Fwd/non-fwd) Number of prefixes in the VRF, how many of then are
forwarded, and how many or not forwarded.
Table id 0 Table identification number.
Database epoch: Number of the epoch (0) and number of entries in the epoch.
0 (9 entries at this epoch)
10.1.1.1/32, epoch 0, flags attached, Details about the prefix: the epoch in which it is found, and
connected, receive the flags that are set for the prefix:
attachedPrefix is connected to a network
connectedPrefix includes an address that is bound to
an interface on the device
receivePrefix is punted to and handled by the Process
code rather than Cisco Express Forwarding
Interface source: Loopback0 Indicates that the source interface for the prefix was an
interface, specifically Interface Loopback0.
receive for Loopback0 Indicates that the prefix is a receive type for the Lookback
interface. Traffic matching this prefix will be punted to the
process level and handled by the process code.
Syntax Description group-address (Optional) Address of the IP multicast group for which to display the MFIB
table.
source-address (Optional) Address of the source of IP multicast packets for which to display the
MFIB table.
Usage Guidelines Use this command on the line card. This command displays the MFIB table, forwarding information, and
related flags and counts.
Note To reach the console for a line card, enter attach slot# (slot number where the line card resides).
On a Gigabit Switched Router (GSR) only, line card commands can be executed from the Route
Processor (RP) using the following syntax: execute [slot slot-number | all] command.
The command argument is any of the line card show commands, such as show ip mds summary and
show ip mds forward.
Examples The following is sample output from the show ip mds forwarding command:
Router# show ip mds forwarding
(*, 224.2.170.73),
Field Description
(172.17.62.86, Source and group addresses. The number in brackets is the hash bucket for
224.2.170.73) [31]) the route.
Incoming interface Expected interface for a multicast packet from the source. If the packet is
not received on this interface, it is discarded.
Pkts Total number of packets switched by the entry in the table.
last used: Time when this MFIB entry was used to switch a packet.
Kbps: Kilobits per second of the switched traffic.
Outgoing interface list Interfaces through which packets will be forwarded.
Syntax Description vrf (Optional) Supports the Multicast Virtual Private Network (VPN) routing and
forwarding instance (VRF).
vrf-name (Optional) Name assigned to the VRF.
Examples The following is sample output from the show ip mds interface command:
Router# show ip mds interface
Field Description
Interface The specified interface.
SW-Index Software index.
HW-Index Hardware index.
HW IDB Hardware interface description block.
FS Vector Fast Switching Vector.
VRF VPN routing/forwarding instance.
Usage Guidelines The switching and linecard keywords are available only on the Route Processor (RP). The ipc-msg
keyword is available on both the RP and line card (LC).
Examples The following is sample output from the show ip mds stats command with the switching keyword:
Router# show ip mds stats switching
Field Description
Slot Slot number for the line card.
Total Total number of packets received.
Switched Total number of packets switched.
Drops Total number of packets dropped.
Field Description
RPF Total number of packets that failed reverse path forwarding (RPF) lookup.
Punts Total number of packets sent to the RP because the line card could not switch
them.
Failures Times that the RP tried to switch but failed because of lack of resources or
(switch/clone) clone for the RSP only; failed to get a packet clone.
The following is sample output from the show ip mds stats command with the linecard keyword:
Router# show ip mds stats linecard
Field Description
Slot Slot number for the line card.
Status MDS line card status.
IPC(seq/max) MDS IPC message sequence number and maximum sequence number for the
linecard.
Q(high/route) Length of the high and normal priority MDS IPC queue.
Reloads The number of MDS downloads that happened in the line card.
The following is sample output from a line card using the show ip mds stats command with the ipc-msg
keyword:
Router# show ip mds stats ipc-msg
Field Description
MDFS Reload stats
Full reload request Number of full multicast distributed switching (MDS) download requests
sent.
Partial reload request Number of partial MDS download requests sent.
LC disable request Number of requests sent to disable MDS on the line card.
MDFS ipc messages sent
line card stats Number of line card statistic messages sent.
mdb stats Number of Multicast Descriptor Block (MDB) statistics messages sent.
hwidb stats Number of hardware Interface Descriptor Block (HWIDB) statistics messages
sent.
swidb stats Number of software Interface Descriptor Block (SWIDB) statistics messages
sent.
flow control msg Number of flow control messages sent.
clear mroute msg Number of clear multicast route (mroute) messages sent.
MDFS alert messages received
mdfs enable alert Number of multicast distributed fast switching (MDFS) enable alert messages
received.
table2 size alert Number of table2 size alert messages received.
clear all alert Number of clear all alert messages received.
clear stats alert Number of clear statistics alert messages received
spd alert Number of selective packet discard (SPD) alert messages received.
svd alert Number of singular value decomposition (SVD) alert messages received.
route limit alert Number of mroute limit alert messages received.
source limit alert Number of sources per group limit alert messages received.
punt limit alert Number of MDFS punt limit alert messages received.
MDFS ipc messages received
gdb msg Number of GDB messages received.
mdb msg Number of MDB messages received.
midb msg Number of multicast interface data block (MIDB) messages received.
hwidb msg Number of HWIDB messages received.
Field Description
oir hwidb msg Number of HWIDB online insertion and removal (OIR) messages received.
hwidb erase msg Number of HWIDB erase messages received.
swidb msg Number of SWIDB messages received.
oir swidb msg Number of SWIDB OIR messages received.
swidb erase msg Number of SWIDB erase messages received.
mdt msg Number of Multicast Distribution Tree (MDT) messages received.
rpdf msg Number of rendezvous point designated forwarder (RPDF) messages
received.
fwd table erase msg Number of MDFS forwarding table erase messages received.
mdt mgid ext Number of MDFS MDT multicast global identifier (MGID) extended
slotmask msg slotmask messages received.
mvrf ext slotmask Number of MDFS Multicast Virtual Routing and Forwarding (MVRF)
msg extended slotmask messages received.
Usage Guidelines Use this command on a line card. On a Gigabit Switched Router (GSR) only, line card commands can
be executed from the Route Pricessor (RP) using the following syntax:
execute [slot slot-number | all] command
The command argument is any of the line card show commands, such as show ip mds summary or show
ip mds forward.
Examples The following is sample output from the show ip mds summary command:
Router# show ip mds summary
(*, 224.2.170.73),
Incoming interface: Null
Pkts: 0, last used: never, Kbps: 0, fast-flags: N
(172.17.62.86, 224.2.170.73) [31]
Incoming interface: Fddi3/0/0
Pkts: 3045, last used: 00:00:03, Kbps: 0, fast-flags: M
(172.22.3.7, 224.2.170.73) [334]
Incoming interface: Fddi3/0/0
Pkts: 0, last used: never, Kbps: 0, fast-flags: M
Field Description
(172.17.62.86, 224.2.170.73) Source and group addresses. The number in brackets is the hash
[31] bucket for the route.
Incoming interface Expected interface for a multicast packet from the source. If the
packet is not received on this interface, it is discarded.
Pkts Total number of packets switched by that entry.
last used Time when this MFIB entry was used to switch a packet.
Kbps Kilobits per second of the switched traffic.
show ip traffic
To display the global or system-wide IP traffic statistics for one or more interfaces, use the show ip
traffic command in user EXEC or privileged EXEC mode.
Syntax Description interface type number (Optional) Displays the global or system-wide IP traffic statistics for a
specific interface. If the interface keyword is used, the type and number
arguments are required.
Command Default Using the show ip traffic command with no keywords or arguments displays the global or system-wide
IP traffic statistics for all interfaces.
Usage Guidelines Using the show ip traffic command with the optional interface keyword displays the ipIfStatsTable
counters for the specified interface if IPv4 addressing is enabled.
Examples The following is sample output from the show ip traffic command:
Router# show ip traffic
IP statistics:
Rcvd: 27 total, 27 local destination
0 format errors, 0 checksum errors, 0 bad hop count
0 unknown protocol, 0 not a gateway
0 security failures, 0 bad options, 0 with options
Opts: 0 end, 0 nop, 0 basic security, 0 loose source route
0 timestamp, 0 extended security, 0 record route
0 stream ID, 0 strict source route, 0 alert, 0 cipso, 0 ump
0 other
Frags: 0 reassembled, 0 timeouts, 0 couldn't reassemble
0 fragmented, 0 couldn't fragment
Bcast: 27 received, 0 sent
Mcast: 0 received, 0 sent
Sent: 0 generated, 0 forwarded
Drop: 0 encapsulation failed, 0 unresolved, 0 no adjacency
0 no route, 0 unicast RPF, 0 forced drop
Drop: 0 packets with source IP address zero
ICMP statistics:
Rcvd: 0 format errors, 0 checksum errors, 0 redirects, 0 unreachable
0 echo, 0 echo reply, 0 mask requests, 0 mask replies, 0 quench
0 parameter, 0 timestamp, 0 info request, 0 other
0 irdp solicitations, 0 irdp advertisements
0 time exceeded, 0 timestamp replies, 0 info replies
Sent: 0 redirects, 0 unreachable, 0 echo, 0 echo reply
0 mask requests, 0 mask replies, 0 quench, 0 timestamp
0 info reply, 0 time exceeded, 0 parameter problem
0 irdp solicitations, 0 irdp advertisements
BGP statistics:
Rcvd: 0 total, 0 opens, 0 notifications, 0 updates
0 keepalives, 0 route-refresh, 0 unrecognized
Sent: 0 total, 0 opens, 0 notifications, 0 updates
0 keepalives, 0 route-refresh
EIGRP-IPv4 statistics:
Rcvd: 0 total
Sent: 0 total
TCP statistics:
Rcvd: 0 total, 0 checksum errors, 0 no port
Sent: 0 total
UDP statistics:
Rcvd: 185515 total, 0 checksum errors, 185515 no port
Sent: 0 total, 0 forwarded broadcasts
OSPF statistics:
Rcvd: 0 total, 0 checksum errors
0 hello, 0 database desc, 0 link state req
0 link state updates, 0 link state acks
Sent: 0 total
0 hello, 0 database desc, 0 link state req
0 link state updates, 0 link state acks
Probe statistics:
Rcvd: 0 address requests, 0 address replies
0 proxy name requests, 0 where-is requests, 0 other
Sent: 0 address requests, 0 address replies (0 proxy)
0 proxy name replies, 0 where-is replies
ARP statistics:
Rcvd: 1477 requests, 8841 replies, 396 reverse, 0 other
Sent: 1 requests, 20 replies (0 proxy), 0 reverse
Drop due to input queue full: 0
The following is sample output from the show ip traffic command for Ethernet interface 0/0:
Router# show ip traffic interface ethernet 0/0
IP statistics:
Rcvd: 27 total, 27 local destination
0 format errors, 0 checksum errors, 0 bad hop count
0 unknown protocol, 0 not a gateway
0 security failures, 0 bad options, 0 with options
Opts: 0 end, 0 nop, 0 basic security, 0 loose source route
0 timestamp, 0 extended security, 0 record route
0 stream ID, 0 strict source route, 0 alert, 0 cipso, 0 ump
0 other
Frags: 0 reassembled, 0 timeouts, 0 couldn't reassemble
0 fragmented, 0 couldn't fragment
Bcast: 27 received, 0 sent
Mcast: 0 received, 0 sent
Sent: 0 generated, 0 forwarded
Field Description
format errors Indicates a gross error in the packet format, such as an impossible Internet
header length.
bad hop count Occurs when a packet is discarded because its time-to-live (TTL) field was
decremented to zero.
encapsulation failed Usually indicates that the router had no Address Resolution Protocol (ARP)
request entry and therefore did not send a datagram.
no route Counted when the Cisco IOS software discards a datagram that it did not
know how to route.
show ipv6 cef with epoch epoch-number [checksum | detail | internal [checksum] | platform
[checksum | detail | internal [checksum]]]
Usage Guidelines Use this command to display information about prefix properties for a specified epoch in the
Cisco Express Forwarding IPv6 FIB. This command is similar to the show ip cef with epoch command,
except that it is IPv6 specific. Use the show ipv6 cef epoch command to display entries filtered by epoch
number.
Examples The following is sample output from the show ipv6 cef with epoch command:
Router# show ipv6 cef with epoch 0
::/0
no route
::/127
discard
2000::1/128
receive for Loopback0
2000::2/128
nexthop FE80::A8BB:CCFF:FE00:2500 Ethernet0/0
2000::3/128
nexthop FE80::A8BB:CCFF:FE00:2602 Ethernet2/0
2000::4/128
nexthop FE80::A8BB:CCFF:FE00:2602 Ethernet2/0
2001::/64
attached to Ethernet2/0
2001::1/128
receive for Ethernet2/0
2001::3/128
attached to Ethernet2/0
2001:1::/64
attached to Ethernet0/0
2001:1::1/128
receive for Ethernet0/0
2001:2::/64
nexthop FE80::A8BB:CCFF:FE00:2602 Ethernet2/0
2002::/64
attached to Tunnel0
2002::1/128
receive for Tunnel0
FE80::/10
receive for Null0
FF00::/8
receive for Null0
Field Description
no route No route is associated with the IPv6 prefix.
discard Traffic for this prefix is discarded.
2000::1/128 A receive prefix for interface Loopback0.
receive for Loopback0
2000::2/128 An IPv6 prefix that is forwarded to a next-hop address
nexthop (FE80::A8BB:CCFF:FE00:2500) through interface Ethernet 0/0.
FE80::A8BB:CCFF:FE00:2500
Ethernet0/0
2001::/64 This prefix is a connected network on interface Ethernet 0/0.
attached for Ethernet2/0
2001::1/128 A receive prefix for interface Ethernet 0/0.
receive for Ethernet2/0
The following is sample output from the show ipv6 cef with epoch detail command:
Router# show ipv6 cef with epoch 0 detail
Field Description
IPv6 CEF is enabled and running Indicates that IPv6 CEF is enabled and running on the RP.
centrally
VRF base Number of prefixes in the VRF, how many of them are
16 prefixes (16/0 fwd/non-fwd) forwarded, and how many are not forwarded.
Table id 0 Table identification number.
Database epoch Value of the database epoch and number of entries in the
0 (16 entries at this epoch) epoch.
2000::1/128, epoch 0, flags attached, Provides detail for the table entries. In this example,
connected, receive, local 2000:1/128 is an IPv6 prefix at epoch 0. The flags set for this
receive for Loopback0 prefix are:
attachedPrefix is a connected network
connectedPrefix includes an address that is bound to
an interface on the device
receivePrefix is punt to and handled by the process
level
localPrefix is a subset of receive and marks prefixes
that are received by on interface on the device
The following is sample output from the show ipv6 cef with epoch checksum command:
Router# show ipv6 cef with epoch 0 checksum
::/0
FIB checksum: 0x64E25610
::/127
FIB checksum: 0xE0B3DE11
2000::1/128
FIB checksum: 0xD04E36EC
2000::2/128
FIB checksum: 0x84892BA5
2000::3/128
FIB checksum: 0x912BA720
2000::4/128
FIB checksum: 0xC6D89ADA
.
.
.
Field Description
::/0 Default route handler. ::/0 prefix matches all addresses. (
::/128 prefix is an exact match for all zero addresses only.)
FIB checksum: 0x64E25610 FIB checksum associated with the named prefix.
show ipv6 cef with source source-type [checksum | detail | epoch | internal [checksum] |
platform [checksum | detail | internal [checksum]]]
Syntax Description source-type The source-type argument must be replaced by one of the following
keywords that are supported for your release.
Keywords for all supported Cisco IOS releases:
aliasDisplays alias address prefix sources in the Cisco Express
Forwarding IPv6 FIB.
broadbandDisplays broadband receive prefix sources in the
Cisco Express Forwarding IPv6 FIB.
fallbackDisplays fallback lookup prefix sources in the Cisco Express
Forwarding IPv6 FIB.
interfaceDisplays interface configuration prefix sources in the
Cisco Express Forwarding IPv6 FIB.
natDisplays Network Address Translation (NAT) prefix sources in
the Cisco Express Forwarding IPv6 FIB.
ribDisplays Routing Information Base (RIB) prefix sources in the
Cisco Express Forwarding IPv6 FIB.
specialDisplays special prefix sources in the Cisco Express
Forwarding IPv6 FIB.
testDisplays test command prefix sources in the Cisco Express
Forwarding IPv6 FIB.
virtualDisplays virtual address prefix sources in the Cisco Express
Forwarding IPv6 FIB, for example, Virtual Router Redundancy
Protocol (VRRP) and Hot Standby Router Protocol (HSRP) addresses.
Additional keywords for Cisco IOS Releases 12.2(25)S, 12,2(28)SB,
12.2(33)SRA, and later SB and SR releases:
adjacencyDisplays adjacency prefix sources in the Cisco Express
ForwardingIPv6 FIB.
default-routeDisplays default route handler prefix sources in the
Cisco Express Forwarding FIB.
inherited-path-listDisplays inherited path list prefix source in the
Cisco Express Forwarding FIB.
Additional keywords for Cisco IOS Releases 12.2(33)SXH, 12.4(20)T, and
later SX and T releases:
adjDisplays adjacency prefix sources in the Cisco Express
Forwarding FIB.
Usage Guidelines Use this command to filter on prefixes in the Cisco Express Forwarding FIB that are added by a specified
source.
::/127
discard
2000::1/128
receive for Loopback0
2000::2/128
Field Description
::/127 IPv6 prefix.
discard Indicates that traffic destined for this prefix should be discarded.
2000::1/128 An IPv6 prefix that is a receive prefix for interface Loopback0.
receive for Loopback0 Traffic destined for this prefix will be punted to the process level.
2000::2/128 An IPv6 prefix that is forwarded to a next-hop address
nexthop (FE80::A8BB:CCFF:FE00:2500) through interface Ethernet 0/0.
FE80::A8BB:CCFF:FE00:2500
Ethernet0/0
2001::/64 An IPv6 prefix that is a connected network on interface Ethernet 0/0.
attached for Ethernet2/0 That is, the destination can be reached directly through the specified
interface.
The following is sample output from the show ipv6 cef with source fib detail command:
Router# show ipv6 cef with source rib detail
Table 65 show ipv6 cef with source rib detail Field Descriptions
Field Description
IPv6 CEF is enabled and running Verifies that Cisco Express Forwarding for IPV6 is enabled
centrally. globally.
VRF base Base VRF table.
16 prefixes (16/0 Fwd/non-fwd) Number of prefixes in the VRF, how many prefixes are
forwarded, and how many are not forwarded.
Table id 0 Identifies the table by number.
Database epoch: Specifies the type of epoch.
0 (16 entries at this epoch) Number of the epoch (0) and number of entries in the epoch.
2000::1/128, epoch 0, flags attached, Details about the prefix: the epoch in which it is found, the
connected, receive, local flags set for the prefix:
attachedPrefix is a connected network
connectedPrefix includes an address that is bound to
an interface on the device
receivePrefix is punt to and handled by the process
level
localPrefix is a subset of receive and marks prefixes
that are received by on interface on the device
Examples for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA, and Later SB and SR Releases
The following is sample output from the show ipv6 cef with source adjacency command:
Router# show ipv6 cef with source adjacency
2001::3/128
attached to Ethernet2/0
Field Description
20001::3/128 IPv6 prefix whose source is an adjacency.
attached to Ethernet2/0 Indicates that the prefix is a connected network through
Interface Ethernet 2/0.
The following is sample output from the show ipv6 cef with source adjacency detail command:
Router# show ipv6 cef with source adjacency detail
#
IPv6 CEF is enabled and running centrally.
VRF Default
16 prefixes (16/0 fwd/non-fwd)
Table id 0x1E000000
Database epoch: 0 (16 entries at this epoch)
Table 67 show ipv6 cef with source adjacency detail Field Descriptions
Field Description
IPv6 CEF is enabled and running centrally. Verifies that Cisco Express Forwarding for IPV6 is
enabled and running on the RP.
VRF Default Default VRF table.
16 prefixes (16/0 Fwd/non-fwd) Number of prefixes in the VRF, how many prefixes are
forwarded and how many are not forwarded.
Table id 0x1E000000 Identifies the table by hexadecimal number.
2001::3/128, epoch 0, flags attached Lists a prefix, its epoch number, and flags. Attached
flag indicates a connected network.
Adj source: IPv6 adj out of Ethernet2/0, Indicates that the prefix was sourced by an adjacency
addr 2000::3 050878F0 and specifies the address family, interface, and address
in memory of the adjacency.
Table 67 show ipv6 cef with source adjacency detail Field Descriptions (continued)
Field Description
Dependent covered prefix type adjfib cover A prefix sourced by an adjacency is dependent on
2001::/64 another less specific prefix (2001::/64) for forwarding
information. If this less specific prefix changes, the
dependent prefix will need to be recomputed.
attached to Ethernet2/0 Indicates the prefix is a connect network through
interface Ethernet 2/0.
The following is sample output from the show ipv6 cef with source adjacency checksum command:
Router# show ipv6 cef with source adjacency checksum
2001::3/128
FIB checksum: 0x4AE0F5DC
Table 68 show ipv6 cef with source adjacency checksum Field Descriptions
Field Description
2001::3/128 IPv6 prefix whose source is an adjacency.
FIB checksum: 0x4AE0F5DC FIB checksum.
Examples for Cisco IOS Releases 12.2(33)SXH, 12.4(20)T and Later SX and T Releases
The following is sample output from the show ipv6 cef with source adjacency command:
Router# show ipv6 cef with source adj
2001::3/128
attached to Ethernet2/0
Field Description
20001::3/128 IPv6 prefix whose source is an adjacency.
attached to Ethernet2/0 Indicates that the prefix is a network connected through
interface Ethernet 2/0.
The following is sample output from the show ipv6 cef with source adj detail command:
Router# show ipv6 cef with source adj detail
Table 70 show ipv6 cef with source adj detail Field Descriptions
Field Description
IPv6 CEF is enabled and running centrally. Verifies that Cisco Express Forwarding for IPV6 is
enabled an running on the RP.
VRF base Base VRF table.
16 prefixes (16/0 Fwd/non-fwd) Number of prefixes, and how many prefixes are
forwarded and how many are not forwarded.
2001::3/128, epoch 0, flags attached Provides more detail about the adjacency source, such
as epoch number and flags.
Adj source: IPv6 adj out of Ethernet2/0, Lists a prefix, its epoch number, and flags. Attached
addr 2000::3 050878F0 flag indicates a connected network.
Dependent covered prefix type adjfib cover A prefix sourced by an adjacency is dependent on
2001::/64 another less specific prefix (2001::/64) for forwarding
information. If this less specific prefix changes, the
dependent prefix will need to be recomputed.
attached to Ethernet2/0 Indicates the prefix is a connect network through
interface Ethernet 2/0.
The following is sample output from the show ipv6 cef with source adj checksum command:
Router# show ipv6 cef with source adj checksum
2001::3/128
FIB checksum: 0x4AE0F5DC
Table 71 show ipv6 cef with source adj checksum Field Descriptions
Field Description
2001::3/128 IPv6 prefix whose source is an adjacency.
FIB checksum: 0x4AE0F5DC FIB checksum.
show mls cef [ip] [prefix [mask-length | load-info]] [detail] [module number]
show mls cef [ip] [{lookup ...} | {multicast ...} | {rpf ...} | {vpn ...} | {vrf ...}]
show mls cef [{adjacency ...} | {block block-number [entries}] | {config-register reg-address} |
{diags [detail]} | {entry index [detail]} | {exact-route ...} | {hardware [module number]} |
{inconsistency ...} | {lookup ...} | {masks [type] [module number]} | {rpf ...} | {statistics ...}
| {summary [module number]} | {tunnel fragment} | {used-blocks [type] [module number]}
| {vpn ...} | {vrf ...}]
show mls cef [{eom ...} | {ip ...} | {ipv6 ...} | {mpls ...}]
Syntax Description ip (Optional) Displays IPv6 unicast entries in the MLS-hardware Layer 3-switching
table; see the Usage Guidelines section for additional information.
prefix (Optional) Entry prefix in the format A.B.C.D.
mask-length (Optional) Mask length; valid values are from 0 to 32.
load-info (Optional) Displays output with a hash value next to each adjacency.
detail (Optional) Displays detailed hardware information. See the Usage Guidelines
section for important information.
module number (Optional) Displays information about the entries for a specific module.
lookup ... (Optional) Displays IP entries in the MLS-hardware Layer 3-switching table for the
specified destination IP address. See the show mls cef lookup command.
multicast ... (Optional) Displays IP entries in the MLS-hardware Layer 3-switching table in the
compact Cisco Express Forwarding table display format; see the show mls cef ip
multicast command.
rpf ... (Optional) Displays information about the Reverse Path Forwarding (RPF)
hardware in the MLS-hardware Layer 3-switching table; see the show mls cef rpf
command.
vpn ... (Optional) Displays information about the Virtual Private Network (VPN) ID
Cisco Express Forwarding table. See the Usage Guidelines section for important
information.
vrf ... (Optional) Displays information about the Cisco Express Forwarding table for the
specified VRF name.
adjacency ... (Optional) Displays information about the MLS-hardware Layer 3-switching
adjacency node; see the show mls cef adjacency command.
block (Optional) Displays information about the mask-block utilization for a specific
block-number block; valid values are from 0 to 4294967295. See the Usage Guidelines section
for important information.
entries (Optional) Displays the mask-block utilization entries. See the Usage Guidelines
section for important information.
config-register (Optional) Displays information about the hardware configuration register for a
reg-address specific register. See the Usage Guidelines section for important information.
diags (Optional) Displays information about the diagnostic entry. See the Usage
Guidelines section for important information.
entry index (Optional) Specifies the specified prefix entry index to display; valid values are
from 0 to 4294967295. See the Usage Guidelines section for important
information.
exact-route ... (Optional) Displays information about hardware load sharing; see the show mls cef
exact-route command.
hardware (Optional) Displays a summary of the hardware information. See the Usage
Guidelines section for important information.
inconsistency ... (Optional) Displays information about the consistency checker; see the show mls
cef inconsistency command.
masks ... (Optional) Displays information about the mask. See the Usage Guidelines
section for important information.
statistics ... (Optional) Displays the number of switched packets and bytes; see the show mls cef
statistics command.
tunnel fragment (Optional) Displays the operational status of tunnel fragmentation.
summary ... (Optional) Displays a summary of rates in the hardware for each protocol; see the
show mls cef summary command.
used-blocks (Optional) Displays a list of used blocks; see the Usage Guidelines section for
important information.
eom ... Displays information about the EoM protocol; this keyword is not supported.
ip ... Displays information about the IP protocol; see the Usage Guidelines section for
additional information.
ipv6 ... Displays information about the IPv6 protocol.
mpls ... Displays information about the MPLS protocol; see the show mls cef mpls
command.
Command Default If you do not specify a protocol, the default display is for IP and the global Cisco Express Forwarding
table.
Release Modification
12.2(33)SXI This command was modified. Support for the command was added for PCF3BXL,
PFC3C, and PFC3CXL modes only.
12.2(33)SXI2 This command was modified. Support was added for all PFC3 modes.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
mpls
Default keywordsThe following keywords display identical output for both the show mls cef and
show mls cef ip commands:
prefix
lookup
multicastThis keyword is not supported on systems configured with a Supervisor
Engine 720.
module
rpf
vpn
vrf
Examples This example shows how the show mls cef and show mls cef ip commands are identical:
Router# show mls cef
This example shows how to display all the MLS-hardware Layer 3-switching table IP entries:
Router# show mls cef ip
Field Description
Index MLS-hardware Layer 3-switching table entry index; the maximum is
256,000 entries.
Prefix Entry prefix address/mask.
Adjacency Adjacency types are as follows:
dropPackets matching the prefix entry are dropped.
puntPackets are redirected to an MSFC for further processing.
mac-addressPackets matching the prefix are forwarded to this specific next
hop or the final destination host if directly attached.
This example shows how to display the operational status of tunnel fragmentation:
Router# show mls cef tunnel fragment
show mls cef adjacency [all | decap-tunnel | {encap-tunnel ip-src-addr} | {entry index [to
end-range]} | {flags lower-flag upper-flag} | mac-address number | mac-rewrite | macv4 |
{mpls [label]} | multicast | nat | recirculation | special | tcp | usage] [detail] [module number]
Usage Guidelines The decap-tunnel and endcap-tunnel keywords are used to display the tunnel nodes. The encapsulator
node is considered the tunnel-entry point and the decapsulator node is considered the tunnel-exit point.
There may be multiple source-destination pairs using the same tunnel between the encapsulator and
decapsulator.
The decap-tunnel and endcap-tunnel keywords are not supported on Cisco 7600 series routers that are
configured with a Supervisor Engine 720.
The flags keyword applies to all adjacency formats (for example, mac-rewrite, mpls, and multicast) and
indicates the bits that are set in the adjacency for the specific adjacency.
The module number keyword and argument designate the module and port number. Valid values depend
on the chassis and module used. For example, if you have a 48-port 10/100BASE-T Ethernet module
installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for
the port number are from 1 to 48.
MLS-hardware Layer 3 switching applies to IP traffic only.
MLS-hardware Layer 3-switching adjacency statistics are updated every 60 seconds.
You can display hardware-switched IP-directed broadcast information by entering the show mls cef
adjacency mac-address number detail command.
For each MLS-hardware Layer 3-switching Forwarding Information Base (FIB) entry, MLS-hardware
Layer 3 switching stores Layer 2 information from the MSFC2 for adjacent nodes in the MLS-hardware
Layer 3-switching adjacency table. Adjacent nodes are directly connected at Layer 2. To forward traffic,
MLS-hardware Layer 3 switching selects a route from a MLS-hardware Layer 3-switching FIB entry,
which points to a MLS-hardware Layer 3-switching adjacency entry, and uses the Layer 2 header for the
adjacent node in the adjacency table entry to rewrite the packet during Layer 3 switching. MLS-hardware
Layer 3 switching supports one million adjacency-table entries.
This example shows how to display the adjacency-entry information for a specific index:
Router# show mls cef adjacency entry 132
This example shows how to display the adjacency-entry information for a range of indexes:
Router# show mls cef adjacency entry 132 to 134
This example shows how to display adjacency-node information for a specific MAC address:
Router# show mls cef adjacency mac-address 00e0.f74c.842d
This example shows how to display information about the MPLS adjacency:
Router# show mls cef adjacency mpls detail
This example shows how to display information about the multicast adjacency:
Router# show mls cef adjacency multicast detail
This example shows how to display information about the NAT adjacency:
Router# show mls cef adjacency nat detail
This example shows how to display information about the special adjacency:
Router# show mls cef adjacency special
<Output is truncated>
This example shows how to display information about the TCP adjacency:
Router# show mls cef adjacency tcp detail
This example shows how to display information about the adjacency usage:
Router# show mls cef adjacency usage
This example shows how to display adjacency-node information for a specific MAC address:
Router# show mls cef adjacency mac-address 00e0.f74c.842e
Router#
This example shows how to display the adjacency node information for a specific MAC address for a
specific module:
Router# show mls cef adjacency mac-address 00e0.f74c.842e module 4
Module 4#
Index 17415 : mac-sa:00d0.061d.200a, mac-da:00e0.f74c.842e
interface:Vl46, mtu:1514
packets:0000000000000000, bytes:0000000000000000
Router#
show mls cef exact-route {vrf instance-name src-ip | src-ip} {dest-ip | src-l4port} [dest-l4port |
module num]
Syntax Description vrf Displays the numeric Virtual Private Network (VPN) routing and forwarding
instance-name (VRF) ID for the specified VRF instance name.
src-ip Source IP address.
dest-ip Destination IP address.
src-l4port Layer 4-source port number; valid values are from 0 to 65535.
dest-l4port (Optional) Layer 4-destination port number; valid values are from 0 to 65535.
module num (Optional) Module number.
Usage Guidelines The vrf instance-name keyword and argument are not supported on Cisco 7600 series routers that are
configured with a Supervisor Engine 2.
Examples This example shows how to display the hardware load-sharing information. The fields shown in the
display are self-explanatory.
Router# show mls cef exact-route 172.20.52.16 172.20.52.31
Interface: Gi2/1, Next Hop: 255.255.255.255, Vlan: 4073, Destination Mac: 00d0.061d.200a
Router#
Note The show mls cef exception command is not available in Cisco IOS Release 12.2(33)SXJ and later
Cisco IOS 12.2SX releases.
Syntax Description status Displays information about the Cisco Express Forwarding exception status.
detail (Optional) Displays detailed hardware information; see the Usage Guidelines
section for more information.
priorities Displays information about the Cisco Express Forwarding exception priority.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
The detail keyword is for expert users only and is not documented.
In the output of the show mls cef exception status command, the following definitions apply:
FALSEIndicates that the protocol is not under the exception.
TRUEIndicates that the protocol is under the exception.
Examples This example shows how to display detailed information about the Cisco Express Forwarding exception
status. The fields shown in the display are self-explanatory.
Router# show mls cef exception status
This example shows how to display the Forwarding Information Base (FIB) Error Rate Monitor (ERM)
exception priority. The fields shown in the display are self-explanatory.
Router# show mls cef exception priorities
Priority Protocol
=====================
1 IPv4
2 IPv6
3 MPLS
Router#
Syntax Description module number (Optional) Displays the adjacency-node information for a specific module.
Usage Guidelines In Cisco 7600 series routers that are configured with a Supervisor Engine 2 with a Policy Feature Card
(PFC) and an Multilayer Switching Feature Card 2 (MSFC2), MLS-hardware Layer 3 switching
provides IP unicast and IP multicast Layer 3 switching for a Supervisor Engine 2, a PFC2, an MSFC2,
and fabric-enabled switching modules that have a Distributed Feature Card (DFC).
MLS-hardware Layer 3 switching applies to IP traffic only.
0 IP mcast
Free blocks (non-contiguous range):
27 - 4095 upper blocks, 4096 - 8191 lower blocks
Options:
sanity check: off
sanity interval: 301 seconds
consistency check: on
consistency check interval: 61 seconds
redistribution: off
redistribution interval: 120 seconds
redistribution threshold: 10
compression: on
compression interval: 30 seconds
bank balancing: off
bank differential limit: 5
rpf mode: off
tcam shadowing: on
Background Task statistics:
sanity check count: 0000000000000169
Consistency check count: 0000000000000834
Consistency check errors: 0000000000000002
block redistribute count: 0000000000000000
block compress count: 0000000000000011
IP ucast [29]: 0000000000000001
IP ucast [28]: 0000000000000001
Hardware switching status:
ip switching: on
ipx switching: off
Router#
show mls cef inconsistency [module num | now | records] [detail] [module num]
Syntax Description module num (Optional) Displays inconsistency information for the specified module.
now (Optional) Runs a consistency check and displays any issues.
records (Optional) Displays the inconsistency records.
detail (Optional) Displays hardware-entry details.
module num (Optional) Displays the adjacency-node information for a specific module.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
If you enter the show mls cef inconsistency command with no arguments, this information is displayed:
Consistency check count
Ternary Content Addressable Memory (TCAM)-consistency check errors
Synchronous static random access memory (SSRAM)-consistency check errors
Examples This sections contains examples from the show mls cef inconsistency command. The fields shown in
the displays are self-explanatory.
This example shows how to display information about the consistency checker:
Router# show mls cef inconsistency
This example shows how to display information about the consistency checker for a specific module:
Router# show mls cef inconsistency module 7
This example shows how to run a consistency check and display any issues:
Router# show mls cef inconsistency now
Router#
Router#
show mls cef ip {lookup ...} | {multicast tcam ...} | {rpf ...} | {vpn ...} | {vrf ...}
Usage Guidelines For Cisco 7600 series routers that are configured with a Supervisor Engine 720, see the show mls cef ip
multicast tcam command for information about this command.
For Cisco 7600 series routers that are configured with a Supervisor Engine 2, the supported syntax for
the show mls cef ip multicast tcam command is show mls cef ip {multicast tcam [prefix [mask]}
[module num]].
The following keywords are not supported on Cisco 7600 series routers that are configured with a
Supervisor Engine 2:
detail
rpf
vpn
vrf
The ... indicates that there is additional information.
The vpn keyword is for expert users only and is not documented.
Information in the output of the show mls cef ip command is also displayed in the show mls cef
commands.
The lookup is performed as a longest prefix match and displays the TCAM-entry index that applies to
the specified destination IP address.
The information output is in this format: Index, Prefix, Mask, and Adjacency.
These examples show the output from Cisco 7600 series routers that are configured with a Supervisor
Engine 720.
This example shows how the show mls cef and show mls cef ip commands are identical:
Router# show mls cef
This example shows how to display all the MLS-hardware Layer 3-switching table IP entries:
Router# show mls cef ip
Field Description
Index MLS-hardware Layer 3-switching table entry index; the maximum is
256,000 entries.
Prefix Entry prefix address/mask.
Adjacency Adjacency information.
This example shows how to display the detailed MLS-hardware Layer 3-switching table entries:
Router# show mls cef ip 127.0.0.1 detail
This example shows how to display all the prefixes that are configured for the statistic collection:
Router# show mls cef ip accounting per-prefix
A - Active, I - Inactive
Router#
show mls cef ip multicast {bidir | grp-only | source source-ip} [detail | group group-id |
vlan rpf-vlanid]
show mls cef ip multicast control [detail | prefix prefix | vlan rpf-vlanid]
show mls cef ip multicast src-grp [detail | group group-ip | source | vlan rpf-vlanid]
show mls cef ip multicast subnet [detail | prefix prefix | vlan rpf-vlanid]
show mls cef ip multicast tcam [prefix [mask]] [detail] [module num] [vrf src-ip {src-port |
dst-ip} [dst-port | module num]]
show mls cef ip multicast {grp-mask | vlan rpf-vlanid | vpn vpn-id} [detail]
Usage Guidelines For Cisco 7600 series routers that are configured with a Supervisor Engine 2, the only supported syntax
for the show mls cef ip multicast command is show mls cef ip {multicast tcam [prefix [mask]}
[module num]].
There are two Multicast Multilayer Switching (MMLS) modes, ingress and egress. The output displayed
differs for each mode.
The hardware-entry types are as follows:
{S/m,*}Interface/mask (or subnet) entries that are used to catch a directly connected source.
{*,G/m}Groups that are served by the route processors as group/mask.
{G,C}G indicates a destination MAC address, which is derived from an IP-multicast address, and
C indicates the ingress VLAN.
{S,G,C}S indicates the source IP address, G indicates the destination IP address, which is a
multicast address, and C indicates the ingress VLAN, which is usually the RPF VLAN of the flow.
{S,G}Multicast-routing table entry that is maintained by the software or a multicast-forwarding
table entry that is created in the Forwarding Information Base (FIB) table.
{*,G}Same as {S,G}, except that the source address is a wildcard.
The designated forwarder (DF) index field ranges from 1 to 4 and is an index into the acceptance
(Protocol Independent Multicast [PIM] Route Processors (RPs) multiplied by the DF) table. The
acceptance table is used with DF forwarding and is used to identify the set of DF interfaces for each of
the four RPs in a VPN.
Examples This example shows how to display ingress hardware-entry information that is based on Bidir (*,G/m)
shortcuts:
Router# show mls cef ip multicast grp-mask
This example shows how to display detailed ingress hardware-entry information that is based on Bidir
(*,G/m) shortcuts:
Router# show mls cef ip multicast grp-mask detail
(*, 226.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:0 AdjPtr:7,32775,65543,98311 FibRpfNf:0 FibRpfDf:0 FibAddr:0x100
rwvlans:0 rwindex:0x0 adjmac:0006.d606.e240 rdt:0 E:0 CAP1:0
fmt:mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0x5
packets:0000000000000 bytes:000000000000000000
Starting Offset: 0x0005
V E C: 50 I:0x00449
(*, 225.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:1 AdjPtr:8,32776,65544,98312 FibRpfNf:0 FibRpfDf:0 FibAddr:0x102
rwvlans:0 rwindex:0x0 adjmac:0006.d606.e240 rdt:0 E:0 CAP1:0
fmt:mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0x6
packets:0000000000000 bytes:000000000000000000
Starting Offset: 0x0006
V E C: 51 I:0x0044B
(*, 227.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:1 AdjPtr:19,32787,65555,98323 FibRpfNf:0 FibRpfDf:0 FibAddr:0x104
rwvlans:0 rwindex:0x0 adjmac:0006.d606.e240 rdt:0 E:0 CAP1:0
fmt:mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0x7
packets:0000000000000 bytes:000000000000000000
Starting Offset: 0x0007
V E C: 51 I:0x0044B
(*, 225.2.2.2)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:1 AdjPtr:10,32778,65546,98314 FibRpfNf:0 FibRpfDf:0 FibAddr:0xE2
rwvlans:0 rwindex:0x0 adjmac:0006.d606.e240 rdt:0 E:0 CAP1:0
fmt:mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0xA
packets:0000000000000 bytes:000000000000000000
Starting Offset: 0x000A
V C: 51 I:0x004B5 P->19A0
- V
V E C: 30 I:0x0049B
(*, 225.2.2.1)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:1 AdjPtr:9,32777,65545,98313 FibRpfNf:0 FibRpfDf:0 FibAddr:0xE0
rwvlans:0 rwindex:0x0 adjmac:0006.d606.e240 rdt:0 E:0 CAP1:0
fmt:mcast l3rwvld:1 DM:0 mtu:1518 rwtype:L3 met2:0x0 met3:0x8
packets:0000000000000 bytes:000000000000000000
Starting Offset: 0x0008
V C: 51 I:0x004B1 P->199C
- V
V E C: 30 I:0x00499
This example shows how to display egress hardware-entry information that is based on Bidir (*,G/m)
shortcuts:
Router# show mls cef ip multicast grp-mask
* 227.2.2.0/24 - Bpr 0 0
0x4AE Vl51 [1 oifs]
* 227.2.2.0/24 - Br 0 0
0x40E Vl51 [1 oifs]
Found 3 entries. 3 are mfd entries
Router#
This example shows how to display detailed egress hardware-entry information that is based on Bidir
(*,G/m) shortcuts:
Router# show mls cef ip multicast grp-mask detail
(*, 225.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:0 AdjPtr:7,32775,65543,98311 FibRpfNf:0 FibRpfDf:0 FibAddr:0x120
rwvlans:0 rwindex:0x0 rdt:0 E:0 CAP1:0
fmt:recir l3rwvld:1 DM:0 mtu:1522 rwtype:RECIR
packets:0000000000000 bytes:000000000000000000
(*, 226.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:1 AdjPtr:10,32778,65546,98314 FibRpfNf:0 FibRpfDf:0 FibAddr:0x126
rwvlans:0 rwindex:0x0 rdt:0 E:0 CAP1:0
fmt:recir l3rwvld:1 DM:0 mtu:1522 rwtype:RECIR
packets:0000000000000 bytes:000000000000000000
(*, 227.2.2.0/24)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:0 AdjPtr:13,32781,65549,98317 FibRpfNf:0 FibRpfDf:0 FibAddr:0x12C
rwvlans:0 rwindex:0x0 rdt:0 E:0 CAP1:0
fmt:recir l3rwvld:1 DM:0 mtu:1522 rwtype:RECIR
packets:0000000000000 bytes:000000000000000000
(*, 225.2.2.2)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:0 AdjPtr:19,32787,65555,98323 FibRpfNf:0 FibRpfDf:0 FibAddr:0xE6
rwvlans:0 rwindex:0x0 rdt:0 E:0 CAP1:0
fmt:recir l3rwvld:1 DM:0 mtu:1522 rwtype:RECIR
packets:0000000000000 bytes:000000000000000000
(*, 225.2.2.1)
PI:1 (1) CR:0 (0) Recirc:0 (1)
DFidx:0 AdjPtr:16,32784,65552,98320 FibRpfNf:0 FibRpfDf:0 FibAddr:0xE0
rwvlans:0 rwindex:0x0 rdt:0 E:0 CAP1:0
fmt:recir l3rwvld:1 DM:0 mtu:1522 rwtype:RECIR
packets:0000000000000 bytes:000000000000000000
show mls cef ipv6 [vrf vrf-name] [ip-address/mask] [accounting per-prefix] [module number]
Syntax Description vrf (Optional) IPv6 Virtual Private Network (VPN) routing and forwarding (VRF)
instance.
vrf-name (Optional) VRF name.
ip-address/mask (Optional) Entry IPv6 address and prefix mask. Valid values for the mask argument
are from 0 through 128.
accounting (Optional) Displays per-prefix accounting statistics.
per-prefix
module number (Optional) Displays the entries for a specific module.
exact-route Provides the exact route of IPv6-switching table entries.
src-addr Source IP address.
L4-src-port (Optional) Layer 4-source port number; valid values are from 0 to 65535.
dst-addr Destination IP address.
L4-dst-port (Optional) Layer 4-destination port number; valid values are from 0 to 65535.
multicast tcam Displays IPv6-multicast entries.
v6mcast-address (Optional) IPv6-multicast address.
detail (Optional) Displays detailed hardware information.
internal (Optional) Displays internal hardware information.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
You can enter this command on the supervisor engine and Multilayer Switching (MLS)-hardware
Layer 3-switching module consoles only. Enter the remote login command to enter a session into the
supervisor engine and distributed forwarding card (DFC)-equipped module to enter the commands.
When entering the ip-address/mask argument, use this format, X:X:X:X::X/mask, where valid values for
mask are from 0 to 128.
Up to 64 IPv6 prefixes are supported.
You must enter the L4-src-port and L4-dst-port arguments when the load-sharing mode is set to full, for
example, when Layer 4 ports are included in the load-sharing hashing algorithm.
Examples This example shows how to display the hardware IPv6-switching table entries:
Router# show mls cef ipv6
This example shows how to display the IPv6 entries for a specific IPv6 address and mask:
Router# show mls cef ipv6 2001:4747::/64
This example shows how to display all the IPv6-FIB entries that have per-prefix statistics available:
Router# show mls cef ipv6 accounting per-prefix
A - Active, I - Inactive
show mls cef ipx [prefix [mask | module number] | module number]
Usage Guidelines This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
only.
Information in the output of the show mls cef ipx command is also displayed in the show mls ipx
command.
Examples This example shows how to display the IPX entries in the MLS-hardware Layer 3-switching table. The
fields shown in the display are self-explanatory.
Router# show mls cef ipx
Router#
Index Prefix Mask Adjacency
.
Syntax Description module number (Optional) Displays the entries for a specific module.
Usage Guidelines This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
only.
In Cisco 7600 series routers that are configured with a Supervisor Engine 2 with a Policy Feature Card
(PFC) and a Multilayer Switch Feature Card 2 (MSFC2), multilayer switching (MLS)-hardware Layer 3
switching provides IP unicast and IP multicast Layer 3 switching for a Supervisor Engine 2, a Policy
Feature Card 2 (PFC2), an MSFC2, and fabric-enabled switching modules that have a Distributed
Forwarding Card (DFC).
The TCAM-inconsistency buffer records any inconsistency that is found in the TCAM.
MLS-hardware Layer 3 switching applies to IP traffic only.
Examples This example shows how to display the contents of the TCAM inconsistency buffer. The significant
fields shown in the display are self-explanatory.
Router# show mls cef logging
PFIB_ERR:TCAM_SHADOW_CONSISTENCY_ERR:value : Index: 100
Expected: 0 -0 -0
Hardware: 5 -1020304 -0
PFIB_ERR:TCAM_SHADOW_CONSISTENCY_ERR:Mask : Index: 3
Expected: 4 -0 -0
Hardware: 6 -FFF00000-0
Syntax Description ip (Optional) Displays IP entries in the MLS-hardware Layer 3-switching table; see the
Usage Guidelines section for additional information.
address IP address in the format A.B.C.D.
detail (Optional) Displays hardware-entry details.
module number (Optional) Displays the entries for a specific module.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
The lookup is performed as a longest-prefix match and displays the ternary content addressable
memory (TCAM)-entry index that applies to the specified destination IP address.
The information output is in this format: Index, Prefix, Mask, and Adjacency.
The output of the show mls cef lookup ip and the show mls cef lookup commands is identical.
Examples This example shows how to display the longest prefix match that applies to a specific IPv4-unicast
address. The fields shown in the display are self-explanatory.
Router# show mls cef lookup 224.0.0.0
Syntax Description module num (Optional) Displays the entries for a specific module.
Usage Guidelines This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2
only.
In Cisco 7600 series routers that are configured with a Supervisor Engine 2 with a Policy Feature Card
(PFC) and a Multilayer Switch Feature Card 2 (MSFC2), multilayer switching (MLS)-hardware Layer 3
switching provides IP unicast and IP multicast Layer 3 switching for a Supervisor Engine 2, a Policy
Feature Card 2 (PFC2), an MSFC2, and fabric-enabled switching modules that have a Distributed
Forwarding Card (DFC).
Examples This example shows how to display the MLS-hardware Layer 3-switching MAC-address information for
the MSFC. The fields shown in the display are self-explanatory.
Router# show mls cef mac
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
When you enter the mls cef maximum-routes command to change the configuration, the following
additional fields appear in the output of the show mls cef maximum-routes command:
User configuredShows configuration changes that you have made.
Upon rebootShows the configuration after a system reboot.
These fields appear if you have not saved the change (using the copy system:running-config nvram:
startup-config command) after entering the mls cef maximum-routes command. See the Examples
section for additional information.
Examples This section contains examplse of the msl cef maximum-routes command. The fields shown in the
display are self-explanatory.
This example shows the display after you have entered the mls cef maximum-routes command, saved
the change (copy system:running-config nvram: startup-config command), and rebooted the system:
Router# show mls cef maximum-routes
This example shows the display if you entered the mls cef maximum-routes command and did not save
the change:
Router# show mls cef maximum-routes
This example shows the output if you have made a configuration change and saved the change (copy
system:running-config nvram: startup-config command):
Router# show mls cef maximum-routes
show mls cef mpls [detail] [internal] [labels value] [module number] [vpn instance]
[vrf instance]
Command History 12.2(17a)SX Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples This examples shows how to display MPLS entries. The fields shown in the display are self-explanatory.
Router# show mls cef mpls
Syntax Description ip (Optional) Displays IP entries in the MLS-hardware Layer 3-switching table; see the
Usage Guidelines section for additional information.
ip-address (Optional) IP address.
module num (Optional) Displays the entries for a specific module.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
If you enter the show mls cef ip rpf command without arguments, the RPF global mode status is
displayed.
The output of the show mls cef ip rpf and the show mls cef rpf commands is identical.
Examples This example shows how to display the status of the RPF global mode. The fields shown in the display
are self-explanatory.
Router# show mls cef rpf
This example shows how to display the RPF information for a specific IP address. The fields shown in
the display are self-explanatory.
Router# show mls cef rpf 10.100.0.0
Syntax Description module number (Optional) Displays the information for a specific module.
Usage Guidelines In Cisco 7600 series routers that are configured with a Supervisor Engine 2 with a Policy Feature Card
(PFC) and a Multilayer Switching Feature Card 2 (MSFC2), Multilayer Switching (MLS)-hardware
Layer 3 switching provides IP unicast and IP multicast Layer 3 switching for a Supervisor Engine 2, a
PFC2, an MSFC2, and fabric-enabled switching modules that have a Distributed Forwarding Card
(DFC).
Examples This example shows how to display the MLS-hardware Layer 3-switching statistics. The fields shown in
the display are self-explanatory.
Router# show mls cef statistics
Syntax Description module number (Optional) Displays the information for a specific module.
Usage Guidelines The number of prefixes in the MLS-hardware Layer 3-switching table indicates the individual numbers
for IPv4 and IPv6 unicast, IPv4 multicast, Multiprotocol Label Switching (MPLS), and EoM routes.
For Cisco 7600 series routers that are configured with a Supervisor Engine 2, the output displays the
CEF-switched packets and total bytes.
When IPv6 is not configured, the command output from a Cisco Catalyst 6500 series switch running
Cisco IOS Release 12.2(33)SXI or a later release will show 255 IPv6 VRF routes.
12.2(33)SXI Example
This example shows the output from a Cisco Catalyst 6500 series switch running Cisco IOS
Release 12.2(33)SXI or a later release:
Router# show mls cef summary
Table 74 describes the fields in the show mls cef summary command output.
Field Description
Total MLS-hardware Number of MLS-hardware Layer 3-switching packets forwarded by the
Layer 3-switching MLS-hardware Layer 3-switching engine.
switched packets
Total MLS-hardware Number of bytes forwarded by the MLS-hardware Layer 3-switching engine.
Layer 3-switching
switched bytes
Total routes Number of route entries.
IP unicast routes Number of IP-unicast route entries.
IP VRF routes Number of virtual routing and forwarding (VRF) route entries.
IPX routes Number of Internetwork Packet Exchange (IPX) route entries.
IP multicast routes Number of IP-multicast route entries.
show mls cef vrf instance-name [prefix] [detail] [lookup ip-address] [module num]
[rpf [ip-address]]
Syntax Description instance-name VPN routing/forwarding instance name; valid values are from 0 to 4095.
prefix (Optional) Prefix of the entry to display.
detail (Optional) Displays the hardware-entry details.
lookup ip-address (Optional) Displays the longest prefix-match lookup entry for the specified
address.
module num (Optional) Displays the entries for a specific module.
rpf ip-address (Optional) Displays the unicast Reverse Path Forwarding (uRPF) check
information for the (optional) specified IP address.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
The show mls cef ip command displays the Cisco Express Forwarding entries in the default VRF. To
display specific (non-default) VRF entries, use the show mls cef [ip] vrf vrf-name command.
Examples This example shows how to display information about the VPN routing and forwarding instance
Cisco Express Forwarding table for a specific VRF name. The fields shown in the display are
self-explanatory.
Router# show mls cef vrf vpn-1
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Examples This example shows how to display the RPF Cisco Express Forwarding table entries. The fields shown
in the display are self-explanatory.
Router# show mls ip cef rpf-table
----------------------------------------------------------------------------
172.16.10.0/24 [0] Fa2/1, Fa2/2, Fa2/3, Fa2/4
172.16.20.0/24
172.16.30.0/24
10.10.0.0/16 [1] Gi1/1, Gi1/2
10.20.0.0/16
show mls ip non-static [count [module number] | detail [module number] | module number]
Syntax Description count (Optional) Displays the total number of nonstatic entries.
module number (Optional) Designates the module number.
detail (Optional) Specifies a detailed per-flow output.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Examples This sections contains examples from the show mls ip non-static command. The fields shown in the
display are self-explanatory.
This example shows how to display the software-installed nonstatic entries:
Router> show mls ip non-static
This example shows how to display detailed information for the software-installed nonstatic entries:
Router> show mls ip non-static detail
This example shows how to display the total number of software-installed nonstatic entries:
Router> show mls ip non-static count
Number of shortcuts = 0
Router>
show mls ip routes [non-static | static] [count [module number] | detail [module number] |
module number]
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Examples This section contains examples of the show mls ip routes non-static command. The fields shown in the
display are self-explanatory.
This example shows how to display the software-installed nonstatic routing entries:
Router> show mls ip routes non-static
This example shows how to display detailed information for the software-installed nonstatic routing
entries:
Router> show mls ip routes non-static detail
--------------------------------------------------------------------
Pkts Bytes Age LastSeen Attributes
---------------------------------------------------
Router>
This example shows how to display the total number of software-installed routing entries:
Router> show mls ip routes count
Number of shortcuts = 0
Router>
show mls ip static [count [module number] | detail [module number] | module number]
Syntax Description count (Optional) Displays the total number of static entries.
module number (Optional) Designates the module number.
detail (Optional) Specifies a detailed per-flow output.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor
Engine 2.
Examples This section contains examples from the show mls ip static command. The fields shown in the display
are self-explanatory.
This example shows how to display the software-installed static entries:
Router> show mls ip static
This example shows how to display detailed information for the software-installed static entries:
Router> show mls ip static detail
Router>
This example shows how to display the total number of software-installed static entries:
Router> show mls ip static count
Number of shortcuts = 0
Router>
show mls ip statistics [count [module number] | detail [module number] | module number]
Syntax Description count (Optional) Displays the total number of NetFlow entries.
module number (Optional) Displays the entries that are downloaded on the specified module.
detail (Optional) Specifies a detailed per-flow output.
Examples This section contains examples from the show mls ip statistics command. The fields shown in the
display are self-explanatory.
This example shows how to display statistical information for the NetFlow IP entries:
Router> show mls ip statistics
This example shows how to display detailed statistical information for the NetFlow IP entries:
Router> show mls ip statistics detail
Usage Guidelines You can enter the aggregate keyword to display the statistics for the NetFlow-creation failures and
NetFlow-hash aliases in the Supervisor Engine 720.
You can enter the aggregate keyword to display the page hits and misses in the Supervisor Engine 2.
The last reading of the corresponding registers are displayed in the summary and detailed keywords for
the Supervisor Engine 720.
Examples This section contains examples from the show mls table-contention command. The fields shown in the
display are self-explanatory.
This example shows how to display a detailed list of TCL information:
Router# show mls table-contention detailed
This example shows how to display an aggregate count of all missed flows in the Supervisor Engine 720
and page hits/misses in Supervisor Engine 2:
Router# show mls table-contention aggregate
Earl in Module 1
Detailed Table Contention Level Information
===========================================
Layer 3
-------
L3 Contention Level: 0
Page Hits Requiring 1 Lookup = 24000
Page Hits Requiring 2 Lookups = 480
Page Hits Requiring 3 Lookups = 0
Page Hits Requiring 4 Lookups = 0
Page Hits Requiring 5 Lookups = 0
Page Hits Requiring 6 Lookups = 0
Page Hits Requiring 7 Lookups = 0
Page Hits Requiring 8 Lookups = 0
Page Misses = 0
show monitor event-trace {all-traces [merged] {all | back {mmm | hhh:mm} | clock hh:mm [date
month | month date] | from-boot seconds | latest} | component {all | back {mmm | hhh:mm} |
clock hh:mm [date month | month date] | from-boot seconds | latest | parameters}} [detail]
Syntax Description all-traces (Optional) Displays all event trace messages in memory to the console.
merged (Optional) Displays all event traces entries sorted by time.
all Displays all event trace messages currently in memory.
back {mmm | hhh:mm} Specifies how far back from the current time you want to view messages.
For example, you can gather messages from the last 30 minutes. The time
argument is specified either in minutes or in hours and minutes format
(mmm or hh:mm).
clock hh:mm Displays event trace messages starting from a specific clock time in hours
and minutes format (hh:mm).
date (Optional) Day of the month.
month (Optional) Displays the month of the year.
from-boot seconds Displays event trace messages starting from a specified number of seconds
after booting (uptime). To display the uptime, in seconds, enter the
show monitor event-trace component from-boot ? command.
latest Displays only the event trace messages since the last show monitor
event-trace command was entered.
component (Optional) Name of the Cisco IOS software subsystem component that is
the object of the event trace. To get a list of components that support event
tracing in this release, use the monitor event-trace ? command.
parameters Displays the trace parameters. The only parameter displayed is the size
(number of trace messages) of the trace file.
detail (Optional) Displays detailed trace information.
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE.
The spa component keyword was added to support online insertion and
removal (OIR) event messages for shared port adapters (SPAs).
The bfd keyword was added for the component argument to display trace
messages relating to the Bidirectional Forwarding Detection (BFD) feature.
12.4(4)T Support for the bfd keyword was added for Cisco IOS Release 12.4(4)T.
12.0(31)S Support for the bfd keyword was added for Cisco IOS Release 12.0(31)S.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB and
implemented on the Cisco 10000 series routers.
12.4(9)T The cfd keyword was added as an entry for the component argument to
display trace messages relating to crypto fault detection.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(33)SB This command was integrated into Cisco IOS Release 12.2(33)SB.
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines Use the show monitor event-trace command to display trace message information.
The trace function is not locked while information is being displayed to the console, which means that
new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed,
some messages can be lost. If this happens, the show monitor event-trace command will generate a
message indicating that some messages might be lost; however, messages will continue to display on the
console. If the number of lost messages is excessive, the show monitor event-trace command will stop
displaying messages.
Use the bfd keyword for the component argument to display trace messages relating to the BFD feature.
Use the cfd keyword for the component argument to display trace messages relating to the crypto fault
detection feature. This keyword displays the contents of the error trace buffers in an encryption data path.
BFD Component for Cisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T
Use the show monitor event-trace bfd all command to display logged messages for important BFD
events in the recent past. The following trace messages show BFD session state changes:
Router# show monitor event-trace bfd all
To display trace information for all components configured for event tracing on the networking device,
enter the show monitor event-trace all-traces command. In this example, separate output is provided
for each event, and message numbers are interleaved between the events.
Router# show monitor event-trace all-traces
00:01:15.364: subslot 2/3: 4xOC3 POS SPA, TSM Event:inserted New state:wait_psm
_ready
spa type 0x440
00:02:02.308: subslot 2/0: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/0: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/1: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/1: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/2: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/2: not present, TSM Event:remove_complete New state:idle
00:02:02.312: subslot 2/3: not present(plugin 4xOC3 POS SPA), TSM Event:empty New
state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.312: subslot 2/3: not present, TSM Event:remove_complete New state:idle
The following example shows the IPv6 or IPv4 events related to the Cisco Express Forwarding
component. Each trace message is numbered and is followed by a time stamp (derived from the device
uptime). Following the time stamp is the component-specific message data.
Router# show monitor event-trace cef ipv6 all
In the following example, all event trace messages for the Cisco Express Forwarding component are
displayed:
Router# show monitor event-trace cef events all
Cisco Express Forwarding Component Examples for Cisco 10000 Series Routers Only
The following example shows the IPv4 events related to the Cisco Express Forwarding component. Each
trace message is numbered and is followed by a time stamp (derived from the device uptime). Following
the time stamp is the component-specific message data.
Router# show monitor event-trace cef ipv4 all
In the following example, all event trace message for the Cisco Express Forwarding component are
displayed:
Router# show monitor event-trace cef events all
Note If no packets have been dropped, this command does not display any output.
show monitor event-trace adjacency {{all | back trace-duration | clock hh:mm [date] [month] |
from-boot [seconds] | latest} [detail] | parameters}
Syntax Description all Displays all event trace messages in the current buffer.
back Specifies how far back from the current time you want to view messages. For
example, you can gather messages from the last 30 minutes.
trace-duration The time duration in hours and minutes format (mmm or hhh:mm).
clock hh:mm Displays event trace messages starting from a specified time in hours and
minutes format (hh:mm).
date (Optional) Day of the month from 1 to 31.
month (Optional) Month of the year.
from-boot Displays event trace messages starting after booting up (uptime).
seconds (Optional) The specified number of seconds following bootup (uptime) after
which event trace messages should start being displayed. The range is from
0 to 785.
latest Displays the latest trace events since last display.
detail (Optional) Displays detailed trace information.
parameters Displays the parameters configured for the trace.
Examples The following is sample output from the show monitor event-trace adjacency all command. The fields
are self-explanatory.
Router# show monitor event-trace adjacency all
*Aug 7 05:13:56.408: GLOBAL: adj system chunk pool created (element size 276) [OK]
*Aug 7 05:13:56.408: GLOBAL: adj system state change to adjacency system up [OK]
*Aug 7 05:13:56.408: GLOBAL: adj manager background process started [OK]
show monitor event-trace cef {all [detail] | back {minutes | hours:minutes} [detail] | clock
hours:minutes [day month] [detail] | from-boot [seconds] [detail] | latest [detail]
| merged {all [detail] | back {minutes | hours:minutes} [detail] | clock hours:minutes [day
month] [detail] | from-boot [seconds] [detail] | latest [detail]}}
Syntax Description all Displays all event trace messages currently in memory for Cisco Express
Forwarding.
detail (Optional) Displays detailed trace information.
back Specifies how far back from the current time you want to view messages. For
example, you can gather messages from the last 30 minutes.
minutes Specifies the time argument in minutes. The time argument is specified in
minutes format (mmm).
hours:minutes Specifies the time argument in hours and minutes. The time argument is
specified in hours and minutes format (hh:mm).
clock Displays event trace messages starting from a specific clock time in hours
and minutes format (hh:mm).
day month (Optional) The day of the month from 1 to 31 and the month of the year.
from-boot Displays event trace messages starting after booting (uptime).
To display the uptime, in seconds, enter the show monitor event-trace cef
from-boot ? command.
seconds (Optional) Displays event trace messages starting from a specified number
of seconds after booting (uptime). Range: 0 to 3369.
latest Displays only the event trace messages since the last show monitor
event-trace cef command was entered.
merged Displays entries in all event traces sorted by time.
Usage Guidelines Use the show monitor event-trace cef command to display trace message information for Cisco Express
Forwarding.
The trace function is not locked while information is displayed to the console, which means that new
trace messages can accumulate in memory. If entries accumulate faster than they can be displayed, some
messages can be lost. If this happens, the show monitor event-trace cef command generates a message
indicating that some messages might be lost; however, messages continue to display on the console. If
the number of lost messages is excessive, the show monitor event-trace cef command stops displaying
messages.
Examples The following is sample output from the show monitor event-trace cef all command:
Router# show monitor event-trace cef all
cef_events:
cef_interface:
The output is in table format where the first column contains a timestamp, the second column lists the
type of event, and the third column lists the detail for the event.
Table 75 describes the significant fields shown in the display.
Field Description
*Aug 22 20:14:58.999: A timestamp that indicates the month, day, and time when the event was
captured.
cef_events Indicates that messages about Cisco Express Forwarding events will
follow.
SubSys The event type that is related to the initialization of a subset of
functionality. For example, ipv4fib_ios_def_cap init is the initialization
of IPv4 Cisco Express Forwarding IOS default capabilities.
Inst The event type that records changes to an instance, such as changes to a
Route Processor (RP) or line card. For example, a change from unknown
to RP occurs at startup when the software detects what the instance is.
Flag The event type that records changes to Cisco Express Forwarding control
flags that handle what is running, for example, Common CEF enabled set
to yes.
GState The event type that notes changes to the Cisco Express Forwarding global
state: CEF enabled or CEF disabled.
Process The event type that records when Cisco Express Forwarding processes are
created, begin, or complete normal operations,
cef_interface Indicates that messages about Cisco Express Forwarding interface events
will follow.
Et0/0 Indicates that the following recorded event affects interface Ethernet 0/0.
(hw 3) The detail for this event is as follows:
SWvecLES <unknown> (hw3)The hardware interface descriptor block (idb) number for the
(0x01096A3C) interface
SWvecLESThe switching vector for this interface is changed to the
LES path
<unknown>The switching vector name is unknown
(0x01096A3C)The address in memory of the switching vector
The following is sample output from the show monitor event-trace cef latest command:
Router# show monitor event-trace cef latest
cef_events:
cef_interface:
Field Description
(sw15) The detail for this event is as follows:
FlagCha 0x60C1 add (sw 15)The software idb number for the interface.
puntLC FlagChaIndicates a Forwarding Information Base interface descriptor
block (fibidb) flag change for the interface.
0x60C1The flag field in hexadecimals after the change.
addFlags are added.
puntLCChanged flag or flagspuntLC is one flag that indicates
packets that are switched to this interface on the linecard are handled by
the next slower path (not switched by Cisco Express Forwarding).
State Indicates a change in state, for example when an interface goes from an up
state to a down state.
Create Indicates that an interface was created.
Nameset Indicates that the name of the interface changed.
RCFlags Indicates that a route cache change occured.
show monitor event-trace cef events {all [detail] | back {minutes | hours:minutes} [detail] | clock
hours:minutes [day month] [detail] | from-boot [seconds] [detail] | latest [detail] |
parameters}
Syntax Description all Displays all event trace messages currently in memory for Cisco Express
Forwarding.
detail (Optional) Displays detailed trace information.
back Specifies how far back from the current time you want to view messages. For
example, you can gather messages from the last 30 minutes.
minutes Time argument (mmm) in minutes.
hours:minutes Time argument (hh:mm) in hours and minutes. You must enter the colon (:)
in the argument.
clock Displays event trace messages starting from a specific clock time in hours
and minutes format (hh:mm).
day month (Optional) The day of the month from 1 to 31 and the name of the month of
the year.
from-boot Displays event trace messages starting after booting (uptime).
To display the uptime, in seconds, enter the show monitor event-trace cef
from-boot ? command.
seconds (Optional) Displays event trace messages starting from a specified number
of seconds after booting (uptime). Range: 0 to 3279.
latest Displays only the event trace messages generated since the last show
monitor event-trace cef command was entered.
parameters Displays parameters configured for the trace. The only parameter displayed
is the size (number of trace messages) of the trace file.
Usage Guidelines Use the show monitor event-trace cef events command to display trace message information about
events associated with Cisco Express Forwarding.
The trace function is not locked while information is being displayed to the console. This means that
new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed,
some messages can be lost. If this happens, the show monitor event-trace cef events command
generates a message indicating that some messages might be lost; however, messages continue to be
displayed on the console. If the number of lost message is excessive, the show monitor event-trace cef
events command stops displaying messages.
Examples The following is sample output from the show monitor event-trace cef events all command:
Router# show monitor event-trace cef events all
Field Description
*Aug 13 17:38:27.999: A time stamp that indicates the month, day, and time when
the event was captured.
SubSys The event type that is related to the initialization of a subset
of functionality. For example, ipv4fib_ios_def_cap init is
the initialization of IPv4 Cisco Express Forwarding IOS
default capabilities.
Inst The event type that records changes to an instance, such as
changes to a Route Processor (RP) or line card. For example,
a change from unknown to RP occurs at startup when the
software detects what the instance is.
Flag The event type that records changes to Cisco Express
Forwarding control flags that handle what is running, for
example, Common CEF enabled set to yes.
Table 77 show monitor event-trace cef events all Field Descriptions (continued)
Field Description
GState The event type that notes changes to the Cisco Express
Forwarding global state: CEF enabled or CEF disabled.
Process The event type that records when Cisco Express Forwarding
processes are created, begin, or complete normal operations,
show monitor event-trace cef interface {all [detail] | back {minutes | hours:minutes} [detail] |
clock hours:minutes [day month] [detail] | from-boot [seconds] [detail] | latest [detail] |
parameters | {hw | sw} interface-index {all [detail] | back {minutes | hours:minutes} [detail]
| clock hours:minutes [day month] [detail] | from-boot [seconds] [detail] | latest [detail]}}
Syntax Description all Displays all event trace messages currently in memory for Cisco Express
Forwarding.
detail (Optional) Displays detailed trace information for Cisco Express
Forwarding interface events.
back Specifies how far back from the current time you want to view messages. For
example, you can gather messages from the last 30 minutes.
minutes Time argument (mmm) in minutes.
hours:minutes Time argument (hh:mm) in hours and minutes. You must enter the colon (:)
in the argument.
clock Displays event trace messages starting from a specific clock time in hours
and minutes format (hh:mm).
day month (Optional) The day of the month from 1 to 31 and the name of the month of
the year.
from-boot Displays event trace messages starting after booting (uptime).
To display the uptime, in seconds, enter the show monitor event-trace cef
from-boot ? command.
seconds (Optional) Displays event trace messages starting from a specified number
of seconds after booting (uptime). Range: 0 to 4429.
latest Displays only the event trace messages generated since the last show
monitor event-trace cef command was entered.
parameter Displays parameters configured for the trace.
hw Displays trace events for the specified hardware interface index.
sw Displays trace events for the specified hardware interface index
interface-index Specifies the interface index. Range: 0 to 10000.
Release Modification
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines Use the show monitor event-trace cef interface to display trace message information about interface
events associated with Cisco Express Forwarding.
The trace function is not locked while information is displayed to the console. This means that new trace
messages can accumulate in memory. If entries accumulate faster than they can be displayed, some
messages can be lost. If this happens, the show monitor event-trace cef interface command generates
a message indicating that some messages might be lost; however, messages continue to be displayed on
the console. If the number of lost messages is excessive, the show monitor event-trace cef interface
command stops displaying messages.
Examples The following is sample output from the show monitor event-trace cef interface latest command:
Router# show monitor event-trace cef interface latest
Field Description
Et0/0 Indicates that the following recorded event affects interface
Ethernet 0/0.
(hw3) SWvecLES <unknown> The detail for this event is as follows:
(0x01096A3C)
(hw3)The hardware interface descriptor block (idb)
number for the interface
SWvecLESThe switching vector for this interface is
changed to the LES path
<unknown>The switching vector name is unknown
(0x01096A3C)The address in memory of the
switching vector
State Indicates a change in state, for example, when an interface
goes from the up state to the down state.
Create Indicates that an interface was created.
Nameset Indicates that the name of the interface changed.
RCFlags Indicates that a route cache change occurred.
FlagCha Indicates that a Forwarding Information Base interface
descriptor block (fibidb) flag changed for the interface.
show monitor event-trace cef ipv4 {{ip-address | vrf vrf-name ip-address} {all [detail] | back
{minutes | hours:minutes} [detail] | clock hours:minutes [day month] [detail] | from-boot
seconds [detail] | latest [detail]} | all [detail] | back {minutes | hours:minutes} [detail] | clock
hours:minutes [day month] [detail] | from-boot seconds [detail] | latest [detail] | parameters}
Release Modification
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines Use the show monitor event-trace cef ipv4 command to display trace message information for
Cisco Express Forwarding IPv4 events.
The trace function is not locked while information is displayed to the console. This means that new trace
messages can accumulate in memory. If entries accumulate faster than they can be displayed, some
messages can be lost. If this happens, the show monitor event-trace cef ipv4 command generates a
message indicating that some messages might be lost; however, messages continue to be displayed on
the console. If the number of lost messages is excessive, the show monitor event-trace cef ipv4
command stops displaying messages.
Examples The following is sample output from the show monitor event-trace cef ipv4 all command:
Router# show monitor event-trace cef ipv4 all
Field Description
*Aug 22 20:14:59.075: Time stamp that indicates the month, day, and time when the
event was captured.
[Default] *.*.*.*/* Identifies the default VRF.
Allocated FIB table [OK] Provides the event detail and indicates if the event happened
or if it was ignored ([Ignr]). In this instance, a FIB table was
allocated.
Add source Default table Indicates that a source for the Default table was added.
Following is sample output from the show monitor event-trace cef ipv4 parameters command:
Router# show monitor event-trace cef ipv4 parameters
Field Description
Trace has 1000 entries The size of the event logging buffer is 1000 entries.
Stacktrace is disabled by default Stack trace at tracepoints is disabled.
Matching all events Event tracing for all events is matched.
show monitor event-trace cef ipv6 {ipv6-address {all [detail] | back {minutes | hours:minutes}
[detail] | clock hours:minutes [day month] [detail] | from-boot seconds [detail] | latest
[detail]} | all [detail] | back {minutes | hours:minutes} [detail] | clock hours:minutes [day
month] [detail] | from-boot seconds [detail] | latest [detail] | parameters}
Syntax Description ipv6-address Specifies an IPv6 address. This address must be specified in hexadecimals
using 16-bit values between colons, as specified in RFC 2373.
all Displays all event trace messages currently in memory for Cisco Express
Forwarding IPv6 events.
detail (Optional) Displays detailed trace information for Cisco Express
Forwarding IPv6 events.
back Specifies how far back from the current time you want to view messages. For
example, you can gather messages from the last 30 minutes.
minutes Time argument (mmm) in minutes.
hours:minutes Time argument (hh:mm) in hours and minutes. You must enter the colon (:)
in the argument.
clock Displays event trace messages starting from a specific clock time in hours
and minutes format (hh:mm).
day month (Optional) The day of the month from 1 to 31 and the name of the month of
the year.
from-boot Displays event trace messages starting after booting (uptime).
To display the uptime, in seconds, enter the show monitor event-trace cef
from-boot ? command.
seconds (Optional) Displays event trace messages starting from a specified number
of seconds after booting (uptime). Range: 0 to 3279.
latest Displays only the event trace messages generated since the last show
monitor event-trace cef ipv6 command was entered.
parameters Displays parameters configured for the trace.
Usage Guidelines Use the show monitor event-trace cef ipv6 command to display trace message information for
Cisco Express Forwarding IPv6 events.
The trace function is not locked while information is displayed to the console. This means that new trace
messages can accumulate in memory. If entries accumulate faster than they can be displayed, some
messages can be lost. If this happens, the show monitor event-trace cef ipv6 command generates a
message indicating that some messages might be lost; however, messages continue to be displayed on
the console. If the number of lost messages is excessive, the show monitor event-trace cef ipv6
command stops displaying messages.
Examples The following is a sample of the show monitor event-trace cef ipv6 all command:
Router# show monitor event-trace cef ipv6 all
Field Description
*Aug 22 20:14:59.075: Time stamp that indicates the month, day, and time when the
event was captured.
[Default] *::*/* Identifies the default VRF.
Allocated FIB table [OK] Provides the event detail and indicates if the event happened.
In this instance, a FIB table was allocated.
The following is sample output from the show monitor event-trace cef ipv6 parameters command:
Router# show monitor event-trace cef ipv6 parameters
Field Description
Trace has 1000 entries The size of the event logging buffer is 1000 entries.
Stacktrace is disabled by default Stack trace at tracepoints is disabled.
Matching all events Event tracing for all events is matched.
Examples The following is sample output from the show monitor event-trace continuous command. The fields
are self-explanatory.
Router# show monitor event-trace continuous
show monitor event-trace cpu-report {brief {all | back {mmm | hhh:mm} | clock hh:mm [date
month | month date] | from-boot [seconds] | latest} [detail] | handle handle-number}
Usage Guidelines Use the show monitor event-trace cpu-report command with the brief keyword to display the CPU
report details. To display individual snapshots, use the show monitor event-trace cpu-report handle
handle-number command.
To display the uptime, in seconds, enter the show monitor event-trace cpu-report from-boot ?
command.
Examples To display CPU report details for event tracing on a networking device, enter the show monitor
event-trace cpu-report brief all command. The field descriptions are self-explanatory.
Router# show monitor event-trace cpu-report brief all
To display CPU report details for event tracing on a networking device for the handle number 1, enter
the show monitor event-trace cpu-report handle 1 command. The field descriptions are
self-explanatory.
Router# show monitor event-trace cpu-report handle 1
58 1 15192/15192
112 1 15192/15192
117 1 15192/15192
99 1 15172/15172
47 1 15172/15172
97 1 15172/15172
################################################################################
Global Statistics
-----------------
5 sec CPU util 0%/0% Timestamp 00:00:00
Queue Statistics
----------------
Exec Count Total CPU Response Time Queue Length
(avg/max) (avg/max)
Critical 0 0 0/0 0/0
High 0 0 0/0 0/0
Normal 0 0 0/0 0/0
Low 0 0 0/0 0/0
show monitor event-trace hw-api {{all | back time | clock time day month | from-boot [time] |
latest} [detail] | parameters}
Syntax Description all Displays all event traces in the current buffer.
back Displays trace from a specific time far back in the past.
time Duration of trace in the format mmm or hhh:mm.
clock Displays trace from a specific clock time and date.
time Time in the format hh:mm.
day Day of the month.
month Month of the year.
from-boot Displays trace from specified seconds after booting.
time (Optional) Time after boot in seconds. Valid range is 0 to 217696.
latest Displays latest trace events since last display.
detail (Optional) Displays detailed trace information.
parameters Displays the parameters of the trace.
Examples The following is sample output from the show monitor event-trace hw-api all command. The fields are
self-explanatory.
Router# show monitor event-trace hw-api all
0.000
*Jan 14 17:42:25.207: bwalk at 000756FC rpflst 014B1450
0.000
*Jan 14 17:42:25.207: bwalk as 00075600 fibidb Ethernet0/0
0.000
*Jan 14 17:42:25.207: bwalk at 000756FC fibidb Ethernet0/0
0.000
*Jan 14 17:42:25.207: bwalk as 00075600 adj Et0/0 IP 192.168.1.1 0
0.000
*Jan 14 17:42:25.207: bwalk at 000756FC adj Et0/0 IP 192.168.1.1 0
0.000
*Jan 14 17:42:25.207: bwalk as 00075600 rpflst 014B1450
0.000
*Jan 14 17:42:25.207: bwalk at 000756FC rpflst 014B1450
0.000
*Jan 14 17:42:25.207: bwalk as 00075600 adj Et0/0 IP 192.168.1.1 0
Syntax Description trace-buffer-name Name of the trace buffer. You can specify up to four trace buffers.
Examples The following is sample output from the show monitor event-trace merged-list command. The output
displays event trace information for the lists cef_interface and licnvram, sorted by time. The fields are
self-explanatory.
Router# show monitor event-trace merged-list list1 cef_interface licnvram
Usage Guidelines You can display information about the interface types shown in Table 83 using the show pxf accounting
command:
Examples The following is sample output from the show pxf accounting ? command:
Router# show pxf accounting ?
The following is sample output from the show pxf accounting ethernet command with an Ethernet
interface in slot 4 on a Cisco 7200 VXR series router:
Router# show pxf accounting ethernet 4/0
The following is sample output from the show pxf accounting null command with a null interface in
slot 0 on a Cisco 7200 VXR series router:
Router# show pxf accounting null 0/0
The following is sample output from the show pxf accounting pos command with a
Packet-over-SONET interface in slot 4 on a Cisco 7200 VXR series router:
Router# show pxf accounting pos
The following is sample output from the show pxf accounting serial command with a serial interface
in slot 5 on a Cisco 7200 VXR series router:
Router# show pxf accounting serial 5/0
The following is sample output from the show pxf accounting summary command:
Router# show pxf accounting summary
PXF Statistic:
Packets RP -> PXF:
switch ip: 0
switch raw: 30048360
qos fastsend: 0
qos enqueue: 1938
Total: 30050298
show pxf cpu access-lists [security [ [tcam acl-name [detail] ] | flex-sum | children] | qos | pbr |
compiled]
Syntax Description security (Optional) Displays information about the security ACLs defined in
Cisco IOS and compiled to the PXF. Also displays information about split
ACLs, such as how much memory has been used.
tcam acl-name (Optional) Displays information about the specified security ACL stored in
ternary content addressable memory (TCAM).
This option is only available on the PRE3 for the Cisco 10000 series router.
detail (Optional) Displays decoded information about the packet fields used for
matching in the TCAM.
flex-sum (Optional) Displays summary information describing the amount of memory
allocated in the parallel express forwarding (PXF) engine for use by the
flexible key construction microcode. This information is useful for design
teams.
This option is only available on the PRE3 for the Cisco 10000 series router.
children (Optional) Displays information for child policies. If an ACL is a template
child, the output typically does not display the child information. Specifying
the children keyword displays data for child policies, too, and shows the
children and the parent policy of each child.
Use caution when using the children keyword as there might be thousands
of child policies configured, which could have negative effects on the
command output.
qos (Optional) Displays information about the QoS ACLs defined in Cisco IOS
and compiled to the PXF.
pbr (Optional) Displays information about ACLs for policy-based routing (PBR).
compiled (Optional) Displays information for all compiled Turbo-ACLs.
The PRE2 supports Turbo-ACLs and the compiled option. The PRE3
accepts the PRE2 compiled option, but does not implement Turbo-ACLs.
Examples The sample output from the show pxf cpu access-lists security command (see Sample Output) is based
on the configuration of the access control list (ACL) called test_list (see ACL Configuration). The
sample output is divided into several sections with a description of the type of information displayed in
each.
ACL Configuration
Router# show pxf cpu access-lists test_list
Sample Output
The following sample output describes the information displayed in the first section of the command
output from the show pxf cpu access-lists security command:
Router# show pxf cpu access-lists security
Table 84, Part 1, describes the significant fields shown in the display.
Table 84, Part 1 show pxf cpu access-lists security Field Descriptions
Field Description
ACL Identifies the ACL by name or number.
State Displays the current state of the ACL:
CopyingACL is in the process of being created or
compiled.
OperationalACL is active and filtering packets.
Out of acl private memACL has run out of the private
memory that was allocated exclusively to it.
Out of shared memACL has run out of the memory
that it shares with other ACLs.
Unknown FailureACL has failed because of an
uncategorized reason.
UnneededACL was allocated but is not currently in
use.
Tables An indicator of whether the ACL has been split into more
than one PXF pass. The first three ACLs in the output are
MiniACLs, and have the ACL_index duplicated in the Tables
column.
Entries The count of ACL rules as seen by the Turbo compiler. This
is the sum of the Config, Fragment, and Redundant columns
plus 1.
Config The count of rules for this ACL.
Fragment The count of extra rules added to handle fragment handling,
where Layer 4 information is needed but not available in a
packet fragment.
Redundant The count of rules that are not needed because they are
covered by earlier rules.
Memory The amount of PXF XCM in use for the ACL.
ACL_index The index of the ACL in XCM.
The following sample output describes the information displayed in the next section of the command
output from the show pxf cpu access-lists security command:
First level lookup tables:
Block Use Rows Columns Memory used
0 TOS/Protocol 1/128 1/32 16384
1 IP Source (MS) 1/128 1/32 16384
2 IP Source (LS) 1/128 1/32 16384
3 IP Dest (MS) 2/128 1/32 16384
4 IP Dest (LS) 12/128 1/32 16384
5 TCP/UDP Src Port 1/128 1/32 16384
6 TCP/UDP Dest Port 1/128 1/32 16384
7 TCP Flags/Fragment 1/128 1/32 16384
Table 84, Part 2, describes the significant fields shown in the display.
Table 84, Part 2 show pxf cpu access-lists security Field Descriptions
Field Description
Block Indicates the block number.
Use Describes the IP packet field that is being matched.
Rows An indication of where the largest variety of values are in use
in the ACLs that are being applied. In the output, 12/128
means that there are 12 different values of significance in the
field. If there are other rules added and the value exceeds 128,
more memory will be needed to accommodate the new rules.
Columns An indication of the number of TurboACLs in PXF memory.
In the output, 1/32 means there is only one TurboACL in PXF
memory. If there are more than 31 added, another chunk of
memory is needed to accommodate the new ACLs.
Memory used Displays the total amount of memory used for this particular
lookup table.
The following sample output describes the information displayed in the next section of the command
output from the show pxf cpu access-lists security command. There are 16 banks of XCM in each PXF
column. This output section shows the usage level of each bank.
Table 84, Part 3, describes the significant fields shown in the display.
Table 84, Part 3 show pxf cpu access-lists security Field Descriptions
Field Description
Banknum The block of memory used for this particular lookup table.
Heapsize The total amount of memory, in bytes, allocated for this
block.
Freesize The amount of memory, in bytes, that is currently available
for use by this block of memory.
%Free The percentage of memory that is free and available for use for
this block of memory. When the %Free drops to 0, the router
cannot hold any more ACLs in PXF memory, and any new
ACL will not pass traffic.
This section of the sample command output indicates the memory usage of the MiniACLs in the router.
All of the rows state about the same thing. To determine the actual number of MiniACLs in play, divide
the memory used in any of blocks 1 to 10 by 256, or blocks 11 to 14 by 16.
The following describes the information displayed in the last section of the sample output from the show
pxf cpu access-lists security command:
Available MiniACL count = 8191
Usable ranges(inclusive):
1->8191
Table 84, Part 4, describes the significant fields shown in the display.
Table 84, Part 4 show pxf cpu access-lists security Field Descriptions
Field Description
Available MiniACL The number of ACLs currently available for allocation in
XCM.
Usable ranges The ACL indexes that will be assigned to MiniACLs.
PRE2 and PRE3 Security ACLs Examples (Cisco 10000 Series Router)
This section compares the output from the show pxf cpu access-lists security command when issued on
the PRE2 and PRE3.
For the PRE2, the following sample output displays VMR (value, plus a mask and result) data for the
ACL named ICMP_IGMP_MATCH:
Router# show pxf cpu access-lists security tcam ICMP_IGMP_MATCH detail
-------------------------------------------------------------
VMR Format - handle: 524607B4
Format has 5 fields, refcount = 1
Field: Format, FIXED, start_bit = 69, end_bit = 71
Field: ACL index, FIXED, start_bit = 54, end_bit = 68
Field: Flags, FIXED, start_bit = 43, end_bit = 53
Field: L4 proto, FIXED CNV, start_bit = 16, end_bit = 23
Field: L4 source port, FIXED CNV, start_bit = 0, end_bit = 15 Total bits = 53, format = 72
GMR used: 5 Col 2 LKBP Vector: 544
-------------------------------------------------------------
VMRs
------ VMR 0 ------
V: 001B0000 0000010B 00
M: FFFFC000 0000FFFF FF
R: 00010001
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00000B00/0000FFFF
L4 proto: 00000001/000000FF
Flags: 00000000/00000000
------ VMR 1 ------
V: 001B0000 00000103 01
M: FFFFC000 0000FFFF FF
R: 00010002
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00000301/0000FFFF
L4 proto: 00000001/000000FF
Flags: 00000000/00000000
------ VMR 2 ------
V: 001B0000 00000213 00
M: FFFFC000 0000FFFF 00
R: 00010003
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00001300/0000FF00
L4 proto: 00000002/000000FF
Flags: 00000000/00000000
------ VMR 3 ------
V: 001B0000 00000214 00
M: FFFFC000 0000FFFF 00
R: 00010004
Format: 00000000/00000007
ACL index: 0000006C/00007FFF
L4 source port: 00001400/0000FF00
L4 proto: 00000002/000000FF
Flags: 00000000/00000000
For the PRE3, the following sample output displays for the show pxf cpu access-lists security
command. Notice that the output does not include the columns shown above that are relevant to only the
PRE2 and the output no longer displays first-level lookup tables.
Router# show pxf cpu access-lists security
Examples The following example shows AToM forwarding information for Gigabit Ethernet interface 6/0/0. The
fields shown in the display are self-explanatory.
Router#: show pxf cpu atom gigabitethernet 6/0/0
Examples The following example shows BBA groups information in the PXF CPU:
Router# show pxf cpu bba
6w3d: show_pxf_bba
6w3d: %IPCOIR-4-REPEATMSG: IPC handle already exists for 1/0
6w3d: %IPCOIR-2-CARD_UP_DOWN: Card in slot 1/0 is down. Notifying 4oc3atm-1 dr.
6w3d: %C10K_ALARM-6-INFO: ASSERT CRITICAL slot 1 Card Stopped Responding OIR Al
6w3d: %IPCOIR-5-CARD_DETECTED: Card type 4oc3atm-1 (0x2D8) in slot 1/0
6w3d: %IPCOIR-5-CARD_LOADING: Loading card in slot 1/0 sw version 1.1 code MD5 C
6w3d: %C10K-5-LC_NOTICE: Slot[1/0] 4oc3atm-1 Image Downloaded...Booting...
6w3d: %IPCOIR-5-CARD_DETECTED: Card type 4oc3atm-1 (0x2D8) in slot 1/0
6w3d: %C10K_ALARM-6-INFO: CLEAR CRITICAL slot 1 Card Stopped Responding OIR Ala
6w3d: %IPCOIR-2-CARD_UP_DOWN: Card in slot 1/0 is up. Notifying 4oc3atm-1 driv.
Usage Guidelines This command provides information about the number of handles that are used and available. Handles
are outstanding packets in the virtual time management system (VTMS).
Examples The following example shows the number of handles that are used and available:
Router# show pxf cpu buffers
Field Description
pool Identifies the buffer pool.
# handles The number of handles that are currently used.
available The number of handles that are currently available.
Examples The show pxf cpu context command shows how busy the PXF forwarding process (FP) is with the
current traffic load. The first section displays the number of contexts of each type that have entered the
PXF engine since it was last reloaded. If counters are idle, the PXF pipeline is not operating properly.
Router# show pxf cpu context
FP context statistics count rate (since last time command was run)
--------------------- ------------- ----------
feed_back 168635 0
new_work_from_lc 7474477 13
new_work_from_rp 964679 1
new_work_from_replay 0 0
null_context 3797097495884 6312156
----------
6312170
FP average context/sec 1min 5min 60min
--------------------- ---------- ---------- ----------
feed_back 0 0 0 cps
new_work_from_lc 8 8 8 cps
new_work 1 1 1 cps
new_work_from_replay 0 0 0 cps
null_context 6312260 6312261 6312250 cps
--------------------- ---------- ---------- ----------
Total 6312270 6312271 6312260 cps
Field Description
FP context statistics
feed_back Packets requiring additional passes through the pipeline. This
counter is incremented once for each additional pass.
new_work New packets input to the PXF pipeline. This counter
represents a snapshot of the amount of incoming traffic being
processed by the processor.
null_context An indication of unused forwarding bandwidth (idle time).
This counter is incremented for every context during which the
PXF pipeline is not processing traffic. This counter represents
the processors potential to handle additional traffic. As the
processor becomes more busy, the value for null decreases until
it becomes zero, at which point the processor has reached its
maximum usage.
FP average context/sec
feed_back Displays the rate, in terms of the number of contexts per
second (cps) for the feed_back counter for the last 1-minute,
5-minute, and 60-minute time periods.
new_work Displays the rate, in terms of the number of contexts per second
(cps) for the new_work counter for the last 1-minute, 5-minute,
and 60-minute time periods.
null_context Displays the rate, in terms of the number of contexts per second
(cps) for the null_counter for the last 1-minute, 5-minute, and
60-minute time periods.
FP context utilization
Actual Displays the actual percentage of processor usage per second,
compared to the theoretical maximum, for the last 1-minute,
5-minute, and 60-minute time periods.
Theoretical Displays the percentage of processor usage compared to the
ideal theoretical capacities for the last 1-minute, 5-minute, and
60-minute time periods. The theoretical maximum for the PXF
processors is 3,125,000 contexts per second (cps).
Maximum Displays the actual maximum percentage of processor usage
that has occurred for the last 1-minute, 5-minute, and 60-minute
time periods.
Load for five secs: 5%/0%; one minute: 6%; five minutes: 2%
Time source is hardware calendar, *21:13:02.615 UTC Tue Nov 29 2005
Syntax Description detail (Optional) Displays detailed information about policies and templates.
policy policy-name (Optional) Displays summary policy information.
template (Optional) Displays summary template information.
Examples The following example shows PXF template information. The fields shown in the display are
self-explanatory.
Router# show pxf cpu iedge template
show pxf cpu ipv6 [ipv6: address [prefix] | acl-prefixes | hash | summary]
show pxf cpu ipv6 [acl-prefixes | address | hash | summary | table | vrf]
Syntax Description ipv6: address [prefix] (Optional) Specifies the IPv6 address and optional IPv6 prefix for the
information you want to display.
acl-prefixes (Optional) Displays access control list (ACL) prefixes mapping information.
address (Optional) Displays PXF IPv6 address-specific information.
hash (Optional) Displays hash table summary information.
summary (Optional) Displays a summary of the PXF IPv6 statistics.
table (Optional) Displays detailed information about the PXF IPv6 forwarding
table.
vrf (Optional) Displays PXF IPv6 VRF information.
Syntax Description labels label-value (Optional) Displays the transport type and output features associated with
the specified label value or label range. The label-value range is 0 to 524288.
vrf (Optional) Displays virtual routing and forwarding (VRF) root information.
Examples The following example shows VRF root information. The fields shown in the display are
self-explanatory.
Router# show pxf cpu mpls vrf
Syntax Description [ipaddress1] (Optional) Displays PXF mroute information for a particular group or range
[ipaddress2] of groups.
In : 0 0x000004
In : 0 0x000008
Field Description
Interface Interface or subinterface.
vcci Virtually Cool Common Index (VCCI) for the interface or
subinterface.
rw index Index used to read and write into the multicast table for this
entry.
mac_header MAC header that is used when rewriting the packet for
output.
Syntax Description action map-name (Optional) Displays PBR action information and redirects the command
output to the route map you specify.
tcam map-name (Optional) Displays VMR (value, plus a mask and result) information stored
in ternary content addressable memory (TCAM) and redirects the command
output to the route map you specify.
Note This option is only available on the PRE3 for the Cisco 10000 series
router.
flex-sum (Optional) Displays summary information describing the amount of memory
allocated in the PXF engine for use by the flexible key construction
microcode. This information is useful for design teams.
Note This option is only available on the PRE3 for the Cisco 10000 series
router.
Usage Guidelines This command is useful to determine if an adjacency has been found for a set ip next-hop ip-address
route map configuration command.
Examples The following example shows the PBR route maps configured in the PXF:
Router# show pxf cpu pbr action foo
The following sample output from the show pxf cpu pbr command shows the type of information that
displays based on the above PBR configuration:
Router# show pxf cpu pbr action pbr_length
----------------------------------------------------------------------
Policy number: 3
......................................................................
map number = 1
action index = 65
map vcci out = 0x0
tt_pkt_count = 0 tt_byte_count = 0
......................................................................
The following sample output from the show pxf cpu pbr tcam command shows the type of detailed
VMR (value, plus a mask and result) information that displays:
Router# show pxf cpu pbr tcam pbr_length detail
-------------------------------------------------------------
VMR Format - handle: 5050BC90
Format has 5 fields, refcount = 1
Field: Format, FIXED, start_bit = 69, end_bit = 71
Field: ACL index, FIXED, start_bit = 54, end_bit = 68
Field: Flags, FIXED, start_bit = 43, end_bit = 53
Field: L4 proto, FIXED CNV, start_bit = 16, end_bit = 23
Field: Unknown, FLEX, start_bit = 0, end_bit = 15 Total bits = 53, format = 72 GMR used: 0
Col 3 LKBP Vector: 96C
Status: Running
-------------------------------------------------------------
VMRs
------ VMR 0 ------
V: 7000C000 00000600 70
M: FFFFD800 0000FFFF F0
R: 80000104
Format: 00000003/00000007
ACL index: 00004003/00007FFF
L4 proto: 00000006/000000FF
Flags: 00000000/00000300
Packet Length: 00000070/0000FFF0
------ VMR 1 ------
V: 7000C000 00000600 68
M: FFFFD800 0000FFFF F8
R: 80000104
Format: 00000003/00000007
ACL index: 00004003/00007FFF
L4 proto: 00000006/000000FF
Flags: 00000000/00000300
Packet Length: 00000068/0000FFF8
------ VMR 2 ------
V: 7000C000 00000600 64
M: FFFFD800 0000FFFF FC
R: 80000104
Format: 00000003/00000007
ACL index: 00004003/00007FFF
L4 proto: 00000006/000000FF
Flags: 00000000/00000300
Packet Length: 00000064/0000FFFC
.
.
.
------ VMR 18 ------
V: 7000C000 00000000 00
M: FFFFC000 00000000 00
R: 80000110
Format: 00000003/00000007
ACL index: 00004003/00007FFF
L4 proto: 00000000/00000000
Flags: 00000000/00000000
Packet Length: 00000000/00000000
Syntax Description policy-map-name (Optional) Policy for which you want to display PXF policing statistics.
Usage Guidelines If a policy name is not specified, the command displays policing statistics for all policy maps.
Examples The following example shows the PXF policing statistics for a policy called policetest. The fields shown
in the display are self-explanatory.
Router# show pxf cpu police policetest
Policy policetest:
Class: police_class
Interface VCCI 0x9DD Output Policy:
police 8000 8000 15000 conform-action transmit exceed-action drop violate-action drop
Class: class-default
*** No police action ***
Examples The following example shows PXF policy data which is information related to the number of classes in
a policy and the reservation of unique indexes to support match statistics and token buckets. Policy data
index statistics are related to free match statistics indexes. Exhaustion of these indexes means no more
policies can be created in the router. Secondary policy data indexes are related to free token bucket
indexes. The fields shown in the display are self-explanatory.
Router# show pxf cpu policy-data
The Group size field is the number of policy classes. The Chunk count field is the number of blocks the
group holds.
show pxf cpu qos [vcci | classifiers | flex-sum | policy-map policy-name | vcci-maps]
Syntax Description vcci (Optional) Virtual Channel Circuit Identifier (VCCI). Information about this
specified VCCI will be displayed.
classifiers (Optional) Displays information about the criteria used to classify traffic.
flex-sum (Optional) Displays summary information describing the amount of memory
allocated in the PXF engine for use by the flexible key construction
microcode.
Note This option is only available on the Cisco 10000 series router for the
PRE3.
policy-map (Optional) Displays per-policy map information.
policy-name
vcci-maps (Optional) Displays VCCI map values.
Usage Guidelines This command is useful in verifying the presence of a policy on interfaces and indexes programmed in
the PXF.
Examples The following example shows XCM contents related to a policy called police_test, which is defined as
follows:
policy-map police_test
class high-priority
priority
class low-priority
set atm-clp
class class-default
queue-limit 512
Syntax Description interface (Optional) The interface for which you want to display PXF queueing
statistics. This displays PXF queueing statistics for the main interface and all
subinterfaces and permanent virtual circuits (PVCs). It also displays packets
intentionally dropped due to queue lengths.
QID (Optional) The queue identifier.
summary (Optional) Displays queue scaling information such as:
Number of queues and recycled queues.
Number of available queue IDs (QIDs).
Number of packet buffers, recycled packet buffers, and free packet
buffers.
Usage Guidelines When neither the interface or QID is specified, the command displays queuing statistics for the route
processors (RPs).
In Cisco IOS Release 12.2(33)SB and later releases, the output from the show pxf cpu queue interface
summary command displays only the physical interface and the number of logical links. The output
does not display the number of priority queues, class queues, and so on. This modification applies to the
PRE3 and PRE4.
Cisco uBR10012 Universal Broadband Router
If dynamic bandwidth sharing (DBS) is enabled, the link queue information that is displayed refers to
the specific type of interface that is configuredmodular cable or wideband cable. The summary
keyword option is not supported for the Cisco uBR10012 universal broadbandrRouter for wideband
cable or modular cable interfaces. The ATM interface output is not available for this router.
See Table 88 for descriptions of the interface keyword fields.
Field Description
<0-131071> QID (queue identifier)
ATM Asynchronous transfer mode interface
Note The ATM interface output is not available for the
Cicso uBR10012 universal broadband router.
BVI Bridge-group virtual interface
Bundle Cable virtual bundle interface
CTunnel CTunnel interface
Cable Cable modem termination service (CMTS) interface
DTI Digital trunk interface
Dialer Dialer interface
Ethernet IEEE 802.3
FastEthernet FastEthernet IEEE 802.3
GigabitEthernet GigabitEthernet IEEE 802.3z
Group-Async Async group interface
Loopback Loopback interface
MFR Multilink frame relay bundle interface
Table 88 show pxf cpu queue Interface Option Field Descriptions (continued)
Field Description
Modular-Cable Modular cable interface
Multilink Multilink group interface
Null Null interface
Port-channel Ethernet channel of interfaces
RP Forwarding path (FP) to route processing (RP) queues
Tunnel Tunnel interface
Vif Pragmatic general multicast (PGM) host interface
Virtual-Template Virtual template interface
Virtual-TokenRing Virtual token ring
WB-SPA line card to line card (LC-LC) queues
Wideband-Cable Wideband CMTS interface
Examples The following example shows PXF queueing statistics for an ATM interface when a QID is not
specified. The sample output includes the dropped and dequeued packets for the VCs, and for classes
associated with sessions that inherit queues from VCs.
Router# show pxf cpu queue atm 5/0/2
VCCI 2517: ATM non-aggregated VC 1/229, VCD 1, Handle 1, Rate 500 kbps
VCCI 2520: ATM non-aggregated VC 1/232, VCD 3, Handle 3, Rate 500 kbps
VCCI 2519: ATM non-aggregated VC 1/231, VCD 2, Handle 2, Rate 500 kbps
The following example displays PXF queuing statistics for QID 267:
Router# show pxf cpu queue 267
ID : 267
Priority : Lo
CIR (in-use/configured) : 0/65535
EIR (in-use/configured) : 0/0
MIR (in-use/configured) : 0/65535
Maximum Utilization configured : no
Link : 2
Flowbit (period/offset) : 32768/32768
Burst Size : 1024 bytes
Bandwidth : 133920 Kbps
Channel : 0
Packet Descriptor Base : 0x00000100
ML Index : 0
Length/Average/Alloc : 0/0/32
Enqueues (packets/octets) : 293352/9280610
Dequeues (packets/octets) : 293352/9280610
Drops (tail/random/max_threshold) : 0/0/0
Drops (no_pkt_handle/buffer_low) : 0/0
WRED (weight/avg_smaller) : 0/0
WRED (next qid/drop factor) : 0/0
WRED (min_threshold/max_threshold/scale/slope):
precedence 0 : 0/0/0/0
precedence 1 : 0/0/0/0
precedence 2 : 0/0/0/0
precedence 3 : 0/0/0/0
precedence 4 : 0/0/0/0
precedence 5 : 0/0/0/0
precedence 6 : 0/0/0/0
precedence 7 : 0/0/0/0
Link Queues :
QID CIR(act/conf) EIR MIR RF Chan. Status
420 19661/19661 1/1 65535/65535 0 Inactive
Link Queues :
QID CIR(act/conf) EIR MIR RF Chan. Status
419 32768/32768 1/1 65535/65535 0 Inactive
566 19661/19661 1/1 65535/65535 1 Inactive
The following example shows service flow queue information for modular cable interfaces.
Router# show pxf cpu queue modular-cable 1/2/0:0
* CIR Queues
Examples The following example shows reassembly summary information. The fields shown in the display are
self-explanatory.
Router# show pxf cpu reasm_index summary
show pxf cpu statistics [atom | backwalk | clear | diversion | drop [interface | vcci] | ip | ipv6 |
l2tp | mlp | qos [interface] | queue | rx [vcci] | security | arp-filter | drl [ cable-wan-ip |
wan-non-ip ]]
show pxf cpu statistics diversion [ pxf [interface {interface | vcci}] | top number]
Syntax Description atom (Optional) Displays Any Transport over MPLS (AToM) statistics.
backwalk (Optional) Displays backwalk requests statistics.
clear (Optional) Clears PXF CPU statistics.
diversion (Optional) Displays packets that the PXF diverted to the Route Processor
(RP) for special handling.
drop [interface] [vcci] (Optional) Displays packets dropped by the PXF for a particular interface or
Virtual Circuit Connection Identifier (VCCI).
ip (Optional) Displays IP statistics.
ipv6 (Optional) Displays IPv6 statistics.
l2tp (Optional) Displays packet statistics for an L2TP Access Concentrator (LAC)
(Optional) and L2TP Network Server (LNS).
mlp (Optional) Displays multilink PPP (MLP) statistics.
pxf (Optional) Displays packets that the PXF diverted to the Route Processor
(RP). Available on the Cisco 10000 series router only.
pxf interface interface (Optional) Displays per-interface PXF statistical information for the divert
cause policer on a particular interface. Available on the Cisco 10000 series
router only.
pxf interface vcci (Optional) Displays per-VCCI PXF statistical information for the divert
cause policer on a particular Virtual Circuit Connection Identifier (VCCI).
Available on the Cisco 10000 series router only.
qos [interface] (Optional) Displays match statistics for a service policy on an interface.
queue (Optional) Displays queueing counters for all interfaces.
rx [vcci] (Optional) Displays receive statistics for a VCCI.
security (Optional) Displays ACL matching statistics.
top number (Optional) Displays PXF statistical information for the number of top
punters you specify. Available on the Cisco 10000 series router only. Valid
values are from 1 to 100.
arp-filter (Optional) Displays the ARP filter statistics.
drl (Optional) Displays the divert rate limit.
cable-wan-ip (Optional) Displays cable / wan-ip statistics for dropped packets.
wan-non-ip (Optional) Displays DRL wan-non-ip statistics for dropped packets.
Examples The following example shows PXF queueing counters information. These are aggregate counters for all
interfaces. The Total column is the total for all columns.
Note If you are troubleshooting link utilization issues, the deq_vtp_req, deq_flow_off, and
deq_ocq_off counters may indicate what is causing the versatile time management scheduler
(VTMS) to slow down.
If you are troubleshooting overall PXF throughput issues, look at the High Next Time, Low Next
Time, High Wheel Slot, and Low Wheel Slot counters.
dbg Counters 0 1 2 3 4 5 6 7
Total
============= ========== ========== ========== ========== ========== ========== ========== ==========
==========
enq_pkt 0x0000FD9B 0x0000FC77 0x0000FE4A 0x0000FF81 0x0000FC53 0x0000FD2E 0x0000FF19 0x0000FDDE
0x0007EE55
tail_drop_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
deq_pkt 0x0000FD47 0x0000FEF2 0x0000FCB3 0x0000FF65 0x0000FCE7 0x0000FC45 0x0000FEE7 0x0000FDF1
0x0007EE55
deq_vtp_req 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
deq_flow_off 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
deq_ocq_off 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
enqdeq_conflict 0x0000003A 0x00000043 0x0000004A 0x00000039 0x0000003A 0x0000004F 0x00000036 0x00000031
0x000001F0
bndl_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
frag_pkt 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg_frag_drop 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg_bndl_sem 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
context_inhibit 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
bfifo_enq_fail 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg1 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg2 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg3 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000
dbg6 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
0x0000
dbg7 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
dbg Counters 0 1 2 3 4 5 6 7
Total
Field Description
Column 6 Enqueue/Dequeue Counters by Rows:
enq_pkt Packets the PXF enqueued.
tail_drop_pkt Packets the PXF tails dropped.
deq_pkt Packets the PXF dequeued.
deq_vtp_req Number of times a dequeue was inhibited due to the virtual
traffic policer.
deq_flow_off Numbers of times a dequeue was inhibited due to a flowoff
from the line card.
deq_ocq_off Number of times a dequeue was inhibited due to link level
flow control.
enqdeq_conflict Shows a dequeue failed due to an enqueue to the same queue
in progress.
bndl_pkt Count of packets that were fragmented.
frag_pkt Count of fragments sent.
dbg_frag_drop Count of invalid multilink PPP (MLP) fragment handles.
dbg_bndl_sem Count of semaphone collision (used for MLP).
Field Description
context_inhibit Number of times multilink transmit fragment processing was
inhibited due to a lack of DMA resources.
bfifo_enq_fail Count of bundle FIFO (BFIFO) enqueue failures.
Column 7 Rescheduling State Counters by Rows:
High Next Time Current next send time for the high priority wheel.
Low Next Time Current next send time for the low priority wheel.
High Wheel Slot Current high priority slot number.
Low Wheel Slot Current low priority slot number.
DEQ_WHEEL Count of successful dequeues from the timing wheel.
DQ-lock Fails Count of timing wheel dequeue failures (both queue empty
and race conditions).
TW ENG Fails Timing wheel enqueue failures.
Q_SCHED Count of queues scheduled/rescheduled onto the timing
wheel.
FAST_SCHED Count of queues fast scheduled/rescheduled onto the timing
wheel.
Q_DEACT Count of queue deactivations.
Q_ACTIVATE Count of queue activations (activate state).
Q_CHANGE Count of queue changes; for example, Route Processor (RP)
inspired rates changes.
Note For L2TP Access Concentrator (LAC) operation, all statistics are applicable. For L2TP Network Server
(LNS) operation, only the PPP Control Packets, PPP Data Packets, and PPP Station Packets statistics are
meaningful.
The following example displays match statistics for the police_test policy on an ATM interface. The
Classmap Index differentiates classes within a policy while the Match Number differentiates match
statements within a class.
Router# show pxf cpu statistics qos atm 6/0/0.81801
class-default (1) 0 0 0
Examples The following example shows subblocks information for Gigabit Ethernet interface 7/0/0:
Router# show pxf cpu subblocks g7/0/0
GigabitEthernet7/0/0 is up
ICB = 1C000, LinkId = 6, interface PXF, enabled
link next_send: 0x37022604 channel number: 0
link bandwidth mult: 33467 shift: 22
link bandwidth mult: 33467 shift: 22
link aggregate cir: 0x00000000 aggregate eir: 0x00000000
IOS encapsulation type 1 ARPA
Min mtu: 14 Max mtu: 1528
VCCI maptable location = A3340000
VCCI 9D3 (802.1Q VLAN 1)
icmp ipaddress 0.0.0.0 timestamp 0
fib_root 0x0, fib_root_rpf 0x0 cicb_flags 0x00, flags/netmask 0x02
VCCI 9DB (802.1Q VLAN 1)
icmp ipaddress 0.0.0.0 timestamp 0
fib_root 0x0, fib_root_rpf 0x0 cicb_flags 0x00, flags/netmask 0x02
Field Description
Interface Identifies the interface or subinterface.
Status Displays the status of the interface:
AdministThe interface has been shut down and is in
the administrative down state.
DeletedThe subinterface has been removed from the
router's configuration.
DownThe interface is down because of a cable or other
connectivity problem.
InitialiThe interface is in the process of initializing.
ResetThe interface is currently being reset.
UpThe interface is up and passing traffic.
ICB Displays the Interface Control Block (ICB) that is mapped to
this interface.
WQB_ID Displays the Work Queue Block (WQB) identifier for the
interface.
Fwding Displays whether traffic is being forwarded (PXF) or not
(disable).
Field Description
Enc Identifies the type of encapsulation used on the interface. The
most common encapsulation types are:
0 = None
1 = Ethernet ARPA
2 = Ethernet SAP
3 = 802.2 SNAP
5 = Serial, raw HDLC
8 = Serial, LAPB
9 = Serial, X.25
20 = Frame Relay
21 = SMDS
22 = MAC-level packets
27 = Logical Link Control (LLC) 2
28 = Serial, SDLC (primary)
30 = Async SLIP encapsulation
33 = ATM interface
35 = Frame Relay with IETF encapsulation
42 = Dialer encapsulation
46 = Loopback interface
51 = ISDN Q.921
59 = DOCSIS (previously known as MCNS)
61 = Transparent Mode
62 = TDM clear channel
64 = PPP over Frame Relay
65 = IEEE 802.1Q
67 = LAPB terminal adapter
68 = DOCSIS Cable Modem
VCCI-map Displays the memory address for the Virtually Cool Common
Index (VCCI) map table for this particular VCCI.
VCCI Identifies the VCCI, in hexadecimal, assigned to the interface
or subinterface.
VC Identifies the virtual circuit (VC).
Usage Guidelines The VCCI is an index that uniquely identifies each interface or subinterface in the PXF and it maps that
interface to the appropriate set of services and features. This command is useful to verify the number of
VCCIs that are used and available.
The Cisco 10000 series router has 65,536 VCCIs. A VCCI is assigned to each individual routed interface.
A VCCI is not assigned to virtual template interfaces and loopbacks.
Examples The following example shows how to display the number of used and available VCCIs. The fields shown in
the display are self-explanatory.
Router# show pxf cpu vcci summary
Examples The following example shows crash information as a result of a PXF direct memory access (DMA) error.
The PXF crash information is typically stored in bootflash.
Router# show pxf crash
Summary of bootflash:pxf_crashinfo_20060117-152035
PXF DMA Error - End of Descriptor Before Cmd Byte Length Exhausted
Current microcode:
file=system:pxf/c10k2-11-ucode.108.0.0.0,
version=108.0.0.0,
description=Nightly Build Software created Sat 19-Nov-05 00:12
Field Description
Summary of bootflash: Displays the filename in bootflash where the PXF crash
information is stored. The filename format includes the date
and time of the PXF crash.
Time of crash Displays the date of the PXF crash.
Field Description
UTC Displays the Universal Coordinated Time (UTC) of the PXF
crash.
Current microcode Displays identifying information for the microcode currently
running on the PXF.
Field Description
Descriptor Address Memory address pointing to the descriptor for this buffer.
Buffer Address Address of this buffer in memory.
Buffer Length Length, in bytes, of this particular buffer.
Descriptor Flags Internal flags identifying this buffers use and status.
Context Bit State of the context bit which is set when the buffer is
currently in use by a context (the basic unit of packet
processing).
Examples The following is sample output from the show pxf feature cef command. The fields shown in the display
are self-explanatory.
Router# show pxf feature cef entry
Usage Guidelines Use this command to display VRF PXF routing feature tables for a specified VPN for Cisco Express
Forwarding. This command also displays information about prefix and MTRIE resource usage.
Examples The following is sample output for the show pxf feature cef vrf command when it is used to display
information about VRF vpn1:
Router# show pxf feature cef vrf vpn1
Field Description
Shadow 8-8-4-4-8 PXF Mtrie MTRIE lookup table index structures.
51 leaves All created leaves for all MTRIEs.
2448 leaf bytes Leaf byte counter. When a new leaf is created, the leaf byte
counter is incremented by the size of the leaf structure.
92 nodes All created nodes for all MTRIEs.
56352 node bytes Node byte counter. When a new node is created, the node
byte counter is incremented.
10 invalidations Invalidations counter. When a route (represented by a leaf) is
deleted from an MTRIE, the invalidations counter is
incremented. This counter includes all MTRIEs.
61 prefix updates IP prefix counter. When an IP prefix (represented by a leaf)
is added to the MTRIE, the IP prefix counter is incremented.
This counter includes all MTRIEs.
refcounts Counters associated with references between leaves.
3666 leaf MTRIEs have a leaf lock and a leaf free function. The leaf
lock function increments the leaf refcount. The leaf free
function decrements the leaf refcount. The leaf lock and leaf
free functions prevent a leaf from being freed (deleted) while
the leaf is still being referenced. This counter includes all
MTRIEs.
3733 node Node counter. When a child node is added to another node,
the node to which the child node is added becomes a parent
node. The node counter is decremented when a child node is
deleted. This counter includes all MTRIEs.
Prefix/Length The IP address and subnet mask of a leaf.
Refcount The number of leaves that reference a specified leaf. The
refcount counter is incremented when the leaf lock function
is called and decremented when the leaf free function is
called.
Parent When you add a less specific route to a more specific route,
the more specific route has a back pointer that points to the
less specific route.
Address The address of the memory for the specified leaf.
Shadow The shadow address in Route Processor memory for the
specified leaf.
Examples The following is sample output from the show pxf feature nat command. The fields shown in the
display are self-explanatory.
Router# show pxf feature nat
Usage Guidelines If you do not specify an interface, the command displays a summary of the statistics for all PXF
interfaces on the router.
Examples The following example shows PXF statistics for serial interface 1/0/0. The significant fields shown in
the display are self-explanatory.
Router# show pxf interface s1/0/0
Examples The following example shows the microcode version that is currently loaded on the PXF:
Router# show pxf microcode
Field Description
PXF complex The number of PXF processors, their associate memory
columns, and their current status.
Loaded microcode The source and filename for the microcode that is currently
loaded on the PXF processor.
Version The microcode version.
Field Description
Release Software created The time and date the current microcode was compiled.
Signature The signature in the microcode version.
Microcode load attempted The number of times the PXF processor has loaded the
microcode since the Cisco IOS image was loaded at system
boot. Also, shows the time (in days and hours) since the last
successful load of the microcode.
tmc# The current program counters and configuration for the PXF
processors.
Examples The following example shows the NetFlow PXF statistics. The fields shown in the display are
self-explanatory.
Router# show pxf netflow
show pxf stall-monitoring [counters | reset {active-status | cob-fib | cob-tib | pxf-drop} subslot
sub-slot]
Examples The following example displays a sample output of the show pxf stall-monitoring command:
Router# show pxf stall-monitoring
The following example displays a sample output of the show pxf stall-monitoring counters command:
Router# show pxf stall-monitoring counters
To RP Counters
==============
IOS To RP Counter = 20665
PXF To RP Drop Counter = 0
Current Counter Values
======================
Slot 0 Subslot 0 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 0 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 1 Subslot 0 Cob TIB = 2368 Cob FIB = 0 PXF Drop = 0
Slot 1 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 2 Subslot 0 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 2 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 3 Subslot 0 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 3 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 4 Subslot 0 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 4 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 5 Subslot 0 Cob TIB = 6162 Cob FIB = 6204 PXF Drop = 0
Slot 5 Subslot 1 Cob TIB = 6101 Cob FIB = 6065 PXF Drop = 0
Slot 5 Subslot 2 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 5 Subslot 3 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 7 Subslot 0 Cob TIB = 8402 Cob FIB = 8402 PXF Drop = 0
Slot 7 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 8 Subslot 0 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Slot 8 Subslot 1 Cob TIB = 0 Cob FIB = 0 PXF Drop = 0
Line Card Participant Status
============================
Slot 1 Subslot 0 = 1
Slot 1 Subslot 1 = 0
Slot 2 Subslot 0 = 0
Slot 2 Subslot 1 = 0
Slot 3 Subslot 0 = 0
Slot 3 Subslot 1 = 0
Slot 4 Subslot 0 = 0
Slot 4 Subslot 1 = 0
Slot 5 Subslot 0 = 0
Slot 5 Subslot 1 = 1
Slot 5 Subslot 2 = 0
Slot 5 Subslot 3 = 0
Slot 7 Subslot 0 = 1
Slot 7 Subslot 1 = 0
Slot 8 Subslot 0 = 1
Slot 8 Subslot 1 = 0
Line Card Active Status
=======================
Slot 1 Subslot 0 = 0
Slot 1 Subslot 1 = 0
Slot 2 Subslot 0 = 0
Slot 2 Subslot 1 = 0
Slot 3 Subslot 0 = 0
Slot 3 Subslot 1 = 0
Slot 4 Subslot 0 = 0
Slot 4 Subslot 1 = 0
Slot 5 Subslot 0 = 0
Slot 5 Subslot 1 = 1
Slot 5 Subslot 2 = 0
Slot 5 Subslot 3 = 0
Slot 7 Subslot 0 = 0
Slot 7 Subslot 1 = 0
Slot 8 Subslot 0 = 0
Slot 8 Subslot 1 = 0
The following example shows a summary of PXF statistics for dropped packets:
Router# show pxf statistics drop
The following example shows detailed PXF statistics for dropped packets:
Router# show pxf statistics drop detail
The following example shows summarized statistics for traffic diverted from the PXF:
Router# show pxf statistics diversion
Examples The following example shows XCM information for each PXF processor:
Router# show pxf xcm
Toaster 0:
Number of Columns: 2
Proc ID: 0x00000004 = TMC_X72
ASIC Revision: 0x00000001 = T3-ECC
XCM0 type:FCRAM, size = 67108864
ECC is enabled for column 0
XCM AB Config Register: 0x024703B9
XCM CD Config Register: 0x024703B9
XCM Exception Type Register: 0x00000000
FCRAM-A Counters
Number of ECC single bit errors: 0
FCRAM-B Counters
Number of ECC single bit errors: 0
FCRAM-C Counters
Number of ECC single bit errors: 0
FCRAM-D Counters
Number of ECC single bit errors: 0
XCM1 type:FCRAM, size = 67108864
ECC is enabled for column 1
XCM AB Config Register: 0x024703B9
XCM CD Config Register: 0x024703B9
XCM Exception Type Register: 0x00000000
FCRAM-A Counters
Number of ECC single bit errors: 0
FCRAM-B Counters
Number of ECC single bit errors: 0
FCRAM-C Counters
Number of ECC single bit errors: 0
FCRAM-D Counters
Number of ECC single bit errors: 0
Toaster 1:
Number of Columns: 2
Proc ID: 0x00000004 = TMC_X72
ASIC Revision: 0x00000001 = T3-ECC
FCRAM-B Counters
Number of ECC single bit errors: 0
FCRAM-C Counters
Number of ECC single bit errors: 0
FCRAM-D Counters
Number of ECC single bit errors: 0
Toaster 2:
Number of Columns: 2
Proc ID: 0x00000004 = TMC_X72
ASIC Revision: 0x00000001 = T3-ECC
XCM0 type:FCRAM, size = 67108864
ECC is enabled for column 0
XCM AB Config Register: 0x024703B9
XCM CD Config Register: 0x024703B9
XCM Exception Type Register: 0x00000000
FCRAM-A Counters
Number of ECC single bit errors: 0
FCRAM-B Counters
Number of ECC single bit errors: 0
FCRAM-C Counters
Number of ECC single bit errors: 0
FCRAM-D Counters
Number of ECC single bit errors: 0
XCM1 type:FCRAM, size = 67108864
ECC is enabled for column 1
XCM AB Config Register: 0x024703B9
XCM CD Config Register: 0x024703B9
XCM Exception Type Register: 0x00000000
FCRAM-A Counters
Number of ECC single bit errors: 0
FCRAM-B Counters
Number of ECC single bit errors: 0
FCRAM-C Counters
Number of ECC single bit errors: 0
FCRAM-D Counters
Number of ECC single bit errors: 0
Toaster 3:
Number of Columns: 2
Proc ID: 0x00000004 = TMC_X72
ASIC Revision: 0x00000001 = T3-ECC
XCM0 type:FCRAM, size = 67108864
ECC is enabled for column 0
XCM AB Config Register: 0x024703B9
Field Description
The following fields appear for each PXF processor.
Toaster # Identifies the PXF processor.
Number of Columns Displays the number of memory columns on the PXF
processor.
Proc ID Displays the processor type (TMC is Toaster Memory
Column).
ASIC Revision Displays the internal version number of the PXF processor.
The following fields appear for each XCM memory column.
XCM type Displays the type and size, in bytes, of memory used in this
particular column.
ECC is enabled for column Displays whether Error Code Correction (ECC) checking is
enabled or disabled for this memory column.
XCM Config Register and XCM Displays the contents of these two registers for the memory
Exception Type Register column.
Number of ECC single bit errors Displays the number of single-bit errors detected in memory.
Usage Guidelines This command displays the counts of one-way route map IPC messages from the RP to the VIP when
NetFlow policy routing is configured. If you execute this command on the RP, the messages are shown
as Sent. If you execute this command on the VIP console, the IPC messages are shown as Received.
Examples The following is sample output of the show route-map ipc command when it is executed on the RP:
Router# show route-map ipc
The following is sample output of the show route-map ipc command when it is executed on the VIP:
Router# show route-map ipc
Field Description
Route-map RP IPC Config Indicates that IPC messages are being sent from the RP to the VIP.
Updates Sent
Name Number of IPC messages sent about the name of the route map.
Match access-list Number of IPC messages sent about the access list.
Match length Number of IPC messages sent about the length to match.
Set precedence Number of IPC messages sent about the precedence.
Set tos Number of IPC messages sent about the type of service (ToS).
Set nexthop Number of IPC messages sent about the next hop.
Set interface Number of IPC messages sent about the interface.
Set default nexthop Number of IPC messages sent about the default next hop.
Set default interface Number of IPC messages sent about the default interface.
Clean all Number of IPC messages sent about clearing the policy routing
configuration from the VIP. When dCEF is disabled and reenabled,
the configuration related to policy routing must be removed
(cleaned) from the VIP before the new information is downloaded
from the RP to the VIP.
show xdr
To display details about eXternal Data Representation (XDR), use the show xdr command in user EXEC
or privileged EXEC mode.
Syntax Description client {client-name | all} Displays client basic information or statistics for a client or all clients.
statistics (Optional) Displays XDR statistics.
linecard (Line cards only) (Route/Switch Processor (RSP) on Cisco 7500 series and
Route Processor (RP) on Cisco 10000 series) Displays XDR information
for all XDR line card peer instances or the specified XDR line card peer
instance.
linecard-number (Optional) Specifies the line card slot number.
internal (Optional) (RSP only) Displays internal information.
multicast-group Displays XDR multicast groups.
timers Displays XDR timers.
Usage Guidelines This command is available only on distributed platforms (such as the Cisco 7500 series) and on the
Cisco 10000 series routers.
Examples The following example shows how to display XDR information for all clients:
Router# show xdr client all
The following example shows how to display XDR information for all XDR line card peer instances:
Router# show xdr linecard
The following example shows how to display XDR information for the XDR line card peer instance in
slot number 1:
Router# show xdr linecard 1
The following example shows how to display internal XDR information for the XDR line card peer
instance in slot number 1:
Router# show xdr linecard 1 internal
FIBIDB broker :
80 30960 0 0 fibidb update
FIBIDB Subblock brok:
10 315 0 0 fibswsb update
Adjacency update :
2 6 0 0 Adjacency update me
3 9 0 0 Adjacency repopulat
IPv4 table broker :
16 558 0 0 prefix
4 24 0 0 epoch
2 36 0 0 table
4 44 0 0 multicast prefix
IPv6 table broker :
1 18 0 0 table
CEF push :
12 72 19 114 repopulation req
0 0 1 12 isl table update rq
0 0 1 12 dot1q table updateq
2 10 0 0 state
9 452 0 0 control
1 3 0 0 flow features deace
1 22 0 0 flow cache config
1 40 0 0 flow export config
6 470 0 0 access-list config
2 10 0 0 access-list delete
1 12 0 0 route-map
1 16 0 0 icmp limit
1 8 0 0 SSM RP to LC commas
XDR ping :
3 12 3 12 ping message
The following is sample output from the show xdr multicast-group command:
Router# show xdr multicast-group
The following is sample output from the show xdr timers command:
Router# show xdr timers
XDR RP timers
Expiration Type
| 1:19.236 (parent)
| 1:19.236 Sending Time
| 4:59.236 Keepalive timer slot: 2
| 4:59.236 Keepalive timer slot: 1
| 4:59.248 Keepalive timer slot: 3
The following example shows how to display XDR information for all XDR line card peer instances:
Router# show xdr linecard
The following example shows how to display XDR information for the XDR line card peer instance in
slot number 1:
Router# show xdr linecard 1
The following example shows how to display internal XDR information for the XDR line card peer
instance in slot number 1:
Router# show xdr linecard 1 internal
Syntax Description seconds The time to allow before an inconsistency notification is sent during the process
of updating forwarding information from the Routing Information Base (RIB) to
the Route Processor (RP) and the line card databases. The valid values are from
0 to 3600 seconds.
Usage Guidelines Use this command in conjunction with the snmp-server enable traps cef inconsistency command to
set the time that elapsed between the occurrence of a Cisco Express Forwarding database inconsistencies
and the time when you want to receive an inconsistency notification.
If you set the throttling interval to 0 seconds, throttling is disabled.
Examples The following example shows how to set the throttling interval for CEF-MIB inconsistency notification
to 300 seconds:
configure terminal
!
snmp-server enable traps cef inconsistency
snmp mib cef throttling-interval 300
Syntax Description peer-state-change (Optional) Enables the sending of CEF-MIB SNMP notifications for
changes in the operational state of Cisco Express Forwarding peers.
resource-failure (Optional) Enables the sending of CEF-MIB SNMP notifications for
resource failures that affect Cisco Express Forwarding operations.
inconsistency (Optional) Enables the sending of CEF-MIB SNMP notifications for
inconsistencies that occur when routing information is updated from the
Routing Information Base (RIB) to the Cisco Express Forwarding
Forwarding Information Base (FIB) on the Route Processor (RP) and to the
Cisco Express Forwarding FIB on the line cards.
peer-fib-state-change (Optional) Enables the sending of CEF-MIB SNMP notifications for
changes in the operational state of the Cisco Express Forwarding peer FIB.
Usage Guidelines You can use this command to enable CEF-MIB SNMP notifications that correspond to specific
Cisco Express Forwarding events. To send the notifications to an NMS or host system, you must
configure the snmp-server host command with the cef keyword.
You can enable all CEF-MIB SNMP notifications if you enter the snmp-server enable traps cef
command without entering an optional keyword.
Examples The following example shows how to enable a router to send Cisco Express Forwarding peer state
changes and forwarding inconsistencies as informs to the NMS with IP address 10.56.125.47 and to use
the community string defined as public:
configure terminal
!
snmp-server enable traps cef peer-state-change inconsistency
snmp-server host 10.56.125.47 informs version 2c public
snmp-server host
To specify the recipient of a Simple Network Management Protocol (SNMP) notification operation, use
the snmp-server host command in global configuration mode. To remove the specified host from the
configuration, use the no form of this command.
Command Syntax on Cisco ME 3400, ME 3400E, and Catalyst 3750 Metro Switches
Syntax Description hostname Name of the host. The SNMP notification host is typically a network
management station (NMS) or SNMP manager. This host is the recipient of
the SNMP traps or informs.
ip-address IPv4 address or IPv6 address of the SNMP notification host.
vrf (Optional) Specifies that a Virtual Private Network (VPN) routing and
forwarding (VRF) instance should be used to send SNMP notifications.
In Cisco IOS Release 12.2(54)SE, the vrf keyword is required.
vrf-name (Optional) VPN VRF instance used to send SNMP notifications.
In Cisco IOS Release 12.2(54)SE, the vrf-name argument is required.
informs (Optional) Specifies that notifications should be sent as informs.
In Cisco IOS Release 12.2(54)SE, the informs keyword is required.
traps (Optional) Specifies that notifications should be sent as traps. This is the
default.
In Cisco IOS Release 12.2(54)SE, the traps keyword is required.
version (Optional) Specifies the version of the SNMP that is used to send the traps
or informs. The default is 1.
In Cisco IOS Release 12.2(54)SE, the version keyword is required and
the priv keyword is not supported.
If you use the version keyword, one of the following keywords must be
specified:
1SNMPv1.
2cSNMPv2C.
3SNMPv3. The most secure model because it allows packet
encryption with the priv keyword. The default is noauth.
One of the following three optional security level keywords can follow
the 3 keyword:
authEnables message digest algorithm 5 (MD5) and Secure Hash
Algorithm (SHA) packet authentication.
noauthSpecifies that the noAuthNoPriv security level applies to
this host. This is the default security level for SNMPv3.
privEnables Data Encryption Standard (DES) packet encryption
(also called privacy).
community-string Password-like community string sent with the notification operation.
Note You can set this string using the snmp-server host command by
itself, but Cisco recommends that you define the string using the
snmp-server community command prior to using the snmp-server
host command.
Note The at sign (@) is used for delimiting the context information.
udp-port (Optional) Specifies that SNMP traps or informs are to be sent to an NMS
host.
In Cisco IOS Release 12.2(54)SE, the udp-port keyword is not
supported.
port (Optional) User Datagram Protocol (UDP) port number of the NMS host.
The default is 162.
In Cisco IOS Release 12.2(54)SE, the port argument is not supported.
notification-type (Optional) Type of notification to be sent to the host. If no type is specified,
all available notifications are sent. See the Notification-Type Keywords
section on page 455 in the Usage Guidelines section for more information
about the keywords available.
Command Default This command behavior is disabled by default. A recipient is not specified to receive notifications.
Release Modification
12.0(22)S All features in Cisco IOS Release 12.0ST were integrated into Cisco
IOS Release 12.0(22)S.
The mpls-vpn notification-type keyword was added.
12.0(23)S The l2tun-session notification-type keyword was added.
12.0(26)S The memory notification-type keyword was added.
12.0(27)S Support for SNMP over IPv6 transport was added. Either an IP or IPv6
Internet address can be specified as the hostname argument.
The vrf vrf-name keyword and argument combination was added to
support multiple Lightweight Directory Protocol (LDP) contexts for
VPNs.
12.0(31)S The l2tun-pseudowire-status notification-type keyword was added.
Release 12.2S
12.2(18)S This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(25)S The cpu notification-type keyword was added.
The memory notification-type keyword was added.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2 The cef notification-type keyword was added.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(33)SB This command was integrated into Cisco IOS Release 12.2(33)SB.
12.2(33)SXI5 The dhcp-snooping notification-type keyword was added.
The errdisable notification-type keyword was added.
12.2(54)SE This command was modified. See the Command Syntax on Cisco ME 3400,
ME 3400E, and Catalyst 3750 Metro Switches section on page 450 for the
command syntax for these switches.
Cisco IOS Release 15S
15.0(1)S This command was modified. The flowmon notification-type keyword was
added.
Cisco IOS XE
Cisco IOS XE This command was integrated into Cisco IOS XE Release 2.1.
Release 2.1
Usage Guidelines If you enter this command with no optional keywords, the default is to send all notification-type traps
to the host. No informs will be sent to the host.
The no snmp-server host command with no keywords disables traps, but not informs, to the host. To
disable informs, use the no snmp-server host informs command.
Note If a community string is not defined using the snmp-server community command prior to using this
command, the default form of the snmp-server community command will automatically be inserted
into the configuration. The password (community string) used for this automatic configuration of the
snmp-server community will be the same as that specified in the snmp-server host command. This
automatic command insertion and use of passwords is the default behavior for Cisco IOS
Release 12.0(3) and later releases.
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver
does not send acknowledgments when it receives traps. The sender cannot determine if the traps were
received. However, an SNMP entity that receives an inform request acknowledges the message with an
SNMP response protocol data unit (PDU). If the sender never receives the response, the inform request
can be sent again. Thus, informs are more likely than traps to reach their intended destination.
Compared to traps, informs consume more resources in the agent and in the network. Unlike a trap,
which is discarded as soon as it is sent, an inform request must be held in memory until a response is
received or the request times out. Also, traps are sent only once; an inform may be tried several times.
The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. To configure the router to
send SNMP notifications, you must enter at least one snmp-server host command. If you enter the
command with no optional keywords, all trap types are enabled for the host.
To enable multiple hosts, you must issue a separate snmp-server host command for each host. You can
specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap
or inform), each succeeding command overwrites the previous command. Only the last snmp-server
host command will be in effect. For example, if you enter an snmp-server host inform command for a
host and then enter another snmp-server host inform command for the same host, the second command
will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable command. Use
the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to
receive most notifications, at least one snmp-server enable command and the snmp-server host
command for that host must be enabled.
Some notification types cannot be controlled with the snmp-server enable command. Some notification
types are always enabled, and others are enabled by a different command. For example, the linkUpDown
notifications are controlled by the snmp trap link-status command. These notification types do not
require an snmp-server enable command.
The availability of a notification-type options depends on the router type and the Cisco IOS software
features supported on the router. For example, the envmon notification type is available only if the
environmental monitor is part of the system. To see what notification types are available on your system,
use the command help ? at the end of the snmp-server host command.
The vrf keyword allows you to specify the notifications being sent to a specified IP address over a
specific virtual routing and forwarding (VRF) VPN. The VRF defines a VPN membership of a user so
that data is stored using the VPN.
In the case of the NMS sending the query having a correct SNMP community but that does not have a
read or a write view, the SNMP agent returns the following error values:
For a get or a getnext query, returns GEN_ERROR for SNMPv1 and AUTHORIZATION_ERROR
for SNMPv2C.
For a set query, returns NO_ACCESS_ERROR.
Notification-Type Keywords
The notification type can be one or more of the following keywords:
Note The available notification types differ based on the platform and Cisco IOS release. For a
complete list of available notification types, use the question mark (?) online help function.
mpls-ldpSends MPLS Label Distribution Protocol (LDP) notifications indicating status changes
in LDP sessions.
mpls-traffic-engSends MPLS traffic engineering notifications indicating changes in the status of
MPLS traffic engineering tunnels.
mpls-vpnSends MPLS VPN notifications.
msdpSends SNMP Multicast Source Discovery Protocol (MSDP) notifications.
mvpnSends multicast VPN notifications.
nhrpSends Next Hop Resolution Protocol (NHRP) notifications.
ospfSends Open Shortest Path First (OSPF) sham-link notifications.
pimSends Protocol Independent Multicast (PIM) notifications.
port-securitySends SNMP port-security notifications.
power-ethernetSends SNMP power Ethernet notifications.
pw-vcSends SNMP pseudowire virtual circuit (VC) notifications.
repeaterSends standard repeater (hub) notifications.
resource-policySends CISCO-ERM-MIB notifications.
rfSends SNMP RF MIB notifications.
rogue-apSends an SNMP 802.11 Rogue AP trap.
rsrbSends remote source-route bridging (RSRB) notifications.
rsvpSends Resource Reservation Protocol (RSVP) notifications.
rtrSends Response Time Reporter (RTR) notifications.
sdlcSends Synchronous Data Link Control (SDLC) notifications.
sdllcSends SDLC Logical Link Control (SDLLC) notifications.
slbSends SNMP server load balancer (SLB) notifications.
snmpSends any enabled RFC 1157 SNMP linkUp, linkDown, authenticationFailure, warmStart,
and coldStart notifications.
Note To enable RFC 2233-compliant link up/down notifications, you should use the snmp server
link trap command.
Examples If you want to configure a unique SNMP community string for traps but prevent SNMP polling access
with this string, the configuration should include an access list. The following example shows how to
name a community string comaccess and number an access list 10:
Router(config)# snmp-server community comaccess ro 10
Router(config)# snmp-server host 192.20.2.160 comaccess
Router(config)# access-list 10 deny any
Note The at sign (@) is used as a delimiter between the community string and the context in which it is
used. For example, specific VLAN information in BRIDGE-MIB may be polled using
community@VLAN-ID (for example, public@100), where 100 is the VLAN number.
The following example shows how to send RFC 1157 SNMP traps to a specified host named
myhost.cisco.com. Other traps are enabled, but only SNMP traps are sent because only snmp is specified
in the snmp-server host command. The community string is defined as comaccess.
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com comaccess snmp
The following example shows how to send the SNMP and Cisco environmental monitor
enterprise-specific traps to address 192.30.2.160 using the community string public:
Router(config)# snmp-server enable traps snmp
Router(config)# snmp-server enable traps envmon
Router(config)# snmp-server host 192.30.2.160 public snmp envmon
The following example shows how to enable the router to send all traps to the host myhost.cisco.com
using the community string public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com public
The following example will not send traps to any host. The BGP traps are enabled for all hosts, but only
the ISDN traps are enabled to be sent to a host. The community string is defined as public.
Router(config)# snmp-server enable traps bgp
Router(config)# snmp-server host myhost.cisco.com public isdn
The following example shows how to enable the router to send all inform requests to the host
myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
The following example shows how to send HSRP MIB informs to the host specified by the name
myhost.cisco.com. The community string is defined as public.
Router(config)# snmp-server enable traps hsrp
Router(config)# snmp-server host myhost.cisco.com informs version 2c public hsrp
The following example shows how to send all SNMP notifications to example.com over the VRF named
trap-vrf using the community string public:
Router(config)# snmp-server host example.com vrf trap-vrf public
The following example shows how to configure an IPv6 SNMP notification server with the IPv6 address
2001:0DB8:0000:ABCD:1 using the community string public:
Router(config)# snmp-server host 2001:0DB8:0000:ABCD:1 version 2c public udp-port 2012
The following example shows how to specify VRRP as the protocol using the community string public:
Router(config)# snmp-server enable traps vrrp
Router(config)# snmp-server host myhost.cisco.com traps version 2c public vrrp
The following example shows how to send all Cisco Express Forwarding informs to the notification
receiver with the IP address 192.40.3.130 using the community string public:
Router(config)# snmp-server enable traps cef
Router(config)# snmp-server host 192.40.3.130 informs version 2c public cef
The following example shows how to enable all NHRP traps, and how to send all NHRP traps to the
notification receiver with the IP address 192.40.3.130 using the community string public:
Router(config)# snmp-server enable traps nhrp
Router(config)# snmp-server host 192.40.3.130 traps version 2c public nhrp
Syntax Description number-of-restarts The number of PXF restarts that are allowed within the specified time
period. If the PXF processors restart this many times within the given time
period, the router switches over to the redundant PRE module. The valid
range is 1 to 25. The default is 2 PXF restarts within 5 hours.
time-period Time period, in hours, that PXF restart counts are monitored. The valid range
is 0 to 120 hours.
Note A value of 0 specifies that a switchover occurs on the configured
number-of-restarts regardless of the time period.
Command Default If this command is not configured, the default is 2 PXF restarts within 5 hours.
Usage Guidelines The startup and running configurations of the standby PRE are synchronized with the active PRE,
ensuring the fastest possible cut-over time if the active PRE fails. A second switchover is prevented for
2 hours if a PXF restart occurs on the new active PRE.
A PXF restart following a PXF fault may restore service more quickly when the features in use are not
configured for nonstop forwarding with stateful switchover (NSF/SSO), or when SSO mode is not configured
on the router. Conversely, a PRE switchover in response to a PXF restart may restore service more quickly
when NSF/SSO is configured on the router and all configured features support NSF/SSO.
When a switchover occurs because of repeated PXF restarts, the router displays the following system
message:
C10KEVENTMGR-3-PXF_FAIL_SWITCHOVER: Multiple PXF failures, switchover to redundant PRE
initiated.
Examples The following example shows how to configure the router so that if five PXF restarts occur within a
one-hour period, the router initiates a switchover to the redundant PRE module.
Router(config)# redundancy
Router(config-red)# main-cpu
Router(config-r-mc)# switchover pxf restart 5 1
Syntax Description detail (Optional) Displays detailed information about the consistency of prefixes
in the Cisco Express Forwarding FIB table.
Usage Guidelines This command displays recorded Cisco Express Forwarding consistency records found by the lc-detect,
scan-rib-ios, scan-ios-rib, scan-lc-rp, and scan-rp-lc detection mechanisms. The scan-lc-rp and
scan-rp-lc detection mechanisms are available only on routers with line cards.
You can configure the Cisco Express Forwarding prefix consistency-detection mechanisms using the cef
table consistency-check command.
Examples The following is sample output from the test cef table consistency command:
Router# test cef table consistency
The following is sample output from the test cef table consistency detail command:
Router# test cef table consistency detail
Field Description
FIB checked 12 prefixes, and The scan-rib-ios consistency checker checked 12 prefixes in the FIB
found 0 missing against the FIB and found 0 missing.
Checked 12 FIB prefixes in 1 The scan-ios-rib consistency checker checked 12 prefixes in the RIB
pass, and found 0 extra. and found no extra prefixes in one pass.
Linecard 4 checked 26 IPv4 The scan-rp-lc consistency checker found no inconsistencies on
prefixes (ignored 0). 0 line card 4 after checking 26 IPv4 prefixes.
inconsistent.