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 hipri
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:<value>
for hipri link
lltconfig -T peertroublelo:<value>
for lopri links.
See the lltconfig(1m) manual page for details.
-
Replace the LLT link.
See Adding and removing LLT links.
|
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.
If the peer node has not actually gone
down, check for the following:
See Adding and removing LLT links.
|
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:
See Adding and removing LLT links.
|
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.
|
|
On local node that detects the link failure:
LLT INFO V-14-1-10519 link 0 down
LLT INFO V-14-1-10585 local link 0 down
for 1 sec
LLT INFO V-14-1-10586 send linkdown_ntf
on link 1 for local link 0
LLT INFO V-14-1-10590 recv linkdown_ack
from node 1 on link 1 for local link 0
LLT INFO V-14-1-10592 received ack from
all the connected nodes
On peer nodes:
LLT INFO V-14-1-10589 recv
linkdown_ntf from node 0 on link 1
for peer link 0
LLT INFO V-14-1-10587 send linkdown_ack
to node 0 on link 1 for peer link 0
|
These messages are printed when you have enabled LLT to detect faster failure of links.
When a link fails or is disconnected from a node (cable pull, switch failure, and so on), LLT on the local node detects this event and propagates this information to all the peer nodes over the LLT hidden link. LLT marks this link as disconnected when LLT on the local node receives the acknowledgment from all the nodes.
|
