(no subject)

From: Jason Cash (cash2001@swbell.net)
Date: Thu Aug 14 2003 - 18:09:39 GMT-3


This is odd, I have an ACL to the distance command under OSPF on R5 and R6
(doing mutual
redist. on OSPF /EIGRP):

R2's OSPF RID is 192.168.2.2

router ospf 1
distance 171 192.168.2.2 0.0.0.0 10
access-list 10 permit 192.168.8.8
access-list 10 permit 10.8.1.0 0.0.0.255 access-list 10 permit 10.7.1.0
0.0.0.255 access-list 10 permit 10.7.2.0 0.0.0.255 access-list 10 permit
172.30.80.0 0.0.0.31

I clear the route table on R5 and the routes are correct:

r5#si ei | i EX
D EX 192.168.8.8 [170/307200] via 172.30.200.7, 00:00:21, Ethernet0
D EX 172.30.40.0/24 [170/537600] via 172.30.200.6, 00:00:22, Ethernet0
D EX 172.30.100.0/24 [170/537600] via 172.30.200.6, 00:00:22, Ethernet0
D EX 172.30.80.0/27 [170/307200] via 172.30.200.7, 00:00:21, Ethernet0
D EX 192.168.4.0/24 [170/537600] via 172.30.200.6, 00:00:22, Ethernet0
D EX 10.8.1.0 [170/307200] via 172.30.200.7, 00:00:22, Ethernet0
D EX 10.7.1.0 [170/307200] via 172.30.200.7, 00:00:22, Ethernet0
D EX 10.7.2.0 [170/307200] via 172.30.200.7, 00:00:22, Ethernet0

When I clear the route table on R6, R5's then installs the OSPF routes:
(after clear ip ro * on R6)

23:37:52: RT: no routes to 172.30.40.0
23:37:53: RT: closer admin distance for 10.8.1.0, flushing 1 routes
23:37:53: RT: add 10.8.1.0/24 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 10.7.1.0, flushing 1 routes
23:37:53: RT: add 10.7.1.0/24 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 10.7.2.0, flushing 1 routes
23:37:53: RT: add 10.7.2.0/24 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 192.168.8.8, flushing 1 routes
23:37:53: RT: add 192.168.8.8/32 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 172.30.80.0, flushing 1 routes
23:37:53: RT: add 172.30.80.0/27 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 192.168.4.0, flushing 0 routes
23:37:53: RT: add 192.168.4.0/24 via 172.30.100.2, ospf metric [110/20]
23:37:53: RT: closer admin distance for 172.30.40.0, flushing 0 routes
23:37:53: RT: add 172.30.40.0/24 via 172.30.100.2, ospf metric [110/20]

r5#si ospf | i E2
O E2 192.168.8.8 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 172.30.40.0/24 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 172.30.24.0/24 [110/20] via 172.30.100.2, 00:01:53, Serial0
O E2 172.30.12.0/26 [110/20] via 172.30.100.2, 00:01:53, Serial0
O E2 172.30.80.0/27 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 192.168.4.0/24 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 10.8.1.0 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 10.7.1.0 [110/20] via 172.30.100.2, 00:00:29, Serial0
O E2 10.7.2.0 [110/20] via 172.30.100.2, 00:00:29, Serial0

How can that be? Shouldn't the ditance command adhere permanently?



This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:59 GMT-3