2. Installation

2.1 Installing iXOS-JUKEMAN for Windows NT

The installation program for Windows NT copies files to a directory on your hard drive, installs iXOS-JUKEMAN services and sets up registry entries.

Before you begin installation, log on as administrator or a super user.

Start by setting up an installation directory, for example \ixos. Copy the jukeman.exe file into the directory and extract it by typing:

C:\ixos>jukeman.exe

The Jukeman installation program starts. In the setup dialog, specify where you want to install the iXOS-JUKEMAN user programs. The default is c:\jukeman.

Then select the portions of the software you want to install:

• The Jukebox File System includes the administration service and the jukebox daemon, which controls jukeboxes and supports both file system and administration service.
• The Administration Client administers a local or remote iXOS-JUKEMAN jukebox file system.
• The Recording Software contains the ISO 9660 formatter and the cdglow recording software.

You will probably want to install all these items.

Click OK to start installation. The installer creates an iXOS-JUKEMAN folder containing Jukeman Administrator and Jukeman CD-Writer icons. Icons from previous versions of iXOS-JUKEMAN are not removed automatically.

When installation is complete, reboot your system.

2.2 Installing iXOS-JUKEMAN for UNIX

Be sure all jukeboxes and drives are turned on. Create an empty directory for installation, using any new path. You need about 2 MB of disk space for installation.

Copy the iXOS-JUKEMAN software into the installation directory using the iXOS-JUKEMAN CD or distribution files from our web site, www.jukeman.com.

If you have an iXOS-JUKEMAN CD, then you can find the software packages for certain UNIX platforms and example configurations in a subdirectory called 'unix' or 'os'.

If you download the software via WWW, then please refer to the information on the Web pages. Important files, which should be downloaded, are the example configurations ('examples.tar.Z') and the compressed tar file for the appropriate UNIX platform.

Copy the compressed tar files into the installation directory. (For example 'solaris.tz' or 'os_solaris.tar.Z')

Extract the file corresponding to your operating system. For example, if your operating system is Solaris, enter:

# zcat < solaris.tz | tar xvf -

Now you have all the files except license files, device descriptions, and configuration. If you are upgrading an old installation, copy the old configuration files and the volumes database into the new installation directory. For first installation it is recommended to extract template configuration files. If necessary, you can obtain such templates (except volumes) by entering:

# zcat < examples.tz | tar xvf -

The volumes file is generated automatically by cdnfsd. Delete the .tar or .tz files by typing:

# rm *.tar.Z *.tz

Next, install the SCSI driver and create standard iXOS device names by typing:

# jmsetup

Since the cdnfsd program runs only under root id and the performance of cdglow is much better if it runs under root id, change the owner to root and the permissions to suid:

# chown root cdnfsd cdglow
# chmod u+s cdnfsd cdglow

For HP-UX 10.* change the permissions for the cdadm command:

# chown root cdadm
# chmod u+s cdadm

2.3 About SCSI Devices

This section explains how SCSI devices are represented by the iXOS-JUKEMAN generic SCSI driver.

2.3.1 Controllers, Buses, IDs, and LUNs

A computer can have several SCSI controllers for multiple SCSI buses. Each SCSI bus has 8 IDs, named 0-7. Normally, each device on a SCSI bus requires a SCSI ID. Jukeboxes often need one ID per drive and one for the changer. Usually, the SCSI controller occupies ID 7 and 0-6 are free for devices. SGI computers occupy ID 0, which means you can connect devices with IDs 1-7.

WARNING: When you connect devices to the bus, be sure the new devices use IDs that are not occupied by existing devices or the controller. If you use an occupied ID, you can damage your hardware.

Each SCSI ID can be split into 8 Logical Units (LUNs). The advantage of LUNs is that a jukebox uses only one SCSI ID, so you can attach more devices to a single bus. Addressing LUNs is explained later in this manual.

2.3.2 SCSI Devices and Device Names

In UNIX and NT, each device is represented by a device name, which is a path in the root file system tree.

Devices in NT

NT hides the devices, but iXOS-JUKEMAN makes the names visible. For example, SCSI ID x on bus y of controller z is represented by the path \\.\pzbytx. So if you have a PCI bus and put Adaptec twin adapters AHA 3940 into bus slots 0 to 2, you have 6 SCSI buses, and ID 4 on bus 1 of adapter 2 is represented as \\.\p2b1t4. Each enumeration begins with 0.

Within an ID, LUNs are represented by appending a comma and the LUN. So \\.p2b1t4,1 is LUN 1 of SCSI ID 4; \\.\p2b10t4 and \\.\p2b10t4,0 are the same.

If you know which paths represent your devices, you can use the inquiry command to verify the paths. For example, if you have a CDR 100 Recordable from NSM that is connected to the only SCSI bus on an NT system using SCSI ID 5, the command

inquiry \\.\p0b0t5

will return something like

0000002 \\.\p0b0t5 is HP's CD-drive "C4324/C4325"

where 0000002 is the time in 1/100 seconds. The message

0000000 Can't open \\.\p0b0t5

occurs if the SCSI driver doesn't run, the path is wrong, the device doesn't work, or the cable is bad. It is also possible that the device may be unknown if it did not run when you booted the system.

If you don't know the paths that represent your devices, call

scsidevs

which returns a complete list of all known and working SCSI devices.

If you add a new controller, you can use these commands to test if the path names have changed.

Devices in UNIX

In UNIX, all devices are located in a subdirectory of /dev. iXOS-JUKEMAN creates directories such as /dev/iXOS_SCSI0, /dev/iXOS_SCSI1, and so on.

Each directory represents a SCSI bus. Devices are represented by numbers. So if your bus is represented by /dev/iXOS_SCSI1, the device using SCSI ID 4 is represented as /dev/iXOS_SCSI1/4.

If you use LUNs, add a comma and the LUN number. dev/iXOS_SCSI1/4,1 is LUN 1 of the device using SCSI ID 4 on the bus represented by /dev/iXOS_SCSI1.

On Solaris, if you add devices, either reinstall the SCSI drive with jmsetup or /etc/halt the operating system and reboot with boot -r. You may need to reconfigure vold so it does not try to control the CD drives in your jukeboxes. See man vold and man vold.conf.

On IRIX, free SCSI IDs are 1-7, not 0-6 as on other computers, because the controller occupies ID 0.

AIX uses a multiplexed driver. You cannot see the devices, but you can use them. The driver generates the device paths automatically upon access.

2.4 Setting Up the Writer

If installation was successful, the writer is set up and ready for use. See Chapter 5, "The Writer", for information.

If you have a license key for the writer, insert the key in the file named writer.lic. For example,

version=2
writer
license=abcdefgh

Without a license key, the writer runs in demo mode, which means you can send only 128 MB to a recorder drive even if you use cdglow or the writable file system.

2.5 Setting Up the Server

Server setup requires that you decide how the file system should be represented and which devices should be used.

2.5.1 License Key (server.lic file)

The server.lic file contains the number of supported physical CDs and a license key. For example,

version=2
volumes=500
license=ijklmnop

If this file is missing or the key is invalid, the server runs in demo mode, which means it supports only a few disks (usually five) and runs for a maximum of two hours. When the time is up, you can restart the server.

For additional information, see "License Policy and Demo Versions' in Chapter 1.

2.5.2 Step 1: Setting Up File System Views

The server maintains a single file system containing all CDs as subdirectories, but different clients may require different views of this file system. For example, PCs prefer the 8.3 file name format with no mixed cases, while some UNIX clients want to see long file names stored with the optional Rock Ridge extensions. In other cases, some clients may need to see all CDs, while others need only a small subset.

iXOS-JUKEMAN contains two standard views that are adequate for most applications. If necessary, you can customize the views (see "Exported File System Views" in Chapter 3). The following instructions tell you how to run the default view configuration.

Running the Default Views with Windows NT

The NT version presents drive x: , containing all CDs in a format for PC clients. It simultaneously exports two additional file system views in PC (z: ) and RR format (y: ) to NFS clients. PCs access x: as a network drive and NFS clients can mount either

jukeman_hostname:/views_pc

or

jukeman_hostname:/views_rr

for the PC or RR view.

Example of a UNIX mount command:

# mount -o timeo=99,retrans=14,soft jm_hostname:/views_pc /cds In directory '/cds' are visible then the CDs controlled by Jukeman.

You can configure additional file system views using the Jukeman Administrator. (After you change the device or file system configuration, press F5 from the File Manager to refresh the screen.)

Running the Default Views under UNIX

If there is no NFS running, your file system installation is complete. But if NFS is running, you must set up the standard rpc.mountd to cooperate with the server.

rpc.mountd monitors the file systems. Clients that want to mount a Network File System ask rpc.mountd for a root file handle, which is the key for later requests to either the standard nfsd or the jukebox NFS server. Without this key, you cannot use the Network File System.

There cannot be a root file handle without a file system root. So you must create an empty directory for each standard view. These views are normally /view/rr for RR format and /views/pc for PC format, though other file names are possible as well (although other names do not comply with the iXOS standard server.cfg file). Create the directories by typing:

# mkdir /views_rr
# mkdir /views_pc

Next export a file system by telling rpc.mountd to give the file handles to clients. Most flavors of UNIX maintain a file named /etc/exports containing all exported file systems. If you add the line /views to this file, rpc.mountd exports all views of the iXOS-JUKEMAN file system.

Under Solaris, exported file systems are listed in the file /etc/dfs/dfstab. Add the lines

share -F nfs /views_pc
share -F nfs /views_rr

On some versions of UNIX (Solaris and others), the change does not take effect immediately. On Solaris, call the commands unshareall and shareall to update the export list. Other UNIX systems offer the exportfs command, so you can use exportfs -a to export all file systems. Another method is to reboot the server.

You can easily test if the directories are exported by using showmount -e. When you start the server, it tests whether the directories for all views are exported by requesting the file handle from rpc.mountd. It stops if it cannot get a file handle.

Once the directories are exported, start the server. In the installation directory call cdnfsd. The server runs and exports file systems. However, they are empty because you have not yet defined devices, and you cannot see them because they are Network File Systems and you must mount them before you can see anything. The CDs never appear in /views_rr or /views_pc; these directories only satisfy the rpc.mountd requirements. You must mount them as any NFS client does.

2.5.3 Step 2: Defining Devices

Each device that the server controls requires a file that describes the device type, the SCSI addresses of the drives, and the SCSI address or the RS232-address of the changer (also addressed as robot in the following examples). The file can also describe which jukebox storage slots the server should use (the default is all), and which file, if any, contains information about which CDs occupy which slots of the jukebox.

Once you create a device description file named device, the command

cdadm attach device

attaches the device to the server. The server inspects the slots and presents the CDs in all file system views. This inspection is normally only performed if you attach the device for the first time or change CDs manually without informing iXOS-JUKEMAN. Now clients should be able to see the CDs.

For additional information, see the description of save files in "Device Descriptions" later in this chapter. For details on cdadm, see "Controlling the Server" in Chapter 3.

Device descriptions are discussed generally here. Chapter 4, "Supported Jukeboxes," contains individual descriptions for each type of device.

Serial Lines

For several jukebox types, the changer is controlled through a serial line, which allows you to save a SCSI ID. For the NSM Mercury jukebox the serial interface allows the software to fully exploit the features of the jukebox and its ability to execute several movements in different states simultaneously. iXOS-JUKEMAN uses this parallel capability; even under high load the server can satisfy 14 client requests for different CDs in a single Mercury per minute. Moreover, you can connect 16 NSM changers to a single serial line (even mixed jukeboxes for 100 CDs and 150 CDs) and all can move simultaneously.

Each serial line is represented in the file system by a name that depends on the operating system. The first two serial lines are:

NT	com1:	com2:
SunOS	/dev/ttya	/dev/ttyb
Solaris	/dev/ttya	/dev/ttyb
HP-UX 10.*	/dev/tty00 or /dev/tty0p0	/dev/tty01 or /dev/tty0p0
AIX	/dev/tty0	/dev/tty1
DEC UNIX	/dev/tty00	/dev/tty01
IRIX	/dev/ttyd1	/dev/ttyd2

For IRIX, also see the output of "man serial." For AIX and SGI (IRIX), the special serial cables that are required are available from IBM.

Device Descriptions

A device description file contains lines in the format key=value. Some keys must be specified for all devices, others depend on the type of device. The most important parameter is the device type:

device=type

Supported types include: grundig200, cdr100, kubik, nakamichi, nec, mercury, pioneer6, pioneer18, pioneer500, sony_cdr, sony_cdl, single (for a single SCSI CD drive), tower6, tower7, image (for an ISO image on a hard disk), and standard, which you can use for all standard SCSI 2 jukeboxes. Contact our web site ("Writable File System" in Chapter 3).