[c-nsp] OSPF router gets separated from a broadcast domain
Gabor Ivanszky
ivanszky at niif.hu
Wed Jan 30 01:15:44 EST 2008
Hi Peter, all,
thanks for all the responses!
After thinking over the situation first(days ago), I also came to the
same conclusion, so we solved the issue through design. I was just
curious whether there is any "nice" solution possible in the framework
of routing protocols. It seemed so improbable that there is no standard
way to solve a common situation like this.
Now I understand that there is no straightforward solution possible, so
this kind of situation must be a voided.
thanks again,
Gabor
Peter Rathlev wrote:
> I can't see how you could avoid this problem. If you have the following:
>
> Host1 Host2
> v v
> RTR-A <-> SW-A <-> SW-B <-> RTR-B
>
> and you break the link between SW-A and SW-B, what would you suggest
> would determine if RTR-A or RTR-B is the "correct" one to announce the
> net? You have a scenario called "segmentation", and there's no easy
> resolution.
>
> If there are no "Host1"s you use SW-A as a simple bridge, a little like
> using an IMC McBasic media converter, and then you need some "poisoning"
> feature, like their "LinkLoss".
>
> If you have both "Host1"s and "Host2"s, which ones would you like to not
> have any connection to the outside world?
>
>
More information about the cisco-nsp
mailing list