Editing a network bond
Follow these steps to edit a network bond to change the bonded interfaces.
To edit a network bond
- From the System topology page on the Flex Appliance Console, click on each of your application instances and verify that the bond is not listed in the IP address and interface pairs field. If the bond is listed for one or more instances, edit the network of each instance to remove the bond. See Editing instance network settings.
You may need to add a different IP address and interface pair if the bond that you want to edit is the only interface that is assigned to the instance. If you do not have another available configured interface, configure an interface with placeholder values that you can use until you complete the edits. See Configuring or editing a network interface.
- Navigate to the Network interfaces page and select the bond that you want to edit.
- Click Edit bond.
- Make the required changes, including the transmit hash policy for bonds in 802.3ad (LACP) mode, and click Save.
Note:
A transmit hash policy change is applied to the running bond without bringing the interface down, so no traffic interruption is expected. If you select Layer 3+4 for a bond that is not in 802.3ad (LACP) mode, the Flex Appliance Console displays a validation error and does not apply the change.
Note:
The Network interfaces page shows the transmit hash policy that is currently active for each 802.3ad (LACP) bond, so you can confirm that a change took effect.
Note:
After you edit a bond, allow up to 30 seconds for link aggregation to stabilize. During this time the bond's shows as Updating on the page. It updates automatically to Up or Down once the bond finishes aggregating, without requiring a page refresh.
New bonds always default to Layer 2, to preserve existing traffic behavior. If a bond's transmit hash policy was manually changed from Layer 2 to Layer 3+4 before you upgrade to a release that includes this feature, the setting is not automatically corrected as part of the upgrade.
To avoid this manual configuration being overwritten, clear it before you upgrade, or re-apply the desired transmit hash policy from the s page after the upgrade completes.