VCOM Interoperability with Simple Network Management Protocol (SNMP)
Installation
Prior to installing the VCOM Virtual Matrix it is important to ensure that the Microsoft SNMP Service is installed. If installed, a running service called 'SNMP Service' can be found in the Services dialog. If SNMP Services are not installed, follow the directions here to install it.
From the Services Dialog, With the 'SNMP service' running, right click on the SNMP Service Configuration and select the 'Security' tab and ensure an Accepted Community is defined to with a name of 'Public' and the rights of Read-Only. Next select the 'Traps' tab. In this dialog, enter the IP address of the SNMP Monitoring tool that will be receiving the SNMP Trap messages.
With the SNMP services enabled, the installation process of the VCOM Virtual Matrix will automatically install and configure VCOM SNMP Agent for use by the SNMP Service.
Lastly, the provided MIB file may be added to the SNMP Monitoring Tool environment. In some cases, the SNMP Monitoring Tool must be configured with the IP address of the source of the incoming SNMP messages which would be the address(es) of the VCOM Virtual Matrix (both Primary and Secondary).
Operation
The SNMP implementation is limited only to the generation of SNMP Trap messages. There is no VCOM configuration required for the SNMP as the system will always generate the SNMP Trap messages for specific events if SNMP is installed and licensed. The SNMP Trap messages that are supported are:
• VDI/SIP Client Disconnect - An SNMP Trap will be generated for every VCOM Device Interface or SIP Client disconnect. The VDI and SIP Clients generally support critical system functionality and their disconnect is considered an event that should be investigated. The SNMP Trap message includes the VCOM Talk/Listen Selector Name of the VDI/SIP client that disconnected
• Failover Status Change - An SNMP Trap will be generated for every change in the Failover Status. In normal operation there should be no changes in the Failover state and as such any change is considered an event that should be noted. The most significant events that require investigation are any events that indicate that Secondary server or Primary server have gone offline.
SNMP TRAP Message Detail
| MIB Object Identifier | Message Function | Data Type (bytes) | Data Length | Data Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.41961.0.0.2 | VDI/SIP Client Disconnect | Octet String | variable | Selector Name as configured in VVM |
| 1.3.6.1.4.1.41961.0.0.3 | Failover Status Change | Integer | 4 | 0 - Failover is not licensed 1 - Failover is not configured 2 - Primary server is active, Failover server is offline 3 - Primary server is active, Failover server is ready 4 - Failover server is active, Primary server is offline 5 - Failover server is active, Primary server is ready |