Replace a ServiceNav Box Ubuntu 16.04 with a ServiceNav Box 4.17 Ubuntu 20.04

On the page

Do you need help?


Use this procedure to migrate an Ubuntu 16.04 ServiceNav Box to a ServiceNav Box deployed with the master 4.17.1 - Ubuntu 20.04 LTS.

The principle is as follows:

  • create a new ServiceNav Box
  • from the new ServiceNav Box, run a migration script that copies the data from the old ServiceNav Box, including its network configuration, turns it off and restarts the new ServiceNav Box


Creating the new ServiceNav Box

Get the ServiceNav Box master in the right format from (contact assistance in order to obtain the identifiers)

Import the master into the virtualization environment.

Configure the network for this ServiceNav Box.

Detailed steps here.

Prepare the old ServiceNav Box

La copie des données se fait depuis la nouvelle ServiceNav Box sous SSH, sur le port habituel. Ce port doit donc être ouvert sur l’ancienne ServiceNav Box, ce qui doit être le cas si les deux ServiceNav Box sont sur le même réseau LAN.

Pour tester que le port de connexion SSH habituel est bien ouvert sur l’ancienne ServiceNav Box, exécuter la commande suivante sur la nouvelle ServiceNav Box :

telnet <IP ancienne SNB> <port SSH>

In the opposite case, modify the /etc/init.d/ file on the old ServiceNav Box and reload this file.


Execute the migration

Connect with an SSH client to the new ServiceNav Box.

Run the following command while logged in with the user root:

/usr/local/nagios/bin/ --host  -u coadmin -p  --halt-remote --reboot

Online help for the command

/usr/local/nagios/bin/ -host [host] -u [user] -p [password] [options]

-host Remote box hostname (required).
–port Remote box port
-timeout Connect timeout in seconds (default: 10)
-u, -user Username used to connect to remote box (default: coadmin).
-p, -password Password used to connect to remote box (required).
-o, -output Filepath to log file (default: importConfigurationFromBox.log).
-halt-remote Halt remote box upon operation success (default: false).
-reboot Reboot this host upon operation success (default: false).

Post-migration operations

Reconnect to the new SNB and restart remoteOperationBox : 

service remoteOperationBox restart

Restarting Nagios :

service nagios restart

Reload the configuration of the supervision for SNB from the ServiceNav website.

Test the correct NTP configuration:

ntpq -np

Go back to the email configuration :

dpkg-reconfigure exim4-config

Test sending an email:

echo "mail from snb" | mail -s "mail from snb"

If the old ServiceNav Box was used as a ServiceNav agent feedback collector, the port opposite, which is closed by default, should be opened:

  1. Edit the file /etc/init.d/
  2. Uncomment the line : iptables -A INPUT -p tcp -dport $PORT_NSCA -j ACCEPT
  3. Execute : /etc/init.d/

Restart the snmp service:

service snmpd restart

Vérifier la bonne remontée des données de supervision sur le website ServiceNav.

Important - version 4.17.0 Once the new ServiceNav Box is linked to ServiceNav, go to Configuration > Box, select the ServiceNav Box and click on "Start Migration", in order to upgrade it to version 4.17.1

Changing the password of the user coadmin

Under the coadmin user, do the command


follow the indications to indicate the password of the coadmin account that the script cannot modify for security reasons.

You may also be interested in

servicenav hyperV1

Commissioning of a ServiceNav Box

Setting up a proxy on a ServiceNav Box

IMG 0006

Configure Exim emailing with Microsoft Office365


Welcome to ServiceNav!

Do you need some help? More information about our products? Write to us!
You have taken note of our privacy policy.
We use cookies to ensure the best experience on our site. If you continue to use this site, we will assume that you are satisfied with it.

Reserve your place

You have taken note of our privacy policy.