Cisco OSPF Session Compatibility Status flagged as AREA_MISMATCH in configuration #924
Description
Found a false positive for the OSPF Session Compatibility question when using a router ospf network statement with the area defined "network 192.168.1.0 0.0.0.255 area 10" configuration. See config example below:
result = bf.q.ospfSessionCompatibility().answer()
interface Vlan 1
description test-point-to-point-connection
ip address 192.168.1.1 255.255.255.0
ip ospf network point-to-point
router ospf 1
network 192.168.1.0 0.0.0.255 area 10If you configure the command ip router ospf 1 area 0.0.0.10 under the interface configuration in Cisco IOS, here's what will happen:
Direct Interface Area Assignment: This command directly assigns the interface to OSPF process 1 and OSPF area 0.0.0.10 (which is equivalent to area 10). This bypasses the need for the OSPF network statement under the router ospf 1 configuration to assign the interface to an area. The interface will participate in OSPF and will be directly placed into area 0.0.0.10.
Overrides Network Statement: If you have both the network statement under the router ospf configuration and the ip router ospf command under the interface, the interface-level OSPF configuration will take precedence for that specific interface. This means the interface will always belong to the area specified at the interface level, regardless of any matching network statements in the global OSPF configuration.
Key Points:
-
The ip router ospf 1 area 0.0.0.10 command at the interface level overrides any area assignments made by network statements for that specific interface.
-
If you want more granular control of which area each interface belongs to, configuring OSPF at the interface level is a valid approach.
-
However, if you already have a network statement covering the interface's IP range, the interface-level OSPF configuration isn't necessary unless you want to specifically manage the area at the interface level.