Feedback
Contents
- IP Routing Protocol-Independent Commands: S through T
- send-lifetime
- set automatic-tag
- set default interface
- set interface
- set ip default next-hop
- set ip default next-hop verify-availability
- set ip global
- set ip next-hop
- set ip next-hop verify-availability
- set ip vrf
- set level (IP)
- set local-preference
- set metric (BGP-OSPF-RIP)
- set metric-type
- set next-hop
- set tag (IP)
- set ipv6 default next-hop
- set ipv6 next-hop (PBR)
- set ipv6 precedence
- show bfd drops
- show bfd neighbors
- show bfd summary
- show dampening interface
- show fm ipv6 pbr all
- show fm ipv6 pbr interface
- show interface dampening
- show ip cef platform
- show ip static route bfd
- show ip cache policy
- show ip local policy
- show ip policy
- show ip protocols
- show ip route
- show ip route loops
- show ip route profile
- show ip route summary
- show ip route supernets-only
- show ip route tag
- show ip route track-table
- show ip route vrf
- show ip static route
- show ip static route bfd
- show ipv6 policy
- show ipv6 route
- show ipv6 route shortcut
- show ipv6 route summary
- show ipv6 route tag
- show ipv6 route vrf
- show isis fast-reroute
- show key chain
- show monitor event-trace
- show platform hardware qfp active feature cef-mpls prefix ip
- show platform hardware qfp active feature cef-mpls prefix ipv6
- show platform hardware qfp active feature cef-mpls prefix mpls
- show route-map
- show route-tag list
- traffic-share min
- vccv
- vccv bfd status signaling
- vccv bfd template
IP Routing Protocol-Independent Commands: S through T
send-lifetime
To set the time period during which an authentication key on a key chain is valid to be sent, use the send-lifetime command in key chain key configuration mode. To revert to the default value, use the no form of this command.
Syntax Description
Command History
|
Release |
Modification |
|---|---|
|
11.1 |
This command was introduced. |
|
12.4(6)T |
Support for IPv6 was added. |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Specify a start-time value and one of the following values: infinite, end-time, or duration seconds.
We recommend running Network Time Protocol (NTP) or some other time synchronization method if you intend to set lifetimes on keys.
If the last key expires, authentication will continue and an error message will be generated. To disable authentication, you must manually delete the last valid key.
Examples
The following example configures a key chain named chain1. The key named key1 will be accepted from 1:30 p.m. to 3:30 p.m. and be sent from 2:00 p.m. to 3:00 p.m. The key named key2 will be accepted from 2:30 p.m. to 4:30 p.m. and be sent from 3:00 p.m. to 4:00 p.m. The overlap allows for migration of keys or a discrepancy in the set time of the router. There is a 30-minute leeway on each side to handle time differences.
Router(config)# interface ethernet 0 Router(config-if)# ip rip authentication key-chain chain1 Router(config-if)# ip rip authentication mode md5 ! Router(config)# router rip Router(config-router)# network 172.19.0.0 Router(config-router)# version 2 ! Router(config)# key chain chain1 Router(config-keychain)# key 1 Router(config-keychain-key)# key-string key1 Router(config-keychain-key)# accept-lifetime 13:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 14:00:00 Jan 25 1996 duration 3600 Router(config-keychain-key)# exit Router(config-keychain)# key 2 Router(config-keychain-key)# key-string key2 Router(config-keychain-key)# accept-lifetime 14:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 15:00:00 Jan 25 1996 duration 3600
The following example configures a key chain named chain1 for EIGRP address-family. The key named key1 will be accepted from 1:30 p.m. to 3:30 p.m. and be sent from 2:00 p.m. to 3:00 p.m. The key named key2 will be accepted from 2:30 p.m. to 4:30 p.m. and be sent from 3:00 p.m. to 4:00 p.m. The overlap allows for migration of keys or a discrepancy in the set time of the router. There is a 30-minute leeway on each side to handle time differences.
Router(config)# eigrp virtual-name Router(config-router)# address-family ipv4 autonomous-system 4453 Router(config-router-af)# network 10.0.0.0 Router(config-router-af)# af-interface ethernet0/0 Router(config-router-af-interface)# authentication key-chain trees Router(config-router-af-interface)# authentication mode md5 Router(config-router-af-interface)# exit Router(config-router-af)# exit Router(config-router)# exit Router(config)# key chain chain1 Router(config-keychain)# key 1 Router(config-keychain-key)# key-string key1 Router(config-keychain-key)# accept-lifetime 13:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 14:00:00 Jan 25 1996 duration 3600 Router(config-keychain-key)# exit Router(config-keychain)# key 2 Router(config-keychain-key)# key-string key2 Router(config-keychain-key)# accept-lifetime 14:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 15:00:00 Jan 25 1996 duration 3600
Related Commands
|
Command |
Description |
|---|---|
|
accept-lifetime |
Sets the time period during which the authentication key on a key chain is received as valid. |
|
key |
Identifies an authentication key on a key chain. |
|
key chain |
Defines an authentication key chain needed to enable authentication for routing protocols. |
|
key-string (authentication) |
Specifies the authentication string for a key. |
|
show key chain |
Displays authentication key information. |
set automatic-tag
To automatically compute the tag value, use the setautomatic-tag command in route-map configuration mode. To disable this function, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the matchcriteria--the conditions under which redistribution is allowed for the current route-mapcommand. The set commands specify the setactions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The noroute-map command deletes the route map.
The set route-map configuration commands specify the redistribution setactions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example configures the Cisco IOS software to automatically compute the tag value for the Border Gateway Protocol (BGP) learned routes:
route-map tag match as path 10 set automatic-tag ! router bgp 100 table-map tag
Related Commands
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes any routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set as-path |
Modifies an autonomous system path for BGP routes. |
|
set community |
Sets the BGP communities attribute. |
|
set level (IP) |
Indicates where to import routes. |
|
set local-preference |
Specifies a preference value for the autonomous system path. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set next-hop |
Specifies the address of the next hop. |
|
set tag (IP) |
Sets a tag value of the destination routing protocol. |
|
set weight |
Specifies the BGP weight for the routing table. |
|
show route-map |
Displays all route maps configured or only the one specified. |
set default interface
To indicate where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination, use the set default interface command in route-map configuration mode. To delete an entry, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
11.0 |
This command was introduced. |
|
12.3(7)T |
This command was modified. This command was updated for use in configuring IPv6 policy-based routing (PBR). |
|
12.2(30)S |
This command was integrated into Cisco IOS Release 12.2(30)S. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 3.2S |
This command was integrated into Cisco IOS XE Release 3.2S. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the type and number arguments .
Use this command to provide certain users a different default route. If Cisco software has no explicit route for the destination, then it routes the packet to this interface. The first interface specified with the set default interface command is used. The optionally specified interfaces are tried in turn.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
In PBR for IPv6, use the ipv6 policy route-map or ipv6 local policyroute-map command with match and set route map configuration commands to define conditions for policy routing packets.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
Examples
In the following example, packets that have a Level 3 length of 3 to 50 bytes and for which the software has no explicit route to the destination are output to Ethernet interface 0:
interface serial 0 ip policy route-map brighton ! route-map brighton match length 3 50 set default interface ethernet 0
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
ipv6 local policy route-map |
Identifies a route map to use for local IPv6 PBR. |
|
ipv6 policy route-map |
Configures IPv6 PBR on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ipv6 address |
Distributes IPv6 routes that have a prefix permitted by a prefix list or specifies an IPv6 access list to use to match packets for PBR for IPv6. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of route map for policy routing. |
|
set ip default next-hop verify-availability |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination. |
|
set ipv6 default next-hop |
Specifies an IPv6 default next hop to which matching packets will be forwarded. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ipv6 next-hop (PBR) |
Indicates where to output IPv6 packets that pass a match clause of a route map for policy routing. |
|
set ipv6 precedence |
Sets the precedence value in the IPv6 packet header. |
set interface
To indicate where to forward packets that pass a match clause of a route map for policy routing, use the set interface command in route-map configuration mode. To delete an entry, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
11.0 |
This command was introduced. |
|
12.3(7)T |
This command was modified. This command was updated for use in configuring IPv6 policy-based routing (PBR). |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB, and hardware switching support was introduced for the Cisco 7600 series platform. |
|
12.2SX |
This command was integrated into the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 3.2S |
This command was integrated into Cisco IOS XE Release 3.2S. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the type and number arguments .
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy-routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
In PBR for IPv6, use the ipv6 policy route-map or ipv6 local policy route-map command with match and set route-map configuration commands to define conditions for policy-routing packets.
If the first interface specified with the set interface command is down, the optionally specified interfaces are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
A useful next hop implies an interface. As soon as a next hop and an interface are found, the packet is routed.
Specifying the set interface null 0 command is a way to write a policy that the packet be dropped and an "unreachable" message be generated. In Cisco IOS Release 12.4(15)T and later releases, the packets are dropped; however, the "unreachable" messages are generated only when CEF is disabled.
In Cisco IOS Release 12.2(33)SRB and later releases, hardware switching support was introduced for PBR packets sent over a traffic engineering (TE) tunnel interface on a Cisco 7600 series router. When a TE tunnel interface is configured using the set interface command in a policy, the packets are processed in the hardware. In previous releases, PBR packets sent over TE tunnels are fast switched by Route Processor software.
Examples
In the following example, packets with a Level 3 length of 3 to 50 bytes are forwarded to Ethernet interface 0:
interface serial 0 ip policy route-map testing ! route-map testing match length 3 50 set interface ethernet 0
The following example for IPv6 shows that packets with a Level 3 length of 3 to 50 bytes are forwarded to Ethernet interface 0:
interface serial 0 ipv6 policy route-map testing ! route-map testing match length 3 50 set interface ethernet 0
In the following example, a TE tunnel interface is configured on a Cisco 7600 series router using the set interface command in a policy, and the packets are processed in hardware, instead of being fast switched by Route Processor software. This example can be used only with a Cisco IOS Release 12.2(33)SRB, or later release image.
interface Tunnel101 description FRR-Primary-Tunnel ip unnumbered Loopback0 tunnel destination 172.17.2.2 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng path-option 1 explicit name p1 ! access-list 101 permit ip 10.100.0.0 0.255.255.255 any ! route-map test permit 10 match ip address 101 set interface Tunnel101 ! interface GigabitEthernet9/5 description TO_CE_C1A_FastEther-5/5 ip address 192.168.5.1 255.255.255.0 ip policy route-map test no keepalive
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
ipv6 local policy route-map |
Configures PBR for IPv6 for originated packets. |
|
ipv6 policy route-map |
Configures IPv6 PBR on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ipv6 address |
Specifies an IPv6 access list to use to match packets for PBR for IPv6. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map |
Defines the conditions for redistributing routes from one routing protocol into another or enables policy routing. |
|
set default interface |
Indicates where to forward packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set ip default next-hop verify-availability |
Indicates where to forward packets that pass a match clause of a route map for policy routing and for which the Cisco software has no explicit route to a destination. |
|
set ip next-hop |
Indicates where to forward packets that pass a match clause of a route map for policy routing. |
|
set ipv6 default next-hop |
Specifies an IPv6 default next hop to which matching packets will be forwarded. |
|
set ipv6 next-hop (PBR) |
Indicates where to output IPv6 packets that pass a match clause of a route map for policy routing. |
|
set ipv6 precedence |
Sets the precedence value in the IPv6 packet header. |
set ip default next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination, use the setipdefaultnext-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
11.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument .
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, then it routes the packet to this next hop. The first next hop specified with the setipdefaultnext-hopcommand needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ippolicyroute-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the matchcriteria--the conditions under which policy routing occurs. The set commands specify the setactions--the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
Examples
The following example provides two sources with equal access to two different service providers. Packets arriving on asynchronous interface 1 from the source 10.1.1.1 are sent to the router at 172.16.6.6 if the software has no explicit route for the destination of the packet. Packets arriving from the source 10.2.2.2 are sent to the router at 172.17.7.7 if the software has no explicit route for the destination of the packet. All other packets for which the software has no explicit route to the destination are discarded.
access-list 1 permit ip 10.1.1.1 0.0.0.0 access-list 2 permit ip 10.2.2.2 0.0.0.0 ! interface async 1 ip policy route-map equal-access ! route-map equal-access permit 10 match ip address 1 set ip default next-hop 172.16.6.6 route-map equal-access permit 20 match ip address 2 set ip default next-hop 172.17.7.7 route-map equal-access permit 30 set default interface null0
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of route map for policy routing. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
set ip default next-hop verify-availability
To configure a router, for policy routing, to check the CDP database for the availability of an entry for the default next hop that is specified by the set ip default next-hop command, use the set ip default next-hop verify-availability route map configuration command. To disable this function, use the no form of this command.
Usage Guidelines
Use this command to force the configured policy routing to check the CDP database to determine if an entry is available for the next hop that is specified by the set ip default next-hop command. This command is used to prevent traffic from being "black holed" if the configured next hop becomes unavailable.
Examples
The following example:
Router(config-route-map)# set ip default next-hop verify-availability
Related Commands
|
Command |
Description |
|---|---|
|
set ip default next-hop verify-availability |
Configures policy routing to verify if the next hops of a route map are CDP neighbors before policy routing to those next hops. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
set ip global
To indicate where to forward packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software uses the global routing table, use the setipglobalcommand in route-map configuration mode. To disable this feature, use the no form of this command.
Usage Guidelines
Use this command to allow packets to enter a VRF interface and be policy-routed or forwarded out of the global table.
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Examples
The following example allows use of the global table and specifies that the next-hop address is 10.5.5.5:
set ip global next-hop 10.5.5.5
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ip default next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination. |
|
set ip vrf |
Indicates where to forward packets that pass a match clause of a route map for policy routing when the next hop must be under a specified VRF name. |
set ip next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing, use the set ip next-hop command in route-map configuration mode. To delete an entry indicating where to output the packets, use the no form of this command.
Syntax Description
Command History
|
Release |
Modification |
|---|---|
|
11.0 |
This command was introduced. |
|
12.0(28)S |
This command was modified. The recursive keyword was added. |
|
12.3(14)T |
This command was integrated into Cisco IOS Release 12.3(14)T. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 2.2 |
In Cisco IOS XE Release 2.2, this command was integrated into the Cisco ASR 1000 Series Routers. |
|
12.2(33)SRE |
This command was modified. The encapsulate and l3vpn keywords were added. |
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--particular routing actions to be performed if the criteria enforced by the match commands are met.
If the interface associated with the first next hop, which is specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
 Note | The set ip next-hop and the set ip default next-hop commands are similar but have a different order of operations. Configuring the set ip next-hop command causes the system to use policy-based routing first and then use the routing table. Configuring the set ip default next-hop command causes the system to use the routing table first and then the policy route to the specified next hop. |
Note | The set ip next-hop command does not support Inherit-VRF routing on Cisco 7600 series routers because the set ip next-hop ip-address command is treated as equivalent to the set ip global next-hop ip-address command on Cisco 7600 series routers. (Inherit-VRF routing enables packets arriving on a VRF interface to be routed by the same outgoing interface.) Therefore, when using Cisco 7600 series routers, we recommend that you use the set ip vrf vrf next-hop command to explicitly indicate the VRF from which the next hop is to be chosen. We also recommend that in Cisco 7600 series routers, the set ip next-hop command be used only for route maps applied on non-VRF interfaces, where the software behavior and the hardware behavior would be similar. |
Examples
The following example shows how packets with a Level 3 length of 3 to 50 bytes are output to the router at IP address 10.14.2.2:
interface serial 0 ip policy route-map thataway ! route-map thataway match length 3 50 set ip next-hop 10.14.2.2
The following example shows how IP address 10.3.3.3 is set as the recursive next-hop address:
route-map map_recurse set ip next-hop recursive 10.3.3.3
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ip default next-hop verify-availability |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination. |
set ip next-hop verify-availability
To configure policy routing to verify the reachability of the next hop of a route map before the router performs policy routing to that next hop, use the setipnext-hopverify-availabilitycommand in route-map configuration mode. To disable this function, use the no form of this command.
Syntax Description
|
next-hop-address |
(Optional) IP address of the next hop to which packets will be forwarded. |
|
sequence |
(Optional) Sequence of next hops. The acceptable range is from 1 to 65535. |
|
track |
(Optional) The tracking method is track. |
|
object |
(Optional) Object number that the tracking subsystem is tracking. The acceptable range is from 1 to 500. |
Command Default
The reachability of the next hop of a route map before a router performs policy routing, is not verified.
Command History
|
Release |
Modification |
|---|---|
|
12.0(3)T |
This command was introduced. |
|
12.3(4)T |
The optional track keyword and next-hop-address, sequence, and object arguments were added. |
|
12.3(14)T |
The SAA feature (uses rtr commands) was replaced by the IP SLAs feature (uses ipsla commands). |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 2.2 |
In Cisco IOS XE Release 2.2 this command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
The setipnext-hopverify-availability command can be used in the following two ways:
- With policy-based routing (PBR) to verify next hop reachability using Cisco Discovery Protocol (CDP).
- With optional arguments to support object tracking using Internet Control Message Protocol (ICMP) ping or an HTTP GET request to verify if a remote device is reachable.
Using CDP Verification
This command is used to verify that the next hop is reachable before the router tries to policy route to it. This command has the following characteristics:
- It causes some performance degradation.
- CDP must be configured on the interface.
- The next hop must be a Cisco device with CDP enabled.
- It is supported in process switching and Cisco Express Forwarding (CEF) policy routing, but is not available in distributed CEF (dCEF) because of the dependency of the CDP neighbor database.
If the router is policy routing packets to the next hop and the next hop is down, the router will try unsuccessfully to use Address Resolution Protocol (ARP) for the next hop (which is down). This behavior will continue indefinitely. To prevent this situation from occurring, use the setipnext-hopverify-availability command to configure the router to verify that the next hop of the route map is a CDP neighbor before routing to that next hop.
This command is optional because some media or encapsulations do not support CDP, or it may not be a Cisco device that is sending traffic to the router.
If this command is set and the next hop is not a CDP neighbor, then the router looks to the subsequent next hop, if there is one. If there is no next hop, the packets are not policy routed.
If this command is not set, the packets are either successfully policy routed or remain forever unrouted.
If you want to selectively verify availability of only some next hops, you can configure different route map entries (under the same route map name) with different criteria (using access list matching or packet size matching), and then use thesetipnext-hopverify-availability command selectively.
Using Object Tracking
With optional arguments to support object tracking, this command allows PBR to make decisions based on the following criteria:
- ICMP ping reachability to a remote device.
- Application running on a remote device (for example, the device responds to an HTTP GET request).
- A route exists in the Routing Information Base (RIB) (for example, policy route only if 10.2.2.0/24 is in the RIB).
- Interface state (for example, packets received on E0 should be policy routed out E1 only if E2 is down).
Object tracking functions in the following manner. PBR will inform the tracking process that it is interested in tracking a certain object. The tracking process will in turn notify PBR when the state of the object changes. This notification is done via registries and is event driven.
The tracking subsystem is responsible for tracking the state of an object. The object can be an IP address that is periodically being pinged by the tracking process. The state of the object (up or down) is stored in a track report data structure. The tracking process will create the tracking object report. Then the exec process that is configuring the route map can query the tracking process to determine if a given object exists. If the object exists, the tracking subsystem can start tracking it and read the initial state of the object. If the object changes state, the tracking process will notify all the clients that are tracking this process that the state of the object has changed. So, the route map structure that PBR is using can be updated to reflect the current state of the object in the track report. This interprocess communication is done by means of registries and the shared track report.
Note | If the CDP and object tracking commands are mixed, the tracked next hops will be tried first. |
Examples
The following configuration sample demonstrates the use of the setipnext-hopverify-availability command to configure the router to verify that the next hop of the route map is a CDP neighbor before routing to that next hop. In this example, the next hop 10.0.0.8 in the route map named "Example1" will be verified as a CDP neighbor before the router tries to policy-route to it.
ip cef interface ethernet0/0/1 ip policy route-map Example1 exit route-map Example1 permit 10 match ip address 1 set ip precedence priority set ip next-hop 10.0.0.8 set ip next-hop verify-availability exit route-map Example1 permit 20 match ip address 101 set interface Ethernet0/0/3 set ip tos max-throughput end
Using Object Tracking
The following configuration sample shows a configuration used to track an object:
! Configure the objects to be tracked. ! Object 123 will be up if the router can ping 10.1.1.1. ! Object 124 will be up if the router can ping 10.2.2.2. ip sla monitor 1 type echo protocol ipicmpecho 10.1.1.1 ip sla monitor schedule 1 start-time now life forever ! ip sla monitor 2 type echo protocol ipicmpecho 10.2.2.2 ip sla monitor schedule 2 start-time now life forever ! track 123 rtr 1 reachability track 124 rtr 2 reachability ! ! Enable policy routing using route-map alpha on Ethernet 0. interface ethernet 0 ip address 10.4.4.254 255.255.255.0 ip policy route-map alpha ! ! 10.1.1.1 is via this interface interface ethernet 1 ip address 10.1.1.254 255.255.255.0 ! 10.2.2.2 is via this interface interface ethernet 2 ip address 10.2.2.254 255.255.255.0 ! ! Configure a route-map to set the next-hop to 10.1.1.1 if object 123 is up. If object 123 ! is down, the next hop will be set to 10.2.2.2 if object 124 is up. If object 124 is also ! down, then policy routing fails and unicast routing will route the packet. route-map alpha set ip next-hop verify-availability 10.1.1.1 10 track 123 set ip next-hop verify-availability 10.2.2.2 20 track 124
set ip vrf
To indicate where to forward packets that pass a match clause of a route map for policy routing when the next hop must be under a specified virtual routing and forwarding (VRF) name, use the setipvrfcommand in route-map configuration mode. To disable this feature, use the no form of this command.
Syntax Description
|
vrf-name |
Name of the VRF. |
||
|
next - hop ip-address |
IP address of the next hop to which packets are forwarded. The next hop must be an adjacent router. |
||
|
next - hop recursive ip-address |
IP address of the recursive next-hop router.
|
Usage Guidelines
The setipvrfcommand allows you to apply policy-based routing to a VRF interface.
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use the ippolicyroute-map interface configuration command, the route-mapglobal configuration command, and matchconfiguration commands to define the conditions for policy-routing packets. The ippolicyroute-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The setcommands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
If the interface associated with the first next hop specified with the setipvrfcommand is down, the optionally specified IP addresses are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
- set TOS
- set DF (Don't Fragment) bit in IP header
- set vrf
- set ip next-hop
- set interface
- set ip default next-hop
- set default interface
Examples
The following example specifies that the next hop must be under the VRF name that has the IP address 10.5.5.5:
set ip vrf myvrf next-hop 10.5.5.5
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for policy routing on an interface. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ip default next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisc IOS software has no explicit route to a destination. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
set level (IP)
To indicate where to import routes, use the setlevel command in route-map configuration mode. To delete an entry, use the no form of this command.
Syntax Description
|
level-1 |
Imports routes into a Level 1 area. |
|
level-2 |
Imports routes into a Level 2 subdomain. |
|
level-1-2 |
Imports routes into Level 1 and Level 2 areas. |
|
nssa-only |
Imports routes only into NSSA areas. |
|
stub-area |
Imports routes into an Open Shortest Path First (OSPF) NSSA area. |
|
backbone |
Imports routes into an OSPF backbone area. |
Command Default
This command is disabled by default. For Intermediate System-to-Intermediate System (IS-IS) destinations, the default value is level-2.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
15.0(1)M |
This command was modified. The nssa-only keyword was added. |
Usage Guidelines
Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the matchcriteria--the conditions under which redistribution is allowed for the current route-mapcommand. The set commands specify the setactions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The noroute-map command deletes the route map.
The set route-map configuration commands specify the redistribution setactions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
The stub-areaandbackbonekeywordshavenoeffectonwhereroutesareimported.
Examples
In the following example, routes will be imported into the Level 1 area:
route-map name set level level-l
Related Commands
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set automatic-tag |
Automatically computes the tag value. |
|
set community |
Sets the BGP communities attribute. |
|
set ip next-hop |
Specifies the address of the next hop. |
|
set level (IP) |
Indicates where to import routes. |
|
set local-preference |
Specifies a preference value for the autonomous system path. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set origin (BGP) |
Sets the BGP origin code. |
|
set tag (IP) |
Sets the value of the destination routing protocol. |
set local-preference
To specify a preference value for the autonomous system paths that pass the route map, use the set local-preference command in route-map configuration mode. To delete the entry from the route map, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The local preference attribute is a number that indicates the relative preference of one route over another when there is more than one route to a destination. A higher preference causes a route to be preferred over a route with a lower preference.
This attribute is exchanged between iBGP peers only. That is, the preference is sent to all routers in the local autonomous system only. This attribute is used to determine local policy
You can change the default preference value with the bgp default local-preference command.
Examples
The following example sets the local preference to 200 for all routes that are included in access list 1:
route-map map-preference match as-path 1 set local-preference 200
Related Commands
|
Command |
Description |
|---|---|
|
bgp default local-preference |
Changes the default local preference value. |
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set automatic-tag |
Automatically computes the tag value. |
|
set community |
Sets the BGP communities attribute. |
|
set ip next-hop |
Specifies the address of the next hop. |
|
set level (IP) |
Indicates where to import routes. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set origin (BGP) |
Sets the BGP origin code. |
|
set tag (IP) |
Sets the value of the destination routing protocol. |
set metric (BGP-OSPF-RIP)
To set the metric value for a routing protocol, use the setmetric command in route-map configuration mode. To return to the default metric value, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
We recommend that you consult your Cisco technical support representative before changing the default value.
Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria --the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions --the particular redistribution actions to perform if the criteria enforced by the match commands are met. The noroute-map command deletes the route map.
The set route-map configuration commands specify the redistribution setactions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the metric value for the routing protocol to 100:
route-map set-metric set metric 100
Related Commands
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set automatic-tag |
Automatically computes the tag value. |
|
set community |
Sets the BGP communities attribute. |
|
set ip next-hop |
Specifies the address of the next hop. |
|
set level (IP) |
Indicates where to import routes. |
|
set local-preference |
Specifies a preference value for the autonomous system path. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set origin (BGP) |
Sets the BGP origin code. |
|
set tag (IP) |
Sets the value of the destination routing protocol. |
set metric-type
To set the metric type for the destination routing protocol, use the setmetric-type command in route-map configuration mode. To return to the default, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the matchcriteria--the conditions under which redistribution is allowed for the current route-mapcommand. The set commands specify the setactions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The noroute-map command deletes the route map.
The set route-map configuration commands specify the redistribution setactions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Note | This command is not supported for redistributing routes into Border Gateway Protocol (BGP). |
Examples
The following example sets the metric type of the destination protocol to OSPF external Type 1:
route-map map-type set metric-type type-1
Related Commands
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set automatic-tag |
Automatically computes the tag value. |
|
set community |
Sets the BGP communities attribute. |
|
set ip next-hop |
Specifies the address of the next hop. |
|
set level (IP) |
Indicates where to import routes. |
|
set local-preference |
Specifies a preference value for the autonomous system path. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set origin (BGP) |
Sets the BGP origin code. |
|
set tag (IP) |
Sets the value of the destination routing protocol. |
|
set weight |
Specifies the BGP weight for the routing table. |
set next-hop
To specify the address of the next hop, use thesetnext-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the matchcriteria--the conditions under which redistribution is allowed for the current route-mapcommand. The set commands specify the setactions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. Thenoroute-map command deletes the route map.
The set route-map configuration commands specify the redistribution setactions to be performed when all the match criteria of the router are met. When all match criteria are met, all set actions are performed.
Examples
In the following example, routes that pass the access list have the next hop set to 172.160.70.24:
route-map map_hop match address 5 set next-hop 172.160.70.24
Related Commands
|
Command |
Description |
|---|---|
|
match as-path |
Matches a BGP autonomous system path access list. |
|
match community |
Matches a BGP community. |
|
match interface (IP) |
Distributes routes that have their next hop out one of the interfaces specified. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match ip next-hop |
Redistributes any routes that have a next hop router address passed by one of the access lists specified. |
|
match ip route-source |
Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. |
|
match metric (IP) |
Redistributes routes with the metric specified. |
|
match route-type (IP) |
Redistributes routes of the specified type. |
|
match tag |
Redistributes routes in the routing table that match the specified tags. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set automatic-tag |
Automatically computes the tag value. |
|
set community |
Sets the BGP communities attribute. |
|
set ip next-hop |
Specifies the address of the next hop. |
|
set level (IP) |
Indicates where to import routes. |
|
set local-preference |
Specifies a preference value for the autonomous system path. |
|
set metric (BGP, OSPF, RIP) |
Sets the metric value for a routing protocol. |
|
set metric-type |
Sets the metric type for the destination routing protocol. |
|
set origin (BGP) |
Sets the BGP origin code. |
|
set tag (IP) |
Sets the value of the destination routing protocol. |
|
set weight |
Specifies the BGP weight for the routing table. |
set tag (IP)
To set a tag value for a route in a route map, use the set tag command in route-map configuration mode. To delete the entry, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
Cisco IOS XE Release 2.1 |
This command was implemented on Cisco ASR 1000 Series Aggregation Services Routers. |
|
15.2(2)S |
This command was modified. This command was integrated into Cisco IOS Release 15.2(2)S and the tag-value-dotted-decimal argument was added to support tag values in dotted-decimal format. |
|
Cisco IOS XE Release 3.6S |
This command was modified. The tag-value-dotted-decimal argument was added to support tag values in dotted-decimal format. |
Usage Guidelines
Use the set tag command to set an administrative tag for a route within a route map. Route tags are 32-bit values attached to routes. You can set tag values as plain decimals or dotted decimals. Route tags are used by route maps to filter routes. The tag value has no impact on routing decisions. It is used to mark or flag routes to prevent routing loops when routes are redistributed between routing protocols.
Examples
The following example shows how to set the tag value of the destination routing protocol to 5:
Device(config)# route-map tag Device(config-route-map)# set tag 5
The following example shows how to set the tag value in the dotted-decimal format:
Device(config)# route-map tag Device(config-route-map)# set tag 10.10.10.10
set ipv6 default next-hop
To specify an IPv6 default next hop to which matching packets are forwarded, use the set ipv6 default next-hop command in route-map configuration mode. To delete the default next hop, use the no form of this command.
Syntax Description
|
vrf vrf-name |
(Optional) Specifies explicitly that the default next-hops are under the specific Virtual Routing and Forwarding (VRF) instance. |
|
global |
(Optional) Specifies explicitly that the default next-hops are under the global routing table. |
|
global-ipv6-address |
IPv6 global address of the next hop to which packets are output. The next-hop router must be an adjacent router. This argument must be in the form documented in RFC 2373, where the address is specified in hexadecimal using 16-bit values between colons. |
Command History
|
Release |
Modification |
|---|---|
|
12.3(7)T |
This command was introduced. |
|
12.2(30)S |
This command was integrated into Cisco IOS Release 12.2(30)S. |
|
12.2(33)SXI4 |
This command was integrated into Cisco IOS Release 12.2(33)SXI4. |
|
Cisco IOS XE Release 3.2S |
This command was modified. It was integrated into Cisco IOS XE Release 3.2S. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the global-ipv6-address argument.
Use the set ipv6 default next-hop command in policy-based routing PBR for IPv6 to specify an IPv6 next-hop address to which a packet is policy routed when the router has no route in the IPv6 routing table or the packets match the default route. The IPv6 next-hop address must be adjacent to the router; that is, reachable by using a directly connected IPv6 route in the IPv6 routing table. The IPv6 next-hop address also must be a global IPv6 address. An IPv6 link-local address cannot be used because the use of an IPv6 link-local address requires interface context.
If the software has no explicit route for the destination in the packet, then the software routes the packet to the next hop as specified by the set ipv6 default next-hop command. The optional specified IPv6 addresses are tried in turn.
Use the ipv6 policy route-map command, the route-map command, and the match and set route-map commands to define the conditions for PBR packets. The ipv6 policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria, which are the conditions under which PBR occurs. The set commands specify the set actions, which are the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
Note | The set ipv6 next-hop and set ipv6 default next-hop are similar commands. The set ipv6 next-hop command is used to policy route packets for which the router has a route in the IPv6 routing table. The set ipv6 default next-hop command is used to policy route packets for which the router does not have a route in the IPv6 routing table (or the packets match the default route). |
Examples
The following example shows how to set the next hop to which the packet is routed:
ipv6 access-list match-dst-1 permit ipv6 any 2001:DB8:4:1::1/64 any route-map pbr-v6-default match ipv6 address match-dst-1 set ipv6 default next-hop 2001:DB8:4:4::1/64
Related Commands
|
Command |
Description |
|---|---|
|
ipv6 local policy route-map |
Identifies a route map to use for local IPv6 PBR. |
|
ipv6 policy route-map |
Configures IPv6 policy-based routing (PBR) on an interface. |
|
match ipv6 address |
Specifies an IPv6 access list to use to match packets for PBR for IPv6. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or to enable policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ipv6 next-hop (PBR) |
Indicates where to output IPv6 packets that pass a match clause of a route map for policy routing. |
|
set ipv6 precedence |
Sets the precedence value in the IPv6 packet header. |
set ipv6 next-hop (PBR)
To indicate where to output IPv6 packets that pass a match clause of a route map for policy-based routing (PBR), use the set ipv6 next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
Syntax Description
|
vrf vrf-name |
(Optional) Specifies explicitly that next-hops are under the specific Virtual Routing and Forwarding (VRF) instance. |
|
global |
(Optional) Specifies explicitly that next-hops are under the global routing table. |
|
global-ipv6-address global-ipv6-address... |
IPv6 global address of the next hop to which packets are output. The next-hop router must be an adjacent router. This argument must be in the form documented in RFC 2373, where the address is specified in hexadecimal using 16-bit values between colons. |
Command History
|
Release |
Modification |
|---|---|
|
12.3(7)T |
This command was introduced. |
|
12.2(30)S |
This command was integrated into Cisco IOS Release 12.2(30)S. |
|
12.2(33)SXI4 |
This command was integrated into Cisco IOS Release 12.2(33)SXI4. |
|
Cisco IOS XE Release 3.2S |
This command was integrated into Cisco IOS XE Release 3.2S. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
The following set commands support inherit-VRF, inter-VRF, and VRF-to-global routing in an IPv6-specific implementation:
The set ipv6 next-hop command is similar to the set ip next-hop command, except that it is IPv6-specific.
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the global-ipv6-address argument. A global IPv6 address must be specified. An IPv6 link-local address cannot be used because the use of an IPv6 link-local address requires interface context.
The global-ipv6-address argument must specify an address that is installed in the IPv6 Routing Information Base (RIB) and is directly connected. A directly connected address is an address that is covered by an IPv6 prefix configured on an interface or an address covered by an IPv6 prefix specified on a directly connected static route.
Examples
The following example shows how to set the next hop to which the packet is routed:
ipv6 access-list match-dst-1 permit ipv6 any 2001:DB8::1 any route-map pbr-v6-default match ipv6 address match-dst-1 set ipv6 next-hop 2001:DB8::F
Related Commands
|
Command |
Description |
|---|---|
|
ipv6 local policy route-map |
Identifies a route map to use for local IPv6 PBR. |
|
ipv6 policy route-map |
Configures IPv6 PBR on an interface. |
|
match ipv6 address |
Specifies an IPv6 access list to use to match packets for PBR for IPv6. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ipv6 default next-hop |
Specifies an IPv6 default next hop to which matching packets are forwarded. |
|
set ipv6 precedence |
Sets the precedence value in the IPv6 packet header. |
set ipv6 precedence
To set the precedence value in the IPv6 packet header, use the set ipv6 precedence command in route-map configuration mode. To remove the precedence value, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(7)T |
This command was introduced. |
|
12.2(30)S |
This command was integrated into Cisco IOS Release 12.2(30)S. |
|
12.2(33)SXI4 |
This command was integrated into Cisco IOS Release 12.2(33)SXI4. |
|
Cisco IOS XE Release 3.2S |
This command was integrated into Cisco IOS XE Release 3.2S. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
The way the network gives priority (or some type of expedited handling) to the marked traffic is through the application of weighted fair queueing (WFQ) or weighted random early detection (WRED) at points downstream in the network. Typically, you would set IPv6 precedence at the edge of the network (or administrative domain) and have queueing act on it thereafter. WFQ can speed up handling for high precedence traffic at congestion points. WRED ensures that high precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of Cisco high-end Internet quality of service (QoS), IPv6 precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network. For example, IPv6 precedence 2 can be given 90 percent of the bandwidth on output links in the network, and IPv6 precedence 6 can be given 5 percent using the distributed weight fair queueing (DWFQ) implementation on the Versatile Interface Processors (VIPs).
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions--the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the IPv6 precedence value to 5 for packets that pass the route map match:
interface serial 0 ipv6 policy route-map texas ! route-map cisco1 match length 68 128 set ipv6 precedence 5
Related Commands
|
Command |
Description |
|---|---|
|
ipv6 local policy route-map |
Identifies a route map to use for local IPv6 PBR. |
|
ipv6 policy route-map |
Configures IPv6 PBR on an interface. |
|
match ipv6 address |
Specifies an IPv6 access list to use to match packets for PBR for IPv6. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
|
set ipv6 default next-hop |
Specifies an IPv6 default next hop to which matching packets will be forwarded. |
|
set ipv6 next-hop |
Indicates where to output IPv6 packets that pass a match clause of a route map for policy routing. |
|
set ipv6 precedence |
Sets the precedence value in the IPv6 packet header. |
show bfd drops
To display the number of dropped packets in Bidirectional Forwarding Detection (BFD), use the show bfd drops command in user EXEC or privileged EXEC mode.
Examples
The following is sample output from the show bfd drops command. The IPV4 and IPV6 columns display single hop session counters for IPv4 and IPv6, respectively. The IPV4-M and IPV6-M columns display multihop session counters for IPv4 and IPv6, respectively.
Router# show bfd drops
BFD Drop Statistics
IPV4 IPV6 IPV4-M IPV6-M MPLS_PW MPLS_TP_LSP
Invalid TTL 0 0 0 0 0 0
BFD Not Configured 0 0 0 0 0 0
No BFD Adjacency 0 0 0 0 0 0
Invalid Header Bits 0 0 0 0 0 0
Invalid Discriminator 0 0 0 0 0 0
Session AdminDown 0 0 0 0 0 0
Authen invalid BFD ver 0 0 0 0 0 0
Authen invalid len 0 0 0 0 0 0
Authen invalid seq 0 0 0 0 0 0
Authen failed 0 0 0 0 0 0
The following table describes the significant fields shown in the display.
| Table 1 | show bfd drops Field Descriptions |
|
Field |
Description |
|---|---|
|
Invalid Header Bits |
Some header bits are invalid or unexpected. |
|
BFD Not Configured |
A packet was received for a session that does not exist. |
|
Invalid Discriminator |
Invalid or unexpected discriminator ID. |
|
Authen invalid BFD ver |
An authenticated packet was received in a BFD session with a version that does not support authentication. |
|
Authen invalid len |
An authenticated packet was received with an invalid authentication length. |
|
Authen invalid seq |
An authenticated packet was received with an invalid authentication sequence. |
show bfd neighbors
To display a line-by-line listing of existing Bidirectional Forwarding Detection (BFD) adjacencies, use the show bfd neighbors command in user EXEC or privileged EXEC mode.
Syntax Description
|
client |
(Optional) Displays neighbors of a specific client. |
|
bgp |
(Optional) Displays a Border Gateway Protocol (BGP) client. |
|
eigrp |
(Optional) Displays an Enhanced Interior Gateway Routing Protocol (EIGRP) client. |
|
isis |
(Optional) Displays an Intermediate System-to-Intermediate System (IS-IS) client. |
|
ospf |
(Optional) Displays an Open Shortest Path First (OSPF) client. |
|
rsvp |
(Optional) Displays a Resource Reservation Protocol (RSVP) client. |
|
te-frr |
(Optional) Displays a traffic engineering (TE) Fast Reroute (FRR) client. |
|
dampened |
(Optional) Displays dampening information about the BFD sessions that are currently dampened. |
|
dampening |
(Optional) Displays dampening information about the BFD sessions that are configured with BFD dampening. |
|
details |
(Optional) Displays all BFD protocol parameters and timers for each neighbor. |
|
interface-type interface-number |
(Optional) Neighbors at the specified interface. |
|
internal |
(Optional) Displays internal BFD information. |
|
ipv4 |
(Optional) Displays an IPv4 neighbor. If the ipv4 keyword is used without the ip-address argument, all IPv4 sessions are displayed. |
|
ip-address |
(Optional) IP address of a neighbor in A.B.C.D format. |
|
ipv6 |
(Optional) Displays an IPv6 neighbor. If the ipv6 keyword is used without the ipv6-address argument, all IPv6 sessions are displayed. |
|
ipv6-address |
(Optional) IPv6 address of a neighbor in X:X:X:X::X format. |
|
vrf vrf-name |
(Optional) Displays entries for the specified VPN routing and forwarding (VRF) instance. |
Command History
|
S Release |
Modification |
|---|---|
|
12.0(31)S |
This command was introduced. |
|
12.2(18)SXE |
This command was integrated into Cisco IOS Release 12.2(18)SXE. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SRC |
This command was modified. The vrf vrf-name keyword-argument pair, the client keyword, and the ip-address argument were added. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was modified. The output was modified to display the "OurAddr" field only with the details keyword. |
|
12.2(33)SRE |
This command was modified. Support for IPv6 was added. |
|
15.1(2)S |
This command was modified. |
|
15.1(3)S |
This command was modified to display information about multihop sessions. |
|
15.2(4)S |
This command was modified. The output of the command was enhanced to include Template and Authentication fields for single-hop sessions. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
|
T Release |
Modification |
|
12.4(4)T |
This command was integrated into Cisco IOS Release 12.4(4)T. |
|
12.4(9)T |
This command was modified. Support for BFD Version 1 and BFD echo mode was added. |
|
15.1(2)T |
This command was modified. Support for IPv6 was added. |
|
15.1(1)SG |
This command was integrated into Cisco IOS Release 15.1(1)SG. |
|
XE Release |
Modification |
|
Cisco IOS XE Release 2.1 |
This command was integrated into Cisco IOS XE Release 2.1. |
|
Cisco IOS XE Release 3.8S |
This command was modified. The dampened and dampening keywords were added. The output of the command was enhanced to include BFD dampening sessions. |
|
15.1(2)SNG |
This command was implemented on Cisco ASR 901 Series Aggregation Services Routers. |
Usage Guidelines
The show bfd neighbors command can be used to help troubleshoot the BFD feature.
The full output for the details keyword is not supported on the Route Processor (RP) for the Cisco 12000 Series Internet Router. If you want to enter the show bfd neighbors command with the details keyword on the Cisco 12000 Series Internet Router, you must enter the command on the line card. Use the attach slot command to establish a CLI session with a line card.
Depending on your releases that support BFD hardware offload, the Tx and Rx intervals on both BFD peers must be configured in multiples of 50 milliseconds. If they are not, output from the show bfd neighbors details command will show the configured intervals, and not the changed ones.
See the "Configuring Synchronous Ethernet on the Cisco 7600 Router with ES+ Line Card" section of the Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) Line Card Configuration Guide for more information about prerequisites and restrictions for hardware offload.
Examples for BFD Dampening
The following is sample output from the show bfd neighbors command when it is entered with the details keyword, which shows BFD protocol parameters, timers for each neighbor, and BFD dampening session details:
Device# show bfd neighbors details
NeighAddr LD/RD RH/RS State Int
10.1.1.2 1/1 1(RH) Up Et0/0
Session state is UP and not using echo function.
OurAddr: 10.1.1.1
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3
Received MinRxInt: 50000, Received Multiplier: 3 Holddown (hits): 150(0), Hello (hits): 50(2223)
Rx Count: 2212, Rx Interval (ms) min/max/avg: 8/68/49 last: 0 ms ago
Tx Count: 2222, Tx Interval (ms) min/max/avg: 40/60/49 last: 20 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Dampening: penalty: 0 - not dampened
flap count: 0 - halflife: 2 sec
reuse threshold: 2000 - suppress threshold: 3000
max suppress time: 6 sec
Registered protocols: CEF Stub
Uptime: 00:01:49
Last packet: Version: 0 - Diagnostic: 0
I Hear You bit: 1 - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 3 - Length: 24
My Discr.: 1 - Your Discr.: 1
Min tx interval: 50000 - Min rx interval: 50000
Min Echo interval: 50000
The following is sample output from the show bfd neighbors command when it is entered with the dampened keyword, which shows dampening information about the BFD sessions that are currently dampened:
Device# show bfd neighbors dampened
IPv4 Sessions
NeighAddr[vrf] LD/RD RH/RS State
10.1.1.2 1/0 Down Down
Dampening: penalty: 4500 - dampened
flap count: 10 - halflife: 2 sec
reuse threshold: 2000 - suppress threshold: 3000
max suppress time: 6 sec
The following is sample output from the show bfd neighbors command when it is entered with the dampening keyword, which shows dampening information about the BFD sessions configured with BFD dampening:
Device# show bfd neighbors dampening
IPv4 Multihop Sessions
NeighAddr[vrf] LD/RD RH/RS State
10.1.1.2 1/0 Down Down
Dampening: penalty: 0 - not dampened
flap count: 0 - halflife: 2 sec
reuse threshold: 2000 - suppress threshold: 3000
max suppress time: 6 sec
The table below describes the significant fields shown in the displays.
| Table 2 | show bfd neighbors Field Descriptions |
|
Field |
Description |
|---|---|
|
NeighAddr |
IPv4 or IPv6 address of the BFD adjacency or neighbor. |
|
LD/RD |
Local discriminator (LD) and remote discriminator (RD) being used for the session. |
|
RH/RS |
Remote Heard (RH) and Remote Seen (RS) indicates the state of the BFD session on a peer device. |
|
State |
State of the BFD session on a given device. |
|
Dampening |
Dampening information about the BFD sessions. |
|
penalty |
Penalty accumulated by the BFD session at the current moment. |
|
flap Count |
Number of times that a BFD session has flapped. |
|
reuse Threshold |
Value of the accumulated penalty (after a session has been dampened) at which the session will be undampened/unsuppressed. |
|
max suppress time |
Maximum time (after a session has become stable) that a session can be in a suppressed/dampened state. |
|
halflife |
Time (in seconds) after which the penalty is reduced by half. |
|
suppress threshold |
Value of the accumulated penalty that triggers the device to dampen a flapping session. |
Examples for Cisco IOS Release 12.0(31)S, 12.2(18)SXE, 12.2(33)SRA, 12.2(33)SB, and 12.4(4)T
The following is sample output from the show bfd neighbors command that shows the status of the adjacency or neighbor:
Device# show bfd neighbors
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int
172.16.10.1 172.16.10.2 1/6 1 260 (3 ) Up Fa0/1
The following is sample output from the show bfd neighbors command when it is entered with the details keyword that shows BFD protocol parameters and timers for each neighbor:
Device# show bfd neighbors details
NeighAddr LD/RD RH/RS State Int
10.1.1.2 1/1 1(RH) Up Et0/0
Session state is UP and not using echo function.
OurAddr: 10.1.1.1
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3
Received MinRxInt: 50000, Received Multiplier: 3 Holddown (hits): 150(0), Hello (hits): 50(2223)
Rx Count: 2212, Rx Interval (ms) min/max/avg: 8/68/49 last: 0 ms ago
Tx Count: 2222, Tx Interval (ms) min/max/avg: 40/60/49 last: 20 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: CEF Stub
Uptime: 00:01:49
Last packet: Version: 0 - Diagnostic: 0
I Hear You bit: 1 - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 3 - Length: 24
My Discr.: 1 - Your Discr.: 1
Min tx interval: 50000 - Min rx interval: 50000
Min Echo interval: 50000
The following is sample output from the show bfd neighbors command when it is entered on a Cisco 12000 Series Internet Router Route Processor (RP) that shows the status of the adjacency or neighbor:
Device# show bfd neighbors
Cleanup timer hits: 0
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int
172.16.10.2 172.16.10.1 2/0 0 0 (0 ) Up Fa6/0
Total Adjs Found: 1
The following is sample output from the show bfd neighbors command when it is entered in a Cisco 12000 Series Internet Router RP that shows the status of the adjacency or neighbor with the details keyword:
Device# show bfd neighbors details
Cleanup timer hits: 0
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int
172.16.10.2 172.16.10.1 2/0 0 0 (0 ) Up Fa6/0
Registered protocols: OSPF
Uptime: never
%% BFD Neighbor statistics are not available on RP. Please execute this command on Line Card.
The following is sample output from the show bfd neighbors command when it is entered on a Cisco 12000 Series Internet Router line card that shows the status of the adjacency or neighbor:
Device# attach 6 Entering Console for 8 Port Fast Ethernet in Slot: 6 Type "exit" to end this session Press RETURN to get started! Device> show bfd neighbors Cleanup timer hits: 0 OurAddr NeighAddr LD/RD RH Holdown(mult) State Int 172.16.10.2 172.16.10.1 2/1 1 848 (5 ) Up Fa6/0 Total Adjs Found: 1
The following is sample output from the show bfd neighbors command when it is entered on a Cisco 12000 Series Internet Router line card that shows the status of the adjacency or neighbor with the details keyword:
Device# attach 6 Entering Console for 8 Port Fast Ethernet in Slot: 6 Type "exit" to end this session Press RETURN to get started! Device> show bfd neighbors details Cleanup timer hits: 0 OurAddr NeighAddr LD/RD RH Holdown(mult) State Int 172.16.10.2 172.16.10.1 2/1 1 892 (5 ) Up Fa6/0 Local Diag: 0, Demand mode: 0, Poll bit: 0 MinTxInt: 50000, MinRxInt: 1000, Multiplier: 3 Received MinRxInt: 200000, Received Multiplier: 5 Holdown (hits): 1000(0), Hello (hits): 200(193745) Rx Count: 327406, Rx Interval (ms) min/max/avg: 152/248/196 last: 108 ms ago Tx Count: 193748, Tx Interval (ms) min/max/avg: 204/440/331 last: 408 ms ago Last packet: Version: 0 - Diagnostic: 0 I Hear You bit: 1 - Demand bit: 0 Poll bit: 0 - Final bit: 0 Multiplier: 5 - Length: 24 My Discr.: 1 - Your Discr.: 2 Min tx interval: 200000 - Min rx interval: 200000 Min Echo interval: 0 Uptime: 17:54:07 SSO Cleanup Timer called: 0 SSO Cleanup Action Taken: 0 Pseudo pre-emptive process count: 7728507 min/max/avg: 8/16/8 last: 12 ms ago IPC Tx Failure Count: 0 IPC Rx Failure Count: 0 Total Adjs Found: 1 Device>
Example for Cisco IOS Release 12.4(9)T and Later Releases
The following is sample output from the show bfd neighbors details command that shows that the BFD neighbor device is running BFD Version 1 and that the BFD session is up and running in echo mode:
Device# show bfd neighbors details OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int 172.16.1.2 172.16.1.1 1/6 Up 0 (3 ) Up Fa0/1 Session state is UP and using echo function with 50 ms interval. Local Diag: 0, Demand mode: 0, Poll bit: 0 MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3 Received MinRxInt: 1000000, Received Multiplier: 3 Holdown (hits): 3000(0), Hello (hits): 1000(337) Rx Count: 341, Rx Interval (ms) min/max/avg: 1/1008/882 last: 364 ms ago Tx Count: 339, Tx Interval (ms) min/max/avg: 1/1016/886 last: 632 ms ago Registered protocols: EIGRP Uptime: 00:05:00 Last packet: Version: 1 - Diagnostic: 0 State bit: Up - Demand bit: 0 Poll bit: 0 - Final bit: 0 Multiplier: 3 - Length: 24 My Discr.: 6 - Your Discr.: 1 Min tx interval: 1000000 - Min rx interval: 1000000 Min Echo interval: 50000
Example for Cisco IOS XE Release 2.1 and Later Releases
The following is sample output from the show bfd neighbors command that displays all IPv6 sessions:
Device# show bfd neighbors ipv6 2001::1
OurAddr NeighAddr LD/RD RH/RS Holddown(mult) State Int
2001:DB8:0:ABCD::1 2001:DB8:0:ABCD::2 2/2 Up 0 (3 ) Up Et0/0
2001:DB8:0:1:FFFF:1234::5 2001:DB8:0:1:FFFF:1234::6 4/4 Up 0 (3 ) Up Et1/0
Examples for Cisco IOS Release 12.2(33)SXI, 12.2(33)SRE, 12.2(33)XNA, and Later Releases
The following is sample output from the show bfd neighbors command:
Device# show bfd neighbors
NeighAddr LD/RD RH/RS State Int
192.0.2.1 4/0 Down Down Et0/0
192.0.2.2 5/0 Down Down Et0/0
192.0.2.3 6/0 Down Down Et0/0
192.0.2.4 7/0 Down Down Et0/0
192.0.2.5 8/0 Down Down Et0/0
192.0.2.6 11/0 0(RH) Fail Et0/0
2001:DB8::1 9/0 Down Down Et0/0
2001:DB8:0:ABCD::1 10/0 Down Down Et0/0
2001:DB8::2 1/0 0(RH) Fail Et0/0
2001:DB8:0:1::1 2/0 Down Down Et0/0
2001:DB8:0:1:FFFF:1234::5 3/0 Down Down Et0/0
The following is sample output from the show bfd neighbors details command:
Device# show bfd neighbors details
NeighAddr LD/RD RH/RS State Int
192.0.2.5 4/0 Down Down Et0/0
OurAddr: 192.0.2.8
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3
Received MinRxInt: 0, Received Multiplier: 0
Holddown (hits): 0(0), Hello (hits): 1000(120)
Rx Count: 0, Rx Interval (ms) min/max/avg: 0/0/0 last: 118672 ms ago
Tx Count: 120, Tx Interval (ms) min/max/avg: 760/1000/885 last: 904 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: Stub
Last packet: Version: 1 - Diagnostic: 0
State bit: AdminDown - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 0 - Length: 0
My Discr.: 0 - Your Discr.: 0
Min tx interval: 0 - Min rx interval: 0
Min Echo interval: 0
NeighAddr LD/RD RH/RS State Int
2001:DB8::1 9/0 Down Down Et0/0
OurAddr: 2001:DB8::2
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3
Received MinRxInt: 0, Received Multiplier: 0
Holddown (hits): 0(0), Hello (hits): 1000(208)
Rx Count: 0, Rx Interval (ms) min/max/avg: 0/0/0 last: 194760 ms ago
Tx Count: 208, Tx Interval (ms) min/max/avg: 760/1000/878 last: 424 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: Stub
Last packet: Version: 1 - Diagnostic: 0
State bit: AdminDown - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 0 - Length: 0
My Discr.: 0 - Your Discr.: 0
Min tx interval: 0 - Min rx interval: 0
Min Echo interval: 0
The table below describes the significant fields shown in the displays.
| Table 3 | show bfd neighbors Field Descriptions |
|
Field |
Description |
||
|---|---|---|---|
|
OurAddr |
IP address of the interface for which the show bfd neighbors details command was entered. |
||
|
NeighAddr |
IPv4 or IPv6 address of the BFD adjacency or neighbor. |
||
|
LD/RD |
Local discriminator (LD) and remote discriminator (RD) being used for the session. |
||
|
RH |
Remote Heard (RH) indicates that the remote BFD neighbor has been heard. |
||
|
Holdown (mult) |
Detect timer multiplier that is used for this session. |
||
|
State |
State of the interface--Up or Down. |
||
|
Int |
Interface type and slot/port. |
||
|
Session state is UP and using echo function with 50 ms interval. |
BFD is up and running in echo mode. The 50-millisecond interval has been adopted from the bfd command.
|
||
|
Rx Count |
Number of BFD control packets that are received from the BFD neighbor. |
||
|
Tx Count |
Number of BFD control packets that are sent by the BFD neighbor. |
||
|
Tx Interval |
The interval, in milliseconds, between sent BFD packets. |
||
|
Registered protocols |
Routing protocols that are registered with BFD. |
||
|
Last packet: Version: |
BFD version detected and run between the BFD neighbors. The system automatically performs BFD version detection, and BFD sessions between neighbors will run in the highest common BFD version. For example, if one BFD neighbor is running BFD Version 0 and the other BFD neighbor is running Version 1, the session will run BFD Version 0.
|
||
|
Diagnostic |
A diagnostic code specifying the local system's reason for the last transition of the session from Up to some other state. State values are as follows: |
||
|
I Hear You bit |
The I Hear You bit is set to 0 if the transmitting system is either not receiving BFD packets from the remote system or is tearing down the BFD session for some reason. During normal operation, the I Hear You bit is set to 1 to signify that the remote system is receiving the BFD packets from the transmitting system. |
||
|
Demand bit |
Demand mode bit. BFD has two modes: asynchronous and demand. If the demand mode is set, the transmitting system prefers to operate in demand mode. The Cisco implementation of BFD supports only asynchronous mode. |
||
|
Poll bit |
Indicates that the transmitting system is requesting verification of connectivity or verification of a parameter change. |
||
|
Final bit |
Indicates that the transmitting system is responding to a received BFD control packet that had a Poll (P) bit set. |
||
|
Multiplier |
Detect time multiplier. The negotiated transmit interval multiplied by the detect time multiplier determines the detection time for the transmitting system in BFD asynchronous mode. The detect time multiplier is similar to the hello multiplier in Intermediate System-to-Intermediate System (IS-IS), which is used to determine the hold timer: (hello interval) * (hello multiplier) = hold timer. If a hello packet is not received within the hold-timer interval, it indicates that a failure has occurred. Similarly, for BFD: (transmit interval) * (detect multiplier) = detect timer. If a BFD control packet is not received from the remote system within the detect-timer interval, it indicates that a failure has occurred. |
||
|
Length |
Length of the BFD control packet, in bytes. |
||
|
My Discr. |
My Discriminator is a unique, nonzero discriminator value generated by the transmitting system used to demultiplex multiple BFD sessions between the same pair of systems. |
||
|
Your Discr. |
Your Discriminator is a discriminator that is received from the corresponding remote system. This field reflects the received value of My Discriminator or is zero if that value is unknown. |
||
|
Min tx interval |
Minimum transmission interval, in microseconds, that the local system wants to use when sending BFD control packets. |
||
|
Min rx interval |
Minimum receipt interval, in microseconds, between received BFD control packets that the system can support. |
||
|
Min Echo interval |
Minimum interval, in microseconds, between received BFD control packets that the system can support. If the value is zero, the transmitting system does not support the receipt of BFD echo packets. The Cisco implementation of BFD for Cisco IOS Releases 12.2(18)SXE and 12.0(31)S does not support the use of echo packets. |
Example for Cisco IOS Release 15.1(2)S with Hardware Offload to Cisco 7600 Series Routers
The following is sample output from the show bfd neighbors details command for BFD sessions offloaded to hardware. The Rx and Tx counts show the number of packets received and transmitted by the BFD session in hardware.
Device# show bfd neighbors details
NeighAddr LD/RD RH/RS State Int
192.0.2.1 298/298 Up Up Te7/1.2
Session state is UP and not using echo function.
Session Host: Hardware - session negotiated with platform adjusted timer values.
Holddown - negotiated: 510000 adjusted: 0
OurAddr: 192.0.2.2
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 170000, MinRxInt: 170000, Multiplier: 3
Received MinRxInt: 160000, Received Multiplier: 3
Holddown (hits): 0(0), Hello (hits): 170(0)
Rx Count: 1256983
Tx Count: 24990
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: OSPF CEF
Uptime: 18:11:31
Last packet: Version: 1 - Diagnostic: 0
State bit: Up - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 3 - Length: 24
My Discr.: 298 - Your Discr.: 298
Min tx interval: 160000 - Min rx interval: 160000
Min Echo interval: 0
Examples for Cisco IOS Release 15.1(2)S with Changes in the Header Line in the Output
The following is sample output from the show bfd neighbors command showing a header type identifying the type of session:
Device# show bfd neighbors
MPLS-TP Sessions
Interface LSP type LD/RD RH/RS State
Tunnel-tp1 Working 1/0 Down Down
Tunnel-tp2 Working 3/0 Down Down
Tunnel-tp1 Protect 2/0 Down Down
IPv4 Sessions
NeighAddr LD/RD RH/RS State Int
192.0.2.1 2/0 Down Down Et2/0
The following is sample output from the show bfd neighbors command for Virtual Circuit Connection Verification (VCCV) sessions:
Device# show bfd neighbors
VCCV Sessions
Peer Addr :VCID LD/RD RH/RS State
198.51.100.1 :100 1/1 Up Up
The following is sample output from the show bfd neighbors command for IPv4 and IPv6 sessions:
Device# show bfd neighbors
IPv4 Sessions
NeighAddr LD/RD RH/RS State Int
192.0.2.1 6/0 Down Down Et1/0
203.0.113.1 7/6 Up Up Et3/0
198.51.100.2 8/7 Up Up Et0/0
IPv6 Sessions
NeighAddr LD/RD RH/RS State Int
2001:DB8::1 1/1 Up Up Et0/0
2001:DB8:0:ABCD::1 2/2 Up Up Et0/0
2001:DB8::2 3/3 Up Up Et0/0
2001:DB8:0:1:FFFF:1234::5 4/4 Up Up Et0/0
2001:DB8:0:1::1 5/5 Up Up Et0/0
The table below describes the significant fields shown in the displays.
Example for Single-Hop Sessions
The following is sample output from the show bfd neighbors command for a single-hop session:
Device# show bfd neighbors
IPv4 Sessions
NeighAddr LD/RD RH/RS State Int
192.0.2.0 1/12 Up Up Et0/0
Session state is UP and using echo function with 300 ms interval.
Session Host: Software
OurAddr: 192.0.2.1
Handle: 12
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3
Received MinRxInt: 1000000, Received Multiplier: 3
Holddown (hits): 0(0), Hello (hits): 1000(62244)
Rx Count: 62284, Rx Interval (ms) min/max/avg: 1/2436/878 last: 239 ms ago
Tx Count: 62247, Tx Interval (ms) min/max/avg: 1/1545/880 last: 246 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: Stub CEF
Template: my-template
Authentication(Type/Keychain): sha-1/my-chain
Uptime: 00:22:06
Last packet: Version: 1 - Diagnostic: 0
State bit: Up - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 3 - Length: 24
My Discr.: 12 - Your Discr.: 1
Min tx interval: 1000000 - Min rx interval: 1000000
Min Echo interval: 300000
The table below describes the significant fields shown in the display.
Example for Multihop Sessions
The following is sample output from the show bfd neighbors command for an IPv4 multihop session. The section headed "Map information:" has information specific to the multihop session.
Device# show bfd neighbors
IPv4 Multihop Sessions
NeighAddr[vrf] LD/RD RH/RS State
192.0.2.21 2/13 Up Up
Session state is UP and not using echo function.
Session Host: Software
OurAddr: 192.0.2.91
Handle: 13
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 750000, MinRxInt: 750000, Multiplier: 3
Received MinRxInt: 750000, Received Multiplier: 15
Holddown (hits): 10772(0), Hello (hits): 750(82985)
Rx Count: 82973, Rx Interval (ms) min/max/avg: 24/1334/659 last: 478 ms ago
Tx Count: 82935, Tx Interval (ms) min/max/avg: 1/1141/660 last: 78 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: Xconnect
Map information:
Destination[vrf]: 192.0.2.11/24
Source[vrf]: 192.0.2.18/24
Template: mh
Authentication(Type/Keychain): md5/qq
last_tx_auth_seq: 5 last_rx_auth_seq 4
Uptime: 15:12:26
Last packet: Version: 1 - Diagnostic: 0
State bit: Up - Demand bit: 0
Poll bit: 0 - Final bit: 0
Multiplier: 15 - Length: 48
My Discr.: 13 - Your Discr.: 2
Min tx interval: 750000 - Min rx interval: 750000
Min Echo interval: 0
The table below describes the significant fields shown in the display.
| Table 6 | show bfd neighbors Field Descriptions for Multihop BFD Sessions |
|
Field |
Description |
|---|---|
|
Destination |
BFD map destination address. |
|
Source |
BFD map source address. |
|
Template |
BFD multihop template name. |
|
Authentication |
Authentication type and key chain. |
|
last_tx_auth_seq |
Last authenticated sequence sent by the peer. |
|
last_rx_auth_seq |
Last authenticated sequence received by the peer. |
show bfd summary
To display summary information for Bidirectional Forwarding Protocol (BFD), use the show bfd summary command in user EXEC or privileged EXEC mode.
Usage Guidelines
Use this command to display summary information about BFD, BFD clients, or BFD sessions.
When a BFD client launches a session with a peer, BFD sends periodic BFD control packets to the peer. Information about the following states of a session are included in the output of this command:
- Up--When another BFD interface acknowledges the BFD control packets, the session moves into an up state.
- Down--The session, and data path, is declared down if a data path failure occurs and BFD does not receive a control packet within the configured amount of time. When a session is down, BFD notifies the BFD client so that the client can perform necessary actions to reroute traffic.
Examples
The following is sample output from the show bfd summary command:
Router# show bfd summary
Session Up Down
Total 1 1 0
The following is sample output from the show bfd summary session command:
Router# show bfd summary session
Protocol Session Up Down
IPV4 1 1 0
Total 1 1 0
The following is sample output from the show bfd summary client command:
Router# show bfd summary client
Client Session Up Down
EIGRP 1 1 0
CEF 1 1 0
Total 2 2 0
The table below describes the significant fields shown in the display.
| Table 7 | show bfd summary Field Descriptions |
|
Field |
Description |
|---|---|
|
Session |
Sum of launched sessions by type or when combined with Total, sum of all launched sessions. |
|
Up |
Number of sessions for which the BFD client acknowleged receipt of control packets. |
|
Down |
Number of sessions for which the BFD client did not receive control packets from a peer. |
|
Total |
Sum of all launched sessions, all Up sessions, or all Down sessions in list. |
|
Protocol |
Routing protocol of interface in a session. |
|
Client |
Type of client in a session. |
show dampening interface
To display a summary of dampened interfaces, use the showdampinginterfacecommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(22)S |
This command was introduced. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(18)SXD |
This command was integrated into Cisco IOS Release 12.2(18)SXD. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Examples
The following is sample output from the showdampinginterfacecommand in privileged EXEC mode:
Router# show dampening interface
3 interfaces are configured with dampening.
No interface is being suppressed.
Features that are using interface dampening:
IP Routing
CLNS Routing
The table below describes the significant fields shown in the sample output of the show dampening interface command.
| Table 8 | show dampening interface Field Descriptions |
|
Field |
Description |
|---|---|
|
... interfaces are configured with dampening. |
Displays the number of interfaces that are configured for event dampening. |
|
No interface is being suppressed. |
Displays the suppression status of the interfaces that are configured for event dampening. |
|
Features that are using interface dampening: |
Displays the routing protocols that are configured to perceived interface dampening. |
show fm ipv6 pbr all
show fm ipv6 pbr interface
show interface dampening
To display dampened interfaces on the local router, use the showinterface dampening command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.0(22)S |
This command was introduced. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. |
|
12.2(18)SXD |
This command was integrated into Cisco IOS Release 12.2(18)SXD. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
Examples
The following is sample output from the showinterfacedampening command:
Router# show interface dampening
Flaps Penalty Supp ReuseTm HalfL ReuseV SuppV MaxSTm MaxP Restart
0 0 FALSE 0 5 1000 2000 20 16000 0
The table below describes the significant fields shown in the display.
| Table 9 | show interface dampening Field Descriptions |
|
Field |
Description |
|---|---|
|
Flaps |
Displays the number of times that an interface has flapped. |
|
Penalty |
Displays the accumulated penalty. |
|
Supp |
Indicates if the interface is dampened. |
|
ReuseTm |
Displays the reuse timer. |
|
HalfL |
Displays the half-life counter. |
|
ReuseV |
Displays the reuse threshold timer. |
|
SuppV |
Displays the suppress threshold. |
|
MaxSTm |
Displays the maximum suppress. |
|
MaxP |
Displays the maximum penalty. |
|
Restart |
Displays the restart timer. |
show ip cef platform
To display entries in the Forwarding Information Base (FIB) or to display a summary of the FIB, use the show ip cef platformcommand in privileged EXEC mode.
Syntax Description
|
ip-prefix |
(Optional) IP address prefix of the entries to display. |
|
mask |
(Optional) Subnet mask of the entries to display. |
|
checksum |
(Optional) Displays FIB entry checksum information. |
|
detail |
(Optional) Displays detailed FIB entry information. |
|
internal checksum |
(Optional) Displays internal data structures. The checksum option includes FIB entry checksum information in the output. |
Examples
The following example shows FIB entry information for IP address prefix 10.4.4.4:
Router# show ip cef 10.4.4.4 platform
10.4.4.4/32
Fib Entry: 0xD6680610 XCM leaf from 0x50805550(RP) 0xA0805550(FP):
load_bal_or_adj[0] 0x0 load_bal_or_adj[1] 0x18 load_bal_or_adj[2] 0x1C
leaf points to an adjacency, index 0x607
ip_mask 0x0 as_number 0x0 precedence_num_loadbal_intf 0xF0 qos_group 0x0
Label object OCE Chain:
Label(0x12, real) Adjacency
c10k_label_data = 0x450467F8
tag_elt_addr = 0x50003038
ipv6_tag_elt_addr = 0x0
tag_index = 0x607
tt_tag_rew = 0x45046800
Tag Rewrite: vcci = 0x9DA, fib_root = 0x0
mac_rewrite_index = 0x395, flags = 0x9
pktswitched = 0 byteswitched = 0
XCM Tag Rewrite: vcci = 0x9DA, fib_root = 0x0
mac_rewrite_index = 0x395, flags = 0x9
mac_index_extension = 0x0
XCM mac rewrite from index 0x395
mtu from 0x53800E54(RP) 0xA3800E54(FP)
frag_flags = 0x0
mtu = 1496
mac length 0x12 encap length 0x16 upd_offset=0x02FF
mac string start from bank4 0x32001CA8(RP)
0x82001CA8(FP)
mac string end from bank9 0x50801CA8(RP)
0xA0801CA8(FP)
Encap String: 0005DC387B180003A011A57881000002884700012000
The following example shows how to display IP Fast ReRoute (FRR) entry information for IP address prefix 10.4.4.4:
Router# show ip cef 10.4.4.4 platform
10.4.4.4/32
=== OCE ===
OCE Type: Fast ReRoute OCE, Number of children: 2
FRR state: : 1
FRR next hw oce ptr: : 0x89b002f0
Backup hw oce ptr: : 0x89b00300
=== OCE ===
OCE Type: Adjacency, Number of children: 0
Adj Type: : IPV4 Adjacency
Encap Len: : 14
L3 MTU: : 1500
Adj Flags: : 0
Fixup Flags: : 0
Interface Name: FastEthernet1/2/7
Encap: : 00 1c b1 d7 8a 44 00 1f 6c 24 30 67 08 00
Next Hop Address: : 0b000002 00000000 00000000 00000000
Next HW OCE Ptr: : 00000000
=== OCE ===
OCE Type: Adjacency, Number of children: 0
Adj Type: : IPV4 Adjacency
Encap Len: : 14
L3 MTU: : 1500
Adj Flags: : 0
Fixup Flags: : 0
Interface Name: FastEthernet1/2/6
Encap: : 00 1c b1 d7 8a 43 00 1f 6c 24 30 66 08 00
Next Hop Address: : 0a000002 00000000 00000000 00000000
Next HW OCE Ptr: : 00000000
show ip static route bfd
To display information about the IPv4 static Bidirectional Forwarding Detection (BFD) configuration from specific configured BFD groups and nongroup entries, use the show ip static route bfd command in user EXEC or privileged EXEC mode.
Usage Guidelines
You can specify a BFD group for a set of BFD-tracked static routes. Nongroup entries are BFD-tracked static routes for which a BFD group is not specified. Use the ip route static bfd command to configure static route BFD neighbors.
Use the show ip static route bfd command to display information about the IPv4 static BFD configuration from specific configured BFD groups and nongroup entries. The group group-name keyword and argument specifies a BFD group and BFD group name.
Examples
The following is sample output from the show ip static route bfd command:
Router# show ip static route bfd group group1
Codes in []: R - Reachable, U - Unreachable, L - Loop, D - Not Tracked
GigabitEthernet1/1 10.1.1.1 [U] [group1, Active]
GigabitEthernet1/2 10.2.2.2 [U] [group1, Passive]
The table below describes the significant fields shown in the display.
| Table 10 | show ip static route bfd Field Descriptions |
|
Field |
Description |
|---|---|
|
GigabitEthernet1/1 |
Interface through which the BFD session is initiated. |
|
10.1.1.1 |
Next hop IP address. |
|
group1 |
BFD group name. |
|
Active |
Active member of the group. |
|
GigabitEthernet1/2 |
Interface through which the BFD session is initiated. |
|
10.2.2.2 |
Next hop IP address. |
|
Passive |
Passive member of the group. |
show ip cache policy
To display the cache entries in the policy route cache, use the showipcachepolicycommand in EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.3 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the showipcachepolicycommand:
Router# show ip cache policy
Total adds 10, total deletes 10
Type Routemap/sequence Age Interface Next Hop
NH george/10 00:04:31 Ethernet0 192.168.1.2
Int george/30 00:01:23 Serial4 192.168.5.129
The table below describes the significant fields shown in the display.
| Table 11 | show ip cache policy Field Descriptions |
|
Field |
Description |
|---|---|
|
Total adds |
Number of times a cache entry was created. |
|
total deletes |
Number of times a cache entry or the entire cache was deleted. |
|
Type |
"NH" indicates the setipnext-hop command. "Int" indicates the setinterfacecommand. |
|
Routemap |
Name of the route map that created the entry; in this example, george. |
|
sequence |
Route map sequence number. |
|
Age |
Age of the cache entry. |
|
Interface |
Output interface type and number. |
|
Next Hop |
IP address of the next hop. |
show ip local policy
To display the route map used for local policy routing, if any, use the showiplocalpolicy command in EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.1 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the showiplocalpolicy command:
Router# show ip local policy
Local policy routing is enabled, using route map equal
route-map equal, permit, sequence 10
Match clauses:
length 150 200
Set clauses:
ip next-hop 10.10.11.254
Policy routing matches: 0 packets, 0 bytes
route-map equal, permit, sequence 20
Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.10.11.14
Policy routing matches: 2 packets, 172 bytes
The table below describes the significant fields shown in the display.
| Table 12 | show ip local policy Field Descriptions |
|
Field |
Description |
|---|---|
|
route-map equal |
The name of the route map is equal. |
|
permit |
The route map contains permit statements. |
|
sequence |
The sequence number of the route map, which determines in what order it is processed among other route maps. |
|
Match clauses: |
Clauses in the route map that must be matched to satisfy the permit or deny action. |
|
Set clauses: |
Set clauses that will be put into place if the match clauses are met. |
|
Policy routing matches: packets |
Number of packets that meet the match clauses. |
|
bytes |
Number of bytes in the packets that meet the match clauses. |
Related Commands
|
Command |
Description |
|---|---|
|
ip policy route-map |
Identifies a route map to use for local policy routing. |
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of route map for policy routing. |
|
set ip default next-hop verify-availability |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
show ip policy
To display the route map used for policy routing, use the showippolicy command in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
11.1 |
This command was introduced. |
|
12.3(7)T |
The display output was modified to include a label for dynamic route maps. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the showippolicy command:
Router# show ip policy
Interface Route map
local equal
Ethernet0/2 equal
Ethernet0/3 AAA-02/06/04-14:01:26.619-1-AppSpec (Dynamic)
The following is sample output from the showroute-map command, which relates to the preceding sample display:
Router# show route-map
route-map equal, permit, sequence 10
Match clauses:
length 150 200
Set clauses:
ip next-hop 10.10.11.254
Policy routing matches: 0 packets, 0 bytes
route-map equal, permit, sequence 20
Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.10.11.14
Policy routing matches: 144 packets, 15190 bytes
The table below describes the significant fields shown in the display.
| Table 13 | show ip policy Field Descriptions |
|
Field |
Description |
|---|---|
|
route-map equal |
The name of the route map is equal. |
|
permit |
The route map contains permit statements. |
|
sequence |
Sequence number of the route map, which determines in what order it is processed among other route maps. |
|
Match clauses |
Clauses in the route map that must be matched to satisfy the permit or deny action. |
|
Set clauses |
Set clauses that will be put into place if the match clauses are met. |
|
Policy routing matches packets |
Number of packets that meet the match clauses. |
|
bytes |
Number of bytes in the packets that meet the match clauses. |
Related Commands
|
Command |
Description |
|---|---|
|
match ip address |
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets. |
|
match length |
Bases policy routing on the Level 3 length of a packet. |
|
route-map (IP) |
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
set default interface |
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. |
|
set interface |
Indicates where to output packets that pass a match clause of route map for policy routing. |
|
set ip default next-hop verify-availability |
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination. |
|
set ip next-hop |
Indicates where to output packets that pass a match clause of a route map for policy routing. |
show ip protocols
To display the parameters and the current state of the active routing protocol process, use the showipprotocols command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(15)T |
This command was modified. Support for the route-hold timer was integrated into the output. |
|
12.2(28)SB |
This command was integrated into Cisco IOS 12.2(28)SB. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
|
15.1(2)S |
This command was modified. The output of the command was modified to display that Routing Information Protocol (RIP) default routes are sent on passive interfaces. |
Usage Guidelines
The information displayed by the showipprotocolscommand is useful in debugging routing operations. Information in the Routing Information Sources field of the showipprotocols output can help you identify a router suspected of delivering bad routing information.
Once you configure the default-informationoriginateon-passive command, the output of the showipprotocols command displays that RIP default routes are sent on passive interfaces.
Examples
The following sample output from the showipprotocols command shows Enhanced Interior Gateway Routing Protocol (EIGRP) process 3:
Router# show ip protocols
*** IP Routing is NSF aware ***
Routing Protocol is "eigrp 3"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
Redistributing: eigrp 3
EIGRP-IPv4 VR(test) Address-Family Protocol for AS(3)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 10.1.1.1
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 3
Total Redist Count: 0
Automatic Summarization: disabled
Maximum path: 4
Routing for Networks:
10.0.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.1.2 90 00:05:10
Distance: internal 90 external 170
The table below describes the significant fields shown in the display.
| Table 14 | show ip protocols Field Descriptions |
|
Field |
Description |
|---|---|
|
Routing Protocol is... |
Name and autonomous system number of the currently running routing protocol. |
|
Outgoing update filter list for all interfaces... |
Indicates whether a filter for outgoing routing updates has been specified with the distribute-listout command. |
|
Incoming update filter list for all interfaces... |
Indicates whether a filter for incoming routing updates has been specified with the distribute-listin command. |
|
Redistributing: |
Indicates whether route redistribution has been enabled with the redistribute command. |
|
EIGRP-IPv4 Protocol for AS(10) |
EIGRP instance and autonomous system number. |
|
Metric weight |
EIGRP metric calculations. |
|
NSF-aware route hold timer... |
Route-hold timer value for a nonstop forwarding (NSF)-aware router. |
|
Router-ID: 10.1.1.1 |
Router ID. |
|
Topology |
Number of entries in the EIGRP topology table. |
|
Active Timer |
EIGRP routing active time limit (in minutes). |
|
Distance |
Internal and external administrative distance. Internal distance is the degree of preference given to EIGRP internal routes. External distance is the degree of preference given to EIGRP external routes. |
|
Maximum path |
Maximum number of parallel routes that the EIGRP can support. |
|
Maximum hopcount |
Maximum hop count (in decimal). |
|
Maximum metric variance |
Metric variance used to find feasible paths for a route. |
|
Automatic Summarization |
Indicates whether route summarization has been enabled with the auto-summary command. |
|
Routing for Networks: |
Networks for which the routing process is currently injecting routes. |
|
Routing Information Sources: |
Lists all the routing sources that the Cisco IOS software is using to build its routing table. The following is displayed for each source: |
IS-IS Example
The following sample output from the showipprotocols command shows an Intermediate System-to-Intermediate System (IS-IS) process:
Router# show ip protocols
Routing Protocol is "isis"
Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: isis
Address Summarization:
None
Routing for Networks:
Serial0
Routing Information Sources:
Distance: (default is 115)
The table below describes the significant fields shown in the display.
| Table 15 | show ip protocols Field Descriptions for an IS-IS Process |
|
Field |
Description |
|---|---|
|
Routing Protocol is "isis" |
Specifies the routing protocol used. |
|
Sending updates every 0 seconds |
Specifies the time (in seconds) between sending updates. |
|
Invalid after 0 seconds |
Specifies the value of the invalid parameter. |
|
hold down 0 |
Specifies the current value of the hold-down parameter. |
|
flushed after 0 |
Specifies the time (in seconds) after which the individual routing information will be thrown out (flushed). |
|
Outgoing update ... |
Specifies whether the outgoing filtering list has been set. |
|
Incoming update ... |
Specifies whether the incoming filtering list has been set. |
|
Redistributing |
Lists the protocol that is being redistributed. |
|
Routing |
Specifies the networks for which the routing process is currently injecting routes. |
|
Routing Information Sources |
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed: |
RIP Example
The following sample output from the showipprotocols command displays RIP processes:
Router# show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 6 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Sending Default route on Passive interfaces
Redistributing: rip
Default version control: send version 2, receive version 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.19.0.0
10.2.0.0
10.3.0.0
Passive Interface(s):
Ethernet0/0
Ethernet0/1
Ethernet0/2
Ethernet0/3
Ethernet1/0
Ethernet1/1
Ethernet1/2
Ethernet1/3
Passive Interface(s):
Serial2/0
Serial2/1
Serial2/2
Serial2/3
Serial3/0
Serial3/1
Serial3/2
Serial3/3
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 120)
The table below describes the significant fields shown in the display.
| Table 16 | show ip protocols Field Descriptions for a RIP Process |
|
Field |
Description |
|---|---|
|
Routing Protocol is "rip" |
Specifies the routing protocol used. |
|
Outgoing update ... |
Specifies whether the outgoing filtering list has been set. |
|
Incoming update ... |
Specifies whether the incoming filtering list has been set. |
|
Sending updates every 30 seconds |
Specifies the time (in seconds) between sending updates. |
|
next due in 6 seconds |
Specifies when the next update is due to be sent. |
|
Invalid after 180 seconds |
Specifies the value of the invalid parameter. |
|
hold down 180 |
Specifies the current value of the hold-down parameter. |
|
flushed after 240 |
Specifies the time (in seconds) after which the individual routing information will be thrown (flushed) out. |
|
Sending Default route on Passive interfaces |
Specifies that RIP update packets are sent only with a default route on passive interfaces. |
|
Redistributing |
Lists the protocol that is being redistributed. |
|
Default version control: |
Specifies the version of RIP packets that are sent and received. |
|
Routing |
Specifies the networks for which the routing process is currently injecting routes. |
|
Routing Information Sources |
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed: |
EIGRP NSF Awareness Verification Example
The following is sample output from the showipprotocols command. The output shows that the router is running EIGRP, is NSF-aware, and that the route-hold timer is set to 240 seconds, which is the default value for the route-hold timer.
Router# show ip protocols
Routing Protocol is "eigrp 101"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 101
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.4.9.0/24
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
The table below describes the significant fields shown in the display.
| Table 17 | show ip protocols Field Descriptions for an EIGRP NSF-Aware Process |
|
Field |
Description |
|---|---|
|
Routing Protocol is "eigrp 101" |
Specifies the routing protocol used. |
|
Outgoing update ... |
Specifies whether the outgoing filtering list has been set. |
|
Incoming update ... |
Specifies whether the incoming filtering list has been set. |
|
Default networks... |
Specifies how these networks will be handled in both incoming and outgoing updates. |
|
EIGRP... |
Specifies the value of the K0-K5 metrics, and the maximum hop count. |
|
Redistributing |
Lists the protocol that is being redistributed. |
|
EIGRP NSF-Aware... |
Displays the route-hold timer value. |
|
Automatic network summarization... |
Specifies that automatic summarization is enabled. |
|
Routing |
Specifies the networks for which the routing process is currently injecting routes. |
|
Routing Information Sources |
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed: |
Related Commands
|
Command |
Description |
|---|---|
|
auto-summary (EIGRP) |
Allows automatic summarization of subnet routes into network-level routes. |
|
default-information originate (RIP) |
Generates a default route into RIP. |
|
distribute-list in (IP) |
Filters networks received in updates. |
|
distribute-list out (IP) |
Suppresses networks from being advertised in updates. |
|
redistribute (IP) |
Redistributes routes from one routing domain into another routing domain. |
show ip route
To display contents of the routing table, use the show ip route command in user EXEC or privileged EXEC mode.
Syntax Description
|
ip-address |
(Optional) IP address for which routing information should be displayed. |
|
repair-paths |
(Optional) Displays the repair paths. |
|
next-hop-override |
(Optional) Displays the Next Hop Resolution Protocol (NHRP) next-hop overrides that are associated with a particular route and the corresponding default next hops. |
|
dhcp |
(Optional) Displays routes added by the Dynamic Host Configuration Protocol (DHCP) server. |
|
mask |
(Optional) Subnet mask. |
|
longer-prefixes |
(Optional) Displays output for longer prefix entries. |
|
protocol |
(Optional) The name of a routing protocol or the keyword connected, mobile, static, or summary. If you specify a routing protocol, use one of the following keywords: bgp, eigrp, hello, isis, odr, ospf, nhrp, or rip. |
|
process-id |
(Optional) Number used to identify a process of the specified protocol. |
|
list |
(Optional) Filters output by an access list name or number. |
|
access-list-number |
(Optional) Access list number. |
|
access-list-name |
(Optional) Access list name. |
|
static |
(Optional) Displays static routes. |
|
download |
(Optional) Displays routes installed using the authentication, authorization, and accounting (AAA) route download function. This keyword is used only when AAA is configured. |
|
update-queue |
(Optional) Displays Routing Information Base (RIB) queue updates. |
Command History
|
Release |
Modification |
|---|---|
|
9.2 |
This command was introduced. |
|
10.0 |
This command was modified. The "D--EIGRP, EX--EIGRP, N1--SPF NSSA external type 1 route" and "N2--OSPF NSSA external type 2 route" codes were included in the command output. |
|
10.3 |
This command was modified. The process-id argument was added. |
|
11.0 |
This command was modified. The longer-prefixes keyword was added. |
|
11.1 |
This command was modified. The "U--per-user static route" code was included in the command output. |
|
11.2 |
This command was modified. The "o--on-demand routing" code was included in the command output. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA, and the update-queue keyword was added. |
|
11.3 |
This command was modified. The command output was enhanced to display the origin of an IP route in Intermediate System-to-Intermediate System (IS-IS) networks. |
|
12.0(1)T |
This command was modified. The "M--mobile" code was included in the command output. |
|
12.0(3)T |
This command was modified. The "P--periodic downloaded static route" code was included in the command output. |
|
12.0(4)T |
This command was modified. The "ia--IS-IS" code was included in the command output. |
|
12.2(2)T |
This command was modified. The command output was enhanced to display information on multipaths to the specified network. |
|
12.2(13)T |
This command was modified. The egp and igrp arguments were removed because the Exterior Gateway Protocol (EGP) and the Interior Gateway Routing Protocol (IGRP) were no longer available in Cisco software. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(14)SX |
This command was integrated into Cisco IOS Release 12.2(14)SX. |
|
12.3(2)T |
This command was modified. The command output was enhanced to display route tag information. |
|
12.3(8)T |
This command was modified. The command output was enhanced to display static routes using DHCP. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRE |
This command was modified. The dhcp and repair-paths keywords were added. |
|
12.2(33)XNE |
This command was integrated into Cisco IOS Release 12.2(33)XNE. |
|
Cisco IOS XE Release 2.5 |
This command was integrated into Cisco IOS XE Release 2.5. The next-hop-override and nhrp keywords were added. |
|
15.2(2)S |
This command was modified. The command output was enhanced to display route tag values in dotted decimal format. |
|
Cisco IOS XE Release 3.6S |
This command was modified. The command output was enhanced to display route tag values in dotted decimal format. |
|
15.2(4)S |
This command was implemented on the Cisco 7200 series router. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
The following is sample output from the show ip route command when an IP address is not specified:
Device# show ip route
Codes: R - RIP derived, O - OSPF derived,
C - connected, S - static, B - BGP derived,
* - candidate default route, IA - OSPF inter area route,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is 10.119.254.240 to network 10.140.0.0
O E2 10.110.0.0 [160/5] via 10.119.254.6, 0:01:00, Ethernet2
E 10.67.10.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
O E2 10.68.132.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2
O E2 10.130.0.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2
E 10.128.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.129.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2
E 10.65.129.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.10.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.75.139.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.16.208.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.84.148.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.31.223.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.44.236.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.141.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2
E 10.140.0.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
The following sample output from the show ip route command includes routes learned from IS-IS Level 2:
Device# show ip route
Codes: R - RIP derived, O - OSPF derived,
C - connected, S - static, B - BGP derived,
* - candidate default route, IA - OSPF inter area route,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is not set
10.89.0.0 is subnetted (mask is 255.255.255.0), 3 subnets
C 10.89.64.0 255.255.255.0 is possibly down,
routing via 10.0.0.0, Ethernet0
i L2 10.89.67.0 [115/20] via 10.89.64.240, 0:00:12, Ethernet0
i L2 10.89.66.0 [115/20] via 10.89.64.240, 0:00:12, Ethernet0
The following is sample output from the show ip route ip-address mask longer-prefixes command. When this keyword is included, the address-mask pair becomes the prefix, and any address that matches that prefix is displayed. Therefore, multiple addresses are displayed. The logical AND operation is performed on the source address 10.0.0.0 and the mask 10.0.0.0, resulting in 10.0.0.0. Each destination in the routing table is also logically ANDed with the mask and compared with 10.0.0.0. Any destinations that fall into that range are displayed in the output.
Device# show ip route 10.0.0.0 10.0.0.0 longer-prefixes
Codes: R - RIP derived, O - OSPF derived,
C - connected, S - static, B - BGP derived,
* - candidate default route, IA - OSPF inter area route,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is not set
S 10.134.0.0 is directly connected, Ethernet0
S 10.10.0.0 is directly connected, Ethernet0
S 10.129.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
S 10.49.246.0 is directly connected, Ethernet0
S 10.160.97.0 is directly connected, Ethernet0
S 10.153.88.0 is directly connected, Ethernet0
S 10.76.141.0 is directly connected, Ethernet0
S 10.75.138.0 is directly connected, Ethernet0
S 10.44.237.0 is directly connected, Ethernet0
S 10.31.222.0 is directly connected, Ethernet0
S 10.16.209.0 is directly connected, Ethernet0
S 10.145.0.0 is directly connected, Ethernet0
S 10.141.0.0 is directly connected, Ethernet0
S 10.138.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
10.19.0.0 255.255.255.0 is subnetted, 1 subnets
C 10.19.64.0 is directly connected, Ethernet0
10.69.0.0 is variably subnetted, 2 subnets, 2 masks
C 10.69.232.32 255.255.255.240 is directly connected, Ethernet0
S 10.69.0.0 255.255.0.0 is directly connected, Ethernet0
The following sample outputs from the show ip route command display all downloaded static routes. A "p" indicates that these routes were installed using the AAA route download function.
Device# show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR, P - periodic downloaded static route T - traffic engineered route Gateway of last resort is 172.16.17.1 to network 10.0.0.0 172.31.0.0/32 is subnetted, 1 subnets P 172.31.229.41 is directly connected, Dialer1 10.0.0.0/8 is subnetted, 3 subnets P 10.1.1.0 [200/0] via 172.31.229.41, Dialer1 P 10.1.3.0 [200/0] via 172.31.229.41, Dialer1 P 10.1.2.0 [200/0] via 172.31.229.41, Dialer1 Device# show ip route static 172.16.4.0/8 is variably subnetted, 2 subnets, 2 masks P 172.16.1.1/32 is directly connected, BRI0 P 172.16.4.0/8 [1/0] via 10.1.1.1, BRI0 S 172.31.0.0/16 [1/0] via 172.16.114.65, Ethernet0 S 10.0.0.0/8 is directly connected, BRI0 P 10.0.0.0/8 is directly connected, BRI0 172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks S 172.16.114.201/32 is directly connected, BRI0 S 172.16.114.205/32 is directly connected, BRI0 S 172.16.114.174/32 is directly connected, BRI0 S 172.16.114.12/32 is directly connected, BRI0 P 10.0.0.0/8 is directly connected, BRI0 P 10.1.0.0/16 is directly connected, BRI0 P 10.2.2.0/24 is directly connected, BRI0 S* 0.0.0.0/0 [1/0] via 172.16.114.65, Ethernet0 S 172.16.0.0/16 [1/0] via 172.16.114.65, Ethernet0
The following sample output from the show ip route static download command displays all active and inactive routes installed using the AAA route download function:
Device# show ip route static download
Connectivity: A - Active, I - Inactive
A 10.10.0.0 255.0.0.0 BRI0
A 10.11.0.0 255.0.0.0 BRI0
A 10.12.0.0 255.0.0.0 BRI0
A 10.13.0.0 255.0.0.0 BRI0
I 10.20.0.0 255.0.0.0 172.21.1.1
I 10.22.0.0 255.0.0.0 Serial0
I 10.30.0.0 255.0.0.0 Serial0
I 10.31.0.0 255.0.0.0 Serial1
I 10.32.0.0 255.0.0.0 Serial1
A 10.34.0.0 255.0.0.0 192.168.1.1
A 10.36.1.1 255.255.255.255 BRI0 200 name remote1
I 10.38.1.9 255.255.255.0 192.168.69.1
The following sample outputs from the show ip route nhrp command display shortcut switching on the tunnel interface:
Device# show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP Gateway of last resort is not set 10.0.0.0/16 is variably subnetted, 3 subnets, 2 masks C 10.1.1.0/24 is directly connected, Tunnel0 C 172.16.22.0 is directly connected, Ethernet1/0 H 172.16.99.0 [250/1] via 10.1.1.99, 00:11:43, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets C 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip route nhrp H 172.16.99.0 [250/1] via 10.1.1.99, 00:11:43, Tunnel0
The following are sample outputs from the show ip route command when the next-hop-override keyword is used. When this keyword is included, the NHRP next-hop overrides that are associated with a particular route and the corresponding default next hops are displayed.
=============================================================== 1) Initial configuration =============================================================== Device# show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip route next-hop-override Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip cef Prefix Next Hop Interface . . . 10.2.1.255/32 receive Loopback1 10.10.10.0/24 attached Tunnel0 <<<<<<<< 10.11.11.0/24 attached Ethernet0/0 172.16.0.0/12 drop . . . =============================================================== 2) Add a next-hop override address = 10.10.10.0 mask = 255.255.255.0 gateway = 10.1.1.1 interface = Tunnel0 =============================================================== Device# show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip route next-hop-override Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 [NHO][1/0] via 10.1.1.1, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip cef Prefix Next Hop Interface . . . 10.2.1.255/32 receive Loopback110.10.10.0/24 10.10.10.0/24 10.1.1.1 Tunnel0 10.11.11.0/24 attached Ethernet0/0 10.12.0.0/16 drop . . . =============================================================== 3) Delete a next-hop override address = 10.10.10.0 mask = 255.255.255.0 gateway = 10.11.1.1 interface = Tunnel0 =============================================================== Device# show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip route next-hop-override Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route Gateway of last resort is not set 10.2.0.0/16 is variably subnetted, 2 subnets, 2 masks C 10.2.1.0/24 is directly connected, Loopback1 L 10.2.1.1/32 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 1 subnets S 10.10.10.0 is directly connected, Tunnel0 10.11.0.0/24 is subnetted, 1 subnets S 10.11.11.0 is directly connected, Ethernet0/0 Device# show ip cef Prefix Next Hop Interface . . . 10.2.1.255/32 receive Loopback110.10.10.0/24 10.10.10.0/24 attached Tunnel0 10.11.11.0/24 attached Ethernet0/0 10.120.0.0/16 drop . . .
The table below describes the significant fields shown in the displays:
| Table 18 | show ip route Field Descriptions |
|
Field |
Description |
|---|---|
|
Codes (Protocol) |
Indicates the protocol that derived the route. It can be one of the following values:
|
|
Codes (Type) |
Type of route. It can be one of the following values:
|
|
10.110.0.0 |
Indicates the address of the remote network. |
|
[160/5] |
The first number in brackets is the administrative distance of the information source; the second number is the metric for the route. |
|
via 10.119.254.6 |
Specifies the address of the next device to the remote network. |
|
0:01:00 |
Specifies the last time the route was updated (in hours:minutes:seconds). |
|
Ethernet2 |
Specifies the interface through which the specified network can be reached. |
The following is sample output from the show ip route command when an IP address is specified:
Device# show ip route 10.0.0.1
Routing entry for 10.0.0.1/32
Known via "isis", distance 115, metric 20, type level-1
Redistributing via isis
Last update from 10.191.255.251 on Fddi1/0, 00:00:13 ago
Routing Descriptor Blocks:
* 10.22.22.2, from 10.191.255.247, via Serial2/3
Route metric is 20, traffic share count is 1
10.191.255.251, from 10.191.255.247, via Fddi1/0
Route metric is 20, traffic share count is 1
When an IS-IS router advertises its link-state information, the router includes one of its IP addresses to be used as the originator IP address. When other routers calculate IP routes, they store the originator IP address with each route in the routing table.
The preceding example shows the output from the show ip route command for an IP route generated by IS-IS. Each path that is shown under the Routing Descriptor Blocks report displays two IP addresses. The first address (10.22.22.2) is the next-hop address. The second is the originator IP address from the advertising IS-IS router. This address helps you determine the origin of a particular IP route in your network. In the preceding example, the route to 10.0.0.1/32 was originated by a device with IP address 10.191.255.247.
The table below describes the significant fields shown in the display.
| Table 19 | show ip route with IP Address Field Descriptions |
|
Field |
Description |
|---|---|
|
Routing entry for 10.0.0.1/32 |
Network number and mask. |
|
Known via... |
Indicates how the route was derived. |
|
Redistributing via... |
Indicates the redistribution protocol. |
|
Last update from 10.191.255.251 |
Indicates the IP address of the router that is the next hop to the remote network and the interface on which the last update arrived. |
|
Routing Descriptor Blocks |
Displays the next-hop IP address followed by the information source. |
|
Route metric |
This value is the best metric for this Routing Descriptor Block. |
|
traffic share count |
Indicates the number of packets transmitted over various routes. |
The following sample output from the show ip route command displays the tag applied to the route 10.22.0.0/16. You must specify an IP prefix to see the tag value. The fields in the display are self-explanatory.
Device# show ip route 10.22.0.0
Routing entry for 10.22.0.0/16
Known via "isis", distance 115, metric 12
Tag 120, type level-1
Redistributing via isis
Last update from 172.19.170.12 on Ethernet2, 01:29:13 ago
Routing Descriptor Blocks:
* 172.19.170.12, from 10.3.3.3, via Ethernet2
Route metric is 12, traffic share count is 1
Route tag 120
The following example shows that IP route 10.8.8.0 is directly connected to the Internet and is the next-hop (option 3) default gateway. Routes 10.1.1.1 [1/0], 10.3.2.1 [24/0], and 172.16.2.2 [1/0] are static, and route 10.0.0.0/0 is a default route candidate. The fields in the display are self-explanatory.
Device# show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 10.0.19.14 to network 0.0.0.0
10.0.0.0/24 is subnetted, 1 subnets
C 10.8.8.0 is directly connected, Ethernet1
10.0.0.0/32 is subnetted, 1 subnets
S 10.1.1.1 [1/0] via 10.8.8.1
10.0.0.0/32 is subnetted, 1 subnets
S 10.3.2.1 [24/0] via 10.8.8.1
172.16.0.0/32 is subnetted, 1 subnets
S 172.16.2.2 [1/0] via 10.8.8.1
10.0.0.0/28 is subnetted, 1 subnets
C 10.0.19.0 is directly connected, Ethernet0
10.0.0.0/24 is subnetted, 1 subnets
C 10.15.15.0 is directly connected, Loopback0
S* 10.0.0.0/0 [1/0] via 10.0.19.14
The following sample output from the show ip route repair-paths command shows repair paths marked with the tag [RPR]. The fields in the display are self-explanatory:
Device# show ip route repair-paths Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP + - replicated route, % - next hop override Gateway of last resort is not set 10.0.0.0/32 is subnetted, 3 subnets C 10.1.1.1 is directly connected, Loopback0 B 10.2.2.2 [200/0] via 172.16.1.2, 00:31:07 [RPR][200/0] via 192.168.1.2, 00:31:07 B 10.9.9.9 [20/0] via 192.168.1.2, 00:29:45 [RPR][20/0] via 192.168.3.2, 00:29:45 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks C 172.16.1.0/24 is directly connected, Ethernet0/0 L 172.16.1.1/32 is directly connected, Ethernet0/0 192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks C 192.168.1.0/24 is directly connected, Serial2/0 L 192.168.1.1/32 is directly connected, Serial2/0 B 192.168.3.0/24 [200/0] via 172.16.1.2, 00:31:07 [RPR][200/0] via 192.168.1.2, 00:31:07 B 192.168.9.0/24 [20/0] via 192.168.1.2, 00:29:45 [RPR][20/0] via 192.168.3.2, 00:29:45 B 192.168.13.0/24 [20/0] via 192.168.1.2, 00:29:45 [RPR][20/0] via 192.168.3.2, 00:29:45 Device# show ip route repair-paths 10.9.9.9 >Routing entry for 10.9.9.9/32 > Known via "bgp 100", distance 20, metric 0 > Tag 10, type external > Last update from 192.168.1.2 00:44:52 ago > Routing Descriptor Blocks: > * 192.168.1.2, from 192.168.1.2, 00:44:52 ago, recursive-via-conn > Route metric is 0, traffic share count is 1 > AS Hops 2 > Route tag 10 > MPLS label: none > [RPR]192.168.3.2, from 172.16.1.2, 00:44:52 ago > Route metric is 0, traffic share count is 1 > AS Hops 2 > Route tag 10 > MPLS label: none
show ip route loops
To display all routes currently in the routing information base (RIB) that are part of a loop, use the showiprouteloops command in user EXEC or privileged EXEC mode.
Usage Guidelines
Use the showiprouteloops command to display information about all routes currently in the RIB that are part of a loop.
For example, the following configuration introduces a loop in the RIB that cannot be safely resolved without the risk of oscillation.
ip route 0.0.0.0 0.0.0.0 192.168.5.6 ip route 192.168.0.0 255.255.0.0 192.168.1.2
Note | The above configuration is not useful. The same forwarding behavior can be achieved if you configure iproute0.0.0.00.0.0.0192.168.1.2. |
When the connected route for 192.168.1.2/30 is removed, loop is introduced and the following log message is displayed:
*Mar 31 15:50:16.307: %IPRT-3-RIB_LOOP: Resolution loop formed by routes in RIB
You can use the showiprouteloops command to view information about this loop.
show ip route profile
Command History
|
Release |
Modification |
|---|---|
|
12.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use this command in combination with the iprouteprofile global configuration command to validate the routing table change statistics.
Examples
The following example shows the frequency of routing table changes in a 5-second sampling interval. In this example, the Prefix add change occurred 22 times in one interval and 24 times in another interval. The output represents this with a Fwd-path change value of 2 and a Prefix add value of 2:
Router# show ip route profile
--------------------------------------------------------------------
Change/ Fwd-path Prefix Nexthop Pathcount Prefix
interval change add Change Change refresh
--------------------------------------------------------------------
0 87 87 89 89 89
1 0 0 0 0 0
2 0 0 0 0 0
3 0 0 0 0 0
4 0 0 0 0 0
5 0 0 0 0 0
10 0 0 0 0 0
15 0 0 0 0 0
20 2 2 0 0 0
25 0 0 0 0 0
The table below describes the significant fields shown in the display.
| Table 20 | show ip route profile Field Descriptions |
|
Field |
Description |
|---|---|
|
Change/interval |
Represents the frequency buckets. A Change/interval of 20 represents the bucket that is incremented when a particular event occurs 20 times in a sampling interval. It is very common to see high counters for the Change/interval bucket for 0. This counter represents the number of sampling intervals in which there were no changes to the routing table. Route removals are not counted in the statistics, only route additions. |
|
Fwd-path change |
Number of changes in the forwarding path. This value represents the accumulation of Prefix add, Nexthop change, and Pathcount change. |
|
Prefix add |
A new prefix was added to the routing table. |
|
Nexthop change |
A prefix is not added or removed, but the next hop changes. This statistic is only seen with recursive routes that are installed in the routing table. |
|
Pathcount change |
The number of paths in the routing table has changed. This change is the result of an increase in the number of paths for an Interior Gateway Protocol (IGP). |
|
Prefix refresh |
Indicates standard routing table maintenance. The forwarding behavior was not changed. |
show ip route summary
To display the current state of the routing table, use the showiproutesummary command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.3(2)T |
The number of multipaths supported by the routing table was added to the output. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from theshowiproutesummary command:
Router# show ip route summary
IP routing table name is Default-IP-Routing-Table(0)
IP routing table maximum-paths is 16
Route Source Networks Subnets Overhead Memory (bytes)
connected 0 3 126 360
static 1 2 126 360
eigrp 109 747 12 31878 91080
internal 3 360
Total 751 17 32130 92160
Table 1 describes the significant fields shown in the display.
| Table 21 | show ip route summary Field Descriptions |
|
Field |
Description |
|---|---|
|
IP routing table name is... |
Displays routing table type and table ID. |
|
IP routing table maximum-paths is... |
Number of parallel routes supported by this routing table. |
|
Route Source |
Routing protocol name, or the connected,static, or internalkeyword. "Internal" indicates those routes that are in the routing table that are not owned by any routing protocol. |
|
Networks |
Number of prefixes that are present in the routing table for each route source. |
|
Subnets |
Number of subnets that are present in the routing table for each route source, including host routes. |
|
Overhead |
Any additional memory involved in allocating the routes for the particular route source other than the memory specified in the Memory field. |
|
Memory |
Number of bytes allocated to maintain all the routes for the particular route source. |
show ip route supernets-only
To display information about supernets, use the showiproutesupernets-only command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the showiproutesupernets-only command. This display shows supernets only; it does not show subnets.
Router# show ip route supernets-only
Codes: R - RIP derived, O - OSPF derived
C - connected, S - static, B - BGP derived
i - IS-IS derived, D - EIGRP derived
* - candidate default route, IA - OSPF inter area route
E1 - OSPF external type 1 route, E2 - OSPF external type 2 route
L1 - IS-IS level-1 route, L2 - IS-IS level-2 route
EX - EIGRP external route
Gateway of last resort is not set
B 172.16.0.0 (mask is 255.255.0.0) [20/0] via 172.16.72.30, 0:00:50
B 192.0.0.0 (mask is 255.0.0.0) [20/0] via 172.16.72.24, 0:02:50
The table below describes the significant fields shown in the display.
| Table 22 | show ip route supernets-only Field Descriptions |
|
Field |
Description |
|---|---|
|
B |
Border Gateway Protocol (BGP) derived, as shown in list of codes. |
|
172.16.0.0 (mask is 255.255.0.0) |
Supernet IP address. |
|
[20/0] |
Administrative distance (external/internal). |
|
via 172.16.72.30 |
Next hop IP address. |
|
0:00:50 |
Age of the route (how long ago the update was received). |
show ip route tag
To display route tag entries for IPv4 routes, use the show ip route tag command in user EXEC or privileged EXEC mode.
Usage Guidelines
Route tags are 32-bit values attached to routes. They are used to filter routes. You can display route tag values as either plain decimals or dotted decimals.
Examples
The following sample output from the show ip route tag command displays detailed information about route tag entries. The route tag entries in this output are displayed in dotted-decimal format.
Device# show ip route tag 1.1.1.1
Routing entry for 192.168.10.0/24
Known via "eigrp 2", distance 170, metric 1536000
Tag 1.1.1.1, type external
Redistributing via eigrp 2
Last update from 10.0.0.1 on Ethernet0/1, 00:00:20 ago
Routing Descriptor Blocks:
* 10.0.0.1, from 10.0.0.1, 00:00:20 ago, via Ethernet0/1
Route metric is 1536000, traffic share count is 1
Total delay is 2000 microseconds, minimum bandwidth is 10000 Kbit
Reliability 100/255, minimum MTU 1500 bytes
Loading 100/255, Hops 1
Route tag 1.1.1.1
The following sample output from the show ip route tag command displays detailed information about route tag entries with the wild card mask. The route tag entries in this output are displayed in dotted-decimal format.
Device# show ip route tag 10.10.10.0 0.0.0.7
Routing entry for 10.1.10.4/30
Known via "eigrp 7", distance 170, metric 2560512256
Tag 10.10.10.3, type external
Redistributing via eigrp 7, ospf 10
Last update from 172.16.2.9 on Serial2/1, 00:02:28 ago
Routing Descriptor Blocks:
* 172.16.2.9, from 172.16.2.9, 00:02:28 ago, via Serial2/1
Route metric is 2560512256, traffic share count is 1
Total delay is 20010 microseconds, minimum bandwidth is 1 Kbit
Reliability 1/255, minimum MTU 1 bytes
Loading 1/255, Hops 1
Route tag 10.10.10.3
Routing entry for 192.168.1.0/24
Known via "eigrp 7", distance 170, metric 2560512256
Tag 10.10.10.2, type external
Redistributing via eigrp 7, ospf 10
Advertised by ospf 10 metric 100 route-map to_ospf
Last update from 172.16.2.9 on Serial2/1, 00:01:59 ago
Routing Descriptor Blocks:
* 172.16.2.9, from 172.16.2.9, 00:01:59 ago, via Serial2/1
Route metric is 2560512256, traffic share count is 1
Total delay is 20010 microseconds, minimum bandwidth is 1 Kbit
Reliability 1/255, minimum MTU 1 bytes
Loading 1/255, Hops 1
Route tag 10.10.10.2
Routing entry for 192.168.2.0/24
Known via "eigrp 7", distance 170, metric 2560512256
Tag 10.10.10.2, type external
Redistributing via eigrp 7, ospf 10
Advertised by ospf 10 metric 100 route-map to_ospf
Last update from 172.16.2.9 on Serial2/1, 00:01:59 ago
Routing Descriptor Blocks:
* 172.16.2.9, from 172.16.2.9, 00:01:59 ago, via Serial2/1
Route metric is 2560512256, traffic share count is 1
Total delay is 20010 microseconds, minimum bandwidth is 1 Kbit
Reliability 1/255, minimum MTU 1 bytes
Loading 1/255, Hops 1
Route tag 10.10.10.2
The table below describes the significant fields shown in the displays.
| Table 23 | show ip route tag Field Descriptions |
|
Field |
Description |
|---|---|
|
Known via |
Indicates how the route was derived. |
|
Redistributing via |
Indicates the redistribution protocol. |
|
Last update from |
Indicates the interface on which the last update arrived. |
|
Routing Descriptor Blocks |
Displays the next-hop IP address followed by the information source. |
|
Route metric |
Displays the best metric for this routing descriptor block. |
|
Total Delay |
Displays the total delay of the route. |
|
Reliability |
Indicates the reliability of the link. |
|
Loading |
Displays the total load on the link. |
|
Route tag |
Displays the tag of the prefix or network. |
show ip route track-table
To display information about the IP route track table, use theshowiproutetrack-tablecommand in privileged EXEC mode.
show ip route vrf
To display the IP routing table associated with a specific VPN routing and forwarding (VRF) instance, use the show ip route vrf command in user EXEC or privileged EXEC mode.
Syntax Description
|
vrf-name |
Name of the VRF. |
|
connected |
(Optional) Displays all connected routes in a VRF. |
|
protocol |
(Optional) Routing protocol. To specify a routing protocol, use one of the following keywords: bgp, egp, eigrp, hello, igrp, isis, ospf, or rip. |
|
as-number |
(Optional) Autonomous system number. |
|
list number |
(Optional) Specifies the IP access list to be displayed. |
|
profile |
(Optional) Displays the IP routing table profile. |
|
static |
(Optional) Displays static routes. |
|
summary |
(Optional) Displays a summary of routes. |
|
ip-prefix |
(Optional) Network for which routing information is displayed. |
|
ip-address |
(Optional) Address for which routing information is displayed. |
|
mask |
(Optional) Network mask. |
|
longer-prefixes |
(Optional) Displays longer prefix entries. |
|
repair-paths |
(Optional) Displays repair paths. |
|
dhcp |
(Optional) Displays routes added by the DHCP server. |
|
supernets-only |
(Optional) Displays only supernet entries. |
|
tag |
(Optional) Displays information about route tags in the VRF table. |
|
tag-value |
(Optional) Route tag values as a plain decimals. |
|
tag-value-dotted-decimal |
(Optional) Route tag values as a dotted decimals. |
|
mask |
(Optional) Route tag wildcard mask. |
Command History
|
Release |
Modification |
|---|---|
|
12.0(5)T |
This command was introduced. |
|
12.2(2)T |
This command was modified. The ip-prefix argument was added. The command output was enhanced to display information on multipaths to the specified network. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.0(22)S |
This command was modified. Support for Enhanced Interior Gateway Routing Protocol (EIGRP) VRFs was added. |
|
12.2(15)T |
This command was modified. Support for EIGRP VRFs was added. |
|
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. The output was enhanced to display remote label information and corresponding Multiprotocol Label Switching (MPLS) flags for prefixes that have remote labels stored in the Routing Information Base (RIB). |
|
12.2(33)SRE |
This command was modified. The repair-paths, dhcp, and supernets-only keywords were added. Support for the Border Gateway Protocol (BGP) Best External and BGP Additional Path features was added. |
|
12.2(33)XNE |
This command was integrated into Cisco IOS Release 12.2(33)XNE. |
|
Cisco IOS XE Release 2.5 |
This command was integrated into Cisco IOS XE Release 2.5. |
|
15.2(2)S |
This command was modified. The tag keyword and tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain or dotted decimals in the command output. |
|
Cisco IOS XE Release 3.6S |
This command was modified. The tag keyword and tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain or dotted decimals in the command output. |
|
15.2(4)S |
This command was implemented on the Cisco 7200 series router. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Examples
The following sample output displays the IP routing table associated with the VRF named vrf1:
Device# show ip route vrf vrf1
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
I - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route
Gateway of last resort is not set
B 10.0.0.0/8 [200/0] via 10.13.13.13, 00:24:19
C 10.0.0.0/8 is directly connected, Ethernet1/3
B 10.0.0.0/8 [20/0] via 10.0.0.1, 02:10:22
B 10.0.0.0/8 [200/0] via 10.13.13.13, 00:24:20
This following sample output shows BGP entries in the IP routing table associated with the VRF named vrf1:
Device# show ip route vrf vrf1 bgp
B 10.0.0.0/8 [200/0] via 10.13.13.13, 03:44:14
B 10.0.0.0/8 [20/0] via 10.0.0.1, 03:44:12
B 10.0.0.0/8 [200/0] via 10.13.13.13, 03:43:14
The following sample output displays the IP routing table associated with a VRF named PATH:
Device# show ip route vrf PATH 10.22.22.0
Routing entry for 10.22.22.0/24
Known via "bgp 1", distance 200, metric 0
Tag 22, type internal
Last update from 10.22.5.10 00:01:07 ago
Routing Descriptor Blocks:
* 10.22.7.8 (Default-IP-Routing-Table), from 10.11.3.4, 00:01:07 ago
Route metric is 0, traffic share count is 1
AS Hops 1
10.22.1.9 (Default-IP-Routing-Table), from 10.11.1.2, 00:01:07 ago
Route metric is 0, traffic share count is 1
AS Hops 1
10.22.6.10 (Default-IP-Routing-Table), from 10.11.6.7, 00:01:07 ago
Route metric is 0, traffic share count is 1
AS Hops 1
10.22.4.10 (Default-IP-Routing-Table), from 10.11.4.5, 00:01:07 ago
Route metric is 0, traffic share count is 1
AS Hops 1
10.22.5.10 (Default-IP-Routing-Table), from 10.11.5.6, 00:01:07 ago
Route metric is 0, traffic share count is 1
AS Hops 1
The following sample output from the show ip route vrf vrf-name tag command displays route tag information for routes associated with vrf1. The route tags in the sample output are displayed in dotted decimal format.
Device# show ip route vrf vrf1 tag 5
Routing Table: vrf1
Routing entry for 10.0.0.1/24
Known via "static", distance 1, metric 0 (connected)
Tag 0.0.0.5
Routing Descriptor Blocks:
* directly connected, via Null0
Route metric is 0, traffic share count is 1
Route tag 0.0.0.5
The following sample outputs from the show ip route vrf command include recursive-via-host and recursive-via-connected flags:
Device# show ip route vrf v2 10.2.2.2 Routing Table: v2 Routing entry for 10.2.2.2/32 Known via "bgp 10", distance 20, metric 0 Tag 100, type external Last update from 192.168.1.1 00:15:54 ago Routing Descriptor Blocks: * 192.168.1.1, from 192.168.1.1, 00:15:54 ago, recursive-via-conn Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 100 MPLS label: none Device# show ip route vrf v2 10.2.2.2 Routing Table: v2 Routing entry for 10.2.2.2/32 Known via "bgp 10", distance 200, metric 0 Tag 100, type internal Last update from 10.3.3.3 00:18:11 ago Routing Descriptor Blocks: * 10.3.3.3 (default), from 10.5.5.5, 00:18:11 ago, recursive-via-host Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 100 MPLS label: 16 MPLS Flags: MPLS Required
The table below describes the significant fields shown in the displays.
| Table 25 | show ip route vrf Field Descriptions |
|
Field |
Description |
|---|---|
|
Routing entry for 10.22.22.0/24 |
Network number. |
|
Known via ... |
Indicates how the route was derived. |
|
distance |
Administrative distance of the information source. |
|
metric |
Metric used to reach the destination network. |
|
Tag |
Integer used to tag the route. |
|
type |
Indicates whether the route is an L1 type or L2 type of route. |
|
Last update from 10.22.5.10 |
Indicates the IP address of the device that is the next hop to the remote network and identifies the interface on which the last update arrived. |
|
00:01:07 ago |
Specifies the last time the route was updated (in hours:minutes:seconds). |
|
Routing Descriptor Blocks |
Displays the next-hop IP address followed by the information source. |
|
10.22.6.10, from 10.11.6.7, 00:01:07 ago |
Indicates the next-hop address, the address of the gateway that sent the update, and the time that has elapsed since this update was received (in hours:minutes:seconds). |
|
Route metric |
This value is the best metric for this routing descriptor block. |
|
Traffic share count |
Indicates the number of packets transmitted over various routes. |
|
AS Hops |
Number of hops to the destination or to the device where the route first enters internal BGP (iBGP). |
The following is sample output from the show ip route vrf command on devices using the Cisco IOS Software Modularity for Layer 3 VPNs feature. The output includes remote label information and corresponding MPLS flags for prefixes that have remote labels stored in the RIB if BGP is the label distribution protocol.
Device# show ip route vrf v2 10.2.2.2
Routing entry for 10.2.2.2/32
Known via "bgp 1", distance 200, metric 0, type internal
Redistributing via ospf 2
Advertised by ospf 2 subnets
Last update from 10.0.0.4 00:22:59 ago
Routing Descriptor Blocks:
* 10.0.0.4 (Default-IP-Routing-Table), from 10.0.0.31, 00:22:59 ago
Route metric is 0, traffic share count is 1
AS Hops 0
MPLS label: 1300
MPLS Flags: MPLS Required
The table below describes the significant fields shown in the display.
| Table 26 | show ip route vrf Field Descriptions |
|
Field |
Description |
|---|---|
|
MPLS label |
Displays the BGP prefix from the BGP peer. The output shows one of the following values:
The MPLS label field is not displayed if any of the following conditions is true:
|
|
MPLS Flags |
Name of the MPLS flag. One of the following MPLS flags is displayed:
|
The following sample output from the show ip route vrf command shows repair paths in the routing table. The fields in the display are self-explanatory.
Device> show ip route vrf test1 repair-paths 192.168.3.0
Routing Table: test1
Routing entry for 192.168.3.0/24
Known via "bgp 10", distance 20, metric 0
Tag 100, type external
Last update from 192.168.1.1 00:49:39 ago
Routing Descriptor Blocks:
* 192.168.1.1, from 192.168.1.1, 00:49:39 ago, recursive-via-conn
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 100
MPLS label: none
[RPR]10.4.4.4 (default), from 10.5.5.5, 00:49:39 ago, recursive-via-host
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 100
MPLS label: 29
MPLS Flags: MPLS Required, No Global
show ip static route
To display the static process local Routing Information Base (RIB) information, use the showipstaticroutecommand in user EXEC or privileged EXEC configuration mode.
Syntax Description
|
bfd |
(Optional) Displays IPv4 static Bidirectional Forwarding Detection (BFD) neighbor information. |
|
vrf vrf-name |
(Optional) Name of the VRF by which static routing information should be displayed. |
|
topology topology-name |
(Optional) Static route information for the specified topology. |
|
ip-address |
(Optional) Address by which static routing information should be displayed. |
|
mask |
(Optional) Subnet mask. |
|
multicast |
(Optional) Displays IPv4 multicast information. |
|
summary |
(Optional) Displays summary information. |
Examples
The following is sample output from the showipstaticroute command:
Router# show ip static route
Codes: M - Manual static, A - AAA download, N - IP NAT, D - DHCP,
G - GPRS, V - Crypto VPN, C - CASA, P - Channel interface processor,
B - BootP, S - Service selection gateway
DN - Default Network, T - Tracking object
L - TL1, E - OER
Codes in []: A - active, N - non-active, B - BFD-tracked, P - permanent
The table below describes the significant fields shown in the display.
show ip static route bfd
To display information about the IPv4 static Bidirectional Forwarding Detection (BFD) configuration from specific configured BFD groups and nongroup entries, use the show ip static route bfd command in user EXEC or privileged EXEC mode.
Usage Guidelines
You can specify a BFD group for a set of BFD-tracked static routes. Nongroup entries are BFD-tracked static routes for which a BFD group is not specified. Use the ip route static bfd command to configure static route BFD neighbors.
Use the show ip static route bfd command to display information about the IPv4 static BFD configuration from specific configured BFD groups and nongroup entries. The group group-name keyword and argument specifies a BFD group and BFD group name.
Examples
The following is sample output from the show ip static route bfd command:
Router# show ip static route bfd group group1
Codes in []: R - Reachable, U - Unreachable, L - Loop, D - Not Tracked
GigabitEthernet1/1 10.1.1.1 [U] [group1, Active]
GigabitEthernet1/2 10.2.2.2 [U] [group1, Passive]
The table below describes the significant fields shown in the display.
| Table 28 | show ip static route bfd Field Descriptions |
|
Field |
Description |
|---|---|
|
GigabitEthernet1/1 |
Interface through which the BFD session is initiated. |
|
10.1.1.1 |
Next hop IP address. |
|
group1 |
BFD group name. |
|
Active |
Active member of the group. |
|
GigabitEthernet1/2 |
Interface through which the BFD session is initiated. |
|
10.2.2.2 |
Next hop IP address. |
|
Passive |
Passive member of the group. |
show ipv6 policy
To display the IPv6 policy-based routing (PBR) configuration, use the show ipv6 policy command in user EXEC or privileged EXEC mode.
Usage Guidelines
IPv6 policy matches will be counted on route maps, as is done in IPv4. Therefore, IPv6 policy matches can also be displayed on the show route-map command.
show ipv6 route
To display contents of the IPv6 routing table, use the show ipv6 route command in user EXEC or privileged EXEC mode.
Syntax Description
|
ipv6-address |
(Optional) Displays routing information for a specific IPv6 address. |
|
ipv6-prefix |
(Optional) Displays routing information for a specific IPv6 network. |
|
/prefix-length |
(Optional) The length of the IPv6 prefix. A decimal value that indicates how many of the high-order contiguous bits of the address comprise the prefix (the network portion of the address). A slash mark must precede the decimal value. |
|
longer-prefixes |
(Optional) Displays output for longer prefix entries. |
|
protocol |
(Optional) The name of a routing protocol or the keyword connected, local, mobile, or static. If you specify a routing protocol, use one of the following keywords: bgp, isis, eigrp, ospf, or rip. |
|
updated |
(Optional) Displays routes with time stamps. |
|
boot-up |
(Optional) Displays routing information since boot up. |
|
day month |
(Optional) Displays routes since the specified day and month. |
|
time |
(Optional) Displays routes since the specified time, in hh:mm format. |
|
interface |
(Optional) Displays information about the interface. |
|
type |
(Optional) Interface type. |
|
number |
(Optional) Interface number. |
|
nd |
(Optional) Displays only routes from the IPv6 Routing Information Base (RIB) that are owned by Neighbor Discovery (ND). |
|
nsf |
(Optional) Displays routes in the nonstop forwarding (NSF) state. |
|
table table-id |
(Optional) Displays IPv6 RIB table information for the specified table ID. The table ID must be in hexadecimal format. The range is from 0 to 0-0xFFFFFFFF. |
|
watch |
(Optional) Displays information about route watchers. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.2(8)T |
This command was modified. The isis keyword was added, and the I1 - ISIS L1, I2 - ISIS L2, and IA - ISIS interarea fields were included in the command output. |
|
12.0(21)ST |
This command was integrated into Cisco IOS Release 12.0(21)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. The timer information was removed, and an indicator was added to display IPv6 Multiprotocol Label Switching (MPLS) interfaces. |
|
12.2(13)T |
This command was modified. The timer information was removed, and an indicator was added to display IPv6 MPLS virtual interfaces. |
|
12.2(14)S |
This command was modified. The longer-prefixes keyword was added. |
|
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
|
12.2(25)SG |
This command was integrated into Cisco IOS Release 12.2(25)SG. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
|
Cisco IOS XE Release 2.1 |
This command was introduced on Cisco ASR 1000 series Aggregation Services Routers. |
|
12.4(24)T |
This command was modified in a release earlier than Cisco IOS Release 12.4(24)T. The table, nsf, watch, and updated keywords and day, month, table-id, and time arguments were added. |
|
15.2(2)S |
This command was modified. The command output was enhanced to include route tag values in dotted-decimal format. |
|
Cisco IOS XE Release 3.6S |
This command was modified. The command output was enhanced to include route tag values in dotted-decimal format. |
|
15.1(1)SY |
The nd keyword was added. |
| 15.2(2)SNG | This command was implemented on Cisco ASR 901 Series Aggregation Services Routers. |
Usage Guidelines
The show ipv6 route command provides output similar to the show ip route command, except that the information is IPv6-specific.
When the ipv6-address or ipv6-prefix/prefix-length argument is specified, the longest match lookup is performed from the routing table, and only route information for that address or network is displayed. When a routing protocol is specified, only routes for that protocol are displayed. When the connected, local, mobile, or static keyword is specified, only the specified type of route is displayed. When the interface keyword and type and number arguments are specified, only the specified interface-specific routes are displayed.
Examples
The following is sample output from the show ipv6 route command when no keywords or arguments are specified:
Device# show ipv6 route
IPv6 Routing Table - 9 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - IIS interarea
B 2001:DB8:4::2/48 [20/0]
via FE80::A8BB:CCFF:FE02:8B00, Serial6/0
L 2001:DB8:4::3/48 [0/0]
via ::, Ethernet1/0
C 2001:DB8:4::4/48 [0/0]
via ::, Ethernet1/0
LC 2001:DB8:4::5/48 [0/0]
via ::, Loopback0
L 2001:DB8:4::6/48 [0/0]
via ::, Serial6/0
C 2001:DB8:4::7/48 [0/0]
via ::, Serial6/0
S 2001:DB8:4::8/48 [1/0]
via 2001:DB8:1::1, Null
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
The table below describes the significant fields shown in the display.
| Table 29 | show ipv6 route Field Descriptions |
|
Field |
Description |
|---|---|
|
Codes: |
Indicates the protocol that derived the route. Values are as follows: |
|
2001:DB8:4::2/48 |
Indicates the IPv6 prefix of the remote network. |
|
[20/0] |
The first number in brackets is the administrative distance of the information source; the second number is the metric for the route. |
|
via FE80::A8BB:CCFF:FE02:8B00 |
Specifies the address of the next router to the remote network. |
When the ipv6-address or ipv6-prefix/prefix-length argument is specified, only route information for that address or network is displayed. The following is sample output from the show ipv6 route command when IPv6 prefix 2001:DB8::/35 is specified. The fields in the display are self-explanatory.
Device# show ipv6 route 2001:DB8::/35
IPv6 Routing Table - 261 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
B 2001:DB8::/35 [20/3]
via FE80::60:5C59:9E00:16, Tunnel1
When you specify a protocol, only routes for that particular routing protocol are shown. The following is sample output from the show ipv6 route bgp command. The fields in the display are self-explanatory.
Device# show ipv6 route bgp
IPv6 Routing Table - 9 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
B 2001:DB8:4::4/64 [20/0]
via FE80::A8BB:CCFF:FE02:8B00, Serial6/0
The following is sample output from the show ipv6 route local command. The fields in the display are self-explanatory.
Device# show ipv6 route local
IPv6 Routing Table - 9 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
L 2001:DB8:4::2/128 [0/0]
via ::, Ethernet1/0
LC 2001:DB8:4::1/128 [0/0]
via ::, Loopback0
L 2001:DB8:4::3/128 [0/0]
via ::, Serial6/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
The following is sample output from the show ipv6 route command when the 6PE multipath feature is enabled. The fields in the display are self-explanatory.
Device# show ipv6 route
IPv6 Routing Table - default - 19 entries
Codes:C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
.
.
.
B 2001:DB8::/64 [200/0]
via ::FFFF:172.11.11.1
via ::FFFF:172.30.30.1
show ipv6 route shortcut
To display the IPv6 routes that contain shortcuts, use the show ipv6 route shortcutcommand in privileged EXEC mode.
Usage Guidelines
The show ipv6 route shortcut command displays only the routes that have overriding shortcut paths.
Examples
The following is sample output from the show ipv6 route shortcutcommand:
Router# show ipv6 route shortcut
IPv6 Routing Table - default - 7 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP
H - NHRP, I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
IS - ISIS summary, D - EIGRP, EX - EIGRP external, NM - NEMO
ND - Neighbor Discovery, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S 7000:1::/64 [1/0]
via 4000:1:1::1, Ethernet1/1 [Shortcut]
via 5000:1:1::1, Ethernet1/1 [Shortcut]
via Ethernet1/1, directly connected
S 8000:1:1::/64 [1/0]
via 6000:1:1::1, Ethernet0/1 [Shortcut]
via Ethernet0/0, directly connected
The table below describes the significant fields shown in the display.
| Table 30 | show ipv6 route shortcut Field Descriptions |
|
Field |
Description |
|---|---|
|
Codes: |
Indicates the protocol that derived the route. Values are as follows: |
|
S 7000:1::/64 [1/0] |
Indicates paths that may be shortcut paths. |
|
via 4000:1:1::1, Ethernet1/1 |
Indicates a path that may be a shortcut path. |
|
via 5000:1:1::1, Ethernet1/1 [Shortcut] |
Indicates a path that may be a shortcut path. |
|
via Ethernet1/1, directly connected |
Shows routes connected to the router directly. |
show ipv6 route summary
To display the current contents of the IPv6 routing table in summary format, use the show ipv6 route summarycommand in user EXEC or privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(21)ST |
This command was integrated into Cisco IOS Release 12.0(21)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
|
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
|
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
|
12.2(25)SG |
This command was integrated into Cisco IOS Release 12.2(25)SG. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
Examples
The following is sample output from the show ipv6 route summary command:
Router# show ipv6 route summary
IPv6 Routing Table Summary - 257 entries
37 local, 35 connected, 25 static, 0 RIP, 160 BGP
Number of prefixes:
/16: 1, /24: 46, /28: 10, /32: 5, /35: 25, /40: 1, /48: 63, /64: 19
/96: 15, /112: 1, /126: 31, /127: 4, /128: 36
The table below describes the significant fields shown in the display.
| Table 31 | show ipv6 route summary Field Descriptions |
|
Field |
Description |
|---|---|
|
entries |
Number of entries in the IPv6 routing table. |
|
Route source |
Number of routes that are present in the routing table for each route source, which can be local routes, connected routes, static routes, a routing protocol, prefix and address or name, and longer prefixes and address or name. Routing protocols can include RIP, IS-IS, OSPF, and BGP. Other route sources can be connected, local, static, or a specific interface. |
|
Number of prefixes: |
Number of routing table entries for given prefix length. |
show ipv6 route tag
To display route tag entries for IPv6 routes, use the show ipv6 route tag command in user EXEC or privileged EXEC mode.
Usage Guidelines
Route tags are 32-bit values attached to routes. They are used to filter routes. You can display route tag entries as either plain decimals or dotted decimals.
Examples
The following sample output from the show ipv6 route tag command displays detailed information about route tag entries in the routing table. Route tag values in this output are displayed in dotted-decimal format.
Device# show ipv6 route tag 0.0.10.10
IPv6 Routing Table - default - 4 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, H - NHRP, I1 - ISIS L1
I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE -
Destination
NDr - Redirect, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R 2001:DB8::/96 [120/2]
Tag 0.0.10.10
via FE80::A8BB:CCFF:FE00:A00, Ethernet0/0
The following sample output from the show ipv6 route tag command displays detailed information about route tag entries with the wild card mask. Route tag values in this output are displayed in dotted-decimal format.
Device# show ipv6 route tag 0.0.0.10 0.0.0.7
IPv6 Routing Table - default - 4 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, H - NHRP, I1 - ISIS L1
I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE - Destination
NDr - Redirect, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R 2001:DB8::/32 [0/0]
Tag 0.0.0.10
via FE80::A8BB:CCFF:FE00:A00, Ethernet0/0
The table below describes the significant fields in the displays.
| Table 32 | show ipv6 route tag Field Descriptions |
|
Field |
Description |
|---|---|
|
Codes |
Indicates the protocol that derived the route. It can be one of the following values: |
|
2001:DB8::/96 [120/2] |
Indicates the address of the remote network. |
|
Tag |
Identifies the tag associated with the remote network. |
|
via FE80::A8BB:CCFF:FE00:A00 |
Specifies the IPv6 address of the next router to the remote network. |
|
Ethernet0/0 |
Specifies the interface through which the specified network can be reached. |
show ipv6 route vrf
To display IPv6 routing table information associated with a VPN routing and forwarding (VRF) instance, use the show ipv6 route vrf command in user EXEC or privileged EXEC mode.
Syntax Description
|
vrf-name |
Name assigned to the VRF. |
|
vrf-number |
Hexadecimal number assigned to the VRF. |
|
tag |
(Optional) Displays information about route tags in the VRF table. |
|
tag-value |
(Optional) Displays route tag value in plain decimals. |
|
tag-value-dotted-decimal |
(Optional) Displays route tag values in dotted decimals. |
|
mask |
(Optional) Route tag wildcard mask. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(33)SRB |
This command was introduced. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
15.2(2)S |
This command was integrated into Cisco IOS Release 15.2(2)S. The tag keyword and the tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain decimals or dotted decimals in the command output. |
|
Cisco IOS XE Release 3.6S |
This command was integrated into Cisco IOS XE Release 3.6S. The tag keyword and the tag-value, tag-value-dotted-decimal, and mask arguments were added to enable the display of route tags as plain decimals or dotted decimals in the command output. |
| 15.2(4)M | This command was integrated into Cisco IOS Release 15.2(4)M. |
Examples
The following sample output from the show ipv6 route vrf command displays information about the IPv6 routing table associated with VRF1:
Device# show ipv6 route vrf VRF1
IPv6 Routing Table VRF1 - 6 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
C 2001:DB8:4::2/48 [0/0]
via ::, FastEthernet0/0
L 2001:DB8:4::3/48 [0/0]
via ::, FastEthernet0/0
B 2001:DB8:4::4/48 [200/0]
via ::FFFF:192.168.1.4,
B 2001:DB8:4::5/48 [20/1]
via 2001:8::1,
C 2001:DB8:4::6/48 [0/0]
via ::, Loopback1
L 2001:DB8:4::7/48 [0/0]
via ::, Loopback1
The following sample output from the show ip route vrf vrf-name tag command displays information about tagged IPv6 routes in vrf1:
Device# show ipv6 route vrf vrf1 tag 0.0.0.6
IPv6 Routing Table - vrf1 - 2 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, H - NHRP, I1 - ISIS L1
I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE - Destination
NDr - Redirect, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
Routing entry for 2001::/32
Known via "static", distance 1, metric 0
Tag 0.0.0.6
Route count is 1/1, share count 0
Routing paths:
directly connected via Null0
Last updated 00:00:23 ago
The table below describes the significant fields shown in the displays.
show isis fast-reroute
To display information about Intermediate System-to-Intermediate System (IS-IS) fast reroute (FRR) configurations, use the show isis fast-reroute command in user EXEC or privileged EXEC mode.
Syntax Description
|
interfaces |
Displays information about platform support capability for all interfaces running IS-IS. |
|
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
|
number |
(Optional) Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function. |
|
summary |
Displays FRR configuration information summary. |
| remote-lfa tunnels |
Displays information about remote loop-free alternate (LFA) tunnels. |
Usage Guidelines
The show isis fast-reroute command displays whether an interface is supported by a platform.
Examples
The following is sample output from the show isis fast-reroute interfaces command:
Router# show isis fast-reroute interfaces
Tag Null - Fast-Reroute Platform Support Information:
Serial6/3: Protectable: Yes. Usable for repair: Yes
Serial6/2: Protectable: Yes. Usable for repair: Yes
Loopback16: Protectable: No. Usable for repair: No
The table below describes the significant fields shown in the display.
| Table 34 | show isis fast-reroute interfaces Field Descriptions |
|
Field |
Description |
|---|---|
|
Protectable |
Specifies whether an interface is supported by the platform to be protected by FRR. |
|
Usable for repair |
Specifies whether an interface is supported by the platform to be used as a repair path. |
Note | Whether an interface is actually FRR protected or is acting as an FRR repair interface depends on the topology and the configuration. The information in the show isis fast-reroute interfaces command shows only the capability of the interface as supported by the platform. |
The following is sample output from the show isis fast-reroute summary command:
Router# show isis fast-reroute summary
Prefix Counts: Total Protected Coverage
High priority: 17 17 100%
Normal priority: 0 0 0%
The table below describes the significant fields shown in the display.
| Table 35 | show isis fast-reroute summary Field Descriptions |
|
Field |
Description |
|---|---|
|
Total |
Total number of prefixes. |
|
Protected |
Total number of protected prefixes. |
|
High priority |
Prefixes that have a high priority. |
|
Normal priority |
Prefixes that have a normal priority. |
The following is sample output from the show isis fast-reroute remote-lfa tunnels command:
Router# show isis fast-reroute remote-lfa tunnels
Tag Null - Fast-Reroute Remote-LFA Tunnels:
MPLS-Remote-Lfa1: use Et1/0, nexthop 10.0.0.1, end point 24.24.24.24
MPLS-Remote-Lfa2: use Et0/0, nexthop 10.1.1.2, end point 24.24.24.24
show key chain
Command History
|
Release |
Modification |
|---|---|
|
11.1 |
This command was introduced. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the showkeychain command:
Router# show key chain
Key-chain trees:
key 1 -- text "chestnut"
accept lifetime (always valid) - (always valid) [valid now]
send lifetime (always valid) - (always valid) [valid now]
key 2 -- text "birch"
accept lifetime (00:00:00 Dec 5 1995) - (23:59:59 Dec 5 1995)
send lifetime (06:00:00 Dec 5 1995) - (18:00:00 Dec 5 1995)
Related Commands
|
Command |
Description |
|---|---|
|
accept-lifetime |
Sets the time period during which the authentication key on a key chain is received as valid. |
|
key |
Identifies an authentication key on a key chain. |
|
key chain |
Enables authentication for routing protocols. |
|
key-string (authentication) |
Specifies the authentication string for a key. |
|
send-lifetime |
Sets the time period during which an authentication key on a key chain is valid to be sent. |
show monitor event-trace
To display event trace messages for Cisco IOS software subsystem components, use the showmonitorevent-trace command in privileged EXEC mode.
Syntax Description
|
all-traces |
(Optional) Displays all event trace messages in memory to the console. |
|
component |
(Optional) Name of the Cisco IOS software subsystem component that is the object of the event trace. To get a list of components that support event tracing in this release, use the monitorevent-trace? command. |
|
all |
Displays all event trace messages currently in memory for the specified component. |
|
back hour:minute |
Specifies how far back from the current time you want to view messages. For example, you can gather messages from the last 30 minutes. The time argument is specified in hours and minutes format (hh:mm). |
|
clock hour:minute |
Displays event trace messages starting from a specific clock time in hours and minutes format (hh:mm). |
|
from-boot seconds |
Displays event trace messages starting from a specified number of seconds after booting (uptime). To display the uptime, in seconds, enter the showmonitorevent-tracecomponentfrom-boot? command. |
|
latest |
Displays only the event trace messages since the last showmonitorevent-trace command was entered. |
|
parameters |
Displays the trace parameters. The only parameter displayed is the size (number of trace messages) of the trace file. |
Command History
|
Release |
Modification |
|---|---|
|
12.0(18)S |
This command was introduced. |
|
12.2(8)T |
This command was integrated into Cisco IOS Release 12.2(8)T. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. The showmonitorevent-tracecef command replaced the showcefeventsand showipcefevents commands. |
|
12.2(18)SXE |
This command was integrated into Cisco IOS Release 12.2(18)SXE. The spa component keyword was added to support online insertion and removal (OIR) event messages for shared port adapters (SPAs). The bfd keyword was added for the component argument to display trace messages relating to the Bidirectional Forwarding Detection (BFD) feature. |
|
12.4(4)T |
Support for the bfd keyword was added for Cisco IOS Release 12.4(4)T. |
|
12.0(31)S |
Support for the bfd keyword was added for Cisco IOS Release 12.0(31)S. |
|
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers. |
|
12.4(9)T |
The cfd keyword was added as an entry for the component argument to display trace messages relating to crypto fault detection. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
Usage Guidelines
Use the showmonitorevent-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 showmonitorevent-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 showmonitorevent-tracecommand 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.
IPC Component Example
The following is sample output from the showmonitorevent-tracecomponent 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 ipc
3667: 6840.016:Message type:3 Data=0123456789
3668: 6840.016:Message type:4 Data=0123456789
3669: 6841.016:Message type:5 Data=0123456789
3670: 6841.016:Message type:6 Data=0123456
BFD Component for Cisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T
Use the showmonitorevent-tracebfdallcommand to display logged messages for important BFD events in the recent past. The following trace messages show BFD session state changes:
Router# show monitor event-trace bfd all
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], event Session
create, state Unknown -> Fail
3d03h: 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 Session
create, state Unknown -> Fail
3d07h: 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 showmonitorevent-traceall-traces command. In this example, separate output is provided for each event, and message numbers are interleaved between the events.
Router# show monitor event-trace all-traces
Test1 event trace:
3667: 6840.016:Message type:3 Data=0123456789
3669: 6841.016:Message type:4 Data=0123456789
3671: 6842.016:Message type:5 Data=0123456789
3673: 6843.016:Message type:6 Data=0123456789
Test2 event trace:
3668: 6840.016:Message type:3 Data=0123456789
3670: 6841.016:Message type:4 Data=0123456789
3672: 6842.016:Message type:5 Data=0123456789
3674: 6843.016:Message type:6 Data=0123456789
SPA Component Example
The following is sample output from the showmonitorevent-tracecomponentlatest command for the spa component:
Router# show monitor event-trace spa latest
00:01:15.364: subslot 2/3: 4xOC3 POS SPA, TSM Event:inserted New state:wait_psm
_ready
spa type 0x440
00:02:02.308: subslot 2/0: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/0: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/1: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/1: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/2: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/2: not present, TSM Event:remove_complete New state:idle
00:02:02.312: subslot 2/3: not present(plugin 4xOC3 POS SPA), TSM Event:empty New
state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.312: subslot 2/3: not present, TSM Event:remove_complete New state:idle
Cisco 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: showmonitorevent-tracecef [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 all 00:00:24.612: [Default] *::*/*'00 New FIB table [OK] Router# show monitor event-trace cef ipv4 all 00: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 all 00:00:18.884: SubSys fib_ios_chain init 00:00:18.884: Inst unknown -> RP 00:00:24.584: SubSys fib init 00:00:24.592: SubSys fib_ios init 00:00:24.592: SubSys fib_ios_if init 00:00:24.596: SubSys ipv4fib init 00:00:24.608: SubSys ipv4fib_ios init 00:00:24.612: SubSys ipv6fib_ios init 00:00:24.620: Flag IPv4 CEF enabled set to yes 00:00:24.620: Flag 0x7BF6B62C set to yes 00:00:24.620: Flag IPv4 CEF switching enabled set to yes 00:00:24.624: GState CEF enabled 00:00:24.628: SubSys ipv4fib_les init 00:00:24.628: SubSys ipv4fib_pas init 00:00:24.632: SubSys ipv4fib_util init 00:00:25.304: Process Background created 00:00:25.304: Flag IPv4 CEF running set to yes 00:00:25.304: Process Background event loop enter 00:00:25.308: Flag IPv4 CEF switching running set to yes
The following example shows Cisco Express Forwarding interface events:
Router# show monitor event-trace cef interface all 00:00:24.624: <empty> (sw 4) Create new 00:00:24.624: <empty> (sw 4) SWIDBLnk FastEthernet0/0(4) 00:00:24.624: Fa0/0 (sw 4) NameSet 00:00:24.624: <empty> (hw 1) Create new 00:00:24.624: <empty> (hw 1) HWIDBLnk FastEthernet0/0(1) 00:00:24.624: Fa0/0 (hw 1) NameSet 00:00:24.624: <empty> (sw 3) Create new 00:00:24.624: <empty> (sw 3) SWIDBLnk FastEthernet0/1(3) 00:00:24.624: Fa0/1 (sw 3) NameSet 00:00:24.624: <empty> (hw 2) Create new
Cisco Express Forwarding Component Examples for Cisco 10000 Series Routers Only
The following example shows the IPv4 events related to the Cisco Express Forwarding component. Each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.
Router# show monitor event-trace cef ipv4 all
00: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 all
00:00:18.884: SubSys fib_ios_chain init
00:00:18.884: Inst unknown -> RP
00:00:24.584: SubSys fib init
00:00:24.592: SubSys fib_ios init
00:00:24.592: SubSys fib_ios_if init
00:00:24.596: SubSys ipv4fib init
00:00:24.608: SubSys ipv4fib_ios init
00:00:24.620: Flag IPv4 CEF enabled set to yes
00:00:24.620: Flag 0x7BF6B62C set to yes
00:00:24.620: Flag IPv4 CEF switching enabled set to yes
00:00:24.624: GState CEF enabled
00:00:24.628: SubSys ipv4fib_les init
00:00:24.628: SubSys ipv4fib_pas init
00:00:24.632: SubSys ipv4fib_util init
00:00:25.304: Process Background created
00:00:25.304: Flag IPv4 CEF running set to yes
00:00:25.304: Process Background event loop enter
00:00:25.308: Flag IPv4 CEF switching running set to yes
The following examples show Cisco Express Forwarding interface events:
Router# show monitor event-trace cef interface all
00:00:24.624: <empty> (sw 4) Create new
00:00:24.624: <empty> (sw 4) SWIDBLnk FastEthernet1/0/0(4)
00:00:24.624: Fa0/0 (sw 4) NameSet
00:00:24.624: <empty> (hw 1) Create new
00:00:24.624: <empty> (hw 1) HWIDBLnk FastEthernet1/0/0(1)
00:00:24.624: Fa0/0 (hw 1) NameSet
00:00:24.624: <empty> (sw 3) Create new
00:00:24.624: <empty> (sw 3) SWIDBLnk FastEthernet1/1/0(3)
00:00:24.624: Fa0/1 (sw 3) NameSet
00:00:24.624: <empty> (hw 2) Create new
CFD Component for Cisco IOS Release 12.4(9)T
To troubleshoot errors in an encryption datapath, enter the showmonitorevent-tracecfdallcommand.Inthisexample,eventsareshownseparately,eachbeginningwithatimestamp,followedbydatafromtheerrortracebuffer.CiscoTechnicalAssistanceCenter(TAC)engineerscanusethisinformationtodiagnosethecauseoftheerrors.
Note | If no packets have been dropped, this command does not display any output. |
Router# show monitor event-trace cfd all
00: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 F8AC4E64
Related Commands
|
Command |
Description |
|---|---|
|
monitor event-trace (EXEC) |
Controls event trace functions for a specified Cisco IOS software subsystem component. |
|
monitor event-trace (global) |
Configures event tracing for a specified Cisco IOS software subsystem component. |
|
monitor event-trace dump-traces |
Saves trace messages for all event traces currently enabled on the networking device. |
show platform hardware qfp active feature cef-mpls prefix ip
To display the interface name along with the interface descriptor block (IDB) information, use the showplatformhardwareqfpactivefeaturecef-mplsprefixip command in privileged EXEC.
Syntax Description
|
ipv4 prefix |
IPv4 address and mask. |
|
vrf |
(Optional) Displays information about VPN Routing and Forwarding (VRF). |
|
id |
(Optional) Information about the particular VRF instance. The range is from 0 to 4294967295. If no VRF ID is specified, information about the global VRF, which is the prefix in global routing table, is displayed. |
|
exact |
(Optional) Find and displays the exact match of the IPV4 prefix. |
|
brief |
(Optional) Displays a summary of prefix information. |
Examples
The following is sample output from theshowplatformhardwareqfpactivefeaturecef-mplsprefixip command:
Router# show platform hardware qfp active feature cef-mpls prefix ip 0.0.0.0/1 vrf Gtrie Node Type: Leaf Node HW Content: : 00002000 00000000 897daf40 895db490 QPPB QoS Precedence valid: 0 QoS Precedence: 0 QPPB QoS Group valid: 0 QoS Group: 0 BGPPA Traffic Index valid: 0 BGPPA Traffic Index: 0 TBLF refcount: 2 TBLF application lf handle: 0 Prefix Length: 32 Prefix: 64 00 00 01 === uRPF path list === Loose Flag: : 1 Path list pointer: : 0x8b8414a0 Number of interfaces: : 1 Interfaces: : 1017 Interface Name(s): GigabitEthernet0/3/1 === OCE === OCE Type: Adjacency, Number of children: 0 Adj Type: : IPV4 Adjacency Encap Len: : 14 L3 MTU: : 1500 Adj Flags: : 0 Fixup Flags: : 0 Output UIDB: : 65522 Interface Name: GigabitEthernet0/3/1 Encap: : 00 14 f1 74 9c 1a 00 1a 30 44 3a 31 08 00 Next Hop Address: : 64000001 00000000 00000000 00000000 Oce Chain: : 0
The following example shows the output with the names of each interface when there are multiple interfaces in the unicast reverse path forwarding (uRPF) path list:
Router# show platform hardware qfp active feature cef-mpls prefix ip 0.0.0.0/2 vrf
Gtrie Node Type: Leaf Node HW Content: : 00001800 00000000 897dae00 895d8df0 QPPB QoS Precedence valid: 0 QoS Precedence: 0 QPPB QoS Group valid: 0 QoS Group: 0 BGPPA Traffic Index valid: 0 BGPPA Traffic Index: 0 TBLF refcount: 2 TBLF application lf handle: 0 Prefix Length: 24 Prefix: 4d 4d 4d === uRPF path list === Loose Flag: : 1 Path list pointer: : 0x8b8414a0 Number of interfaces: : 2 Interfaces: : 1019, 1017 Interface Name(s): : GigabitEthernet0/0/4, GigabitEthernet0/3/1
show platform hardware qfp active feature cef-mpls prefix ipv6
To display the interface name, along with the interface descriptor block (IDB) information for IPv6 addressing, use the show platform hardware qfp active feature cef-mpls prefix ipv6 command in privileged EXEC mode.
Syntax Description
|
ipv6-prefix |
IPv6 address and prefix. The IPv6 prefix is in the range from 0 to 128. |
|
vrf id |
(Optional) Displays the particular VPN Routing and Forwarding (VRF) instance. The VRF ID is in the range from 0 to 4294967295. If no VRF ID is specified, information about the global VRF (prefix in global routing table) is displayed. |
|
exact |
(Optional) Finds and displays the exact match of the IPv6 prefix. |
|
brief |
(Optional) Displays a summary of prefix information. |
Command Modes
Privileged EXEC (#)
Examples
The following is sample output from the show platform hardware qfp active feature cef-mpls prefix ipv6 command:
Router# show platform hardware qfp active feature cef-mpls prefix ipv6 2001:DB8::/64
=== Gtrie Node ===
Gtrie Node Type: Tree Node
HW Content: : 89d000cd 00000004 60000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 1, TN skip 0
TN zero perf real len: 0
TN par bl offset: 0
TN par bl len: 0
TBM Tree Array
TA NNodes 2, TA INode Exists 1, TN TNRefs 0x11608698
TBM Tree Node Bitmap
Search Node Bitmap: 60 00 00 00 00 00 00 00
=== Gtrie Node ===
Gtrie Node Type: Leaf Node
HW Content: : 00004000 00000000 89995400 895c9420
QPPB QoS Precedence valid: 0
QoS Precedence: 0
QPPB QoS Group valid: 0
QoS Group: 0
BGPPA Traffic Index valid: 0
BGPPA Traffic Index: 0
TBLF refcount: 2
TBLF application lf handle: 0
CTS src_sgt: 0
CTS dst_sgt: 0
Prefix Length: 64
Prefix: cc 1e 00 00 00 00 00 00
Lisp local eid: 0
Lisp remote eid: 0
Lisp locator status bits: 0
=== uRPF path list ===
Loose Flag: : 1
Path list pointer: : 0x895c9670
Number of interfaces: : 1
Interfaces: : 1015
Interface Name(s): : GigabitEthernet0/2/0
=== OCE ===
OCE Type: Adjacency, Number of children: 0
Adj Type: : Glean Adjacency
Encap Len: : 0
L3 MTU: : 0
Adj Flags: : 0
Fixup Flags: : 0
Interface Name:
Next Hop Address: : 00000000 00000000 00000000 00000000
Next HW OCE Ptr: : 00000000
show platform hardware qfp active feature cef-mpls prefix mpls
To display the interface name, along with the interface descriptor block (IDB) information, use the show platform hardware qfp active feature cef-mpls prefix mpls command in privileged EXEC mode.
Syntax Description
| label |
Multiprotocol Label Switching (MPLS) label. The range is from 0 to 1048575. |
| vrf |
(Optional) Displays information about VPN Routing and Forwarding (VRF). |
| id |
(Optional) Information about the particular VRF instance. The range is from 0 to 4294967295. If no VRF ID is specified, information about the global VRF, which is the prefix in global routing table, is displayed. |
| exact |
(Optional) Finds and displays the exact match of the prefix. |
| brief |
(Optional) Displays a summary of prefix information. |
Command Modes
Privileged EXEC (#)
Examples
The following is sample output from the show platform hardware qfp active feature cef-mpls prefix mpls command:
Router# show platform hardware qfp active feature cef-mpls prefix mpls 0
=== Gtrie Node ===
Gtrie Node Type: Tree Node
HW Content: : 89b00cad 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TN zero perf real len: 0
TN par bl offset: 0
TN par bl len: 0
TBM Tree Array
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116085e8
TBM Tree Node Bitmap
Search Node Bitmap: 80 00 00 00 00 00 00 00
=== Gtrie Node ===
Gtrie Node Type: Tree Node
HW Content: : 89b00cbd 00000000 80000000 00000000
Gtrie Tree Node Type:: Search Trie Node
=== Gtrie Search Node ===
TN type 0, TN scan use 0, TN stride 6
TN inode exists 0, TN skip 0
TN zero perf real len: 0
TN par bl offset: 0
TN par bl len: 0
TBM Tree Array
TA NNodes 1, TA INode Exists 0, TN TNRefs 0x116093d8
TBM Tree Node Bitmap
Search Node Bitmap: 80 00 00 00 00 00 00 00
=== Gtrie Node ===
Gtrie Node Type: Leaf Node
HW Content: : 0a000000 00000f00 00000000 895c97f0
QPPB QoS Precedence valid: 0
QoS Precedence: 0
QPPB QoS Group valid: 0
QoS Group: 0
BGPPA Traffic Index valid: 0
BGPPA Traffic Index: 0
TBLF refcount: 2
TBLF application lf handle: 0
CTS src_sgt: 0
CTS dst_sgt: 0
Prefix Length: 20
Prefix: 00 00 00
Lisp local eid: 0
Lisp remote eid: 0
Lisp locator status bits: 0
=== OCE ===
OCE Type: EOS OCE, Number of children: 2
Next HW OCE Ptr: : 0x895c97d0, 0x895c97b0
=== OCE ===
OCE Type: Label OCE, Number of children: 1
Label flags: : 65
Num Labels: : 1
Num Bk Labels: : 0
Out Labels: : 3
Next HW OCE Ptr: : 0x895c9790
=== OCE ===
OCE Type: Lookup OCE, Number of children: 0
Lookup flags: : 1
Table Type: : 0
Lookup table ID: : 0
show route-map
To display static and dynamic route maps configured on the router, use the show route-map command in user EXEC or privileged EXEC mode.
Syntax Description
|
map-name |
(Optional) Name of a specific route map. |
|
dynamic |
(Optional) Displays dynamic route map information. |
|
dynamic-map-name |
(Optional) Name of a specific, dynamic route map. |
|
application |
(Optional) Displays dynamic route maps based on applications. |
|
application-name |
(Optional) Name of a specific application. |
|
all |
(Optional) Displays all static and dynamic route maps. |
|
detailed |
(Optional) Displays details of access control lists (ACLs) that have been used in match clauses for dynamic route maps. |
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S, and support for Continue clauses was included in the command output. |
|
12.2(27)SBA |
This command was modified. The output was enhanced to display dynamically assigned route maps in VPN routing and forwarding (VRF) tables. |
|
12.2(15)T |
This command was modified. An additional counter-collect policy routing statistic was added to the command output. |
|
12.3(2)T |
This command was modified. Support for Continue clauses was included in the command output. |
|
12.2(17b)SXA |
This command was integrated into Cisco IOS Release 12.2(17b)SXA. |
|
12.3(7)T |
This command was modified. The dynamic, application, and all keywords were added. |
|
12.0(28)S |
This command was modified. Support for the recursive next-hop clause was added to the command output. |
|
12.3(14)T |
This command was modified. Support for the recursive next-hop clause, map display extension functionality, and the detailed keyword was added. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
Cisco IOS XE Release 2.2 |
This command was integrated into Cisco IOS XE Release 2.2. |
|
15.0(1)M |
This command was modified. The detailed keyword was removed. |
|
15.2(2)S |
This command was modified. The command output was enhanced to display route tag values in dotted-decimal format. |
|
Cisco IOS XE Release 3.6S |
This command was modified. The command output was enhanced to display route tag values in dotted-decimal format. |
|
15.1(1)SY |
This command was integrated into Cisco IOS Release 15.1(1)SY. |
Usage Guidelines
The show route-map command displays information about route maps configured on the router. The output will vary depending on the keywords included with the command and the Cisco software image running on your router.
The following is sample output from the show route-map command when no keywords or arguments are used:
Device# show route-map
route-map ROUTE-MAP-NAME, permit, sequence 10
Match clauses:
ip address (access-lists): 1
metric 10
Continue: sequence 40
Set clauses:
as-path prepend 10
Policy routing matches: 0 packets, 0 bytes
route-map ROUTE-MAP-NAME, permit, sequence 20
Match clauses:
ip address (access-lists): 2
metric 20
Set clauses:
as-path prepend 10 10
Policy routing matches: 0 packets, 0 bytes
route-map ROUTE-MAP-NAME, permit, sequence 30
Match clauses:
Continue: to next entry 40
Set clauses:
as-path prepend 10 10 10
Policy routing matches: 0 packets, 0 bytes
route-map ROUTE-MAP-NAME, deny, sequence 40
Match clauses:
community (community-list filter): 20:2
Set clauses:
local-preference 100
Policy routing matches: 0 packets, 0 bytes
route-map LOCAL-POLICY-MAP, permit, sequence 10
Match clauses:
Set clauses:
community 655370
Policy routing matches: 0 packets, 0 bytes
The following sample output from the show route-map command displays information about route tags:
Device# show route-map
route-map STATIC, permit, sequence 10
Match clauses:
ip address (access-lists): 1
Set clauses:
metric 56 100 255 1 1500
tag 1.1.1.1
Policy routing matches: 0 packets, 0 bytes
route-map STATIC, permit, sequence 20
Match clauses:
ip address (access-lists): 2
Set clauses:
metric 56 100 255 1 1500
tag 1.1.1.2
Policy routing matches: 0 packets, 0 bytes
The following sample output from the show route-map command shows Multiprotocol Label Switching (MPLS)-related route map information:
Device# show route-map
route-map OUT, permit, sequence 10
Match clauses:
ip address (access-lists): 1
Set clauses:
mpls label
Policy routing matches: 0 packets, 0 bytes
route-map IN, permit, sequence 10
Match clauses:
ip address (access-lists): 2
mpls label
Set clauses:
Policy routing matches: 0 packets, 0 bytes
The following is sample output from the show route-map dynamic command:
Device# show route-map dynamic
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 0, identifier 1137954548
Match clauses:
ip address (access-lists): PBR#1 PBR#2
Set clauses:
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 1, identifier 1137956424
Match clauses:
ip address (access-lists): PBR#3 PBR#4
Set clauses:
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 2, identifier 1124436704
Match clauses:
ip address (access-lists): PBR#5 PBR#6
length 10 100
Set clauses:
ip next-hop 172.16.1.1
ip gateway 172.16.1.1
Policy routing matches: 0 packets, 0 bytes
Current active dynamic routemaps = 1
The following is sample output from the show route-map dynamic application command:
Device# show route-map dynamic application
Application - AAA
Number of active routemaps = 1
When you specify an application name, dynamic routes for that application are displayed. The following is sample output from the show route-map dynamic application command when you specify the name of the application:
Device# show route-map dynamic application AAA AAA Number of active rmaps = 2 AAA-02/06/04-14:01:26.619-1-AppSpec AAA-02/06/04-14:34:09.735-2-AppSpec Device# show route-map dynamic AAA-02/06/04-14:34:09.735-2-AppSpec route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 0, identifier 1128046100 Match clauses: ip address (access-lists): PBR#7 PBR#8 Set clauses: Policy routing matches: 0 packets, 0 bytes route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 1, identifier 1141277624 Match clauses: ip address (access-lists): PBR#9 PBR#10 Set clauses: Policy routing matches: 0 packets, 0 bytes route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 2, identifier 1141279420 Match clauses: ip address (access-lists): PBR#11 PBR#12 length 10 100 Set clauses: ip next-hop 172.16.1.12 ip gateway 172.16.1.12 Policy routing matches: 0 packets, 0 bytes Current active dynamic routemaps = 2
The following is sample output from the show route-map dynamic detailed command:
Device# show route-map dynamic detailed
route-map AAA-01/20/04-22:03:10.799-1-AppSpec, permit, sequence 1, identifier 29675368
Match clauses:
ip address (access-lists):
Extended IP access list PBR#3
1 permit icmp 0.0.16.12 1.204.167.240 10.1.1.0 0.0.0.255 syn dscp af12 log-input fragments
Extended IP access list PBR#4
1 permit icmp 0.0.16.12 1.204.167.240 10.1.1.0 0.0.0.255 syn dscp af12 log-input fragments
Set clauses:
ip next-hop 172.16.1.14
ip gateway 172.16.1.14
Policy routing matches: 0 packets, 0 bytes
The following is sample output from the show route-map dynamic command when a VRF is configured for VRF autoclassification:
Device# show route-map dynamic
route-map None-06/01/04-21:14:21.407-1-IP VRF, permit, sequence 0
identifier 1675771000
Match clauses:
Set clauses: vrf vrf1
Policy routing matches: 0 packets, 0 bytes
Current active dynamic routemaps = 1
The table below describes the significant fields shown in the displays.
| Table 36 | show route-map Field Descriptions |
|
Field |
Description |
|---|---|
|
Route-map ROUTE-MAP-NAME |
Name of the route map. |
|
Permit |
Indicates that the route is redistributed based on set actions. |
|
Sequence |
Number that indicates the position of the new route map in the list of configured route maps. |
|
Match clauses |
Match criteria or conditions based on which the route map is redistributed. |
|
Continue |
Displays the configuration of a continue clause and the next route-map entry to which the clause is sent. |
|
Set clauses |
Specific redistribution actions to be performed if the match command criteria are met. |
|
Tag |
Tag for routes to the remote network. |
|
Policy routing matches |
Number of packets and bytes that have been filtered by policy routing. |
Related Commands
|
Command |
Description |
|---|---|
|
redistribute (IP) |
Redistributes routes from one routing domain into another routing domain. |
|
route-map (IP) |
Defines conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
|
match interface (IP) |
Distributes any route that has the next hop out of one of the specified interfaces. |
|
match ip next-hop |
Redistributes any route that has a next-hop router address that is passed by one of the specified access lists. |
|
match tag |
Filters routes that match specific route tags. |
show route-tag list
To display information about route tag lists configured on the router, use the show route-tag list command in user EXEC or privileged EXEC mode.
Command Default
If this command is used without the list-name argument, information about all route tag lists configured on the router are displayed.
Usage Guidelines
Use the list-name argument to display information about a specific route tag list. Route tags are 32-bit values attached to routes. They are used to filter routes. You can display route tag values as either plain decimals or dotted decimals. To enable show commands to display route tag values in dotted-decimal format, configure the route-tag notation command in global configuration mode.
Examples
The following sample output from the show route-tag list command displays route tag information in dotted-decimal format. The fields in the display are self-explanatory.
Device# show route-tag list
route-tag-list List1 :
permit 5 1.1.1.1 1.1.1.1
permit 10 2.2.2.2 2.2.2.2
permit 12 3.3.3.3 3.3.3.3
permit 15 4.4.4.4 4.4.4.4
permit 18 6.6.6.6 6.6.6.6
route-tag-list List2 :
permit 5 1.1.1.1 1.1.1.1
permit 10 2.2.2.2 2.2.2.2
permit 12 3.3.3.3 3.3.3.3
permit 15 4.4.4.4 4.4.4.4
permit 18 6.6.6.6 6.6.6.6
traffic-share min
To c onfigure traffic to use minimum-cost routes, when there are multiple routes that have different-cost routes to the same destination network, use thetraffic-sharemincommand in router address family topology or router configuration mode. To disable this function, use the no form of this command.
Command Modes
Router address family topology configuration (config-router-af-topology) Router configuration (config-router)
Command History
|
Release |
Modification |
|---|---|
|
10.0 |
This command was introduced. |
|
11.0(3) |
This command became protocol independent when the across-interfaceskeyword was added. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SRB |
This command was made available in router address family topology configuration mode. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The traffic-sharemin command causes the Cisco IOS software to divide traffic only among the routes with the best metric. Other routes will remain in the routing table, but will receive no traffic. Configuring this command with the across-interfaces keyword allows you to configure multi-interface load splitting on different interfaces with equal-cost paths.
Release 12.2(33)SRB
If you plan to configure the Multi-Topology Routing (MTR) feature, you need to enter the traffic-sharemincommand in router address family topology configuration mode in order for this OSPF router configuration command to become topology-aware.
vccv
To configure the pseudowire Virtual Circuit Connection Verification (VCCV) control channel (CC) type for Multiprotocol Label Switching (MPLS) pseudowires, use the vccv command in the appropriate configuration mode. To disable a pseudowire VCCV CC type, use the no form of this command.
Command Modes
Interface configuration (config-if)
Pseudowire class configuration (config-pw-class)
Template configuration (config-template)
Command History
|
Release |
Modification |
|---|---|
|
15.0(1)S |
This command was introduced. |
|
Cisco IOS XE Release 3.7S |
This command was integrated into a release prior to Cisco IOS XE Release 3.7S. This command was modified as part of the MPLS-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command was made available in interface configuration and template configuration modes in Cisco IOS XE Release 3.7S. |
|
15.3(1)S |
This command was integrated in Cisco IOS Release 15.3(1)S. |
Usage Guidelines
This command was modified as part of the MPLS-based Layer 2 VPN (L2VPN) command modifications for cross-OS support.
When an initiating provider edge (PE) device sends a setup request message to a remote PE device, the message includes VCCV capability information. This capability information is a combination of the CC type and the control verification (CV) type. Use the vccv command to configure the CC type capabilities of the MPLS pseudowire.
If the CV type for the MPLS pseudowire is set to a type that does not use IP/UDP headers, then you must set the CC type to the CC Type 1 control word.
Examples
The following example shows how to configure the MPLS pseudowire class to use CC Type 1:
Device(config)# pseudowire-class bfdclass Device(config-pw-class)# encapsulation mpls Device(config-pw-class)# protocol none Device(config-pw-class)# vccv control-word
The following example shows how to configure the MPLS pseudowire class to use CC Type 1 in interface configuration mode:
Device(config)# interface pseudowire 100 Device(config-if)# encapsulation mpls Device(config-if)# signaling protocol none Device(config-if)# vccv control-word
The following example shows how to configure the MPLS pseudowire class to use CC Type 1 in template configuration mode:
Device(config)# template type pseudowire 100 Device(config-template)# encapsulation mpls Device(config-template)# signaling protocol none Device(config-template)# vccv control-word
Related Commands
|
Command |
Description |
|---|---|
|
bfd-template |
Creates a BFD template and enters BFD configuration mode. |
|
encapsulation (pseudowire) |
Specifies an encapsulation type for tunneling Layer 2 traffic over a pseudowire. |
|
pseudowire-class |
Specifies the name of the pseudowire class and enters pseudowire class configuration mode. |
|
signaling protocol |
Specifies the signaling protocol to be used for signaling labels. |
|
vccv bfd template |
Enables VCCV BFD for a pseudowire class. |
|
vccv bfd status signaling |
Enables status signaling for BFD VCCV. |
vccv bfd status signaling
To enable status signaling for Bidirectional Forwarding Detection (BFD) Virtual Circuit Connection Verification (VCCV), use the vccv bfd status signaling command in the appropriate configuration mode. To disable status signaling, use the no form of this command.
Command Modes
Interface configuration (config-if)
Pseudowire class configuration (config-pw-class)
Template configuration (config-template)
Command History
|
Release |
Modification |
|---|---|
|
15.0(1)S |
This command was introduced. |
|
Cisco IOS XE Release 3.7S |
This command was integrated into a release prior to Cisco IOS XE Release 3.7S. This command was modified as part of the Multiprotocol Label Switching (MPLS)-based L2VPN command modifications for cross-OS support. This command was made available in interface configuration and template configuration modes in Cisco IOS XE Release 3.7S. |
|
15.3(1)S |
This command was integrated in Cisco IOS Release 15.3(1)S. |
Usage Guidelines
Use this command to allow BFD to provide the status signaling functionality that indicates the fault status of an attachment circuit. This command is applicable only for static pseudowires; that is, when the signaling protocol is none.
Examples
The following example shows how to enable VCCV BFD status signaling for a Multiprotocol Label Switching (MPLS) pseudowire class:
Device(config)# pseudowire-class bfdclass Device(config-pw-class)# encapsulation mpls Device(config-pw-class)# protocol none Device(config-pw-class)# vccv control-word Device(config-pw-class)# vccv bfd template bfdtemplate raw-bfd Device(config-pw-class)# vccv bfd status signaling
The following example shows how to enable VCCV BFD status signaling in interface configuration mode:
Device(config)# interface pseudowire 100 Device(config-if)# encapsulation mpls Device(config-if)# signaling protocol none Device(config-if)# vccv control-word Device(config-if)# vccv bfd template bfdtemplate raw-bfd Device(config-if)# vccv bfd status signaling
The following example shows how to enable VCCV BFD status signaling in template configuration mode:
Device(config)# template type pseudowire 100 Device(config-template)# encapsulation mpls Device(config-template)# signaling protocol none Device(config-template)# vccv control-word Device(config-template)# vccv bfd template bfdtemplate raw-bfd Device(config-template)# vccv bfd status signaling
Related Commands
|
Command |
Description |
|---|---|
|
bfd-template |
Creates a BFD template and enters BFD configuration mode. |
|
encapsulation (pseudowire) |
Specifies an encapsulation type for tunneling Layer 2 traffic over a pseudowire. |
|
pseudowire-class |
Specifies the name of the pseudowire class and enters pseudowire class configuration mode. |
|
signaling protocol |
Specifies the signaling protocol to be used for signaling labels. |
|
source template type pseudowire |
Configures the name of a source template of type pseudowire. |
|
vccv |
Configures the pseudowire VCCV CC type for MPLS pseudowires. |
|
vccv bfd template |
Enables VCCV BFD for a pseudowire class. |
vccv bfd template
To enable Virtual Circuit Connection Verification (VCCV) Bidirectional Forwarding Detection (BFD) for a pseudowire class, use the vccv bfd template command in the appropriate configuration mode. To disable VCCV BFD, use the no form of this command.
Command Default
VCCV BFD is disabled for the pseudowire class. The template that is selected by default is raw-bfd.
Command Modes
Interface configuration (config-if)
Pseudowire class configuration (config-pw-class)
Template configuration (config-template)
Command History
|
Release |
Modification |
|---|---|
|
15.0(1)S |
This command was introduced. |
|
Cisco IOS XE Release 3.7S |
This command was integrated into a release prior to Cisco IOS XE Release 3.7S. The command was modified as part of the Multiprotocol Label Switching (MPLS)-based Layer 2 VPN (L2VPN) command modifications for cross-OS support. This command was made available in interface configuration and template configuration modes in Cisco IOS XE Release 3.7S. |
|
15.3(1)S |
This command was integrated in Cisco IOS Release 15.3(1)S. |
Usage Guidelines
Use the bfd-template command to specify the BFD template and settings for the BFD interval values.
VCCV defines two types of encapsulation for VCCV messages to differentiate them from data packets--BFD with IP/UDP headers and BFD without IP/UDP headers.
Support for BFD without IP/UDP headers can be enabled only for pseudowires that use a control word, or a Layer 2 Specific Sublayer (L2SS) that can take the pseudowire associated channel header control word format.
Examples
The following example shows how to enable the BFD template without support for IP/UDP header encapsulation:
Device(config)# pseudowire-class bfdclass Device(config-pw-class)# encapsulation mpls Device(config-pw-class)# protocol none Device(config-pw-class)# vccv control-word Device(config-pw-class)# vccv bfd template bfdtemplate raw-bfd Device(config-pw-class)# vccv bfd status signaling
The following example shows how to enable the BFD template without support for IP/UDP header encapsulation in interface configuration mode:
Device(config)# interface pseudowire 100 Device(config-if)# encapsulation mpls Device(config-if)# Signaling protocol none Device(config-if)# vccv control-word Device(config-if)# vccv bfd template bfdtemplate raw-bfd Device(config-if)# vccv bfd status signaling
The following example shows how to enable the BFD template without support for IP/UDP header encapsulation in template configuration mode:
Device(config)# template type pseudowire template1 Device(config-template)# encapsulation mpls Device(config-template)# Signaling protocol none Device(config-template)# vccv control-word Device(config-template)# vccv bfd template bfdtemplate raw-bfd Device(config-template)# vccv bfd status signaling
Related Commands
|
Command |
Description |
|---|---|
|
bfd-template |
Creates a BFD template and enters BFD configuration mode. |
|
encapsulation (pseudowire) |
Specifies an encapsulation type for tunneling Layer 2 traffic over a pseudowire. |
|
pseudowire-class |
Specifies the name of the pseudowire class and enters pseudowire class configuration mode. |
|
signaling protocol |
Specifies the signaling protocol to be used for signaling labels. |
|
source template type pseudowire |
Configures the name of a source template of type pseudowire. |
|
vccv |
Configures the pseudowire VCCV CC type for MPLS pseudowires. |
|
vccv bfd template |
Enables VCCV BFD for a pseudowire class. |