Last Modified: May 14, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
13.1.0, 13.0.1, 12.1.2 HF1
Opened: Nov 03, 2016
Related AskF5 Article: K37665112
CMP state change can result in a blade crash.
Blade crash resulting in potential loss of service.
CMP state change with a PEM profile enabled on a virtual. The former can be triggered using a TMM restart/unrelated crash, blade insertion or blade administrative state change.
Deploy PEM in an HA-pair with a chassis fail over configured to occur if at most one blade on the active chassis fails.
The system now gracefully handles sessionDB errors due to a CMP state change.