One can skip all that stuff with masks by using "ip ospf .. area .." under the interface configuration. Makes the configuration much more readable, too.
In R&S it'll be available on 12.4M, recent 12.2SE (40 or 44 and above IIRC) and obviously in 12.4T so on everything for 4.0. Obviously it will help if one is still able to calculate wildcards as a backup ;-) Kaj > From: Joe Astorino <[email protected]> > Date: Mon, 31 Aug 2009 22:37:43 -0700 > To: Rick Mur <[email protected]> > Cc: <[email protected]> > Subject: Re: [OSL | CCIE_RS] OSPF network config > > Either method will work fine, it is MOSTLY a matter of preference. When I say > mostly I mean that if you are not going to use the very specific 0.0.0.0 > inverse mask, make very sure you know EXACTLY what interfaces you are actually > advertising with a more broad inverse mask. > > When we get to the CCIE level, my preferred method is to exactly match every > interface with a 0.0.0.0 wildcard mask. The reason is that it is much more > specific and you don't end up unintentionally advertising things you don't > want into a routing protocol. In the real world, your general 0.0.0.255 mask > is probably OK. In the CCIE lab, lock everything down as tight as you can > here and you will likely avoid a headache later on.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
