Documentation

Deploying monitoring with a ServiceNav Box

On the page

Need some help?

1. Document conventions

The following conventions apply in this document.
Warning          Indicates that failure to comply with the instruction given may prevent the proper functioning of the application.
Warning 2          Indicates specific instructions or clarifying information.
TipThis icon indicates a tip.
Field          Fields to be modified or identified in the application
Important    Important information
Value           a value to be inserted/modified in an applications field

 

2. Objective

Explain how to set up monitoring at a client site. We assume that the company has already been created in ServiceNav and if it's monitored in box mode, it's associated with an SNB(s).
The preparation of the ServiceNav Box and the prerequisites on the customer's network are described in other documentation on this site.

The creation of a company or a site is either carried out by the service provider of the client, or by following the documentation: Company/Site Management

Linking a ServiceNav Box with a company or site is dealt with in other documentation on this site.

Notification management is an important step and only occurs after the configuration of the uploads. This step is covered in the documentation : Notification configuration available on this site.

3. Preamble

The deployment of a client is done in 5 steps:

  1. ServiceNav Prerequisites Configuration
  2. Creation of monitoring accounts
  3. Adding hosts to be monitored by ServiceNav
  4. Checkpoint Configuration
  5. Creation of user services

4. Prerequisite configuration

The prerequisites are typically as follows:

  • SNMP installed and configured on the hosts to be monitored. The community used must be specified on the monitoring discovery page.
  • Have a domain account that is in the administrator group (used for some types of Microsoft server monitoring and for inventory)
  • Supply a fixed internal IP address on the SNB and along with associated information (default gateway, subnet mask, domain name servers).
  • Open the required TCP port (Ask support) from the client network intranet to the DNS name of the monitoring web platform (the address of the ServiceNav platform is azure.servicenav.io).
  • Sending of e-mail messages (SMTP protocol) must be allowed from the box to the Internet, or the box must be allowed to send messages via a mail relay server.

In some cases, in order to be able to monitor hosts, it may be necessary to configure the SNMP service on the host.
To configure these prerequisites on your host, consult the manufacturer documentation. The configuration of some prerequisites is also described here :
servicenav.coservit.com/en/documentations

5. Monitoring accounts

Before we start adding hosts to be monitored, we will create monitoring accounts that permit information to be retrieved via SNMP, WMI, etc...

To do so, you must go to the chosen company and then to Configuration " and in the menu " General > Monitoring accounts .
In order to save time in deploying monitoring we will create monitoring accounts: SNMP, Windows - WMI and Windows - Standard.

Monitoring Accounts

  • Add a monitoring account. The main accounts are :
    a. SNMP
    b. Windows - WMI
    c. Windows - Standard
  • List of existing monitoring accounts

Example of adding an SNMP monitoring account :

ServiceNav-Add-Account-Supervision-SNMP

  • Select the type of monitoring account to add, here SNMP
  • insert the SNMP community, here coservit
  • Fill in the port used for SNMP connections, do not enter anything if you use the default port.

6. Adding hosts to be monitored

6.1. Discovery

To accelerate deployment of monitoring, a network discovery tool is available. It allows you to detect the devices that respond to ping and SNMP present within the network IP address range that you specify.
To perform a discovery go to Configuration and then Hosts > Discovery .

 

ServiceNav-New Census

Click on Discovery 

ServiceNav-Recensement-Nonglet-Launch

  • Choose from the list the SNB that will perform the host discovery.
  • Enter the IP address range in which we want to discover devices.

ServiceNav-Recensus-Account

  • The SNMP community is the one defined in the monitoring accounts. If in the environment to monitor there are several SNMP communities in use you can add more by separating them with a comma. The community(ies) will be used to check the SNMP pre-requisite for monitoring.
  • The Windows Admin account allows you to test the WMI connection prerequisite for Windows-based devices.

Launch a discovery :

  • Click on "Apply" to start discover.
  • A progress bar indicates that the discovery is in progress.

Census - Ongoing

Discovery results :

ServiceNav-Recensus-Result

The column protocol indicates whether the host meets the prerequisites. For all hosts the protocols ping and snmp must be in green. For Windows server type hosts the protocol wmi must also be in green. If not check the pre-requisites and run discovery again.
To promote a host to monitoring, just click on the icon in the 1st column.
To add multiple hosts just check them and choose the action "Add to monitoring".

Adding hosts:
To add a host click on the icon in the 1st column, the following configuration window appears.

ServiceNav-Recensement-add-equipment

  • Modify the host name which will be visible in monitoring (if needed).
  • Edit host IP address . It is also possible to put a DNS name to supervise the equipment in DHCP (if needed).
  • Selectassociation with a company site.
  • Host category. The host category determines the available host templates.
  • Host template: Allows you to apply a group of services for this host category more quickly. The list represents the available host templates for the host category that you wish to monitor. You just choose templates you need.
  • When you click on an host template, its description is displayed, allowing you to understand the different services that will be deployed by this template.
  • Choose the criticality of the host to assist in the configuration of dashboards and notifications

Once the general information has been filled in, navigate to the "Networks" tab.

ServiceNav-Configuration-Equipment-Recenting-MapNetwork

 

  • Additional network interface monitoring can be done either according to SNMP ID or according to SNMP name. It is recommended to add interfaces with their "SNMP name" for switches and for virtual machines with automatic hypervisor failover (vMotion, Live Migration, etc...).
  • Select the interfaces to be added. By default the interfaces in "UP" status and with an IP address are selected. For switch type hosts all "UP" interfaces are selected.
  • Interface status green = "UP", red = "DOWN", by default the UP interfaces appear first in the list.
  • A pencil appears when the line is hovered over so that you can edit the name that the service will take in the monitoring screens.
  • As the information is not updated periodically, it is advisable to restart a discovery before adding hosts if it is more than 24 hours old.

Once the network information has been filled in, we go to the " " tab. Disks / Partitions

ServiceNav-Configuration-Equipment-Recenting-Partition

  • Select the disk partitions to be added. By default all partitions are selected.
  • Percentage utilisation of the partition obtained by the discovery.
  • A pencil appears when the line is hovered over so that you can edit the name that the service will take in the monitoring screens.
  • As the information is not updated periodically, it is advisable to restart a discovery before adding hosts if it is more than 24 hours old.
  • Click on "Apply" to add the host to monitoring.

 

Then we go to the Services list to refine the configuration.
Go to Configuration and then Services > List .

ServiceNav-Configuration-Services-List

 

List : Filter according to name, service template, criticality and/or notification
Action buttons (+ Add, Duplicate, etc ...) possible configurations to perform on services.
Displayed results represent all the services associated with the host, RADIOLOGY
Select a service to configure it.

Specific configuration of services :
In the General Information tab you can change the name, the template, its criticality and its description.

ServiceNav-Configuration-Services-List-Configuration-Service-Onglet-General

General information of a service :

  • Service template used
  • Name of service as shown in monitoring
  • Criticality of the service, it can be High Medium or Low
  • Description of the service template to explain what it does.
  • Operational instructions
  • Documentation (Link to a web page for example)

To ensure that the service reports back information, you have to go configure its arguments and the check period during which you want to monitor with this check.

ServiceNav-Configuration-Services-List-Configuration-Service-Onglet-Control

Setting the Availability and checks Tab :
1) Enter desired availability rate target (based on time slot)
2) Enter time slot over which the availability rate will be calculated.
3) Enter time slot over which monitoring using the service will take place. Caution: it must be identical or cover the entire time slot defined for calculating the availability rate.
4) Indicate if a monitoring account is used to retrieve the information. When this is the case, you can either choose the "No" option to use the monitoring account configured at the level of the host, the site the host is associated with, or a site higher up the company tree. If "Yes" option is selected, then the desired monitoring account for the service will need to be entered. For more information, please refer to the documentation on monitoring accounts.
5) Enter the parameters necessary for the successful gathering of information through monitoring.
6) Information about the selected argument.
7) Enter a time interval between successive checks (expressed in minutes), or use default values.

Repeat this step for all services requiring configuration.

You may need to add hosts manually without running discovery. To do this, follow the procedure 6.2 Adding hosts manually.
You can also add services manually. To do this, follow the procedure 6.3 Manually adding a service.
If this is not your case, you can go directly to the generation of the ServiceNav Box configuration by 6.4. Generation of the configuration.

6.2. Adding hosts manually

To add a host, go to Configuration and then Hosts > List

ServiceNav-Configuration-Equipment-List-Add-List

Click on " + Add  ": a configuration window opens.

Fill in the general information

ServiceNav-Configuration-Equipment-Add-InfoGenerale

1) Enter the name of the host you wish to add to monitoring
2) Enter your IP address or DNS name
3) Modify if necessary the site membership
4) Modify if necessary the host category
5) Select the SNB to use for monitoring
6) Add Host templates as required
7) Set its criticality within the information system
8) Describe the function of this host within the overall information system

Click on Availability and checks .

ServiceNav-Configuration-Equipment-Add-On-DispoControl

  • Set the desired availability rate target (based on a time slot)
  • Choose the time slot over which the availability rate will be calculated.
  • Choose the time slot during which monitoring using the service will take place. Caution: it must be identical to or cover the entire time slot defined for the calculation of the availability rate.
  • Define the time interval between two successive checks

Click on Relations .

ServiceNav-Configuration-Equipment-Add-Relations

  • Choose the host group it is part of, if required. (Not functional in this version)
  • Define the parent host from the ServiceNav Box perspective
  • Select child host(s) from the ServiceNav Box perspective
  • Apply to create the host

Parents and children of a host are hosts that must always be monitored by the same ServiceNav Box as the host in question.

 

NB: After adding a host, check that you do not need to make specific configurations for its services (see the step: "Specific configuration of services" in the documentation: "Deploying monitoring with a ServiceNav Box").

6.3. Manually adding a service

To add a service without using host templates you must navigate to Configurationand then Service > List .

ServiceNav-Configuration-Service-Add

Click on " + Add ": a configuration window opens.

Fill in the general information

ServiceNav-Configuration-Service-Add-InfoGenerale

  • Choose the service template appropriate to the check you wish to carry out
  • Enter the service name you wish to add to monitoring
  • Define its criticality within the information system
  • In Description describe the role of this service within the information system

Click on Availability and checks 

ServiceNav-Configuration-Service-Add-On-DispoControl1

  • Set the availability rate desired (based on a time slot)
  • Choose the time slot for the availability period on which the availability rate will be calculated.
  • Choose the time slot for the check period during which monitoring using this service will take place. Attention: it must be identical to or cover the entire time slot defined for the calculation of the availability rate.
  • Enter the information necessary for successful monitoring to occur. (In this example: Warning Threshold, Critical Threshold, Port)
  • Set the interval of time between two checks (expressed in minutes), or use the default values

Click on Relations 

ServiceNav-Configuration-Service-Add-Relations

  • Select the host(s) on which you wish to deploy this service. This allows for more efficient deployment.
  • Click Apply, once the choice of the hosts(s) has been made.

NB : Do not forget to push the configuration to update the ServiceNav Box.

6.4. Loading the configuration

Navigate to Configuration and then General > Loading

ServiceNav-Generation-Box

This page shows which ServiceNav Boxes need to update their configuration. Only the ServiceNav Boxes that need to be updated and those that you can administer are visible on this screen.

  • Click on the "Apply" button to update the configuration and start monitoring.

A pop-up appears at the bottom right of the page to confirm that the ServiceNav Box configuration has been sent for update.ServiceNav-Generation-Box-Application

 

7. Checking the update

Navigate to Monitoring and then Monitoring

ServiceNav-Supervision-Operation

To speed up the first polling it is possible to do the following initiate an immediate check. Filter on the 'No data' state (blue) and select the checks :

ServiceNav-Supervision-Operation - help

1) Filter on the "No data"state, then validate by clicking on, Search
2) All items in "No data" status are selected using the search filter.
3) Then click on Check

To see if the monitoring data is up to date, you have to update the screen by clicking on the icon : manual refresh  it is also possible to set the page to auto-refresh by clicking on the play button. automatic refresh: which will then turn green. The stop refresh button stops the automatic page refresh.
Once the first check of each of the elements has been carried out, in some cases there will still be services with an "Unknown" status. These services require a specific configuration that can only be identified after an initial check, for example: network traffic.
Network traffic needs to be configured according to an interface number that will be known only after the first check because the interface numbers vary according to the type of device, model, operating system, ...

Here's how to complete the configuration of the check.

1) Set the filtering parameters and validate by clicking on, Search

ServiceNav-Supervision-Operation - unknown

2) Select an unknown service to modify its configuration.

To reload the ServiceNav Box configuration, go back to step 6.4. Configuration generation or click on the popup that appears at the bottom right. Attention this popup will not be displayed for more than 5 seconds.

ServiceNav-Send-Box-Application

 

8. Creating and configuring user services

This step is dealt with in the documentation "Creating user services", where it explains the rules and best practices. Recall that the purpose of user services is to reflect the production usage of IT services consumed by users of the company.

This may also be of interest to you

tel1

Ensure and maintain the availability of its ServiceNav Box fleet

install script

Preparing for DR of a ServiceNav Box

Configuring a ServiceNav Box to use an authenticated mail server

en_US
fr_FR en_US

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.