SNMP Monitoring of SVM status

You can receive information about the status of SVMs deployed in the virtual infrastructure by using any network monitoring system that utilizes the SNMP protocol. An SNMP agent is installed on the SVM. The SNMP agent can communicate the SVM status to your organization network monitoring system. If SNMP monitoring is enabled in the active policy that defines the SVM operation settings, the SNMP agent installed on the SVM becomes available for connecting via port 161. The community name specified when connecting the network monitoring system to the agent must be "ksvsnmp". Once connected, the SNMP agent starts sending SVM status information to SNMP monitoring system in your organization.

If the policy that enables SNMP monitoring is inactive, information about the status of SVMs is not relayed.

SNMP Agent can relay the following information about the status of SVMs with the File Threat Protection component:

• Information about RAM usage by the ksvmain process (as a percentage of the maximum value that, when reached, causes the application to restart)
• The number of protected virtual machines running desktop operating systems and the number of protected virtual machines running server operating systems.

  The count of protected virtual machines includes all virtual machines that were under the protection of the application over the last 30 days, even if those virtual machines are currently powered off.

• Information about whether virtual machine scan tasks are currently running on the SVM
• If scan tasks are running, information about the number of virtual machines that are currently waiting to be scanned, and the number of virtual machines that are being simultaneously scanned
• Information about the status of services of the File Threat Protection component on SVMs: On (services are running) or Off (services are not running)

For SVMs with the Network Threat Protection component, SNMP Agent can transmit information about RAM usage by the nsmain process (as a percentage of the maximum value that, when reached, causes the application to restart).

This data is specific to the application and such information is contained in the MIB files named KSV-MIB.txt and KSVNS-MIB.txt that are supplied together with the application. You can use these files to receive additional information from SVMs. You can also use other MIB files to receive the necessary information from SVMs.

You can restrict the list of IP addresses to which the SNMP Agent relays SVM status information to prevent unauthorized access to the SNMP service.