just a little addition to what Edison had alread written.
With point-to-multipoint non-broadcast the neighbor statement is required and accepts a cost option.
With this network type a per-neighbor cost can be specified, whereas in the point-to-multipoint network type the cost is the usual outgoing OSPF interface cost so all neighbors are seen at the same cost.
The reason for this is when PVCs with different bandwidth parameters lead to two or more remote routers you can provide a preferred path without using two different interfaces or subinterfaces.
So this is how it works if I understood it correctly.
ip ospf network non-broadcast (default)
- elects DR/BDR
- requires neighbor command to establish adjacency
- does not multicast hello but rather unicasts
ip ospf network point-to-multipoint
- does not elect DR/BDR
- multicasts hellos to establish neighbor adjacency
ip ospf network point-to-multipoint non-broadcast
- does not elect DR/BDR
- does not multicast hellos and neighbor command is required to establish adjacency. utilizes unicast as hello.
The "ip ospf network" command only applies for ospf hellos and adjacency and also determines if there will be a DR/BDR. This is completely different with frame-relay map ip broadcast keyword right? Thanks for all your replies.
Thank you Sir Edison. What about the other things that I just wrote? Are they correct?
In a point-to-multipoint configuration where neighbor command is not needed, you will need to specify frame-relay map ip broadcast command since neighbor command is not necessary. By configuring frame-relay map ip broadcast, the multicast hellos of OSPF will be able to cross the link.
In point-to-multipoint non-broadcast, even if the broadcast keyword is in place in the frame-relay map ip command, OSPF hellos will not be sent right?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...