Home » HP Manuals » Tape Drives » HP Surestore Tape Library Model 6/140 » Manual Viewer

HP Surestore Tape Library Model 6/140 HP Tape Library Configuration Guide - Page 12

Verifying the, Installation

View all HP Surestore Tape Library Model 6/140 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

Verifying the Installation Confirm that the communications path to the robotics controller is functional: 1. Compile the SCSI I/O test program: cc /usr/contrib/src/scsi_io.c. -o/usr/contrib/ bin/scsi_io 2. Run the SCSI I/O test program, using the device file created during installation. For example, if the device file name is /dev/ rmt/HPA1234, the command would be: /usr/contrib/bin/scsi_io /dev/scsi/HPA1234 If the robotics is correctly configured, the following appears: the thing claims to be: HP C7200-8000 NOTE HP C7200-8000 is used only as an example. The actual ioscan output will reflect the product number and firmware revision of the library you are configuring. 10 Configuring the Host System

Section	Page
hp tape library configuration guide	1
Configuration 3	3
Diagnostics 17	3
Configuration	5
Configuring the Host System	5
Windows NT	6
Sun Solaris	7
1. Close all open applications and exit the Common Desktop Environment (CDE).	7
2. Type “init 0” at any prompt. This will shut down all processes, and take you to the OpenBoot P...	7
3. Type “reset”.	7
4. At the OK prompt, type “probe-scsi-all”.	7
HP-UX Hosts	8
Table 1 Drivers Needed	8
Installing the Pass-Through Driver	9
HSC or PCI Pass-Through Driver Installation	10
1. Run SAM.	10
2. Select Kernel Config, and press Return.	10
3. Select Drivers, and press Return.	10
4. Select sctl.	10
5. From the Menu Bar, select Actions. Select Add Drivers to Kernel, and press Return.	10
6. From the Menu Bar, select Actions. Select Create New Kernel, and press Return.	10
7. At the Are you sure prompt, respond Yes. Press Return.	10
8. After the status messages, select OK. Press Return. The system reboots.	10
Creating a Device File for the Robotics Controller	10
1. Use the mknod command to create a device file to access the robotics controller. The command s...	10
2. Determine the value for <majornum> by executing the following command for robotics attached to...	11
Verifying the Installation	12
1. Compile the SCSI I/O test program: cc /usr/contrib/src/scsi_io.c. -o/usr/contrib/ bin/scsi_io	12
2. Run the SCSI I/O test program, using the device file created during installation. For example,...	12
MPE/iX Hosts	13
Requirements	13
Configuring the Host	13
1. Power on the library and host. Run ODE at the ISL prompt: ISL>ODE	13
2. Identify the device path through RUN MAPPER: ODE> RUN MAPPER *STARTING EXECUTION OF MAPPER...	13
3. Boot the system. At the MPE prompt, run sysgen and start the io section: sysgen SYSGEN version...	14
4. If not already configured, configure the differential card and the pseudo/target level of the ...	14
5. Configure the robotics controller and the drives (the pass-thru driver): io> adev 30 id=HPA466...	14
6. Verify the bindings between PATH, LDEV number, ID, PMGR (device drivers), and LMGR attributes ...	14
a. Verify the binding for the device adapter (the fw/differential dam): io> lpath 10/4/4.0.0 PATH...	15
b. Verify the binding for the targets (the transparent dm): io> lpath 10/4/4.0 PATH: 10/4/4.0 LDE...	15
c. Verify the binding for the robotics controller (the pass-thru driver): io> lpath 10/4/4.0.0 PA...	15
d. Verify the binding for the tape drives (the differential tape dm): io> lpath 10/4/4.1.0 PATH: ...	15
e. To configure the Storage Node on the NetWorker server, verify the ldev specifications: io> Ide...	16
7. Save the configuration changes as follows:	16
a. Hold the configuration changes: io> hold	16
b. Exit the io section: io> exit	16
c. If you have followed the local convention for backing up the configuration file, keep the chan...	16
d. Exit sysgen and reboot according to local convention: sysgen> exit	17
Verifying the Connection	17
Diagnostics	19
Diagnostic support tools	19
The following external support tools are available for the library:	19
HP Library & Tape Tools	20
With HP Library & Tape Tools installed on your host computer, you can do the following:	20
The HP Library & Tape Tools diagnostic provides an intuitive graphical user interface with integr...	20
Support Tools Manager (STM)	21
STM is the primary HP-UX support tool. Though this document provides general information about ST...	21
There are three user interfaces, all in /usr/sbin/stm/ui/bin/:	21
Overview of STM Menu Structure	22
Performing Operations	23
There are three basic operations in STM:	23
1. To select a device or devices:	23
2. To run a tool: Tools -> <tool> -> Run	23
3. To view logs after the tool completes: Tools -> <tool> -> <log>	23
Using the STM Tools	23
Reviewing Logs	24
STM saves detailed information in several logs:	24
Types of STM Tools for Tape Libraries	26
Table 4 on page24 shows which types of STM tools are supported on the robotic and tape drive com...	26
Table 4 Supported Tool Characteristics	26
Expert Tools	27
Within an expert tool, select a category and command for the tool to execute:	27
Drive Tool	27
Table 5 on page25 lists expert tool categories and the specific commands that are applicable to ...	27
Table 5 Drive Expert Tool Command	27
Robotics Controller Tool	29
Table 6 on page27 lists expert tool categories and the specific commands applicable to the libra...	29
Table 6 Robotic Controller Expert Tool Command	29
Firmware Update Tool	32
When started, the firmware update tool will examine the firmware revision of the current SCSI dev...	32
If no files are found (or no compatible files are found), it will display an error message statin...	32
If you have enabled the licensed firmware update tool, you can start it by selecting [Utility], f...	32
Sysdiag	33
Sysdiag is the MPE/iX support tool, and provides a consistent user interface for support of tape ...	33
Sysdiag is a licensed-use tool, so a user must first know and enter a diagnostics password. Enter...	33
:suplicen	33
Use of sysdiag also assumes knowledge of the ldevs at which the components to be supported are lo...	33
:sysdiag	33
This command will bring up the Diagnostic User Interface (DUI) prompt. Two diagnostics are availa...	33
SCSITAC and SCSIDLT are divided into parts called “sections.” To use either of these diagnostics,...	33
DUI> scsitac ldev=6 sc=4	33
SCSITAC Sections	34
SCSITAC contains three sections:	34
Sections 1 and 2 perform tests on the library, report results, and return to the DUI prompt. Sect...	34
Table 7 SCSITAC Interactive Commands	34
SCSIDLT Sections	34
SCSIDLT contains four sections:	34
Sections 1, 2, and 3 perform tests on the library, report results, and return to the DUI prompt.	34
Section 4 provides the user with a SCSIDLT prompt, which will accept the following commands (Tabl...	35