From: Denise Donohue (fradendon@xxxxxxxxxxx)
Date: Tue May 14 2002 - 22:26:22 GMT-3
If you really want to get rid of it, reload the router. Otherwise, just
wait a while. The wrong one will go away eventually. And it shouldn't hurt
your routing. But then, I always clear the OSPF processes to change the
router ID - I've never taken off OSPF and then put it back.
-----Original Message-----
From: Khurram Khani [mailto:kkhani@nortelnetworks.com]
Sent: Tuesday, May 14, 2002 9:13 PM
To: fradendon@comcast.net; Khurram Khani
Cc: ccielab@groupstudy.com
Subject: Re: OSPF Question - Entries not invalidating in LSDB
Hi Denise -
As specified in the last message LSDB gets cleaned after removing router
ospf
and pasting it back but after establishing the adjacency "NEIGHBOR" is
sending
the "OLD ROUTER-ID" back in DDs Exchnage.
And i see two entries:
* New Router-ID + Old Router-ID both in OSPD Database
Link ID ADV Router Age Seq# Checksum Link count
1.160.240.99 1.160.240.99 988 0x80000117 0x9F31 3 ---->
invalid entry !!!! (incorrect)
160.160.160.1 160.160.160.1 609 0x80000003 0xDE2D 3 ----->
New one (correct)
----- Original Message -----
From: "Denise Donohue" <fradendon@comcast.net>
To: "Khani, Khurram [INGO1:8851:EXCH]" <kkhani@americasm06.nt.com>
Sent: Tuesday, May 14, 2002 5:54 PM
Subject: RE: OSPF Question - Entries not invalidating in LSDB
> Reloading the router should get rid of the old database info. Also, you
> don't need to remove OSPF to change the router ID - just "clear ip ospf
> process" at the enable prompt.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Khurram Khani
> Sent: Tuesday, May 14, 2002 7:53 PM
> To: ccielab@groupstudy.com
> Subject: OSPF Question - Entries not invalidating in LSDB
>
>
> Folks,
>
> I have a Router in Area 100. Original OSPF Router-ID was 1.160.240.99
> I created a new loopback10 on this router assigned ip 160.160.160.1 to the
> loopback interface 10 on this Router. Removed "router ospf 1" command
from
> the
> Router and pasted it back so that Router can select new Loopback ID.
> It came up fine with new OSPF Router-ID 160.160.160.1. When it
established
> the adjacency with its neighbour and state went to FULL. I can see the
old
> Router-ID
> still in OSPF LSDB (Database)
>
> Router Link States (Area 100)
>
> Link ID ADV Router Age Seq# Checksum Link count
> 1.160.240.99 1.160.240.99 988 0x80000117 0x9F31
---->
> invalid entry !!!!
> 10.160.240.10 10.160.240.10 609 0x800000B9 0x4C5 1
> 160.160.160.1 160.160.160.1 609 0x80000003 0xDE2D 3 ----->
> changed Router ID from 1.160.240.99 to 160.160.160.1
>
> Putting the protocol analyzer on the link, I found that actually the
> neighbour sends during DDs
> Exchange neighbour is sending that LSA as part of DDB update, and then my
> Router sends out a
> LSR to get full update.
>
> My question is , how to cleanup OSPF Database and when these entries will
> age out in database???
>
> Below is my LSDB dump
>
>
> Cisco2500-1#sh ip os da
>
> OSPF Router with ID (160.160.160.1) (Process ID 1)
>
>
> Router Link States (Area 100)
>
> Link ID ADV Router Age Seq# Checksum Link count
> 1.160.240.99 1.160.240.99 988 0x80000117 0x9F31
---->
> invalid entry !!!!
> 10.160.240.10 10.160.240.10 609 0x800000B9 0x4C5 1
> 160.160.160.1 160.160.160.1 609 0x80000003 0xDE2D 3 ----->
> changed Router ID from 1.160.240.99 to 160.160.160.1
>
> Net Link States (Area 100)
>
> Link ID ADV Router Age Seq# Checksum
> 48.0.0.1 10.160.240.10 610 0x80000038 0x4F54
>
> Summary Net Link States (Area 100)
>
> Link ID ADV Router Age Seq# Checksum
> 90.90.2.0 10.160.240.10 572 0x800000AE 0x1D15
>
> Type-5 AS External Link States
>
> Link ID ADV Router Age Seq# Checksum Tag
> 25.0.0.0 160.160.160.1 648 0x80000001 0xCDE9 0
> 25.0.1.0 160.160.160.1 648 0x80000001 0xC2F3 0
> 25.0.2.0 160.160.160.1 648 0x80000001 0xB7FD 0
> 134.0.0.0 10.160.240.10 573 0x800000AC 0x25AD 0
> Sonic2500-1#
>
>
>
> config dump
>
>
> Sonic2500-1#sh run
> Building configuration...
>
> Current configuration:
> !
> version 11.2
> no service password-encryption
> no service udp-small-servers
> no service tcp-small-servers
> !
> hostname Sonic2500-1
> !
> enable secret 5 $1$ZyJJ$Iz6rBgFfa2bHITTJHHTAK1
> !
> ip subnet-zero
> !
> interface Loopback0
> ip address 1.160.240.99 255.255.255.255
> !
> interface Loopback1
> ip address 160.160.160.1 255.255.255.0
> !
> interface Loopback10
> ip address 78.78.78.1 255.255.255.0
> !
> interface Ethernet0
> ip address 48.0.0.2 255.255.255.0
> !
> interface Ethernet1
> ip address 10.160.240.99 255.255.255.0
> ip ospf priority 255
> !
> interface Serial0
> no ip address
> shutdown
> !
> interface Serial1
> no ip address
> shutdown
> !
> router ospf 1
> redistribute static metric 1 subnets route-map range
> network 48.0.0.0 0.0.0.255 area 100
> network 160.0.0.0 0.255.255.255 area 100
> network 78.0.0.0 0.255.255.255 area 100
> !
> no ip classless
> ip route 0.0.0.0 0.0.0.0 10.160.240.1
> ip route 25.0.0.0 255.255.255.0 Loopback10
> ip route 25.0.1.0 255.255.255.0 Loopback10
> ip route 25.0.2.0 255.255.255.0 Loopback10
> ip route 134.177.211.0 255.255.255.0 10.160.240.1
> access-list 1 permit 25.0.0.0 0.255.255.255
> access-list 101 permit ip 25.0.0.0 0.255.255.255 any log
> route-map range permit 10
> match ip address 1
> !
> bridge 1 protocol ieee
> !
> line con 0
> line aux 0
> line vty 0 4
> password rwa
> login
> !
> end
>
> Sonic2500-1#
>
>
>
> Sonic2500-1#
> Sonic2500-1#sh ip os ne
>
> Neighbor ID Pri State Dead Time Address
Interface
> 10.160.240.10 1 FULL/DR 00:00:34 48.0.0.1
Ethernet0
> Sonic2500-1#
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:56 GMT-3