Cisco IOS Access Lists

Debugging route maps and BGP

Debugging route maps is very similar to debugging access lists for routing policies since both deal with manipulating routes. For the most part, the same techniques I covered with routing access lists can be used to find problems with route maps. There are, however, some problems and commands unique to working with route maps, and I discuss these in this section.

First of all, you need to know the most convenient way to see the contents of route maps and AS-path access lists. While showing the running configuration shows you all your route maps, this may be time-consuming if you have a long configuration. The show route-map command prints out all your route maps. When followed by a route map name, a specific route map is displayed. Recall the route map I created called ROUTES-OUT:

route-map ROUTES-OUT permit 10
 match ip address 1
 set metric 10
route-map ROUTES-OUT permit 20
 match ip address 2
 set metric 20

The show route-map output of this route map looks like this:

Router1>show route-map ROUTES-OUT
route-map ROUTES-OUT, permit, sequence 10
  Match clauses:
    ip address (access-lists): 1
  Set clauses:
    Metric 10
  Policy routing matches: 0 packets, 0 bytes
route-map ROUTES-OUT, permit, sequence 20
  Match clauses:
    ip address (access-lists): 2
  Set clauses:
    Metric 20
  Policy routing matches: 0 packets, 0 bytes

The output divides each route map entry into match and set clauses. The policy route matches should be ignored when looking at route maps for BGP.

AS-path ...