Network

Help users solve network problems, covering VPC, L2 Networks, IP subnets, domain name services, security groups, resilient NICs, EIP, load balancing content.

What does Network Management cover?

It mainly includes VPC, L2 Network, IP subnet, reserved IP, security group, EIP, resilient NIC, key, domain name service and other aspects.

What rates of network interfaces does the product support?

Support 40G, Gigabit, 10 Gigabit and other rates of network interfaces, the actual production environment recommended gigabit or more.

Will the management network and data network be affected if they are put together?

It is recommended to separate the management network and data network to improve security and reasonable network load sharing. If the network resources are insufficient, they can be put together.

Will there be any conflict between DHCP service provided by the product and the current DHCP in the server room?

The DHCP service of OneCloud does not conflict with the DHCP service already configured in the current server room. The DHCP broadcast message of OneCloud only takes effect for the computing resources of the nano management. However, the network segment used by the servers inside OneCloud must not overlap with the IP range already in use within the current environment, and if it does, IP address conflicts may occur.

Does the same Layer 3 network support setting different subnet masks and gateways?

Yes, administrators can plan and set up multiple IP subnets.

If the Linux server NIC interface name is not eth0, eth1… how can I change the NIC name to eth0, etc.?

Since CentOS 7, Ubuntu 14.04LTS in order to make the NIC name persistently displayed before and after hardware changes (e.g. adding or subtracting NICs), the NIC will be named using the NIC’s BIOS address, so that the NIC name will no longer be eth0, eth1… but will be displayed as ens192, enp1s, etc. . The following is an example of how to turn off the persistent naming of NICs in CentOS 7.

modify /etc/default/grub file, add the parameter “net.ifnames = 0 biosdevname = 0” to GRUB_CMDLINE_LINUX.

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release . *$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=auto rhgb quiet intel_iommu=on iommu=pt vfio_iommu_type1.allow_unsafe_interrupts=1 rdblacklist= nouveau nouveau.modeset=0 net.ifnames=0 biosdevname=0"
GRUB_DISABLE_RECOVERY="true"

After the modification, execute the following command to generate the boot file.
1. If the server is BIOS-booted, execute the following command.
```
$ grub2-mkconfig -o /boot/grub2/grub.cfg
```
1. If the server is UEFI booted, execute the following command.
```
$ grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
```
After rebooting the system, check if the MAC corresponding NIC name has been changed to eth0.