From: Edward Monk (edmonk@xxxxxxxxx)
Date: Mon Jul 22 2002 - 15:16:28 GMT-3
I am having trouble with setting the precedence on a local policy
route-map. When I try to set the precedence to any value it is rejected.
If I take out the set precedence value and instead set the next-hop in
the route-map it matches the access-list (just like with set ip
precedence )and is routed per route-map (unlike precedence). Is there
something obvious I am missing here?
Below are the outputs with the route-map and the appropriate debugs. My
access-list permits ip any any. I have tried to specify source and
destination in access-list but the results are the same.
R13#sh route-map
route-map r13_local, permit, sequence 10
Match clauses:
ip address (access-lists): 150
Set clauses:
ip next-hop 172.16.134.4
Policy routing matches: 120 packets, 10620 bytes
R13#ping 172.16.100.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.100.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 116/119/124
ms
R13#
23:59:13: IP: s=172.16.13.1 (local), d=172.16.4.1, len 40, policy match
23:59:13: IP: route map r13_local, item 10, permit
23:59:13: IP: s=172.16.13.1 (local), d=172.16.4.1 (FastEthernet0/0), len
40, policy routed
23:59:13: IP: local to FastEthernet0/0 172.16.134.4
R13#sh route-map
route-map r13_local, permit, sequence 10
Match clauses:
ip address (access-lists): 150
Set clauses:
ip precedence internet
Policy routing matches: 133 packets, 11625 bytes
R13#ping 172.16.100.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.100.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 117/120/125
ms
R13#
1d00h: IP: s=172.16.134.13 (local), d=172.16.100.6, len 100, policy
match
1d00h: IP: route map r13_local, item 10, permit
1d00h: IP: s=172.16.134.13 (local), d=172.16.100.6, len 100, policy
rejected -- normal forwarding
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:39 GMT-3