OpenVaultIntroductionInstallation Information for IRIX SystemsInstallation Information for SGI ProPack for Linux SystemsActivating Your OpenVault LicenseInstallation and Support NotesIntroduction
1. Introduction
These notes describe release 1.5.5 of OpenVault, a software
product that allows sharing of removable media libraries and
drives, media cataloging and lifecycle management, and other
features.
Note: Packaged with your software is a separate sheet that
contains the Software License Agreement. This
software is provided to you solely under the terms
and conditions of the Software License Agreement.
Please take a few moments to review the Agreement.
This document contains the following chapters:
1. Introduction
2. Installation Information for IRIX Systems
3. Installation Information for SGI ProPack for Linux
Systems
4. Activating Your OpenVault License
5. Installation and Support Notes
1.1 OpenVault Overview
An OpenVault server is a piece of software that manages the
use of removable media devices and libraries. Components of
the OpenVault architecture called Library Control Programs
(LCPs) and Drive Control Programs (DCPs) are pieces of
software that control the specific device they are
configured for and provide services to the OpenVault server.
Client applications request services from the OpenVault
server which then makes use of the LCPs and DCPs available
to it so the server can fulfill the request from the client
application.
The OpenVault server, LCPs, DCPs, and client applications
can all run on different systems in a local or wide area
network. The application can only access drives that are
connected to the same system it is running on, OpenVault
does not provide data movement across the network.
The OpenVault system allows removable media libraries and
drives to be shared between applications. It also provides
greater access to information about the health of the media
to the System Administrator.
Refer to the OpenVaultAdministrator'sGuide (Silicon
Graphics document number 007-3211-008) for more information
about the services provided by the OpenVault software, as
well as instructions about how to configure and manage the
system.
1.2 Release Identification Information
Following is the release identification information for
OpenVault 1.5.5:
SoftwareProduct OpenVault
Version 1.5.5
ProductCodeforIRIXsystems SC4-OPVAULT-I-1.5.5
ProductCodeforSGIProPackforLinuxsystems SC5-OPVAULT-L-1.5.5
SystemSoftwareReqs. IRIX: IRIX 6.5.23 or later
Linux: SGI ProPack 3 or later
SGI Propack 4 or later
Administrator'sGuide Silicon Graphics Document Number
007-3211-008
1.3 Hardware Requirements
The system selected to be an OpenVault server does not have
to have any media devices attached to it, it is simply a
central control engine. The systems that have the libraries
and drives attached to them must be running LCPs and DCPs,
respectively.
Drive Control Programs (DCPs) have been developed for the
following tape drives so far:
+ DLT2000
+ Quantum DLT4000
+ Quantum DLT7000
+ Quantum DLT8000
+ Quantum SuperDLT1
+ Quantum SDLT320
+ Quantum SDLT600
+ IBM 3590 "Magstar"
+ IBM 3590E "Magstar"
+ IBM 3590H "Magstar"
+ IBM 3592J
+ Sony AIT-1
+ Sony AIT-2
+ Sony AIT-3
+ Sony SAIT-1
+ Sony GY-2120 (IRIX only)
+ Sony GY-8240 (IRIX only)
+ StorageTek 9840 and T9840B
+ StorageTek T9840C
+ StorageTek T9940A
+ StorageTek T9940B
+ Certance (Seagate) LTO Ultrium Generation 1
+ IBM SCSI LTO Ultrium Generation 1
+ IBM FibreChannel LTO Ultrium Generation 1
+ IBM SCSI LTO Ultrium Generation 2
+ IBM FibreChannel Ultrium Generation 2
+ IBM SCSI LTO Ultrium Generation 3
+ IBM FibreChannel Ultrium Generation 3
+ HP SCSI LTO Ultrium Generation 2
+ HP FibreChannel LTO Ultrium Generation 2
+ HP SCSI LTO Ultrium Generation 3
+ HP FibreChannel LTO Ultrium Generation 3
+ StorageTek SD-3 "Redwood" (IRIX only)
+ StorageTek "Timberline" (IRIX only)
+ Ampex DIS/DST drive models (IRIX only) (with 3rd party
DCP from Ampex)
+ A software simulation of a drive used for testing.
+ Please check the Silicon Graphics Web site for more
DCPs: http://www.sgi.com/software/openvault
Library Control Programs (LCPs) have been developed for the
following automated libraries so far:
+ All ADIC libraries that use the DAS interface,
including the AML-series, Scalar 1000, Scalar 10K, and
dual-aisle Scalar 10K.
+ ADIC Scalar 24/100/1000/10K, controlled via SCSI
+ ADIC i2000, controlled via SCSI
+ IBM 3584 library using the SCSI interface.
+ IBM-3494 libraries using the TCP/IP control interface.
(IRIX only)
+ StorageTek 9710, 9714, 9730, and 9740 libraries using
the SCSI interface.
+ StorageTek L20, L40, L80, L180, L700, L700e, and SL500
libraries using the SCSI interface.
+ All StorageTek libraries controlled by the ACSLS
interface, release 5.1 or later.
+ Sony DMS-B35 and DMS-PSC "PetaSite" libraries, and Sony
CSM-200, CSM-100, and CSM-60 libraries (IRIX only)
+ Ampex 712 or other SCSI-attached libraries (IRIX only)
(with 3rd party LCP from Ampex)
+ A software simulation of a library used for testing.
+ Please check the Silicon Graphics Web site for more
LCPs: http://www.sgi.com/software/openvault
1.4 Firmware Requirements
Silicon Graphics tests specific firmware revisions for each
drive and library with OpenVault. It is our intention that
OpenVault work correctly with all firmware revisions of each
device, but it is possible that some firmware revisions will
not be supported.
1.5 Online Release Notes
For IRIX systems:
After you install the online release notes for a product
(the relnotes subsystem), you can view the release notes
on your screen.
Note: You can read the online release notes for most
products before installing the software. Refer to
the booklet in your CD-ROM case for more
information.
If you have a graphics system, select ``Release Notes''
from the Help submenu of the Toolchest. This displays the
grelnotes(1) graphical browser for the online release
notes.
Refer to the grelnotes(1) man page for information on
options to this command.
If you have a non-graphics system, you can use the
relnotes command. Refer to the relnotes(1) man page for
accessing the online release notes.
For SGI ProPack for Linux systems:
You can access the release notes from the following
location:
/usr/share/doc/openvault-1.5.5/README
1.6 Product Support
Silicon Graphics, Inc., provides a comprehensive product
support maintenance program for its products.
If you are in the United States or Canada and would like
support for your Silicon Graphics-supported products,
contact the Technical Assistance Center at +1 (800) 800-
4SGI. If you are outside these areas, contact the Silicon
Graphics subsidiary or authorized distributor in your
country.

Installation Information for IRIX Systems
2. Installation Information for IRIX Systems
This chapter provides supplemental information regarding
installation of OpenVault 1.5.5. on IRIX systems. For
detailed information on this installation process, refer to
the following documents:
+IRIXAdmin: SoftwareInstallationandLicensing+OpenVaultAdministratorsGuide
When upgrading an existing OpenVault 1.4.2 or earlier
system, please also see the information in Chapter 5 of this
document.
Once the executables for the OpenVault product have been
installed, the OpenVault environment must be configured.
The following script must be run after installation:
/usr/sbin/ov_admin
It provides options for configuring the server and each
system that has libraries or drives attached, ie OpenVault
client systems.
2.1 OpenVault Subsystems
OpenVault 1.5.5 for IRIX systems includes subsystems in
three major groups. The first group contains the OpenVault
server, administrative tools, reference pages,
documentation, and example source code. The second group
contains Library Control Programs and support software. The
third group contains Drive Control Programs and support
software. If you select the 'default' installation option
of swmgr(1) or inst(1), all server software, administrative
tools, documentation, LCPs, and DCPs will be installed.
Using the 'default' installation option is valid for both
OpenVault server and client machines; when configuring
OpenVault you choose the OpenVault server machine and which
DCPs and LCPs to configure; if unused OpenVault components
are installed, they simply are not used. It is not valid to
mix OpenVault 1.5.5 subsystems with OpenVault 1.4.2 or
earlier subsystems on the same machine.
2.1.1 OpenVault Server Subsystems
These generally only need to be installed on the system that
is running the OpenVault server. There is only one such
system in a single administrative domain. The Installation
and Configuration chapter in the administrative guide, found
in the OpenVault.docs.adminguide contain detailed
instructions on how to determine which subsystems you must
install on a given host.
Certain subsystems in this group should also be installed on
machines running LCPs or DCPs. Eg: OpenVault.sw.config.
Certain subsystems in this group should also be installed on
machines running the administrative tools. Eg:
OpenVault.sw.admin and OpenVault.man.*.
OpenVault.sw.admin
Command line tools used to administer an OpenVault
environment. These are the tools released in the
OpenVault.sw.admin_new subsystem in OpenVault
1.4.2 and earlier.
OpenVault.sw.config
Scripts used to configure systems that are running
components of the OpenVault environment (eg: the
server or an LCP or a DCP).
OpenVault.sw.core
OpenVault core servers.
OpenVault.sw.startstop
OpenVault scripts to start and stop daemons.
OpenVault.sw.user
Common tools and utility programs available to
non-priviledged users that make use of OpenVault.
OpenVault.upgrade.files
A script to help when upgrading from an existing
installation of OpenVault 1.4.2 or earlier. It
will automatically run if it is selected for
installation.
OpenVault.docs.adminguide
A Portable Document Format (PDF) version of the
OpenVaultAdministrator'sGuide.
OpenVault.docs.designdoc
An Hypertext Markup Language (HTML) version of the
OpenVault design and specification documents.
OpenVault.man.manpages
The reference pages (man pages) for the OpenVault
administrative command line utilities.
OpenVault.man.relnotes
These release notes.
OpenVault.dev.examples
C Language source code for example programs using
the OpenVault client interface.
OpenVault.dev.include
C language header files necessary for programs to
use the client interface to OpenVault.
OpenVault.dev.libs
C Libraries that can be used by client programs to
access the OpenVault interfaces.
2.1.2 OpenVault Library Control Program Subsystems
Each subsystem can be individually installed on systems
spread throughout the environment, choosing the appropriate
subsystem for each piece of hardware attached to each
system.
OpenVault.lcp.ADICDAS
An LCP for ADIC libraries that use the DAS
interface
OpenVault.lcp.ADICSCSI
An LCP for the ADIC Scalar 24/100/1000/10K SCSI-
attached libraries.
OpenVault.lcp.ADICISERIES
An LCP for the ADIC i-series SCSI-attached
libraries
OpenVault.lcp.IBM3494
An LCP for the IBM-3494 library using the TCP/IP
control interface.
OpenVault.lcp.SONYPSC
An LCP for Sony DMS-B35 and DMS-PSC "PetaSite"
libraries, and Sony CSM-200, CSM-100, and CSM-60
libraries (IRIX only)
OpenVault.lcp.GENERIC
An LCP for the IBM 3584 library.
OpenVault.lcp.STKACSLS
An LCP for StorageTek libraries controlled through
the ACSLS interface.
OpenVault.lcp.STK9700
An LCP for the StorageTek 9700 series libraries
(eg: the 9710, 9714, 9730, and 9740).
OpenVault.lcp.STKLseries
An LCP for the StorageTek L-series libraries (eg:
the L20, L40, L80, L180, L700, L700e, and SL500).
OpenVault.lcp.pseudo
An LCP that only simulates a real library. It is
used for testing of the OpenVault environment.
2.1.3 OpenVault Drive Control Program Subsystems
Each subsystem can be individually installed on systems
spread throughout the environment, choosing the appropriate
subsystem for each piece of hardware attached to each
system.
OpenVault.dcp.DLT2000
A DCP for DLT 2000 drives.
OpenVault.dcp.DLT4000
A DCP for DLT 4000 drives.
OpenVault.dcp.DLT7000
A DCP for DLT 7000 drives.
OpenVault.dcp.DLT8000
A DCP for DLT 8000 drives.
OpenVault.dcp.SuperDLT1
A DCP for Quantum SuperDLT1 drives.
OpenVault.dcp.SDLT320
A DCP for Quantum SDLT320 drives.
OpenVault.dcp.SDLT600
A DCP for Quantum SDLT600 drives.
OpenVault.dcp.IBM3590
A DCP for IBM 3590 "Magstar" drives.
OpenVault.dcp.IBM3590E
A DCP for IBM 3590E "Magstar" drives.
OpenVault.dcp.IBM3590H
A DCP for IBM 3590H "Magstar" drives.
OpenVault.dcp.IBM3592J
A DCP for IBM 3592J drives.
OpenVault.dcp.STK9840
A DCP for StorageTek 9840 and T9840B drives.
OpenVault.dcp.STK9840C
A DCP for StorageTek T9840C drives.
OpenVault.dcp.STK9940
A DCP for StorageTek T9940A drives.
OpenVault.dcp.STK9940B
A DCP for StorageTek T9940B drives.
OpenVault.dcp.Ultrium1
A DCP for Certance (formerly Seagate) SCSI LTO
Ultrium Generation 1 drives, IBM SCSI LTO Ultrium
Generation 1 drives, and IBM FibreChannel LTO
Ultrium Generation 1 drives.
OpenVault.dcp.Ultrium2
A DCP for IBM SCSI LTO Ultrium Generation 2
drives, IBM FibreChannel LTO Ultrium Generation 2
drives, HP SCSI LTO Ultrium Generation 2 drives,
and HP FibreChannel LTO Ultrium Generation 2
drives.
OpenVault.dcp.Ultrium3
A DCP for IBM SCSI LTO Ultrium Generation 3
drives, IBM FibreChannel LTO Ultrium Generation 3
drives, HP SCSI LTO Ultrium Generation 3 drives,
and HP FibreChannel LTO Ultrium Generation 3
drives.
OpenVault.dcp.STKredwood
A DCP for StorageTek SD-3 "Redwood" drives.
OpenVault.dcp.STKtimberline
A DCP for StorageTek 9490 "Timberline" drives.
OpenVault.dcp.AIT1
A DCP for Sony AIT-1 drives.
OpenVault.dcp.AIT2
A DCP for Sony AIT-2 drives.
OpenVault.dcp.AIT3
A DCP for Sony AIT-3 drives.
OpenVault.dcp.SAIT1
A DCP for Sony SAIT-1 drives.
OpenVault.dcp.GY2120
A DCP for Sony GY-2120 drives.
OpenVault.dcp.GY8240
A DCP for Sony GY-8240 drives.
OpenVault.dcp.pseudo
A DCP that only simulates a real drive. It is
used for testing of the OpenVault environment.
2.2 OpenVault 1.5.5 Subsystem Disk Space Requirements
This section lists the subsystems (and their sizes) of
OpenVault 1.5.5 for IRIX systems.
For complete installation instructions, please see Chapter 1
of the OpenVaultAdministrator'sGuide.
Note: The listed subsystem sizes are approximate. Refer to
the software installer documentation (listed at the
beginning of this chapter) for information on finding
exact sizes.
Subsystem Name Subsystem Size
(Kilobytes)
OpenVault.dcp.AIT1 (default) 284
OpenVault.dcp.AIT2 (default) 296
OpenVault.dcp.AIT3 (default) 300
OpenVault.dcp.SAIT1 (default) 280
OpenVault.dcp.GY2120 (default) 280
OpenVault.dcp.GY8240 (default) 280
OpenVault.dcp.DLT2000 (default) 292
OpenVault.dcp.DLT4000 (default) 308
OpenVault.dcp.DLT7000 (default) 324
OpenVault.dcp.DLT8000 (default) 328
OpenVault.dcp.SDLT320 (default) 308
OpenVault.dcp.SDLT600 (default) 484
OpenVault.dcp.SuperDLT1 (default) 304
OpenVault.dcp.IBM3590 (default) 284
OpenVault.dcp.IBM3590E (default) 292
OpenVault.dcp.IBM3590H (default) 296
OpenVault.dcp.IBM3592J (default) 296
OpenVault.dcp.STK9840 (default) 288
OpenVault.dcp.STK9840C (default) 284
OpenVault.dcp.STK9940 (default) 280
OpenVault.dcp.STK9940B (default) 284
OpenVault.dcp.STKredwood (default) 304
OpenVault.dcp.STKtimberline (default) 280
OpenVault.dcp.Ultrium1 (default) 296
OpenVault.dcp.Ultrium2 (default) 304
OpenVault.dcp.Ultrium3 (default) 468
OpenVault.dcp.pseudo (default) 228
OpenVault.dev.examples (default) 64
OpenVault.dev.include (default) 60
OpenVault.dev.libs (default) 748
OpenVault.docs.adminguide (default) 6624
OpenVault.docs.designdoc (default) 608
OpenVault.lcp.ADICDAS (default) 500
OpenVault.lcp.ADICSCSI (default) 360
OpenVault.lcp.ADICISERIES (default) 360
OpenVault.lcp.IBM3494 (default) 648
OpenVault.lcp.SONYPSC (default) 648
OpenVault.lcp.STK9700 (default) 356
OpenVault.lcp.STKACSLS (default) 1012
OpenVault.lcp.STKLseries (default) 356
OpenVault.lcp.pseudo (default) 260
OpenVault.man.manpages (default) 256
OpenVault.man.relnotes (default) 84
OpenVault.sw.admin (default) 4660
OpenVault.sw.config (default) 336
OpenVault.sw.core (default) 6148
OpenVault.sw.startstop (default) 12
OpenVault.sw.user (default) 460
OpenVault.upgrade.files (default) 52
2.3 Installation Method
All of the subsystems for OpenVault can be installed using
IRIX. You do not need to use the miniroot. Refer to the
software installation documents (listed at the beginning of
this chapter) for complete installation instructions.
2.4 Prerequisites
OpenVault is designed to run on IRIX 6.5.22 and above on all
server-class hardware platforms. Specifically: Challenge M,
L, and XL, and Origin 200, 2000, and 3000.
2.5 Compatibility
The location of many of the OpenVault executables and other
files changed in OpenVault 1.5.0. DMF has various scripts
that reference OpenVault files. Because of this, it is
recommended that you use DMF 3.0.1 or later release with
OpenVault 1.5.5.
If OpenVault is used as a TMF loader, TMF 1.4.2 or later is
required with OpenVault 1.5.5 on IRIX and SGI ProPack 3.x
Linux systems. TMF 1.5 or later is required with OpenVault
1.5.5 on SGI ProPack 4.x Linux systems.
LCPs and DCPs that were written to work with OpenVault 1.4.2
may require a new "config.sh" script to work with OpenVault
1.5.5. This is because the OpenVault infrastructure requires
the config.sh script to have functions for starting and
stopping the LCP/DCP. This is an important consideration if
you have LCPs or DCPs obtained from a source other than SGI.
If you have such LCPs or DCPs, please send email to the
OpenVault email reflector, openvault-discuss, and we will
then work with the other vendors to obtain the proper
config.sh scripts. The web page
http://www.sgi.com/software/opensource/openvault/resources.html
contains information about this mailing list.
2.6 Configuration Files
Here is a list of files containing configuration values that
may exist on a system:
/var/opt/openvault/clients/admin/keys
/var/opt/openvault/clients/dcp/*/*
/var/opt/openvault/clients/lcp/*/*
/var/opt/openvault/server/config/config
/var/opt/openvault/server/config/core_keys
/var/opt/openvault/server/config/services
/etc/ibmatl.conf
2.7 Files Not Listed by versions
There are many files that will be created by a running
OpenVault server or a DCP that will not be listed by the
versions(1M) command.
All the files created by a normally configured OpenVault
server, DCP, or LCP will be created within the
/var/opt/openvault directory tree. Specifically, files will
be created and modified in:
/var/opt/openvault/clients/dcp
/var/opt/openvault/clients/lcp
/var/opt/openvault/clients/handles
/var/opt/openvault/clients/admin
/var/opt/openvault/server/config
/var/opt/openvault/server/dbase
/var/opt/openvault/server/logs

Installation Information for SGI ProPack for Linux Systems
3. InstallationInformationforSGIProPackforLinuxSystems
This chapter provides supplemental information regarding
installation of OpenVault 1.5.5 on SGI ProPack for Linux
systems. More information on this process is available in
the following document:
+OpenVaultAdministratorsGuide
Once the executables for the Openvault product have been
installed, the OpenVault environment must be configured.
The following script must be run after installation:
/usr/sbin/ov_admin
It provides options for configuring the server and each
system that has libraries or drives attached, ie OpenVault
client systems.
3.1 Installing the OpenVault RPM
OpenVault 1.5.5 for SGI ProPack for Linux systems is
supplied as two RPM files.
The file openvault-sw-1.5.5-0.ia64.rpm contains all of the
OpenVault server software, administrative tools, reference
pages, documentation, and supported Library Control Programs
and Drive Control Programs.
The file openvault-dev-1.5.5-0.ia64.rpm contains code for
writing OpenVault applications, including header files,
libraries, and sample code.
To install the openvault-sw-1.5.5-0.ia64.rpm rpm, log in as
root, change directories to the location of the openvault-sw-1.5.5-0.ia64.rpm file, and issue the following command:
%rpm-Uvhopenvault-sw-1.5.5-0.ia64.rpm
3.2 Configuration Files
Here is a list of files containing configuration values that
may exist on a system:
/var/opt/openvault/clients/admin/keys
/var/opt/openvault/clients/dcp/*/*
/var/opt/openvault/clients/lcp/*/*
/var/opt/openvault/server/config/config
/var/opt/openvault/server/config/core_keys
/var/opt/openvault/server/config/services
/etc/ibmatl.conf
3.3 Files Not Listed by rpm
There are many files that will be created by a running
OpenVault server or a DCP that will not be listed by the
query options of the rpm(8) command.
All the files created by a normally configured OpenVault
server, DCP, or LCP will be created within the
/var/opt/openvault directory tree. Specifically, files will
be created and modified in:
/var/opt/openvault/clients/dcp
/var/opt/openvault/clients/lcp
/var/opt/openvault/clients/handles
/var/opt/openvault/clients/admin
/var/opt/openvault/server/config
/var/opt/openvault/server/dbase
/var/opt/openvault/server/logs

Activating Your OpenVault License
4. Activating Your OpenVault License
Your copy of OpenVault requires at least one software
license to operate. This chapter defines some important
software licensing terms, describes the basic procedure for
obtaining, installing, and testing a software license for
OpenVault, and lists addresses and phone numbers that you
can use to contact Silicon Graphics License Administration.
For more information about software licenses on IRIX
systems, see the IRIXAdmin: SoftwareInstallationandLicensing, which provides detailed information on obtaining,
installing, using, and administering software licenses. It
is included in the system software documentation; the online
version is in the subsystem "eoe.books.IA_InstLicns".
4.1 A Few Definitions
A softwarelicense is a collection of information that,
after installation, allows you to use a licensed software
product on one or more systems. The software license
information includes the license type, the license
expiration date, a license password, and host identification
numbers (hostid and serial numbers). You can get a system's
hostid number by giving the command /sbin/sysinfo -s or
/usr/sbin/lmhostid. Note that these both return the same
value, but the former gives the value in decimal, whereas
the latter returns it in hexadecimal. The sysinfo command is
available only on IRIX.
The license must be installed on the system that has the
hostid number included in the software license information.
If the hostid is Any, the software license can be installed
on any system.
There are two types of software licenses, node-locked and
concurrent, and two durations of software licenses,
temporary and permanent:
node-locked A node-locked license is installed on a
particular system (node) and allows the
licensed software to run on that system.
concurrent A concurrent license allows the licensed
software to run on one or more systems in the
network simultaneously. OpenVault uses node-
locked licenses only.
temporary A temporary license allows you to use the
licensed software for a short period, typically
a week to a few months. The expiration date
tells you the last date on which you can use
the licensed software. Temporary licenses are
often shipped with software so that you can use
the software before a permanent license is
issued. OpenVault is shipped with at least one
temporary license. Due to the harsh nature of
this software's reaction to out-of-date
licenses (see section 5 of this document for
more information), please be certain to upgrade
your temporary license(s) to the permanent type
well before they expire.
permanent A permanent license allows you to use this
release of the licensed software for a very
long time. For example, an expiration date in
the year 2038 indicates a permanent license.
Permanent licenses are only issued for software
that has been purchased.
4.2 Obtaining and Installing a Software License
This section explains the procedure for obtaining and
installing a software license: checking to see if you have
received software license information, determining if you
need to install a license, requesting software license
information if you need it, identifying the system on which
you will install the license, installing the software
license information, and verifying that the license is
working.
1. Check to see if you have received software license
information.
Software license information is distributed in several
ways: on labels attached to a Software License
Registration card, on sheets of paper included with
the product, or by mail, FAX, or electronic mail.
This product is shipped with one or more licenses, all
temporary. Each license enables a particular set of
functions for the server. If you are updating to
OpenVault from any previous release, you need to
obtain and install a new license.
If you have received both a temporary license and a
permanent software license, install the permanent
license; do not install the temporary license. If you
have received a permanent license, you should install
it because it enables you to use the software that you
have purchased. If you have received a temporary
software license and do not need to use the software
immediately, you may choose to wait to install a
license until you obtain the permanent license.
2. Request a software license if you don't have any.
To obtain a software license, fill out the Software
License Registration card that was included with the
software (or information on the Web page,
http://www.sgi.com/Products/license.html). Send the
information or the card by electronic mail
(preferred), FAX, or mail to Silicon Graphics License
Administration or your local service provider (see the
next section for addresses). After your request is
received by Silicon Graphics or your local service
provider, you should receive a software license within
two business days.
3. Identify the system on which you will install the
software license.
Because OpenVault software license information must be
installed on a particular system, follow these
guidelines:
+ If the hostid is a number, identify the system
that returns that number as the output of the
command /sbin/sysinfo -s. (It may be easier to
identify the system using the serial number,
which is included in the software license
information. Note also that the lmhostid command
returns this same number in hexadecimal, as
described above. On SGI ProPack for Linux
systems, use the lmhostid command.)
The license you have in your license.dat file may
have a # before the host id number. The #
signifies "decimal"; if you have a host id given
without the #, it means that it's in hexadecimal.
+ If the hostid is Any, you can install the license
on any system you choose.
+ If the hostid number included with the software
license information doesn't match the hostid
number of the system on which you want to install
the license, contact Silicon Graphics License
Administration.
4. Install the software license (temporary or permanent).
Check the ``license type'' listed in the software
license information to find out whether the license is
a node-locked license or a concurrent license. The
installation procedure depends on the license type:
+ See both Chapter 3, ``Installing Node-locked
Licenses,'' in the NetworkLicenseSystemAdministrationGuide and Chapter 2, ``Installing
OpenVault,'' in the OpenVaultAdministrator'sGuide for instructions on installing the
licenses.
5. Verify that the software license has been successfully
installed.
When you run ov_admin on the OpenVault server, it will
attempt to start the licensed program in OpenVault. If
no valid licenses are installed, an error message will
be displayed. For example:
WhatisthenameoftheOpenVaultserver?[citron]TheOpenVaultserverisnotrunning;wouldyouliketostartit?[Yes]Error:nolicenseavailableforopenvault.(Nosuchfeatureexists)
If you installed a temporary license and you are
entitled to a permanent license, replace the temporary
license with a permanent license as soon as possible
to ensure uninterrupted use of OpenVault.
4.3 Contacting Silicon Graphics License Administration
In the United States and Canada, Silicon Graphics License
Administration provides software license information to
Silicon Graphics customers. You can contact Silicon
Graphics License Administration in these ways:
Electronic mail: license@sgi.com
FAX: +1 (650) 390-0537
Mail: Software Licensing M/S 134
Silicon Graphics, Inc.
P.O. Box 7311
Mountain View, CA 94039-9600
In an emergency, you can telephone Silicon Graphics at
+1 (800) 800-4744.
If you are not in the United States or Canada, or if you
purchased the system or software from a vendor other than
Silicon Graphics, please contact your local service
provider.

Installation and Support Notes
5. Installation and Support Notes
5.1 Important Upgrade Information
This section is applicable only for IRIX systems. If you
are upgrading OpenVault over an existing installation of
version 1.4.2 or earlier, note the following:
+ The location of many files changed in 1.5.0. Files
previously located in /usr/OpenVault have moved to
/usr/openvault and /var/opt/openvault. As part of the
upgrade process, existing OpenVault configuration,
database and log files are copied from their old
locations in /usr/OpenVault to their new locations in
/var/opt/openvault. Some of the files may also be
modified, to conform to what OpenVault 1.5.5 expects.
The old files are left in /usr/OpenVault.
+ The script /usr/OpenVault/setup, which was used in
OpenVault 1.4.2 and earlier releases to configure
OpenVault has been substantially rewritten and renamed
/usr/sbin/ov_admin. The "OpenVault Administrator's
Guide" contains more information on this command.
+ The script /usr/OpenVault/status has been replaced by
the command /usr/sbin/ov_procs.
+ The script /usr/OpenVault/stop has been replaced by the
command /usr/sbin/ov_stop, and /usr/OpenVault/start has
been replaced by /usr/sbin/ov_start.
+ The OpenVault server log files, previously located in
/usr/OpenVault/var, have been moved to
/var/opt/openvault/server/logs. The OpenVault database
files, previously located in /usr/OpenVault/var have
been moved to /var/opt/openvault/server/dbase. They
have also been renamed; instead of being named TEXT,
TEXT.n, LOG and LOG.n, they are now named DBASE,
DBASE.n, INDEX, and INDEX.n, where n is a digit.
+ The LCP configuration files and other files necessary
for running the LCP have been moved to the directory
/var/opt/openvault/clients/lcp/lcpname/inst, where
lcpname is the name of LCP, and inst is the instance
name of the LCP. DCP configuration files and other
files necessary for running the DCP were moved in a
similar fashion to subdirectories in
/var/opt/openvault/clients/dcp/dcpname/inst.
+ The file /usr/OpenVault/admin/keys has been moved to
/var/opt/openvault/clients/admin/keys.
+ The file /usr/OpenVault/mlm/config has been moved to
/var/opt/openvault/server/config/config.
+ The file /usr/OpenVault/mlm/services has been moved to
/var/opt/openvault/server/config/services.
+ The file /usr/OpenVault/var/core_keys has been moved to
/var/opt/openvault/server/config/core_keys.
+ Files located in /usr/OpenVault/include in OpenVault
1.4.2 are now located in /usr/openvault/include on IRIX
systems.
+ Files located in /usr/OpenVault/lib in OpenVault 1.4.2
are now located in /usr/openvault/lib32 on IRIX
systems.
+ Most of the OpenVault administrative commands are now
located in /usr/openvault/sbin on IRIX systems.
Additionally, links to them are created in /usr/sbin.
The following commands are located in
/usr/openvault/sbin on IRIX systems and have links in
/usr/sbin: ov_admin, ov_app, ov_cart, ov_cartgroup,
ov_carttype, ov_dcstats, ov_drive, ov_drivegroup,
ov_dumptable, ov_eject, ov_import, ov_inject,
ov_library, ov_lscarts, ov_lsvols, ov_mount, ov_msg,
ov_operator, ov_part, ov_procs, ov_purge, ov_recycle,
ov_scandev, ov_shutdown, ov_slottype, ov_start,
ov_stop, ov_system, ov_task, ov_unmount, and ov_vol.
Most of these commands were installed in
/usr/OpenVault/admin_new, and had links in /usr/sbin,
in OpenVault 1.4.2.
+ These OpenVault commands are located in
/usr/openvault/bin on IRIX systems, and have links in
/usr/bin: ov_reqsh, ov_stat, and ov_umsh.
+ Files located in /usr/OpenVault/admin in OpenVault 1.2
or earlier are no longer installed.
+ STK-9840 DCPs that were created in an OpenVault release
prior to 1.4.1 and have not been reconfigured since
that time will not work after the conversion to 1.5.5
because their config files contain only the deprecated
STK9840 definitions which have been removed from the
database as part of the 1.5.5 database conversion. To
get them working again, execute ov_admin and select the
"2 - Manage DCPs for locally attached Drives" option,
then select "2 - Modify a DCP" for one of the non-
working DCPs. Follow the instructions for modifying
the DCP, but simply respond to the questions with their
previously-used values. (ov_admin will prompt with
those, so only carriage returns should be needed.) The
act of modifying a DCP causes its config file to be
refreshed using more recent definitions, and so the
reconfigured DCP will be able to mount tape
successfully. Repeat these steps for any other STK-
9840 DCP older than release 1.4.1.
The following lists changes made when upgrading from
OpenVault 1.2 or earlier systems to OpenVault 1.4.2. It
is included here for historical purposes only.
+ The location of many files has changed. Files
previously located in /usr/OpenVault/lib have moved to
/usr/OpenVault/lib32. Files previously located in
/usr/OpenVault/bin have moved to /usr/OpenVault/usr.
Files previously located in /usr/OpenVault/admin have
been moved to /usr/OpenVault/admin_old. These files are
no longer installed by default. Files previously
located in /usr/OpenVault/admin_new have moved to
/usr/OpenVault/sbin. Links to these files are also
created in /usr/sbin.
+ The config files for the STK-9700 LCP's need a new
eighth line added after the polling interval and before
the list of drives. The new line is the default
cartridge shape. Accepted values for this line include:
'DLT' '3480' '8mm' 'DAT' 'D2-S' 'D2-M' 'D2-L' and 'DTF'
+ The administrative command line tools have been
reworked and may not be compatible with their
counterparts from previous versions. If any scripts or
programs fail with the new tools, the older versions
will still be available in /usr/OpenVault/admin.
5.2 Installation Considerations
The OpenVault server should be installed on one system in an
administrative domain that has been chosen for that task.
That system should be both reliable and highly available,
access to removable media drives and libraries will
completely depend on that system being available.
Library Control Programs and their support files should be
installed on those systems that have libraries attached to
them. When the LCP is configured, it must be told the
name/address of the system running the OpenVault server.
Drive Control Programs, like Library Control Programs,
should be installed on those systems that have drives
attached to them. When the DCP is configured, it must be
told the name/address of the system running the OpenVault
server.
There will be low bandwidth but time-sensitive information
flowing between the LCPs and the server and the DCPs and the
server so a reliable network connection is also important.
5.3 Updates to the OpenVault Server
Updates to the OpenVault server will become available from
time to time.
5.4 New Library and Drive Control Programs
New Library and Drive Control Programs will become available
from time to time. Please check the Silicon Graphics Web
site for a current listing of the supported devices and the
latest versions of the LCPs and DCPs required to interface
to them. The Web address is:
http://www.sgi.com/software/openvault
5.5 Portions of OpenVault are Licensed as Open Source
Portions of this release of OpenVault are licensed as Open
Source software. The source code for those portions can be
obtained from the Silicon Graphics Web site. The Web
address is:
http://www.sgi.com/software/opensource/openvault
5.6 Copyrights, Trademarks, and Limited Rights Legend
COPYRIGHT (c) 1997, 1998, 2000, 2002-2004, Silicon Graphics,
Inc. All rights reserved; provided portions may be copyright
in third parties, as indicated elsewhere herein. No
permission is granted to copy, distribute, or create
derivative works from the contents of this electronic
documentation in any manner, in whole or in part, without
the prior written permission of Silicon Graphics, Inc.
LIMITED RIGHTS LEGEND
The electronic (software) version of this document was
developed at private expense; if acquired under an agreement
with the USA government or any contractor thereto, it is
acquired as "commercial computer software" subject to the
provisions of its applicable license agreement, as specified
in (a) 48 CFR 12.212 of the FAR; or, if acquired for
Department of Defense units, (b) 48 CFR 227-7202 of the DoD
FAR Supplement; or sections succeeding thereto.
Contractor/manufacturer is Silicon Graphics, Inc., 1600
Amphitheatre Pkwy 2E, Mountain View, CA 94043-1351.
TRADEMARKS AND ATTRIBUTIONS
Silicon Graphics, SGI, the SGI logo, and IRIX are registered
trademarks, and Altix, OpenVault, Performance Co-Pilot, and
SGI ProPack are trademarks of Silicon Graphics, Inc, in the
United States and/or other countries worldwide. Ampex and
DST are trademarks of Ampex Corp. Digital is a trademark of
Digital Equipment Corporation. DLT and Quantum are
trademarks of Quantum Corp. EXABYTE is a trademark of
EXABYTE Corp. IBM and Magstar are trademarks of
International Business Machines Corp. Linux is a registered
trademark of Linus Torvalds, used with permission by Silicon
Graphics, Inc. RedWood, TimberLine, STK, and StorageTek are
trademarks of Storage Technology Corp. Sony is a registered
trademark of Sony Corp. UNIX is a registered trademark of
the Open Group in the United States and other countries.