Which component would most likely need rebooting after a configuration change affecting HA?

After making a significant configuration change that impacts High Availability (HA) within a Sophos XG Firewall environment, it is often necessary to reboot both the primary and secondary devices to ensure that they synchronize correctly and operate effectively after the change.

When HA is configured, the primary device and the secondary device work in tandem to provide redundancy and failover capabilities. However, changes in configuration could lead to inconsistencies between the two units. Rebooting both devices helps to clear any cached configurations and properly establish the new settings across the HA pair, thus maintaining the integrity of the HA functionality.

In some situations, the primary device might have a configuration that the secondary device does not recognize, or vice versa. This could result in operational issues or degraded performance if both are not aligned in terms of their configuration. Therefore, performing a reboot on both is a crucial step to ensure that they are fully synchronized and ready to handle traffic as intended.

This understanding is vital for network administrators who need to ensure seamless operation and reliability of their firewall systems, particularly in an HA setup.