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

Background

Use this proceduer to migrate an Ubuntu 12.04 ServiceNav Box to a ServiceNav Box 4.0 and higher version

The Steps are as follows:

  • create a new ServiceNav Box following the usual procedures,
  • on 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

Retrieve the Master of the ServiceNav Box in the correct format, from ftp://software.servicenav.io (contact  support to obtain the access credentials)

Import the master to your virtualisation platform

Configure the networking on this ServiceNav Box.

Steps detailed here, up to step 2.3.2.

 

 

Prepare the old ServiceNav Box

Data copying is done from the new ServiceNav Box under SSH on the TCP / 22 port. This port must be open on the old ServiceNav Box, even if both ServiceNav Boxes are on the same LAN.

To test that the TCP / 22 port is open on the old ServiceNav Box, execute the following command on the new ServiceNav Box: telnet <old IP SNB> 22.

If not, modify the file /etc/init.d/iptables.sh on the old ServiceNav Box and reload this file.

Run the migration

Connect with an ssh client to the new ServiceNav Box

Run the following command, connected as the root user:

/usr/local/nagios/bin/importConfigurationFromBox.sh --host <IP ancienne SNB> -p <password> --halt-remote --reboot


Command-line help

/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 actions

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

restart Nagios : service nagios restart

Reload the monitoring configuration for the SNB from the ServiceNav web interface.

Test the NTP configuration: ntpq -np

Update the mail configuration: dpkg-reconfigure exim4-config

Test sending an email: echo “mail from snb” | mail -s “mail from snb” firstname.lastname@mail.com

Restart snmp service: service snmpd restart

Check that the monitornig data is correctly reported on the ServiceNav web interface.

UK ServiceNav Product Development Manager; my priority is to be needful of the particular requirements of all ‘English-speaking’ markets where ServiceNav is sold. I have over 20 years experience of the IT monitoring field - covering a wide variety of products and technologies.