Aruba Central utilizes a " Top-Down " management model for UI Groups . To maintain the integrity of the network and ensure that the central dashboard remains the " Source of Truth, " specific logic is applied during the onboarding process.
* Configuration Conflict Prevention: If a group in Central already has a configuration defined (VLANs, DNS, NTP, etc.), and you add a switch that has its own local startup-configuration , Central detects a conflict. It does not know whether to trust the local switch settings or the group settings.
* The Factory Default Rule: To protect the network from unintended configuration overwrites, Central will only automatically sync and push group settings to a switch that is in a Factory Default state. If the switch has an existing configuration, Central marks it as having a " Config Conflict " and stops the synchronization process until an administrator manually intervenes to choose which configuration should " win. "
* Evaluating other options:
* Option B: If Central weren ' t enabled, the switch wouldn ' t even show up as " connected " or " online " in the dashboard, let alone fail a sync within a group.
* Option C: Central supports VSX monitoring and management (particularly through Template groups or specific UI workflows).
* Option D: Authorization happens at the " Device Inventory " level. If you have already added it to a group, the device is already authorized.

OSPF neighbors on broadcast networks typically reach the 2WAY state during the DR/BDR election process.
It is normal behavior for OSPF neighbors on a broadcast network to be in the 2WAY state until a Designated Router (DR) and Backup DR (BDR) are elected.
The tie in DR election explains why multiple neighbors can be in 2WAY.
No OSPF networks advertised would not cause 2WAY.
IGMP snooping does not affect OSPF adjacency states.
References:
OSPF RFC 2328
ArubaOS-CX OSPF Configuration and Operation Guide
Network Protocol Behavior Reference Manuals