From: ccie2be (ccie2be@nyc.rr.com)
Date: Tue Jan 11 2005 - 09:50:02 GMT-3
Oliver,
You are right.
There's no DR or BDR election for network type
point-to-multipoint or
point-to-multipoint non-broadcast
Rack1R4#sh ip os n det
Neighbor 150.1.5.5, interface address 130.1.45.5
In the area 345 via interface BRI0/0
Neighbor priority is 0, State is FULL, 6 state changes
DR is 0.0.0.0 BDR is 0.0.0.0 <--
no Dr or BDR
Options is 0x72
LLS Options is 0x1 (LR)
Neighbor is up for 00:03:42
Index 1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Rack1R4#
I knew that was true for p2m but wasn't sure about p2m non-broadcast, but
as you can see from above output, that's
true for both types of p2m network types.
One thing to note:
When you do a show ip ospf int, the network type shows
point-to-multipoint regardless of whether the non-broadcast keyword isused.
Tim
----- Original Message -----
From: "Oliver Grenham" <ogrenham@optusnet.com.au>
To: "ccie2be" <ccie2be@nyc.rr.com>; <steve.skinner@uk.pwc.com>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, January 11, 2005 8:38 AM
Subject: Re: osfp over isdn using unicasts
> an ospf interface that is set is point-to-multipoint does not elect a
> designated router or a backup designated router so dont believe priority
> will do much to make this work.
>
> Ollie.
> ----- Original Message -----
> From: "ccie2be" <ccie2be@nyc.rr.com>
> To: <steve.skinner@uk.pwc.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Tuesday, January 11, 2005 6:44 PM
> Subject: Re: osfp over isdn using unicasts
>
>
> > Actually, I haven't but I wouldn't think that would be
> >
> > needed as I hard-coded the router-id on each side.
> >
> > Did you find priority needs to be changed to make this work?
> >
> > Thanks
> > ----- Original Message -----
> > From: <steve.skinner@uk.pwc.com>
> > To: "ccie2be" <ccie2be@nyc.rr.com>
> > Cc: <ccielab@groupstudy.com>
> > Sent: Tuesday, January 11, 2005 4:40 AM
> > Subject: Re: osfp over isdn using unicasts
> >
> >
> > >
> > > Hi ,
> > >
> > > have you tried changing the priority on one end of the link ...
> > >
> > > i.e ip ospf priority 0
> > >
> > > HTH
> > >
> > > Stephen Skinner
> > >
> > >
> > >
> > >
> > >
> > > "ccie2be"
> > > <ccie2be@nyc.rr.com To: "Group Study"
> > <ccielab@groupstudy.com>
> > > > cc:
> > > Sent by: Subject: osfp over
isdn
> > using unicasts
> > > nobody@groupstudy.c
> > > om
> > >
> > >
> > > 11/01/2005 04:14
> > >
> >
> > >
> > >
> > > Please respond to
> > > "ccie2be"
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi guys,
> > >
> > > Has anyone gotten this to work?
> > >
> > > This is from IEWB lab 15, task 5.21.
> > >
> > > According to IE, the config should be fairly simple and like this:
> > >
> > >
> > > R4
> > > int bri 0/0
> > > ip ospf network point-to-multipoint non-broadcast
> > > dialer map ip 130.1.45.5 name ROUTER5 5555
> > >
> > > ROUTER OSPF 1
> > > net 130.1.45.0 0.0.0.255 area 345
> > > neighbor 130.1.45.5
> > >
> > > R5
> > >
> > > int bri 0/0
> > > ip ospf network point-to-multipoint non-broadcast
> > > dialer map ip 130.1.45.4 name ROUTER5 4444
> > >
> > > ROUTER OSPF 1
> > > net 130.1.45.0 0.0.0.255 area 345
> > >
> > >
> > > Before changing to the above the config, I had established an ospf
> > > adjacency
> > >
> > > between R4 and R5. But, once I changed the config to the above,
> > >
> > > the ospf adjacency flapped between down and init.
> > >
> > > Any one have any ideas on what is needed to make this work.
> > >
> > > TIA, Tim
> > >
> > >
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:21 GMT-3