FORTIGATE - diag sys ha reset-uptime: Difference between revisions

From IT-Arts.net
← Older edit
No edit summary
m Text replacement - "Category:Wiki" to "Category:Wiki '''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]''''' "
 
Line 1: Line 1:
[[Category:Wiki]]
[[Category:Wiki]]
'''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]'''''


==  Required privileges ==
==  Required privileges ==

Latest revision as of 08:20, 17 January 2026


Return to Wiki Index


Required privileges

  • Super-admin (profile with full diagnostic access)
  • Console or SSH access

Command syntax

diag sys ha reset-uptime

No arguments or parameters are supported.

Verify HA uptime reset

Before reset: 

get system ha status

Output excerpt: HA Health Status: OK HA Uptime: 5 days, 3 hours, 12 minutes

After reset: 

get system ha status

Output excerpt: HA Health Status: OK HA Uptime: 0 days, 0 hours, 1 minute

Troubleshooting

Command has no visible effect

Possible causes:

  • Device not in HA mode
  • Insufficient privileges
  • HA process not running properly

Verification steps: 

get system ha status

diagnose sys ha status

HA uptime resets unexpectedly

Potential causes:

  • HA daemon crash or restart
  • Firmware bugs
  • Network instability on HA heartbeat interfaces
  • Power or hardware issues

Recommended actions:

  • Enable HA debugging
  • Review system crash logs
  • Check HA heartbeat integrity

HA failover confusion after reset

Clarification:

  • Resetting HA uptime does not indicate a failover
  • Always correlate with:
get system ha history
execute log filter category event

Best practices

  • Use only for diagnostics and testing
  • Avoid in production unless explicitly required
  • Always capture HA status before and after execution
  • Coordinate with monitoring teams prior to execution
Retrieved from "https://it-arts.net/index.php?title=FORTIGATE_-_diag_sys_ha_reset-uptime&oldid=1030"