Table Of Contents
Cisco Express Forwarding Commands on Cisco IOS XR Software
cef accounting non-recursive
cef ipv4 unicast check-consistency
cef purge-delay
clear adjacency ipv4
clear adjacency statistics
clear cef ipv4 drop
clear cef ipv4 exceptions
clear cef ipv4 interface bgp-policy-statistics
clear cef ipv4 prefix
clear cef ipv4 prefix-statistics
clear cef ipv6 drop
clear cef ipv6 exceptions
ipv4 bgp policy accounting
ipv4 verify unicast source reachable-via
ipv6 verify unicast source reachable-via any
rp mgmtethernet forwarding
show adjacency
show cef ipv4
show cef ipv4 drop
show cef ipv4 exact-route
show cef ipv4 exceptions
show cef ipv4 interface
show cef ipv4 interface bgp-policy-statistics
show cef ipv4 non-recursive
show cef ipv4 summary
show cef ipv4 unicast check-consistency
show cef ipv4 unresolved
show cef ipv6
show cef ipv6 drop
show cef ipv6 exact-route
show cef ipv6 exceptions
show cef ipv6 non-recursive
show cef ipv6 summary
show cef ipv6 unresolved
Cisco Express Forwarding Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Cisco Express Forwarding (CEF) on Cisco IOS XR software.
For detailed information about CEF concepts, configuration tasks, and examples, see the Cisco IOS XR IP Addresses and Services Configuration Guide.
cef accounting non-recursive
To enable network accounting of Cisco Express Forwarding (CEF) nonrecursive prefixes, use the cef accounting non-recursive command in global configuration mode. To disable network accounting of CEF nonrecursive prefixes, use the no form of this command.
cef accounting non-recursive
no cef accounting non-recursive
Syntax Description
This command has no arguments or keywords.
Defaults
Network accounting of CEF nonrecursive prefixes is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You might want to collect statistics to better understand CEF patterns in your network. Nonrecursive accounting allows you to display how much traffic is going through nonrecursive prefixes. When you enable network accounting for CEF nonrecursive prefixes with the cef accounting non-recursive command, the number of packets and bytes that are forwarded through a prefix will be collected.
Note
Individual prefix accounting is not supported.
Examples
The following example shows how to enable the collection of CEF nonrecursive prefix accounting statistics:
RP/0/RP0/CPU0:router(config)# cef accounting non-recursive
Related Commands
cef ipv4 unicast check-consistency
To enable periodic background consistency checking for IPv4 unicast prefixes stored in the Routing Information Base (RIB) and the Cisco Express Forwarding (CEF) table, use the cef ipv4 unicast check-consistency command in global configuration mode. To disable IPv4 unicast prefix consistency checking, use the no form of this command.
cef ipv4 unicast check-consistency [count max-entries | period seconds]
no cef ipv4 unicast check-consistency [count max-entries | period seconds]
Syntax Description
count max-entries
|
(Optional) Specifies the maximum number of prefix entries scanned for one consistency check. Range is 1 to 100000 entries. Default is 1000.
|
period seconds
|
(Optional) Specifies the period between consistency checks. Range is 30 to 3600 seconds. Default is 60 seconds.
|
Defaults
max-entries: 1000 prefix entries
seconds: 60 seconds
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When this command is enabled, the consistency check scans the prefixes stored in the RIB against the prefixes stored in the CEF table, inspecting those tables for missing prefixes, incorrect paths, and incorrect next hops.
To display the results of IPv4 unicast consistency checks, use the show cef ipv4 unicast check-consistency log command.
Examples
The following example shows how to enable consistency checking for IPv4 unicast prefixes:
RP/0/RP0/CPU0:router(config)# cef ipv4 unicast check-consistency
Related Commands
cef purge-delay
To configure a delay in purging routes when the Routing Information Base (RIB) or other related processes experience a failure, use the cef purge-delay command in global configuration mode. To restore the default value, use the no form of this command.
cef purge-delay seconds
no cef purge-delay seconds
Syntax Description
seconds
|
Number of seconds configured to delay the purge routes. Range is 1 to 3600 seconds. Default is 360 seconds.
|
Defaults
seconds: 360 seconds
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure the delay in purging routes when the RIB process experiences a failure to 180 seconds:
RP/0/RP0/CPU0:router(config)# cef purge-delay 180
clear adjacency ipv4
To clear the IPv4 Cisco Express Forwarding (CEF) adjacency table, use the clear adjacency ipv4 command in EXEC mode.
clear adjacency ipv4 [location node-id]
Syntax Description
location node-id
|
(Optional) Clears the IPv4 CEF adjacency table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you issue the clear adjacency ipv4 command, entries in the adjacency table that reside on the route processor (RP) are removed and then repopulated.
If you do not specify a node with the location keyword and node-id argument, this command clears the CEF adjacency table for the node on which the command is issued.
Examples
The following example shows how to clear the IPv4 CEF adjacency table on the RP:
RP/0/RP0/CPU0:router# clear adjacency ipv4
Related Commands
Command
|
Description
|
show adjacency
|
Displays the IPv4 CEF adjacency table.
|
clear adjacency statistics
To clear adjacency packet and byte counter statistics, use the clear adjacency statistics command in EXEC mode.
clear adjacency statistics [ipv4 [nexthop ipv4-address] | mpls | ipv6] [type instance | location
node-id]
Syntax Description
ipv4
|
(Optional) Clears only IPv4 adjacency packet and byte counter statistics.
|
nexthop ipv4-address
|
(Optional) Clears adjacency statistics that are destined to the specified IPv4 nexthop.
|
mpls
|
(Optional) Clears only MPLS adjacency statistics.
|
ipv6
|
(Optional) Clears only IPv6 adjacency statistics.
|
type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
instance
|
(Optional) Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
location node-id
|
(Optional) Clears detailed adjacency statistics for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command is useful for troubleshooting network connection and forwarding problems.
If you do not specify any of the optional keywords, all adjacency statistics are cleared for the node on which the command is issued.
Examples
The following example shows how to clear the IPv4 CEF adjacency statistics:
RP/0/RP0/CPU0:router# clear adjacency statistics
Related Commands
Command
|
Description
|
show adjacency
|
Displays the IPv4 CEF adjacency table.
|
clear cef ipv4 drop
To clear Cisco Express Forwarding (CEF) IPv4 packet drop counters, use the clear cef ipv4 drop command in EXEC mode.
clear cef ipv4 drop [location node-id]
Syntax Description
location node-id
|
(Optional) Clears IPv4 packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command are IPv4 CEF drop counters for all nodes.
Examples
The following example shows how to clear IPv4 CEF drop counters for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv4 drop
Related Commands
clear cef ipv4 exceptions
To clear IPv4 Cisco Express Forwarding (CEF) exception packet counters, use the clear cef ipv4 exceptions command in EXEC mode.
clear cef ipv4 exceptions [location node-id]
Syntax Description
location node-id
|
(Optional) Clears IPv4 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command will clear IPv4 CEF exception packet counters for all nodes.
Examples
The following example shows how to clear IPv4 CEF exception packets for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv4 exceptions
Related Commands
clear cef ipv4 interface bgp-policy-statistics
To clear Cisco Express Forwarding (CEF) IPv4 interface BGP policy statistics, use the clear cef ipv4 interface bpg-policy-statistics command in EXEC mode.
clear cef ipv4 interface type instance bpg-policy-statistics
Syntax Description
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command clears the Border Gateway Protocol (BGP) policy accounting counters for the specified interface.
Examples
The following example shows how to clear IPv4 CEF BGP policy statistics:
RP/0/RP0/CPU0:router# clear cef ipv4 interface MgmtEth 0/RP1/CPU0/0 bgp-policy-statistics
Related Commands
clear cef ipv4 prefix
To clear the IPv4 Cisco Express Forwarding (CEF) table, use the clear cef ipv4 prefix command in EXEC mode.
clear cef ipv4 prefix [location node-id]
Syntax Description
location node-id
|
(Optional) Clears the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the command is effective only for the node on which the command is issued. Otherwise, it is effective on the node specified by the location keyword and node-id argument.
Examples
The following example shows how to clear the IPv4 CEF table for node 0/1/cpu0:
RP/0/RP0/CPU0:router# clear ipv4 cef prefix location 0/1/cpu0
Related Commands
Command
|
Description
|
show cef ipv4
|
Displays IPv4 CEF table entries or statistics.
|
clear cef ipv4 prefix-statistics
To clear IPv4 Cisco Express Forwarding (CEF) counters, use the clear cef ipv4 prefix-statistics command in EXEC mode.
clear cef ipv4 {prefix [mask] | *} prefix-statistics
Syntax Description
prefix
|
IPv4 destination prefix. Specifying the optional prefix argument clears the longest matching CEF entry for the designated IPv4 destination prefix.
|
mask
|
(Optional) IPv4 prefix mask. Specifying the optional prefix and mask arguments clears the exact CEF entry for the designated IPv4 prefix and mask.
|
*
|
Clears counters for all CEF entries.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command clears the IPv4 CEF table statistics that are displayed when you issue the show cef ipv4 prefix [mask] detail command.
Examples
The following example shows how to clear all CEF prefix entry counters for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv4 * prefix-statistics
Related Commands
Command
|
Description
|
show cef ipv4
|
Displays IPv4 CEF table entries or statistics.
|
clear cef ipv6 drop
To clear Cisco Express Forwarding (CEF) IPv6 packet drop counters, use the clear cef ipv6 drop command in EXEC mode.
clear cef ipv6 drop [location node-id]
Syntax Description
location node-id
|
(Optional) Clears IPv6 packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command clears IPv6 CEF drop counters for all nodes.
Examples
The following example shows how to clear IPv6 CEF drop counters for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv6 drop
Related Commands
clear cef ipv6 exceptions
To clear IPv6 Cisco Express Forwarding (CEF) exception packet counters, use the clear cef ipv6 exceptions command in EXEC mode.
clear cef ipv6 exceptions [location node-id]
Syntax Description
location node-id
|
(Optional) Clears IPv6 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command clears IPv6 CEF exception packet counters for all nodes.
Examples
The following example shows how to clear IPv6 CEF exception packets for all nodes:
RP/0/RP0/CPU0:router# clear cef ipv6 exceptions
Related Commands
ipv4 bgp policy accounting
To enable Border Gateway Protocol (BGP) policy accounting, use the ipv4 bgp policy accounting command in interface configuration mode. To disable BGP policy accounting, use the no form of this command.
ipv4 bgp policy accounting {input | output {destination-accounting [source-accounting] |
source-accounting [destination-accounting]}}
no ipv4 bgp policy accounting {input | output {destination-accounting [source-accounting] |
source-accounting [destination-accounting]}}
Syntax Description
input
|
Enables BGP policy accounting policy on the ingress IPv4 unicast interface.
|
output
|
Enables BGP policy accounting policy on the egress IPv4 unicast interface.
|
{destination-accounting [source-accounting] | source-accounting [destination-accounting]}
|
Once you specify the ingress or egress interface, you must specify one of the following keywords:
• destination-accounting—Enables accounting policy on the basis of the destination address.
• source-accounting—Enables accounting policy on the basis of the source address.
After specifying destination-accounting you can optionally specify source-accounting, or after specifying source-accounting, you can optionally specify destination-accounting.
|
Defaults
There is no BGP policy accounting.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
Release 3.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you use the no form of the command, accounting is disabled for both the source and destination. To change accounting on either the destination or source address, reconfigure the ipv4 bgp policy accounting command specifying the destination-accounting or source-accounting keyword. In the following example, you want BGP policy accounting disabled on the source address after enabling source and destination address accounting earlier:
RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy accounting output destination-accounting
See the Cisco IOS XR Routing Configuration Guide for information on configuring a BGP policy. BGP accounting policy is based on community lists, autonomous system numbers, or autonomous system paths.
For BGP policy propagation to function, you must enable BGP.
To specify the accounting policy, the proper route policy configuration must be in place matching specific BGP attributes using the set traffic-index command. In BGP router configuration mode, use the table-policy command to modify the accounting buckets when the IP routing table is updated with routes learned from BGP. To display accounting policy information, use the show cef ipv4 interface bgp-policy-statistics, show bgp policy, and show ip route bgp commands.
Examples
The following example shows how to configure BGP policy accounting:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv4 bgp policy accounting output source-accounting
Related Commands
Command
|
Description
|
show bgp policy
|
Displays information about BGP advertisements under a proposed policy.
|
show cef ipv4 interface bgp-policy-statistics
|
Displays IPv4 CEF BGP policy statistics.
|
show route bgp
|
Displays the current routes for BGP in the RIB.
|
route-policy
|
Defines a route policy.
|
table-policy
|
Applies a routing policy to routes being installed into the routing table.
|
ipv4 verify unicast source reachable-via
To enable IPv4 unicast Reverse Path Forwarding (RPF) checking, use the ipv4 verify unicast source reachable-via command in interface configuration mode. To disable unicast RPF, use the no form of this command.
ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
no ipv4 verify unicast source reachable-via {any | rx} [allow-default] [allow-self-ping]
Syntax Description
any
|
Enables loose unicast RPF checking. If loose unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table.
|
rx
|
Enables strict unicast RPF checking. If strict unicast RPF is enabled, a packet is not forwarded unless its source prefix exists in the routing table and the output interface matches the interface on which the packet was received.
|
allow-default
|
(Optional) Enables the matching of default routes. This option applies only to loose RPF.
|
allow-self-ping
|
(Optional) Enables the router to ping out an interface. This option applies only to loose RPF.
|
Defaults
IPv4 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the ipv4 verify unicast source reachable-via interface command to mitigate problems caused by malformed or forged (spoofed) IP source addresses that pass through a router. Malformed or forged source addresses can indicate denial-of-service (DoS) attacks based on source IP address spoofing.
When strict unicast RPF is enabled on an interface, the router examines all packets received on that interface. The router checks to make sure that the source address appears in the routing table and matches the interface on which the packet was received.
Examples
The following example shows how to configure strict RPF on PoS interface 0/1/0/0:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv4 verify unicast source reachable-via rx
Related Commands
ipv6 verify unicast source reachable-via any
To enable loose IPv6 unicast Reverse Path Forwarding (RPF) checking, use the ipv6 verify unicast source reachable-via any command in interface configuration mode. To disable loose IPv6 unicast RPF checking, use the no form of this command.
ipv6 verify unicast source reachable-via any
no ipv6 verify unicast source reachable-via any
Syntax Description
This command has no arguments or keywords.
Defaults
Loose IPv6 unicast RPF is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enable loose RPF checking on PoS interface 0/1/0/0:
RP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-if)# ipv6 verify unicast source reachable-via any
Related Commands
rp mgmtethernet forwarding
To enable switching from the line card to the route processor Management Ethernet interfaces, use the rp mgmtethernet forwarding command in global configuration mode. To disable switching from the modular services card to the route processor Management Ethernet interfaces, use the no form of this command.
rp mgmtethernet forwarding
no rp mgmtethernet forwarding
Syntax Description
This command has no arguments or keywords.
Defaults
Switching is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enable switching from the modular services card to the RP Management Ethernet interfaces:
RP/0/RP0/CPU0:router(config)# rp mgmtethernet forwarding
show adjacency
To display Cisco Express Forwarding (CEF) adjacency table information, use the show adjacency command in EXEC command.
show adjacency [ipv4 [nexthop ipv4-address] | mpls | ipv6] [type instance] [remote] [detail]
[location node-id]
Syntax Description
ipv4
|
(Optional) Displays only IPv4 adjacencies.
|
nexthop ipv4-address
|
(Optional) Displays adjacencies that are destined to the specified IPv4 nexthop.
|
mpls
|
(Optional) Displays only MPLS adjacencies.
|
ipv6
|
(Optional) Displays only IPv6 adjacencies.
|
type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
remote
|
(Optional) Displays only remote adjacencies. A remote adjacency is an internal adjacency used to forward packets between line cards.
|
detail
|
(Optional) Displays detailed adjacency information, including Layer 2 information.
|
location node-id
|
(Optional) Displays detailed CEF information for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This 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.
If you do not specify a node with the location keyword and node-id argument, this command displays the CEF adjacency table for the node on which the command is issued.
Examples
The following is sample output from show adjacency command with the location keyword specified:
RP/0/RP0/CPU0:router# show adjacency location 0/0/CPU0
Interface Address Version Refcount Protocol
POS0/0/1/2 (src mac only) 6 1 ipv4
POS0/0/1/2 point to point 7 100004
POS0/0/1/2 (interface) 3 1
The following is sample output from the show adjacency command with the detail and location keywords specified:
RP/0/RP0/CPU0:router# show adjacency ipv4 POS 0/0/0/2 detail location 0/0/CPU0
Interface Address Version Refcount Protocol
POS0/0/0/2 point to point 7 100004 ipv4
mtu: 4470, flags 0 0 40000000
The following is sample output from the show adjacency ipv4 nexthop command with the detail and location keywords specified:
RP/0/RP0/CPU0:router: show adjacency ipv4 nexthop 10.10.10.1 detail location 0/3/CPU0
Interface Address Version Refcount Protocol
POS0/3/1/0 10.10.10.1 11 6 ipv4
000c86f33d330800453a21c10800
mtu: 1500, flags 0 0 40000000
Table 9 describes the significant fields shown in the display.
Table 9 show adjacency Field Descriptions
Field
|
Description
|
Interface
|
Outgoing interface associated with the adjacency.
|
Address
|
Address can represent one of these addresses:
• Next hop IPv4 or IPv6 address
• Point-to-Point address
Information in parentheses indicates different types of adjacency.
|
Version
|
Version number of the adjacency. Updated whenever the adjacency is updated.
|
Refcount
|
Number of references to this adjacency.
|
Protocol
|
Protocol for which the adjacency is associated.
|
0f000800 and 000c86f33d330800453a21c10800
|
Layer 2 encapsulation string.
|
mtu
|
Value of the MTU1 .
|
flags
|
Internal field.
|
packets
|
Number of packets going through the adjacency.
|
bytes
|
Number of bytes going through the adjacency.
|
Related Commands
show cef ipv4
To display the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 command in EXEC mode.
show cef ipv4 [prefix [mask] | type instance] [detail] [location node-id]
Syntax Description
prefix
|
(Optional) Longest matching CEF entry for the specified IPv4 destination prefix.
|
mask
|
(Optional) Exact CEF entry for the specified IPv4 prefix and mask.
|
type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
detail
|
(Optional) Displays full CEF entry information.
|
location node-id
|
(Optional) Displays the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the CEF table on the node in which the command is issued. Otherwise, the command is effective on the node specified by the location node-id keyword and argument.
Examples
The following is sample output from the show cef ipv4 command:
RP/0/RP0/CPU0:router# show cef ipv4
Prefix Next Hop Interface
10.0.0.0/8 attached POS0/1/0/2
10.0.0.0/32 broadcast POS0/1/0/2
10.1.1.2/32 receive POS0/1/0/2
10.255.255.255/32 broadcast POS0/1/0/2
11.0.0.0/8 attached POS0/1/0/2
11.0.0.0/32 broadcast POS0/1/0/2
11.10.10.2/32 receive POS0/1/0/2
11.255.255.255/32 broadcast POS0/1/0/2
12.37.0.0/16 attached MgmtEth0/RP0/CPU0/0
12.37.0.0/32 broadcast MgmtEth0/RP0/CPU0/0
12.37.12.1/32 receive MgmtEth0/RP0/CPU0/0
12.37.46.1/32 12.31.46.1 MgmtEth0/RP0/CPU0/0
12.37.46.10/32 12.31.46.10 MgmtEth0/RP0/CPU0/0
12.37.255.255/32 broadcast MgmtEth0/RP0/CPU0/0
22.24.22.0/24 attached POS0/0/0/0
22.24.22.0/32 broadcast POS0/0/0/0
22.24.22.23/32 receive POS0/0/0/0
22.24.22.255/32 broadcast POS0/0/0/0
111.111.111.111/32 receive Loopback20
192.53.20.0/24 attached POS0/2/1/0
192.53.20.0/32 broadcast POS0/2/1/0
192.53.20.2/32 receive POS0/2/1/0
192.53.20.255/32 broadcast POS0/2/1/0
193.16.10.0/24 attached POS0/2/1/0
193.16.10.0/32 broadcast POS0/2/1/0
193.16.10.2/32 receive POS0/2/1/0
193.16.10.255/32 broadcast POS0/2/1/0
223.255.254.254/32 attached MgmtEth0/RP0/CPU0/0
255.255.255.255/32 broadcast
Table 10 describes the significant fields shown in the display.
Table 10 show cef ipv4 Field Descriptions
Field
|
Description
|
Prefix
|
Prefix in the IPv4 CEF table.
|
Next Hop
|
Next hop of the prefix.
|
Interface
|
Interface associated with the prefix.
|
Related Commands
show cef ipv4 drop
To display IPv4 Cisco Express Forwarding (CEF) table packet drop counters, use the show cef ipv4 drop command in EXEC mode.
show cef ipv4 drop [location node-id]
Syntax Description
location node-id
|
(Optional) Displays IPv4 CEF table packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
A packet might be dropped from the IPv4 CEF table because of unresolved CEF entries, unsupported features, absence of route information, absence of adjacency information, or an IP checksum error.
If you do not specify a node with the location keyword and node-id argument, this command displays IPv4 CEF packet drop counters for all nodes.
Examples
The following is sample output from the show cef ipv4 drop command:
RP/0/RP0/CPU0:router# show cef ipv4 drop
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 308
No Adjacency drops packets : 0
Checksum error drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
Unresolved drops packets : 0
Unsupported drops packets : 0
No route drops packets : 0
No Adjacency drops packets : 0
Checksum error drops packets : 0
Table 11 describes the significant fields shown in the display.
Table 11 show cef ipv4 drop Field Descriptions
Field
|
Description
|
Unresolved drops
|
Drops due to unresolved routes.
|
Unsupported drops
|
Drops due to an unsupported feature.
|
No route drops
|
Number of packets dropped because there were no routes to the destination.
|
No Adjacency drops
|
Number of packets dropped because there were no adjacencies established.
|
Checksum error drops
|
Drops due to IPv4 checksum error.
|
RPF drops
|
Drops due to IPv4 unicast RPF1 .
|
Related Commands
show cef ipv4 exact-route
To display an IPv4 Cisco Express Forwarding (CEF) exact route, use the show cef ipv4 exact-route command in EXEC mode.
show cef ipv4 exact-route {source-address destination-address} [detail | location node-id]
Syntax Description
detail
|
(Optional) Displays full CEF entry information.
|
location node-id
|
(Optional) Displays the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show cef ipv4 exact-route command:
RP/0/RP0/CPU0:router# show cef ipv4 exact-route 10.1.1.1 10.1.1.2 detail
K0.0.0.0/0, version 4, source-destination sharing
Prefix Len 0, traffic index 0, origin AS 0, precedence routine (0)
via 12.25.0.1, MgmtEth0/RP0/CPU0/0, 1 dependency
next hop 12.25.0.1/32, MgmtEth0/RP0/CPU0/0
Recursive load sharing using 12.25.0.1/32
Load distribution: 0 (refcount 2)
Hash OK Interface Address Packets
1 Y MgmtEth0/RP0/CPU0/0 12.25.0.1 13790
The following is sample output from the show cef ipv4 exact-route command with source-address and destination-address arguments specified:
RP/0/RP0/CPU0:router# show cef ipv4 exact-route 10.1.1.1 10.1.1.2 location 0/3/CPU0
Prefix Next Hop Interface
0.0.0.0/0 12.25.0.1 MgmtEth0/RP0/CPU0/0
12.25.0.0/16 attached MgmtEth0/RP0/CPU0/0
12.25.0.0/32 broadcast MgmtEth0/RP0/CPU0/0
12.25.0.1/32 12.25.0.1 MgmtEth0/RP0/CPU0/0
12.25.0.2/32 12.25.0.2 MgmtEth0/RP0/CPU0/0
12.25.12.11/32 receive MgmtEth0/RP0/CPU0/0
12.25.13.10/32 12.25.13.10 MgmtEth0/RP0/CPU0/0
12.25.13.12/32 12.25.13.12 MgmtEth0/RP0/CPU0/0
12.25.16.10/32 12.25.16.10 MgmtEth0/RP0/CPU0/0
12.25.16.11/32 12.25.16.11 MgmtEth0/RP0/CPU0/0
12.25.20.9/32 12.25.20.9 MgmtEth0/RP0/CPU0/0
12.25.20.10/32 12.25.20.10 MgmtEth0/RP0/CPU0/0
12.25.20.11/32 12.25.20.11 MgmtEth0/RP0/CPU0/0
12.25.20.12/32 12.25.20.12 MgmtEth0/RP0/CPU0/0
12.25.24.11/32 12.25.24.11 MgmtEth0/RP0/CPU0/0
12.25.24.12/32 12.25.24.12 MgmtEth0/RP0/CPU0/0
12.25.26.10/32 12.25.26.10 MgmtEth0/RP0/CPU0/0
12.25.26.12/32 12.25.26.12 MgmtEth0/RP0/CPU0/0
12.25.29.3/32 12.25.29.3 MgmtEth0/RP0/CPU0/0
12.25.41.4/32 12.25.41.4 MgmtEth0/RP0/CPU0/0
12.25.55.2/32 12.25.55.2 MgmtEth0/RP0/CPU0/0
12.25.57.3/32 12.25.57.3 MgmtEth0/RP0/CPU0/0
12.25.64.10/32 12.25.64.10 MgmtEth0/RP0/CPU0/0
12.25.255.255/32 broadcast MgmtEth0/RP0/CPU0/0
255.255.255.255/32 broadcast
Table 12 describes the significant fields shown in the display.
Table 12 show cef ipv4 exact-route Field Descriptions
Field
|
Description
|
Prefix
|
Prefix in the IPv4 CEF table.
|
Next Hop
|
Next hop of the prefix
|
Interface
|
Interface associated with the prefix
|
show cef ipv4 exceptions
To display IPv4 Cisco Express Forwarding (CEF) exception packet counters, use the show cef ipv4 exceptions command in EXEC mode.
show cef ipv4 exceptions [location node-id]
Syntax Description
location node-id
|
(Optional) Displays CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
CEF exception packets are those packets that have been sent from the hardware to the software because they require additional handling. The types of IPv4 CEF exception packets are displayed in the command's output and are defined.
If you do not specify a node with the location keyword and node-id argument, this command displays IPv4 CEF exception packet counters on all nodes.
Examples
The following is sample output from the show cef ipv4 exceptions command:
RP/0/RP0/CPU0:router# show cef ipv4 exceptions
Redirect packets : 0 Receive packets : 0
TTL expired packets : 314
Table 13 describes the significant fields shown in the display.
Table 13 show cef ipv4 exceptions Field Descriptions
Field
|
Description
|
Slow encap
|
Number of packets requiring special processing during encapsulation.
|
Redirect
|
Number of ICMP1 redirect messages sent.
|
Receive
|
Number of packets destined to the router.
|
Broadcast
|
Number of broadcasts received.
|
IP options
|
Number of IP option packets.
|
TTL expired
|
Number of packets with expired TTLs2 .
|
Fragmented
|
Number of packets that have been fragmented.
|
Related Commands
show cef ipv4 interface
To display IPv4 Cisco Express Forwarding (CEF)-related information for an interface, use the show cef ipv4 interface command in EXEC mode.
show cef ipv4 interface type instance [detail] [location node-id]
Syntax Description
type
|
Displays the interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
detail
|
(Optional) Displays detailed CEF information for all the interfaces on the node in which the command is issued.
|
location node-id
|
(Optional) Displays IPv4 CEF-related information for an interface. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the CEF-related information for an interface for all nodes.
Examples
The following is sample output from the show cef ipv4 interface command:
RP/0/RP0/CPU0:router# show cef ipv4 interface MgmtEth 0/RP0/CPU0/0
MgmtEth0/RP0/CPU0/0 is up (if_handle 0x00180020)
ICMP redirects are always sent
Table 14 describes the significant fields shown in the display.
Table 14 show cef ipv4 interface Field Descriptions
Field
|
Description
|
MgmtEth 0/RP0/CPU0/0 is up
|
Status of the interface.
|
if_handle
|
Internal interface handle.
|
ICMP redirects are always sent or never sent
|
Indicates whether ICMP1 redirect messages should be sent. By default, ICMP redirect messages are always sent.
|
IP MTU
|
Value of the IPv4 MTU2 size set on the interface.
|
Reference count
|
Internal reference counter.
|
show cef ipv4 interface bgp-policy-statistics
To display IPv4 Cisco Express Forwarding (CEF)-related BGP policy statistics information for an interface, use the show cef ipv4 interface bgp-policy-statistics command in EXEC mode.
show cef ipv4 interface type instance bgp-policy-statistics
Syntax Description
type
|
Displays the interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command displays all the configured BGP policy counters for the specified interface.
Examples
The following is sample output from the show cef ipv4 interface bgp-policy-statistics command:
RP/0/RP0/CPU0:router# show cef ipv4 interface TenGigE 0/2/0/4 bgp-policy-statistics
Input BGP policy accounting on src IP address enabled
Output BGP policy accounting on dst IP address enabled
Output BGP policy accounting on src IP address enabled
Table 15 describes the significant fields shown in the display.
Table 15 show cef ipv4 interface bgp-policy-statistics Field Descriptions
Field
|
Description
|
TenGigE 0/2/0/4 is up
|
Status of the interface.
|
Input BGP policy accounting on src IP address enabled
|
Enabled BGP policy accounting features.
|
buckets
|
Traffic index.
|
packets
|
Number of packets counted in the bucket.
|
bytes
|
Number of bytes counted in the bucket.
|
show cef ipv4 non-recursive
To display the IPv4 nonrecursive prefix entries in the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 non-recursive command in EXEC mode.
show cef ipv4 non-recursive [detail] [type instance] [location node-id]
Syntax Description
detail
|
(Optional) Displays detailed information about nonrecursive prefix entries in the IPv4 CEF table.
|
type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
instance
|
(Optional) Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
location node-id
|
(Optional) Displays the IPv4 nonrecursive prefix entries in the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the IPv4 CEF nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv4 non-recursive
Prefix Next Hop Interface
10.0.0.0/8 attached POS0/1/1/2
10.0.0.0/32 broadcast POS0/1/1/2
10.1.1.2/32 receive POS0/1/1/2
10.255.255.255/32 broadcast POS0/1/1/2
11.0.0.0/8 attached POS0/1/1/2
11.0.0.0/32 broadcast POS0/1/1/2
11.10.10.2/32 receive POS0/1/1/2
11.255.255.255/32 broadcast POS0/1/1/2
12.37.0.0/16 attached MgmtEth0/RP0/CPU0/0
12.37.0.0/32 broadcast MgmtEth0/RP0/CPU0/0
12.37.12.1/32 receive MgmtEth0/RP0/CPU0/0
12.37.46.1/32 12.31.46.1 MgmtEth0/RP0/CPU0/0
12.37.46.10/32 12.31.46.10 MgmtEth0/RP0/CPU0/0
12.37.255.255/32 broadcast MgmtEth0/RP0/CPU0/0
22.24.22.0/24 attached POS0/0/1/0
22.24.22.0/32 broadcast POS0/0/1/0
22.24.22.23/32 receive POS0/0/1/0
22.24.22.255/32 broadcast POS0/0/1/0
111.111.111.111/32 receive Loopback20
192.51.20.0/24 attached POS0/2/1/1
192.51.20.0/32 broadcast POS0/2/1/1
192.51.20.2/32 receive POS0/2/1/1
192.51.20.255/32 broadcast POS0/2/1/1
193.16.10.0/24 attached POS0/2/1/1
193.16.10.0/32 broadcast POS0/2/1/1
193.16.10.2/32 receive POS0/2/1/1
193.16.10.255/32 broadcast POS0/2/1/1
223.255.254.254/32 223.255.254.254 MgmtEth0/RP0/CPU0/0
255.255.255.255/32 broadcast
Table 16 describes the significant fields shown in the display.
Table 16 show cef ipv4 non-recursive Field Descriptions
Field
|
Description
|
Prefix
|
Nonrecursive prefixes detected on the node.
|
Next Hop
|
Routing next hop.
|
Interface
|
Interface associated with the nonrecursive prefix.
|
show cef ipv4 summary
To display a summary of the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 summary command in EXEC mode.
show cef ipv4 summary [location node-id]
Syntax Description
location node-id
|
(Optional) Displays a summary of the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays a summary of the IPv4 CEF table for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 summary command:
RP/0/RP0/CPU0:router# show cef ipv4 summary
IP CEF with switching (Table Version 45)
37 routes, 0 reresolve, 0 unresolved (0 old, 0 new)
27 load sharing elements, 13176 bytes, 27 references
0 CEF resets, 0 revisions of existing leaves
Exponential (currently 1s, peak 0s)
0 prefixes modified in place
Adjacency Table has 16 adjacencies
Table 17 describes the significant fields shown in the display.
Table 17 show cef ipv4 summary Field Descriptions
Field
|
Description
|
Table Version
|
Version of the CEF table.
|
routes
|
Total number of routes.
|
reresolve
|
Total number of routes being reresolved.
|
unresolved (x old, x new)
|
Number of routes not yet resolved.
|
load sharing elements
|
Total number of internal load-sharing data structures.
|
bytes
|
Total memory used by internal load sharing data structures.
|
references
|
Total reference count of all internal load sharing data structures.
|
CEF resets
|
Number of CEF table resets.
|
revisions of existing leaves
|
Number of updates to existing prefixes.
|
Exponential (currently xs, peak xs)
|
Currently not used.
|
prefixes modified in place
|
Prefixes modified in place.
|
Adjacency Table has x adjacencies
|
Total number of adjacencies.
|
x incomplete adjacency
|
Total number of incomplete adjacencies.
|
show cef ipv4 unicast check-consistency
To display results of IPv4 unicast consistency checking, use the show cef ipv4 unicast check-consistency command in EXEC mode.
show cef ipv4 unicast check-consistency [prefix mask | log] [location node-id]
Syntax Description
prefix mask
|
(Optional) IPv4 prefix and mask. Specifying an IPv4 prefix and mask with the prefix and mask arguments displays the results of the consistency checks for a range of route entries.
|
log
|
(Optional) Displays the contents of the consistency check log, which is a circular buffer that displays up to the last 1000 inconsistencies before starting over.
|
location node-id
|
(Optional) Displays the results of IPv4 unicast consistency checking for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Issuing the show cef ipv4 unicast check-consistency command causes an instantaneous IPv4 unicast prefix consistency check to be performed, whether or not you have enabled IPv4 unicast prefix consistency checking with the cef ipv4 unicast check-consistency command. The output, accordingly, displays the results from that instantaneous consistency check.
To enable periodic background IPv4 unicast prefix consistency checking, you must enable the cef ipv4 unicast consistency-check command.
Use the show cef ipv4 unicast check-consistency log command to display the contents of the IPv4 unicast consistency check log, which records the number of consistency checks that have been performed and the number of errors that have been detected. The output of the show cef ipv4 unicast check-consistency command displays the results of both background and instantaneous consistency checks.
If you do not specify a node with the location keyword and node-id argument, this command displays IPv4 unicast consistency-check information for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 unicast check-consistency command:
RP/0/RP0/CPU0:router# show cef ipv4 unicast check-consistency
---------------------------------------------------------------------------
node checks performed errors
Mon Aug 25 19:50:08 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:50:08 2003: 10.5.0.0/16 :node 0/2/CPU0 :Path info error
Mon Aug 25 19:50:08 2003: 10.5.0.0/16 :node 0/4/CPU0 :Path info error
The following is sample output from the show cef ipv4 unicast check-consistency command where a range of prefix entries is specified:
RP/0/RP0/CPU0:router# show cef ipv4 unicast check-consistency 10.0.0.0 255.255.255.0
---------------------------------------------------------------------------
node checks performed errors
The following is sample output from the show cef ipv4 unicast check-consistency log command:
RP/0/RP0/CPU0:router# show cef ipv4 unicast check-consistency log
IPv4-Unicast enabled table wraps = 36
---------------------------------------------------------------------------
node checks performed errors
Mon Aug 25 19:27:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:28:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:28:53 2003: 10.5.0.0/16 :node 0/4/CPU0 :Path info error
Mon Aug 25 19:29:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:29:53 2003: 10.5.0.0/16 :node 0/4/CPU0 :Path info error
Mon Aug 25 19:29:53 2003: 10.5.0.0/16 :node 0/2/CPU0 :Path info error
Mon Aug 25 19:30:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:30:53 2003: 10.5.0.0/16 :node 0/4/CPU0 :Path info error
Mon Aug 25 19:31:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:31:53 2003: 10.5.0.0/16 :node 0/4/CPU0 :Path info error
Mon Aug 25 19:31:53 2003: 10.5.0.0/16 :node 0/2/CPU0 :Path info error
Mon Aug 25 19:32:53 2003: 10.5.0.0/16 :node 0/6/CPU0 :Path info error
Mon Aug 25 19:32:53 2003: 10.5.0.0/16 :node 0/2/CPU0 :Path info error
Table 18 describes the significant fields shown in the display.
Table 18 show cef ipv4 unicast check-consistency Field Descriptions
Field
|
Description
|
node
|
Nodes where the consistency checks have been performed.
|
checks performed
|
Number of consistency checks performed on the corresponding node.
|
errors
|
Number of consistency check errors reported on the corresponding node.
|
table wraps
|
Number of times a complete table has been checked.
|
Related Commands
show cef ipv4 unresolved
To display unresolved routes in the IPv4 Cisco Express Forwarding (CEF) table, use the show cef ipv4 unresolved command in EXEC mode.
show cef ipv4 unresolved [location node-id]
Syntax Description
location node-id
|
(Optional) Displays the unresolved routes in the IPv4 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, the output displays the unresolved routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv4 unresolved command when an unresolved route is detected:
RP/0/RP0/CPU0:router# show cef ipv4 unresolved
Prefix Next Hop Interface
Table 19 describes the significant fields shown in the display.
Table 19 show cef ipv4 unresolved Field Descriptions
Field
|
Description
|
Prefix
|
Prefix of the unresolved CEF.
|
Next Hop
|
Next hop of the unresolved CEF.
|
Interface
|
Next hop interface. A question mark (?) indicates that the interface has not been resolved.
|
show cef ipv6
To display the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 command in EXEC mode.
show cef ipv6 [interface-type interface-number | ipv6-prefix/prefix-length] [detail] [location
node-id]
Syntax Description
interface-type interface-number
|
(Optional) IPv6 prefixes going through the specified next hop interface.
|
ipv6-prefix/prefix-length
|
(Optional) Longest prefix entry in the CEF table matching the specified IPv6 prefix and prefix length.
|
detail
|
(Optional) Displays detailed IPv6 CEF table information.
|
location node-id
|
(Optional) Displays the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the IPv6 CEF table for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 command:
RP/0/RP0/CPU0:router# show cef ipv6
recursive fe80::3031:48ff:fe53:5533, POS0/3/0/0
recursive fe80::205:5fff:fe1d:7600, POS0/4/0/0
Table 20 describes the significant fields shown in the display.
Table 20 show cef ipv6 Field Descriptions
Field
|
Description
|
drop
|
Indicates that packets sent to the destination prefix are dropped.
|
loopback
|
Indicates that the prefix points to a loopback address. Packets sent to loopback addresses are dropped.
|
receive
|
Indicates that the prefix is configured on one of the router interfaces. Packets sent to those prefixes are received by the router.
|
connected
|
Indicates that the prefix points to a directly connected next-hop interface.
|
recursive
|
Indicates that the prefix is not directly connected but is reachable through the next-hop prefix displayed.
|
The following is sample output from show cef ipv6 detail:
RP/0/RP0/CPU0:router# show cef ipv6 detail
Loadinfo owner: <this route>
Loadinfo owner: <this route>
interface : <not specified>
flags: loopback, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_rib
Loadinfo owner: <this route>
flags: connected, no_nexthops, source_rib
Loadinfo owner: <this route>
flags: receive, source_rib
Loadinfo owner: <this route>
flags: connected, no_nexthops, source_rib
Loadinfo owner: <this route>
flags: receive, source_rib
Loadinfo owner: <this route>
flags: recursive, host_route, shared_loadinfo, source_rib
Loadinfo owner: fe80::/10
next hop : fe80::3031:48ff:fe53:5533
flags: connected, source_rib
Loadinfo owner: <this route>
flags: receive, source_rib
Loadinfo owner: <this route>
flags: recursive, host_route, shared_loadinfo, source_rib
Loadinfo owner: fe80::/10
next hop : fe80::205:5fff:fe1d:7600
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_fib
Loadinfo owner: <this route>
interface : <not specified>
flags: receive, source_fib
Loadinfo owner: <this route>
interface : <not specified>
Table 21 describes the significant output fields shown in the display.
Table 21 show cef ipv6 detail Field Descriptions
Field
|
Description
|
flags:
|
Properties of the indicated prefix.
|
Loadinfo owner:
|
Owner of the Loadinfo used by the prefix for forwarding. The Loadinfo owner is the prefix that owns the array of pointers to adjacencies.
|
fast adj:
|
Cached adjacency used for forwarding.
|
path 1:
|
The following three items are displayed below path 1:
• flags-Properties of the path.
• next hop-Next-hop prefix if the packet is being forwarded.
• interface-Next-hop interface if the packet is being forwarded.
|
show cef ipv6 drop
To display IPv6 Cisco Express Forwarding (CEF) table packet drop counters, use the show cef ipv6 drop command in EXEC mode.
show cef ipv6 drop [location node-id]
Syntax Description
location node-id
|
(Optional) Displays IPv6 CEF table packet drop counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
A packet might be dropped by the IPv6 CEF table because of unresolved CEF entries, unsupported features, absence of route information, absence of adjacency information, or an IP checksum error.
If you do not specify a node with the location keyword and node-id argument, this command displays the packet drops for all nodes.
Note
Because no hardware forwarding occurs on the route processor (RP), no packet drop information is displayed for that node.
Examples
The following is sample output from the show cef ipv6 drop command:
RP/0/RP0/CPU0:router# show cef ipv6 drop location 0/2/CPU0
Line status down ingress : 0 egress : Not Applicable
Packet sanity fail ingress : 0 egress : 0
PLU set to drop ingress : 0 egress : 0
Unknown type,plu drop ingress : 0 egress : 0
Packet length err ingress : 0 egress : 0
TCAM src-comp err ingress : 0 egress : 0
Table 22 describes the significant fields shown in the display.
Table 22 show cef ipv6 drop Field Descriptions
Field
|
Description
|
Line status down
|
Packet drops due to the line protocol of the incoming interface being down.
|
Packet sanity fail
|
Packet drops due to the prefix failing the IPv6 sanity test. The sanity test verifies that the IPv6 packet is valid.
|
PLU set to drop
|
Packet drops due the IPv6 destination prefix being set to drop.
|
Unknown type, plu drop
|
Packet drops due to the prefix being of an unknown type.
|
Packet length errs
|
Length specified in the header does not match the actual length of the packet received.
|
TCAM src-comp err
|
Packet drops due to source compression errors that have occurred in the hardware.
|
Related Commands
show cef ipv6 exact-route
To display the path an IPv6 flow comprising a source and destination address would take, use the show cef ipv6 exact-route command in EXEC mode.
show cef ipv6 exact-route {source-address destination-address} [detail | location node-id]
Syntax Description
detail
|
(Optional) Displays full CEF entry information.
|
location node-id
|
(Optional) Displays the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show cef ipv6 exact-route command:
RP/0/RP0/CPU0:router# show cef ipv6 exact-route 222::2 9999::6751 loc
0/3/CPU0 source address: 222::2 destination address: 9999::6751
interface : TenGigE0/3/0/3 non local interface
show cef ipv6 exceptions
To display IPv6 Cisco Express Forwarding (CEF) exception packet counters, use the show cef ipv6 exceptions command in EXEC command.
show cef ipv6 exceptions [location node-id]
Syntax Description
location node-id
|
(Optional) Displays IPv6 CEF exception packet counters for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
CEF exception packets are those packets that have been sent from the hardware to the software because they require additional handling. The types of IPv6 CEF exception packets are displayed in the output of show cef ipv6 exceptions.
If you do not specify a node with location keyword and node-id argument, this command displays IPv6 CEF exception packet counters for all nodes.
Examples
The following is sample output from the show cef ipv6 exceptions command:
RP/0/RP0/CPU0:router: show cef ipv6 exceptions location 0/3/CPU0
IPv6 CEF Exception Statistics
TTL err ingress : 0 egress : Not Applicable
Link-local dst addr ingress : 0 egress : 0
Hop-by-Hop header ingress : 0 egress : 0
PLU entry set to punt ingress : 0 egress : 20
Packet too big ingress : Not Applicable egress : 0
Med priority punt ingress : 0 egress : Not Applicable
Table 23 describes the significant fields shown in the display.
Table 23 show cef ipv6 exceptions Field Descriptions
Field
|
Description
|
TTL err
|
Packets sent to software for processing because the packet header of the IPv6 prefix had a TTL1 error.
|
Link-local dst addr
|
Packets sent to the software for processing because the destination address of the IPv6 prefix is link local.
|
Hop-by-Hop header
|
Packets sent to the software for processing because the IPv6 packet has a hop-by-hop header.
|
PLU entry set to punt
|
Packets sent to software for processing because the IPv6 prefix is set to punt.
|
Packet too big
|
Packets sent to the software for processing because the packet size exceeded the MTU2 .
|
Med priority punt
|
Field used internally for troubleshooting.
|
Related Commands
show cef ipv6 non-recursive
To display the IPv6 nonrecursive prefix entries in the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 non-recursive command in EXEC mode.
show cef ipv6 non-recursive [location node-id]
Syntax Description
location node-id
|
(Optional) Displays the nonrecursive prefix entries in the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the nonrecursive routes for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 non-recursive command:
RP/0/RP0/CPU0:router# show cef ipv6 non-recursive
Table 24 describes the significant fields shown in the display.
Table 24 show cef ipv6 non-recursive Field Descriptions
Field
|
Description
|
drop
|
Indicates that packets sent to the destination prefix are dropped.
|
loopback
|
Indicates that the prefix points to a loopback address. Packets sent to loopback addresses are dropped.
|
receive
|
Indicates that the prefix is configured on one of the router interfaces. Packets sent to those prefixes are received by the router.
|
connected
|
Indicates that the prefix points to a directly connected next-hop interface.
|
show cef ipv6 summary
To display a summary of the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 summary command in EXEC mode.
show cef ipv6 summary [location node-id]
Syntax Description
location node-id
|
(Optional) Displays a summary of the IPv6 CEF table for the designated node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays a summary of the IPv6 CEF table for the node on which the command is issued.
Examples
The following is sample output from the show cef ipv6 summary command:
RP/0/RP0/CPU0:router# show cef ipv6 summary
IPv6 CEF with switching (Table Version 0)
9 routes, 0 background, 0 pending, 0 unresolved paths
9 load sharing elements, 324 bytes, 9 references
3384 bytes fib leaf memory
Adjacency Table has 15 adjacencies
Table 17 describes the significant fields shown in the display.
Table 25 show cef ipv6 summary Field Descriptions
Field
|
Description
|
Table Version
|
Version of the CEF table.
|
routes
|
Total number of routes.
|
unresolved (x old, x new)
|
Number of routes not yet resolved.
|
load sharing elements
|
Total number of internal load-sharing data structures.
|
bytes
|
Total memory used by internal load sharing data structures.
|
references
|
Total reference count of all internal load sharing data structures.
|
CEF resets
|
Number of CEF table resets.
|
revisions of existing leaves
|
Number of updates to existing prefixes.
|
Exponential (currently xs, peak xs)
|
Currently not used.
|
prefixes modified in place
|
Prefixes modified in place.
|
Adjacency Table has x adjacencies
|
Total number of adjacencies.
|
x incomplete adjacency
|
Total number of incomplete adjacencies.
|
show cef ipv6 unresolved
To display the unresolved routes in the IPv6 Cisco Express Forwarding (CEF) table, use the show cef ipv6 unresolved command in EXEC mode.
show cef ipv6 unresolved [location node-id]
Syntax Description
location node-id
|
(Optional) Displays the unresolved routes in the IPv6 CEF table for the specified node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a node with the location keyword and node-id argument, this command displays the unresolved routes for the node on which the command is issued.
Examples
This following is sample output from show cef ipv6 unresolved command when an unresolved route is detected:
RP/0/RP0/CPU0:router# show cef ipv6 unresolved
Table 26 describes the significant fields shown in the display.
Table 26 show cef ipv6 unresolved Field Descriptions
Field
|
Description
|
xxxx::/xx
|
Detected unresolved route.
|