Re: OSPF wildcard bits

From: Manny Gonzalez (manny@xxxxxxxxxxxxxxxxxxx)
Date: Sat Jun 29 2002 - 21:43:26 GMT-3


   
Ed forgot the disclaimer:

"Sample test performed on a closed course by a professional network geek. Pleas
e
do not attempt this in the real lab. Serious injury may occur"

:-))

Manny Gonzalez
CCIE #9013

Edmund Roche-Kelly wrote:
> After (I think) 12.1 , you can't get the order wrong -- IOS will
> reorder it:
>
> r5#sho running-config
> !
> router ospf 1
> network 10.1.0.0 0.0.255.255 area 0
> !
> r5#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> r5(config)#router ospf 1
> r5(config-router)#network 10.1.1.0 0.0.0.255 area 10
> r5(config-router)#exit
> r5(config)#
> 05:44:24: %OSPF-6-AREACHG: 10.1.1.0/24 changed from area 0 to area 10
> r5(config)#
> r5#sho running-config
> router ospf 1
> network 10.1.1.0 0.0.0.255 area 10
> network 10.1.0.0 0.0.255.255 area 0
> !
> r5#sho ip ospf int loop 10
> Loopback10 is up, line protocol is up
> Internet Address 10.1.1.1/24, Area 10
> Process ID 1, Router ID 10.10.5.1, Network Type LOOPBACK, Cost: 1
> Loopback interface is treated as a stub Host
> r5#
>
>
> It probably doesn't count as best practice though.
>
> Ed
>
>
>>Pls note that the order of the network statements does matter!. For ex. In
>>the 2nd method, if you reverse the order of the network statements, ospf
>>will not consider 172.16.1.1 under area 0 because 172.16.0.0 matches it and
>>you will have problems!.
>>
>>HTH
>>
>>Harish
>



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