From: Ryan Hoffman (ryan.hoffman@xxxxxxxxx)
Date: Wed Sep 06 2000 - 11:09:36 GMT-3
Have the following topology:
e0 e1 e0 e0
2514 ----- 4000 ----- 2514
r9 r11 r10
Build initially with two processes, 2 between r9&r11, 1 btwn r11&r10.
Redistributed 2 into 1.
Then combined into one process, 2 by moving network statement on r11 from
one process to the other.
r10 initially had two adjacencies on it's e0, for different IPs of r11. It
quickly determined only one was valid. However, it kept in it's database
EX2 routes from the old redistribution for r9 loopback networks.
ex:
r10#sh ip ospf database external 192.168.1.0
OSPF Router with ID (192.168.2.2) (Process ID 1)
Type-5 AS External Link States
LS age: 1800
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 192.168.1.0 (External Network Number )
Advertising Router: 192.168.2.1
LS Seq Number: 80000003
Checksum: 0xAC24
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 11
Forward Address: 0.0.0.0
External Route Tag: 0
Yet as part of the new process it sees these as IA routes:
r10#sh ip route 192.168.1.0
Routing entry for 192.168.1.0/24
Known via "ospf 1", distance 110, metric 21, type inter area
Redistributing via ospf 1
Last update from 192.168.2.1 on Ethernet0, 00:17:46 ago
Routing Descriptor Blocks:
* 192.168.2.1, from 192.168.0.129, 00:17:46 ago, via Ethernet0
Route metric is 21, traffic share count is 1
Is there a way to flush these old routes from the database?
I'm assuming I have to remove the ospf process on all routers, then bring
things up clean. Hoping there's an easier way though.
The LS Age is increasing on them. Will this grow to a point where they
expire?
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:52 GMT-3