Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
dum0785
New Contributor II

HA uptime and system uptime different things?

Hi,

I'm currently testing HA switching.

Please tell me, are HA uptime and system uptime two different things?

Also, is there a command to check HA uptime?

2 Solutions
srajeswaran

Can you check the individual node uptime using "diagnose sys ha dump-by group" as suggested in https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-verify-HA-cluster-members-individua...

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

View solution in original post

dum0785
New Contributor II

I confirmed it!

 

before

"diagnose sys ha dump-by group"

Spoiler
vcluster_nr=1
vcluster_0: start_time=1694414132(2023-09-10 23:35:32), state/o/chg_time=2(work)/3(standby)/1694420054(2023-09-11 01:14:14)
pingsvr_flip_timeout/expire=3600s/1579s
mondev: port1(prio=50,is_aggr=0,status=1)
'FGVMEVIPX9HOLV5D': ha_prio/o=1/1, link_failure=0, pingsvr_failure=0, flag=0x00000000, mem_failover=0, uptime/reset_cnt=0/19   ←Slave
'FGVMEVQ3405RTR72': ha_prio/o=0/0, link_failure=0, pingsvr_failure=0, flag=0x00000001, mem_failover=0, uptime/reset_cnt=6702/3   ←Master

Master #diagnose sys ha reset-uptime

 

 

after

 "diagnose sys ha dump-by group"

Spoiler
vcluster_nr=1
vcluster_0: start_time=1694422187(2023-09-11 01:49:47), state/o/chg_time=3(standby)/2(work)/1694422187(2023-09-11 01:49:47)
pingsvr_flip_timeout/expire=3600s/3589s
mondev: port1(prio=50,is_aggr=0,status=1)
'FGVMEVIPX9HOLV5D': ha_prio/o=0/0, link_failure=0, pingsvr_failure=0, flag=0x00000001, mem_failover=0, uptime/reset_cnt=1353/19   ←Slave
'FGVMEVQ3405RTR72': ha_prio/o=1/1, link_failure=0, pingsvr_failure=0, flag=0x00000000, mem_failover=0, uptime/reset_cnt=0/4   ←Master

 

View solution in original post

5 REPLIES 5
srajeswaran
Staff
Staff

HA uptime is the time since a monitored interface failed or is disconnected. Age is also reset when a cluster unit starts (boots up). So, when all cluster units start up at about the same time, they all have the same age. Age does not affect primary unit selection when all cluster units start up at the same time.

If a link failure of a monitored interface occurs, the age value for the cluster unit that experiences the link failure is reset. So, the cluster unit that experienced the link failure also has a lower age value than the other cluster units.

System uptime is the time since the device booted up, link failures don't influence this value.

You can check HA uptime using "get system ha status" look for "cluster uptime"

Master (global) # get system ha status
HA Health Status: OK
Model: FortiGate-VM64
Mode: HA A-P
Group: 100
Debug: 0
Cluster Uptime: 0 days 0:39:28

Ref: https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-verify-HA-cluster-members-individua...

System uptime can be seen under "get system performance status"

# get system performance status

CPU states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq

Virus caught: 0 total in 1 minute
IPS attacks blocked: 0 total in 1 minute
Uptime: 0 days, 0 hours, 23 minutes

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

dum0785
New Contributor II

Hi,
srajeswaran

 

Thank you for your reply.
What I don't understand is that even after I run the "diagnose sys ha reset-uptime" command and check "get system ha status", there is no change in Cluster Uptime.
After I type the "diagnose sys ha reset-uptime" command, what do I see to know that Uptime has been reset?

 

Regards,

srajeswaran

Can you check the individual node uptime using "diagnose sys ha dump-by group" as suggested in https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-verify-HA-cluster-members-individua...

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

dum0785
New Contributor II

I confirmed it!

 

before

"diagnose sys ha dump-by group"

Spoiler
vcluster_nr=1
vcluster_0: start_time=1694414132(2023-09-10 23:35:32), state/o/chg_time=2(work)/3(standby)/1694420054(2023-09-11 01:14:14)
pingsvr_flip_timeout/expire=3600s/1579s
mondev: port1(prio=50,is_aggr=0,status=1)
'FGVMEVIPX9HOLV5D': ha_prio/o=1/1, link_failure=0, pingsvr_failure=0, flag=0x00000000, mem_failover=0, uptime/reset_cnt=0/19   ←Slave
'FGVMEVQ3405RTR72': ha_prio/o=0/0, link_failure=0, pingsvr_failure=0, flag=0x00000001, mem_failover=0, uptime/reset_cnt=6702/3   ←Master

Master #diagnose sys ha reset-uptime

 

 

after

 "diagnose sys ha dump-by group"

Spoiler
vcluster_nr=1
vcluster_0: start_time=1694422187(2023-09-11 01:49:47), state/o/chg_time=3(standby)/2(work)/1694422187(2023-09-11 01:49:47)
pingsvr_flip_timeout/expire=3600s/3589s
mondev: port1(prio=50,is_aggr=0,status=1)
'FGVMEVIPX9HOLV5D': ha_prio/o=0/0, link_failure=0, pingsvr_failure=0, flag=0x00000001, mem_failover=0, uptime/reset_cnt=1353/19   ←Slave
'FGVMEVQ3405RTR72': ha_prio/o=1/1, link_failure=0, pingsvr_failure=0, flag=0x00000000, mem_failover=0, uptime/reset_cnt=0/4   ←Master

 

srajeswaran

It shows the uptime is reset to zero "uptime/reset_cnt=0/4 ←Master", please correct me if I am missing any points.

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

Labels
Top Kudoed Authors