Loading...
Loading...
1) FMC license gets into an UNREGISTERED state. 2) The first deployment post-upgrade could kick out cluster data nodes and it would re-join automatically.
1) FMC upgrade
As of now a manual re-registration of FMC would be needed and the changes need to be force deployed. Note: The deployment may kick out the data nodes and the export control functionality will be toggled.
1. In the 7.4.x version, the fix of this defect takes effect for software upgrades from version 7.4.2 to the next version. This means that the symptoms of this defect may still be observed in version 7.4.2. 2. Post FMC upgrade the user may see the FMC Smart License get into an UNREGISTERED state. The first deployment post the upgrade may kick out cluster data nodes depending on the criteria if the export control functionality was previously enabled. FMC needs to be manually Re-registered to the CSSM server and the change needs to be force deployed. The force deployment may kick out the nodes again depending on the export functionality toggle. The following logs can be seen on the FTD console: Master unit (unit-1-1) forcing member (unit-2-1) out of the cluster due to 3DES license update on the master. Unit unit-2-1 will attempt to join back into the cluster in 5 seconds. unit-2-1 will attempt to rejoin the cluster after adjusting the 3DES license to match that of the master unit.
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.