Preparing for ServiceNav Box DR

On the page

Need some help?

Purpose of this document

We have identified 2 scenarios in which a ServiceNav Box (SNB or monitoring box) may need to be replaced:

  • A ServiceNav Box becomes unstable and has unpredictable behaviour and should be migrated to a new one : Migration of a ServiceNav Box
  • A ServiceNav Box becomes completely unusable and after rebooting, it is no longer possible to connect to it either via the network or via a local console.

This documentation will deal with this second case and will present the 2 solutions available to customers to set up a Recovery Plan for SNBs.
The actions below can be carried out by customers without the intervention of ServiceNav support.

Backing up local configuration files

If the entire box configuration is stored on the central platform, some configuration files are only present locally on the box, so it is very important to keep a copy on external storage in case access to the box storage is no longer possible.

Here are the files in question :

  • The file iptablesTo be saved if custom rules have been set up -> /etc/init.d/
  • The file freetds containing the configuration for MSSQL database monitoring -> /etc/freetds.conf
  • The file tnsnames containing the configuration for Oracle database monitoring -> /usr/lib/oracle/12.2/client64/network/admin/tnsnames.ora OR/usr/lib/oracle/11.2/client64/network/admin/tnsnames.ora

It is mandatory to place them in the correct location on the new SNB.

Complete replacement of a ServiceNav Box

If no backup of the box is available, it is possible to replace the ServiceNav Box with a new one.

Actions to be carried out :

  1. Provision a new ServiceNav Box from the image on our FTP site. It must have exactly the same hardware characteristics as the original SNB: CPU, RAM, disk space.
    Please note: in order to improve performance, it is advisable to make this provisioning in advance (Thick).
  2. Switch off the faulty box completely and boot the new one.
  3. Connect to the machine, go to root and run the box initialization script.
  4. Follow documentation to complete the different stages: Installation of an SNBSee Part 3 "Configuring the ServiceNav Box".
    For the "Network settings" section: set the same IP LAN the same Hostname as the SNB that is out of order.
    For the "Download configuration" part: generate a token and an ID for the SNB in question.
    -> The new SNB will have the same name, ID and VPN IP address as the defective one.
    Make the link with the platform and configure the emails.
  5. Copy all local configuration files to the new SNB.
  6. Push the configuration back to the new SNB so it has the same monitoring configuration as the failed SNB.

This new SNB replaces the old SNB and contains all its configuration.

Monitoring is operational again.

Rollback from a backup of the ServiceNav Box

When the ServiceNav Boxes are in the form of a virtual machine, it is very important to make regular backups of them (via the hypervisor directly or via a backup solution). It will then be very quick to restore a backup.

Actions to be carried out :

  1. Turn off the failed box completely.
  2. Deploy the last available backup of the box on the hypervisor.
  3. Start the new box from the backup.
  4. Verify that the VPN tunnel is properly mounted -> ifconfig tun0
    If the interface is present, the tunnel is operational :
  5. If one of the files listed in the chapter "Backing up local configuration files" has been modified since the last backup of the box, you will need to copy it to the new box that was created from the backup.
  6. In order to update this new box from the backup with the new configuration: connect to the ServiceNav web interface and push the configuration back to the box.

Monitoring is operational again.

This may also be of interest to you

servicenav hyperV1

Deploying a ServiceNav Box

IMG 0006

Configure Exim emailing with Microsoft Office365


Ensuring and maintaining the availability of ServiceNav Boxes


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.