NAME

rmevent - RAID Manager Event File Format

SUMMARY

RAID Manager Event File Format

DESCRIPTION

This is the file format used by RAID Manager applications to dispatch an event to the rmscript notification script. It also happens to be the format for the proprietary log, used by the proprietary log viewer.

One event record consists of a single line of ASCII text, with each field separated by tildes "~". The line can be separated into a common portion and an event-specific portion. The common portion looks like:

{Host}~{Controller Serial #}~{Device Name}~{Date}~{Time}~{Event Type}~

Where

{Host}

Is the name of the computer that generated the event.

{Controller Serial # or RAID Module Identification}

Is the controller serial number or RAID module name that the disk array uses to identify itself. There may be a colon ":" followed by a number if the event occurred on a particular LUN.

{Device Name}

Is a system specific name which the host uses to access the device, whether it is the controller or a LUN on the controller.

{Date} and {Time}

The date and time when the event occurred.

{Event Type}

Is a number which specifies the event type. The possible numbers are 00 for an AEN event, 10 for a mode page event, 20 for a parity event, 30 for an I/O error event, and 90 for a text event.

The event-specific fields for the AEN (00) and I/O error (30) events are:

{ASC/ASCQ Codes}~{FRU}~{LUN #}~{LUN Status}~{Sense Data}

Where

{ASC/ASCQ Codes}

Are four ASCII-encoded hexadecimal digits, the first two specifying the Additional Sense Code, and the second two specifying the Additional Sense Code Qualifier.

{FRU}

Is a two digit ASCII-encoded hexadecimal number representing the Field Replaceable Unit that is affected by the AEN. It is only valid if LUN status field is nonzero.

{LUN #}

Is the LUN number (should be the same as any LUN specified in the {Controller Serial #} field) of the affected LUN. This field is only valid if

the LUN status field is nonzero.

{LUN Status}

Is an ASCII-encoded hexadecimal number which represents the LUN status.

{Sense Data}

Is a long string of ASCII-encoded hexadecimal digits which represent the sense data returned by the SCSI device. Every two digits specify one byte.

The event-specific fields for the Parity (20) event are:

{First Block}~{Last Block}~{Block count}~{LUN Number}~{Condition Code}

Where

{First Block}

Specifies the beginning of a region where parity errors were

found.

{Last Block}

Specifies the end of a region where errors were found.

{Block Count}

Is the number of blocks in the region that have parity errors.

{LUN Number}

Is the LUN where the parity errors were found.

{Condition Code}

Is a special number used by RAID Manager's SNMP trap

dispatcher.

The event-specific fields for the Mode Page (10) event are:

0~0~0~0~{Mode page data}

Where the {Mode page data} is a long string of ASCII-encoded hexadecimal digits which represent the sense data returned by the SCSI device. Every two digits specify one byte.

The event-specific fields for the Text (90) event are:

{Encoded string}~0~0~0~{Condition Code}

Where {Encoded string} is the message text, encoded so that newlines are represented by \n, tildes (~) are represented by \q, and backslashes (\) are represented by \\. The {Condition Code} is a special number used by RAID Manager's SNMP trap dispatcher.

Currently, the arraymon and parityck applications only generate AEN and parity events.

SEE ALSO

arraymon(1M), lad(1M), nvutil(1M), parityck(1M), raidutil(1M), rdac(7), rdacutil(1M), rdaemon(1M), rdriver(4), rm6(1M), rmparams(4), rmscript(1M)