QuestionQ59

VerifiedIdentify and Resolve LTM Device Issues

While investigating the reason for a device failover, an LTM Specialist finds the following events in /var/log/ltm:

01010029:5: Clock advanced by 518 ticks  
01010029:5: Clock advanced by 505 ticks  
01010029:5: Clock advanced by 590 ticks  
01010029:5: Clock advanced by 568 ticks  
01010029:5: Clock advanced by 1681 ticks  
01010029:5: Clock advanced by 6584 ticks  
01140029:5: HA daemon_heartbeat tmm fails action is failover and restart.  
010c0026:5: Failover condition, active attempting to go standby.  

Which issue caused the failover?

Explanation

In BIG-IP logs, “Clock advanced by” indicates that TMM was descheduled from the CPU. TMM descheduling can prevent TMM from updating its daemon heartbeat, causing the configured HA action of failover and restart.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!