Configuring the back-end interface configuration files for bonding

Deploying an HCP VM System on KVM

Version

9.6.x

Audience

anonymous

Part Number

MK-94HCP009-07

To bridge the back-end network, configure the host operating system to specify the physical network interfaces that will constitute the bond in the back-end interface configuration. In this example, the first back-end network configuration file is named ifcfg-eno2, and the second back-end network configuration file is named ifcfg-eno4.

Note: Do not delete information that is specific to your system network configuration.

Enter the following command to open the network-scripts folder:
cd /etc/sysconfig/network-scripts/
Enter the following command to access the first back-end network configuration file:
vi ifcfg-eno2
Press I to edit the file.
Replace the existing contents with the following text:
```
NAME=Bond-device-Name
DEVICE=Device-Name
ONBOOT=yes
MASTER=Back-End-Bond-File
SLAVE=yes
ETHTOOL_OPTS=""
```
Note: Do not delete information that is particular to your system network configuration.

Here is an example of the completed file:
```
NAME=bond1-en02
DEVICE=eno2
ONBOOT=yes
MASTER=bond1
SLAVE=yes
ETHTOOL_OPTS=""
```
Press Esc.
Enter the following command to save and exit the file:
:wq
Enter the following command to access the second back-end network configuration file:
vi ifcfg-eno4
Press I to edit the file.
Replace the existing contents with the following text:
```
NAME=Bond-device-Name
DEVICE=Device-Name
ONBOOT=yes
MASTER=back-end-Bond-File
SLAVE=yes
ETHTOOL_OPTS=""
```
Note: Do not delete information that is particular to your system network configuration.

Here is an example of the completed file:
```
NAME=bond1-en04
DEVICE=eno4
ONBOOT=yes
MASTER=bond1
SLAVE=yes
ETHTOOL_OPTS=""
```
Press Esc.
Enter the following command to save and exit the file:
:wq