Your network statements need to match the interfaces you want added into the OSPF process. Passive-interface doesn't play a part in what does/doesn't get inserted into the OSPF process. Passive-interface turns off the sending of hello packets out that interface (and processing of any received). So you can have a network (interface) that is inserted into OSPF, yet can't form any neighbors. The configuration of OSPF directly on interfaces is a part of OSPFv3 (for IPv6 only I believe).
Chuck -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of CiscoNSP List Sent: Tuesday, March 03, 2015 3:41 PM To: [email protected] Subject: [c-nsp] ospf (passive-interface default) Hi Everyone, Dont have a lab handy to test this, so hoping someone can answer: If you configure: router ospf 1 network 10.10.10.0 0.0.0.3 area 1 without passive-int default, will ospf be "enabled" on all Interfaces, or just the Interface with 10.10.10.0/30 configured on it? I was always under the impression that (best practice) is to do the following, so that ospf is disabled on all ints, apart from the ones configured with "no passive int foo" router ospf 1 passive-int default no passive int gi0/1 network 10.10.10.0 0.0.0.3 area 1 ...and, (As an alternative) is configuring ospf under each interface now a method many use instead of the above example? ...I havent tried the "per int" method (I will later today), but in theory, I think having all the config under "router ospf xx" would be easier to maintain...i.e. all the config is in the one section for ospf? Cheers. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
