Forum Discussion
NimbostratusClearing 'FailsafeFault' due to crypto failsafe action
Is it possible to clear a FailsafeFault condition caused by the crypto failsafe by action other than rebooting the unit? I wasn't sure if restarting all services would clear this condition, and even if it would if that would be the 'recommended' action to fully clear the issue.
Rebooting has worked just fine; just seeing if other options available.
7 Replies
RobertBorowski_I had the same problem and after some digging I found the following KB article.
https://support.f5.com/csp/article/K16951
I tried this fix and it works like a charm (no reboot required).
tmsh modify sys db crypto.ha value disable
Ed_SummersInteresting. I wonder if modifying these DB keys also updates the HA action as listed in 'show sys ha-status'.
It appears this key only changes the action taken when a crypto system failure is detected. So if no action is taken, no restart or reboot would be required. Without knowing more about the crypto system (and there is little documentation available, apparently even for support engineers) I'd be hesitant to set 'no action' if the system detects a crypto hardware failure on a production system.
Thanks for the article reference!
chad_14652Agree with Ed, this seems to be an unadvised action. Kind of like unplugging the check engine light rather than fixing the problem.
As of autumn 2018, recent releases of BIG-IP software include an improvement (RFE ID 571651) that enables the system to recover more gracefully from some types of crypto queue problems.
jaikumar_f5Noctilucent
Richard,
Can you please help me in understanding the drawbacks that could arise when the DB value is disabled for crypto.hwacceleration,as per the article.
As of autumn 2018, recent releases of BIG-IP software include an improvement (RFE ID 571651) that enables the system to recover more gracefully from some types of crypto queue problems.
- jaikumar_f5
Richard,
Can you please help me in understanding the drawbacks that could arise when the DB value is disabled for crypto.hwacceleration,as per the article.
