OSPF passive interface detection using automatic CLI discovery is controlled by the parameter, EnableOSPFPassiveInterfaceDiscovery, in the <BASEDIR>/conf/ospf/ospf.conf file. The value is displayed under MSI_AdapterManager in the Domain Manager Administration Console.

By default, OSPF interface IsPassive=FALSE. (An exception is made when OSPFInterface has no associated OSPFEndpoints. For that exception, that interface is marked IsPassive=TRUE.)

During the CLI discovery process, Network Protocol Manager for OSPF discovers and tries to match each OSPFInterface with its OSPFEndpoints.

If, during the CLI discovery process, IsPassive is set to TRUE (indicating the interface is marked as passive) and the interface links to endpoints, those endpoints or sessions will be deleted during the postprocessing phase of discovery. (The OSPF interfaces will still display in the topology.) This reduces the number of FALSE down notifications on OSPF passive interfaces.

Currently, Cisco IOS, Juniper, Juniper ERX, and Force10 devices support CLI detection of passive OSPF interfaces because they support the commands shown in CLI commands by vendor:

Table 1. CLI commands by vendor


CLI discovery command

Cisco IOS and IOS XR

show ip ospf interface


sh ip ospf interface


show ospf interface <interfaceName> detail

Juniper ESX

show ip ospf interface <interfaceName>

Examples of the command output are provided here: