Context: use this procedure to deploy a monitoring appliance for Microsoft Azure, and integrate it into an Azure subnet.
Download the VM from our site ftp://software.servicenav.io (contact support for the login details)
In the VSM-VSB folder take the most recent image without exceeding the version of your platform.
Deploy the image in Azure
Connect to the AZURE portal and follow steps 1 to 3
and select the VHD file.
2) Creating the image
- Go to the image menu and click on the button, Add
Click on Create.
3) Creating the VM from the image
Click on Virtual Machine and then on the + Add
Select the previously created image.
Attention, in the "Instance details > Size" section, make sure to select a non-modular size, such as Dv4 or Dsv4 Series. Credit VMs such as the scalable B-Series can have high CPU load issues.
The password given for the created user is useless, it will have to be changed later.
Disk Options
Networking
The public IP address is created and associated with the VM automatically.
Management
Check the default choices below:
Advanced
Do not change anything.
Tags
Do not change anything.
Validate the last step after verification, then click on Create.
Finalize the configuration of the created VM
TCP port opening
Do this only if the virtual machine is used to collect data from ServiceNav agents. Contact Coservit support for more details.
On the ServiceNav box launch the installation script without changing the IP address. Start at the token step of the procedures below.
Once a VM is put under monitoring, if it does not ping/timesout for snmp, check that the Box and the VM are on the same resource group/address, in the global view.
Perform virtual network peering if the VNs are different.
Commissioning of a ServiceNav Box
Follow the procedure below from section 2:
License mode: https://servicenav.coservit.com/en/documents/commissioning-a-servicenav-box/
SaaS mode : https://servicenav.coservit.com/en/documents/commissioning-a-servicenav-box/