From: Curtis Phillips (cphillips@xxxxxxxxxxxx)
Date: Sun Mar 10 2002 - 13:53:44 GMT-3
The router id will be the loopback addresses.
they do not have to be in the routing table to be used
as virtual address targets. They are advertised in neighbor
messages and LSAa anyway.
If your router id is the loopback, you must use the loopbacks as virtual
link entries
----- Original Message -----
From: "Carl Phelan" <carlphelan@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, March 10, 2002 11:15 AM
Subject: OSPF Virtual Links
> Hi All,
>
> I am having problems establishing virtual links in OSPF as follows:
>
> R2 has a loopback not configured in a routing protocol and has S0 in
> area 0 and e0 in area 1, R4 has its e0 in area 1 also and has neighbored
> with R2 in area 1. R2 has a loopback address in area 55. I need to
> create a virtual link over area 1 for area 55 as it is not physically
> connected to area 0. The router-ids for both R2 and R4 is of course the
> loopbacks but I cannot specify these in the virtual links as they cannot
> be seen by either router so I have created the virtual link as follows:
>
> R2
> .
> Area 1 virtual-link 135.14.220.2 (e0 on R4)
>
> R4
> ..
> Area 1 virtual-link 135.14.220.1 (e0 on R2)
>
> But this does not work. Must I include R2's loopback into OSPF as this
> is the router-id? I would rather not and would also try and avoid
> manually changing the router-id with that command.
>
> Any ideas?
>
> Many thanks,
>
> Carl
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:58 GMT-3