SNMP alerts

SNMP alerts inform you that a problem that has occurred on your DS6000™ series.

Simple Network Management Protocol (SNMP) allows communication between SNMP managers and SNMP agents over your TCP/IP network. An SNMP manager allows you to view the messages that the SNMP agent sends. You can define your SNMP objects through the Management Information Base (MIB) in the SNMP manager. The objects that are contained in the MIB relate to the management of the storage units and attached hosts. Once these objects are defined, you can receive SNMP alerts that are sent from the SNMP agent, in this case the DS6000 series, to your SNMP manager. You receive an SNMP alert when an error occurs on your DS6000 series.

SNMP alerts are enabled after you complete the following process:

Install and configure an SNMP manager such as Tivoli^® NetView^®. You can find configuration information for your SNMP manager and MIB in the SNMP_readme.txt file that is located on the DS CLI installation CD-ROM.
Note: Ensure that the DS6000 processor cards and your SNMP manager can communicate through your network. The processor cards must be able to send SNMP messages to your SNMP manager. You can test your configuration using the Create test option in the DS Storage Manager or the testcallhome command in the DS CLI.
Set up your SNMP alerts in the Configure Notifications page of the DS Storage Manager, or through the setsnmp command of the DS CLI.

An SNMP message is sent every time a problem log entry is generated. After you receive an SNMP message, review the corresponding problem log entry in the DS Storage Manager. Follow the instructions that are provided in the problem log entry and the corresponding help documentation to resolve the problem. Most problem log entries close automatically after you correct the problem that generated the entry; however, there are a few problems that you must close manually. Problems that must be manually closed are indicated in the message text for that individual problem.

One SNMP message and one problem log entry are generated when the first instance of the problem occurs. Any additional occurrences of the same problem are noted in the problem record, but do not generate additional SNMP messages.

SNMP messages contain two types of error codes: SRCs and alert traps. A system resource code (SRC) is an 8-digit hexadecimal code. Alert traps can also use a combination of a generic alert trap number and a specific alert trap number to indicate the type of error.

Example

The following SNMP message example provides both a combination of a generic and specific alert trap and a system resource code (SRC):

SNMP Trap received at : 2006-01-19 10:24:13.265
Trap date is : Thu Jan 19 10:24:13 CET 2006
Message : version=0 communityString=public
enterprise=1.2.3.4.5.6.7.8.901 agentAddr=1.2.3.4 genericTrap=6
specificTrap=3 timeStamp=17968154
(1.3.6.1.4.1.2.6.130.1.5:323030362f30312f31392031313a31333a3032204d616e75666163747572657
23d49424d0a5265706f7274696e674d544d533d313735302d3531312a313341415957410a50726f624e6d3d3
23030362d30312d31392d31312e31332e30352e3733323832360a4c7061724e616d653d200a4661696c696e6
7456e636c6f737572654d544d533d313735302d3531312a313341415957410a5352433d30784245383032363
4430a4576656e74546578743d200a)
Translation of the character string after the : (one byte = ASCII character)
2006/01/19 11:13:02 Manufacturer=IBM
ReportingMTMS=1750-511*13ABCDE
ProbNm=2006-01-19-11.13.05.732826
LparName= 
FailingEnclosureMTMS=1750-511*13ABCDE
SRC=0xBE80264C
EventText=

In this example, the SNMP message provides a generic alert trap 6 and specific alert trap 3, which indicates that a problem log entry has been created. This example SNMP message also provides an SRC of 0xBE80264C, which indicates that there is a hardware error with the host system cables or SFPs.