Replacement of a ServiceNav Box

1. Preamble

A replacement may be necessary in two cases:

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

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

This will require:

• collect information about the old 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 that the certificates are generated on the web server side: in the case of a replacement this step is not necessary, as the certificates already exist.

1.1 Replacing a VMWare VM

• Retrieve the last OVF files and import them on the desired hypervisor or the V-Center. Once the VM is imported, you have to allocate resources to it according to the number of elements to supervise.
• Install VMWare tools.
• Mount VMWare Tools.

mount /dev/cdrom /mnt
cp /media/cdrom/VMWareTools-X.Y.Z-aaaaaa.tar.gz /root/
tar xvf VMWareTools-X.Y.Z-aaaaaa.tar.gz
./vmware-tools-distrib/vmware-install.pl

• Keep the default installation settings.
• Restart.

1.2 Replacing a Hyper-V VM

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

Then a VM creation wizard opens:

Click on Next.

Define the name and the location

Set the amount of RAM that you want to allocate for this VM.

Choose the right networkthen click directly on Next.

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

Select the ".vhd" file that you downloaded from the FTP download site. Then click on open, then next.

Note you should always take the latest version of the Hyper-V documentation and template from 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.

Check the summary and click on Finish

1.3. Replacing a ServiceNav Box (physical)

Order the ServiceNav Box from Coservit. It is possible to have it configured by Coservit (in this case you have to fill in the inventory file), otherwise you have to follow the documentation below, and bring the following items:
- VGA monitor
- USB keyboard
- Network (with access to the VSP supervision platform)

2. Configuration of the ServiceNav Box

2.1. Prerequisites

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:
- 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 to the Internet
- The messaging configuration: direct sending or relaying, in case of relaying configuration of the relay (IP address, authentication information)
- Configuration of MSSQL database monitoring: collect the file /etc/freetds.conf (symbolic link to /usr/local/freetds/etc/freetds.conf)
- Configuration of the Oracle database monitoring: collect the file /usr/lib/oracle/11.2/client/network/admin/tnsnames.ora
- Specific configuration : Your specific files (ex : rsa key for nagios user /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 via 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 started on the operating system it will ask for login information. Before modification this information is as follows:

Login : To be requested from support

Mdp: To be requested from support

At this point, the ServiceNav Box is configured in DHCP.

2.3 Installation

2.3.1 Launching the installer

To launch the ServiceNav Box installer, execute 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 a key to continue

2.3.2 Network settings

• DHCP configuration

To set the ServiceNav Box to DCHP press 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", then press Enter to validate your choice:

##### NETWORK CONFIGURATION #####

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

Type "s", then press the Enter to validate your choice:

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

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

IP address : 192.168.192.27

Ip saved : 192.168.192.27

If the subnet mask is not to be changed, press the Enter.

Otherwise, enter the subnet mask and confirm by pressing the Enter

Netmask [default = 255.255.255.0]:

If the broadcast address is not to be changed, press the Enter.

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

Broadcast [default = 192.168.192.255]:

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

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

Gateway [default = 192.168.192.254]:

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

Please note that 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 validate by pressing the Enter

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

Enter 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 ServiceNav Box configuration is available for download via an API running on the solution's web server.

This configuration contains, among other things, the previously generated certificates.

In order 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 " Configuration then General "then the sub-menu " Box .

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

A pop-up window opens:

An installation token is generated with a lifetime of ten minutes. Keep this pop-up open while you recover the box configuration 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 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 username and fill it in:

ID: 103

Retrieve the installation token from the pop-up and fill it in:

Token installation : Kw3TL4uxAzph

The download is done :

--> 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 the email sending with the Exim4 email service located on the ServiceNav Box.

To set up email notifications, type "y" and 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 do to answer the questions:

Configuration type:

• Direct distribution by SMTP (Website)

Email name of the system:

• en

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

• 127.0.0.1

Other destinations whose email must be accepted:

• (white)

Areas to be relayed:

• .

Relay machines:

• 127.0.0.1

Should we minimize DNS queries (on-demand connections)?

• No

Method of delivering local mail:

• Format in /var/mail

Should the configuration be separated into several files?

• No

• Configuration via a relay server

Here's what you need to do to answer the questions:

Configuration type:

• Sending via relay (smarthost) - no local mail

Email name of the system:

• en

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

• 127.0.0.1

Other destinations whose email must be accepted:

• (white)

Visible domain name for 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 we minimize DNS queries (on-demand connections)?

• No

Should the configuration be separated into several files?

• No

Once the configuration is complete the service will restart:

* 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 the 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
• Upper/lower case/numbers/

punctuation/uniqueness 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 without a network connection.

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

passwd

Save the password in your production repository.

3. Configuring the ServiceNav Box monitoring

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

4. Import the configuration files from the old ServiceNav Box

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

• Configuration of MSSQL database monitoring: collect the file /etc/freetds.conf
• Configuration of the Oracle database monitoring: 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 nagios user /home/nagios/.ssh/, other plugins, syslog configuration ...)

5. Import of the supervision configuration

This final step is to load the monitoring configuration onto the new ServiceNav Box:

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