Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do I stop individual interfaces from developing adjacencies in an OSPF network?

April 26, 2017adjacencies developing individual interfaces Network ospf

0

Posted

How do I stop individual interfaces from developing adjacencies in an OSPF network?

2 Answers

0

Posted

A. To stop routers from becoming OSPF neighbors on a particular interface, issue the passive-interface command at the interface. In Internet service provider (ISP) and large enterprise networks, many of the distribution routers have more than 200 interfaces. Configuring passive-interface on each of the 200 interfaces can be difficult. The solution in such situations is to configure all the interfaces as passive by default using a single passive-interface default command. Then, configure individual interfaces where adjacencies are desired using the no passive-interface command. For more information, refer to Default Passive Interface Feature. There are some known problems with the passive-interface default command. Workarounds are listed in Cisco bug ID CSCdr09263 (registered customers only) .

0

Posted

A. To stop routers from becoming OSPF neighbors on a particular interface, issue the passive-interface command at the interface. In Internet service provider (ISP) and large enterprise networks, many of the distribution routers have more than 200 interfaces. Configuring passive-interface on each of the 200 interfaces can be difficult. The solution in such situations is to configure all the interfaces as passive by default using a single passive-interface default command. Then, configure individual interfaces where adjacencies are desired using the no passive-interface command. For more information, refer to Default Passive Interface Feature. There are some known problems with the passive-interface default command. Workarounds are listed in Cisco bug ID CSCdr09263 ( registered customers only) .