Context: use this procedure to deploy a monitoring box for Microsoft Azure, and integrate it into an Azure subnet.
VM recovery on our site ftp://software.servicenav.io (contact support to get credentials)
In the VSM-VSB folder take the image :
- SNM_MASTER_AZURE_2018_03_16_V3.13.1.vhd.zip if your platform is in version < 4.0
- SNB_MASTER_AZURE_2019_03_28_V4.0.0.vhd.zip if your platform is in version >=4.0
Deploy the image in Azure
Login to the AZURE portal and follow steps 1 to 3
and select the VHD file.
2) Creation of the image
- Go to the images 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 button + add
Select the previously created image
The password to be given for the created user is useless, it will then have to be changed.
Disk Options
Networking
The public IP address is created and associated with the VM automatically.
Management
Check the default choices below :
Advanced
Don't change anything.
Tags
Don't change anything.
Validate the last step after verification, then click on Create.
Finalize the configuration of the created VM
TCP port opening
To be done only if the virtual machine is used to collect data from ServiceNav agents. See with Coservit support for more details.
On the supervision box, launch the installation script without changing the IP address. Start at the token step of the procedures below.
Once a VM has been put under supervision, if it does not ping/timeout snmp, check that the Box and the VM are on the same group/address resource, in the global view.
Perform a virtual network peering if the VNs are different.
Commissioning of a ServiceNav Box
Follow the following procedure from section 2 onwards:
License mode: https://coservit.com/servicenav/fr/documentation/mise-en-service-dune-box-servicenav/
SaaS mode: https://servicenav.coservit.com/en/documentations/commissioning-of-a-servicenav-box-in-saas-mode/