We're going to explain how to configure your network interface. Before we start, this guide is written using CentOS 7 as an example, it might be different on other Linux distributions. The first thing you should do is navigate to:
/etc/sysconfig/network-scripts/

For a single network card

When the dedicated server only has one network card, the network card configuration should be as following:

This file can be reached by opening it using any text editor. In this case:

vi /etc/sysconfig/network-scripts/ifcfg-enp1s0f0

If you decide to use the single network card method (not bond0), configure only NIC A, as NIC B will work only as bond0 redundancy.


Network redundancy

Some of our dedicated servers have network redundancy. For that, you need to configure the bond interface.

vi /etc/sysconfig/network-scripts/ifcfg-bond0

After you create the Bond interface both network interfaces should be as following:

vi /etc/sysconfig/network-scripts/ifcfg-enp1s0f0 and vi /etc/sysconfig/network-scripts/ifcfg-enp1s0f1

After both network cards have been configured a command needs to be run modprobe --first-time bonding
and restarting network service by running
systemct restart network.service.

Important information: BONDING_OPTS="mode=4 miimon=100 lacp_rate=fast" this option is required for our system to work, changing the mode from 4 to 3 might lead to packet loss as an example. Our recommendation to use it as we provide it!

Extra information

In some of our locations dedicated server will be given /29 and in other /30 and due to this the mask of your server will be different. The prefix can be checked by running
ip a
command and checking the netmask (/29: 255.255.255.248, /30: 255.255.255.252) or contacting our support.

Additional recommendations from us. If your system is running the NetworkManager service, we recommend stopping it. it can be done by running
systemctl stop NetworkManager.service as well as
systemctl disable NetworkManager.service

If you don't require network redundancy you should only set up the first network card. If you set up on the second network card, it will not work, as it only works on the bonded interface.

A short explanation of network interface configuration files.
BOOTPROTO - Dictates what protocol is used on boot-time.

DEVICE - Device name.

HWADDR - MAC address of network card.

IPADDR - IP address used by the network card.

NETMASK - Netmaks used by the network card.

GATEWAY - Gateway IP used by the network card.

ONBOOT - Dictates if the network card starts on boot.

TYPE - The type of network interface device.

DNS1 - Primary DNS IP address.

DNS2 - Secondary DNS IP address.

USERCTL - Directs that only root or all system users can control the device.

MASTER - Show what device has master control.

SLAVE - Dictates if the stand-alone device or running as a slave device.

If you have any other questions or don't understand parts of this article, feel free to contact our support at support@heficed.com!

Did this answer your question?