From: Bit Gossip (bit.gossip@chello.nl)
Date: Fri Mar 16 2007 - 18:29:20 ART
Hello Naveen,
very detailed and interesting; my 2 cents:
- Multipoint - point - 2 - multimpoint: 'When LSAs from a DRother is sent to
all others by the DR, the next hop IS modified': there is no DR for this
network type
- Multipoint - Point-2-Multipoint non-broadcast: I think neighbor statement
is necessary in this case
Thanks,
Luca.
----- Original Message -----
From: "Navin MS" <navin_ms07@yahoo.com>
To: "Jeff Mullan" <jmullan78@gmail.com>; "Bit Gossip" <bit.gossip@chello.nl>
Cc: <ccielab@groupstudy.com>
Sent: Friday, March 16, 2007 9:46 PM
Subject: Re: OSPF cheat sheet
> Folks,
>
> I had prepared a similar cheat-sheet which I thought would share with the
group. Should you find
> something wrong, feel free to point it out.
>
> Hope you find it useful.
> Naveen.
>
>
> --- Jeff Mullan <jmullan78@gmail.com> wrote:
>
> > I meant next hop :)
> >
> > On 3/16/07, Jeff Mullan <jmullan78@gmail.com> wrote:
> > >
> > > You might want to add what would be the next hope in all the scenarios
but
> > > point-to-point.
> > > Thanks,
> > > -JM
> > >
> > >
> > > On 3/16/07, Bit Gossip <bit.gossip@chello.nl> wrote:
> > > >
> > > > Hi Group,
> > > > I want to squeeze in one page all the most important factors to
choose
> > > > the
> > > > OSPF network type so that I can stuff it into my long term
memory......
> > > > Any comment is welcome, especially on the compatibility between
network
> > > > types
> > > > Thanks,
> > > > Luca.
> > > >
> > > > Network Type BROADCAST
> > > > Hello to 224.0.0.5
> > > > Hello 10, Dead 40
> > > > DR election: Yes
> > > > Compatible: NON_BROADCAST fixing timers
> > > > NextHop Change: no
> > > > Generate Host Route: no
> > > > Neighbor: not allowed
> > > > best suited for: LAN
> > > >
> > > > Network Type NON_BROADCAST
> > > > Hello to unicast neighbor address
> > > > Hello 30, Dead 120
> > > > DR election: Yes
> > > > Compatible: BROADCAST fixing timers
> > > > NextHop Change: no
> > > > Generate Host Route: no
> > > > Neighbor: necessary
> > > > best suited for: NBMA fully meshed
> > > >
> > > > Network Type POINT_TO_MULTIPOINT
> > > > Hello to 224.0.0.5 even if neighbor is configured
> > > > Hello 30, Dead 120
> > > > DR election: no
> > > > Compatible: p2mp non-broadcast, p2p
> > > > NextHop Change: Yes
> > > > Generate Host Route: Yes
> > > > Neighbor: not necessary but allowed to change the cost
> > > > best suited for: NBMA partially meshed, hub and spoke
> > > >
> > > > Network Type POINT_TO_MULTIPOINT non-broadcast
> > > > Hello to unicast neighbor address
> > > > Hello 30, Dead 120
> > > > DR election: no
> > > > Compatible: p2mp, p2p
> > > > NextHop Change: Yes
> > > > Generate Host Route: Yes
> > > > Neighbor: necessary
> > > > best suited for: NBMA partially meshed, hub and spoke
> > > >
> > > > Network Type POINT_TO_POINT
> > > > Hello to 224.0.0.5
> > > > Hello 10, Dead 40
> > > > DR election: no
> > > > Compatible: p2mp fixing timers
> > > > NextHop Change: n/a (only 2 router on the network)
> > > > Generate Host Route: no
> > > > Neighbor: not allowed
> > > > best suited for: ppp, hdlc, p2p fr sub-if
> > > >
> > > >
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:51 ART