From: Gopal@xxxxx
Date: Sat Jan 27 2001 - 21:30:34 GMT-3
I used 0.0.0.0 in the lab. But in real life you hardly have that comfort-You
don't want to enter 50 lines for your 50 interfaces:-( By the way, for who have
trouble making wild card bits, it is wildcard bits=255.255.255.255 - subnet
mask.
for the subnet mask, 255.128.0.0 - the wild card mask = 0.127.255.255 :-)
rgs, gopal
Jarrod Mills wrote:
> Chuck,
>
> In my OSPF confis, I always entered address and mask (not inverse) on area
> command and let IOS supply network and wildcard mask. That way, I didnt
> have to worry about making mistakes.
>
> Jarrod Mills, CCIE 6679
> ----- Original Message -----
> From: "Chuck Larrieu" <chuck@cl.cncdsl.com>
> To: "Les Hardin" <hardinl@bah.com>; <ccielab@groupstudy.com>
> Sent: Thursday, January 25, 2001 12:29 AM
> Subject: RE: OSPF Config Styles
>
> > Smarter people than I have a diversity of opinion here. A couple of random
> > thoughts:
> >
> > Using 0.0.0.0 255.255.255.255 is quick and dirty. It places all the
> > interfaces you want into the process, and in some cases some that you
> don't
> > want. Definitely NOT recommended for the Lab, where you will undoubtedly
> be
> > told not to advertise something or other
> >
> > Using a.b.c.d 0.0.0.0 serves to place only the specific interface into the
> > process. Specific, clean, easy to troubleshoot, and in any environment is
> > supposed to make troubleshooting easier. Everyone, how many times have you
> > done things this way, found something or other wasn't working, and it took
> a
> > while for your sore eyes to see you made a mistake in the a.b.c.d portion?
> > In a time sensitive environment like the Lab this still might be the
> easiest
> > thing to troubleshot
> >
> > a.b.c.d inverse mask easiest one to make a mistake with, and hardest one
> to
> > troubleshoot, IMHO. Especially in an VLSM environment.
> >
> > BTW, just for fun consider using the interface address as the mask. E.g.
> > 192.168.7.47 192.168.7.47 area 1 it is indeed a legitimate mask, as it
> > places the desired interface into OSPF. Just remember the law of
> unintended
> > consequences :->
> >
> > Question to all - do you find yourselves slipping back and forth between
> > inverse mask / wildcard mask / subnet mask usage?
> >
> > I find myself more than I care entering 0.0.0.0 as a subnet mask and
> > 255.255.255.240 as a wildcard mask. Is this a stage I am going through as
> I
> > pound routers more and more in my prep?
> >
> > Chuck
> >
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Les
> > Hardin
> > Sent: Wednesday, January 24, 2001 10:01 PM
> > To: ccielab@groupstudy.com
> > Subject: OSPF Config Styles
> >
> > All,
> >
> > I'd like to engage in a religious discussion for a moment -- OPSF
> > configuration styles.
> >
> > I know that there are at least 2 schools of thought out there regarding
> > OSPF config.
> >
> > Under router ospf 1:
> > 1) Use network command with classfull IP addresses
> > 2) Use network command with 32-bit interface address, ensuring that only
> > the desired interface is activated for OSPF, then perhaps using area range
> > to summarize.
> >
> > I'd like to hear from a few folks as to what their preference is and
> > why. I'm interested as to where the majority of folks sit on this
> > topic. Thanks for your inputs.
> >
> > Les
> > yada yada yada certs
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:45 GMT-3