[Contents] [Prev] [Next] [Index] [Report an Error]

Advertising Interface Addresses Without Running OSPF

By default, OSPF must be configured on an interface for direct interface addresses to be advertised as interior routes. To advertise the direct interface addresses without actually running OSPF on that interface, include the passive statement:



(ospf | ospf3) {


area area-id {


interface interface-name {



passive {
}


}


}


}

For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.

Point-to-point interfaces differ from multipoint in that only one OSPF adjacency is possible. (A LAN, for instance, can have multiple addresses and can run OSPF on each subnet simultaneously.) As such, when you configure a numbered point-to-point interface to OSPF by name, multiple OSPF interfaces are created. One, which is unnumbered, is the interface on which the protocol is run. An additional OSPF interface is created for each address configured on the interface, if any, which is automatically marked as passive.

For OSPFv3, one OSPF-specific interface must be created per interface name configured under OSPFv3. OSPFv3 does not allow interfaces to be configured by IP address.

Enabling OSPF on an interface (by including the interface statement), disabling it (by including the disable statement), and not actually having OSPF run on an interface (by including the passive statement) are mutually exclusive states.

You can also configure interfaces in OSPF passive traffic engineering mode. For more information, see Configuring OSPF Passive Traffic Engineering Mode and the JUNOS MPLS Applications Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]