User`s guide

Release Notes
AA–RFBPE–TE 387372-005 Page 51
Reservation Error Message
The Agent application, and other applications which access RAID storage
through SCSI, will get a reservation error if a device is reserved by one host and
another host attempts to access the same device. When this occurs, a generic I/O
error will be logged.
Reservation Conflict
Agent will discard reserved LUNs from its list of devices to be statused. 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) rescanning 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.
Multi-agent Functionality
With the current Agent and the direct SCSI connect Client, several Agents and
direct connect Clients can talk to the same controller. Only one will access the
controller at a time, with the others being blocked until the current request is
serviced. The multi-agent functionality will work with any controller with ACS
version 8.5+. This functionality is provided by the controller which the Agent
software takes advantage of.
Problems will still be encountered if running in a heterogeneous environment,
for example, running multiple agents or communicating with a combination of
HSZ70 and HSG80s. It is recommended that only one Agent be running in such
a heterogeneous configuration. The multi-agent functionality is not available in
the Novell Netware Agent.