LLT INFO V-14-1-10205 link 2 (###) node 1 in trouble
This issue can usually be attributed to either high system load or network congestion (on which the LLT low-priority link is set up)
If the high system load or network congestion or other cause can not be determined, then one option is to increase the peertrouble tunable attribute of the LLT module.
When heartbeats are missed for more than "peertrouble" number of seconds, LLT logs the message "link in trouble".
To display the current value of the attribute:
# lltconfig -T query
Current LLT timer values (.01 sec units):
heartbeat = 50
heartbeatlo = 100
peertrouble = 200 <<
.
.
To change it while the cluster is running:
# lltconfig -T peertrouble:
Consider first raising to "400", and continue to monitor.
To set the new value as persistent after reboot:
edit the /etc/llttab file and add the following entry:
set-timer peertrouble:
The value should be amended on all cluster nodes.
Applies To
The link concerned was a low-priority link, i.e. shared with the public network