Skip to main content
Version: v25.07.31

High Availablity Troubleshooting

This document addressed the troubleshooting steps about high availability HA issues. We will detail the common symptoms, overview the system, and describe the commands that have been used for diagnostics.

Troubleshooting steps​

Cloud configuration verification​

This section details how to check the configurations made in the cloud. The commands below can be used to verify the cloud configuration.

Access the CE Terminal​

Follow these steps to gain access to the CE device via the Command Line Interface (CLI).

sudo su -

The sudo su - command starts a shell session with superuser privileges, enabling execution of tasks that require elevated permissions, such as networking and system configuration.

Review Network Configuration​

To view the complete network interface configuration of the device, run the following command. This will display the contents of the network configuration file.

cat /etc/config/network

Example Response​

  • Master Node:-
root@Demo_CE:~# cat /etc/config/network 

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals
	option packet_steering '1'

config interface 'eth0'
	option device 'eth0'
	option default_wan '1'
	option disabled '0'
	option proto 'static'
	option ipaddr '172.20.10.6'
	option netmask '255.255.255.0'
	list dns '172.20.10.1'

config interface 'eth3'
	option device 'eth3'
	option proto 'static'
	option netmask '255.255.255.0'
	option disabled '0'
	option ipaddr '172.30.1.2'

config rule
	option priority '901'
	option lookup 'main'

config interface 'wlm0'
	option disabled '1'
	option proto '3g'
	option pppname 'wlm0'
	option device 'ttyUSB0'
	option apn 'comgt'
	option ipv6 '0'
	option delegate '0'
	option metric '2'
	option ip4table '2'

config route 'f85c71f21c3040bdb4abcd168fa8e900'
	option target '172.30.2.0'
	option netmask '255.255.255.0'
	option gateway '172.31.0.2'
	option table 'main'
	option proto 'static'
	option metric '1'
	option interface 'br25'

config route '1777530465de4eafada07376f1239abf'
	option target '172.30.1.0'
	option netmask '255.255.255.0'
	option gateway '172.31.0.1'
	option table 'main'
	option proto 'static'
	option metric '1'

config interface 'eth1'
	option proto 'static'
	option device 'eth1'
	option ipaddr '100.100.100.1'
	option netmask '255.255.255.0'
	list dns '172.20.10.1'
  • Backup Node:-
root@Backup_node:~# cat /etc/config/network 

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals
	option packet_steering '1'

config interface 'eth0'
	option device 'eth0'
	option default_wan '1'
	option disabled '0'
	option proto 'static'
	option ipaddr '172.20.10.8'
	option netmask '255.255.255.0'
	list dns '172.20.10.1'

config interface 'eth3'
	option device 'eth3'
	option proto 'static'
	option netmask '255.255.255.0'
	option disabled '0'
	option ipaddr '172.30.1.1'

config rule
	option priority '901'
	option lookup 'main'

config interface 'wlm0'
	option disabled '1'
	option proto '3g'
	option pppname 'wlm0'
	option device 'ttyUSB0'
	option apn 'comgt'
	option ipv6 '0'
	option delegate '0'
	option metric '2'
	option ip4table '2'

config route 'f85c71f21c3040bdb4abcd168fa8e900'
	option target '172.30.2.0'
	option netmask '255.255.255.0'
	option gateway '172.31.0.2'
	option table 'main'
	option proto 'static'
	option metric '1'
	option interface 'br25'

config route '1777530465de4eafada07376f1239abf'
	option target '172.30.1.0'
	option netmask '255.255.255.0'
	option gateway '172.31.0.1'
	option table 'main'
	option proto 'static'
	option metric '1'

config interface 'eth1'
	option proto 'static'
	option device 'eth1'
	option ipaddr '100.100.100.2'
	option netmask '255.255.255.0'
	list dns '172.20.10.1'

This command will show the network configuration. Check that the interface, IP address, and other network settings are properly configured on both nodes. Also, check that the virtual IP address is on the same subnet as the real IP address of the nodes.