From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Sat Feb 24 2001 - 17:51:00 GMT-3
Good place to put in a caveat. I've run into this in a couple of places now,
and searches through the doc CD have left me a bit perplexed.
In general, according to the doc CD and to my experience both with bootcamp
racks and my own lab, the ip ospf network point-to-point is not available in
IOS 11.2 or 11.3. It appears to have been introduced in 12.x, although the
doc CD does not say when the command was introduced. ( I believe I am
running the June 2000 CD )
So one should be aware, when fooling with ip ospf network types on
interfaces, of the consequences of your actions. Not only with the timers,
but with what type of network calls for what actions with regards to DR
election etc.
So for example, I am practicing OSPF over various frame configurations. I
have a couple of 12.x routers and an 11.3 router.
The frame / ospf hub router is using the base interface plus ip ospf network
point-to-multipoint. I can run ip ospf point-to-point on the interfaces of
my two 12.x routers, where I have to adjust the timers, but on the 11.3
router, I have to run ip ospf point-to-multipoint. No problem. Just a bit
unintuitive
Also - if using the default ospf network type on a frame relay interface
Non-broadcast ) one still must keep in mind that a DR and BDR are elected
by default. One must then remember the implications and configure so that
the hub becomes the DR and that no BDR is elected for obvious reasons.
The one other thing to remember is how networks are advertised within ospf
under these different network types. Loopbacks as a host route to a stub
network, point-to-multipoint will appear as host routes even if a classful
mask is used.
None of this stuff is real world best practice. But it appears in enough
practice scenarios that it is a pretty good bet that the Lab will require
this knowledge base, and that one can expect a scenario that will strain
one's sanity if this stuff isn't practiced and internalized before walking
in.
I am assuming there are similar issues with ATM as well.
Chuck
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Simon Baxter
Sent: Saturday, February 10, 2001 2:45 PM
To: Atif Awan; akkumar1000@yahoo.com; ccielab@groupstudy.com
Subject: RE: OSPF ip ospf network type
The network types don't have to match, but the timers do. Also be careful
that the rules for the neighbor definitions are similar.
You can have point-to-multipoint on a hub and point-to-point on the spokes
as long as you adjust the hello/dead.
cool trick eh?
-----Original Message-----
From: Atif Awan [mailto:atifawan@hotmail.com]
Sent: Saturday, February 03, 2001 6:35 AM
To: akkumar1000@yahoo.com; ccielab@groupstudy.com
Subject: Re: OSPF ip ospf network type
No you cannot. The network types need to match.
>From: anand kumar <akkumar1000@yahoo.com>
>Reply-To: anand kumar <akkumar1000@yahoo.com>
>To: ccielab@groupstudy.com
>Subject: OSPF ip ospf network type
>Date: Fri, 2 Feb 2001 12:08:53 -0800 (PST)
>
>Hi all,
>
>In a partial mesh config, can I use ip ospf network
>type as "point to multipoint" on the hub router and
>"point-to-point" on the spoke routers eventhough the
>hello and dead intervals are different (40,120 and
>10,40)?
>
>Appreciate your response.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:59 GMT-3