Changing the Bond Mode When Front- and Back-End Storage Shares a Network

Hi team, here's a new case.

Problem Symptom

Change the NIC bond mode when the front- and back-end storage shares a network.

Problem Diagnosis

Scenario 1: To change the bond mode from bond1 to bond4, you need to create and configure a trunk on the switch.

Scenario 2: To change the bond mode from bond4 to bond1, you need to modify the switch configuration and delete the trunk information related to bond4.

Causes

Based on site requirements, you need to change the NIC bond mode when the front- and back-end storage shares a network.

Solution

Scenario 1: Change the bond mode from bond4 to bond1.

1. Modify the switch configuration.

   1. Log in to the switch and run the following commands to view the eth-trunk information of the switch. Note the mapping between the trunk name and ActorPortName in the command output.

      system-view

      disp eth-trunk

      

   2. Query the maintenance document applicable to the current environment, query the cable connection information between storage NICs on all FSA nodes and the switch, and record the information about switch ports that connect to FSA nodes.

   3. In the command output in 1.a, locate the trunk information about the storage NIC of each FSA node in the ActorPortName column based on the switch port information obtained in step 2.

   4. Delete the trunk information of all FSA nodes from the switch.

      Run the following commands to delete a trunk:

      interface Name of a trunk

      undo trunkport Switch port name

      undo trunkport Switch port name

      commit

      quit

      

2. Log in to the active FSM node using the FSM floating IP address, switch to user root, and run the following command to change the bond mode recorded in the FSM configuration file:

   sed -i 's!bond4</bond_mode>!bond1</bond_mode>!g' /opt/omm/oms/workspace/webapps/dsware/WEB-INF/SystemConfiguration.xml

3. Run the following command on the active FSM node to restart the Tomcat service:

   su - omm -c restart_tomcat

   

4. Log in to an FSA node and run the ip addr command to query the name of the NIC used on the current storage network.

5. Run the following command on the FSA node to modify the bond mode in the storage NIC configuration:

   sed -i 's!mode=4 miimon=100 lacp_rate=fast arp_validate=0 xmit_hash_policy=layer3+4!mode=1 miimon=100!g' /etc/sysconfig/network-scripts/ifcfg-NIC name

   

6. Run the following commands in sequence to restart the NIC:

   ifdown NIC name

   ifup NIC name

   

7. Run the following command to restart the dsware_agent process:

   /etc/init.d/dswareAgent restart

8. Perform steps 4 to 7 on other FSA nodes.

Scenario 2: Change the bond mode from bond1 to bond4.

1. Modify the switch configuration.

   If the storage network ports form bond4, you need to configure a trunk. For details, see Configuring Switches in FusionStorage Block Storage Product Documentation.

2. Log in to the active FSM node using the FSM floating IP address, switch to user root, and run the following command to change the bond mode in the FSM configuration file:

   sed -i 's!bond1</bond_mode>!bond4</bond_mode>!g' /opt/omm/oms/workspace/webapps/dsware/WEB-INF/SystemConfiguration.xml

3. Run the following command on the active FSM node to restart the Tomcat service:

   su - omm -c restart_tomcat

   

4. Log in to an FSA node and run the ip addr command to query the name of the NIC used on the current storage network.

5. Run the following command on the FSA node to modify the bond mode in the storage NIC configuration:

   sed -i 's!mode=1 miimon=100!mode=4 miimon=100 lacp_rate=fast arp_validate=0 xmit_hash_policy=layer3+4!g' /etc/sysconfig/network-scripts/ifcfg-NIC name

   

6. Run the following commands in sequence to restart the NIC:

   ifdown NIC name

   ifup NIC name

   

7. Run the following command to restart the dsware_agent process:

   /etc/init.d/dswareAgent restart

8. Perform steps 4 to 7 on other FSA nodes.