show route-map

Displays route-map configuration details.

Syntax

show route-map [ name ]

show route-map interface [ ethernet slot/port | port-channel index | ve ve-number ]

Parameters

name: Specifies the name of the route-map.
interface: Specifies an interface.
ethernet slot/port: Specifies a physical interface.
port-channel index: Specifies a port-channel.
ve ve-number: Specifies a virtual Ethernet interface.

Modes

Privileged EXEC mode

Output

The show route-map command displays the following information:


Output field	Description
Active/Inactive	Indicates the instantiation of the route-map configuration into the underlying hardware. Possible meanings for inactive may be no room in the TCAM for programming the ACL, or the exhaustion of next-hop entries within the hardware next-hop table.
Selected	Indicates which of the configured next hops is currently being used by the policy. If the keyword selected is absent from the display, it indicates that none of the next hops in the list is being used and the packet is being routed by the standard routing mechanism.
Policy routing matches	Provides a summary of the number of times any of the match criteria within the specific ACL have been hit. If the ACL binding was unable to allocate a counter for the ACL (due to resource exhaustion) the count value will show "Counter not available" otherwise an actual counter value will be displayed.

Examples

The following example displays route-map details for all route-maps.

device# show route-map
Interface Ethernet 1/6
 ip policy route-map route1

The following example displays route-map details for a specific route-map.

device# show route-map route1
Interface Ethernet 1/6
ip policy route-map route1 permit 1 (Active)
    match ip address acl test1
    set ip next-hop 6.0.0.1 (selected) (recursive)
       next-hop 10.10.10.1            
    Policy routing matches: 1443 packets

The following example displays route-map details on a specific interface.

device# show route-map interface ethernet 1/6
Interface Ethernet 1/6
ip policy route-map route1 permit 1 (Active)
    match ip address acl test1
    set ip next-hop 6.0.0.1 (selected) (recursive)
       next-hop 10.10.10.1            
    Policy routing matches: 1543 packets

The following example displays the route map configuration from the running configuration.

SLX# show running-config route-map r1
route-map r1 permit 10
   match ip address acl test1
   next-hop-recursion
   set ip next-hop 4.4.4.4         
!
SLX#

The following example displays the configured route-maps.

SLX# show route-map
Interface Ethernet 0/17
   ip policy route-map r1
SLX#

The following example shows the information for a particular route map. This example also shows that recursive next hop resolution is enabled on the route map.

SLX# show route-map r1
Interface Ethernet 0/17
ip policy route-map r1 permit 10 (Active)
    match ip address acl test1
    set ip next-hop 4.4.4.4 (selected) (recursive)
        next-hop 10.10.10.1
    Policy routing matches: 0 packets    Note: Counter values are partial

The following example shows the route map configured on a particular interface. This example also shows that recursive next hop resolution is enabled on the route map. In the below output, 10.10.10.1 is the actual IPv4 next-hop for the recursive route and 2002:db1:0:0:0:ee00:41:2222 the actual IPv6 next-hop.

SLX# show route-map interface eth 0/17
Interface Ethernet 0/17
ip policy route-map r1 permit 10 (Active)
    match ip address acl test1
    set ip next-hop 4.4.4.4 (selected) (recursive)
        next-hop 10.10.10.1
    Policy routing matches: 1543 packets    Note: Counter values are partial
SLX#
SLX# show route-map interface eth 0/18
Interface Ethernet 0/18
ip policy route-map r2 permit 10 (Active)
    match ip address acl test1
    set ip next-hop 2001:db8:0:0:0:ff00:42:1111 (selected) (recursive)
        next-hop 2002:db1:0:0:0:ee00:41:2222
    Policy routing matches: 1543 packets    
SLX#