Forum Discussion
NimbostratusA device recently failover, but I don't know why.
Hi, I recently had a device failover, but I can't find anything in the logs to indicate why.
log
Oct 11 09:13:11 dvice_A notice tmm[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm2[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm2[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm5[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm5[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm6[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm6[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm3[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm3[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm4[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm4[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm7[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:11 dvice_A notice tmm7[13231]: 01340011:5: HA unit 1 state change: from 1 to 0.
Oct 11 09:13:20 dvice_A notice mcpd[6384]: 0107168c:5: Incremental sync complete: This system is updating the configuration on device gro
up /Common/dg device %cmi-mcpd-peer-/Common/dvice_B from commit id { 81368 7424061905973374382 /Common/dvice_A } to commit i
d { 85137 7424304469001948692 /Common/dvice_A }.
Oct 11 09:13:20 dvice_A notice mcpd[6384]: 0107168c:5: Incremental sync complete: This system is updating the configuration on device gro
up /Common/dg device %cmi-mcpd-peer-/Common/dvice_B from commit id { 81368 7424061905973374382 /Common/dvice_A } to commit i
d { 85137 7424304469001948692 /Common/dvice_A }.
Oct 11 09:18:09 dvice_A notice icrd_child[13462]: 13462,13469, iControl REST Child Daemon, INFO,Transaction [1728605588792715] execu
tion time expired.
Oct 11 17:45:40 dvice_A info platform_agent[7260]: 01e10007:6: Token is renewed.
Oct 11 17:45:40 dvice_A info platform_agent[7260]: 01e10007:6: Token is renewed.
thank you
4 Replies
- Jeffrey_Granier
Employee
Are there any other messages before or after this suspected failover? what type of HA do you have setup? Can you check the other devices logs as well? It's also easier to parse logs using ihealth qkview analyzer. I would upload both BIG-IP device qkviews to ihealth and check the log search feature and look for "failover" or active/standby messages.
xmzpfk123Oct 11 09:13:09 warning sod[5051]: 010c0084:4: Failover status message received after 69449.400 second gap, from device (10.5.17.242) (unicast: -> 7.7.7.1).
We have one suspect log, but we haven't found any documentation that fully matches it.
- Jeffrey_Granier
This could indicate packet loss | network disruption between devices. Error Message: 010c0083:4: No failover status messages received for <timeout> seconds, from device <device> (<IP_address>) (f5.com). Are both of your devices exhibiting the same log messages? Is your HA setup across the network? Directly connected between devices ?
- Aswin_mk
MVP
Hello
You can use below KB for find out the root cause of a fail over event
https://my.f5.com/manage/s/article/K95002127
Br
Aswin
