HP HSG80 - StorageWorks RAID Array Controller Release Note page 12

Operating Constraints
To prevent this problem, delete any hidden files with a .GID extension that are in
the Command Console directory. The WinHelp engine uses .GID files to construct
the Index and Find Tabs. If the files are corrupted, the engine may not display one
or both of the tabs. Deleting the files causes the engine to reconstruct the .GID
files.
Communications Failure on Power Up with Low Batteries
If the battery in your cache is discharged when you power up the controller, the
controller may produce an invalid cache error. If you are using the Client as your
controller interface at that time, the error may prevent communication with the
controller. In this case, the controller status bar in the Client changes to yellow,
and the program displays a window containing error information.
To clear the error, you must exit the Client and use a normal controller
maintenance terminal to issue the
before you can use the controller. See your controller documentation for
instructions on use of the
If the battery remains low, the invalid cache error may reappear. In this case, you
can operate your controller with reduced capability, or you can change its cache
policy to get around its built-in battery protection, although at some risk to your
data. Refer to your controller documentation for details on its cache policy
controls.
After you have cleared the invalid cache error, you can use either a normal
maintenance terminal or Client as your controller interface.
Reservation Conflict
Agent will discard reserved LUNs from its list of devices to receive a status. The
reservation conflict will be recorded for each reserved LUN in the system error
log. A notification will appear in the log for each LUN reserved. In addition to the
system's binary error log (Tru64 UNIX), an error message will also be recorded in
the daemon.log file. An example of the error message is "Device lunName is
reserved and cannot be statused by steamd." This only applies to Agent during its
current run. If Agent is restarted without either a) releasing the reservation or
b) scanning the bus, the reservation conflict will be recorded again each time
Agent is restarted.
For prior Agent releases, to avoid filling the binary error log, Agent must be
stopped and restarted with bus scan enabled. Agent will not record the reserved
LUN in the storage.ini file, and will not status the reserved LUN.
12
CLEAR ERRORS INVALID_CACHE
CLEAR ERRORS INVALID_CACHE
command
command.
Command Console V2.5 Release Notes