RE: OSPF wildcard bits

From: Jerry Haverkos (jhaverkos@xxxxxxxxxxxxxxx)
Date: Sat Jun 29 2002 - 21:30:54 GMT-3


   
Ahmed

Consider this -- The network command for OSPF does not actually advertise
routes. It just specifies which interfaces -- on that router -- participate
in OSPF -- and more appropriately a particular OSPF area.

If the interfaces network address is covered by the wildcard mask
specified -- and therefor the interface is participating in OSPF -- it will
be advertised.

If you have several areas on a router and want to break up an address like
101.1.1.0 into several subnets, the OSPF masks have to be specific so each
subnet can be applied to the different areas.

jerry

p.s After I write an OSPF wildcard mask I usually do 'sho ip ospf int' to
make sure that OSPF owns the interface and it is in the appropriate area.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Ahmed Al-Ghawas
Sent: Saturday, June 29, 2002 3:37 PM
To: ccielab@groupstudy.com
Subject: OSPF wildcard bits

Guys,

I am really getting confused!

>From what I understood from "CCIE Practical Studies" book that when using
the
network command, that you ought to be precise in the extent that you would
add
the interface ip address and not advertise the whole subnet mask!

For example:

R1
S0:10.1.128.1/24
|
|
S0:10.1.128.2/24
R2
S1:10.1.80.1/24
|
|
S1:10.1.80.3/24
R3

R1 config:
router ospf 2001
network 10.1.128.1 0.0.0.0 area x (and not; network 10.1.128.0 0.0.0.255
area
x!!)

R2 config:
router ospf 2001
network 10.1.128.2 0.0.0.0 area x (and not; network 10.1.128.0 0.0.0.255
area
x!!)
network 10.1.80.1 0.0.0.0 area x (and not; network 10.1.80.0 0.0.0.255 area
x!!)

R3 config:
router ospf 2001
network 10.1.80.3 0.0.0.0 area x (and not; network 10.1.80.0 0.0.0.255 area
x!!)

I really need to stick to one concept and understand why this book doest it
differently then the other and avoid loosing marks for such stupid thing in
the real lab!!

Any input is much appreciated

Ahmed



This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:44 GMT-3