OSPF Passive Interface Configuration
|
Router OSPF subcommand |
Description |
Examples |
|---|---|---|
| passive-interface <interface interface-id> | Configure the passive-interface on a single or a couple of interfaces individually | Router(config)#router ospf <process-id> Router(config-router)#passive-interface <interface interface-id> |
| passive-interface default | configure all interfaces to be passive interfaces, leaving a single or a couple of interfaces as a non-passive interface |
Router(config)#router ospf <process-id> Router(config-router)#passive-interface default Router(config-router)#no passive-interface <interface interface-id> |
Configuring OSPF Passive Interface in Cisco
Configuring an interface as a passive interface in and OSPF domain causes OSPF to stop sending Hellos on that specified interface. OSPF will continue to advertise the subnet’s passive interface as a stub network. The interface should only be configured as a passive interface that does not have an OSPF router/MLS connected to them so that they (connected to a non-OSPF router/MLS or end hosts) won’t receive any OSPF information. OSPF passive interface thus reduces the OSPF protocol’s routing load on the CPU by minimizing the number of interfaces with which it must interact. The passive interface still listens for the OSPF hello packets but doesn’t originate/propagate them.