Documentations

Replace a ServiceNav Box Ubuntu 12.04 with a ServiceNav Box 4.0 Ubuntu 16.04

On the page

Do you need help?

Context

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

The principle is as follows:

  • create a new ServiceNav Box by 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 it down and restarts the new ServiceNav Box

Creating the new ServiceNav Box

Get the ServiceNav Box master in the right format from ftp://software.servicenav.io (contact support to get the login details)

Import the master into the virtualization environment.

Configure the network for this ServiceNav Box.

Detailed steps hereuntil step 2.3.2.

Prepare the old ServiceNav Box

The data is copied from the new ServiceNav Box under SSH on port TCP/22. This port must be open on the old ServiceNav Box, which is 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 opposite case, modify the /etc/init.d/iptables.sh 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/importConfigurationFromBox.sh --host  -p  --halt-remote --reboot


Online help for the command

/usr/local/nagios/bin/importConfigurationFromBox.sh -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 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" prenom.nom@mail.com

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/iptables.sh
  2. Uncomment the line : iptables -A INPUT -p tcp -dport $PORT_NSCA -j ACCEPT
  3. Execute : /etc/init.d/iptables.sh

If there were inventory bounce backs on the old ServiceNav Box, check the configuration of the new ServiceNav Box by performing this procedure: https://coservit.com/servicenav/fr/documentation/configurer-fonction-inventaire/

Restart the snmp service: service snmpd restart

Check that the supervision data is correctly uploaded to the ServiceNav website.

 

 

You may also be interested in

servicenav hyperV1

Commissioning of a ServiceNav Box

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

Setting up a proxy on a ServiceNav Box

en_GB

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.