HA active-passive preferred primary device

Hi FFin ,

Thank you for reaching out to the community, in the event of failover if the license is properly synced with the aux device they you shall have no problems in the functionality.  There is also an option called Preferred primary device: Ensure here the primary device is selected when the primary is restored from the failure event. 

Hello Vivek Jagad ,

if there‘s no difference in functionality, why is there such a hint in documentation? 

Are „services, such as FastPath offloading“ somehow restricted on non-initial-primary or not?

If yes, what restrictions are there without „correct“ preferred primary in detail?

This is to assure while establishing HA in active-passive !

So it‘s just to remind you to ensure your cluster will get the correct licenses during HA-Setup and there‘s no downside not selecting any preferred master?

That is really misleading in documentation.
As functions like fast-path offloading are even part of base-license and has nothing to do with licensing in HA, even if you have the wrong initial primary on Setup?

So it‘s just to remind you to ensure your cluster will get the correct licenses during HA-Setup and there‘s no downside not selecting any preferred master?

That is really misleading in documentation.
As functions like fast-path offloading are even part of base-license and has nothing to do with licensing in HA, even if you have the wrong initial primary on Setup?

Hello FFin ,

We understand your concern regarding the content specifically mentioned as "only the initial primary device supports services, such as FastPath offloading". I will check with the KBA team to get this updated.

Great Mayur Makvana , thank you very much! This will prevent future misreadings of this tip!

Hello FFin ,

The suggested change has been applied.

https://docs.sophos.com/nsg/sophos-firewall/20.0/Help/en-us/webhelp/onlinehelp/HighAvailablityStartupGuide/HAConfiguration/HAQuickHAConfigureActivePassive/index.html#how-to-configure

We appreciate pointing the correction.

Great! Much clearer now - thanks!