Customer was continuously getting LLT INFO V-14-1-10205 link in trouble messages as per below:

Sep 29 04:24:40 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 4 in trouble
Sep 29 05:20:10 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 3 in trouble
Sep 29 06:00:22 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 3 in trouble
Sep 29 06:00:25 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 3 in trouble
Sep 29 07:20:10 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 3 in trouble
Sep 29 07:32:09 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 0 in trouble
Sep 29 11:58:29 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 5 in trouble
Sep 29 11:58:41 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 5 in trouble
Sep 29 15:19:39 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 0 in trouble
Sep 29 15:19:46 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 0 in trouble
Sep 29 15:19:50 dlesmsx03 genunix: [ID 140958 kern.notice] LLT INFO V-14-1-10205
link 2 (e1000g2) node 0 in trouble


Problem: eTrack 1534270 (LLT : Low pri link goes in trouble due to one-way-link detection code; provide a seperate tunable for trouble on lopri links).


Prior to SF HA 5.1, customer needs to increase the peertrouble setting in lltconfig for these messages to cease.  

Solution:

lltconfig -T peertrouble:400
 

Since SF HA 5.1, a separate peertroublelo tunable has been added for low priority links. So, in order to modify the peertrouble value for low priority links, we can do as follows:

lltconfig – T peertroublelo: