Jump to main content

# Array event codes

The descriptions in this chapter are focused on running the event daemon in a logging mode - where events are automatically forwarded to a file on disk, syslog, SNMP, or the Windows Event Service.

Events below are described in the following format:

Table 1. Array event components
<Event-ID> | <Event-Name>
--- | ---
Category | <Event-Category>
Component | <Event-Component>
Severity | <Event-Severity>
Message | <Event-Message>

Where:

Table 2. Array event details
Event details | Description
--- | ---
<Event-ID> | The event ID - from the SYMAPI_AEVENT2_UID_T enumeration in symapi.h
<Event-Name> | The internal name for this event.
<Event-Category> | The category that this event belongs to, if any. Registering against a category has the effect of registering for all events that belong to that category.
<Event-Component> | The component, if it is known, that the event is delivered with. For Event Logging (to file, Syslog, SNMP, Windows Events), the component is only present if a specific component (for example: a specific device, disk, pool) is known.a
<Event-Severity> | The severity that the event is delivered with: Fatal, Critical, Major, Minor, Warning, Info or Normal.
<Event-Message> | The message that the event is delivered with.

a. The system ignores leading zero(es) when matching device numbers in event registrations against those in delivered events. That means if you register for events on device 01234 or 001234, events for device 1234 are received.

Unless all events are delivered with an Entity-Name set to the Symmetrix ID that relates to the event.