Dot Hill Systems 200 manual Event Log Window

Models: 200

1 35
Download 35 pages 11 Kb
Page 20
Image 20
FIGURE 13: Event Log Window

When the console receives any event, it logs it into SANscape’s Event Log file, EVENTLOG.TXT, and displays it in the Event Log window. Also, if the event occurs on a server, the notification of the event is sent to that server’s operating environment/system event log. On an NT server, it would go to the NT event log. In addition, when the event occurs on a server and that server is set up to send traps to an SNMP enterprise management console, such as HP OpenView, the server agent also sends a trap message to that computer.

Depending on the event received, the console might initiate a refresh process to request the inventory from the last periodic scan of the server involved, so the console can update the server’s inventory on the main SANscape window.

During this refresh process, the satellite dish icon is attached to the server icon, and you cannot perform any SANscape configuration and array activity commands on that server until the process is completed and the main window is updated.

SANscape’s Event Log window displays up to 500 events at a time. If you have more than 500 events, only the most recent 500 are displayed in the Event Log window; however, SANscape does not delete any events from the Event Log file, EVENTLOG.TXT, until more than 10,000 events have been logged.

￿￿After 10,000 events, SANscape reduces the Event Log file to the most current 500 events and then accumulates events until the limit of 10,000 is exceeded again.

￿￿A semi-colon separates the fields of each event record so you can easily import the file into a database.

￿￿EVENTLOG.TXT is located in the directory where the SANscape console program files are installed.

FIGURE 13: Event Log Window

20

Page 20
Image 20
Dot Hill Systems 200 manual Event Log Window