Configuring Local SNMP

You use local SNMP in environments with tight security where use of an SNMP port is not allowed. To secure the connection between the vRealize Automation SNMP agent and the SNMP server, vRealize Automation uses SNMP authentication and AES-256 encryption.

Local SNMP only runs on the localhost. To access the service using the REST API on VAMI port 5480, you use the URL https://$vRA:5480/config#/vSNMP-local-daemon. To maintain network security and accessibility within your environment, leave the local SNMP daemon running.

Before running any SNMP service requests, verify that you have satisfied the prerequisites in Using SNMP to Monitor vRealize Automation.

Obtain information about an Object Identifier

To obtain information about an object identifier (OID) for free memory such as 1.3.6.1.4.1.2021.4.11.0, you use the following GET request.
curl --insecure -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer $token" https://$vRA:5480/config/snmp/local/get?obj=1.3.6.1.4.1.2021.4.11.0
The response body provides information about the OID.
{
  "SNMPv2-SMI::enterprises.2021.4.11.0": "6813296"
}

In this response, 6813296 is the total free memory on the SNMP device.

Walk the local SNMP tree

To walk the local SNMP tree with Management Information Database (MIB) value 1.3.6.1, you use the following GET request.
curl --insecure -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer $token" https://$vRA:5480/config/snmp/local/walk?obj=1.3.6.1
A snippet of the response body shows information about the network objects.
{
  "SNMPv2-SMI::mib-2.6.13.1.5.127.0.0.1.37866.127.0.0.1.61613": "61613",
  "SNMPv2-SMI::mib-2.6.13.1.4.10.126.188.32.58326.10.126.188.32.9300": "10.126.188.32",
  "SNMPv2-SMI::mib-2.25.4.2.1.3.1532": "0.0",
  "SNMPv2-SMI::mib-2.6.20.1.4.1.4.0.0.0.0.8080": "30132",
  "SNMPv2-SMI::mib-2.6.13.1.1.127.0.0.1.44418.127.0.0.1.5433": "5",
  ...
  "SNMPv2-SMI::mib-2.6.13.1.1.127.0.0.1.443.127.0.0.1.33257": "5",
  "SNMPv2-SMI::enterprises.2021.4.11.0": "6727248",
  "SNMPv2-SMI::mib-2.25.3.7.1.2.393232.1": "/dev/sda1",
  "SNMPv2-SMI::mib-2.25.3.7.1.2.393232.2": "/dev/sda2",
  ...
  "SNMPv2-SMI::mib-2.25.4.2.1.5.382": "",
  "SNMPv2-SMI::mib-2.25.4.2.1.4.41367": "postgres: vcac vcac 127.0.0.1(38115) idle",
  "SNMPv2-SMI::mib-2.25.4.2.1.4.41366": "postgres: vcac vcac 127.0.0.1(38113) idle",
  "SNMPv2-SMI::mib-2.25.4.2.1.4.57817": "",
  "SNMPv2-SMI::enterprises.8072.1.2.1.1.5.0.11.1.3.6.1.2.1.55.1.6.1.7.127": "0x80"
}

By using the MIB definition to access all OID data, you can see the names of all SNMP devices.