 Feedback
|
Table Of Contents
Cisco Express Forwarding: Command Changes
Information About Cisco Express Forwarding: Command Changes
How to Configure Cisco Express Forwarding: Command Changes
Configuration Examples for Cisco Express Forwarding: Command Changes
debug ip cef accounting non-recursive
show ip cef switching statistics
Feature Information for Cisco Express Forwarding: Command Changes
Cisco Express Forwarding: Command Changes
First Published: August 11, 2004Last Updated: August 21, 2007This feature module details changes to commands that are required to support updates to Cisco Express Forwarding.
In Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA and 12.2(33)SXH, Cisco Express Forwarding has been updated to support new features and new hardware. These updates enable Cisco Express Forwarding to operate with the Multiprotocol Label Switching (MPLS) High Availability (HA) applications and the MPLS Forwarding Infrastructure (MFI).
Cisco Express Forwarding provides a forwarding path and maintains a complete forwarding and adjacency table for both the software and hardware forwarding engines.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Cisco Express Forwarding: Command Changes" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About Cisco Express Forwarding: Command Changes
•
•
•
Information About Cisco Express Forwarding: Command Changes
Before using the Cisco Express Forwarding commands, you should understand the following concepts:
Deleted Commands
The following commands are obsolete and are no longer available from Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA and 12.2(33)SXH (no replacement commands are provided):
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Replaced Commands
Table 1 lists all replaced Cisco Express Forwarding commands, starting with Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA and 12.2(33)SXH, for the Cisco 7500 series routers:
Table 1 Replaced Cisco Express Forwarding Commands—Cisco 7500 Series Routers
ip cef table consistency-check
debug cef fib attached export
debug ip cef adjfib
ip cef
ip cef switch
monitor event-trace cef ipv4 clear
clear ip cef event-log
monitor event-trace cef linecard size
ip cef linecard event-log max-events
show adjacency nexthop
show cef drop
show cef not-cef-switched
show cef events
show monitor event-trace cef events
show ip cef events (still visible)
show monitor event-trace cef events all
show cef events [internal]
show monitor event-trace cef linecard
show cef linecard events
Table 2 lists all replaced Cisco Express Forwarding commands, starting with Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12.2(33)SRA and 12.2(33)SXH, for the Cisco 10000 series routers:
Table 2 Replaced Cisco Express Forwarding Commands—Cisco 10000 Series Routers
ip cef table consistency-check
debug cef fib attached export
debug ip cef adjfib
ip cef linecard event-log max-events
-
monitor event-trace cef ipv4 clear
clear ip cef event-log
show adjacency nexthop
NA
show cef drop
show cef events
show monitor event-trace cef events
show ip cef events (still visible)
show monitor event-trace cef events all
show cef events [internal]
-
show cef linecard events
How to Configure Cisco Express Forwarding: Command Changes
There are no configuration tasks for this feature.
Configuration Examples for Cisco Express Forwarding: Command Changes
There are no configuration examples for this feature.
Additional References
For additional information related to the Cisco Express Forwarding command changes, see the following references:
•
•
Related Documents
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section contains the following new and modified commands:
•
•
cef table consistency-check
To enable Cisco Express Forwarding table consistency checker types and parameters, use the cef table consistency-check command in global configuration mode. To disable consistency checkers, use the no form of this command.
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] [error-message] [auto-repair delay seconds holddown seconds] [data-checking]
no 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] [error-message] [auto-repair delay seconds holddown seconds] [data-checking]
Syntax Description
Defaults
All consistency checkers are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command replaces the ip cef table consistency-check command.
Examples
The following example enables the Cisco Express Forwarding consistency checker to check IPv4 addresses:
Router(config)# cef table consistency-check ipv4The 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 60The 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
Related Commands
clear adjacency
To clear the Cisco Express Forwarding adjacency table, use the clear adjacency command in privileged EXEC mode.
clear adjacency
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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.
For Cisco 7500 Routers
On a distributed system, the adjacency tables that reside on line cards are always synchronized to the adjacency table that resides on the Route/Switch Processor (RSP). Refreshing the adjacencies also refreshes adjacencies on line cards and purges stale entries. (Entering the clear adjacency command on a line card has no effect.)
Examples
The following example clears the adjacency table:
Router# clear adjacencyRelated Commands
clear cef linecard
To clear Cisco Express Forwarding information from line cards, use the clear cef linecard command in user EXEC or privileged EXEC mode.
clear cef linecard [slot-number] [adjacency | interface | prefix]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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, it's use is recommended only as a last resort for debugging or mitigating serious problems.
Note
Examples
The following example clears the Cisco Express Forwarding information from the line cards:
clear cef linecardRelated Commands
show cef linecard
Displays Cisco Express Forwarding-related interface information by line card.
clear cef table
To clear the Cisco Express Forwarding tables, use the clear cef table command in privileged EXEC mode.
clear cef table {ipv4 | ipv6} [vrf {vrf-name | * }]
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
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, it's 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
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 blue in the IPv4 address family:
Router# clear cef table ipv4 vrf blueThe 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 *06:56:01: FIBtable: Refreshing table IPv4:Default06:56:01: FIBtable: Invalidated 224.0.0.0/4 in IPv4:Default06:56:01: FIBtable: Deleted 224.0.0.0/4 from IPv4:Default06:56:01: FIBtable: Validated 224.0.0.0/4 in IPv4:Default06:56:01: FIBtable: IPv4: Event up, 9.1.41.0/24, vrf Default, 1 path, flags 0100022006:56:01: FIBtable: IPv4: Adding route for 9.1.41.0/24 but route already exists.Trying modify.06:56:01: FIBtable: IPv4: Event up, 10.0.0.11/32, vrf Default, 1 path, flags 0100000006:56:01: FIBtable: IPv4: Adding route for 10.0.0.11/32 but route already exists. Trying modify.06:56:01: FIBtable: IPv4: Event up, 10.0.0.15/32, vrf Default, 1 path, flags 0100000006:56:01: FIBtable: IPv4: Adding route for 10.0.0.15/32 but route already exists. Trying modify.06:56:01: FIBtable: IPv4: Event up, 10.0.0.7/32, vrf Default, 1 path, flags 0100022006:56:01: FIBtable: IPv4: Adding route for 10.0.0.7/32 but route already exists.Trying modify.06:56:01: FIBtable: IPv4: Event up, 10.0.0.0/8, vrf Default, 1 path, flags 0000022006:56:01: FIBtable: IPv4: Adding route for 10.0.0.0/8 but route already exists.Trying modify.06:56:01: FIBtable: IPv4: Event up, 0.0.0.0/0, vrf Default, 1 path, flags 0042000506:56:01: FIBtable: IPv4: Adding route for 0.0.0.0/0 but route already exists. Trying modify.06:56:01: FIBtable: Starting purge of table IPv4:Default to epoch 1306:56:01: FIBtable: Invalidated 10.1.41.1/32 in IPv4:Default06:56:01: FIBtable: Deleted 10.1.41.1/32 from IPv4:Default06:56:01: FIBtable: Purged 1 prefix from table IPv4:Default06:56:01: FIBtable: Validated 10.1.41.1/32 in IPv4:Default06:56:06: FIBtable: IPv4: Event modified, 0.0.0.0/0, vrf Default, 1 path, flags0042000506:56:06: FIBtable: IPv4: Event up, default, 0.0.0.0/0, vrf Default, 1 path, flags 0042000506:56:06: FIBtable: IPv4: Adding route for 0.0.0.0/0 but route already exists. Trying modify.Related Commands
clear ip cef inconsistency
To clear the Cisco Express Forwarding inconsistency checker statistics and records found by the Cisco Express Forwarding consistency checkers, use the clear ip cef inconsistency command in user EXEC or privileged EXEC mode.
clear ip cef inconsistency
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command clears the Cisco Express Forwarding inconsistency checker statistics and records that accumulate when the ip 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 inconsistencyRelated Commands
debug adjacency
To enable the display of information about the adjacency database, use the debug adjacency command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}]
no debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}]
Syntax Description
Defaults
Debugging events are not displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Also, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
You can use any combination of the prefix, interface, connectionid id, and link {ipv4 | ipv6 | mpls} keywords and arguments (in any order) as a filter to enable debugging for a specified subset of adjacencies.
Note
Examples
The following example shows how to display information on the adjacency database:
Router# debug adjacency*Jan 27 06:22:50.543: ADJ-ios_mgr: repopulate adjs on up event for Ethernet3/0*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: init/update from interface*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: set bundle to IPv6 adjacency oce*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: allocated, setup and inserted OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: source IPv6 ND added OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: computed macstring (len 14): OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 src IPv6 ND: made complete (macstring len 0 to 14/0 octets)00:04:40: %LINK-3-UPDOWN: Interface Ethernet3/0, changed state to up00:04:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/0, changedRelated Commands
debug cef
To enable the display of information about Cisco Express Forwarding events, use the debug cef command in privileged EXEC mode. To disable the display of Cisco Express Forwarding events, use the no form of this command.
debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr}
no debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr}
Syntax Description
Defaults
Debugging information about Cisco Express Forwarding events is not displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following is sample output from the debug cef all command:
Router# debug cef all06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:38: HW-API: Counter poll: Label[label=implicit-null]06:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rib-ios scanner' expired, calling 0x40FA03FC, context 0x00010003)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rib-ios scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-ios-rib scanner' expired, calling 0x40FA03FC, context 0x00010004)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-ios-rib scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-ios-rib scanner' expired, calling 0x40FA03FC, context 0x00020004)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-ios-rib scanner' withdelay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rp-lc scanner' expired, calling0x40FA03FC, context 0x00010002)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rp-lc scanner' with delay 6000006:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-rp-lc scanner' expired, calling0x40FA03FC, context 0x00020002)06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-rp-lc scanner' with delay 6000006:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:48: HW-API: Counter poll: Label[label=implicit-null]06:23:58: HW-API: Counter poll: Label[label=implicit-null]06:24:06: FIBtable: IPv4: Event modified, 0.0.0.0/0, vrf Default, 1 path, flags0042000506:24:06: FIBpath: Configuring IPv4 path 444B2AB0 from rib (idb=NULL, gw=9.1.41.1, gw_table=0, rr=1) and host prefix 0.0.0.006:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AB0 path06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null06:24:06: FIBtable: IPv4: Event up, default, 0.0.0.0/0, vrf Default, 1 path, flags 0042000506:24:06: FIBtable: IPv4: Adding route for 0.0.0.0/0 but route already exists. Trying modify.06:24:06: FIBpath: Configuring IPv4 path 444B2AA0 from rib (idb=NULL, gw=9.1.41.1, gw_table=0, rr=1) and host prefix 0.0.0.0sh ip06:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AA0 path06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null vrf06:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-hw-sw scanner' expired, calling0x40FA03FC, context 0x00010005)06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-hw-sw scanner' with delay 6000006:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-sw-hw scanner' expired, calling0x40FA03FC, context 0x00010006)06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-sw-hw scanner' with delay 60000Name Default RD Interfacesred 1:1 Ethernet4/0/5Related Commands
debug ip cef
To troubleshoot various Cisco Express Forwarding events, use the debug ip cef command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list] | interface | dialer}
no debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list] | interface | dialer}
Specific to Interprocess Communication (IPC) Records
debug ip cef {ipc | interface-ipc | prefix-ipc [access-list]}
no debug ip cef {ipc | interface-ipc | prefix-ipc [access-list]}
Cisco 10000 Series Routers Only
debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list]}
no debug ip cef {drops [rpf [access-list]] [access-list] | receive [access-list] | events [access-list]}
Cisco 10000 Series Routers Only—Specific to IPC Records
debug ip cef ipc
no debug ip cef ipc
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command gathers additional information for the handling of Cisco Express Forwarding interface, IPC, or packet events.
Note
Examples
The following is sample output from the debug ip cef rpf command for a packet that is dropped when it fails the RPF check. IP address 172.17.249.252 is the source address, and Ethernet 2/0/0 is the input interface.
Router# debug ip cef drops rpfIP CEF drops for RPF debugging is on00:42:02:CEF-Drop:Packet from 172.17.249.252 via Ethernet2/0/0 -- unicast rpf checkThe following is sample output for Cisco Express Forwarding packets that are not switched using information from the FIB table but are received and sent to the next switching layer:
Router# debug ip cef receiveIP CEF received packets debugging is on00:47:52:CEF-receive:Receive packet for 10.1.104.13Table 3 describes the significant fields shown in the display.
The following is sample output from the debug ip cef dialer command for a legacy dialer:
Router# debug ip cef dialer00:19:50:CEF-Dialer (legacy):add link to 10.10.10.2 via Dialer1 through BRI0/0:100:19:50:CEF-Dialer:adjacency added:0x8116485000:19:50:CEF-Dialer:adjacency found:0x81164850; fib->count:100:19:50:CEF-Dialer:setup loadinfo with 1 pathsThe following is sample output from the debug ip cef dialer command for a dialer profile:
Router# debug ip cef dialer00:31:44:CEF-Dialer (profile dynamic encap (not MLP)):add link to 10.10.10.2 via Dialer1 through Dialer100:31:44:CEF-Dialer:adjacency added:0x8116485000:31:44:CEF-Dialer:adjacency found:0x81164850; fib->count:1Table 4 describes the significant fields shown in the display.
Related Commands
ip cef
Enables Cisco Express Forwarding on the RPC card.
show ip cef
Displays entries in the FIB or displays a summary of the FIB.
debug ip cef accounting non-recursive
To troubleshoot Cisco Express Forwarding accounting records, use the debug ip cef accounting non-recursive command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef accounting non-recursive
no debug ip cef accounting non-recursive
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command records accounting events for nonrecursive prefixes when the ip cef accounting non-recursive command is enabled in global configuration mode.
Examples
The following is sample output from the debug ip cef accounting non-recursive command:
Router# debug ip cef accounting non-recursive03:50:19:CEF-Acct:tmstats_binary:Beginning generation of tmstatsephemeral file (mode binary)03:50:19:CEF-Acct:snapshoting loadinfo 0x63FF200003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF1EA003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF17C003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF1D4003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF1A8003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF074003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF08A003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF0B6003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF0CC003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF0F8003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF10E003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF124003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF13A003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF150003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF192003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF0E2003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF166003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF05E003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF0A0003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF1BE003:50:19:CEF-Acct:snapshoting loadinfo 0x63FF048003:50:19:CEF-Acct:tmstats_binary:aggregation complete, duration 0 seconds03:50:21:CEF-Acct:tmstats_binary:writing 45 bytes03:50:24:CEF-Acct:tmstats_binary:writing 45 bytes03:50:24:CEF-Acct:tmstats_binary:writing 45 bytes03:50:27:CEF-Acct:tmstats_binary:writing 45 bytes03:50:29:CEF-Acct:tmstats_binary:writing 45 bytes03:50:32:CEF-Acct:tmstats_binary:writing 45 bytes03:50:35:CEF-Acct:tmstats_binary:writing 45 bytes03:50:38:CEF-Acct:tmstats_binary:writing 45 bytes03:50:41:CEF-Acct:tmstats_binary:writing 45 bytes03:50:45:CEF-Acct:tmstats_binary:writing 45 bytes03:50:48:CEF-Acct:tmstats_binary:writing 45 bytes03:50:49:CEF-Acct:tmstats_binary:writing 45 bytes03:50:52:CEF-Acct:tmstats_binary:writing 45 bytes03:50:55:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:writing 45 bytes03:50:57:CEF-Acct:tmstats_binary:tmstats file written, status 0Table 5 describes the significant fields shown in the display.
Related Commands
debug ip cef fragmentation
To report fragmented IP packets when Cisco Express Forwarding is enabled, use the debug ip cef fragmentation command in privileged EXEC mode. To disable debugging output, use the no form of this command:
debug ip cef fragmentation
no debug ip cef fragmentation
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to troubleshoot fragmentation problems when Cisco Express Forwarding switching is enabled.
Examples
The following is sample output from the debug ip cef fragmentation command:
Router# debug ip cef fragmentation00:59:45:CEF-FRAG:no_fixup path:network_start 0x5397CF8E datagramstart 0x5397CF80 data_start 0x397CF80 data_block 0x397CF40 mtu 1000 datagramsize 1414 data_bytes 141400:59:45:CEF-FRAG:send frag:datagramstart 0x397CF80 datagramsize 442 data_bytes 44200:59:45:CEF-FRAG:send frag:datagramstart 0x38BC266 datagramsize 1006 data_bytes 100600:59:45:CEF-FRAG:no_fixup path:network_start 0x5397C60E datagramstart 0x5397C600 data_start 0x397C600 data_block 0x397C5C0 mtu 1000 datagramsize 1414 data_bytes 141400:59:45:CEF-FRAG:send frag:datagramstart 0x397C600 datagramsize 442 data_bytes 44200:59:45:CEF-FRAG:send frag:datagramstart 0x38BC266 datagramsize 1006 data_bytes 1006Table 6 describes the significant fields shown in the display.
Related Commands
debug ip cef hash
To record Cisco Express Forwarding load sharing hash algorithm events, use the debug ip cef hash command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef hash
no debug ip cef hash
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when changing the load sharing algorithm to display the hash table details.
Examples
The following is sample output from the debug ip cef hash command with IP Cisco Express Forwarding load algorithm tunnel information:
Router# debug ip cef hash01:15:06:%CEF:ip cef load-sharing algorithm tunnel 001:15:06:%CEF:Load balancing algorithm:tunnel01:15:06:%CEF:Load balancing unique id:1F2BA5F601:15:06:%CEF:Destroyed load sharing hash table01:15:06:%CEF:Sending hash algorithm id 2, unique id 1F2BA5F6 to slot 255The following lines show IP Cisco Express Forwarding load algorithm universal information:
01:15:28:%CEF:ip cef load-sharing algorithm universal 001:15:28:%CEF:Load balancing algorithm:universal01:15:28:%CEF:Load balancing unique id:062063A401:15:28:%CEF:Creating load sharing hash table01:15:28:%CEF:Hash table columns for valid max_index:01:15:28:12: 9 7 7 4 4 10 0 7 10 4 5 0 4 7 8 401:15:28:15: 3 10 10 4 10 4 0 7 1 7 14 6 13 13 11 1301:15:28:16: 1 3 7 12 4 14 8 7 10 4 1 12 8 15 4 801:15:28:%CEF:Sending hash algorithm id 3, unique id 062063A4 to slot 255Table 7 describes the significant fields shown in the display.
Related Commands
debug ip cef
Troubleshoots various Cisco Express Forwarding events.
debug ip cef rrhash
Records Cisco Express Forwarding removal of receive hash events.
debug ip cef rrhash
To record Cisco Express Forwarding removal of receive hash events, use the debug ip cef rrhash command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef rrhash
no debug ip cef rrhash
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to verify the removal of receive hash events when you are shutting down or deleting an interface.
Examples
The following is sample output from the debug ip cef rrhash command:
Router# debug ip cef rrhash00:27:15:CEF:rrhash/check:found 10.1.104.7 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.0 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.255 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.7 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.7 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.0 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.255 on down idb [ok to delete]00:27:15:CEF:rrhash/check:found 10.1.104.7 on down idb [ok to delete]Table 8 describes the significant fields shown in the display.
Related Commands
debug ip cef
Troubleshoots various Cisco Express Forwarding events.
debug ip cef hash
Records Cisco Express Forwarding removal of receive hash events.
debug ip cef subblock
To troubleshoot Cisco Express Forwarding subblock events, use the debug ip cef subblock command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef subblock [id {all | hw hw-id | sw sw-id }] [xdr {all | control | event | none | statistic}]
no debug ip cef subblock [id {all | hw hw-id | sw sw-id }] [xdr {all | control | event | none | statistic}]
Syntax Description
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to record Cisco Express Forwarding subblock messages and events.
Examples
The following is sample output from the debug ip cef subblock command:
Router# debug ip cef subblock00:28:12:CEF-SB:Creating unicast RPF subblock for FastEthernet6/000:28:12:CEF-SB:Linked unicast RPF subblock to FastEthernet6/0.00:28:12:CEF-SB:Encoded unit of unicast RPF data (length 16) for FastEthernet6/000:28:12:CEF-SB:Sent 1 data unit to slot 6 in 1 XDR messageCisco 10000 Series Router Example
The following is sample output from the debug ip cef subblock command:
Router# debug ip cef subblock00:28:12:CEF-SB:Creating unicast RPF subblock for FastEthernet6/0/000:28:12:CEF-SB:Linked unicast RPF subblock to FastEthernet6/0/0.00:28:12:CEF-SB:Encoded unit of unicast RPF data (length 16) for FastEthernet6/0/000:28:12:CEF-SB:Sent 1 data unit to slot 6 in 1 XDR messageTable 9 describes the significant fields shown in the display.
Related Commands
debug ip cef table
To enable the collection of events that affect entries in the Cisco Express Forwarding tables, use the debug ip cef table command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip cef table [access-list | consistency-checkers]
no debug ip cef table [access-list | consistency-checkers]
Syntax Description
access-list
(Optional) Controls collection of consistency checker parameters from specified lists.
consistency-checkers
(Optional) Sets consistency checking characteristics.
Defaults
This command is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to record Cisco Express Forwarding table events related to the Forwarding Information Base (FIB) table. Possible types of events include the following:
•
•
•
•
Examples
The following is sample output from the debug ip cef table command:
Router# debug ip cef table01:25:46:CEF-Table:Event up, 10.1.1.1/32 (rdbs:1, flags:1000000)01:25:46:CEF-IP:Checking dependencies of 0.0.0.0/001:25:47:CEF-Table:attempting to resolve 10.1.1.1/3201:25:47:CEF-IP:resolved 10.1.1.1/32 via 10.1.104.1 to 10.1.104.1 Ethernet2/0/001:26:02:CEF-Table:Event up, default, 0.0.0.0/0 (rdbs:1, flags:400001)01:26:02:CEF-IP:Prefix exists - no-op changeCisco 10000 Series Router Example
The following is sample output from the debug ip cef table command:
Router# debug ip cef table01:25:46:CEF-Table:Event up, 10.1.1.1/32 (rdbs:1, flags:1000000)01:25:46:CEF-IP:Checking dependencies of 0.0.0.0/001:25:47:CEF-Table:attempting to resolve 10.1.1.1/3201:25:47:CEF-IP:resolved 10.1.1.1/32 via 10.1.104.1 to 10.1.104.1 GigabitEthernet2/0/001:26:02:CEF-Table:Event up, default, 0.0.0.0/0 (rdbs:1, flags:400001)01:26:02:CEF-IP:Prefix exists - no-op changeTable 10 describes the significant fields shown in the display.
Related Commands
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.
ip route-cache [cef | distributed | flow | policy | same-interface]
no ip route-cache [cef | distributed | flow | policy | same-interface]
Syntax Description
Defaults
Fast Switching
The default behavior for Fast Switching varies by interface and media.
Distributed Switching
Distributed switching is disabled.
Cisco Express Forwarding and Distributed Cisco Express Forwarding
When Cisco Express Forwarding or distributed Cisco Express Forwarding operation is enabled globally, all interfaces that support Cisco Express Forwarding or distributed Cisco Express Forwarding are enabled by default.
NetFlow Accounting
NetFlow accounting is disabled.
Fast Switching for PBR (FSPBR)
FSPBR is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
IP Route Cache
Note
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
IP Route Cache Same Interface
You can enable IP fast switching when the input and output interfaces are the same interface, using the ip route-cache same-interface command. This configuration normally is not recommended, although it is useful when you have partially meshed media, such as Frame Relay or you are running Web Cache Communication Protocol (WCCP) redirection. You could use this feature on other interfaces, although it is not recommended because it would interfere with redirection of packets to the optimal path.
IP Route Cache Flow
The flow caching option can be used in conjunction with Cisco Express Forwarding switching to enable NetFlow, which allows statistics to be gathered with a finer granularity. The statistics include IP subprotocols, well-known ports, total flows, average number of packets per flow, and average flow lifetime.
Note
ip flow ingress command is configured, both commands will appear in the output of the
show running-config command.IP Route Cache Distributed
The distributed option is supported on Cisco routers with line cards and Versatile Interface Processors (VIPs) that support Cisco Express Forwarding switching.
On Cisco routers with Route/Switch Processor (RSP) and VIP controllers, the VIP hardware can be configured to switch packets received by the VIP with no per-packet intervention on the part of the RSP. When VIP distributed switching is enabled, the input VIP interface tries to switch IP packets instead of forwarding them to the RSP for switching. Distributed switching helps decrease the demand on the RSP.
If the ip route-cache distributed, ip cef distributed, and ip route-cache flow commands are configured, the VIP performs distributed Cisco Express Forwarding switching and collects a finer granularity of flow statistics.
IP Route-Cache Cisco Express Forwarding
In some instances, you might want to disable Cisco Express Forwarding or distributed Cisco Express Forwarding on a particular interface because that interface is configured with a feature that
Cisco Express Forwarding or distributed Cisco Express Forwarding does not support. Because all interfaces that support Cisco Express Forwarding or distributed Cisco Express Forwarding are enabled by default when you enable Cisco Express Forwarding or distributed Cisco Express Forwarding operation globally, you must use the no form of the ip route-cache distributed command in the interface configuration mode to turn Cisco Express Forwarding or distributed Cisco Express Forwarding operation off a particular interface.Disabling Cisco Express Forwarding or distributed Cisco Express Forwarding on an interface disables Cisco Express Forwarding or distributed Cisco Express Forwarding switching for packets forwarded to the interface, but does not affect packets forwarded out of the interface.
Additionally, when you disable distributed Cisco Express Forwarding on the RSP, Cisco IOS software switches packets using the next-fastest switch path (Cisco Express Forwarding).
Enabling Cisco Express Forwarding globally disables distributed Cisco Express Forwarding on all interfaces. Disabling Cisco Express Forwarding or distributed Cisco Express Forwarding globally enables process switching on all interfaces.
Note
IP Route Cache Policy
If Cisco Express Forwarding is already enabled, the ip route-cache route command is not required because PBR packets are Cisco Express Forwarding-switched by default.
Before you can enable fast-switched PBR, you must first configure PBR.
FSPBR supports all of PBR's match commands and most of PBR's set commands, with the following restrictions:
•
•
Also, at the process level, the routing table is consulted to determine if the interface is on a reasonable path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software blindly forwards the packet to the specified interface.
Note
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/0Router(config-if)# ip route-cacheThe following example shows that fast switching is enabled:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP Distributed switching is disabledIP Feature Fast switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledThe following example shows that Cisco Express Forwarding switching is disabled:
Router# show cef interface fastEthernet 0/0/0FastEthernet0/0/0 is up (if_number 3)Corresponding hwidb fast_if_number 3Corresponding hwidb firstsw->if_number 3Internet address is 10.1.1.254/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledHardware idb is FastEthernet0/0/0Fast switching type 1, interface type 18IP CEF switching disabledIP Feature Fast switching turbo vectorIP Null turbo vectorInput fast flags 0x0, Output fast flags 0x0ifindex 1(1)Slot 0 Slot unit 0 VC -1Transmit limit accumulator 0x48001A02 (0x48001A02)IP MTU 1500The following example shows the configuration information for interface fastethernet 0/0/0:
Router# show running-config..!interface FastEthernet0/0/0ip address 10.1.1.254 255.255.255.0no ip route-cache cefno 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 cefThe 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 e0Router(config-if)# ip address 17.252.245.2 255.255.255.0Router(config-if)# ip route-cache distributedRouter(config-if)# ip route-cache flowThe 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 cefRouter(config)# interface e0Router(config-if)# no ip route-cache cefThe 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 distributedRouter(config)# interface e0Router(config-if)# no ip route-cache cefThe following example shows how to reenable distributed Cisco Express Forwarding operation on Ethernet interface 0:
Router(config)# ip cef distributedRouter(config)# interface e0Router(config-if)# ip route-cache distributedConfiguring 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/0Router(config-if)# ip route-cache same-interfaceThe 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/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is enabledIP Flow switching is disabledIP Distributed switching is disabledIP Feature Fast switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are FastRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledThe following example shows the configuration information for interface fastethernet 0/0/0:
Router# show running-config..!interface FastEthernet0/0/0ip address 10.1.1.254 255.255.255.0ip route-cache same-interfaceno ip route-cache cefno ip route-cache distributed!Enabling NetFlow Accounting
The following example shows how to enable NetFlow switching:
Router(config)# interface ethernet 0/0/0Router(config-if)# ip route-cache flowThe following example shows that NetFlow accounting is enabled for interface fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is enabledIP Distributed switching is disabledIP Flow switching turbo vectorIP Null turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, FlowRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledConfiguring Distributed Switching
The following example shows how to enable distributed switching:
Router(config)# ip cef distributedRouter(config)# interface ethernet 0/0/0Router(config-if)# ip route-cache distributedThe following example shows that distributed Cisco Express Forwarding switching is for interface fastethernet 0/0/0:
Router# show cef interface fastEthernet 0/0/0FastEthernet0/0/0 is up (if_number 3)Corresponding hwidb fast_if_number 3Corresponding hwidb firstsw->if_number 3Internet address is 10.1.1.254/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledHardware idb is FastEthernet0/0/0Fast switching type 1, interface type 18IP Distributed CEF switching enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorInput fast flags 0x0, Output fast flags 0x0ifindex 1(1)Slot 0 Slot unit 0 VC -1Transmit limit accumulator 0x48001A02 (0x48001A02)IP MTU 1500Configuring Fast Switching for PBR
The following example shows how to configure a simple policy-based routing scheme and to enable FSPBR:
Router(config)# access-list 1 permit 10.1.1.0 0.0.0.255Router(config)# route-map mypbrtag permit 10Router(config-route-map)# match ip address 1Router(config-route-map)# set ip next-hop 10.1.1.195Router(config-route-map)# exitRouter(config)# interface fastethernet 0/0/0Router(config-if)# ip route-cache policyRouter(config-if)# ip policy route-map mypbrtagThe following example shows that FSPBR is enabled for interface fastethernet 0/0/0:
Router# show ip interface fastEthernet 0/0/0FastEthernet0/0/0 is up, line protocol is upInternet address is 10.1.1.254/24Broadcast address is 255.255.255.255Address determined by non-volatile memoryMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP Flow switching is disabledIP CEF switching is enabledIP Distributed switching is enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorIP multicast fast switching is enabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, Distributed, Policy, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledProbe proxy name replies are disabledPolicy routing is enabled, using route map my_pbr_tagNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledIP multicast multilayer switching is disabledRelated Commands
monitor event-trace (EXEC)
To monitor and control the event trace function for a specified Cisco IOS software subsystem component, use the monitor event-trace command in privileged EXEC mode.
monitor event-trace component {clear | continuous | disable | dump [pretty] | enable | one-shot}
Cisco 10000 Series Routers
monitor event-trace component {disable | dump | enable | size | stacktrace}
Catalyst 6500 Series Switches and Cisco 7600 Series Routers
monitor event-trace all-traces {continuous [cancel] | dump [merged] [pretty]}
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
Command Default
The event trace function is disabled by default.
Command Modes
Privileged EXEC
Command History
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 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 disableRouter# monitor event-trace ipc clearRouter# monitor event-trace ipc enableThe 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-shotThe 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 dumpThe 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 prettyCatalyst 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 disableRouter# monitor event-trace spa clearRouter# monitor event-trace spa enableRelated Commands
monitor event-trace (global)
To configure event tracing for a specified Cisco IOS software subsystem component, use the monitor event-trace command in global configuration mode.
monitor event-trace component {disable | dump-file filename | enable | size number | stacktrace number}
Cisco 10000 Series Routers
monitor event-trace component {disable | dump-file filename | enable | clear | continuous | one-shot}
Syntax Description
Command Default
Event tracing is enabled or disabled depending on the software component.
Command Modes
Global configuration
Command History
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
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 users 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
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.
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 enablemonitor event-trace ipc dump-file slot0:ipc-dumpmonitor event-trace ipc size 4096When 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 enableconfigure terminal!monitor event-trace cef ipv6 enableexitThe 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%EVENT_TRACE-6-ENABLE: Trace already enabled.Related Commands
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.
show adjacency [summary | ip-address | interface-type interface-number | null number | port-channel number | sysclock number | vlan number | ipv6-address | fcpa number | link {ipv4 | ipv6 | mpls} | connectionid number | detail | serial number]
Syntax Description
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXECCommand History
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
The following information may be displayed by the show adjacency commands:
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following examples show how to display adjacency information:
Cisco 7500 Series Router
Router# show adjacencyProtocol Interface AddressIP FastEthernet2/3 172.20.52.1(3045)IP FastEthernet2/3 172.20.52.22(11)The following example shows how to display adjacency information for a specific interface:
Router# show adjacency fastethernet 0/0Protocol Interface AddressIP FastEthernet0/0 10.4.9.2(5)IP FastEthernet0/0 10.4.9.3(5)Cisco 10000 Series Router
Router# show adjacencyProtocol Interface AddressIP FastEthernet2/0/0 172.20.52.1(3045)IP FastEthernet2/0/0 172.20.52.22(11)Cisco 7500 and 10000 Series Router
The following example shows how to display detailed adjacency information for adjacent IPv6 routers:
Router# show adjacency detailProtocol Interface AddressIP Tunnel0 point2point(6)0 packets, 0 bytes00000000CEF expires: 00:02:57refresh: 00:00:57Epoch: 0IPV6 Tunnel0 point2point(6)0 packets, 0 bytes00000000IPv6 CEF neverEpoch: 0IPV6 Ethernet2/0 FE80::A8BB:CCFF:FE01:9002(3)0 packets, 0 bytesAABBCC019002AABBCC012C0286DDIPv6 ND neverEpoch: 0IPV6 Ethernet2/0 3FFE:2002::A8BB:CCFF:FE01:9002(5)0 packets, 0 bytesAABBCC019002AABBCC012C0286DDIPv6 ND neverEpoch: 0Table 11 describes the significant fields shown in the displays.
Table 11 show adjacency Field Descriptions
Protocol
Type of Internet protocol.
Interface
Outgoing interface.
Address
Next hop IP address.
The following example shows how to display a summary of adjacency information:
Router# show adjacency summaryAdjacency table has 7 adjacencies:each adjacency consumes 368 bytes (4 bytes platform extension)6 complete adjacencies1 incomplete adjacency4 adjacencies of linktype IP4 complete adjacencies of linktype IP0 incomplete adjacencies of linktype IP0 adjacencies with fixups of linktype IP2 adjacencies with IP redirect of linktype IP3 adjacencies of linktype IPV62 complete adjacencies of linktype IPV61 incomplete adjacency of linktype IPV6Adjacency database high availability:Database epoch: 8 (7 entries at this epoch)Adjacency manager summary event processing:Summary events epoch is 52Summary events queue contains 0 events (high water mark 113 events)Summary events queue can contain 49151 eventsAdj last sourced field refreshed every 16384 summary eventsRP adjacency component enabledThe following examples show how to display protocol detail and timer information:
For a Cisco 7500 Series Router
Router# show adjacency detailProtocol Interface AddressIP FastEthernet0/0 10.4.9.2(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 1400307131ABFC000500509C080800ARPIP FastEthernet0/0 10.4.9.3(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 14000500506C08000500509C080800ARPFor a Cisco 7600 Series Router
Router# show adjacency detailProtocol Interface AddressIP FastEthernet2/3 172.20.52.1(3045)0 packets, 0 bytes000000000FF9200003800000000000000000000000000000000000000000000000605C865B2800D0BB0F980B0800ARP 03:58:12IP FastEthernet2/3 172.20.52.22(11)0 packets, 0 bytes000000000FF9200003800000000000000000000000000000000000000000000000801C93804000D0BB0F980B0800ARP 03:58:06For a Cisco 10000 Series Router
Router# show adjacency detailProtocol Interface AddressIP FastEthernet2/0/0 10.4.9.2(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 1400307131ABFC000500509C080800ARPIP FastEthernet2/0/0 10.4.9.3(5)0 packets, 0 bytesepoch 0sourced in sev-epoch 2Encap length 14000500506C08000500509C080800ARPThe following examples show how to display protocol detail and timer adjacency information for IP links for a specific interface:
For a Cisco 7500 Series Router
Router# show adjacency tunnel 1 link detailProtocol Interface AddressIP Tunnel1 point2point(7)0 packets, 0 bytesepoch 1sourced in sev-epoch 4empty encap stringP2P-ADJNext chain element:label 16 TAG adj out of Ethernet1/0, addr 10.0.0.0For a Cisco 7600 Series Router
Router# show adjacency fastethernet 2/3Protocol Interface AddressIP FastEthernet2/3 172.20.52.1(3045)IP FastEthernet2/3 172.20.52.22(11)For a Cisco 10000 Series Router
Router# show adjacency tunnel 1 link detailProtocol Interface AddressIP Tunnel1 point2point(7)0 packets, 0 bytesepoch 1sourced in sev-epoch 4empty encap stringP2P-ADJNext chain element:label 16 TAG adj out of FastEthernet0/0, addr 10.0.0.0Related Commands
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 | broker broker-name [detail] | fib | hardware-vectors | idb | linecard [linecard-number] [detail | internal] | loadinfo | memory [summary | chunk-utilisation] | non-ip | nsf | path [list] | table [consistency-check | detail | internal]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
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 information for Cisco Express Forwarding paths:
Router# show cef path28 allocated IPv4 paths, 0 failed allocations4 allocated IPv6 paths, 0 failed allocations32 Total Paths, 587 Recursive Paths, 0 Unresolved PathsThe following example shows how to display Cisco Express Forwarding information for all line cards:
Router# show cef linecardSlot XDRSent Flags1 497 up4 497 up*2 329 upVRF Default, version 20, 11 routesSlot Version I/Fs State Flags1 0 4 Active sync, table-up4 0 12 Active sync, table-up2 0 2 Active sync, table-upVRF red, version 15, 9 routesSlot Version I/Fs State Flags1 0 0 Active sync, table-up4 0 1 Active sync, table-up2 0 0 Active sync, table-upVRF vpn1, version 11, 8 routesSlot Version I/Fs State Flags1 0 1 Active sync, table-up4 0 2 Active sync, table-up2 0 1 Active sync, table-upRelated Commands
clear cef linecard
Clears Cisco Express Forwarding information from line cards.
show cef interface
Displays detailed Cisco Express Forwarding information for all interfaces.
show cef features global
To display Cisco Express Forwarding features for any interface, use the show cef features global command in privileged EXEC mode.
show cef features global
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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 globalGlobal Drop features not attached to a specific interface:Input FNFGlobal Punt features not attached to a specific interface:Input FNF, SPD ClassifyTable 12 describes the significant fields shown in the display.
Table 12 show cef features global Field Descriptions
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.
Related Commands
show cef interface
Displays detailed Cisco Express Forwarding information for all interfaces.
show cef interface
To display detailed Cisco Express Forwarding information for a specified interface or for all interfaces, use the show cef interface command in user EXEC or privileged EXEC mode.
show cef interface [type number] [statistics | detail | internal | brief | policy-statistics [input | output]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 briefInterface IP-Address Status SwitchingEthernet3/0 10.0.212.6 up CEFRouter#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/0FastEthernet1/0/0 is up (if_number 6)Corresponding hwidb fast_if_number 6Corresponding hwidb firstsw->if_number 6Internet address is 10.1.1.1/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledBGP based policy accounting on input is enabledBGP based policy accounting on output is disabledHardware idb is FastEthernet1/0/0 (6)Software idb is FastEthernet1/0/0 (6)Fast switching type 1, interface type 18IP Distributed CEF switching enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorInput fast flags 0x100, Output fast flags 0x0, Flags 0x0ifindex 7(7)Slot 1 Slot unit 0 VC -1Transmit limit accumulator 0xE8001A82 (0xE8001A82)IP MTU 1500The 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 detailFastEthernet1/0/0 is up (if_number 6)Corresponding hwidb fast_if_number 6Corresponding hwidb firstsw->if_number 6Internet address is 10.1.1.1/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledBGP based policy accounting on input is enabledBGP based policy accounting on output is disabledHardware idb is FastEthernet1/0/0 (6)Software idb is FastEthernet1/0/0 (6)Fast switching type 1, interface type 18IP Distributed CEF switching enabledIP Feature Fast switching turbo vectorIP Feature CEF switching turbo vectorInput fast flags 0x100, Output fast flags 0x0, Flags 0x0ifindex 7(7)Slot 1 Slot unit 0 VC -1Transmit limit accumulator 0xE8001A82 (0xE8001A82)IP MTU 1500The following is sample output from the show cef interface Null 0 detail command:
Router# show cef interface null 0 detailNull0 is up (if_number 1)Corresponding hwidb fast_if_number 1Corresponding hwidb firstsw->if_number 1Internet Protocol processing disabledInterface is marked as nullidbPackets switched to this interface on linecard are dropped to next slow pathHardware idb is Null0Fast switching type 13, interface type 0IP CEF switching enabledIP Feature CEF switching turbo vectorInput fast flags 0x0, Output fast flags 0x0ifindex 0(0)Slot -1 Slot unit -1 VC -1Transmit limit accumulator 0x0 (0x0)IP MTU 1500The 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 internalEthernet3/1 is up (if_number 13)Corresponding hwidb fast_if_number 13Corresponding hwidb firstsw->if_number 13Internet address is 10.0.212.6/24ICMP redirects are always sentPer packet load-sharing is disabledIP unicast RPF check is disabledInbound access list is not setOutbound access list is not setIP policy routing is disabledBGP based policy accounting on input is disabledBGP based policy accounting on output is disabledHardware idb is Ethernet3/1Fast switching type 1, interface type 63IP CEF switching enabledIP CEF switching turbo vectorIP CEF turbo switching turbo vectorIP prefix lookup IPv4 mtrie 8-8-8-8 optimizedInput fast flags 0x0, Output fast flags 0x0ifindex 11(11)Slot 3 Slot unit 0 VC -1Transmit limit accumulator 0x0 (0x0)IP MTU 1500Subblocks:IPv6: enabled 1 unreachable FALSE redirect TRUE mtu 1500 flags 0x0link-local address is FE80::20C:CFFF:FEF9:4854Global unicast address(es):10:6:6:6:20C:CFFF:FEF9:4854, subnet is 10:6:6:6::/64 [EUI]IPv4: Internet address is 10.0.212.6/24Broadcast address 255.255.255.255Per packet load-sharing is disabledIP MTU 1500Table 13 describes the significant fields shown in the displays.
Table 13 show cef interface Field Descriptions
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 disabled
Indicates the status of BGP policy accounting on the output interface.
Hardware idb is Ethernet1/0/0
Interface type and number configured.
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Output fast flags
Indicates the output status of various switching features, as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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-statisticsPOS7/0 is up (if_number 8)Index Packets Bytes1 0 02 0 03 50 50004 100 100005 100 100006 10 10007 0 08 0 0The 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-statisticsEthernet1/0 is up (if_number 3)Corresponding hwidb fast_if_number 3Corresponding hwidb firstsw->if_number 3Index Packets Bytes1 0 02 0 03 0 04 0 05 0 06 0 07 0 08 0 0The 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 inputFastEthernet1/0/0 is up (if_number 6)Corresponding hwidb fast_if_number 6Corresponding hwidb firstsw->if_number 6BGP based Policy accounting on input is enabledIndex Packets Bytes1 9999 9999002 0 03 0 04 0 05 0 06 0 07 0 08 0 09 0 010 0 011 0 012 0 013 0 014 0 015 0 016 0 017 0 018 0 019 0 020 0 021 0 022 0 023 0 024 0 025 0 026 0 027 0 028 0 029 0 030 0 031 0 032 0 033 0 034 1234 12340035 0 036 0 037 0 038 0 039 0 040 0 041 0 042 0 043 0 044 0 045 1000 10000046 0 047 0 048 0 049 0 050 0 051 0 052 0 053 0 054 5123 1198782The 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 outputSerial1/1/2 is up (if_number 9)Corresponding hwidb fast_if_number 9Corresponding hwidb firstsw->if_number 9BGP based Policy accounting on output is enabledIndex Packets Bytes1 9999 9999002 0 0...18 0 019 0 020 0 0...34 1234 12340035 0 0...44 0 045 1000 10000046 0 047 0 048 0 049 0 050 0 051 0 052 0 053 0 054 5123 119878255 0 056 0 057 0 058 0 059 0 060 0 061 0 062 0 063 0 064 0 0Table 14 describes the significant fields shown in the display.
Related Commands
show ip cef
To display entries in the 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.
show ip cef [vrf vrf-name] [unresolved [detail] | [detail | summary]]
Specific FIB Entries Based on IP Address Information
show ip cef [vrf vrf-name] [network [mask]] [longer-prefixes] [detail]
Specific FIB Entries Based on Interface Information
show ip cef [vrf vrf-name] [interface-type interface-number] [detail]
Specific FIB Entries Based on Nonrecursive Routes
show ip cef [vrf vrf-name] non-recursive [detail]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 unresolved command:
Router# show ip cef unresolvedIP Distributed CEF with switching (Table Version 136632)45776 routes, 13 unresolved routes (0 old, 13 new)45776 leaves, 2868 nodes, 8441480 bytes, 136632 inserts, 90856 invalidations1 load sharing elements, 208 bytes, 1 references1 CEF resets, 1 revisions of existing leavesrefcounts: 527292 leaf, 465617 node10.214.0.0/16, version 1366220 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.215.0.0/16, version 1366230 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.218.0.0/16, version 1366240 packets, 0 bytesTable 15 describes the significant fields shown in the display.
The following is sample output from the show ip cef summary command:
Router# show ip cef summaryIP Distributed CEF with switching (Table Version 135165)45788 routes, 0 reresolve, 4 unresolved routes (0 old, 4 new)45788 leaves, 2868 nodes, 8442864 bytes, 135165 inserts, 89377 invalidations0 load sharing elements, 0 bytes, 0 references1 CEF resets, 0 revisions of existing leavesrefcounts: 527870 leaf, 466167 nodeFor a description of significant fields in this display, see Table 15.
The following is sample output from the show ip cef summary command for Cisco IOS Release 12.0(26)S and later releases that displays a summary of the IP Cisco Express Forwarding table information, which includes the percentage of memory used and current alarm status of Cisco Express Forwarding hardware resources on all E2 and Cisco IP Services Engine (ISE) line cards in a Cisco 12000 series Internet router:
Router# show ip cef summaryIP Distributed CEF with switching (Table Version 2283113), flags=0x0164413 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 34512234324 instant recursive resolutions, 0 used background process304 load sharing elements, 336 references14758 in-place/0 aborted modifications36745512 bytes allocated to the FIB table data structuresuniversal per-destination load sharing algorithm, id B03E8BB32(0) CEF resetsResolution Timer: Exponential (currently 1s, peak 1s)Tree summary:8-8-8-8 stride patternshort mask protection disabled164413 leaves, 11622 nodes using 16691988 bytesTransient memory used: 168, max: 865064Table epoch: 0 (164413 entries at this epoch)Hardware resource allocation status summaryGreen (Normal), Yellow (Caution) Red (Alarm)Slot HW Resource Name Util Alert1 E3 Rx PLU 22 G1 E3_Rx_TLU 6 G2 E3 Rx PLU 22 G2 E3_Rx_TLU 6 G3 E3 Rx PLU 22 G3 E3_Rx_TLU 6 G9 E3 Rx PLU 22 G9 E3_Rx_TLU 6 GAdjacency Table has 11 adjacenciesTable 16 describes the significant fields shown in the display.
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 172.19.233.33.
Router# show ip cef e0/0 172.19.233.33 detailIP Distributed CEF with switching (Table Version 136808)45800 routes, 8 unresolved routes (0 old, 8 new) 45800 leaves, 2868 nodes, 8444360 bytes, 136808 inserts, 91008 invalidations 1 load sharing elements, 208 bytes, 1 references 1 CEF resets, 1 revisions of existing leaves refcounts: 527343 leaf, 465638 node172.19.233.33/32, version 7417, cached adjacency 172.19.233.33 0 packets, 0 bytes, Adjacency-prefixvia 172.19.233.33, Ethernet0/0, 0 dependenciesnext hop 172.19.233.33, Ethernet0/0valid cached adjacencyTable 17 describes the significant fields shown in the display.
The following is sample output from the show ip cef detail command for the prefix 192.168.5.0, showing that the Border Gateway Protocol (BGP) policy accounting bucket number 4 (traffic_index 4) is assigned to this prefix:
Router# show ip cef 192.168.5.0 detail192.168.5.0/24, version 21, cached adjacency to POS7/20 packets, 0 bytes, traffic_index 4via 10.14.1.1, 0 dependencies, recursivenext hop 10.14.1.1, POS7/2 via 10.14.1.0/30valid cached adjacencyThe following example shows the forwarding table associated with the VRF named vrf1:
Router# show ip cef vrf vrf1Prefix Next Hop Interface0.0.0.0/32 receive10.11.0.0/16 10.50.0.1 Ethernet1/310.12.0.0/16 10.52.0.2 POS6/010.50.0.0/16 attached Ethernet1/310.50.0.0/32 receive10.50.0.1/32 10.50.0.1 Ethernet1/310.50.0.2/32 receive10.255.255.255/32 receive10.51.0.0/16 10.52.0.2 POS6/0224.0.0.0/24 receive255.255.255.255/32 receiveTable 18 describes the significant fields shown in the display.
Table 18 show ip cef vrf Field Descriptions
Prefix
Specifies the network prefix.
Next Hop
Specifies the BGP next hop address.
Interface
Specifies the VRF interface.
Related Commands
show ip cef adjacency
To display Cisco Express Forwarding and distributed Cisco Express Forwarding recursive and direct prefixes resolved through an adjacency, use the show ip cef adjacency command in user EXEC or privileged EXEC mode.
show ip cef [vrf vrf-name] adjacency interface-type interface-number ip-prefix [checksum | detail epoch epoch-number | internal | platform | source]
To display Cisco Express Forwarding and distributed Cisco Express Forwarding recursive and direct prefixes resolved through special adjacency types representing nonstandard switching paths, use this form of the show ip cef adjacency command in user EXEC or privileged EXEC mode.
show ip cef [vrf vrf-name] adjacency {discard | drop | glean | null | punt} [detail] [checksum | detail | epoch epoch-number | internal | platform | source]
For Cisco 10000 Series Routers
To display Cisco Express Forwarding and recursive and direct prefixes resolved through an adjacency, use the show ip cef adjacency command in user EXEC or privileged EXEC mode.
show ip cef [vrf vrf-name] adjacency interface-type interface-number ip-prefix [detail | internal | platform]
To display Cisco Express Forwarding and recursive and direct prefixes resolved through special adjacency types representing nonstandard switching paths, use the show ip cef adjacency command in user EXEC or privileged EXEC mode.
show ip cef [vrf vrf-name ] adjacency {discard | drop | glean | null | punt} [detail] [internal] [platform]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
An adjacency is a node that can be reached by one Layer 2 hop.
Examples
The following is sample output from the show ip cef adjacency command when the glean keyword is specified:
Router# show ip cef adjacency gleanPrefix Next Hop Interface10.2.61.0/24 attached Ethernet1/0/010.17.250.252/32 10.2.61.1 Ethernet1/0/0The following is sample output from the show ip cef adjacency drop command with the detail keyword specified:
Router# show ip cef adjacency drop detailIP CEF with switching (Table Version 4), flags=0x04 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 04 leaves, 8 nodes, 8832 bytes, 13 inserts, 9 invalidations0 load sharing elements, 0 bytes, 0 referencesuniversal per-destination load sharing algorithm, id 00B999CA3 CEF resets, 0 revisions of existing leavesResolution Timer: Exponential (currently 1s, peak 1s)0 in-place modificationsrefcounts: 533 leaf, 536 node10.0.0.0/4, version 30 packets, 0 bytes, Precedence routine (0)via 0.0.0.0, 0 dependenciesnext hop 0.0.0.0valid drop adjacencyThe 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.29Prefix Next Hop Interface10.1.1.0/24 10.20.26.29 GigabitEthernet3/0Cisco 10000 Series Routers Examples Only
The show ip cef adjacency command shows all prefixes resolved through a regular next-hop adjacency or through the usage of a special adjacency type keyword such as discard, drop, glean, null, or punt.
The following is sample output from the show ip cef adjacency command when the glean keyword is specified:
Router# show ip cef adjacency gleanPrefix Next Hop Interface10.2.61.0/24 attached GigabitEthernet1/0/010.17.250.252/32 10.2.61.1 GigabitEthernet1/0/0The following is sample output from the show ip cef adjacency drop command with the detail keyword specified:
Router# show ip cef adjacency drop detailIPv4 CEF is enabled for distributed and runningVRF Default:42 prefixes (42/0 fwd/non-fwd)Table id 0Database epoch: 3 (42 entries at this epoch)10.0.0.0/4, epoch 3Special source: dropdropThe following sample output shows the direct IP prefix when the next hop Gigabit Ethernet interface 3/0/0 is specified:
Router# show ip cef adjacency GigabitEthernet 3/0/0 172.20.26.29Prefix Next Hop Interface10.1.1.0/24 10.20.26.29 GigabitEthernet3/0/0Table 19 describes the significant fields shown in the display.
Table 19 show ip cef adjacency Field Descriptions
Prefix
Destination IP prefix.
Next Hop
Next hop IP address.
Interface
Next hop interface.
Related Commands
show adjacency
Displays Cisco Express Forwarding adjacency table information.
show ip cef summary
Displays a summary of the entries in the FIB.
show ip cef non-recursive
To display nonrecursive route entries in the Forwarding Information Base (FIB), use the show ip cef non-recursive command in user EXEC or privileged EXEC mode.
show ip cef non-recursive [detail | epoch epoch-number | internal | platform | source]
Cisco 10000 Series Routers
show ip cef non-recursive [detail | internal | platform]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 detailIPv6 CEF is enabled and runningIPv6 CEF default table8 prefixes2001:xx::/35nexthop FE80::ssss:CFF:FE3D:DCC9 Tunnel552001:zzz:500::/40nexthop FE80::nnnn:801A Tunnel322001:zzz::/35nexthop 3FFE:mmm:8023:21::2 Tunnel263FFE:yyy:8023:37::1/128 ReceiveReceive3FFE:yyy:8023:37::/64 Attached, Connectedattached to Tunnel373FFE:yyy:8023:38::1/128 ReceiveReceive3FFE:yyy:8023:38::/64 Attached, Connectedattached to Tunnel403FFE:yyy:8023:39::1/128 ReceiveReceiveCisco 10000 Series Router Example
The following is sample output from the show ip cef non-recursive detail command:
Router# show ip cef non-recursive detailIPv4 CEF is enabled for distributed and runningVRF Default:42 prefixes (42/0 fwd/non-fwd)Table id 0Database epoch: 3 (42 entries at this epoch)0.0.0.0/0, epoch 3, flags default route handlerno route0.0.0.0/32, epoch 3, flags receiveSpecial source: receivereceive10.2.2.2/32, epoch 3local label info: global/24nexthop 10.1.1.1 GigabitEthernet1/0/0 label 1810.4.4.4/32, epoch 3local label info: global/30nexthop 10.1.1.1 GigabitEthernet1/0/0 label 1910.5.5.5/32, epoch 3local label info: global/29nexthop 10.1.1.1 GigabitEthernet1/0/010.6.6.6/32, epoch 3, flags receivereceive10.1.1.0/24, epoch 3local label info: global/23nexthop 10.1.1.1 GigabitEthernet1/0/0 label 17Table 20 describes the significant fields shown in the displays.
Related Commands
show ip cef
Displays entries in the FIB.
show ip cef summary
Displays a summary of the entries in the FIB.
show ip cef unresolved
Displays unresolved entries in the FIB.
show ip cef switching statistics
To display switching statistics in the Forwarding Information Base (FIB), use the show ip cef switching statistics command in user EXEC or privileged EXEC mode.
show ip cef switching statistics [feature]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 statisticsReason Drop Punt Punt2HostRP LES Packet destined for us 0 132248 0RP LES Multicast 0 2 0RP LES Link-local 0 33 0RP LES Total 0 132283 0Slot 4 Packet destined for us 0 129546 0Slot 4 Link-local 0 31 0Slot 4 Total 0 129577 0All Total 0 261860 0The following example shows how to display switching statistics for all features in a common format:
Router# show ip cef switching statistics featureIPv4 CEF input features:Path Feature Drop Consume Punt Punt2Host New i/fLES Access List 0 0 1 0 0RSP Access List 0 0 1 0 0Slot 0 Access List 10 0 1 0 0Slot 0 Verify Unicast 9 0 0 0 0Slot 4 Verify Unicast 5 0 0 0 0Total 24 0 3 0 0IPv4 CEF output features:Path Feature Drop Consume Punt Punt2Host New i/fTotal 0 0 0 0 0IPv4 CEF post-encap features:Path Feature Drop Consume Punt Punt2Host New i/fTotal 0 0 0 0 0Cisco 10000 Series Router Examples
The following is sample output from the show ip cef switching statistics command:
Router# show ip cef switching statisticsPath Reason Drop Punt Punt2HostRP LES Packet destined for us 0 1115 0RP LES Total 0 1115 0RP PAS Packet destined for us 0 385 0RP PAS TTL expired 0 0 1833RP PAS Total 0 385 1833All Total 0 1500 1833The following example shows how to display switching statistics for all features in a common format:
Router# show ip cef switching statistics featureIPv4 CEF input features:Path Feature Drop Consume Punt Punt2Host Gave routeTotal 0 0 0 0 0IPv4 CEF output features:Path Feature Drop Consume Punt Punt2Host New i/fTotal 0 0 0 0 0IPv4 CEF post-encap features:Path Feature Drop Consume Punt Punt2Host New i/fTotal 0 0 0 0 0Table 21 describes the significant fields shown in the displays.
Related Commands
show ip cef tree
To display summary information on the default tree in the Forwarding Information Base (FIB), use the show ip cef tree command in user EXEC or privileged EXEC mode.
Cisco 7500 Series Routers
show ip cef tree [statistics | dependents [prefix-filter]]
Cisco 10000 Series Routers
show ip cef tree [statistics]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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:
Cisco 7500 Series Router Example
Router# show ip cef treeVRF Default tree information:RTRIE storing IPv6 addresses6 entries (6/0 fwd/non-fwd)Forwarding & Non-forwarding tree:6 inserts, 0 delete8 nodes using 288 bytesTable 22 describes the significant fields shown in the display for a Cisco 7500 series router.
Cisco 10000 Series Router Example
The following is sample output from the show ip cef tree command:
Router# show ip cef treeVRF Default tree information:MTRIE/MTRIE storing IPv4 addresses42 entries (42/0 fwd/non-fwd)Forwarding tree:Forwarding lookup routine: IPv4 mtrie generic82 inserts, 40 deletes8-4-6-6-4-4 stride patternshort mask protection enabled for <= 4 bits without process suspension42 leaves (1176 bytes), 76 nodes (15744 bytes)18576 total bytesleaf ops: 82 inserts, 40 deletesleaf ops with short mask protection: 3 inserts, 1 deleteper-prefix length stats: lookup off, insert off, delete offrefcounts: 2933 leaf, 2848 nodenode pools:pool[C/4 bits]: 46 allocated (0 failed), 5472 bytespool[C/6 bits]: 29 allocated (0 failed), 9216 bytespool[C/8 bits]: 1 allocated (0 failed), 1056 bytesNon-Forwarding tree:122 inserts, 122 deletes8-4-6-6-4-4 stride patternshort mask protection enabled for <= 4 bits without process suspension0 leaves (0 bytes), 1 node (1040 bytes)2696 total bytesleaf ops: 122 inserts, 122 deletesleaf ops with short mask protection: 4 inserts, 4 deletesper-prefix length stats: lookup off, insert off, delete offrefcounts: 0 leaf, 0 nodenode pools:pool[C/4 bits]: 0 allocated (0 failed), 0 bytespool[C/6 bits]: 0 allocated (0 failed), 0 bytespool[C/8 bits]: 1 allocated (0 failed), 1040 bytesTable 23 describes the significant fields shown in the display for a Cisco 10000 series router.
Related Commands
show ip cef unresolved
To display unresolved entries in the Forwarding Information Base (FIB), use the show ip cef unresolved command in user EXEC or privileged EXEC mode.
show ip cef unresolved [detail | epoch epoch-number | internal | platform | source]
Cisco 10000 Series Routers
show ip cef unresolved [detail | internal | platform]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show ip cef unresolved detail command displays detailed information for all unresolved FIB entries.
Examples
The following is sample output from the show ip cef unresolved command:
Router# show ip cef unresolvedIP Distributed CEF with switching (Table Version 136632)45776 routes, 13 unresolved routes (0 old, 13 new)45776 leaves, 2868 nodes, 8441480 bytes, 136632 inserts, 90856 invalidations1 load sharing elements, 208 bytes, 1 references1 CEF resets, 1 revisions of existing leavesrefcounts: 527292 leaf, 465617 node10.214.0.0/16, version 1366220 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.215.0.0/16, version 1366230 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.218.0.0/16, version 1366240 packets, 0 bytesCisco 10000 Series Router Example
The following is sample output from the show ip cef unresolved command:
Router# show ip cef unresolved10.214.0.0/16, version 1366220 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.215.0.0/16, version 1366230 packets, 0 bytesvia 172.17.233.56, 0 dependencies, recursiveunresolved10.218.0.0/16, version 1366240 packets, 0 bytesRelated Commands
show ip traffic
To display statistics about IP traffic, use the show ip traffic command in user EXEC or privileged EXEC mode.
show ip traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show ip traffic command:
Router# show ip trafficIP statistics:Rcvd: 27 total, 27 local destination0 format errors, 0 checksum errors, 0 bad hop count0 unknown protocol, 0 not a gateway0 security failures, 0 bad options, 0 with optionsOpts: 0 end, 0 nop, 0 basic security, 0 loose source route0 timestamp, 0 extended security, 0 record route0 stream ID, 0 strict source route, 0 alert, 0 cipso, 0 ump0 otherFrags: 0 reassembled, 0 timeouts, 0 couldn't reassemble0 fragmented, 0 couldn't fragmentBcast: 27 received, 0 sentMcast: 0 received, 0 sentSent: 0 generated, 0 forwardedDrop: 0 encapsulation failed, 0 unresolved, 0 no adjacency0 no route, 0 unicast RPF, 0 forced dropDrop: 0 packets with source IP address zeroCisco 10000 Series Routers Example Only
The following is sample output from the show ip traffic command:
Router# show ip trafficIP statistics:Rcvd: 27 total, 27 local destination0 format errors, 0 checksum errors, 0 bad hop count0 unknown protocol, 0 not a gateway0 security failures, 0 bad options, 0 with optionsOpts: 0 end, 0 nop, 0 basic security, 0 loose source route0 timestamp, 0 extended security, 0 record route0 stream ID, 0 strict source route, 0 alert, 0 cipso, 0 ump0 otherFrags: 0 reassembled, 0 timeouts, 0 couldn't reassemble0 fragmented, 0 couldn't fragmentBcast: 27 received, 0 sentMcast: 0 received, 0 sentSent: 0 generated, 0 forwardedDrop: 0 encapsulation failed, 0 unresolved, 0 no adjacency0 no route, 0 unicast RPF, 0 forced drop0 options denied, 0 source IP address zeroTable 24 describes the significant fields shown in the display.
show monitor event-trace
To display event trace messages for Cisco IOS software subsystem components, use the show monitor event-trace command in privileged EXEC mode.
show monitor event-trace [all-traces] [component {all | back hour:minute | clock hour:minute | from-boot seconds | latest | parameters}]
Syntax Description
Command Modes
Privileged EXEC
Command History
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.
Examples
IPC Component Example
The following is sample output from the show monitor event-trace component command for the interprocess communication (IPC) component. Notice that 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 ipc3667: 6840.016:Message type:3 Data=01234567893668: 6840.016:Message type:4 Data=01234567893669: 6841.016:Message type:5 Data=01234567893670: 6841.016:Message type:6 Data=0123456BFD 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 all3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], event Sessioncreate, state Unknown -> Fail3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Fail -> Down(from LC)3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Down -> Init(from LC)3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Init -> Up(from LC)3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], event Sessioncreate, state Unknown -> Fail3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Fail -> Down(from LC)3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Down -> Up(from LC)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-tracesTest1 event trace:3667: 6840.016:Message type:3 Data=01234567893669: 6841.016:Message type:4 Data=01234567893671: 6842.016:Message type:5 Data=01234567893673: 6843.016:Message type:6 Data=0123456789Test2 event trace:3668: 6840.016:Message type:3 Data=01234567893670: 6841.016:Message type:4 Data=01234567893672: 6842.016:Message type:5 Data=01234567893674: 6843.016:Message type:6 Data=0123456789SPA Component Example
The following is sample output from the show monitor event-trace component latest command for the spa component:
Router# show monitor event-trace spa latest00:01:15.364: subslot 2/3: 4xOC3 POS SPA, TSM Event:inserted New state:wait_psm_readyspa type 0x44000:02:02.308: subslot 2/0: not present, TSM Event:empty New state:removespa type 0x0, fail code 0x0(none)00:02:02.308: subslot 2/0: not present, TSM Event:remove_complete New state:idle00:02:02.308: subslot 2/1: not present, TSM Event:empty New state:removespa type 0x0, fail code 0x0(none)00:02:02.308: subslot 2/1: not present, TSM Event:remove_complete New state:idle00:02:02.308: subslot 2/2: not present, TSM Event:empty New state:removespa type 0x0, fail code 0x0(none)00:02:02.308: subslot 2/2: not present, TSM Event:remove_complete New state:idle00:02:02.312: subslot 2/3: not present(plugin 4xOC3 POS SPA), TSM Event:empty Newstate:removespa type 0x0, fail code 0x0(none)00:02:02.312: subslot 2/3: not present, TSM Event:remove_complete New state:idleCisco Express Forwarding Component Examples
If you select Cisco Express Forwarding as the component for which to display event messages, you can use the following additional arguments and keywords: show monitor event-trace cef [events | interface | ipv6 | ipv4][all].
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 all00:00:24.612: [Default] *::*/*'00 New FIB table [OK]Router# show monitor event-trace cef ipv4 all00:00:24.244: [Default] 127.0.0.81/32'01 FIB insert [OK]In the following example, all event trace messages for the Cisco Express Forwarding component are displayed:
Router# show monitor event-trace cef events all00:00:18.884: SubSys fib_ios_chain init00:00:18.884: Inst unknown -> RP00:00:24.584: SubSys fib init00:00:24.592: SubSys fib_ios init00:00:24.592: SubSys fib_ios_if init00:00:24.596: SubSys ipv4fib init00:00:24.608: SubSys ipv4fib_ios init00:00:24.612: SubSys ipv6fib_ios init00:00:24.620: Flag IPv4 CEF enabled set to yes00:00:24.620: Flag 0x7BF6B62C set to yes00:00:24.620: Flag IPv4 CEF switching enabled set to yes00:00:24.624: GState CEF enabled00:00:24.628: SubSys ipv4fib_les init00:00:24.628: SubSys ipv4fib_pas init00:00:24.632: SubSys ipv4fib_util init00:00:25.304: Process Background created00:00:25.304: Flag IPv4 CEF running set to yes00:00:25.304: Process Background event loop enter00:00:25.308: Flag IPv4 CEF switching running set to yesThe following example shows Cisco Express Forwarding interface events:
Router# show monitor event-trace cef interface all00:00:24.624: <empty> (sw 4) Create new00:00:24.624: <empty> (sw 4) SWIDBLnk FastEthernet0/0(4)00:00:24.624: Fa0/0 (sw 4) NameSet00:00:24.624: <empty> (hw 1) Create new00:00:24.624: <empty> (hw 1) HWIDBLnk FastEthernet0/0(1)00:00:24.624: Fa0/0 (hw 1) NameSet00:00:24.624: <empty> (sw 3) Create new00:00:24.624: <empty> (sw 3) SWIDBLnk FastEthernet0/1(3)00:00:24.624: Fa0/1 (sw 3) NameSet00:00:24.624: <empty> (hw 2) Create newCisco 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 all00:00:48.244: [Default] 127.0.0.81/32'01 FIB insert [OK]In the following example, all event trace message for the Cisco Express Forwarding component are displayed:
Router# show monitor event-trace cef events all00:00:18.884: SubSys fib_ios_chain init00:00:18.884: Inst unknown -> RP00:00:24.584: SubSys fib init00:00:24.592: SubSys fib_ios init00:00:24.592: SubSys fib_ios_if init00:00:24.596: SubSys ipv4fib init00:00:24.608: SubSys ipv4fib_ios init00:00:24.620: Flag IPv4 CEF enabled set to yes00:00:24.620: Flag 0x7BF6B62C set to yes00:00:24.620: Flag IPv4 CEF switching enabled set to yes00:00:24.624: GState CEF enabled00:00:24.628: SubSys ipv4fib_les init00:00:24.628: SubSys ipv4fib_pas init00:00:24.632: SubSys ipv4fib_util init00:00:25.304: Process Background created00:00:25.304: Flag IPv4 CEF running set to yes00:00:25.304: Process Background event loop enter00:00:25.308: Flag IPv4 CEF switching running set to yesThe following examples show Cisco Express Forwarding interface events:
Router# show monitor event-trace cef interface all00:00:24.624: <empty> (sw 4) Create new00:00:24.624: <empty> (sw 4) SWIDBLnk FastEthernet1/0/0(4)00:00:24.624: Fa0/0 (sw 4) NameSet00:00:24.624: <empty> (hw 1) Create new00:00:24.624: <empty> (hw 1) HWIDBLnk FastEthernet1/0/0(1)00:00:24.624: Fa0/0 (hw 1) NameSet00:00:24.624: <empty> (sw 3) Create new00:00:24.624: <empty> (sw 3) SWIDBLnk FastEthernet1/1/0(3)00:00:24.624: Fa0/1 (sw 3) NameSet00:00:24.624: <empty> (hw 2) Create newCFD Component for Cisco IOS Release 12.4(9)T
To troubleshoot errors in an encryption datapath, enter the show monitor event-trace cfd all command. In this example, events are shown separately, each beginning with a time stamp, followed by data from the error trace buffer. Cisco Technical Assistence Center (TAC) engineers can use this information to diagnose the cause of the errors.
Note
Router# show monitor event-trace cfd all00:00:42.452: 450000B4 00060000 FF33B306 02020203 02020204 32040000 F672999C 00000001 7A7690C2 A0A4F8BC E732985C D6FFDCC8 00000001 C0902BD0 A99127AE 8EAA22D4 00:00:44.452: 450000B4 00070000 FF33B305 02020203 02020204 32040000 F672999C 00000002 93C01218 2325B697 3C384CF1 D6FFDCC8 00000002 BFA13E8A D21053ED 0F62AB0E 00:00:46.452: 450000B4 00080000 FF33B304 02020203 02020204 32040000 F672999C 00000003 7D2E11B7 A0BA4110 CC62F91E D6FFDCC8 00000003 7236B930 3240CA8C 9EBB44FF 00:00:48.452: 450000B4 00090000 FF33B303 02020203 02020204 32040000 F672999C 00000004 FB6C80D9 1AADF938 CDE57ABA D6FFDCC8 00000004 E10D8028 6BBD748F 87F5E253 00:00:50.452: 450000B4 000A0000 FF33B302 02020203 02020204 32040000 F672999C 00000005 697C8D9D 35A8799A 2A67E97B D6FFDCC8 00000005 BC21669D 98B29FFF F32670F6 00:00:52.452: 450000B4 000B0000 FF33B301 02020203 02020204 32040000 F672999C 00000006 CA18CBC4 0F387FE0 9095C27C D6FFDCC8 00000006 87A54811 AE3A0517 F8AC4E64Related Commands
show xdr
To display details about eXternal Data Representation (XDR), use the show xdr command in user EXEC or privileged EXEC mode.
show xdr {client {client-name | all} [statistics] | linecard [linecard-number] [internal] | multicast-group | timers}
Syntax Description
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXECCommand History
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 allXDR Interrupt P(0) flag:1 decode:0x413B9804 pull:0x413B9AE8 context:8XDR Process Pri(1) flag:1 decode:0x413B99A0 pull:0x413B9D3C context:6FIBHWIDB broker(2) flag:1 decode:0x0 pull:0x413A7B7C context:2FIBIDB broker (3) flag:1 decode:0x0 pull:0x413A844C context:2FIBHWIDB Subblo(4) flag:1 decode:0x0 pull:0x413A8E20 context:2FIBIDB Subblock(5) flag:1 decode:0x0 pull:0x413A97DC context:2XDR High Queue (6) flag:3 decode:0x4031AFFC pull:0x4031B934 context:1Adjacency updat(7) flag:1 decode:0x413B266C pull:0x413B261C context:2XDR Medium Queu(8) flag:3 decode:0x4031B004 pull:0x4031B95C context:1IPv4 table brok(9) flag:1 decode:0x0 pull:0x413B21F0 context:6IPv6 table brok(10) flag:1 decode:0x0 pull:0x413ECA90 context:6XDR Low Queue (11) flag:3 decode:0x4031B00C pull:0x4031B984 context:1MFI RP Pull (12) flag:1 decode:0x0 pull:0x413E1174 context:1Push Client One(13) flag:1 decode:0x413BA300 pull:0x0 context:4CEF push (14) flag:1 decode:0x413A3D74 pull:0x0 context:124MFI non-RP Push(15) flag:1 decode:0x413DFA34 pull:0x0 context:4XDR ping (16) flag:1 decode:0x413BABB4 pull:0x0 context:1The following example shows how to display XDR information for all XDR line card peer instances:
Router# show xdr linecardXDR slot number 1, status PEER UPIPC messages sent 48Next sequence number to send 21Maximum sequence number expected 36XDR slot number 2, status PEER UPIPC messages sent 52Next sequence number to send 31Maximum sequence number expected 46XDR slot number 3, status PEER UPIPC messages sent 55Next sequence number to send 17Maximum sequence number expected 32The following example shows how to display XDR information for the XDR line card peer instance in slot number 1:
Router# show xdr linecard 1XDR slot number 1, status PEER UPIPC messages sent 48Next sequence number to send 21Maximum sequence number expected 36The 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 internalXDR slot number 1, status PEER UPIPC messages sent 48Next sequence number to send 21Maximum sequence number expected 36Tx bytes Rx bytesXDR Interrupt Priori:0 0 2391 11955 Window Message21 336 0 0 Time Message2 8 0 0 Resequence Message0 0 1 6 CEF LC stateXDR Process Priority:0 0 1 3 Registration Signal2 10 0 0 CEF runningFIBHWIDB broker :90 33570 0 0 fibhwidb updateFIBIDB broker :80 30960 0 0 fibidb updateFIBIDB Subblock brok:10 315 0 0 fibswsb updateAdjacency update :2 6 0 0 Adjacency update me3 9 0 0 Adjacency repopulatIPv4 table broker :16 558 0 0 prefix4 24 0 0 epoch2 36 0 0 table4 44 0 0 multicast prefixIPv6 table broker :1 18 0 0 tableCEF push :12 72 19 114 repopulation req0 0 1 12 isl table update rq0 0 1 12 dot1q table updateq2 10 0 0 state9 452 0 0 control1 3 0 0 flow features deace1 22 0 0 flow cache config1 40 0 0 flow export config6 470 0 0 access-list config2 10 0 0 access-list delete1 12 0 0 route-map1 16 0 0 icmp limit1 8 0 0 SSM RP to LC commasXDR ping :3 12 3 12 ping messageThe following is sample output from the show xdr multicast-group command:
Router# show xdr multicast-group0x4300DC00 READY Window: 15 Linecards: 2XDR High Queue xdrs to push: 0XDR Medium Queu xdrs to push: 0XDR Low Queue xdrs to push: 00x4414BC60 READY Window: 15 Linecards: 1XDR High Queue xdrs to push: 0XDR Medium Queu xdrs to push: 0XDR Low Queue xdrs to push: 00x44159420 READY Window: 15 Linecards: 3XDR High Queue xdrs to push: 0XDR Medium Queu xdrs to push: 0XDR Low Queue xdrs to push: 0The following is sample output from the show xdr timers command:
Router# show xdr timersXDR multicast timersExpiration Type| 0.000 (parent)XDR RP ping timersExpiration Type| 0.000 (parent)XDR RP timersExpiration 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: 3Cisco 10000 Series Router Examples
The following example shows how to display XDR information for all clients:
Router# show xdr client allXDR Interrupt P(0) flag:RP|ISSU awareISSU capable slot(s): 1XDR Process Pri(1) flag:RP|ISSU awareISSU capable slot(s): 1FIBHWIDB broker(2) flag:RP|ISSU awareISSU capable slot(s): 1FIBIDB broker (3) flag:RP|ISSU awareISSU capable slot(s): 1FIBHWIDB Subblo(4) flag:RP|ISSU awareISSU capable slot(s): 1FIBIDB Subblock(5) flag:RP|ISSU awareISSU capable slot(s): 1XDR High Queue (6) flag:RP|LCAdjacency updat(7) flag:RP|ISSU awareISSU capable slot(s): 1XDR Medium Queu(8) flag:RP|LCIPv4 table brok(9) flag:RP|ISSU awareISSU capable slot(s): 1XDR Low Queue (11) flag:RP|LCMFI Pull (12) flag:RP|ISSU awareISSU capable slot(s): 1Push Client One(13) flag:RPCEF push (14) flag:RP|ISSU awareISSU capable slot(s): 1MFI Push (15) flag:RP|ISSU awareISSU capable slot(s): 1XDR ping (16) flag:RPMPLS Embedded M(17) flag:RPThe following example shows how to display XDR information for all XDR line card peer instances:
Router# show xdr linecardXDR slot number 1, status PEER UPIPC messages sent 569This is the secondary RPNext sequence number to send 116Maximum sequence number expected 160ISSU state: Nego done, version 2, mtu 7, sid 31The following example shows how to display XDR information for the XDR line card peer instance in slot number 1:
Router# show xdr linecard 1XDR slot number 1, status PEER UPIPC messages sent 570This is the secondary RPNext sequence number to send 116Maximum sequence number expected 160ISSU state: Nego done, version 2, mtu 7, sid 31The 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 internalXDR slot number 1, status PEER UPIPC maximum mtu 1478IPC messages sent 570This is the secondary RPNext sequence number to send 116Maximum sequence number expected 160ISSU state: Nego done, version 2, mtu 7, sid 31Tx bytes Rx bytesXDR Interrupt Priori:0 0 10427 52135 Window Message87 1392 0 0 Time Message1 4 0 0 Resequence Message19 444 11 264 ISSU negoXDR Process Priority:17 51 11 33 Reg Signal1 2 0 0 CEF running0 0 1 4 CEF reload request15 348 9 216 ISSU negoFIBHWIDB broker :32 3588 0 0 fibhwidb update7 156 5 120 ISSU negoFIBIDB broker :49 6429 0 0 fibidb update7 156 5 120 ISSU negoFIBHWIDB Subblock br:7 156 5 120 ISSU negoFIBIDB Subblock brok:41 1533 0 0 fibswsb update13 300 8 192 ISSU negoAdjacency update :62 3089 0 0 adj update4 8 0 0 adj epoch17 396 10 240 ISSU negoIPv4 table broker :285 28557 0 0 prefix8 48 0 0 epoch5 78 0 0 table5 55 0 0 multicast prefix45 1068 24 576 ISSU negoMFI Pull :12 456 0 0 pull update75 1788 39 936 ISSU negoCEF push :8 48 14 84 repopulation req5 10 0 0 state12 816 0 0 control2 0 0 0 mpls_access-list delete2 32 0 0 icmp limit9 204 6 144 ISSU negoMFI Push :3 101 0 0 service reply2 34 0 0 client request0 0 4 106 service request2 16 0 0 enable/redist redistributionclient153 3660 78 1872 ISSU negoXDR ping :6 24 6 24 ping messageRelated Commands
show cef broker
Displays Cisco Express Forwarding information related to a selected update broker.
Feature Information for Cisco Express Forwarding: Command Changes
Table 25 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Glossary
XDR—eXternal Data Representation. A set of library routines that let a C programmer describe arbitrary data structures in a machine-independent fashion. XDR defines a standard representation for data in the network to support heterogeneous network computing.
RP—Route Processor module in the Cisco 7500 series routers that contains the CPU, system software, and most of the memory components that are used in the router. Sometimes called a supervisory processor.
RSP—Route/Switch Processor. Processor module in the Cisco 7500 series routers that integrates the functions of the Route Processor (RP) and the Switch Processor (SP).
SP—Cisco 7500-series processor module that acts as the administrator for all CxBus activities. Sometimes called CiscoBus controller.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2004-2007 Cisco Systems, Inc. All rights reserved.
