From: Jason Gardiner (gardiner@xxxxxxxxxx)
Date: Sat Aug 11 2001 - 12:50:46 GMT-3
I think that if you use the neighbor statement when you have NBMA it
works. with the P2P okay. But upon further consideration, I'll have to
play and see.
Thanks,
Jason Gardiner
Supervisor, Engineering Services
Sprint E|Solutions
"You can swim all day in the Sea of Knowledge and
still come out completely dry. Most people do."
- Norton Juster
On Sat, 11 Aug 2001 jonatale@earthlink.net wrote:
> that will work as far as adj (need to match hello, dead, subnet, area, option
s, and MTU -- maybe the
> std should have included net type, but it did not)
>
> but the db could still be screwed-up
> i think nbma and bcast is ok, and mp2p and p2p is ok
>
> but i think bcast and p2p mixed would confuse the Dijkstra - only bcast has D
R which has a net lsa,
> only p2p has neighbor rtr in the router lsa and has the subnet as a stubnet i
n the router lsa
>
> Jason Gardiner wrote:
>
> > I think you can also do it by setting the hello-interval and dead-interval
> > manually on the interface to match the rest of the area. At least it's
> > worked for me.
> >
> > Thanks,
> >
> > Jason Gardiner
> > Supervisor, Engineering Services
> > Sprint E|Solutions
> >
> > "You can swim all day in the Sea of Knowledge and
> > still come out completely dry. Most people do."
> >
> > - Norton Juster
> >
> > On Thu, 9 Aug 2001, Fred Ingham wrote:
> >
> > > Shane: These are the same OSPF Non-Broadcast network types and you
> > > should have no difficulty establishing adjacencies. If you want R2 to
> > > be the DR a better practice is to set the R1 ip ospf priority to 0.
> > > Then the neighbor statement is only needed on R2 and the priority and
> > > poll-interval options can be dropped.
> > >
> > > I read the original post as: how to correct mismatched OSPF network
> > > types without using a network command.
> > >
> > > How about a tunnel?
> > >
> > > Cheers,Fred.
> > >
> > > SFeldberg@edeltacom.com wrote:
> > > >
> > > > Try this to establish OSPF adjacency and DR on R2:
> > > >
> > > > hostname R1
> > > > !
> > > > int s0.1 multipoint
> > > > ip address 10.1.1.2 255.255.255.248
> > > > frame-relay interface-dlci 123
> > > > ip ospf priority 1
> > > > !
> > > > router ospf 1
> > > > neighbor 10.1.1.1 priority 254 poll-interval 30
> > > >
> > > > << Frame Relay Switch >>
> > > >
> > > > hostname R2
> > > > !
> > > > int S0
> > > > ip address 10.1.1.1 255.255.255.248
> > > > ip ospf priority 254
> > > > !
> > > > router ospf 1
> > > > neighbor 10.1.1.2 priority 1 poll-interval 30
> > > >
> > > > Frame maps and/or inverse arp will be required for the layer 3
> > > > connectivity, depending on the lab requirements.
> > > >
> > > > Steve
> > > >
> > > >
> > > > Shane Miles
> > > > <smiles@ftdat To: "'ccielab@groupstudy.c
om'"
> > > > a.com> <ccielab@groupstudy.com>
> > > > Sent by: cc:
> > > > nobody@groups Subject: alternative to ip
ospf network command
> > > > tudy.com
> > > >
> > > >
> > > > 08/10/2001
> > > > 03:59 PM
> > > > Please
> > > > respond to
> > > > Shane Miles
> > > >
> > > >
> > > >
> > > > If I have a network type mismatch over a Frame Relay PVC the
> > > > only
> > > > way I know to fix it is by using the "ip ospf network" command. I don'
t
> > > > like knowing only one method. Is there an alternative? I read suggest
ions
> > > > about somehow using a route-map but they had no examples and I haven't
been
> > > > able to figure out how.
> > > > --
> > > > Shane P. Miles
> > > > **Please read:http://www.groupstudy.com/list/posting.html
> > > > **Please read:http://www.groupstudy.com/list/posting.html
> > > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:49 GMT-3