From e296daf2303ca8266d9e33264c26e664ce8521a6 Mon Sep 17 00:00:00 2001 From: Yuri Slobodyanyuk Date: Thu, 24 Nov 2022 14:59:03 +0000 Subject: [PATCH] ongoing additions, changes, and fixes --- cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc b/cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc index 9da21d3..eba4d4c 100644 --- a/cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc +++ b/cheat-sheets/Fortigate-debug-diagnose-complete-cheat-sheet.adoc @@ -258,7 +258,7 @@ The output will look like `state/chg_time/now=2(work)/1610773657/1617606630`, wh |*diagnose sys ha reset-uptime* -|Resets uptime of this member making it less than the other member(s)'s uptime +a| Resets uptime of this member making it less than the other member(s)'s uptime and so fails over to those member(s). This is a temporary way to force cluster fail-over to another member from the current one. NOTE: check that the setting below is present or immediately after the reset and failover, this member will become