LLT does not work with Linux NIC bonded interfaces upon initial startup in 5.0 MP3

book

Article ID: 100019076

calendar_today

Updated On:

Resolution

The Veritas Cluster Server 5.0 MP3 Release Notes mention:
 
"LLT supports NIC bonding
You can configure NIC bonds (aggregated interfaces) as private links under LLT. LLT treats each aggregated interface as a single link. So, you must configure these NICs that form the bond in such a way that the NICs are connected to the same switch or hub.
 
Note: If the NICs are connected to different switches or hubs, you must establish connection between the switches or hubs.
 
See the Veritas Cluster Server Installation Guide for instructions to configure private heartbeats that use aggregated interfaces. "
 
 
However when defining the bond interface in the /etc/llttab file using the mac-address,  llt will not work properly.
 
Example:
# more /etc/llttab
set-node sys1
set-cluster 31337
set-verbose 1
link eth2 eth-00:04:23:c5:d4:78 - ether - -
link eth3 eth-00:04:23:C5:D4:79 - ether - -
link-lowpri bond0 eth-00:14:22:23:27:12 - ether - -
 
To be more specific when a Linux NIC aggregate interface is configured in the /etc/llttab file as above, the  'lltstat -nvv | head' command will report the link as DOWN for all peer nodes.
 
For example:
 
sys1# lltstat -nvv | head
LLT node information:
Node State Link Status Address
*0daa21267orc303a OPEN
                      eth3 UP 00:17:08:7D:E6:DD
                      bond0 UP 00:16:35:82:1D:32
1daa21267orc303b OPEN
                      eth3 UP 00:17:08:7D:E0:0B
                      bond0 DOWN
 
sys2# lltstat -nvv | head
LLT node information:
Node State Link Status Address
0daa21267orc303a OPEN
                     eth3 UP00:17:08:7D:E6:DD
                     bond0 DOWN
* 1daa21267orc303b OPEN
                     eth3 UP00:17:08:7D:E0:0B
                     bond0 UP00:15:60:53:96:B0
 
(Please note that this issue affects both private and low-pri LLT links.)
 
Workaround1:
 
It has been observed that by running the following set of commands on each node the problem goes away.
 
lltconfig -u bond0
lltconfig -t bond0 -d bond0 -l
 
However these changes will not be persistent across reboot.
 
Workaround 2(Persistent across reboot):
 
In order to properly configure a linux bond interface for use as a llt link, it must  be defined as follows in the /etc/llttab:
 
# more /etc/llttab
set-node sys1 
set-cluster 31337
set-verbose 1
link eth2 eth-00:04:23:c5:d4:78 - ether - -
link eth3 eth-00:04:23:C5:D4:79 - ether - -
link-lowpri bond0 bond0 - ether - -
 
 
This issue will also cause problems during the installation of SFRAC (installsfrac).  The installation will be interrupted because LLT fails to start.  
 

When the following prompt  appears , edit the /etc/llttab file on all the nodes BEFORE answering the following question, otherwise the LLT links may not come up successfully.:

....

   Is the fully qualified hostname of system "vcslx003" ="vcslx003.my.world.com"? [y,n,q,?] (y)

 
 
Edit the /etc/llttab file (from another terminal) and change all the eth-entries for bonded links with the corresponding bonded link name.
 
eg.
Replace entries like this:
 
link bond1 eth-00:21:5a:b0:98:fa - ether - -
link-lowpri bond0 eth-00:21:5a:b0:98:f8 - ether - -
 
With this:
link bond1 bond1 - ether - -
link-lowpri bond0 bond0 - ether - -
 
 

Once this is done for all the nodes, the pending question on the SFRAC installation can then be answered and the installation continued.

 

 

Issue/Introduction

LLT does not work with Linux NIC bonded interfaces upon initial startup in 5.0 MP3
Powered by Wolken Software