GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: shortcut posted 01/12/2001
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


Becareful with "network 0.0.0.0 255.255.255.255" there are some IOS bugs 
known with that. Also IMHO before attempting the lab it would be a good idea 
to know subnetting and reserve masks back to front in your sleep.

D.


On Friday 12 January 2001 03:51, Brian Hescock wrote:
> Harbir,
>   If you really want a timesaving way of doing ospf (if only a few
> interfaces), and less chance of making an error, use the ip address from
> the interfce and use wildcards bits of 0.0.0.0.  No thinking
> involved.  Most people incorrectly think you need the wildcard bits to
> represent what the network mask is that will be advertised (hey, I used to
> think that... ;-)  All the network statement does is tell ospf which
> interface to turn ospf on, you're not giving it a mask at all.  The mask
> is taken from the interface itself. The only advantage of the wildcards
> bits is you can turn ospf on more than one interface at a time with fewer
> commands.  Example:  network 0.0.0.0 255.255.255.255   We're not
> advertising network 0.0.0.0, we're turning ospf on each interface on the
> router because of the wildcard bits.
>
> Brian
>
> On Thu, 11 Jan 2001, Harbir Kohli wrote:
> > Hello
> > I found a couple of time-savings shortcuts in IOS 12.0.
> > If you wanted to quickly see the config of just an interface so
> >     show run int s0 (works in 12..1.5 but not in 11.2.24)
> > OSPF inverse mask
> >     network 10.10.10.0 255.255.255.0 (works in 12.1.5 and 11.2.24)
> > the router will automatically calculate the inverse mask.  I actually
> > use it even to write access-lists by creating an extra OSPF process and
> > later deleting it, saves me trying to figure out invese masks.
> >
> > Enjoy
> >
> > Harbir
> >
> > _______________________________________________________
> > To unsubscribe from the CCIELAB list, send a message to
> > majordomo@xxxxxxxxxxxxxx with the body containing:
> > unsubscribe ccielab
>
> _______________________________________________________
> To unsubscribe from the CCIELAB list, send a message to
> majordomo@xxxxxxxxxxxxxx with the body containing:
> unsubscribe ccielab

_______________________________________________________
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab