VxBlock How to test SNMP traps from VxBlock components

Summary: How to test SNMP traps from VxBlock components.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Goals:
How to test SNMP traps from VxBlock components.

Facts:
VxBlock Central
SNMP Traps

Solution:
If SNMP trap forwarding is not already set up, see the "VxBlock 1000 Administration Guide" section titled "Set up VxBlock Systems to use VxBlock Central\Integrate with SNMP" for steps on how to properly configure the VxBlock Central Core VM to forward SNMP traps to any third-party Network Management System (NMS) software for viewing, processing, handling of SNMP traps. VxBlock Central only shows critical alerts within the VxBlock Central MSM UI under "System Alerts."
VxBlock Central

Most SNMP trap tests do not show up within VxBlock Central MSM UI under "System Alerts." To view any test SNMP trap sent by a VxBlock component, you should have SNMP forwarding setup as previously described, then verify in your NMS software that the test traps are being received.

NOTE: As of this KB publication VxBlock Central can only accept SNMP v2 traps from VxBlock Components, however VxBlock Central can be configured to take those v2 traps and forward them to v3 NMS software host as SNMP v3 traps, yet the traps will still lack v3 info as they originated as v2 traps. For More information, see the "VxBlock 1000 Administration Guide" section titled "Set up VxBlock Systems to use VxBlock Central\Integrate with SNMP."

The following is a list of SNMP trap test commands that can be performed on some VxBlock components:

Cisco Nexus Switches:

  • From within an SSH session to the Nexus switch, run command "Test pfm snmp test-trap temp_sensor," this sends the test trap to the IP address of the Core VM then the trap is forwarded to your NMS Software IP address. You must have previously configured trap forwarding on the Core VM as previously discussed.

Remaining components require installing the snmp package on either the Core VM or any Linux VM (this might require temp firewall changes for your environment):

On the VxBlock Central Core VM (or any Linux VM) perform the following steps:

  1. SSH into the Core VM (or Linux VM) with root privilege
  2. yum install net-snmp
  3. yum install net-snmp-utils

Change <NMS_IP> to your NMS Software Host's IP address which should have been previously configured on the Core VM using the configureSNMP script.
Replace <Component_IP> with the IP address of the VxBlock component.

NOTE: Copy and paste might result in the command not running correctly. If you encounter this, manually type the IP and apostrophe (') at the end (after the "a").

UCS (C-Series):

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.9.9.719.0.1 .1.3.6.1.4.1.9.9.719.1.1.1.1.20.4915953 s "critical(6)" .1.3.6.1.4.1.9.9.719.1.1.1.1.9.4915953 s "180" .1.3.6.1.4.1.9.9.719.1.1.1.1.11.4015953 s "Result: end-point-unavailable Code:" .1.3.6.1.4.1.9.9.719.1.1.1.1.10.4015953 s "2339806" .1.3.6.1.4.1.9.9.719.1.1.1.1.5.4015953 s "sys/rack-unit-4" .1.3.6.1.6.3.18.1.3 a '<UCSM_IP>'

Or

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.9.9.719.0.1 .1.3.6.1.4.1.9.9.719.1.1.1.1.20.4915953 s "critical(6)" .1.3.6.1.4.1.9.9.719.1.1.1.1.9.4915953 s "180" .1.3.6.1.4.1.9.9.719.1.1.1.1.11.4015953 s "Result: end-point-unavailable Code:" .1.3.6.1.4.1.9.9.719.1.1.1.1.10.4015953 s "2339806" .1.3.6.1.4.1.9.9.719.1.1.1.1.5.4015953 s "SERVER-B" .1.3.6.1.6.3.18.1.3 a '<C-SERIES IP>'

UCS (B-Series):

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.9.9.719.0.1 .1.3.6.1.4.1.9.9.719.1.1.1.1.20.4915953 i 6 .1.3.6.1.4.1.9.9.719.1.1.1.1.9.4915953 i 456 .1.3.6.1.4.1.9.9.719.1.1.1.1.11.4915953 s 'fltEquipmentChassisInoperable' .1.3.6.1.4.1.9.9.719.1.1.1.1.10.4915953 s '2015-23-04' .1.3.6.1.4.1.9.9.719.1.1.1.1.5.4915953 s 'sys/rack-unit-4' .1.3.6.1.6.3.18.1.3 a '<UCSM IP>'

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.9.9.719.0.1 .1.3.6.1.4.1.9.9.719.1.1.1.1.20.4915953 s "critical(6)" .1.3.6.1.4.1.9.9.719.1.1.1.1.9.4915953 s "180" .1.3.6.1.4.1.9.9.719.1.1.1.1.11.4015953 s "Result: end-point-unavailable Code:" .1.3.6.1.4.1.9.9.719.1.1.1.1.10.4015953 s "2339806" .1.3.6.1.4.1.9.9.719.1.1.1.1.5.4015953 s "sys1/chassis-1/" .1.3.6.1.6.3.18.1.3 a '<UCSM_IP>'

Unity:

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.1139.103.1.18.2.2 .1.3.6.1.4.1.1139.103.1.18.1.1 s "12:10760024" 1.3.6.1.4.1.1139.103.1.18.1.2 s "dpe_disk_5" .1.3.6.1.4.1.1139.103.1.18.1.3 s "14:60258" .1.3.6.1.4.1.1139.103.1.18.1.4 s 'DPE Disk 5 has failed (Part Number 00XXXXXXX, Serial Number APMXXXXXXXXXXX)' .1.3.6.1.6.3.18.1.3 a '<Unity_IP>'

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.1139.103.1.18.2.2 .1.3.6.1.4.1.1139.103.1.18.1.1 s "12:10760024" 1.3.6.1.4.1.1139.103.1.18.1.2 s "dpe_disk_5" .1.3.6.1.4.1.1139.103.1.18.1.3 s "14:60001f" .1.3.6.1.4.1.1139.103.1.18.1.4 s 'Snapshot creation on storage resource <a> failed due to insufficient protection space.' .1.3.6.1.6.3.18.1.3 a '<Unity_IP>'

XIO:

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.1139.30.1.2.1 .1.3.6.1.4.1.1139.30.1.1.1.5 s "major" .1.3.6.1.4.1.1139.30.1.1.1.11 s "2000403" .1.3.6.1.4.1.1139.30.1.1.1.8 s "XMS has insufficient free memory: only 483532 Kbytes are available." .1.3.6.1.4.1.1139.30.1.1.1.10 s "alert_def_xms_memory_full" .1.3.6.1.4.1.1139.30.1.1.1.9 s "1513068249455" .1.3.6.1.6.3.18.1.3 a '<XIO_IP>'

VMAX:

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.1139.3.0.4 .1.3.6.1.3.94.1.11.1.3.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0.2858 i 2858 .1.3.6.1.3.94.1.11.1.7.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0.2858 i 2 .1.3.6.1.3.94.1.11.1.8.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0.2858 oid 0.0 .1.3.6.1.3.94.1.11.1.9.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0.2858 s "Save or data device pool is full." .1.3.6.1.3.94.1.11.1.6.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0.2858 i 2 .1.3.6.1.3.94.1.6.1.20.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0 s "000XXXXXXXXX" .1.3.6.1.3.94.1.6.1.3.80.6.4.130.242.42.125.192.0.0.0.0.0.0.0.0 i 11 .1.3.6.1.4.1.1139.3.8888.1.0 i 2 .1.3.6.1.4.1.1139.3.8888.2.0 i 1111 .1.3.6.1.4.1.1139.3.8888.3.0 i 1054 .1.3.6.1.4.1.1139.3.8888.4.0 s "DG1_F_2" .1.3.6.1.6.3.18.1.3 a '<VMAX_IP>'

MDS Switch:

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 1.3.6.1.4.1.9.0.40992 .1.3.6.1.4.1.9.9.40999.1.1.3.0 s 'port fc1/1 is up' .1.3.6.1.6.3.18.1.3 a '<MDS_Switch_IP>'

XMS:

snmptrap -v 2c -c public '<NMS_IP>' 12345678910 .1.3.6.1.4.1.1139.30.1.2.1 .1.3.6.1.4.1.1139.30.1.1.1.5 s "critical" .1.3.6.1.4.1.1139.30.1.1.1.11 s "2000403" .1.3.6.1.4.1.1139.30.1.1.1.8 s "XMS has insufficient free memory: only 483532 Kbytes are available." .1.3.6.1.4.1.1139.30.1.1.1.10 s "XMS" .1.3.6.1.4.1.1139.30.1.1.1.9 s "1513068249455" .1.3.6.1.6.3.18.1.3 a '<XMS_IP>'

 

Affected Products

VxBlock and Vblock Systems
Article Properties
Article Number: 000205783
Article Type: How To
Last Modified: 03 Mar 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.