passive-interface

In large enterprise network supporting distribution routers with multiple interfaces, it’s always a tough task to keep track of adjacencies. There are times where you really wonder whether you want to form adjacencies with all interfaces or not.

The solution to this problem has been to configure the routing protocol on all interfaces and manually set the passive-interface command on the interfaces where adjacency was not desired. In some networks, this meant coding 200 or more passive interface statements. With the Default Passive Interface feature, this problem is solved by allowing all interfaces to be set as passive by default using a single passive-interface default command, then configuring individual interfaces where adjacencies are desired using the no passive-interface command

Configuration Example:-

Command	Purpose
Router(config)# router protocol	Configures the routing protocol on the network.
Router(config-router)# passive-interface default	Sets all interfaces as passive by default.
Router(config-router)# no passive-interface interface-type	Activates only those interfaces that need to have adjacencies set.
Router(config-router)# network network-address [options]	Specifies the list of networks for the routing process..

This feature was introduced with Cisco IOS v12.0. It works for all routing protocols that support the passive-interface command

---

Possibly related posts: (automatically generated)

• BGP quick tips
• Auditing Router Interfaces
• Configuring Switch ports in Campus Environments
• Answers for Interconnecting Cisco Networking Devices (ICND) Practice Questi…