From: Erick B. (erickbe@xxxxxxxxx)
Date: Fri Feb 23 2001 - 04:12:28 GMT-3
It also has to be the RID for the ABR for that area,
which may not be router it is between. This is one
thing people overlook. If you look at the show ip ospf
commands it will report the RID there that is
advertising. Reload or remove/add the OSPF process
back to make sure the RID doesn't change after a
reload because of a new higher IP address somewhere,
etc.
--- "Daniel M. Dawson" <dandawson@lucent.com> wrote:
> I think your problem is that the IP addresses that
> your put on the command
> line after the virtual-link keyword has to be the
> OSPF router ID not just
> any interface.
>
> Daniel M. Dawson
> Member Consulting Staff
> Lucent Worldwide Services
> Lucent Technologies
> Mobile: (405) 850-1493
> Pager: (800) 622-9202
> E-mail: dandawson@lucent.com
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of
> Devon Watkins
> Sent: Thursday, February 22, 2001 10:13 PM
> To: ccielab@groupstudy.com
> Subject: OSPF virtual link
>
>
> Group,
>
> I am working on OSPF virtual links. In the past I
> had thought was fairly
> easy, but now I have a problem that has me stumped.
>
> Here is what I have:
>
> Rtr 1 has an ethernet link in area 1
> Rrt 2 has an ethernet link in area 1 also
> Rtr 2 has a link in area 0
>
> so far so good, but then...
> I add a serial interface on Rtr 1 to area 2 and add
> the following config
> info:
>
> rtr 1
>
> area 1 virtual-link <pingable ip on rtr 2, in area
> 0>
>
> rtr 2
>
> area 1 virtial-link <ip interface of serial
> interface in area 2 of rtr1 (is
> pingable)>
>
> Any idea of what I am screwing up?
>
> Thanks
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:58 GMT-3