User guide

Configuring OSPF Configuring OSPF
OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 1-29
Converting Local Interfaces into OSPF Passive Interface Using
Route Map
Passive interfaces do not accept or send routing updates. In an OSPF network, an interface can be
configured as passive (by setting the hello interval and dead interval to “0”) mainly to add this interface in
the updates to the OSPF neighbor. No OSPF adjacency is formed on a passive interface, and if a OSPF-
enabled interface is configured as passive where an adjacency already exists, the adjacency drops almost
immediately.
In a scenario where there is a requirement to configure more number of passive OSPF interfaces in an
Area, route map can be used. A route map with set action of route-type ‘internal’ needs to be created for
the local interface (routes) on which passive OSPF interface needs to be created. Using this route map in
redistribution, any or all local interfaces can be converted into passive OSPF interfaces.
Example:
Include the IP interfaces which need to be configured as passive OSPF interface in a route map, and set
metric type as ‘internal’ and then redistribute ‘local into ospf’.
-> ip route-map "R1" action permit
-> ip route-map "R1" match ip-address 10.10.0.0/16
-> ip route-map "R1" set metric-type internal
-> ip redist local into ospf route-map R1 admin-state enable
For more information about configuring route map and the other related commands, see the
“IP Commands” chapter in the OmniSwitch AOS Release 7 CLI Reference Guide and “Configuring IP”
chapter in the OmniSwitch AOS Release 7 Network Configuration Guide.
Note. If there are multiple areas configured in an OSPF domain, the passive OSPF interfaces will be
created in the area with the lowest-numbered Area ID, which is usually the Backbone Area.
Use show ip ospf interface command to view the passive OSPF interfaces.