![]() was looking for some advise for an issue i have. If your password is of 32 characters in length, this is enough for the HA functionality to stop functioning, which results in the error above. The bug resides in the password complexity. There is a bug in the SonicWall firmware which I believe affects firmware version 6.2.2.1-14n. The only way to bring them back around is to power off the Secondary, and restart the Primary.Ġ1/31 08:09:29.784: HA Primary : In ACTIVE state - Peer was in NONE state Ġ1/31 08:09:29.800: HA Primary : Got SHAP_CM_GET_LOGIN ACKĠ1/31 08:09:29.800: HA Primary : In SYNC state - Peer was in NONE state Ġ1/31 08:09:29.832: HA Primary : In ACTIVE state - Peer was in NONE state Ġ1/31 08:09:29.848: HA Primary : Got SHAP_CM_GET_LOGIN ACKĠ1/31 08:09:29.848: HA Primary : In SYNC state - Peer was in NONE state Ġ1/31 08:09:29.880: HA Primary : In ACTIVE state - Peer was in NONE state Ġ1/31 08:09:29.896: HA Primary : Got SHAP_CM_GET_LOGIN ACKĠ1/31 08:09:29.896: HA Primary : In SYNC state - Peer was in NONE state However, as there is no configuration present on the Secondary, no configured services will work. If HA was functioning prior to the affected firmware, a HA fail over may result in a loss of service as the Primary believes it has handed over to the Secondary. Primary SonicWall reports 'SYNC' and cycles to 'ACTIVE' constantly, however never manages to synchronize any settings with the Secondary unit in the HA Pair.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |