Adaptec MAN-00005-UG, Installation And User Manual, Page: 71 / 237

72 Spheras Storage Director Installation and User Guide
User Defined: You can type your own parameter string (for example: pager or email) by typing over the
User Defined parameters.
Event Message ID: The number that is displayed in the ID column of the events table (for example, 389).
Event Message Severity: The severity level of the event.
Event Address: The contents of the address column of the events table (for example: ctl:0 chn:0 tgt:1).
Element ID : A text string that contains unique identifiers for each of the resources associated with the
error. This is the controller World Wide Name. The enclosure World Wide Name, or the
physical drive serial number, or both may also be displayed. See the serial number section of
the Event Details dialog for the contents of this string.
Click OK or press the Enter key to save your settings.
Click OK or press the Enter key of the Add Notification Application dialog box to save your settings.
5.2 Launching Application Alerts with Spheras Storage Director Server
The Spheras Storage Director Client handles the launching of application alerts when controller events that match user
specified severities occur. On the Spheras Storage Director Server side, you can modify sections of the cfg.ini file to
launch application alerts from the server. The modification of the cfg.ini must be done with a text editor. To edit the
cfg.ini file, follow these steps:
Locate the cfg.ini file. The file can is located in your Spheras Storage Director installation directory.
Using a text editor, open the cfg.ini file. An example file follows:
;EventAlertApplication#description
;This section holds the contents of the application used to notify
;the user of specified event severity.
;The SeverityCombination section is a bitmap, filled out as follows:
; INFORMATION_EVENT = 1
; WARNING_EVENT = 2
; ERROR_EVENT = 4
; SERIOUS_EVENT = 8
; CRITICAL_EVENT = 16
;The values may be OR’d together to support multiple severity levels
;(eg. To launch an application whenever a
;SERIOUS_EVENT (8) or a CRITICAL_EVENT(16) occurs use a SeverityCombination
;value of 24).
;The user defined parameters must be separated by spaces
;
;The example below describes an Event Alert Application called “Page On Call
;Manager" which
;launches the application c:\pagemgr.bat whenever a critical or serious event
;is generated, and passes it 4 user
;generated parameters :
; AT&F&C1&D2L1
; ATDT
; 555-1234
; #
;and 4 system generated parameters
; EVENT_ID (the ID number representing that event)
; EVENT_SEVERITY (the severity level of the event, as defined above)
; EVENT_ADDRESS (address information for devices involved in the event
;(eg. “ctl: 0, chn: 0, tgt: 0”)