From: Sila Moni (silamoni@yahoo.com)
Date: Sat Jul 09 2005 - 09:52:29 GMT-3
There are two issues that I see from this scenario.
1. Typically, you would use the neighbor statement on
the hub. Since it is on R3 (spoke), it will create
some problems. Are you allowed to put the neighbor
statement on R4 as well?
2. P-T-M non-broadcast is used in NBMA with virtual
circuits of differing speeds (e.g. ISDN and FR).
Here, assigning cost to the neighbor is optional.
--- Amit Jain <netsteps@rediffmail.com> wrote:
> Hi
>
> In the task, R3 and R5 are connected through frame
> relay and R4 and R5 through
> ISDN
>
> R3
> -
> -
> - FR -
> -
>
> R4 - -ISDN - - R5
>
> Now the ospf area 345 is running on FR and ISDN
> links and network type
> non-broadcast between R3 and R5, with neighbor
> command on R3.
> Task requirement is to configure all adjacencies in
> area 345 in such a manner
> that other devices on segment cannot recieve OSPF
> hello packets.
> The solution given is that the network type on ISDN
> and FR segment be changed
> to point-to-multipoint (with ofcourse neighbor
> statements)
>
> My ques is why we need to change it to
> point-to-multpoint from non-broadcast
> on FR segment ? When the netwrk type is
> non-broadcast we are sending packets
> as unicast only, so why specifically change to
> p-to-multipoint ?? (Only
> difference will be no DR/BDR elec and host route)
>
> Also the ISDN segment is network type point-to-point
> so anyways the hello
> packets will only go to the other side ?? What am i
> missing.
>
> Could not get the answer from IE website posts.
>
> Thanks
> Amit Jain
>
>
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3