VCS troubleshooting

LLT link status messages
	Troubleshooting and recovery for VCS

---

LLT link status messages

describes the LLT logs messages such as trouble, active, inactive, or expired in the syslog for the links.

LLT link status messages

Message	Description and Recommended action
LLT INFO V-14-1-10205 link 1 (link_name) node 1 in trouble	This message implies that LLT did not receive any heartbeats on the indicated link from the indicated peer node for LLT peertrouble time. The default LLT peertrouble time is 2s for hi-pri links and 4s for lo-pri links.  Recommended action: If these messages sporadically appear in the syslog, you can ignore them. If these messages flood the syslog, then perform one of the following:  Increase the peertrouble time to a higher value (but significantly lower than the peerinact value). Run the following command: lltconfig -T peertrouble: for hipri link lltconfig - T peertroublelo: for lopri links. See the lltconfig(1m) manual page for details. Replace the LLT link.
LLT INFO V-14-1-10024 link 0 (link_name) node 1 active	This message implies that LLT started seeing heartbeats on this link from that node.   Recommended action: No action is required. This message is informational.
LLT INFO V-14-1-10032 link 1 (link_name) node 1 inactive 5 sec (510)	This message implies that LLT did not receive any heartbeats on the indicated link from the indicated peer node for the indicated amount of time.  Recommended action: If the peer node has not actually gone down, check for the following:  Check if the link has got physically disconnected from the system or switch. Check for the link health and replace the link if necessary.
LLT INFO V-14-1-10510 sent hbreq (NULL) on link 1 (link_name) node 1. 4 more to go. LLT INFO V-14-1-10510 sent hbreq (NULL) on link 1 (link_name) node 1. 3 more to go. LLT INFO V-14-1-10510 sent hbreq (NULL) on link 1 (link_name) node 1. 2 more to go. LLT INFO V-14-1-10032 link 1 (link_name) node 1 inactive 6 sec (510) LLT INFO V-14-1-10510 sent hbreq (NULL) on link 1 (link_name) node 1. 1 more to go. LLT INFO V-14-1-10510 sent hbreq (NULL) on link 1 (link_name) node 1. 0 more to go. LLT INFO V-14-1-10032 link 1 (link_name) node 1 inactive 7 sec (510) LLT INFO V-14-1-10509 link 1 (link_name) node 1 expired	This message implies that LLT did not receive any heartbeats on the indicated link from the indicated peer node for more than LLT peerinact time. LLT attempts to request heartbeat mechanism (sends 5 hbreqs to the peer node) and if the peer node does not respond, LLT marks this link as "expired" for that peer node.  Recommended action: If the peer node has not actually gone down, check for the following:  Check if the link has got physically disconnected from the system or switch. Check for the link health and replace the link if necessary.
LLT INFO V-14-1-10499 recvarpreq link 0 for node 1 addr change from 00:00:00:00:00:00 to 00:18:8B:E4:DE:27	This message is logged when LLT learns the peer node's address.  Recommended action: No action is required. This message is informational.

LLT detects cross links usage

If LLT detects more than one link of a system that is connected to the same network, then LLT logs a warning message similar to the following in the syslog:

LLT WARNING V-14-1-10498 recvarpack cross links? links 0 and 2 saw the same peer link number 1 for node 1

Recommended Action: This is an informational message. LLT supports cross links. However, if this cross links is not an intentional network setup, then make sure that no two links from the same system go to the same network. That is, the LLT links need to be on separate networks.