Replacing an Ubuntu 12.04 ServiceNav Box with a ServiceNav 4.0 Box under Ubuntu 16.04

On the page

Need some help?


Use this procedure to migrate a Ubuntu 12.04 ServiceNav Box to a ServiceNav Box 4.0 and higher.

The principle is as follows:

  • create a new ServiceNav Box following the usual procedure,
  • from the new ServiceNav Box, run a migration script that copies the data from the old ServiceNav Box including its network configuration, shuts down the old ServiceNav Box and restarts the new ServiceNav Box

Creation of the new ServiceNav Box

Retrieve the ServiceNav Box master in the right format, from the site (contact support to get credentials)

Import the master to the virtualization environment.

Configure the network for this ServiceNav Box.

Detailed steps hereto step 2.3.2.

Preparing the old ServiceNav Box

The copy of the data is done from the new ServiceNav Box under SSH on the TCP/22 port. This port must therefore be open on the old ServiceNav Box, which must be the case if both ServiceNav Boxes are on the same LAN.

To test that the TCP/22 port is open on the old ServiceNav Box, run the following command on the new ServiceNav Box: telnet 22.

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

Perform migration

Connect to the new ServiceNav Box using an ssh client.

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

/usr/local/nagios/bin/ --host  -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 (default: 22).
-timeout Connect timeout in seconds (default: 10)
-u, -user Username used to connect to remote box (default: root).
-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 steps

Reconnect to the new SNB and restart remoteOperationBox : service remoteOperationBox restart.

Restarting Nagios : nagios restart service

Reload the monitoring configuration for SNB from the ServiceNav UI.

Test the correct NTP configuration : ntpq -np

Switch back to the mailbox configuration : dpkg-reconfigure exim4-config

Test the sending of an email: echo " mail from snb " | mail -s " mail from snb "

If the old ServiceNav Box was used as a ServiceNav agent collector, the default closed port 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/

If inventory counts were taking place on the old ServiceNav Box, check the configuration of the new ServiceNav Box by running this procedure :

Restart the snmp service: snmpd restart service

Verify that the monitoring data is correctly uploaded to the ServiceNav website.



This may also be of interest to you

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

Setting up a proxy on a ServiceNav Box

servicenav hyperV1

Deploying a ServiceNav Box


Welcome to ServiceNav!

Need help? More information about our products? Write to us!
You have taken note of our privacy policy.


While the epidemic lasts, ensure the availability and performance of your IT services for teleworking, with ServiceNav!

Following the government's call to mobilize to help businesses overcome the current health and economic context, we help you, free of charge, to ensure the complete monitoring of your teleworking environments: VPN, VDI, Teams, Skype Enterprise, Citrix... Objectives: collection, availability and usage indicators, dashboards to support your communication.
We use cookies to ensure that you have the best possible experience on our site, and 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.