Installation problems
About this task
Problems that are encountered during the installation of the library are caused by incorrect SCSI bus
configuration, application software configuration errors, or an incorrectly configured operating system. If
the application software that you are using is not communicating with the library after installation, check
the following components:
v Picker Ship Lock Key:
Ensure that the Picker Ship Lock Key on the top cover is removed before the library is powered on.
v Drive/Library SCSI or Loop ID:
Ensure that the SCSI ID of the Drive/Library (or SAS or Fibre Channel Loop ID) is correct and not the
same as other devices that might be on the same bus.
v Host Bus Adapter (HBA) Compatibility:
Ensure that the library is compatible with the HBA. For best performance, the HBA used for this
library must be SCSI-3 LVDS. Pay particular attention to any steps that describe settings of various
jumpers or switches.
v HBA LUN 0/1 Support:
A single ID addresses both drive and library since the drive is LUN 0 and the library is LUN 1. These
models require an HBA that supports LUN scanning that must be enabled at the HBA.
v Cable Connections:
Ensure that there are no bent pins on cables and that all connections are securely fastened.
v Fibre Channel Tape Support:
Make sure that Fibre Channel Tape Support is enabled on the HBA if you are installing a library with a
Fibre Channel drive.
v SCSI Cable Length:
Ensure that the maximum cable length is not over 25 meters (82 ft.) for a single device on the bus or 12
meters (40 ft.) for multiple devices. Internal SCSI length within the library accounts for 2 ft.
v SCSI Termination:
Verify correct termination on both ends of the SCSI bus.
v Backup Application Installation:
See the documentation included with your backup application software instructions on how to verify
correct installation.
v Device Driver Installation:
Make sure that the correct device driver, if applicable, is installed for the library.
Note: Many backup applications use their own drivers for the library and drive. Before a driver is
installed, make sure that it is not in conflict with the software. Contact your Backup Application
vendor for this information.
Library recovery problem determination
The 2U and 4U library firmware generally retries failed operations up to three times before a failure is
posted to complete the operation, or, in some situations, proceeding with an operation that can be
completed in an alternative manner. If the operation is successful within the allotted retry count, the
appropriate retry counter is updated and recorded in the retry log and the next library operation
commences.
For example, failure to pick or place a cartridge from or to a designated cell or drive location after the
retry count is exhausted results in a failed operation with the appropriate error code. However, failure to
detect a particular cell location by sensing the prism fiducial that is on the cell shelf because it is missing
Troubleshooting 193
To Next Page
Loading...
Need help?
General
