From: Vijay Venkatesh (vijay.venkatesh@xxxxxxx)
Date: Wed Jan 03 2001 - 20:55:34 GMT-3
yes this is resolved thanks. I am stupid. after like 4 hrs on this
I finally did a wri erase on the local r6 and cut ans paste the same
config back and it worked fine. My guess the virtual link was not
happy and had just to be reconfigured.
Vijay
"BUI, TIN T (SBCSI)" wrote:
>
> Did you get this problem resolved? Please post results. Just some
> comments:
>
> * A virtual link is really just an extension of area 0 so there should not
> be any problem with seeing loopback 0. Router id is always the highest ip
> of router. Loopback will be looked first before other ip addresses. One
> problem I've seen is that once a router id has been established, and then
> you add a loopback, that loopback will not be your router id until you
> reload router. Some admins might not realize this so they try to use router
> id of loopback for rid when it's not in effect yet (reboot would make it
> work again). I have also seen the reverse where a person adds loopback 1 to
> router so router id changed to loopback1 when router gets rebooted next time
> which really mess things up especially if you are using virtual links.
> * Make sure that when you do show ip ospf vir that your hello and dead
> timers are same.
> * Check to make sure you do not have a routing loop. Are you doing
> redistribution of any routing protocols? If so, try putting filter to
> prevent that loopback from being redistributed just to test this.
>
> > Tin T. Bui
> > Senior Network Manager
> > Network Management Center
> > SBC Services Inc.
> > 7337 Trade Street, Rm 1110
> > San Diego, Ca 92121
> > Office #: 858-886-4644/858-886-4589
> > Pager #: 858-494-0482
> > Fax #: 858-549-4103
> > Email: tb4565@sbc.com
> >
>
> -----Original Message-----
> From: Johnny Gorham [mailto:jgorham@cisco.com]
> Sent: Wednesday, January 03, 2001 6:41 AM
> To: Vijay Venkatesh
> Cc: chrish@bjen.com; ccielab@groupstudy.com
> Subject: Re: OSPF virtual-link question
>
> I did something very similar on yesterday and reload of all routers was my
> friend.
>
> Vijay Venkatesh wrote:
>
> > Yes yes I have all this setup fine. When I do a sh ip ospf data on r8
> > the network 150.150.100.0/24 shows as a summary as lsa 5. But it does
> > not put this into the routing routing table. r6 sees this network fine
> > with a /32. Debugs are useless and not really informative. The virt
> > link is up and I see all routes on r8 except for this one network.
> > ANy thoughts ?
> > Vijay
> >
> > ChrisH wrote:
> > >
> > > OSPF area 100 and 20 connect directly to Area 0. Area 10 needs to go
> through
> > > Area 100 to get to Area 0. Therefore, you should have a statements that
> > > looks like:
> > >
> > > R6:
> > > area 100 virtual-link x.x.x.x( R1's RID)
> > >
> > > R1:
> > > area 100 virtual-link y.y.y.y (R6's RID)
> > >
> > > In R3, I assume that you have something that looks like:
> > >
> > > router ospf 100
> > > network 150.150.100.1 0.0.0.0 area 20
> > >
> > > I am not aware of any IOS bugs related to this issue.
> > >
> > > Chris
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > > Vijay Venkatesh
> > > Sent: Tuesday, January 02, 2001 9:08 PM
> > > To: ccielab@groupstudy.com
> > > Subject: OSPF virtual-link question
> > >
> > > Here is the situation
> > >
> > > r8 ---- r6 ------r1----r3 ---- network 150.150.100.1/24 (loop 0)
> > >
> > > Between r1 and r3 is area 0
> > > between r6 and r1 is area 100
> > > between r8 and r6 is area 10
> > > r3's loop 0 is in area 20
> > >
> > > area 100 has a ospf virt link between r6 and r1
> > > The ospf virt link is up
> > >
> > > The problem
> > > -----------
> > > r3's loop0 is 150.150.100.1/24 and is in area 20. I can every network
> > > on r8 except for the 150.150.100.1 network. What is the problem ? Is
> > > there something special when sending loopbacks across virtual links ?
> > > Is this an IOS issue ?
> > >
> > > Router versions
> > > ---------------
> > > all routers are running 11.2.19 IOS
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:22 GMT-3