Forum Discussion
Default clientssl ciphers different between HA pair on same version
Running 11.4.1 on an HA pair and when the standby became active, even though the configs were in sync, it was discovered that the parent CSSL profile 'clientssl' was not in sync - it had a custom set of ciphers on the primary LTM, but was set to DEFAULT on the standby. It allowed SSLv3 and RC4 when the standby unit was active, but they are disabled on the primary. I corrected the cipher list to be more exclusive and sync status never changed to 'out of sync'.
Is that bit of config not replicated between HA devices? Seems like an odd choice to be by design, but that's what it looks like.
FYI to anyone else.
SOL14289: Changes made to base profiles are not synchronized to other hosts in a device group
Fixes Introduced In 11.5.0
https://support.f5.com/kb/en-us/solutions/public/14000/200/sol14289.html
- DevBabuCirrus
Should have been replicated. Any reasons 11.4.1 standby went to active ? UPGRADES...
- Kevin_49772Nimbostratus
FYI to anyone else.
SOL14289: Changes made to base profiles are not synchronized to other hosts in a device group
Fixes Introduced In 11.5.0
https://support.f5.com/kb/en-us/solutions/public/14000/200/sol14289.html
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com