HP Tape Library Configuration Guide
Table Of Contents
- hp tape library configuration guide
- Configuration
- Configuring the Host System
- Windows NT
- Sun Solaris
- HP-UX Hosts
- Table 1 Drivers Needed
- Installing the Pass-Through Driver
- HSC or PCI Pass-Through Driver Installation
- 1. Run SAM.
- 2. Select Kernel Config, and press Return.
- 3. Select Drivers, and press Return.
- 4. Select sctl.
- 5. From the Menu Bar, select Actions. Select Add Drivers to Kernel, and press Return.
- 6. From the Menu Bar, select Actions. Select Create New Kernel, and press Return.
- 7. At the Are you sure prompt, respond Yes. Press Return.
- 8. After the status messages, select OK. Press Return. The system reboots.
- 1. Run SAM.
- Creating a Device File for the Robotics Controller
- Verifying the Installation
- Table 1 Drivers Needed
- MPE/iX Hosts
- Requirements
- Configuring the Host
- 1. Power on the library and host. Run ODE at the ISL prompt: ISL>ODE
- 2. Identify the device path through RUN MAPPER: ODE> RUN MAPPER ***STARTING EXECUTION OF MAPPER**...
- 3. Boot the system. At the MPE prompt, run sysgen and start the io section: sysgen SYSGEN version...
- 4. If not already configured, configure the differential card and the pseudo/target level of the ...
- 5. Configure the robotics controller and the drives (the pass-thru driver): io> adev 30 id=HPA466...
- 6. Verify the bindings between PATH, LDEV number, ID, PMGR (device drivers), and LMGR attributes ...
- a. Verify the binding for the device adapter (the fw/differential dam): io> lpath 10/4/4.0.0 PATH...
- b. Verify the binding for the targets (the transparent dm): io> lpath 10/4/4.0 PATH: 10/4/4.0 LDE...
- c. Verify the binding for the robotics controller (the pass-thru driver): io> lpath 10/4/4.0.0 PA...
- d. Verify the binding for the tape drives (the differential tape dm): io> lpath 10/4/4.1.0 PATH: ...
- e. To configure the Storage Node on the NetWorker server, verify the ldev specifications: io> Ide...
- a. Hold the configuration changes: io> hold
- b. Exit the io section: io> exit
- c. If you have followed the local convention for backing up the configuration file, keep the chan...
- d. Exit sysgen and reboot according to local convention: sysgen> exit
- 1. Power on the library and host. Run ODE at the ISL prompt: ISL>ODE
- Verifying the Connection
- Diagnostics
- Diagnostic support tools
- HP Library & Tape Tools
- Support Tools Manager (STM)
- STM is the primary HP-UX support tool. Though this document provides general information about ST...
- There are three user interfaces, all in /usr/sbin/stm/ui/bin/:
- There are three basic operations in STM:
- STM saves detailed information in several logs:
- Table 4 on page24 shows which types of STM tools are supported on the robotic and tape drive com...
- Table 4 Supported Tool Characteristics
- Table 5 Drive Expert Tool Command
- Table 6 Robotic Controller Expert Tool Command
- Firmware Update Tool
- When started, the firmware update tool will examine the firmware revision of the current SCSI dev...
- If no files are found (or no compatible files are found), it will display an error message statin...
- If you have enabled the licensed firmware update tool, you can start it by selecting [Utility], f...
- Sysdiag
- Sysdiag is the MPE/iX support tool, and provides a consistent user interface for support of tape ...
- Sysdiag is a licensed-use tool, so a user must first know and enter a diagnostics password. Enter...
- :suplicen
- Use of sysdiag also assumes knowledge of the ldevs at which the components to be supported are lo...
- :sysdiag
- This command will bring up the Diagnostic User Interface (DUI) prompt. Two diagnostics are availa...
- SCSITAC and SCSIDLT are divided into parts called “sections.” To use either of these diagnostics,...
- DUI> scsitac ldev=6 sc=4
- SCSITAC contains three sections:
- Sections 1 and 2 perform tests on the library, report results, and return to the DUI prompt. Sect...
- Table 7 SCSITAC Interactive Commands
- Table 8 SCSIDLT Interactive Commands
30 Diagnostic support tools
Firmware Update Tool
When started, the firmware update tool will examine the firmware
revision of the current SCSI device, and then search the directory
/var/tmp for firmware files that are compatible with the device. The
internal headers of any firmware files present in this directory will be
checked. If compatible files are found, it will select the most current
version and pop up a dialog box asking if you want to update
firmware immediately. If you select
[Start Update], the tool will
update the device firmware and display text messages indicating the
status in the firmware update menu window.
If no files are found (or no compatible files are found), it will display
an error message stating that no compatible files were found,
followed by a dialog box prompting the user to change the directory
path where the tool searches for firmware files.
If you have enabled the licensed firmware update tool, you can start
it by selecting
[Utility], followed by [Advanced Menu] from the
firmware update menu bar. A list of several compatible firmware files
will be displayed in the dialog box that pops up. You can select from
a list of files, and then select
[Start Update] to begin the firmware
update process.
NOTE After updating firmware, allow time for the device to initialize
and test itself. Power cycling the device before this process
has completed may result in product failure and the inability
to perform further updates.