MENU
You have added a switch with existing configuration to an existing group in HPE Aruba Networking Central but the configuration is not synchronizing. What could cause this?
This scenario highlights the 'Source of Truth' logic within Aruba Central UI Groups.
UI Group Constraints: When a group is managed via the UI (User Interface) mode, Central acts as the absolute master of the configuration. If you add a switch that already has a local configuration (non-factory default) into a group that already has an established configuration, Central perceives a Configuration Conflict.
The Safety Mechanism: To prevent Central from accidentally wiping out a production switch's settings the moment it connects, Central will not automatically synchronize (push) the group configuration to a device that is not in a Factory Default state.
The Resolution: For the switch to synchronize with an existing UI group, you must either:
Erase the startup-configuration on the switch and reboot it (Factory Default), allowing it to 'pull' the group config cleanly.
Manually resolve the conflict by moving the device into the group and then selecting the option to overwrite the local configuration with the group configuration.
Evaluating Other Options:
Option A: This is false. Central fully supports VSX monitoring and configuration (specifically via Template groups or the VSX orchestration UI).
Option B: If the switch is 'added to a group,' it has already passed the initial onboarding/authorization phase.
Option C: If it 'cannot establish a connection,' the switch would show as Offline, not as a synchronization failure within a group.
Currently there are no comments in this discussion, be the first to comment!