Hi Alef, There can be some compatability issues if you mix different network types and while I realise you didn't specifically ask that question, in some cases the lab may restrict what you can change (one side may be fixed) so you cant necessarily pick a single method and have it in your tool box.
There are two main components for interworking different OSPF network types that need to be considered - hello/dead-interval timers (it's either 10/40 or 30/120 depending on the interface type for example getting an interterface type of nbma and broadcast working one side needs its timers adjusted) and whether there is a DR election or not, if you need to play with priorities to ensure that a hub becomes the DR and static neighbor definitions are required. There is a really good explanation of all this an a great slide explaining this in the IPExpert VoD material. If you're stuck and need to see what the timers are, show ip ospf interface <xxx> gives all the good information Cheers, Adam On Thu, May 19, 2011 at 8:05 AM, Alef <[email protected]> wrote: > Can i 'convert' any underlying l2 interface (physical,fastethernet,or frame > point-to-point, multipoint) by using the ip ospf network command and let > them do my bidding? it seems like an easy solution in a lot of cases. is > there no catch? > is it a magic wand? > > Alef > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
