Receiving SNMP v3 traps
Zenoss Cloud can receive SNMP v3 traps from your devices, but there are some prerequisites:
- The device sending the traps must be added as a monitored device
- The zSnmpEngineId configuration property must be set to match the value from the device
To receive SNMP v3 traps for a device, follow these steps:
- If you are not already monitoring the device, add it to an appropriate device class.
- Set the zSnmpEngineId property for the device by:
- Adding the zenoss.snmp.SnmpV3EngineIdMap modeler plugin to the device and remodeling, or
- setting the value manually. To get the engine ID from the device, consult the manufacturer's documentation.
The zenoss.snmp.SnmpV3EngineIdMap modeler plugin only works for devices configured for SNMP v3 monitoring and that have no Engine ID already set.
Each device with a configured zSnmpEngineId must have a unique value for this property. For virtual machine devices that are cloned from a template machine image, this may require changing the engineIDType value in the snmpd.conf configuration file. Please see the Net-SNMP documentation for more details.
Testing SNMP v3 traps
To confirm that your collector is capable of receiving SNMP v3 traps, you may wish to send a test trap and confirm its receipt and conversion into an event on your Event Console. You will need:
- A Linux host, configured for monitoring via SNMP v3
- Access to the command line of that host
- To install the
net-snmp
andnet-snmp-utils
packages, if not already installed
The syntax for the snmptrap
command takes the form of:
snmptrap -v3 -e {dev/zSnmpEngineId} -u {dev/zSnmpSecurityName} -l authPriv -a SHA -A {dev/zSnmpAuthPassword} -x AES -X {dev/zSnmpPrivPassword} $COLLECTOR_IP '' SNMPv2-MIB::sysORUpTime.1
After substituting the {dev/*} variables and the $COLLECTOR_IP, a test command might look like the following:
snmptrap -v3 -e 80001f88806f6c4959a3cc0c5f00000000 -u zenmonitor -l authPriv -a SHA -A authPass -x AES -X privPass 192.0.2.100 '' SNMPv2-MIB::sysORUpTime.1