Documentation

Replacing a ServiceNav Box

On the page

Need some help?

1. Preamble

Replacement may be necessary in two cases:

  • the failure of a ServiceNav Box
  • migration of the OS of a ServiceNav Box (application upgrades are automatic and performed by the ServiceNav website)

In the case of a migration of a ServiceNav Box, the old and new ServiceNav Boxes will not be able to cohabit together because they share the same IP address in the secure ServiceNav network. It is highly likely that they will also share the same IP address in the LAN network if the supervised devices have been configured to respond to requests from a single IP address, the one of the old ServiceNav Box: this is notably a good practice in the implementation of SNMP supervision.

It will therefore be necessary to:

  • collect information on the former ServiceNav Box
  • switch off the old ServiceNav Box
  • apply this procedure for the new ServiceNav Box

Replacing a ServiceNav Box with another one is similar to the installation, except for the generation of certificates on the web server side: in the case of a replacement this step is unnecessary, as the certificates already exist.

 

1.1 Replacing a VM of type VMWare

  • Retrieve the latest OVF files and import them to the desired hypervisor or V-Center. Once the VM has been imported, it must be allocated resources according to the number of devices to be monitored.
  • Install VMWare tools.
  • Mount the VMWare Tools.
mount /dev/cdrom /mnt
cp /media/cdrom/VMWareTools-X.Y.Z-aaaaa.tar.gz /root/
tar xvf VMWareTools-X.Y.Z-aaaaa.tar.gz
./vmware-tools-distrib/vmware-install.pl
  • Keep the default installation settings.
  • Restart.

1.2 Replacement of a Hyper-V VM

To install a Hyper-V virtual ServiceNav Box, you need to go to Hyper-V Manager and create a new "virtual computer":

servicenav-hyperV1

The VM creation wizard opens :

ServiceNav-HyperV003

Click Next.

ServiceNav-HyperV004

Set the name location

ServiceNav-HyperV005

Configure the amount of memory you want to allocate for this VM.

ServiceNav-HyperV006

Choose the correct networkand then click Next.

ServiceNav-HyperV001

Here we will use an existing virtual disk; click on Browse... .

ServiceNav-HyperV008

Select the ".vhd" file you downloaded from the FTP download site. Then click on Open, then Next.

Caution always take the latest version of the documentation and Hyper-V model on the FTP to be up to date. If the version is too old it may not work and/or the deployment procedure will not be up to date.

ServiceNav-HyperV009

Check the summary and click on Finish

 

1.3. Replacement of a ServiceNav Box (physical)

Order the ServiceNav Box from Coservit. Possibility to have it configured by Coservit (in this case you have to fill in the inventory file), otherwise you have to follow the following documentation:
- VGA screen
- USB Keyboard
- Network (with access to the VSP monitoring platform)

2. Configuring the ServiceNav Box

2.1. Prerequisite

In this section you will need the following items:
- The name of the ServiceNav Box as indicated in the ServiceNav web platform, in the Configuration > General > Box section.
- The url of your ServiceNav web platform

For an installation with a fixed IP address (recommended) you will also need to collect the following information from the original ServiceNav Box:
- The IP address of the ServiceNav Box
- The subnet mask to use
- The default gateway
- The local DNS suffix
- The IP address(es) of the DNS servers
- The presence of a client-side proxy for output streams to the Internet
- Messaging configuration: direct sending or by relay, in case of relay configuration of the relay (IP address, authentication information)
- Configuring the supervision of MSSQL databases: collect the file /etc/freetds.conf (symbolic link to /usr/local/freetds/etc/freetds.conf)
- Oracle database supervision configuration: collect the file /usr/lib/oracle/11.2/client/network/admin/tnsnames.ora
- Specific configuration: Your specific files (ex: rsa key for the user nagios /home/nagios/.ssh/, other plugins, syslog configuration ...)
- Apache configuration: only if the original ServiceNav Box is used as a collection point for inventory information from ServiceNav agents.

The ServiceNav Box must be able to reach the ServiceNav website by http in order to be initialized.

Then follow the procedure for reinstalling a ServiceNav Box available on this site.

2.2 Connecting to the new ServiceNav Box

Once the new ServiceNav Box has booted on the operating system it asks for login information. Before modification this information is as follows:

Login : Ask support

Password: Ask support

At this stage the ServiceNav Box is configured in DHCP.

2.3 Installation

2.3.1 Launching the installer

To launch the ServiceNav Box installer, run these two commands :

cd /root/vsb_installation
./vsb_installation.pl

Then follow the instructions on the screen:

############################################################
 ####### VSB INSTALLATION ########
 ############################################################
 Copyright CoServIT 2012-2013. All rights reserved.
 ## Welcome in the VSB Installation script - VSB/VSM side.
 ## This tool will allow you to :
 ## - Configure your network
 ## - Contact the Vsb Installation API to get your synchronization parameters
 ## - Configure the mail
 ## Note: You can exit this program with Ctrl+C
Press any key to continue

Press any key to continue

2.3.2 Network settings

  • DHCP configuration

To set up the ServiceNav Box in DCHP, press directly on the Enter and go to section 3.3.3.

###### NETWORK CONFIGURATION #############
Do you want to configure the Network (y/n) [default: n] :
  • Configuration with a fixed IP address

If you want to use a fixed IP address, type "y" and then press the Enter to validate your choice:

###### NETWORK CONFIGURATION #############
Do you want to configure the Network (y/n) [default: n] : y

Type "s" and then press the key. Enter to validate your choice:

Static (s) or dhcp (d) [default = d] : s

Fill in the IP address you wish to use, then press the key Enter to validate your choice:

IP address : 192.168.192.27
Ip saved: 192.168.192.27

If you do not want to change the subnet mask, press the Enter.

Otherwise fill in the subnet mask and confirm by pressing the key Enter

Netmask [default = 255.255.255.255.0]:

If you do not want to change the broadcast address, press the key directly. Enter.

Otherwise, enter the broadcast address and confirm by pressing the key Enter.

Broadcast [default = 192.168.192.255]:

If you do not want to change the IP address of the gateway, press the key directly. Enter

Otherwise enter the IP address of the gateway and confirm by pressing the key Enter

Gateway [default = 192.168.192.254]:

Fill in the IP address of the domain name server(s). Once you have entered the DNS server addresses, press "n" to proceed to the next step.

Attention it is mandatory to enter at least one DNS server.

DNS Name-servers IP ('n' for next step): 192.168.192.254
DNS saved: 192.168.192.254
DNS Name-servers IP ('n' for next step): n

Fill in the local DNS suffix, then confirm by pressing the key Enter

Local Network Name [default = lan] : coservit.local

Fill in the name given to the ServiceNav Box, this name must be the same as the one given on the Coservit website.

Hostname (example: VSB_1) :SNM-PARTNER

You must then apply the network changes. To confirm your choice, press the Enter

If you change the IP address, you will have to reconnect to the VSB.
Do you want to commit this network configuration ? (y/n) [default : n] : y
--> Committing
--> Done

2.3.3 Downloading the configuration

  • Web application side

The configuration of the ServiceNav Box is available for download through an API running on the solution's web server.

This configuration contains among others the previously generated certificates.

To be able to download this configuration, you have to connect to the platform to authorize the download.

We therefore place ourselves in the application at the level of the section "The application". Configuration and then General " then the sub-menu " Box

ServiceNav-TokenBox

A token is then generated to authorize the download by clicking on the arrow. ServiceNav-FlecheToken

A pop-up window opens:

ServiceNav-RecupTokenBox

An installation token is generated with a lifetime of ten minutes. Keep this pop-up open while the box configuration is being retrieved as you will need this information.

NB: if your token has expired close the pop-up and repeat its generation.

  • ServiceNav Box

Choose the "y" option to be able to download the configuration.

###### CONTACTING INSTALLATION PROVIDER #############
Do you want to retrieve configuration by HTTP/HTTPS api (y/n) [default: n] : y

Then enter the url of the ServiceNav SaaS web platform:

WebApp URL : https://my.supervision.com

Retrieve in the pop-up the identifier and fill in the :

ID : 103

Retrieve the installation token from the pop-up window and enter the :

Token installation : Kw3TL4uxAzph

The download is completed:

--> Request sent to the installation provider
Installation package has been correctly downloaded from the installation provider.
Configuration files have been correctly extracted from the installation package.
* Stopping virtual private network daemon.                            [ OK ]
* Starting virtual private network daemon.
* customer (OK)
                                                                      [ OK ]
Stopping remoteOperationBox: remoteOperationBox
Waiting for remoteOperationBox to exit . done.
Error: /usr/local/nagios/var/remoteOperationBox.pid already exists.
But no remoteOperationBox process runnig
Removing remoteOperationBox pid file
Starting remoteOperationBox: remoteOperationBox

The ServiceNav Box is now securely connected to the server.

2.3.4 Configuring the sending of email notifications

The last step is the configuration of sending emails with the Exim4 email service located on the ServiceNav Box.

To configure the sending of e-mail notifications, type "y" and then press the "Enter" key:

###### MAIL CONFIGURATION (EXIM4) #############
Do you want to configure the Mail (y/n) [default: n] : y
--> Launching exim4 config. do not interrupt!

The Exim4 configuration tool is launched:

  • Live configuration

Here's what you need to answer the questions:

Configuration type:

  • Direct distribution by SMTP (Website)

System email name:

  • en

List of IP addresses at Exim will be waiting for incoming SMTP connections:

  • 127.0.0.1

Other destinations for which email must be accepted:

  • (blank)

Areas to be relayed:

Relay machines:

  • 127.0.0.1

Should DNS queries (connections on demand?) be minimized?

  • No

Method of delivering local mail:

  • Format in /var/mail

Is it necessary to separate the configuration into several files?

  • No
  • Configuration via a relay server

Here's what you need to answer the questions:

Configuration type:

  • Sending via relay (smarthost) - no local mail

System email name:

  • en

List of IP addresses at Exim will be waiting for incoming SMTP connections:

  • 127.0.0.1

Other destinations for which email must be accepted:

  • (blank)

Domain name visible to local users :

Network name or IP address of the smarthost system :

  • x.x.x (@IP of the relay mail server)

Areas to be relayed:

  • en

Relay machines:

  • 127.0.0.1

Should DNS queries (connections on demand?) be minimized?

  • No

Is it necessary to separate the configuration into several files?

  • No

Once the configuration is complete, the service restarts:

* Stopping MTA for restart [ OK ]
* Restarting MTA [ OK ]
--> Exim4 config finished

To test the sending of emails type the following command and adapt it to your needs:

echo test | mail -s 'test' mon.email@mondomaine.com

2.3.5 End of configuration

To exit the installer press a key:

Press any key to exit

In order to secure the box, a password must be generated. We advise you to use a password generator with the following generation rules:

  • 12 characters
  • Uppercase/lowercase/digits/

punctuation/unicity of characters

Warning: when generating a password for a Hyper-V ServiceNavBox do not use punctuation characters. These characters are not always correctly interpreted by the Hyper-V console. This would make it impossible to access the ServiceNavBox without a network connection.

Once the password has been generated, type the following command to change it:

passwd

Warning 2 Save the password in your production repository.


3. Configuration of ServiceNav Box supervision


This is a replacement so the supervision of the ServiceNav Box must already be in place. If this is not the case, please refer to the installation procedure for a new ServiceNav Box.

4. Importing configuration files from the old ServiceNav Box

If necessary, copy or recreate on the new ServiceNav Box the files previously collected on the old ServiceNav Box:

  • Configuring the supervision of MSSQL databases: collect the file /etc/freetds.conf
  • Oracle database supervision configuration: collect the file /usr/lib/oracle/11.2/client/network/admin/tnsnames.ora
  • Apache configuration: only if the original ServiceNav Box is used as a collection point for inventory information from ServiceNav agents.
  • Specific configuration: Your specific files (ex: rsa key for the user nagios /home/nagios/.ssh/, other plugins, syslog configuration ...)

5. Importing the supervision configuration

This final step consists in loading the supervision configuration on the new ServiceNav Box :

  • Go to the ServiceNav website
  • Position yourself on the ServiceNav Box site or company where the ServiceNav Box is located.
  • Navigate to Configuration > General > Generation
  • Go to the tab All my boxes
  • Enter the name of the ServiceNav Box in the search field.
  • Select the ServiceNav Box
  • Click Apply : the supervision configuration is generated and pushed to the new ServiceNav Box
  • Check that the supervision starts in Supervision > Technical Operation

 

This may also be of interest to you

tel1

Ensuring and maintaining the availability of ServiceNav Boxes

install script

Preparing for ServiceNav Box DR

Configuring a ServiceNav Box to use a mail server with authentication

Welcome to ServiceNav!

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

[COVID - 19 ] - TELEWORKING, TARGET AVAILABILITY 100% !

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.