show route-map

To display a route map, use the show route-map command in Privileged EXEC mode.

Example: The following shows example CLI display output for the command.

(Routing) # show route-map test
route-map test, permit, sequence 10
     Match clauses:
       ip address prefix-lists: orange
     Set clauses:
       set metric 50

Example: The following example shows a route map, test1, that is configured with extended community attributes:

(R1) # show route-map test
route-map test1, permit, sequence 10
     Match clauses:
       extended community list1
     Set clauses:
       extended community RT:1:100 RT:2:200

Example: With the inclusion of policy-based routing, more match and set clauses are added. For each sequence number, match count is shown in terms of the number of packets and number of bytes. This counter displays match count in packets and bytes when the route-map is applied. When a route-map is created/removed from interface, this count is shown to be zero. The following example shows the behavior of counters along with how they are displayed when a route-map is applied and removed from an interface:

(Routing) #show route-map simplest

route-map simplest permit 10
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip next-hop 3.3.3.3
       ip precedence 3
Policy routing matches: 0 packets, 0 bytes
route-map simplest permit 20
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip default next-hop 4.4.4.4
       ip precedence 4
Policy routing matches: 0 packets, 0 bytes
route-map simplest permit 30
     Match clauses:
     Set clauses:
       interface null0
Policy routing matches: 0 packets, 0 bytes
(Routing) #
(Routing) #configure

(Routing) (Config)#interface 0/2

(Routing) (Interface 0/2)#ip policy simplest

(Routing) (Interface 0/2)#show route-map simplest

route-map simplest permit 10
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip next-hop 3.3.3.3
       ip precedence 3
Policy routing matches: 5387983 packets, 344831232 bytes
route-map simplest permit 20
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip default next-hop 4.4.4.4
       ip precedence 4
Policy routing matches: 0 packets, 0 bytes
route-map simplest permit 30
     Match clauses:
     Set clauses:
       interface null0
Policy routing matches: 0 packets, 0 bytes
(Routing) (Interface 0/2)#
(Routing) (Interface 0/2)#no ip policy simplest

(Routing) (Interface 0/2)#exit

(Routing) (Config)#exit

(Routing) #show route-map simplest

route-map simplest permit 10
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip next-hop 3.3.3.3
       ip precedence 3
Policy routing matches: 0 packets, 0 bytes
route-map simplest permit 20
     Match clauses:
       ip address (access-lists) : 1
     Set clauses:
       ip default next-hop 4.4.4.4
       ip precedence 4
Policy routing matches: 0 packets, 0 bytes
route-map simplest permit 30
     Match clauses:
     Set clauses:
       interface null0
Policy routing matches: 0 packets, 0 bytes

Example: The following output shows an example of the command when the specified route map is IPv6-based.

(dhcp-10-130-84-138)#show route-map

route-map rm6 permit 10
     Match clauses:
       ipv6 address (access-lists) : acl6
     Set clauses:
       ipv6 next-hop 3001::2 2001::2 5001::2 6001::2
       ipv6 next-hop interface fe80::200:6bff:fee4:35a, via 3/3
Policy routing matches: 0 packets, 0 bytes

route-map rmdef permit 10
     Match clauses:
       ipv6 address (access-lists) : acl6
     Set clauses:
       ipv6 default next-hop 1001::2
       ipv6 default next-hop interface fe80::200:6bff:fee4:35a, via 3/3
Policy routing matches: 0 packets, 0 bytes