[ Contents
] [ Index ]
The SANscape Console receives, logs, and displays events generated by
managed servers and by the SANscape Console itself. The majority of the events are generated by the SANscape Agents on the
managed servers and occur when there are:
Although array processes are initiated by the SANscape Console, it is
the server agent that generates operation notification events after these
processes start on the server. The SANscape Console generates a much smaller number of events. For example,
it generates an event if it does not receive a certain number of consecutive
heartbeats from a managed server. When the console receives any event, it logs 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 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 can 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 window. During this refresh process, the satellite dish icon is attached to the
server icon, and you are not be able to perform any configuration and
array activity commands on that server until the process is completed
and the main window is updated. Event Log File 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.
NOTE: If the event log appears not to contain all of the events
from the managed array, close and reopen the console. The events from the agent are logged into the system log of the host
where the agent is installed, even if the console is not running. The
following table lists the locations where the events are logged to in
each of the operating systems.
To Write Events to a Log File for Systems Running the IBM AIX For IBM AIX, the event logs are not logged by default. You might need to change /etc/syslog.conf to enable it to write to a log file.
Event Log Window To access Event Log, select View > Event Log. This window can be hidden by clicking Close and reopening (from the View menu) without losing any content. The SANscape Console begins to receive events when it is running, regardless of whether the Event Log window is open.
NOTE: You can also save and delete the contents of the eventlog.txt file by using the Save Event Log and Delete Event Log icons on the toolbar. Each event record contains the following fields:
Severity Levels
You receive alarm forwarding for the level selected and any other levels of a higher severity. Thus, if you choose Informational, you are notified of all alarm conditions. However, if you choose Critical, only critical alarms are received. |