InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux

To configure private heartbeat links

1. Choose one of the following options at the installer prompt based on whether you want to configure LLT over Ethernet or LLT over UDP or LLT over TCP or LLT over RDMA.

   • Option 1: Configure the heartbeat links using LLT over Ethernet (answer installer questions)

     Enter the heartbeat link details at the installer prompt to configure LLT over Ethernet.

     Skip to step 2.

   • Option 2: Configure the heartbeat links using LLT over UDP (answer installer questions)

     Make sure that each NIC you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over UDP. If you had not already configured IP addresses to the NICs, the installer provides you an option to detect the IP address for a given NIC.

     Note:

     Ensure that the interface that is used by the LLT links does not have any other IP in the same subnet were the LLT links are configured. Otherwise, the cluster may behave unpredictably.

     Skip to step 3.

   • Option 3: Configure the heartbeat links using LLT over TCP (answer installer questions)

     Make sure that the NIC you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over TCP. If you had not already configured IP addresses to the NICs, the installer provides you an option to detect the IP address for a given NIC.

     Skip to step 4.

   • Option 4: Configure the heartbeat links using LLT over RDMA (answer installer questions)

     Make sure that each RDMA enabled NIC (RNIC) you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over RDMA. If you had not already configured IP addresses to the RNICs, the installer provides you an option to detect the IP address for a given RNIC.

     Skip to step 5.

   • Option 5: Automatically detect configuration for LLT over Ethernet

     Allow the installer to automatically detect the heartbeat link details to configure LLT over Ethernet. The installer tries to detect all connected links between all systems.

     Make sure that you activated the NICs for the installer to be able to detect and automatically configure the heartbeat links.

     Skip to step 8.

     Note:

     Option 5 is not available when the configuration is a single node configuration.

2. If you chose option 1, enter the network interface card details for the private heartbeat links.

   The installer discovers and lists the network interface cards.

   You must not enter the network interface card that is used for the public network (typically eth0.)

   Enter the NIC for the first private heartbeat link on sys1:
   [b,q,?] eth1
   eth1 has an IP address configured on it. It could be a 
   public NIC on sys1.
   Are you sure you want to use eth1 for the first private 
   heartbeat link? [y,n,q,b,?] (n) y
   Would you like to configure a second private heartbeat link?
   [y,n,q,b,?] (y)   
   Enter the NIC for the second private heartbeat link on sys1:
   [b,q,?] eth2
   eth2 has an IP address configured on it. It could be a 
   public NIC on sys1.
   Are you sure you want to use eth2 for the second private 
   heartbeat link? [y,n,q,b,?] (n) y
   Would you like to configure a third private heartbeat link?
   [y,n,q,b,?](n) 

   Do you want to configure an additional low priority heartbeat 
   link? [y,n,q,b,?] (n)

3. If you chose option 2, enter the NIC details for the private heartbeat links. This step uses examples such as private_NIC1 or private_NIC2 to refer to the available names of the NICs.

   Enter the NIC for the first private heartbeat link on sys1: [b,q,?]
   private_NIC1
   Some configured IP addresses have been found on 
   the NIC private_NIC1 in sys1,
   Do you want to choose one for the first private heartbeat link? [y,n,q,?] (y)
   Please select one IP address:
        1)  192.168.0.1/24
        2)  192.168.1.233/24
        b)  Back to previous menu
   
   Please select one IP address: [1-2,b,q,?] (1)
   Enter the UDP port for the first private heartbeat link on sys1:
   [b,q,?] (50000)
   
   Enter the NIC for the second private heartbeat link on sys1: [b,q,?]
   private_NIC2
   Some configured IP addresses have been found on the 
   NIC private_NIC2 in sys1,
   Do you want to choose one for the second 
   private heartbeat link? [y,n,q,?] (y)
   Please select one IP address:
        1)  192.168.1.1/24
        2)  192.168.2.233/24
        b)  Back to previous menu
   
   Please select one IP address: [1-2,b,q,?] (1) 1
   Enter the UDP port for the second private heartbeat link on sys1:
   [b,q,?] (50001)
   
   Would you like to configure a third private heartbeat
   link? [y,n,q,b,?] (n)
   
   Do you want to configure an additional low-priority heartbeat
   link? [y,n,q,b,?] (n) y
   
   Enter the NIC for the low-priority heartbeat link on sys1: [b,q,?]
   private_NIC0
   Some configured IP addresses have been found on 
   the NIC private_NIC0 in sys1,
   Do you want to choose one for the low-priority 
   heartbeat link? [y,n,q,?] (y)
   Please select one IP address:
        1)  10.200.59.233/22
        2)  192.168.3.1/22
        b)  Back to previous menu
   
   Please select one IP address: [1-2,b,q,?] (1) 2
   Enter the UDP port for the low-priority heartbeat link on sys1: 
   [b,q,?] (50010)

4. If you chose option 3, enter the NIC details for the private heartbeat link.

   This step uses an example such as private_NIC1 to refer to the available name of the NIC.

   Enter the NIC for the private heartbeat link on sys1: [b,q,?] (eth1)
   private_NIC1
   Some configured IP addresses have been found on
   the NIC private_NIC1 in sys1,
   Do you want to choose one for the private
   heartbeat link? [y,n,q,?] (y) y
   Please select one IP address:
   1) 192.168.1.1/24
   2) 192.168.2.1/24
   b) Back to previous menu
   
   Please select one IP address: [1-2,b,q,?] (1)
   Enter the TCP port for the first private heartbeat link on sys1:
   [b,q,?] (50000)
   

5. If you chose option 4, choose the interconnect type to configure RDMA.

   1)  Converged Ethernet (RoCE)
   2)  InfiniBand
   b)  Back to previous menu
   
   Choose the RDMA interconnect type [1-2,b,q,?] (1) 2
   

   The system displays the details such as the required OS files, drivers required for RDMA , and the IP addresses for the NICs.

   A sample output of the IP addresses assigned to the RDMA enabled NICs using InfiniBand network. Note that with RoCE, the RDMA NIC values are represented as eth0, eth1, and so on.

   System    				RDMA NIC          IP Address
   =================================================================
   sys1           ib0               192.168.0.1
   sys1           ib1               192.168.3.1
   sys2           ib0               192.168.0.2
   sys2           ib1               192.168.3.2
   

6. If you chose option 4, enter the NIC details for the private heartbeat links. This step uses RDMA over an InfiniBand network. With RoCE as the interconnect type, RDMA NIC is represented as Ethernet (eth).

   Enter the NIC for the first private heartbeat 
   link (RDMA) on sys1: [b,q,?] <ib0>
   
   Do you want to use address 192.168.0.1 for the 
   first private heartbeat link on sys1: [y,n,q,b,?] (y)
   
   Enter the port for the first private heartbeat 
   link (RDMA) on sys1: [b,q,?] (50000) ?
   
   Would you like to configure a second private 
   heartbeat link? [y,n,q,b,?] (y)   
   Enter the NIC for the second private heartbeat link (RDMA) on sys1: 
   [b,q,?] (ib1) 
   
   Do you want to use the address 192.168.3.1 for the second  
   private heartbeat link on sys1: [y,n,q,b,?] (y) 
   Enter the port for the second private heartbeat link (RDMA) on sys1: 
   [b,q,?] (50001)
   
   Do you want to configure an additional low-priority heartbeat link?
   [y,n,q,b,?] (n)

7. Choose whether to use the same NIC details to configure private heartbeat links on other systems.

   Are you using the same NICs for private heartbeat links on all 
   systems? [y,n,q,b,?] (y)

   If you want to use the NIC details that you entered for sys1, make sure the same NICs are available on each system. Then, enter y at the prompt.

   If the NIC device names are different on some of the systems, enter n. Provide the NIC details for each system as the program prompts.

   For LLT over UDP and LLT over RDMA, if you want to use the same NICs on other systems, you must enter unique IP addresses on each NIC for other systems.

8. If you chose option 5, the installer detects NICs on each system and network links, and sets link priority.

   If the installer fails to detect heartbeat links or fails to find any high-priority links, then choose option 1 or option 2 to manually configure the heartbeat links.

   See step 2 for option 1, or step 3 for option 2, or step 4 for option 3, or step5 for option 4

9. Enter a unique cluster ID:

   Enter a unique cluster ID number between 0-65535: [b,q,?] (60842)

   The cluster cannot be configured if the cluster ID 60842 is in use by another cluster. Installer performs a check to determine if the cluster ID is duplicate. The check takes less than a minute to complete.

   Would you like to check if the cluster ID is in use by another 
   cluster? [y,n,q] (y)

10. Verify and confirm the information that the installer summarizes.