Invalid or missing fault displays and event logs – HP StorageWorks EVA Controller HSG V8.8 Software User Manual
Page 99
Troubleshooting
99
Command Console V2.5 User Guide
Invalid or Missing Fault Displays and Event Logs
Invalid or lost notifications may occur when the client system loses connection
with a subsystem. The client system receives notification about most of the
changing subsystem faults at monitored intervals. If the client system no longer
receives notification about subsystem faults, then changes to that subsystem will
not appear in the client system’s Navigation tree, Storage window (if applicable),
Fabric window (if applicable), and Event Viewer.
For example, while client system’s connection with a subsystem is broken, you
will not receive event logs about that subsystem, except the lost connection
notification.
The following list describes common causes for lost connections. After you fix
the physical and/or software problem that is listed below, you need to close and
reopen the Storage window for that subsystem to get its latest status.
■
RAS connections—Remote Access Service (RAS) connections are not
full-time. If no RAS connection exists, events are not logged to the Event
Viewer Application Log.
■
Serial controller connections—There may be a bad or missing serial cable. To
correct this situation, replace or plug in the cable.
■
Network connections—Agent may be missing or not running.
■
Network connections—There may be network discontinuity.
■
The Agent may not be properly configured for a client system.
■
If your setup includes a controller, the controller may have halted, reset, or
hung. To repair the situation, restart or replace the controller.
■
If your setup includes virtual disks, the virtual disk used for communicating
with the subsystem is no longer available.
Pager Notification Continues After Exiting the Command Console Client
You may have noticed continuous pager notification in response to subsystem
faults, even though you have exited the Command Console Client. This behavior
is normal.
AES runs as a service under Windows NT, Windows 2000, and Windows Server
2003. It continues to run after you exit the Command Console Client. AES
communicates with Agents and activates paging when a subsystem event occurs.
To stop pager notification, stop AES. For information about stopping AES, see