User`s guide

Release Notes
AA–RFBPE–TE 387372-005 Page 49
Lost Connections Cause Invalid or Missing Fault Displays and Event Logs
Client receives notification for most types of changing subsystem fault
conditions on the next monitor interval after they occur. You may experience
invalid or lost notifications in situations in which Client’s connection with its
subsystems is broken. Any Windows NT Event Logs that might have occurred
while the connection was broken are also lost.
If the connection between Client and its subsystems is broken for any reason,
Client may continue to display faults that are cleared while the connection is
broken. Similarly, faults that occur while the connection is broken are not
displayed at all.
To avoid lost fault indications, make sure that Client’s connections with its
subsystems are monitored and maintained. To reestablish a connection with a
storage subsystem, you must exit and restart Client.
Broken connections can occur for a variety of reasons:
• For RAS connections—It is the nature of a RAS connection that it is not a
full-time connection. Events that occur during a period when the RAS
connection is not made are not logged to Windows NT’s Event Logging
facility.
• For serial controller connections—Bad or missing serial cable. To repair this
situation, plug in or replace the cable.
• For host port SCSI connections—Bad or missing SCSI host cable, no LUNs
configured on controller on Client startup.
• For network connections—Agent missing or not running, network
discontinuity, Agent not properly configured for your Clients.
• THIS controller halted, reset or hung—To repair this situation, restart or
replace THIS controller.
• The virtual disk being used for communications with the storage subsystem
is no longer available.