HP StoreEver MSL6480 Tape Library User Manual
Page 62
Because these ASCs may be visible in device logs and diagnostic tools they are listed in
.
Table 9 Advanced failover vendor specific additional sense codes
Meaning
Description
ASCQ
ASC
Failover is enabled but the device driver has not opened a
failover capable connection to the device. Check that the
failover driver is installed and attempt to reopen the device.
FAILOVER SESSION SEQUENCE
ERROR
93h
82h
1
The advanced path failover system is unable to ensure that
the command will be executed in the proper sequence. Close
FAILOVER COMMAND SEQUENCE
ERROR
94h
82h
2
all connections to the device and then restart application
services.
The failover driver attempted to use a failover session key
that is currently in use by another host. The driver should
DUPLICATE FAILOVER SESSION KEY
95h
82h
automatically try a different key. Restart application service
if any errors occur.
The failover driver attempted to use a failover session key
that is not valid. Retry opening the device or restart
application services.
INVALID FAILOVER KEY
96h
82h
An event caused the device to close the failover session that
was in use. The driver should automatically open a new
session, if not restart application services.
FAILOVER SESSION RELEASED
97h
82h
A normal event informing the device driver that a event has
caused a change in the media changer state information.
SMC STATE CHANGED
98h
82h
The device driver should automatically update media
changer state information and continue.
A normal event informing the device driver that this path is
not an active control path. The device driver will
automatically use a different path.
FAILOVER SMC DEVICE SERVER
MOVED
99h
82h
1
If advanced path failover is enabled on a tape drive or a library, and the advanced path failover driver is not installed
on the host, this error will be reported to applications attempting to read/write the tape drive or move media using the
changer.
2
In rare cases when all paths to a tape drive are lost while commands are in progress it is possible for this error to be
reported once when the connection is next opened. Closing the device and retrying the connection will clear this condition.
62
Troubleshooting failover operation