Bonding ModeCopy link

You can edit the bonding mode of the Cohesity cluster bond interfaces. The Cohesity cluster supports these bonding modes:

  • Bonding mode 1 (active-backup): Places one of the interfaces into a backup state. If the active interface fails, the interface in the backup state becomes active. This mode provides fault tolerance. By default, bonding mode 1 is configured on the Cohesity cluster bond interfaces.

  • Bonding mode 4 (LACP 802.3ad): This mode is also known as Dynamic Link Aggregation mode. It creates aggregation groups with the same speed and duplex settings.

The physical and logical networking components in Cohesity cluster are illustrated in this image.

Edit the Bonding ModeCopy link

This section provides you steps to change the Cohesity cluster configuration and local ifcfg files to set the bonding mode to LACP.

On the Free Node

Perform these steps on the free node:

  1. Start the Cohesity CLI remotely or locally as described in the Cohesity CLI Reference Guide.

    Specify the static IPv4 or IPv6 address of one of the Cohesity nodes. For example, if the CLI was downloaded to a Linux system, you might use the following command. Provide a Cohesity cluster username and password. 

    ./iris_cli -server 172.16.3.101 -username=admin

  2. Run this command:

    • To update the bonding mode from 1 to 4:

      iris_cli interface update interface-name=bond0 bonding-mode=4 xmit-hash-policy=1

    • To update the bonding mode from 4 to 1:

      iris_cli interface update interface-name=bond0 bonding-mode=1

  3. To verify the node configuration and connectivity, perform these steps:

    • Run this command and verify the output if bonding mode is configured on the bond interface:

      cat /proc/net/bonding/bond<x>

      Where x is the bond interface.

      Example:

      cat /proc/net/bonding/bond0

    • Ping the gateway IP as follows:

      ping <gateway IP address>

On the Cohesity cluster

Perform these steps on one of the nodes in the Cohesity cluster:

  1. Start the Cohesity CLI remotely or locally as described in the Cohesity CLI Reference Guide.

    Specify the static IPv4 or IPv6 address of one of the Cohesity nodes. For example, if the CLI was downloaded to a Linux system, you might use the following command. Provide a Cohesity cluster username and password. 

    ./iris_cli -server 172.16.3.101 -username=admin

  2. Stop the cluster services running on the nodes before you edit the bonding mode:

    admin> cluster stop

  3. Check the cluster status:

    admin> cluster status

    Verify the cluster status in the command output:

    SERVICE STATE SYNC: DONE 
     
    CLUSTER ACTIVE OPERATION:
     
    CLUSTER HEAL STATUS: NORMAL

  4. Set the existing bonding mode:

    iris_cli interface update interface-name=<interface_group_name> bonding-mode=<x> xmit-hash-policy=1

    Example:

    iris_cli interface update interface-name=intf_group1 bonding-mode=4 xmit-hash-policy=1

    or

    iris_cli interface update interface-name=intf_group1 bonding-mode=1

  5. Change the upstream switch ports to LACP or move the network cable connections to LACP configured ports and wait for LACP on the switch and bond0 interface to come up.

  6. To verify the node configuration and connectivity, perform these steps:

    • Run this command and verify the output if bonding mode is configured on the bond interface:

      cat /proc/net/bonding/bond<x>

      Where x is the bond interface.

      Example:

      cat /proc/net/bonding/bond0

    • Ping the gateway IP as follows:

      ping <gateway IP address>

  7. Start the cluster services:

    admin> cluster start

  8. Check the cluster status:

    admin> cluster status

    Verify the cluster status in the command output:

    SERVICE STATE SYNC: DONE 

    CLUSTER ACTIVE OPERATION:

    CLUSTER HEAL STATUS: NORMAL

  9. Verify the updated bonding mode:

    admin> interface list

Create Cross-Bonding InterfaceCopy link

Create Cross-Bonding for a Primary Interface

Perform these steps on one of the nodes in the cluster:

  1. Connect the node in the Cohesity cluster to the IPMI interface via the IPMI Console. For details on how to configure IPMI, see Manage IPMI Configuration.

  2. Run the following command in the IPMI console to get a list of all the connected NIC ports and check the 10GbE link.

    list_all_nic_ports.sh 
    NODE ID : 181140266786854
    NODE IP : 10.1.4.16

    Sample Output

    PORT NAME STATE MAC
I/O Module Slot Port 1 ens802f0 UP a4:bf:01:41:a0:26
I/O Module Slot Port 2 ens802f1 UP a4:bf:01:41:a0:27

Port Type: 1GbE
======================================================
PORT NAME STATE MAC
Embedded 1G NIC Port 1 eno1 DOWN a4:bf:01:21:7e:c8
Embedded 1G NIC Port 2 eno2 DOWN a4:bf:01:21:7e:c9
===============================

  3. Run the following command to stop a single node on a Cohesity cluster:

    node_stop.sh script

    The node_stop.sh script is located at /home/cohesity/bin/

  4. In the ifcfg-ens1f1 file, replace MASTER=bond0 with MASTER=bond1.

    The ifcfg-ens1f1 file is located at /etc/sysconfig/network-scripts/.

  5. In the ifcfg-ens7f1 file, replace MASTER=bond0 with MASTER=bond1.

    The ifcfg-ens7f1 file is located at /etc/sysconfig/network-scripts/.

  6. Restart the node.

  7. Use the following command to verify that the cross-bonding for the primary interface has been successfully created.

    List_all_nic_ports.sh

  8. Repeat steps 1 to 7 for all the nodes in the Cohesity cluster.

Create Cross-Bonding for a Secondary Interface

Follow these steps to create Cross-Bonding for a secondary interface. Perform these steps on one of the nodes in the cluster:

  1. Run the following command in the IPMI console to get a list of all the connected NIC ports and check the 10GbE link.

    list_all_nic_ports.sh 
    NODE ID : 181140266786854
    NODE IP : 10.1.4.16

  2. Run the following command to verify the bond interface and its associated physical interface:

    ip addr

    In this sample output, eno1 and eno2 are bond slaves of bond0, and eno3 and eno4 are bond slaves of bond1.

  3. Remove the bond interface_group.

    iris_cli interface-group delete group-name=<name of the interface group>

  4. Remove the bond to free the interfaces.

    iris_cli bond delete bond-interface=<name of the bond>

  5. Place the node in maintenance mode.

    iris_cli node update id=<ID of the node> maintenance-mode=true

  6. Use the following CLI command to update the cross-bonding interface for bond0 and bond1.

    iris_cli bond update bond-interface=<name of the bond interface> bond-slave-interface=<name of the bond slave interface>

    Example:

    Commands that set eno1 and eno3 as salve-interface bond0 and eno2 and eno4 as slave-interface for bond1:

    iris_cli bond update bond-interface=bond0 bond-slave-interface=eno1
    iris_cli bond update bond-interface=bond1 bond-slave-interface=eno4
    iris_cli bond update bond-interface=bond0 bond-slave-interface=eno1,eno3
    iris_cli bond update bond-interface=bond1 bond-slave-interface=eno2,eno4

  7. Identify the ports that need to be part of the respective bond interface and create bond interfaces using the following command:

    iris_cli bond create bond-interface=<name of the bondinterface> bond-slaveinterface=<name of the bond slave interface>

    Example

    iris_cli bond create bond-interface=bond0 bond-slaveinterface=eno3,eno4
    iris_cli bond create bond-interface=bond1 bond-slaveinterface=eno1,eno2

Delete Cross-Bonding Interface

To delete the cross-bonding interfaces:

  1. Run the following command to delete the interface groups that are associated with the cross-bonding interfaces:

    iris_cli interface-group delete group-name=<name of the interface group>

    Deleting an interface group fails if the underlying network bonding interface has static IPs, VIPs or VLANs configured.

  2. Run the following commands to delete the cross-bonding interfaces:

    iris_cli bond delete bond-interface=<name of the bond interface>

    Example

    iris_cli bond delete bond-interface=bond1

  3. To verify the delete is successful, check if the ifcfg-bond<x> file is deleted/not present in the /etc/sysconfig/network-scripts/ folder.

    Example: Ensure the ifcfg-bond1 file (where 1 is the bond number) is not in the network-scripts folder.