On Tue, Feb 06, 2007 at 11:09:45PM -0500, Nick Davey wrote:
The passive keyword will advertise a network as a stub area, however as
the interface is passive it cannot form a neighbor relationship with any
other router in that area, or on that interface. From the man pages it
would appear
On Wednesday 07 February 2007 00:53, Nigel Roberts wrote:
Is it possible to configure an area in ospfd.conf to be a stub area?
I have an area where all particpating routers (ciscos) are configured
to treat it as a stub ie.
router ospf 1234
...
area 1 stub
...
What excactly is the
On Wed, 07 Feb 2007 at 13:57:52 +0100, Esben Norby wrote:
What excactly is the purpose of this? Is it some cisco trick to save memory
or
does it have a real purpose?
It's not a cisco trick as such, since it's defined in the OSPF RFC
along with NSSA (not so stubby areas) and totally stubby
Is it possible to configure an area in ospfd.conf to be a stub area?
I have an area where all particpating routers (ciscos) are configured
to treat it as a stub ie.
router ospf 1234
...
area 1 stub
...
There doesn't appear to be a way of setting a similar option in
ospfd.conf, so when I start
Nigel Roberts wrote:
Is it possible to configure an area in ospfd.conf to be a stub area?
Yes, use the passive option. It's in the ospfd.conf man page.
---
Lars Hansson
The passive keyword will advertise a network as a stub area, however as
the interface is passive it cannot form a neighbor relationship with any
other router in that area, or on that interface. From the man pages it
would appear there is no way to specify an area as stub however Claudio
or
6 matches
Mail list logo
