LLT INFO V-14-1-10035 timer not called for ### ticks. This message was followed by a GAB panic:GAB: Port v halting system due to network failure

book

Article ID: 100019473

calendar_today

Updated On:

Description

Error Message

LLT INFO V-14-1-10035 timer not called for ### ticks

Cause

LLT timer is the function LLT uses to send and receive heartbeats.  The "LLT INFO V-14-1-10035 timer not called for ### ticks" message is logged when the interval between two calls to the timer is greater than one second.  This is generally caused by a lack of  CPU or memory resources.
 
LLT asks the kernel to schedule the timer periodically according to a set timer value.   This value can be checked with the the "lltstat -t" command and displayed as "basetimer".  For example,

# lltstat -t
LLT kernel tunables:
    maxnids: 32
    maxports: 32
    nominpad: 0
    rthreadpri: 98
    basetimer: 50000       <<< 50000 ms = 50ms

Before VCS 5.0 the bastimer is set to 100ms (10 kernel clock ticks or 0.1 second).  On VCS 5.0 and later versions the basetimer is set to 50ms (5 kernel clock ticks or 0.05 seconds).

LLT asks the kernel to run the LLT timer at the set interval, but the time at which the LLT timer runs will depend on actual system load and other performance factors at the time.  

 

Resolution

If the 'timer not called' messages are occurring frequently, then it will be necessary to check the system's CPU and memory resources to see why the LLT timer is not getting scheduled in a timely manner.
 

 

Applies To

Veritas Cluster Server

Issue/Introduction

LLT INFO V-14-1-10035 timer not called for ### ticks. This message was followed by a GAB panic: GAB: Port v halting system due to network failure

Additional Information

ETrack: 568441