SNMP Traps

This section describes the basic set of SNMP system status traps issued by the Scalar i2000 / i6000. These traps present the physical library point of view, not that of a particular partition.

Intelligent Storage MIB

Traps defined in the Intelligent Storage MIB are issued with enterprise OID “intelligent”, which resolves to 1.3.6.1.4.1.3764.1.1.

Trap # 500: startupSequenceCompleted

This trap indicates that the library has completed its boot sequence.

Trap # 501: shutdownSequenceInitiated

This trap indicates that the library has started its shutdown sequence, which includes reboot and shutdown.

Management MIB for i10.x

These informational traps are defined in the ADIC Management MIB. Each is issued with enterprise OID “management”, which resolves to 1.3.6.1.4.1.3764.1.1.200.20.

Trap # 101: physLibraryOnlineStatusChange

This trap is issued when the physical library is brought online or taken offline.

Trap # 102: physLibraryDoorStatusChange

This trap is issued when the physical library door has been opened, closed, closed and locked, closed and unlocked, or when the controller has failed.

Trap # 103: ieStationDoorStatusChange

This trap is issued when an I/E station door has been opened, closed, locked or unlocked.

Trap # 110: rcuReady

This trap is issued whenever the i2000 / i6000 robotics transitions from the “not ready” state to the “ready” state.

Trap # 111: rcuNotReady

This trap is issued whenever the i2000 / i6000 robotics transitions from the “ready” state to the “not ready” state. For example, this trap will be issued if the front door is opened or the robotics are disabled.

Trap # 204: logicalLibraryOnlineStatusChange

This trap is issued when a logical library, also known as a partition, is brought online or taken offline.

RAS Sub-system Status Change Traps

The i2000 / i6000 issues a trap whenever the aggregate state of one of the six RAS status groups changes. Listening for these traps is the preferred method of monitoring the health of the Scalar i2000 / i6000. The payload of each of these traps is very similar; it is summarized in the table below.

Table 1: RAS System Status Change Trap Payload Description

Payload Element	Description
componentId	Identifies the management control blade which is managing the RAS system. For i2000 / i6000, the varbind value is always set to 8.0.0.0.0.0.1.0.59.
trapSequenceNumber	This integer uniquely identifies the Trap.
trapSeverity	Not Used
trapSummaryText	Not Used
rasStatusGroupIndex	RAS group whose status has changed; connectivity(1), control(2), cooling(3), drivesAndMedia(4), power(5), and robotics(6)
rasStatusGroupStatus	New state; good(1), failed(2), degraded(3), warning(4), informational(5), unknown(6), or invalid(7)
rasTicketId	This is beyond the scope of this document.
rasReportId	This is beyond the scope of this document.

Trap # 400: connectivityGroupStatusChange

The state of the connectivity hardware/software has changed.

Trap # 401: controlGroupStatusChange

The state of the control hardware/software has changed.

Trap # 402: coolingGroupStatusChange

The state of the cooling hardware/software has changed.

Trap # 403: drivesAndMediaGroupStatusChange

The state of the drives and media hardware/software has changed.

Trap # 404: powerGroupStatusChange

The state of the power hardware/software has changed.

Trap # 405: roboticsGroupStatusChange

The state of the robotics hardware/software has changed.

Trap # 407: rasTicketNotification

The state of the specific RAS ticket issue details.

Management MIB for i11.x