HP White Paper Template (content) v5.0

HP Storage
June 2003
HP OpenView Storage Data Protector
SANconf Tool Readme File
Technical
white paper
Table of contents
Legal Notices
Overview
Prerequisites and Limitations
Gathering Device Information on Clients
Library Device Configuration
Initial Configuration of Library Device
Reconfiguration of Library Device
Removing the Configuration
Removing Drives from an Existing Library Device
Removing the Entire Library Device
SANconf Tool Related omnirc File Variable
Usage Synopsis
Troubleshooting
Automatic Recovery Upon Automatic Configuration Failure
Drive Name Convention
Drive Locking Mechanism
2
3
4
5
6
6
9
10
10
10
10
10
13
13
13
14
1
HP OpenView Storage Data Protector
SANconf Tool Readme File
Legal Notices
Hewlett-Packard makes no warranty of any kind with regard to this manual, including,
but not limited to, the implied warranties of merchantability and fitness for a particular
purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct,
indirect, special, incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your Hewlett-Packard
product and replacement parts can be obtained from your local Sales and Service
Office.
Restricted Rights Legend. All rights are reserved. No part of this document may be
photocopied, reproduced, or translated to another language without the prior written
consent of Hewlett-Packard Company Company. The information contained in this
document is subject to change without notice.
Use, duplication or disclosure by the U.S. Government is subject to restrictions as set
forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and
(c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19
for other agencies.
Hewlett-Packard Company
United States of America
Copyright Notices. © Copyright 1983-2002 Hewlett-Packard Company, all rights
reserved.
Reproduction, adaptation, or translation of this document without prior written
permission is prohibited, except as allowed under the copyright laws.
© Copyright 1979, 1980, 1983, 1985-93 Regents of the University of California
This software is based in part on the Fourth Berkeley Software Distribution under license
from the Regents of the University of California.
© Copyright 1986-1992 Sun Microsystems, Inc.
© Copyright 1985-86, 1988 Massachusetts Institute of Technology
© Copyright 1989-93 The Open Software Foundation, Inc.
© Copyright 1986-1997 FTP Software, Inc. All rights reserved
© Copyright 1986 Digital Equipment Corporation
© Copyright 1990 Motorola, Inc.
© Copyright 1990, 1991, 1992 Cornell University
© Copyright 1989-1991 The University of Maryland
© Copyright 1988 Carnegie Mellon University
© Copyright 1991-1995 by Stichting Mathematisch Centrum, Amsterdam,
The Netherlands
© Copyright 1999, 2000 Bo Branten
2
HP OpenView Storage Data Protector
SANconf Tool Readme File
Trademark Notices. UNIX® is a registered trademark in the United States and other
countries, licensed exclusively through X/Open Company Limited.
X Window System is a trademark of the Massachusetts Institute of Technology.
Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other
countries.
Windows NT™ is a U.S. trademark of Microsoft Corporation. Microsoft®, MS-DOS®,
Windows® and MS Windows® are U.S. registered trademarks of Microsoft
Corporation.
Oracle®, SQL*Net®, and Net8® are registered U.S. trademarks of Oracle
Corporation, Redwood City, California. Oracle Reports™, Oracle7™, Oracle7
Server™, Oracle7 Backup Utility™, Oracle8™, Oracle8 Server Manager™ and
Oracle8 Recovery Manager™ are trademarks of Oracle Corporation, Redwood City,
California.
Java™ is a U.S. trademark of Sun Microsystems, Inc.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
ARM® is a registered trademark of ARM Limited.
X/Open® is a registered trademark, and the X device is a trademark of X/ Open
Company Ltd. in the UK and other countries.
VisiCalc® is a U.S. registered trademark of Lotus Development Corp.
HP-UX Release 10.20, HP-UX Release 11.00 and later (in both 32 and 64-bit
configurations) on all HP 9000 computers are Open Group UNIX 95 branded products.
Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications
Corporation.
OpenView® is a registered U.S. trademark of Hewlett-Packard Company.
Other reserved names are trademarks of the respective companies.
Overview
SANconf tool provides easier configuration of libraries in SAN environments for
Windows, HP-UX and Solaris clients.
To learn more about SAN environment, refer to the HP OpenView Storage Data
Protector Administrator’s Guide.
SANconf tool can be executed on the Data Protector Cell Manager or on Data Protector
clients. It resides in the <Data_Protector_home>\bin directory on Windows and in
the /opt/omni/lbin directory on HP-UX and Solaris clients.
You can perform the following tasks using the SANconf tool:
Scan the specified Data Protector clients, gathering the information on SCSI addresses of
drives and pickers connected to the clients via the SAN environment. For more
information, refer to “Gathering Device Information on Clients” on page 5.
Create or modify an existing library or drive settings for given clients using the
information gathered during the scan of Data Protector clients. For more information,
refer to “Library Device Configuration” on page 7.
Remove drives on the specified clients from a library. For more information, refer to
“Removing the Configuration” on page 13.
All SANconf tool sessions are reported in
<Data_Protector_home>\log\sanconf.log on Windows and in
/var/opt/omni/log/sanconf.log on HP-UX and Solaris clients. It can be
used for troubleshooting.
3
HP OpenView Storage Data Protector
SANconf Tool Readme File
Prerequisites
and Limitations
This is a list of prerequisites and limitations for the Data Protector SANconf tool:
Prerequisites
• Before you begin, ensure that you have correctly installed and configured Data
Protector. Refer to the:
– HP OpenView Storage Data Protector Installation and Licensing Guide for
instructions on how to install Data Protector on various architectures.
– HP OpenView Storage Data Protector Administrator’s Guide for instructions on
how to configure and run backups.
• For an up-to-date list of supported versions, platforms, devices, and other information,
refer to the:
– HP OpenView Storage Data Protector Software Release Notes
or
– http://h18006.www1.hp.com/products/storage/software/dataprotector/
specifications.html
Limitations
See the HP OpenView Storage Data Protector Software Release Notes for a list of
general Data Protector limitations. This section describes limitations specific to
SANconf tool:
• SANconf tool is currently supported on the following platforms:
– Windows NT
– Windows 2000
– HP-UX 11.XX
– Solaris 7, 8
• For a full list of libraries that are supported with the SANconf tool, refer to the
Support Matrices in the HP OpenView Storage Data Protector Software
Release Notes.
• The following features are not supported:
– Placing spare drives in drive slots.
– Mixing drive types (combinations of “DLT”, “.9840”, and “LTO”).
– Configuring clients that are not in the Data Protector cell.
– Configuring clients that are currently unavailable is only possible when the
configuration of the library is performed from a configuration file that included
a scan of these clients.
Recommendations
When a single backup device is physically connected to multiple systems,
autoconfiguration of devices in SAN environments using the Data Protector GUI is not
recommended. It is assumed that when you perform autoconfiguration of devices in SAN
environments, one device is physically connected to only one system.
It is also recommended that only one driver is configured on a system for a specific
device.
4
HP OpenView Storage Data Protector
SANconf Tool Readme File
Gathering
Device
Information on
Clients
You can obtain the information on SCSI addresses of drives and pickers connected to the
clients via the SAN environment by running the SANconf tool using the
-list[_devices] option. SANconf tool scans the specified Data Protector clients,
gathers the information and uploads it to the Media Management Database on the Cell
Manager. The information about the configuration and scan data can also be stored in a
configuration file. You can use this configuration file when you are configuring the
library.
The syntax for gathering device information on clients is as follows:
Syntax
sanconf
-list[_devices][ListFileName]
[-hosts host_1 [host_n ... ] | -hostsfile
HostsFileName]
When the command is executed, messages appear on the screen showing the progress
of client scanning. A summary is listed when the scan is done.
If a ListFileName is specified, then the configuration and scan data information
are stored in the configuration file. The configuration file can be used with the
-configure option. For more information on this option, refer to “Library Device
Configuration” on page 6.
SANconf tool requires a list of clients to scan. This list can be specified using the
-hosts or -hostsfile option. If neither -hosts nor -hostsfile option are
specified, all clients within the current cell are scanned.
If -hosts option is specified, then all clients listed are scanned. If -hostsfile option
is specified, then all clients that are listed in the HostsFileName file are scanned.
HostsFileName must be an ASCII file containing the list of clients that you want to
scan. Every client must be specified in a separate line. When you want to save the scan
information to the configuration file, it is recommended that all clients are specified in the
clients list.
Example
sanconf -list_devices -hosts host01 host02 host03
=================== SUMMARY REPORT ===================
LIBRARY="HP:C7200-8000" serial="ABC0000123"
on hosts: host01 host02 host03
DRIVE: index=1; name="QUANTUM:DLT8000";
serial="A0B1C3D4E5"
DRIVE: index=2; name="QUANTUM:DLT8000";
serial="F6G7H8I9J0"
======================================================
5
HP OpenView Storage Data Protector
SANconf Tool Readme File
Library Device
Configuration
Library device is configured using the -configure option.
The syntax for configuring a tape library is as follows:
Syntax
sanconf
-configure [ListFileName]
-library LibSerNumber LibraryName [PickerHostName]
[DeviceTypeNumber | ".<DeviceTypeExtension>"]
[-hosts host_1 [host_n ... ] | -hostsfile
HostsFileName]
[-drive_template DrvTplFileName]
[-library_template LibTplFileName]
If ListFileName parameter is not specified, the SANconf tool scans all clients within
the current cell. If ListFileName parameter is specified, the SANconf tool assumes
that all information on clients is already present in the configuration file. In such case the
scan is not performed. If a client is not scanned, the library will be configured without
drives connected to this host.
Initial Configuration
of Library Device
For the initial configuration you have to run the SANconf tool using the -configure
option. SANconf tool starts devbra on all specified clients that queries devices for
configuration information on physical libraries and drives. It is recommended that the
information on clients is first stored using the -list[_devices] ListFileName
option and then the library and drives are configured using the -configure
ListFileName.
When the ListFileName parameter is used, SANconf tool only reads the
configuration file. In this case no scan of the clients is performed.
When you use the -library parameter, SANconf tool creates only one logical library
per physical library in the system and all devices on all specified clients. Library serial
number can be obtained using the -list_devices option.
Example
sanconf -configure -library MPC0100013 SAN_STORE host33 -hosts
host01 host02 host03
In this example, the SANconf tool scans the specified clients and then creates a logical
library named SAN_STORE with robotics configured on client host33 and drives for that
library configured on clients host01, host02 and host03.
Example
sanconf –list_devices mySAN.cfg -hosts host01 host02 host03
host33
sanconf -configure mySAN.cfg -library MPC0100013 SAN_STORE
host33 -hosts host01 host02 host03
In this example, the SANconf tool first scans the SAN environment for the configuration
information on the specified clients host01, host02, host03 and host33. This information
is then saved in the mySAN.cfg file.
6
HP OpenView Storage Data Protector
SANconf Tool Readme File
The second command uses the information stored in the mySAN.cfg file and creates a
logical library named SAN_STORE with robotics configured on client host33 and drives
for the library configured on clients host01, host02 and host03.
If the PickerHostName parameter is specified, then this library will be configured with
robotics controlled on that client only. If PickerHostName is not specified, the library
will be configured in the way that the robotic can be controlled from every client.
If DeviceTypeNumber parameter or “.<DeviceTypeExtension>” parameter is
used, the drives of type that are configured in the library. For the supported drive types
and their parameters, see Table on page 8. If neither of these parameters is specified,
the DLT drive type is used as default. When drives in the library are not of the same type
as specified, an error is reported. You can run the DeviceTypeNumber parameter
without specifying the PickerHostName parameter.
Device Type Numbers
Device Type Extensions
1
“.DDS”
2
“.QIC”
3
“.EXA”
4
“.AIT”
5
“.3480”
6
“.RDSK”
7
“.REGFILE”
8
“.9840”
9
“.TAPE”
10
“.DLT”
11
“.D3”
12
“.3590”
13
“.LTO”
14
“.SDLT”
15
“.VXA”
16
“.DTF”
17
“.9940”
If you want to configure drives only on the specified clients, you have to run
-configure option with either the -hosts or -hostsfile option. If neither of
these two options are specified, the drives will be configured on all clients in the cell.
If -hosts option is specified, then the drives are configured on all listed clients. If
-hostsfile option is specified, then the drives are configured on all clients that are
listed in the HostsFileName file. HostsFileName must be an ASCII file containing
all clients on which you want to configure the drives of the library. Every client must be
specified in a separate line.
7
HP OpenView Storage Data Protector
SANconf Tool Readme File
Example
To specify a specific drive type when configure a library using the SANconf tool, run the
following command:
sanconf -configure -library MPC0100013 SAN_STORE host33 “.9840”
-hosts host01 host02
This command creates a library named “SAN_STORE” with robotics configured on client
host33 and STK drives configured on clients host01 and host 02. The drives are named
as follows:
SAN_STORE_1_host01
SAN_STORE_1_host02
SAN_STORE_2_host01
SAN_STORE_2_host02
...
You can alter the default configuration of all configured drives in a library using the
-drive_template DrvTplFileName option. The parameters must be specified in
an ASCII file format with each parameter in a separate line. The drive template supports
the following parameters:
• VERIFY
This parameter enables the CRC Check option specified in the Data Protector GUI.
• CLEANME
This parameter enables the Detect dirty drive option specified in the Data
Protector GUI.
• RESCAN
This parameter enables the Rescan option specified in the Data Protector GUI.
You can also alter the default configuration of the library using the -library_template
LibTplFileName option. The parameters must be specified in an ASCII file format with
each parameter in a separate line. The library template supports the following
parameters:
• BARCODEREADER
This parameter enables the Barcode reader support option specified in the
Data Protector GUI.
• BUSYDRIVETOSLOT
This parameter enables the Busy drive handling: Eject medium option
specified in the Data Protector GUI.
• BUSYDRIVETOMAILSLOT
This parameter enables the Busy drive handling: Eject medium to mail
slot option specified in the Data Protector GUI.
Important: You can only alter the default configuration of the library at the initial
configuration. After the library is configured, you can no longer change the
configuration of the library using the SANconf tool.
Note: You have to scan all clients that you want to configure, both those that can see
the robotics and those that can see the drives.
8
HP OpenView Storage Data Protector
SANconf Tool Readme File
Example
In this example, the SANconf tool scans all clients in the cell and then creates a logical
library named SAN_STORE with robotics configured on client host33. The library and
drives are also configured with the parameters specified in DriveTemplate.txt and
LibraryTemplate.txt files.
sanconf -configure -library MPC0100013 SAN_STORE host33
-drive_template DriveTemplate.txt -library_template
LibraryTemplate.txt
Reconfiguration of
Library Device
If you want to reconfigure an existing library, use the -configure option to modify the
existing configuration. SANconf tool can be used the same way as with the initial
configuration except for the clients that already have drives configured on. It is
recommended that configuration information is first stored in the configuration file in
case of configuration failure. It is also recommended that a different filename is used so
that the initial configuration can be restored without any complications. SANconf tool
reuses the custom settings when reconfiguring a library.
Reconfiguring When Switch Changes SCSI Addresses
You can reconfigure or modify an existing logical library when, for example, SCSI
addresses change after a switch was rebooted. You can run the SANconf tool with the
same parameters that were used in the initial configuration. See the examples below.
Examples
To reconfigure a library device when the switch changes SCSI address using the
-hosts option, run the following command:
sanconf -configure -library MPC0100013 SAN_STORE host33 -hosts
host01 host02 host03
To reconfigure a library device using the configuration file when the switch changes
SCSI address, run the following command:
sanconf –list_devices mySAN.cfg -hosts host01 host02 host03
host33
sanconf -configure mySAN.cfg -library MPC0100013 SAN_STORE
host33 -hosts host01 host02 host03
Reconfiguring When New Clients Are Added
SANconf tool can add drives to an existing library on specified clients. Although not
necessary, it is recommended that all new clients are scanned first for configuration data
and then configured in the existing database.
Examples
To reconfigure a library device using the -hosts option when new clients are added to the
cell, run the following command:
sanconf -configure -library MPC0100013 SAN_STORE host33 -hosts
host04 host05
To reconfigure a library device when new clients are added to the cell using the
configuration file, run the following command:
sanconf –list_devices myNewHostsSAN.cfg -hosts host04 host05
sanconf -configure myNewHostsSAN.cfg -library MPC0100013
SAN_STORE host33 -hosts host04 host05
9
HP OpenView Storage Data Protector
SANconf Tool Readme File
Removing the
Configuration
Removing Drives
from an Existing
Library Device
When clients are removed from the existing SAN environment, you can run the SANconf
tool using the -remove_drives option to remove the configured drives that reside in a
library on the specified clients.
The following syntax for the removal of the configuration is provided:
Syntax
sanconf -
remove_drives LibraryName
[-hosts host_1 [host_n ... ] | -hostsfile
HostsFileName]
Note: No rescanning is required for this operation.
Example
To remove all drives in the library named SAN_STORE that are configured on hosts
host04 and host05, run the following command:
sanconf -remove_drives SAN_STORE -hosts host04 host05
Removing the Entire
Library Device
SANconf tool as a configuration tool does not provide an option to delete an entire
library from the IDB. You can perform this action by running the omniupload
command with the following option:
omniupload -remove_library LibraryName
For additional information on the omniupload command, refer to omniupload
man page.
SANconf Tool
Related omnirc
File Variable
The SANconf tool uses the following omnirc file variable:
• OB2SANCONFSCSITIMEOUT=s
Default value: 20 seconds
This variable sets the timeout value for SANconf command related operations and is
used on Windows systems. It must be set on all clients affected by the SANconf
command, before running the SANconf tool. The default value is recommended.
For more information on the location and usage of the omnirc file, refer to the
HP OpenView Storage Data Protector Administrator’s Guide.
Usage Synopsis
NAME
sanconf - SANconf tool is a utility that auto-configures a library within the SAN
environment. It gathers information on drives from the multiple clients and configures
them into a single library.
SYNOPSIS
sanconf -version | -help
sanconf -list[_devices] [ListFileName] [-hosts host_1 [host_n ... ] | -hostsfile
HostsFileName]sanconf -configure [ListFileName] -library LibSerNumber
LibraryName [PickerHostName] [DeviceTypeNumber
|".<DeviceTypeExtension>"] [-hosts host_1 [host_n ... ] |-hostsfile
HostsFileName] [-drive_template DrvTplFileName][-library_template
LibTplFileName]
sanconf -remove_drives LibraryName [-hosts host_1 [host_n... ] | -hostsfile
HostsFileName]
10
HP OpenView Storage Data Protector
SANconf Tool Readme File
OPTIONS
-version
Displays the version of the SANconf tool.
-help
Displays the usage synopsis for the SANconf tool.
-list[_devices] [ListFileName]
This option scans Data Protector clients gathering information on SCSI addresses of
drives and pickers connected to the clients via the SAN environment and lists the
gathered information. When ListFileName parameter is specified, the information
acquired during the scan of clients is saved to the configuration file.
-hosts host_1 [host_n ... ]
Specify the -hosts option if you want to limit the SANconf actions only the specified
clients. Other clients in the Data Protector cell are skipped.
-hostsfile HostsFileName
Specify the -hostsfile option if you want to limit the SANconf actions only the
clients specified in the HostsFileName. Other clients in the Data Protector cell are
skipped. The HostsFileName is comprised of an ASCII list of clients, one client
per line.
-configure [ListFileName]
This option scans, lists, configures, or reconfigures the specified library. Only one
library can be configured with each invocation of the command line. If the
ListFileName option is specified, the scan and data information that was saved
to a file during the scan of clients is used to configure the library. If this option is not
specified, SANconf tool will dynamically scan, list, and configure the library.
-library LibSerNumber LibraryName
[PickerHostName][DeviceTypeNumber | ".<DeviceTypeExtension>"]
Specify the -library parameter to configure or reconfigure the specified library.
Only one library can be configured with each invocation of the command line.
SANconf creates only one logical library per physical library in the system and all
devices on all specified clients. If the PickerHostName parameter is specified, the
specified client will control the picker for the library being configured. If this
parameter is not specified, the library will be created with robotics on all clients
within the Data Protector cell. When DeviceTypeNumber parameter is used, the
drives of that type will be configured in the library. When DeviceTypeNumber is
not specified, the DLT drive types are used as a default. Only one type number may
be specified per library. If you use the “.<DeviceTypeExtension>” parameter
instead of the DeviceTypeNumber parameter, you can specify the device type
extension of the tape device to be configured in the library. Supported extensions
are:”.9840”, “.DDS”, “.DLT”, and “.LTO”.
11
HP OpenView Storage Data Protector
SANconf Tool Readme File
-drive_template DrvTplFileName
This option alters the default configuration of each tape device added to the library.
The DrvTplFileName must be an ASCII file with one parameter specified per line.
Drive template supports the following parameters:
VERIFY
This parameter enables the CRC Check option specified in the Data Protector
GUI.
CLEANME
This parameter enables the Detect dirty drive option specified in the Data
Protector GUI.
RESCAN
This parameter enables the Rescan option specified in the Data Protector GUI.
-library_template LibTplFileName
This option alters the default configuration of the library. The LibTplFileName
must be an ASCII file with one parameter specified per line. Library template supports
the following parameters:
BARCODEREADER
This parameter enables the Barcode reader support option specified in the
Data Protector GUI.
BUSYDRIVETOSLOT
This parameter enables the Busy drive handling: Eject medium option
specified in the Data Protector GUI.
BUSYDRIVETOMAILSLOT
This parameter enables the Busy drive handling: Eject medium to
mail slot option specified in the Data Protector GUI.
-remove_drives LibraryName
This option removes all tape devices in the specified library. If you want to remove
drives on specific clients, you can use the –hosts host_1 [host_n ... ] or
-hostsfile HostsFileName option.
12
HP OpenView Storage Data Protector
SANconf Tool Readme File
Troubleshooting
Automatic Recovery
Upon Automatic
Configuration Failure
When you modify an existing configuration, you can reuse the configuration file created
during the previous successful execution of the sanconf -list_devices command.
In case that errors are encountered during the configuration and library is only partially
created, repeat the configuration using the same configuration file and recover the old
configuration.
If such a problem has occurred, perform the steps below:
1. Create a plain ASCII file named hosts.txt which includes all clients in the cell that
are connected to the same device and all together form your SAN environment.
Each client must be specified in a separate line. Scan the cell by running the
following command:
sanconf –list_drives mySAN.txt –hostsfile hosts.txt
2. Configure your library using the saved configuration file. Run the following
command:
sanconf –configure mySAN.txt -library LibSerNumber
LibraryName [PickerHostName] [DeviceTypeNumber]
-hostsfile hosts.txt
The successful configuration is automatically recovered. In case that you want later to
add, remove or modify the library and the SANconf tool fails for any reason, you can
repeat the above procedure to restore the successful configuration.
Drive Name
Convention
All drives created with the SANconf tool are named automatically by the SANconf tool.
Important: Drive names must not be changed manually because the reconfiguration will
not work.
The following drive naming conventions are used:
libname_index_host
libname_index_busindex_host
Example
A library named SAN_STORE a drive on a client host01 that is in position 2 in the
physical library uses the following drive name:
"SAN_STORE_2_host01"
Example
If you have a dual HBA environment, a bus number is also appended. If there is another
drive located on the client host01 that has an index 2 in the library and is seen on SCSI
adapter bus 4, it will be named:
“SAN_STORE_2_4_host01"
13
HP OpenView Storage Data Protector
SANconf Tool Readme File
Drive Locking
Mechanism
After a successful configuration of the SAN environment there are multiple logical
drives created that represent one physical drive. Data Protector uses a locking
mechanism that prevents a backup using one logical drive and then starting a backup
using a different logical device that maps to the same physical drive. This mechanism is
called Lock Name.
A lock name can be used by all logical drives that represent one physical drive.
SANconf tool automatically creates locknames for drives that it is configuring. A lock
name consists of drive vendor ID string, product ID string and its serial number.
Example
A HP DLT 8000 drive with vendor ID "HP", product ID "DLT8000" and with the serial
number "A1B2C3D4E5" will be automatically configured with the following lock name:
“HP:DLT8000:A1B2C3D4E5”
You must not change the lock names that were created by the SANconf tool in order for
Data Protector to function properly. All other logical drives that are created manually
and represent physical drives configured by SANconf tool must also use lock names
created by SANconf tool.
All brand names are trademarks of their respective owners.
Technical information in this document is subject to change without notice.
© 2003 Hewlett-Packard Company
06/2003
14
Download PDF
Similar pages