[Contents] [Prev] [Next] [Index] [Report an Error]

Creating Table Maps

For static routes and access routes, you can configure and apply a table map that filters routes before an access list adds them to the routing table. For static routes, you can use the ip static-route table-map or ipv6 static-route table-map command. For access routes, you can use the ip access-route table-map or ipv6 access-route table-map command.

Use these commands when triggering on the policy values listed in Table 4.

Table 4: Match and Set Policy Values

Match	Set
ip address	metric
metric	distance
distance	tag
tag

For example, you can configure an access list and route map to filter, based on IP address, any routes that appear in the routing table:



host1(config)#ip access-route table-map just10net 

host1(config)#access-list permit10 permit
10.0.0.0 0.255.255.255 

host1(config)#access-list permit10 deny any 

host1(config)#route-map just10net 

host1(config-route-map)#match ip address permit10

Using the same name for both the table map and the route map creates an association specifying (in this case) that only IP addresses that match the access list criterion appear in the routing table.

ip access-route table-map

ipv6 access-route table-map

Use to filter access routes before an access list adds them to the routing table.
Example 1host1(config)#ip access-route table-map just10net
Example 2host1(config)#ipv6 access-route table-map map2
Use the no version to delete the table map.
See ip access-route table-map.
See ipv6 access-route table-map.

ip static-route table-map

ipv6 static-route table-map

Use to filter static routes before adding them to the routing table.
Example 1host1(config)#ip static-route table-map map3
Example 2host1(config)#ipv6 static-route table-map map4
Use the no version to delete the table map.
See ip static-route table-map.
See ipv6 static-route table-map.

[Contents] [Prev] [Next] [Index] [Report an Error]