Stuck with SolusVM : Network connectivity is lost after VPS restart? We can help you.
Solus Virtual Manager (SolusVM) is a powerful GUI based VPS management system with full OpenVZ, Linux KVM, Xen Paravirtualization and Xen HVM support.
Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.
Today we will see how our Support Engineers fix this for our customers.
SolusVM : Network connectivity is lost after VPS restart
Usually, Network looses connectivity after VPS restart.
CentOS 7/8 looses IPv6 connectivity, Ubuntu 18/20 looses both IPv4 and IPv6 connectivity.
Inside a VPS IPv6 address ip a command shows the following status for IPv6 address:
inet6 2001:db8:f61:a1ff:0:0:0:80/64 scope global tentative dadfailed
What causes SolusVM Network connectivity restart issue?
VPS sends Duplicate Address Detection(DAD) request.
CR receives the request on br-routed interface and responds that there is such IPv6 address.
VPS receives the response from br-routed and turns the IPv6 address off.
How to resolve it?
Today, let us go through the simple steps followed by our Support Techs to resolve this error.
- Firstly, connect to CR via SSH
- Then, run the command:
# ovs-vsctl set bridge br-routed stp_enable=true
In order for settings to apply on reboot and network or network interface restart it is necessary to modify the interface configuration file on CR.
On Debian 10, Ubuntu 18, Ubuntu 20 CR modify the configuration file /etc/network/interfaces for br-routed part with the following content:
… auto br-routed allow-ovs br-routed allow-hotplug br-routed iface br-routed inet manual ovs_type OVSBridge ovs_extra set bridge br-routed stp_enable=true …
On Centos 7/8 CR modify the file /etc/sysconfig/network-scripts/ifcfg-br-routed with the following content:
# Generated by solus DEVICE=br-routed ONBOOT=yes NM_CONTROLLED=no TYPE=OVSBridge DEVICETYPE=ovs OVS_EXTRA=”set bridge br-routed stp_enable=true”
[Need assistance with SolusVM error?We can help you]
In short, today we saw how our Support Techs resolved Network connectivity issue.