ServiceNav offers a module in the tool to carry out a census of its computer fleet.
It can be used to see general information about the machines (IP address, type, name, running services, active supervision protocol, etc.), or supervise equipment.
The interest is to discover automatically the equipment in its network in order to speed up supervision.
The services discovered are disk partitions and network ports equipment.
Principle of operation of the census module
The census incorporates in its main algorithm the exploitation of raw data returned by open-source tools and network discovery protocols (NMAP, SNMP, WMI...).
The diagram below shows the sequence of operations performed for each IP address within the discovery target range.
Prerequisites for use :
The following 2 supervision accounts must be configured:
- Windows Admin (to allow WMI meter reading)
- SNMP Community and SNMPv3
Use cases - Conducting a census
Here we are going to identify a fixed position and put it under supervision with automatically discovered services.
The complete documentation is available here => https://coservit.com/servicenav/fr/documentation/realiser-un-recensement/
A discovery is started from the button, Discovery.
Simply fill in the address range or list the addresses to be surveyed, separated by a comma.
Aq: It is not possible to use DNS names.
The Account tab allows you to check the prerequisites for Windows Admin and SNMP accounts.
By default they are inherited from the site supervision accounts and it is possible to overload them during the census.
Click on Apply is used to start the census. A progress bar appears. This is automatically refreshed every 15 seconds. This makes it possible to evaluate the speed of progress of the census.
The results table is the central are of discovery. It enables the data collected by discovery of the network to be viewed and used.
In the displayed result, we can observe the status of the 3 tested protocols
ping The supervision box is able to ping the equipment.
snmp The supervision box can interrogate the eib of the equipment.
wmi : The supervision box can make a wmi connection on Windows servers.
By default partitions are discovered by SNMP protocol and network ports.
The census therefore allows the automatic addition of control points on the equipment for which the SNMP works.
This is very interesting especially when supervising switches which have many network interfaces.
If the SNMP protocol is in CRITICAL status (Red) then no service is discovered.
Good practice is to understand why the status is not OK before putting the equipment into supervision.
Once the census has been completed it is therefore possible to put the equipment under supervision.
To do this, select the equipment and click on the button
If no template is applied during monitoring and the "Add automatically discovered services" check box is checked then partitions and interfaces will be added automatically.
Note: In some situations port and partition discovery is not used, especially if the devices still have the same configuration. It is then possible to create models that will be applied to the devices without supervising the automatically discovered elements.
Selection rules according to equipment category
When adding a device in supervision (unitary or massive), some network interfaces and partitions are selected by default, and put in supervision. The associated selection rule depends on the equipment categoryand is set as follows:
|Category equipment||Selected network interfaces||Selected Disc Scores|
|Other||Status UP + has an IP (different from 127.0.0.1)||All|
|Server||Status UP + has an IP (different from 127.0.0.1)||All|
|Printer||Status UP + has an IP (different from 127.0.0.1)||All|
|Router||Status UP + has an IP (different from 127.0.0.1)||All|
|Switch||Status UP + IP empty or different from 127.0.0.1||All|
|UPS||Status UP + has an IP (different from 127.0.0.1)||All|
|Camera||Status UP + has an IP (different from 127.0.0.1)||All|
|Phone||Status UP + has an IP (different from 127.0.0.1)||All|
|Windows Server||Status UP + has an IP (different from 127.0.0.1)||All|
|Linux server||Status UP + has an IP (different from 127.0.0.1)||All|
|Windows Agent Server||Status UP + has an IP (different from 127.0.0.1)||All|
|SAN / NAS||Status UP + has an IP (different from 127.0.0.1)||All|
|Monitoring Box||Status UP + has an IP (different from 127.0.0.1)||All|
|Workstation||Status UP + has an IP (different from 127.0.0.1)||All|
|WIFI terminal||Status UP + has an IP (different from 127.0.0.1)||All|
|Management Card||Status UP + has an IP (different from 127.0.0.1)||All|
|Infrastructure||Status UP + has an IP (different from 127.0.0.1)||All|
Result in technical operations
When the equipment is added in supervision the result is as follows:
Use Cases - Conducting a census following a change in its infrastructure
When a change is made to one of the equipment already supervisedIn the technical operation, some control points are not visible or no longer functioning.
This can be the addition of a network card, a disk or a partition.
Example scenario : I move a VM from one ESX to another during maintenance.
The VM present in the supervision indicates me an alert or an unknown state on its network card.
When I look at the settings for the "Network Traffic VMware Virtual Ethernet Adapter for VMnet1" service, the interface number is 27.
As I don't know the interface number assigned following the move of my VM, I will use the census module to search for this number.
So I go into the census module and I will census my machine again (even if it is already under supervision)
So I see the number to be changed. In this case, I have to replace interface 27 by interface 12 in the service settings.
My control is operational again.