FAQ

How to make NIC redundancy at Baremetal Server

(:Last updated)

Steps to make NIC redundancy at Baremetal Server whose host OS is created with Enterprise Cloud 2.0 official template Red Hat Enterprise Linux 7 image is following.

==================================================
1. Connect same logical network to each physical network device which connected each 2 physical NIC on same plane Baremetal server via Enterprise Cloud 2.0 Cloud computing control panel
==================================================
Please make connection between same logical network and each physical network device which connected each 2 physical NIC on same plane Baremetal server with the procedure which informing at following tutorial. In this case, please specify each same segment type.

In addition, please specify same segment ID about segment ID(VLAN ID) each in the case of using vlan in segment type.

==================================================
2. Make redundant interface and configure IP address to redundant interface on Baremetal server host OS(Red Hat Enterprise Linux 7)
==================================================
Please make interface redundancy with execute following command with Shell on Baremetal server host OS(Red Hat Enterprise Linux 7).

--------------------------------------------------
2-1. Disable IPv4 and IPv6 on physical NIC#1 and #2 which connected to the same plane on Baremetal server
--------------------------------------------------
# nmcli connection modify [physical_connection_name_1] autoconnect on ipv4.method disable ipv6.method ignore
# nmcli connection modify [physical_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2

--------------------------------------------------
2-2. Create bonding interface using physical NIC#1 and #2 connected to the same plane on Baremetal server
--------------------------------------------------
# nmcli connection add type bond con-name [bond_connection_name_1] ifname [bond_interface_name_1] miimon 100 updelay 0 downdelay 0 mode active-backup primary [slave_interface_name_1] # nmcli connection add type bond-slave ifname [slave_interface_name_1] master [bond_interface_name_2] # nmcli connection add type bond-slave ifname [slave_interface_name_2] master [bond_interface_name_2]

※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2
※Please specify the new creating connection name for bonding interface to bond_connection_name_1
※Please specify the new creating bonding interface name to bond_interface_name_1
※Please specify the interface name of physical NIC#1 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_1
This interface becomes to primary physical NIC of bonding interface.
※Please specify to interface name of physical NIC#2 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_2
This interface becomes to secondary physical NIC of bonding interface.
※Please specify bonding interface name to bond_interface_name_2. Accordingly, please specify the same value as "bond_interface_name_1"

--------------------------------------------------
(Please carry out "2-3." in addition in the case of only using "flat" for segment type when connected with logical network in "1.".)
2-3. Manually IP address setting to bonding interface(Please specify the parameters such as the default gateway more as needed.)
--------------------------------------------------
# nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_1]

※Please specify the connection name of bonding interface to bond_connection_name_2.
Accordingly, please specify the same value as "bond_connection_name_1".
※Please specify the IP address assigned to bonding interface with CIDR format to ip_address_1.

--------------------------------------------------
(Please carry out "2-4." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
2-4. Disable IPv4 and IPv6 on bonding interface.
--------------------------------------------------
# nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

※Please specify the connection name of bonding interface to bond_connection_name_2.
Accordingly, please specify the same value as "bond_connection_name_1".

--------------------------------------------------
(Please carry out "2-5." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
2-5. Create VLAN interface using bonding interface
--------------------------------------------------
# nmcli connection add type vlan dev [bond_interface_name_3] con-name [vlan_connection_name_1] ifname [vlan_interface_name] id [vlan_id]

※Please specify the new creating bonding interface name which VLAN interface uses to bond_interface_name_3.
Accordingly, please specify the same value as "bond_interface_name_1".
※Please specify the new creating connection name which is for VLAN interface to vlan_connection_name_1
※Please specify the new creating VLAN interface name to vlan_interface_name.
※Please specify VLAN ID which corresponds to connected logical network to vlan_id.

--------------------------------------------------
(Please carry out "2-6." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
2-6. Manually IP address setting to VLAN interface(Please specify the parameters such as the default gateway more as needed.)
--------------------------------------------------
# nmcli connection modify [vlan_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_2]

※Please specify the connection name of VLAN interface to vlan_connection_name_2.
Accordingly, please specify the same value as "vlan_connection_name_1".
※Please specify the IP address assigned to VLAN interface with CIDR format to ip_address_2.

--------------------------------------------------
2-7. Restarting network(or rebooting OS)
--------------------------------------------------
# systemctl restart network.service
(# shutdown -r now)

--------------------------------------------------

  • ECL2.0
  •  
  • Baremetal Server
  •  

Related Pages

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.