C H A P T E R 4

Sun StorEdge SAM-FS Initial Installation Procedure

This chapter describes the procedure for installing and configuring the Sun StorEdge SAM-FS software for the first time. Use this procedure if this is the initial installation of the Sun StorEdge SAM-FS software package at your site.

If you are upgrading Sun StorEdge SAM-FS software on an existing server, see Sun StorEdge SAM-FS Upgrade Procedure.

The procedures in this chapter describe copying and installing the software packages onto your server and configuring the software to match the hardware at your site. You must have superuser (root) access to perform most of the tasks described in this chapter.

You can install and configure your Sun StorEdge SAM-FS file system entirely using Solaris commands, or you can use a combination of commands and SAM-QFS Manager, which is a graphical user interface (GUI) configuration tool, to complete the procedure.

For most of the procedures in this chapter, you must have `root` access.

##

Ensuring That the Installation Prerequisites Are Met

The chapter called System Requirements and Preinstallation Tasks describes the items you need to verify before you install and configure the Sun StorEdge SAM-FS software. If you have not yet completed the system verification steps, complete them now before you proceed. The steps described in that chapter for verifying the system requirements and performing preinstallation tasks are as follows:

- Server Requirements

- Solaris Operating System Requirements

- Planning Your File System and Verifying Disk Cache

- Verifying Disk Space

- (Optional) Verifying Archive Media

- Obtaining a Software License Key

- Obtaining the Release Files

- Verifying Third-Party Compatibilities

- (Optional) Verifying Requirements for the SAM-QFS Manager

- (Optional) Verifying the Network Management Station

##

Adding the Packages on the Sun StorEdge SAM-FS Server

The Sun StorEdge SAM-FS software uses the Sun Solaris packaging utilities for adding and deleting software. The `pkgadd`(1M) utility prompts you to confirm various actions necessary to install the packages.

### To Add the Packages

1. Become superuser.

2. Use the `cd`(1) command to change to the directory where the software package release files reside.

When you completed your preinstallation tasks, you obtained the release files as described in Obtaining the Release Files. Use the `cd`(1) command to change to the directory that contains the release files. Changing to the appropriate directory differs, depending on your release media, as follows:

- If you downloaded the release files, change to the directory to which you downloaded the files.

- If you obtained the release files from a CD-ROM, use one of the following commands:

- If you are installing the software on a Solaris 2.8 platform, use the following command:

    # cd /cdrom/cdrom0/2.8

- If you are installing the software on a Solaris 2.9 platform, use the following command:

    # cd /cdrom/cdrom0/2.9

3. Use the `pkgadd`(1M) command to add the `SUNWsamfsr` and `SUNWsamfsu` packages.

For example:

    # pkgadd -d . SUNWsamfsr SUNWsamfsu

4. Enter `yes` or `y` as the answer to each of the questions.

When you install `SUNWsamfsr` and `SUNWsamfsu`, you are asked if you want to define an administrator group. Select `y` to accept the default (no administrator group) or select `n` if you want to define an administrator group. You can reset permissions on certain commands later by using the `set_admin`(1M) command. For more information on this command, see the `set_admin`(1M) man page.

5. (Optional) Use the `pkgadd`(1M) command to add one or more localized packages.

Perform this step only if you want to install the packages localized for Chinese, French, or Japanese. CODE EXAMPLE 4-1 shows the commands to use to install the localized packages.

CODE EXAMPLE 4-1 Using the `pkgadd` (1M) Command to Install Localized Packages
    # pkgadd -d SUNWcsamf
    # pkgadd -d SUNWfsamf
    # pkgadd -d SUNWjsamf

The procedure for adding the SAM-QFS Manager software appears later in this chapter. The SAM-QFS Manager installation script prompts you to add localized versions of that software.

6. Examine `/tmp/SAM_install.log` .

File `/tmp/SAM_install.log` is the Sun StorEdge SAM-FS log file.

This file should show that the `pkgadd`(1M) command added the `SUNWsamfsr` and `SUNWsamfsu` software packages. Make sure that it also installed the Sun StorEdge SAM-FS `samst` driver. If all files installed properly, the following message appears:

    Restarting the sysevent daemon

##

(Optional) Verifying and Updating the `st.conf` and `samst.conf` Files

Perform this task if you plan to enable archiving to tape or magneto-optical media. You do not need to perform this procedure if you plan to archive to disk.

This task introduces you to the the process of verifying, and perhaps updating, the following two files:

- The `/kernel/drv/st.conf` file, which lists configuration information for tape drives attached to the server through a SCSI or Fibre Channel attachment.

- The `/kernel/drv/samst.conf` file, which lists configuration information for the following devices that the Sun StorEdge SAM-FS software recognizes by default:

- Direct-attached automated libraries.

- Magneto-optical drives attached to the server through a SCSI or Fibre Channel attachment.

The Sun StorEdge SAM-FS package includes the `/opt/SUNWsamfs/examples/st.conf_changes` file. This file includes configuration information for the following kinds of tape drives:

- Tape drives that are not supported in the Solaris kernel by default.

- Tape drives that are supported in the Solaris kernel but are supported with settings that do not accommodate Sun StorEdge SAM-FS software.

This task includes the following procedures:

- To Verify Device Types

- (Optional) To Add Tape Devices to the /kernel/drv/st.conf File

- To Verify or Add a Target Device, LUN, or Worldwide Name to the st.conf File

- (Optional) To Verify or Add Device Support in the samst.conf File

- To Verify That All Devices Are Configured

### To Verify Device Types

1. Obtain the list of devices that you created when you completed the step called To Create a List of Devices.

To Create a List of Devices is a procedure in which you enumerate the devices you want to include in your Sun StorEdge SAM-FS environment. If you have not already taken an inventory of your devices and listed them in TABLE 1-9, do so now. For the rest of the procedures in this installation, this manual refers to TABLE 1-9 as your inventory list.

The procedures in this task include an example that assumes your inventory list is as shown in TABLE 4-1.

TABLE 4-1 An Example Inventory List - Devices to be Configured
Device Name, Manufacturer, and Model | Target ID | LUN | World-Wide Node Name
--- | --- | --- | ---
SCSI-Attached Tape Drives |  |  |
QUANTUM DLT7000 | 1 | 0 | Not applicable
QUANTUM DLT7000 | 2 | 0 | Not applicable
Fibre Channel-Attached Tape Drives |  |  |
STK 9840 | Not Applicable | 0 | 500104f00043abfc
STK 9840 | Not Applicable | 0 | 500104f00045eeaf
IBM ULT3580-TD1 | Not Applicable | 0 | 500104f000416304
IBM ULT3580-TD1 | Not Applicable | 0 | 500104f000416303
SCSI-Attached Automated Libraries |  |  |
STK 9730 | 0 | 0 | Not applicable
Fibre Channel-Attached Automated Libraries |  |  |
STK L700 | Not applicable | 0 | 500104f00041182b

Note - The device names in TABLE 4-1 are represented as they appear in the discovery output.

2. Proceed on to the next step in this installation and configuration procedure.

Depending on the devices on your inventory list, you need to complete one or more of the following procedures:

- If there are any tape drives that you want to include in your Sun StorEdge SAM-FS environment, go to (Optional) To Add Tape Devices to the /kernel/drv/st.conf File.

- If there are any magneto-optical drives, SCSI-attached automated libraries, or Fibre Channel-attached automated libraries that you want to include in your Sun StorEdge SAM-FS environment, go to (Optional) To Verify or Add Device Support in the samst.conf File.

### (Optional) To Add Tape Devices to the `/kernel/drv/st.conf` File

Perform this pocedure if you have tape drives that you want to include in your Sun StorEdge SAM-FS environment.

In this procedure, you make entries for each unique tape drive type that you want to include in your Sun StorEdge SAM-FS environment. For each unique tape drive that is on your inventory list, there must be a corresponding entry in the `st.conf` file.

1. Use the `cp`(1) command to copy `/kernel/drv/st.conf` to a backup file.

For example:

    # cp /kernel/drv/st.conf /kernel/drv/st.conf.orig

2. Use `vi`(1) or another editor to open file `/kernel/drv/st.conf`.

3. Find the line that contains the `tape-config-list` string.

This line is as follows:

    #tape-config-list=

Remove the pound character (`#`) from column 1 of this line.

4. Use `vi`(1) or another editor to open file `/opt/SUNWsamfs/examples/st.conf_changes`.

5. Search file `/opt/SUNWsamfs/examples/st.conf_changes` to find the first device on your inventory list.

In the example inventory list, the first drive you need to find is the Quantum DLT 7000 tape drive. Find the line that contains the following entry:

    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",

This is the device definition for the Quantum DLT 7000 tape drive.

6. Copy the line containing the device definition you need from `st.conf_changes` to `st.conf` so it appears after the `tape-config-list` line.

CODE EXAMPLE 4-2 shows how the `st.conf` file looks at this point.

CODE EXAMPLE 4-2 `st.conf` With Its First Device Definition Entry
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    ...

7. Examine the line you just copied and note the final string enclosed in quotation marks.

In this example, the final string is `"dlt7-tape"`.

8. Search file `/opt/SUNWsamfs/examples/st.conf_changes` to find another line that begins with the final string you noted in Step 7.

The line you are looking for is called the tape configuration value.

In this example, it is as follows:

    dlt7-tape =    1,0x36,0,0xd679,4,0x82,0x83,0x84,0x85,3;

9. Copy the tape configuration line from Step 8 to file `st.conf`.

Put the device configuration line after the device definition line you copied in from Step 6.

For this example, CODE EXAMPLE 4-3 shows the lines now contained in the `st.conf` file.

CODE EXAMPLE 4-3 `st.conf` With a Device Entry and the Device Entry's Tape Configuration Value
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    dlt7-tape =    1,0x36,0,0xd679,4,0x82,0x83,0x84,0x85,3;
    ...

10. Decide whether you want to configure more devices in the `st.conf` file.

If this is the last or only device you want to configure, proceed to Step 17.

If you have more devices to configure, proceed to Step 11.

11. Search file `/opt/SUNWsamfs/examples/st.conf_changes` to find the next device on your inventory list.

In our example inventory list, the next drive you need to find is the StorageTek 9840 tape drive. Find a line that contains the following entry:

    "STK     9840", "STK 9840 Fast Access", "CLASS_9840",

This is the device definition for the StorageTek 9840 tape drive.

12. Copy the line containing the device definition you need from `st.conf_changes` to `st.conf` so it appears after preceding device definition line.

CODE EXAMPLE 4-4 shows how the `st.conf` file looks at this point.

CODE EXAMPLE 4-4 `st.conf` with Another Device Definition Entry
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    "STK     9840", "STK 9840 Fast Access", "CLASS_9840",
    ...

13. Examine the line you just copied and note the final string enclosed in quotation marks.

In this example, the final string is `"CLASS_9840"`.

14. Search file `/opt/SUNWsamfs/examples/st.conf_changes` to find another line that begins with the final string you noted in Step 13.

The line you are looking for is called the tape configuration value.

In this example, it is as follows:

    CLASS_9840 = 1,0x36,0,0x1d679,1,0x00,0;

15. Copy the tape configuration line from Step 14 to file `st.conf`.

Put the device configuration line after the device configuration line you copied in from Step 9.

For this example, CODE EXAMPLE 4-3 shows the tape drive configuration lines now contained in the `st.conf` file.

CODE EXAMPLE 4-5 `st.conf` With a Device Entry and the Device Entry's Tape Configuration Value
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    "STK     9840", "STK 9840 Fast Access", "CLASS_9840",
    dlt7-tape =    1,0x36,0,0xd679,4,0x82,0x83,0x84,0x85,3;
    CLASS_9840 = 1,0x36,0,0x1d679,1,0x00,0;
    ...

16. Decide whether you want to configure more devices in the `st.conf` file.

If you have more devices to configure, go back to Step 11.

If this is the last device you want to configure, proceed to Step 17.

For example, CODE EXAMPLE 4-7 shows the `st.conf` file after you have added definitions for the Quantum DLT 7000, the StorageTek 9840, and the IBM ULT3580 tape drives.

CODE EXAMPLE 4-6 `st.conf` Configured for Multiple Devices (Intermediate Format)
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    "STK     9840", "STK 9840 Fast Access", "CLASS_9840",
    "IBM     ULT3580-TD1",  "IBM 3580 Ultrium",     "CLASS_3580",
    dlt7-tape =    1,0x36,0,0xd679,4,0x82,0x83,0x84,0x85,3;
    CLASS_9840 = 1,0x36,0,0x1d679,1,0x00,0;
    CLASS_3580 = 1,0x24,0,0x418679,2,0x00,0x01,0;
    ...

17. Replace the comma (`,`) at the end of the last device definition line with a semicolon (`;`).

CODE EXAMPLE 4-7 shows the resulting `st.conf` file if you have multiple devices configured.

CODE EXAMPLE 4-7 `st.conf` Configured for Multiple Devices (Final Format)
    ...
    tape-config-list=
    "QUANTUM DLT7000", "DLT 7000 tape drive", "dlt7-tape",
    "STK     9840", "STK 9840 Fast Access", "CLASS_9840",
    "IBM     ULT3580-TD1",  "IBM 3580 Ultrium",     "CLASS_3580";
    dlt7-tape =    1,0x36,0,0xd679,4,0x82,0x83,0x84,0x85,3;
    CLASS_9840 = 1,0x36,0,0x1d679,1,0x00,0;
    CLASS_3580 = 1,0x24,0,0x418679,2,0x00,0x01,0;
    ...

Note - Some device configuration lines in `st.conf_changes` support more than one device definition, but you need only one device definition line in the `st.conf` file for such devices. For example, the Sony SDT-5000 and the Sony SDT-5200 both have `"DAT"` as the final string in their device definition lines. If your environment is to include both of these Sony devices, only one instance of the `DAT = 1,0x34,0,0x0439,1,0x00,0;` device definition needs to appear in the `st.conf` file.

18. Save your changes and proceed to To Verify or Add a Target Device, LUN, or Worldwide Name to the st.conf File.

You do not need to close out of the `st.conf` file at this point because you continue editing `st.conf` in the next procedure. It is a good idea to save your changes, however.

### To Verify or Add a Target Device, LUN, or Worldwide Name to the `st.conf` File

Perform this procedure if you have tape drives that you want to include in your Sun StorEdge SAM-FS environment. You typically perform this procedure after you have completed (Optional) To Add Tape Devices to the /kernel/drv/st.conf File.

For each tape drive on your hardware inventory list that is attached through a SCSI interface, you must confirm that an entry in the `st.conf` file defines that interface. This procedure shows how to verify and, if necessary, add target ID and LUN entries. Do not use this procedure to add interface information for magneto-optical drives.

1. (Optional) Use `vi`(1) or another editor to open file `/kernel/drv/st.conf`.

If you left the file open for editing from the previous procedure ((Optional) To Add Tape Devices to the /kernel/drv/st.conf File), you do not need to perform this step.

2. (Optional) Find the list of SCSI target IDs and LUNs in the `st.conf` file.

Perform this step only if you have tape drives you want to include that are attached through a SCSI interface.

In the `st.conf` file, look for entries that have the following format:

    name="st" class="scsi" target=target lun=lun;

target is the target ID for each SCSI drive found. lun is the corresponding LUN for each SCSI drive found.

3. In the list of SCSI targets and LUNs, find the entry that corresponds to a SCSI target and LUN that are on your inventory list.

For example, the two Quantum DLT 7000 drives are attached to LUN 0 and have target IDs 1 and 2. CODE EXAMPLE 4-8 shows the two lines that correspond to those interfaces.

CODE EXAMPLE 4-8 Example SCSI Target ID and LUN Information
    name="st" class="scsi" target=1 lun=0;
    name="st" class="scsi" target=2 lun=0;

Note that the preceding two lines might extend over two lines in `st.conf` if they contain return characters.

If you cannot find the SCSI target and LUN you need, proceed to Step 5.

4. Ensure that the lines identified in Step 3 are not preceded by pound (`#`) characters.

A pound (`#`) character marks a line as a comment. If the SCSI target and LUN lines you need have a pound character in column one, delete the pound character. Proceed to Step 6.

5. (Optional) Create a line for the SCSI target and LUN that you need.

Perform this step if the SCSI target and LUN line you need is not already listed in `st.conf`.

Use the format shown in Step 2 as a model for the line you add.

6. Decide whether you need to configure more SCSI targets and LUNs in `st.conf`.

If you have more SCSI targets and LUNs to configure, go back to Step 3.

If you do not have more SCSI targets and LUNs to configure, proceed to Step 7.

7. (Optional) Create lines for each device attached through a Fibre Channel interface.

Perform this step only if you have tape drives attached through a Fibre Channel interface in your inventory list and you are not using the Sun SAN Foundation Software I/O stack.

Fibre Channel interfaces are not included in the `st.conf` file by default. At the end of the SCSI target ID and LUN list, create a line for each Fibre Channel interface. Use the following format for the Fibre Channel interface definition lines:

    name="st" parent="fp" lun=lun fc-port-wwn="world-wide-name"

For lun, specify the LUN for the drive.

For world-wide-name, specify the World Wide Name for drive.

For example, CODE EXAMPLE 4-9 shows the lines to add to support the StorageTek 9840 and IBM ULT3580 tape drives included in the inventory list that are attached through Fibre Channel interfaces.

CODE EXAMPLE 4-9 Fibre Channel Interface Definition Lines for the `st.conf` File
    name="st" parent="fp" lun=0 fc-port-wwn="500104f00043abfc"
    name="st" parent="fp" lun=0 fc-port-wwn="500104f00045eeaf"
    name="st" parent="fp" lun=0 fc-port-wwn="500104f000416304"
    name="st" parent="fp" lun=0 fc-port-wwn="500104f000416303"

8. Save your changes and exit the `st.conf` file.

Proceed to (Optional) To Verify or Add Device Support in the samst.conf File if you have any of the following devices in your inventory list:

- Magneto-optical drives

- Automated libraries attached through a SCSI or a Fibre Channel interface.

### (Optional) To Verify or Add Device Support in the `samst.conf` File

Perform this step if you have magneto-optical drives or if you have automated libraries attached through a SCSI or a Fibre Channel interface. You do not need to perform this step if you have only network-attached automated libraries.

The `/kernel/drv/samst.conf` file contains a list of SCSI and Fibre Channel entries. This procedure shows you how to verify entries for your devices and to update the file if necessary. The `samst.conf` file works with the `/opt/SUNWsamfs/examples/inquiry.conf` file to define the devices that can be included in a Sun StorEdge SAM-FS environment. The `inquiry.conf` file lists all devices that are supported, so you do not need to verify or edit that file.

1. Use the `cp`(1) command to copy the `/kernel/drv/samst.conf` file to a backup file.

For example:

    # cp /kernel/drv/samst.conf /kernel/drv/samst.conf.orig

2. Use `vi`(1) or another editor to open the `/kernel/drv/samst.conf` file.

3. (Optional) Find the list of SCSI targets and LUNs in the `samst.conf` file.

Perform this step only if you have SCSI-attached magneto-optical drives or SCSI-attached libraries that you want to include.

In the `samst.conf` file, the entries you are looking for have the following format:

    name="samst" class="scsi" target=target lun=lun;

target is the target ID for each SCSI drive found. lun is the corresponding LUN for each SCSI drive found.

4. In the list of SCSI targets and LUNs, find the entry that corresponds to a SCSI target ID and LUN that are on your inventory list.

For example, the StorageTek 9730 automated library is attached to target 0 and LUN 0. The following line corresponds to that interface:

    name="samst" class="scsi" target=0 lun=0;

Note that the preceding line might extend over two lines in `st.conf` if it contains return characters.

If you cannot find the SCSI target and LUN you need, proceed to Step 6.

5. Ensure that the lines identified in Step 3 are not preceded by pound (`#`) characters.

A pound (`#`) character marks a line as a comment. If the SCSI target and LUN lines you need have a pound character in column one, delete the pound character. Proceed to Step 7.

6. (Optional) Create a line for the SCSI target and LUN that you need.

Perform this step if the SCSI target and LUN line you need is not already listed in `samst.conf`.

Use the format shown in Step 3 as a model for the line you add.

7. Decide whether you need to configure more SCSI targets and LUNs in `samst.conf`.

If you have more SCSI targets and LUNs to configure, go back to Step 4.

If you do not have more SCSI targets and LUNs to configure, proceed to Step 8.

8. (Optional) Create lines for the first device in your inventory list that is attached through a Fibre Channel interface.

Perform this step only if you have Fibre Channel-attached magneto-optical drives or Fibre Channel-attached automated libraries that you want to include.

Fibre Channel interfaces are not included in the `samst.conf` file by default. At the end of the SCSI target and LUN list, create a line for each Fibre Channel interface. Use the following format for the Fibre Channel interface definition lines:

    name="samst" parent="fp" lun=lun fc-port-wwn="world-wide-name"

For lun, specify the LUN for the drive.

For world-wide-name, specify the World Wide Name for drive.

The following example shows the line to add to support the StorageTek L700 tape drive on the example inventory list that is attached through a Fibre Channel interface:

    name="samst" parent="fp" lun=0 fc-port-wwn="500104f00041182b"

9. (Optional) Repeat Step 8 for each device that is attached through a Fibre Channel interface.

10. Save your changes and exit the `samst.conf` file.

### To Verify That All Devices Are Configured

Use the `cfgadm`(1M) command to verify the devices included in the Sun StorEdge SAM-FS environment.

For example:

CODE EXAMPLE 4-10 Output From `cfgadm` (1M)
    # cfgadm -al
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c0                             scsi-bus     connected    configured   unknown
    c0::dsk/c0t6d0                 CD-ROM       connected    configured   unknown
    c1                             fc-private   connected    configured   unknown
    c1::500000e0103c3a91           disk         connected    configured   unknown
    c2                             scsi-bus     connected    unconfigured unknown
    c3                             scsi-bus     connected    unconfigured unknown
    c4                             scsi-bus     connected    configured   unknown
    c4::dsk/c4t1d0                 disk         connected    configured   unknown
    c4::dsk/c4t2d0                 disk         connected    configured   unknown
    c5                             fc-fabric    connected    configured   unknown
    c5::100000e00222ba0b           disk         connected    unconfigured unknown
    c5::210000e08b0462e6           unknown      connected    unconfigured unknown
    c5::210100e08b2466e6           unknown      connected    unconfigured unknown
    c5::210100e08b27234f           unknown      connected    unconfigured unknown
    c5::500104f00043abfc           tape         connected    configured   unknown
    c5::500104f00043bc94           tape         connected    configured   unknown
    c5::500104f00045eeaf           tape         connected    configured   unknown
    c5::500104f000466943           tape         connected    configured   unknown
    c5::500104f00046b3d4           tape         connected    configured   unknown
    c5::500104f0004738eb           tape         connected    configured   unknown
    c6                             fc           connected    unconfigured unknown
    c7                             scsi-bus     connected    unconfigured unknown
    c8                             scsi-bus     connected    unconfigured unknown
    usb0/1                         usb-kbd      connected    configured   ok
    usb0/2                         usb-mouse    connected    configured   ok
    usb0/3                         unknown      empty        unconfigured ok
    usb0/4                         unknown      empty        unconfigured ok

Examine the output to make sure that it shows all the devices you want to configure in your Sun StorEdge SAM-FS environment. If a device is not shown as being configured, and it should be, you can use the `cfgadm`(1M) command to configure it. For more information, see the `cfgadm`(1M) man page.

Because of a bug in the `cfgadm`(1) command, you might receive a device busy error similar to that shown in CODE EXAMPLE 4-11.

CODE EXAMPLE 4-11 `cfgadm` (1M) Output Showing a Device Busy Error that can be Ignored
    # cfgadm -c configure -o force_update c4::500104f000489fe3
    cfgadm: Library error: failed to create device node: 500104f00043abfc: Device busy

Despite the error, the `cfgadm`(1M) command completely processes the request.

### Handling Errors in the `st.conf` File

Errors can occur if the `st.conf` file is not configured properly during Sun StorEdge SAM-FS software installation. The following example shows typical error messages and provides suggestions for problem resolution.

The following message is found in the `sam-log` file:

    May 18 12:38:18 baggins genu-30[374]: Tape device 31 is default type. Update `/kernel/drv/st.conf'.

CODE EXAMPLE 4-12 shows the device log messages that correspond to the `sam-log` message.

CODE EXAMPLE 4-12 Error Messages in the Device Log File
    1999/05/18 12:34:27*0000 Initialized. tp
    1999/05/18 12:34:28*1002 Device is QUANTUM , DLT7000
    1999/05/18 12:34:28*1003 Serial CX901S4929, rev 2150
    1999/05/18 12:34:28*1005 Known as Linear Tape(lt)
    1999/05/18 12:34:32 0000 Attached to process 374
    1999/05/18 12:38:18 1006 Slot 1
    1999/05/18 12:38:18 3117 Error: Device is type default. Update /kernel/drv/st.conf

The preceding messages indicate that the appropriate changes have not been made to `/kernel/drv/st.conf`.

##

Enabling the Sun StorEdge SAM-FS Software License

You need a license key to run the Sun StorEdge SAM-FS software. For information on obtaining license keys, see Obtaining a Software License Key.

The Sun StorEdge SAM-FS environments use encrypted license keys. The license keys consist of encoded alphanumeric strings. You receive one or more license keys depending on the system configuration and the products being licensed.

### To License the Sun StorEdge SAM-FS Software

1. Create the `/etc/opt/SUNWsamfs/LICENSE.4.2` file.

2. Starting in column one, place the license keys you have obtained from your ASP or from Sun Microsystems on the first line and on successive lines in the `/etc/opt/SUNWsamfs/LICENSE.4.2` file.

The key must start in column one. No other keywords, host IDs, comments, or other information can appear in the`/etc/opt/SUNWsamfs/LICENSE.4.2` file.

##

Setting Up `PATH` and `MANPATH` Variables

This task shows you how to modify your `PATH` and `MANPATH` environment variables so you can access the Sun StorEdge SAM-FS commands and man pages easily.

### To Set Up `PATH` and `MANPATH` Variables

1. For users who need to access the Sun StorEdge SAM-FS user commands (for example,`sls`(1)), add `/opt/SUNWsamfs/bin` to the users' `PATH` variables.

2. Use `vi`(1) or another editor to edit your system setup files to include the correct paths to commands and man pages.

a. In the Bourne or Korn shells, edit the `.profile` file, change the `PATH` and `MANPATH` variables, and export the variables.

CODE EXAMPLE 4-13 shows how your `.profile` file might look after editing.

CODE EXAMPLE 4-13 Finished `.profile` File
    PATH=$PATH:/opt/SUNWsamfs/bin:/opt/SUNWsamfs/sbin
    MANPATH=$MANPATH:/opt/SUNWsamfs/man
    export PATH MANPATH

b. In the C shell, edit the `.login` and `.cshrc` files.

When you are finished editing, the `path` statement in your `.cshrc` file might look like the following line:

    set path = ($path /opt/SUNWsamfs/bin /opt/SUNWsamfs/sbin)

CODE EXAMPLE 4-14 shows how the `MANPATH` in your .login file might look like after editing.

CODE EXAMPLE 4-14 Finished `MANPATH` in the `.login` File
    setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\
    share/man:/opt/SUNWsamfs/man

##

Rebooting the System

Note - Failure to reboot the system at this time can cause the `st` and `samst` modules to remain unconfigured.

### To Reboot the System

Reboot the server by issuing the `touch`(1) and `init`(1M) commands.

CODE EXAMPLE 4-15 shows the commands to use to reboot.

CODE EXAMPLE 4-15 Commands to Reboot the Server
    # touch /reconfigure
    # init 6

Changes to the `st.conf` and `samst.conf` files are enabled at this time.

##

(Optional) Enabling the SAM-QFS Manager

Perform this task if you want to be able to use the SAM-QFS Manager to configure, control, monitor, or reconfigure your Sun StorEdge SAM-FS environment.

The procedures in this section are as follows:

- To Install the SAM-QFS Manager Software.

- To Invoke the SAM-QFS Manager for the First Time. Use this procedure to invoke the SAM-QFS Manager software.

- To Use the SAM-QFS Manager for Configuration. Use this procedure to decide which configuration tasks you want to perform using the SAM-QFS Manager software.

In addition to the information in this section, this manual's appendix, SAM-QFS Manager Software Notes, describes other aspects of using the SAM-QFS Manager.

### To Install the SAM-QFS Manager Software

1. Ensure that you have met the installation requirements described in (Optional) Verifying Requirements for the SAM-QFS Manager.

2. Log in to the server that you want to use as the management station.

This can be the same server upon which you installed the `SUNWsamfsr` and `SUNWsamfsu` packages.

3. Become superuser.

4. Use the `cd`(1) command to change to the directory where the software package release files reside on your server.

When you completed your preinstallation tasks, you obtained the release files as described in Obtaining the Release Files. Use the `cd`(1) command to change to the directory that contains the release files.

For example, if you obtained the release files from a CD-ROM, use the following command:

    # cd /cdrom/cdrom0

If you downloaded the release files, change to the directory to which you downloaded the files.

5. Execute the `samqfsmgr_setup` script to install the SAM-QFS Manager software.

For example:

    # samqfsmgr_setup

6. Answer the questions as prompted by the `samqfsmgr_setup` script.

During the installation procedure, you are asked to answer questions about your environment. The script prompts you to enter passwords for the `SAMadmin` role and for the `samadmin` and `samuser` login IDs.

The `samqfsmgr_setup` script automatically installs the following:

- The TomCat, Java Runtime Environment (JRE), JATO, and Sun Web Console packages. If you have existing versions of these software packages that are not compatible with SAM-QFS Manager, the installation software asks you whether you want the appropriate levels to be installed at this time.

- The `SUNWsamqfsuiu` package.

- The `SUNWsamqfsuir` package.

The installation scripts prompt you to answer questions regarding whether you want to install any localized packages.

After installing the packages, it starts the TomCat Web Server, enables logging, and creates the `SAMadmin` role.

7. Use `vi`(1) or another editor to edit your system setup files to include the correct paths to commands and man pages.

a. In the Bourne or Korn shell, edit the `.profile` file, change the `PATH` and `MANPATH` variables, and export the variables.

CODE EXAMPLE 4-16 shows how your `.profile` file might look after editing.

CODE EXAMPLE 4-16 Finished `.profile` File
    PATH=$PATH:/opt/SUNWsamqfsui/bin
    MANPATH=$MANPATH:/opt/SUNWsamqfsui/man
    export PATH MANPATH

b. In the C shell, edit the `.login` and `.cshrc` files.

When you have finished editing, the `path` statement in your `.cshrc` file might look like the following line:

    set path = ($path /opt/SUNWsamqfsui/bin)

CODE EXAMPLE 4-17 shows how the `MANPATH` in your `.login` file might after you have finished editing.

CODE EXAMPLE 4-17 Finished `MANPATH` in the `.login` File
    setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\
    share/man:/opt/SUNWsamfs/man:/opt/SUNWsamqfsui/man

8. Log in to the Sun StorEdge SAM-FS server and become superuser.

9. Use the `ps`(1) and `grep`(1) commands to make sure that the `rpcbind` service is running.

For example:

    # ps -ef | grep rpcbind

10. Examine the output from the preceding commands.

The output should contain a line similar to the following:

    root   269     1  0   Feb 08 ?        0:06 /usr/sbin/rpcbind

If `rpcbind` does not appear in the output, enter the following command:

    # /usr/sbin/rpcbind

11. (Optional) Start the SAM-QFS Manager (`sam-mgmtrpcd`) daemon.

Perform this step if you did not choose to have this daemon started automatically at installation time.

Enter the following command to start the SAM-QFS Manager daemon:

    # /opt/SUNWsamfs/sbin/samadm config -a

With this configuration, the system automatically restarts this daemon every time the daemon process dies. The daemon autorestarts at system reboots.

If you want to stop the daemon completely, enter the following command:

    # /opt/SUNWsamfs/sbin/samadm config -n

The preceding command also prevents the daemon from restarting automatically.

If you want the SAM-QFS Manager daemon to run only once and not automatically restart, use the following command:

    # /opt/SUNWsamfs/sbin/samadm start

If you have used the preceding command to start the daemon, use the following command to stop it:

    # /opt/SUNWsamfs/sbin/samadm stop

For more information, see the `samadm`(1M) man page.

### Using the SAM-QFS Manager Software

After the SAM-QFS Manager is installed, you can log in to the software using two possible user names (`samadmin` and `samuser`) and two different roles (`SAMadmin` or`no role`). The tasks you can perform using the SAM-QFS Manager differ depending on the user name and the role you assume at login. These differences are as follows:

- If you log in as `samadmin`, you can choose from one of two roles.

- The role of `SAMadmin` grants you full adminstrator privileges to configure, monitor, control, and reconfigure the devices in your Sun StorEdge SAM-FS environment.

Only the Sun StorEdge SAM-FS adminstrator should log in using the `SAMadmin` role. All other users should log in as `samuser`.

- The role of`no role` only allows you to monitor the environment. You cannot change or reconfigure it in any way.

- If you log in as `samuser`, you can only monitor the environent. You cannot change or reconfigure it in any way.

With regard to system administration, be aware that the Solaris root user on the server that hosts the SAM-QFS Manager is not necessarily the administrator of the SAM-QFS Manager. Only `samadmin` has administrator priviledges for the SAM-QFS Manager application. The root user is the administrator of the management station.

To Invoke the SAM-QFS Manager for the First Time

Perform this procedure if you want to invoke the SAM-QFS Manager and use it, rather than commands, to perform some of the configuration steps.

1. Log in to the management station web server.

2. From a web browser, invoke the SAM-QFS Manager software.

The URL is as follows:

    https://hostname:6789

For hostname, type the name of the host. If you need to specify a domain name in addition to the host name, specify the hostname in this format: hostname`.`domainname.

Note that this URL begins with `https`, not `http`. The Sun Web Console login screen appears.

3. At the `User Name` prompt, enter `samadmin`.

4. At the `Password` prompt, enter the password you entered when you answered questions during the the `samqfsmgr_setup` script's processing in To Install the SAM-QFS Manager Software.

5. Click the `SAMadmin` role.

Only the Sun StorEdge SAM-FS administrator should ever log in with the `SAMadmin` role.

6. At the `Role Password` prompt, enter the password you entered in Step 4.

7. Click `Log In`.

8. Click `SAM-QFS Manager 1.1`.

You are now logged in to the SAM-QFS Manager.

- If you want to configure your environment at this time using the SAM-QFS Manager, stay at this screen and add the server that you want to administer. If you need help accomplishing this task, click on Help. After you add the servers, see To Use the SAM-QFS Manager for Configuration for more information on configuring your environment using the SAM-QFS Manager.

- If you want to quit using the SAM-QFS Manager at this time, click `Log Out`.

- If you want to create additional accounts at this time, see SAM-QFS Manager Software Notes.

To Use the SAM-QFS Manager for Configuration

This manual guides you through the configuration process using Solaris OS commands, but you can also use the SAM-QFS Manager, instead of commands, to accomplish many of the tasks.

1. Click `Help`, in the upper right corner of the screen, to access the SAM-QFS Manager online documentation.

2. (Optional) Configure your parameters file for network-attached libraries.

If you want to use SAM-QFS Manager to configure your Sun StorEdge SAM-FS environment and you want to include network-attached libraries in this configuration, create your parameters file before you create your `mcf` file. For information on creating a parameters file, see (Optional) Creating Parameters Files for Network-Attached Automated Libraries.

Note - This is not the order in which these tasks are performed if you want to use commands to create these files. If you want to use commands to configure your Sun StorEdge SAM-FS environment, you create your `mcf` file first, and then you create the parameters files for network-attached libraries.

3. Complete the configuration tasks.

Perform the configuration tasks in TABLE 4-2 in the order they appear. You can open a terminal window next to the SAM-QFS Manager window for use when you have to alternate between using commands and using the SAM-QFS Manager.

TABLE 4-2 shows the rest of the tasks you must perform to complete your Sun StorEdge SAM-FS configuration and the means by which you can accomplish each task.

TABLE 4-2 Sun StorEdge SAM-FS Installation Tasks
Task | Accomplish Through SAM-QFS Manager | Accomplish Through Commands
--- | --- | ---
(Optional) Creating Parameters Files for Network-Attached Automated Libraries | No | Yes
Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File | Yes | Yes
Initializing the Sun StorEdge SAM-FS Environment | Yes | Yes
(Optional) Checking the Drive Order | Yes | Yes
(Optional) Creating the archiver.cmd File | Yes | Yes
(Optional) Enabling Disk Archiving | Yes | Yes
(Optional) Editing the defaults.conf File | No | Yes
Verifying the License and mcf Files | No | Yes
(Optional) Labeling Removable Media Cartridges | No | Yes
(Optional) Populating the Catalog | Yes | Yes
(Optional) Creating the samfs.cmd File | Yes | Yes
Updating the /etc/vfstab File and Creating the Mount Point | Yes | Yes
Initializing the File System | Yes | Yes
Mounting the File System | Yes | Yes
(Optional) Sharing the File System With NFS Client Systems | No | Yes
Writing Periodic Dump Files By Using samfsdump(1M) | No | Yes
(Optional) Backing Up Configuration Files | No | Yes
(Optional) Configuring the Remote Notification Facility | No | Yes
(Optional) Adding the Administrator Group | No | Yes
Configuring System Logging | No | Yes
(Optional) Configuring Other Sun StorEdge Products | Not applicable | Not applicable

TABLE 4-2 describes several installation steps as optional. The only required installation steps that you still must perform using Solaris OS commands are as follows:

- Verifying the License and mcf Files. You need to use Solaris OS commands to verify that your license file is installed and working correctly and that your `archiver.cmd`(4) file is free from syntax errors. If you use SAM-QFS Manager to create your `mcf` file, however, you do not need to verify your `mcf` file.

- Writing Periodic Dump Files By Using samfsdump(1M). Performing this step is essential to preserving your data.

The other installation steps in TABLE 4-2 are necessary -- or are highly recommended-- depending on your environment. For example, if you have network-attached automated libraries, you must perform (Optional) Populating the Catalog. Read through the documentation for the tasks described in the preceding list and decide which steps you need to perform.

##

Defining the Sun StorEdge SAM-FS Configuration By Creating the `mcf` File

Each Sun StorEdge SAM-FS software environment is unique. The system requirements and hardware differ from site to site. The Sun StorEdge SAM-FS environments support a wide variety of tape and optical devices, automated libraries, and disk drives. It is up to you, the system administrator at your site, to set up the specific configuration for your environment.

The master configuration file, `/etc/opt/SUNWsamfs/mcf`, defines the equipment topology that the Sun StorEdge SAM-FS file system manages. This file specifies the devices, automated libraries, and file systems included in the environment. You assign each piece of equipment a unique Equipment Identifier in the `mcf` file.

There are examples of `mcf` files in `/opt/SUNWsamfs/examples`.

Note - For information on file system design considerations, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.

To configure a Sun StorEdge SAM-FS environment, create the `/etc/opt/SUNWsamfs/mcf` file. The `mcf` file has two kinds of entries:

- File system device entries. These are the disk devices to be used. In the `mcf` file, you organize them into one or more Sun StorEdge SAM-FS file systems.

- Removable media device entries. These are lines for each device, and you organize the devices into Family Sets. The `mcf` file contains information that enables you to identify the drives to be used and associate them with the automated libraries to which they are attached.

Note - The instructions for creating the `mcf` file differ depending on whether you are creating a Sun StorEdge SAM-FS environment or a Sun SAM-QFS environment. If you are installing the Sun StorEdge SAM-FS software, all configuration instructions are contained in this section. If you are creating a Sun SAM-QFS environment, the instructions for configuring the file system portion of the `mcf` file are contained in Defining the Sun StorEdge QFS Configuration By Creating the mcf File. The instructions for library and drive configuration are contained in this section.

### To Create an `mcf` File

When you create the `mcf` file, follow these guidelines:

- Delimit the fields in each line with spaces or tabs.

- Begin each comment line entered into this file with a pound sign (`#`).

- Use a dash (`-`) to indicate optional fields that are omitted.

CODE EXAMPLE 4-18 shows the `mcf` file fields.

CODE EXAMPLE 4-18 `mcf` File Fields
    #
    # Sun StorEdge SAM-FS file system configuration
    #
    # Equipment       Equip  Equip Fam   Dev    Additional
    # Identifier      Ord    Type  Set   State  Parameters
    # ----------      -----  ----- ----  -----  ----------

The `mcf` file can contain both comment lines and lines that pertain to a device. The types of lines that can pertain to a device are as follows:

- Family Set parent identifiers and family set devices

- Family Set member devices

- Standalone devices

TABLE 4-3 shows the information to be contained in each field and whether or not the field is a required or optional field.

TABLE 4-3 `mcf` File Fields
Field | Description
--- | ---
Equipment Identifier | Required. This field specifies the physical device with which to interact. This field can contain information on file system devices or removable media devices. File System Devices For the initial line in a group of file system definition lines, specify the file system name. This must be the same name as the Family Set name specified in the Family Set field, and it is limited to 31 characters. If the device is a file system member device, specify a`/dev/dsk` entry. This field is limited to 127 characters. Removable Media Devices The Equipment Identifier field is limited to 127 characters for lines that define removable media devices. If the device is a direct-attached automated library or optical drive, specify a`/dev/samst` entry. If the device is a network-attached automated library, specify the full path name to the parameters file for that library. Each automated library in the Sun StorEdge SAM-FS environment must have its own identification line in the `mcf` file. To specify more than one library in the `mcf` file, put each on a separate line. If the device is a tape drive, specify one of the following: The `/dev/rmt/`n `cbn` entry. The path to a different symbolic link that points to the same special file that the `/dev/rmt/`n `cbn` link points to. If you specify the tape drive in this manner, create the link before mounting the file system.
Equipment Ordinal | Required. Specify a unique integer number. All devices and parent identifiers must be assigned a unique Equipment Ordinal. Enter a unique integer such that 1 eq_ord 65534. The number selected affects the order in which devices are displayed in the user interfaces. Lower numbers are displayed first.
Equipment Type | Required. This field provides information that the software uses to determine how to interact with a particular device. Enter the two- or three-character mnemonic for the device type. Most equipment can use the generic equipment types of `od` (optical disk), `tp` (tape), and `rb` (robot). For specific Equipment Types, see the `mcf`(4) man page.
Family Set | Required for most devices. A Family Set parent line identifies groups of devices configured to work together as a group, for example, a library and its drives. For a parent device (for example, a library), enter a descriptive name for the Family Set. The Family Set name binds its members, as follows: If the device is a file system disk device, enter the file system name. If the device is a member device that is associated with a Family Set parent device (that is, a file system or automated library), enter the Family Set name for the parent device. If the device is a standalone device such as a manually loaded drive, use the dash (`-`) to indicate that this field is omitted. This field is limited to 31 characters.
Device State | Optional. Enter a state for the device for when the file system is initialized. This state could be`on`,`off`,`unavail`, `down`, or a dash (`-`) for default behavior.
Additional Parameters | Optional. If you include information in the Additional Parameters field, what you can specify varies by device type, as follows: If the device is a disk, specify the `/dev/rdsk` entry. This is similar to the `/dev/dsk` entry in the Equipment Identifier field. If the device is an automated library, specify an alternate path to the library's media catalog file or specify the default path to the library catalog file (`/var/opt/SUNWsamfs/catalog/`family_set_name). For tape and magneto-optical devices, this field should be left blank.

Note - If you change the `mcf` file after the Sun StorEdge SAM-FS file system is in use, you must convey the new `mcf` specifications to the Sun StorEdge SAM-FS software. For information on propagating `mcf` file changes to the system, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.

### Identifying Peripherals Using the `/var/adm/messages` File

When your system boots, a series of messages are written to `/var/adm/messages`. These messages identify the Sun Solaris hardware path to each of the peripherals on your system. To display information from the latest system reboot, search backward from the end of the file.

As CODE EXAMPLE 4-19 shows, each SCSI peripheral has three lines. Note that the third line wraps to the next line in CODE EXAMPLE 4-19 and that the sixth field, `samst2`, indicates that these lines are associated with each other.

CODE EXAMPLE 4-19 SCSI Peripheral Lines in the `/var/adm/messages` File
    # tail -200 /var/adm/messages | more
    Aug 23 11:52:54 baggins unix: samst2: Vendor/Product ID = HP      C1716T
    Aug 23 11:52:54 baggins unix: samst2 at esp0: target 2 lun 0
    Aug 23 11:52:54 baggins unix: samst2 is /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/samst@2,0

Note - For readability, the preceding output, and many other outputs that are wider than 80 characters, have been wrapped for inclusion in this manual.

The first line displays the vendor and product information that the SCSI peripheral reported to the Sun Solaris kernel.

The second line displays the SCSI bus, SCSI target ID, and LUN of the peripheral.

The third line displays the peripheral's hardware path. This path is reflected in the`/devices` directory. Symbolic links (symlinks) to the `/devices` directory are set up in the `/dev/st`, `/dev/samst`, and `/dev/rmt` directories.

Matching the symbolic link to the correct peripheral is the key to configuring a Sun StorEdge SAM-FS environment. Use the `ls`(1) command with the `-l` option in both the `/dev/st`, `/dev/samst` and `/dev/rmt` directories to display the path name of the peripheral.

Optionally, you can set up the device down notification script at this point. The`dev_down.sh`(1M) man page contains information about setting up this script, which sends email to root when a device is marked `down` or `off`. For more information, see the `dev_down.sh`(1M) man page.

### Example Sun StorEdge SAM-FS Configuration

Assume that the following equipment is to be included in a Sun StorEdge SAM-FS configuration:

- Two Seagate ST15230W 4-gigabyte disk drives used as cache for the file system

- One StorageTek 9730 30-slot automated library that contains two DLT tape drives

- One manually loaded DLT 2000 drive

- One HP Model C1710T magneto-optical automated library containing two HP Model C1716 magneto-optical drives

- One manually loaded HP Model C1716 magneto-optical drive

This equipment is connected to three SCSI buses with the following SCSI targets:

- The server's internal, single-ended, SCSI bus with the target IDs shown in TABLE 4-4.

TABLE 4-4 Target IDs for the Server's Internal Single-Ended SCSI Bus
Target ID | Equipment
--- | ---
2 | Manually loaded magneto-optical drive
3 | The Sun Solaris internal hard disk
4 | Manually loaded DLT drive

- A differential SCSI bus connected to the HP Model C1710T automated library and file system disks with target IDs shown in TABLE 4-5.

TABLE 4-5 Target IDs for the SCSI Bus Connected to the HP Model C1710T Automated Library
Target ID | Equipment
--- | ---
0 and 1 | Seagate 4-gigabyte disks
2 | HP C1710T automated library
5 | First optical drive
6 | Second optical drive

- A differential SCSI bus connected to the StorageTek 9730 automated library and tape drives with target IDs shown in TABLE 4-6.

TABLE 4-6 Target IDs for the SCSI Bus Connected to the StorageTek 9730 Automated Library
Target ID | Equipment
--- | ---
0 | StorageTek 9730 automated library
1 | First DLT 7000 drive
2 | Second DLT 7000 drive

### Example Sun StorEdge SAM-FS Disk Cache Configuration

CODE EXAMPLE 4-20 shows the output from the Sun Solaris `format`(1M) command. It reports how the disks are partitioned.

CODE EXAMPLE 4-20 `format` (1M) Command Example
    1. c1t0d0 <SEAGATE-ST15230W-0168 cyl 3974 alt 2 hd 19 sec 111>
    /iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/sd@0,0
    Current partition table (original) :
    Total disk cylinders available: 3974 + 2 (reserved cylinders)
    Part    Tag          Flag     Cylinders    Size        Blocks
    0       root         wm       0-3499       3.52GB      (3500/0/0)
    1       unassigned   wm       3500-3972    487.09MB    (473/0/0)
    2       backup       wu       0-3973       4.00GB      (3974/0/0)
    3       unassigned   wm       0            0           (0/0/0)
    4       unassigned   wm       0            0           (0/0/0)
    5       unassigned   wm       0            0           (0/0/0)
    6       unassigned   wm       0            0           (0/0/0)
    7       unassigned   wm       0            0           (0/0/0)
    2. c1t1d0 <SEAGATE-ST15230W-0168 cyl 3974 alt 2 hd 19 sec 111>
     /iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/sd@1,0
    Current partition table (original):
    Total disk cylinders available: 3974 + 2 (reserved cylinders)
    Part    Tag          Flag     Cylinders    Size        Blocks
    0       root         wm       1000-3973    2.99GB      (2974/0/0)
    1       unassigned   wu       0            0           (0/0/0)
    2       backup       wu       0-3973       4.00GB      (3974/0/0)
    3       unassigned   wm       0            0           (0/0/0)
    4       unassigned   wm       0            0           (0/0/0)
    5       unassigned   wm       0-999        1.01GB      (1000/0/0)
    6       unassigned   wm       0            0           (0/0/0)
    7       unassigned   wm       0            0           (0/0/0)

This example creates one Sun StorEdge SAM-FS file system (samfs1) on partition 0 of disk c1t0d0 and partition 5 of c1t1d0. It creates another file system (samfs2) on partition 1 of disk c1t0d0 and partition 0 of disk c1t1d0.

The following procedure explains how to begin writing the mcf file for this example configuration by defining the file systems and their disk partitions.

To Write the `mcf` File

1. Make an `ms` (mass storage) entry for the first file system.

An `ms` entry is the Equipment Identifier for a Sun StorEdge SAM-FS file system. The name of this file system (`samfs1`) is used later when writing the `/etc/vfstab` entry for the file system and creating the file system. Note that the name as specified in the Equipment Identifier field must be the same as the Family Set name for the file system.

2. Make a series of `md` (magnetic disk) entries listing the partitions that comprise the `samfs1` file system member devices.

3. Make similar entries for the second (`samfs2`) file system.

CODE EXAMPLE 4-21 shows the `mcf` with the file systems defined.

CODE EXAMPLE 4-21 Sun StorEdge SAM-FS `mcf` File Showing the File Systems
    # Disk cache configuration for 2 file systems: samfs1, samfs2
    #
    # Equipment       Eq    Eq   Fam.  Dev.    Additional
    # Identifier      Ord  Type  Set   State   Parameters
    #-----------      ---   --  ------ ------  ------------------
    samfs1             10   ms  samfs1
    /dev/dsk/c1t0d0s0  11   md  samfs1   on
    /dev/dsk/c1t1d0s5  12   md  samfs1   on
    #
    samfs2             20   ms  samfs2
    /dev/dsk/c1t1d0s0  21   md  samfs2   on
    /dev/dsk/c1t0d0s1  22   md  samfs2   on

| Caution - Make sure you specify disk partitions that are not in use on your system. Do not use overlapping partitions. If a Sun StorEdge SAM-FS file system attempts to use a partition that is already in use, the software usually issues a message to indicate that the device is busy. If you give the wrong partition names, you risk damaging user or system data. This is true when initializing any type of file system. Make sure you specify only disk partitions that are not already in use on your system. Do not use overlapping partitions.

### Configuring a Manually Loaded Magneto-Optical Drive

The HP Model C1716T is target ID 2 on the internal SCSI bus.

To Configure the Drive

1. Examine the `/var/adm/messages` file to find the messages for these devices.

CODE EXAMPLE 4-22 shows the information in `/var/adm/messages` associated with the HP Model C1716T and target 2. Note that the third line wraps to the next line in this example.

CODE EXAMPLE 4-22 Information in `/var/adm/messages`
    Aug 23 11:52:54 baggins unix: samst2: Vendor/Product ID = HP    C1716T
    Aug 23 11:52:54 baggins unix: samst2 at esp0: target 2 lun 0
    Aug 23 11:52:54 baggins unix: samst2 is /iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/samst@2,0

2. Issue the `cd`(1) command to change to the `/dev/samst` directory.

3. Use the `ls`(1) and `grep`(1) commands to find the correct symbolic link.

For example, use the following `ls`(1) command:

    # ls -l | grep "samst@2"

The preceding `ls`(1) command searches for a symbolic link that points to the hardware path shown in CODE EXAMPLE 4-23.

CODE EXAMPLE 4-23 Path to `samst@2`
    lrwxrwxrwx   1 root     other         88 Aug 23 12:27 c0t2u0 -> /devices/iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/samst@2,0:a,raw

The Sun samst driver uses the name `/dev/samst/c0t2u0` when referencing the device.

4. Use an editor to open the `/etc/opt/SUNWsamfs/mcf` file.

5. Add an entry for the drive to the `mcf` file.

Add the following entry in `/etc/opt/SUNWsamfs/mcf`:

    /dev/samst/c0t2u0  30  od  -  on

This entry contains the device name (`/dev/samst/c0t2u0`), a unique Equipment Ordinal (30), the Equipment Type of the drive (`od`), a dash (`-`) to indicate that a Family Set name is not associated with the drive, and the device state (`on`).

### Configuring a Magneto-Optical Library

The HP C1710T automated library has three SCSI devices: the robotic mechanism and the two magneto-optical drives that the automated library loads and unloads.

To Configure the Magneto-Optical Library

1. Examine the `/var/adm/messages` file to find the messages for these devices.

CODE EXAMPLE 4-24 shows these messages.

CODE EXAMPLE 4-24 `/var/adm/messages` for the HP Library and two Drives
    Aug 23 11:52:56 baggins unix: samst16: Vendor/Product ID = HP      C1710T
    Aug 23 11:52:56 baggins unix: samst16 at QLGC,isp0: target 2 lun 0
    Aug 23 11:52:56 baggins unix: samst16 is /iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@2,0
    Aug 23 11:52:56 baggins unix: samst19: Vendor/Product ID = HP      C1716T
    Aug 23 11:52:56 baggins unix: samst19 at QLGC,isp0: target 5 lun 0
    Aug 23 11:52:56 baggins unix: samst19 is /iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@5,0
    Aug 23 11:52:56 baggins unix: samst20: Vendor/Product ID = HP      C1716T
    Aug 23 11:52:56 baggins unix: samst20 at QLGC,isp0: target 6 lun 0
    Aug 23 11:52:56 baggins unix: samst20 is /iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@6,0

2. Issue the `cd`(1) command to change to the `/dev/samst` directory.

3. Use `ls`(1) and `grep`(1) commands to find the symbolic links for the devices.

CODE EXAMPLE 4-25 shows the `ls`(1) commands to use to search for the three symbolic links that point to the `/devices` files with the same Sun Solaris hardware paths shown in CODE EXAMPLE 4-24.

CODE EXAMPLE 4-25 `ls` (1) and `grep` (1) Commands Used to Find Symbolic Links for the Devices in CODE EXAMPLE 4-24
    # ls -l | grep "samst@2"
    lrwxrwxrwx   1 root     other         74 Aug 23 12:27 c1t2u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@2,0:a,raw
    # ls -l | grep "samst@5"
    lrwxrwxrwx   1 root     other         74 Aug 23 12:27 c1t5u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@5,0:a,raw
    # ls -l | grep "samst@6"
    lrwxrwxrwx   1 root     other         74 Aug 23 12:27 c1t6u0 -> /devices/iommu@0,10000000/sbus@0,10001000/QLGC,isp@1,10000/samst@6,0:a,raw

4. Use an editor to open the `/etc/opt/SUNWsamfs/mcf` file.

5. Add entries for the library and drives to the `/etc/opt/SUNWsamfs/mcf` file.

CODE EXAMPLE 4-26 shows the `mcf` file entries.

CODE EXAMPLE 4-26 `mcf` File Entries for the HP Library and its Drives
    /dev/samst/c1t2u0  50  rb  hp30  on
    /dev/samst/c1t5u0  51  od  hp30  on
    /dev/samst/c1t6u0  52  od  hp30  on

The first line defines the automated library itself. It contains the `/dev/samst` name for the device `(/dev/samst/c1t2u0)` followed by a unique Equipment Ordinal (`50`), the Equipment Identifier (`rb`, for a generic SCSI-attached library), the Family Set identifier specified on all devices associated with this library (`hp30`), and the Device State (`on`).

The two remaining lines define the drives inside the library. They are similar to the manually loaded drives defined in the previous section except that instead of a dash, they include the Family Set name of the library where they reside (`hp30`).

Note - The order of drives as specified in the `mcf` file must match the logical order of the drives in a SCSI-attached automated library. The first drive defined in the `mcf` must be the first logical drive in the library, and so on. For more information, see your hardware documentation for the logical orientation of drives. Incorrect configuration can cause cartridges to be mounted in the wrong drives, which will lead to total inoperability of this software.

### Configuring a Manually Loaded DLT Drive

When configuring DLT drives, be sure to add the DLT definitions to the`/kernel/drv/st.conf` file (see (Optional) Verifying and Updating the st.conf and samst.conf Files). DLT drives are not part of the standard Sun Solaris configuration, and the software does not recognize them if they are configured incorrectly.

To Configure the DLT Drive

1. Examine the `/var/adm/messages` file to find the messages for these devices.

CODE EXAMPLE 4-27 shows the `/var/adm/messages` file lines that refer to the manual DLT drive.

CODE EXAMPLE 4-27 Information in `/var/adm/messages`
    Feb 25 13:23:29 collie scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5,1/st@0,0 (st21):
    Feb 25 13:23:29 collie       <Vendor 'DEC     ' Product 'DLT2000        '>
    Feb 25 13:23:29 collie scsi: [ID 193665 kern.info] st21 at glm3: target 0 lun 0
    Feb 25 13:23:29 collie genunix: [ID 936769 kern.info] st21 is /pci@1f,4000/scsi@5,1/st@0,0

2. Use the `ls`(1) and `grep`(1) commands to search for the symbolic links that point to the `/devices` files with the same Sun Solaris hardware paths shown in the `/var/adm/messages` file.

CODE EXAMPLE 4-28 shows the `ls`(1) and `grep`(1) commands to use to locate the DLT drive identified as `scsi@5`.

CODE EXAMPLE 4-28 `ls` (1) and `grep` (1) Commands Used to Find Symbolic Links for the Device in CODE EXAMPLE 4-27
    # ls -l /dev/rmt|grep 'pci@1f,4000/scsi@5,1/st@0'|grep cbn
    lrwxrwxrwx   1 root     other         45 Feb 14 09:48 0cbn -> ../../devices/pci@1f,4000/scsi@5,1/st@0,0:cbn

When making the `mcf` entry, always use the `b` and `n` options. CODE EXAMPLE 4-29 shows the symbolic link for a drive that supports compression. If the drive supports compression, and if you want compression in the hardware, use `cbn` as the prefix.

CODE EXAMPLE 4-29 Symbolic Link Showing a Drive With that Supports Compression
    lrwxrwxrwx   1 root     other         85 Aug 15 11:37 /dev/rmt/0cbn -> ../../devices/iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000 st@4,0:cbn

3. Use `vi`(1) or another editor to open the `/etc/opt/SUNWsamfs/mcf` file.

4. Add the `/etc/opt/SUNWsamfs/mcf` entry.

For example:

    /dev/rmt/0cbn  40  tp  -  on

The first entry on the line is the `st` driver name for the device (`/dev/rmt/0cbn`), followed by a unique Equipment Ordinal (`40`), the Equipment Type (`tp` for a generic tape), a dash (`-`) to indicate that a Family Set name is not associated with the manually mounted device, and the Device State (`on`).

For tape drives, you can leave the Additional Parameters field empty.

### Configuring a DLT Library

The last piece of equipment to define is the STK 9730 automated library. This automated library has three SCSI devices: the robotic mechanism and the two DLT 7000 tape drives that the robot loads and unloads.

To Configure the DLT Library

1. Examine the `/var/adm/messages` to find the messages for these devices.

CODE EXAMPLE 4-30 shows the `/var/adm/messages` file.

CODE EXAMPLE 4-30 Information in `/var/adm/messages`
    Feb  4 09:42:17 server1 samst: [ID 902828 kern.notice] samst42:     Vendor/Product ID = STK     9730
    Feb  4 09:42:17 server1 scsi: [ID 193665 kern.info] samst42 at glm3: target 0 lun 0
    Feb  4 09:42:17 server1 genunix: [ID 936769 kern.info] samst42 is /pci@6,4000/scsi@2,1/samst@0,0
    Feb  4 13:20:21 server1 scsi: [ID 365881 kern.info] /pci@6,4000/scsi@2,1/st@1,0 (st22):
    Feb  4 13:20:21 server1     <DLT 7000 tape drive>
    Feb  4 13:20:21 server1 scsi: [ID 193665 kern.info] st22 at glm3: target 1 lun 0
    Feb  4 13:20:21 server1 genunix: [ID 936769 kern.info] st22 is /pci@6,4000/scsi@2,1/st@1,0
    Feb  4 13:20:21 server1 scsi: [ID 365881 kern.info] /pci@6,4000/scsi@2,1/st@2,0 (st23):
    Feb  4 13:20:21 server1     <DLT 7000 tape drive>
    Feb  4 13:20:21 server1 scsi: [ID 193665 kern.info] st23 at glm3: target 2 lun 0
    Feb  4 13:20:21 server1 genunix: [ID 936769 kern.info] st23 is /pci@6,4000/scsi@2,1/st@2,0

2. Issue the `cd`(1) command to change to the `/dev/samst` directory.

3. Use the `ls`(1) and `grep`(1) commands to find the symbolic links that point to the `/devices` files with the same Sun Solaris hardware paths shown in the `/var/adm/messages` file.

CODE EXAMPLE 4-31 shows the `ls`(1) and `grep`(1) commands to use to locate the symbolic links.

CODE EXAMPLE 4-31 `ls` (1) and `grep` (1) Commands Used to Find Symbolic Links for the Device in CODE EXAMPLE 4-30
    # cd /dev/samst
    # ls -l | grep "samst@0"
    lrwxrwxrwx   1 root     other         49 Feb  4 09:42 c6t0u0 -> ../../devices/pci@6,4000/scsi@2,1/samst@0,0:a,raw

4. Use the `ls`(1) and `grep`(1) commands to find a symbolic link in `/dev/rmt` that points to the tape devices.

Note in CODE EXAMPLE 4-32 that the automated library does not have this additional link.

CODE EXAMPLE 4-32 `ls` (1) and `grep` (1) Commands to Use to Find the Tape Devices
    # cd /dev/rmt
    # ls -l | grep cbn
    lrwxrwxrwx   1 root     root          44 Feb  3 15:38 0cbn -> ../../devices/pci@6,4000/scsi@2,1/st@1,0:cbn
    lrwxrwxrwx   1 root     root          44 Feb  3 15:38 1cbn -> ../../devices/pci@6,4000/scsi@2,1/st@2,0:cbn

Again, there are multiple symbolic links in the directory that point to the same hardware path. To enable hardware compression, choose the one with the `cbn` suffix. If your drive does not support hardware compression, choose the symbolic link that ends with `bn`.

5. Use `vi`(1) or another editor to open the `/etc/opt/SUNWsamfs/mcf` file.

6. Add the `/etc/opt/SUNWsamfs/mcf` entries.

CODE EXAMPLE 4-33 shows the `mcf` file entries for this library and its drives.

CODE EXAMPLE 4-33 `mcf` File Entries for the StorageTek Library and its Drives
    /dev/samst/c2t0u0  60  rb  9730  on
    /dev/rmt/0cbn      61  tp  9730  on
    /dev/rmt/1cbn      62  tp  9730  on

The first line defines the automated library and includes the `/dev/samst` name (`/dev/samst/c2t0u0`). It also contains a unique Equipment Ordinal (`60`), the Equipment Type (`rb`, for the generic robot Equipment Type), a Family Set name for the robot and the drive (`9730`), and the Device State (`on`).

The second line defines the first DLT tape drive inside the library. These entries refer to the Equipment Identifier for this tape device (`/dev/rmt/0cbn`), the Equipment Ordinal for the device (`61`), the Equipment Type (`tp`), the Family Set Name (`9730`), and the Device State (`on`).

The third line defines the second DLT tape drive inside the automated library. These entries refer to the Equipment Identifier for this tape device (`/dev/rmt/1cbn`), the Equipment Ordinal for the device (`62`), the Equipment Type (`tp`), the Family Set name (`9730`), and the Device State (`on`).

7. (Optional) Add the DLT definitions to the`/kernel/drv/st.conf` file.

Perform this step if you are configuring DLT drives.

(Optional) Verifying and Updating the st.conf and samst.conf Files shows how to add definitions to the `/kernel/drv/st.conf` file. DLT drives are not part of the standard Sun Solaris configuration.

TABLE 4-7 shows the completed `mcf` file.

TABLE 4-7 Completed `mcf` File
    # Equipment         Eq   Eq    Family  Dev   Additional
    # Identifier        Ord  Type  Set     Sta   Parameters
    #
    samfs1              10   ms    samfs1
    /dev/dsk/c1t0d0s0   11   md    samfs1  on
    /dev/dsk/c1t1d0s5   12   md    samfs1  on
    #
    samfs2              20   ms    samfs2
    /dev/dsk/c1t1d0s0   21   md    samfs2  on
    /dev/dsk/c1t0d0s1   22   md    samfs2  on
    #
    /dev/samst/c0t2u0   30   od    -       on
    #
    /dev/rmt/0cbn       40   tp    -       on
    #
    /dev/samst/c1t2u0   50   rb    hp30    on
    /dev/samst/c1t5u0   51   od    hp30    on
    /dev/samst/c1t6u0   52   od    hp30    on
    #
    /dev/samst/c2t0u0   60   rb    9730    on
    /dev/rmt/0cbn       61   tp    9730    on
    /dev/rmt/1cbn       62   tp    9730    on

### Example `mcf` File Entries for Network-Attached Libraries

The following examples show `mcf` file entries for network-attached devices. In these examples, note that the first line of each library definition is the full path to a file. This file is the parameters file for that library.

If you are using a network-attached library, you create the parameters files for network attached libraries in (Optional) Creating Parameters Files for Network-Attached Automated Libraries.

Example 1. CODE EXAMPLE 4-34 shows the `mcf` file for an ADIC/Grau network-attached automated library.

CODE EXAMPLE 4-34 ADIC/Grau Automated Library `mcf` File Entries
    #
    # Sample mcf file entries for a GRAU library - DLT
    #
    /etc/opt/SUNWsamfs/grau50  50   gr   gr50  -
    /dev/rmt/0cbn              51   lt   gr50  -
    /dev/rmt/1cbn              52   lt   gr50  -
    #
    # Sample mcf file entries for a GRAU library - HP optical
    #
    /etc/opt/SUNWsamfs/grau60   60   gr  gr60  -
    /dev/samst/c1t1u0           61   od  gr60  -

Example 2. CODE EXAMPLE 4-35 shows the `mcf` file for a Fujitsu LMF network-attached automated library.

CODE EXAMPLE 4-35 Fujitsu LMF Automated Library `mcf` File Entries
    #
    # Sample mcf file entries for an LMF library
    #
    /etc/opt/SUNWsamfs/lmf50 50  fj  fj50  -
    /dev/rmt/0cbn            51  fd  fj50  -
    /dev/rmt/1cbn            52  fd  fj50  -

Example 3. CODE EXAMPLE 4-36 shows the `mcf` file for an IBM 3494 network-attached automated library.

CODE EXAMPLE 4-36 IBM 3494 Automated Library `mcf` File Entries
    # The mcf file entries.
    #
    # IBM 3494 library
    #
    /etc/opt/SUNWsamfs/ibm50 50      im      ibm3494e - ibmcat
    /dev/rmt/1bn             51      tp      ibm3494e
    /dev/rmt/2bn             52      tp      ibm3494e

Example 4. CODE EXAMPLE 4-37 shows the `mcf` file for a Sony network-attached automated library.

CODE EXAMPLE 4-37 Sony Network-Attached Automated Library mcf File Entries
    #
    # Sample mcf file entries for a Sony network-attached library
    #
    /etc/opt/SUNWsamfs/sonyfile 100   pe   psc  on
    /dev/rmt/1cbn               101   so   psc  on
    /dev/rmt/2cbn               102   so   psc  on

Example 5. CODE EXAMPLE 4-38 shows the `mcf` file for a StorageTek ACSLS-attached automated library.

CODE EXAMPLE 4-38 StorageTek Automated Library `mcf` File Entries
    # Equipment              Eq   Eq  Family  Dev  Additional
    # Identifier             Ord  Ty  Set     St   Parameters
    #
    /etc/opt/SUNWsamfs/stk50 50   sk  sk50    on
    /dev/rmt/0cbn            51   sg  sk50    on
    /dev/rmt/1cbn            52   sg  sk50    on

For more information, see the `mcf`(4) man page. There are example `mcf` files located in `/opt/SUNWsamfs/examples/mcf`.

##

(Optional) Creating Parameters Files for Network-Attached Automated Libraries

Perform this task if you want to include network-attached automated libraries in your Sun StorEdge SAM-FS environment.

Automated libraries can be included in a Sun StorEdge SAM-FS environment either by attaching them to the server directly or by attaching them to the environment's network. Libraries attached through a SCSI or Fibre Channel attachment are direct-attached libraries. Libraries attached through a network attachment are network-attached libraries. In this task, you create a parameters file for each network-attached library to be included in your environment.

To configure a network-attached library in your Sun StorEdge SAM-FS environment, find your library in the following list and go to the page indicated:

- ADIC/Grau Automated Libraries

- Fujitsu LMF Automated Libraries

- IBM 3494 Automated Libraries

- Sony Network-Attached Automated Libraries

- StorageTek ACSLS-Attached Automated Libraries

Shared Drives describes the shared drives feature that some libraries support.

Note - The examples and the discussions in the following subsections mention both the parameters files for network-attached automated libraries and the `mcf` file. The Sun StorEdge SAM-FS `mcf` file is the main configuration file for Sun StorEdge SAM-FS software. You created your `mcf` file in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File. The parameters file and the `mcf` file are both mentioned in this section because the two files reference each other.

### ADIC/Grau Automated Libraries

The ADIC/Grau automated library operates within Sun StorEdge SAM-FS environments through the `grauaci` interface. The `grauaci` interface is the interface between the Sun StorEdge SAM-FS software and the ADIC/Grau library. This interface uses the DAS/ACI 3.10 interface supplied by ADIC/Grau. For more information on the DAS/ACI interface, see your ADIC/Grau documentation.

To Configure the Parameters File for an ADIC/Grau Automated Library

1. Ensure that the ADIC/Grau automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.

Ensure that the following are true:

- The ADIC/Grau automated library must be operational.

- The ADIC/Grau library is operating on the DAS server.

- Both the `avc` (avoid volume contention) and the `dismount` parameters must be set to `true` in the DAS configuration file for this client.

2. Use the `cd`(1) command to change to the `/etc/opt/SUNWsamfs` directory.

The parameters file can be written to any directory, but Sun recommends that you write it to `/etc/opt/SUNWsamfs`.

When you created your `mcf` file, in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File, you included the full path name to the parameters file in the `mcf` file. Make sure that the `mcf` file points to the correct location for the parameters file you create in this procedure.

3. Use `vi`(1) or another editor to open a file.

It is a good idea to name the new file to correspond to the library you are configuring. For example, you could invoke `vi`(1) as follows:

    # vi grau50

4. Edit the ADIC/Grau parameters file to consist of a list of keyword = value parameter lines.

The various keyword values identify the ADIC/Grau automated libraries, the drives associated with the libraries, and the server name. All keyword and value entries are case sensitive, so enter them exactly as specified in the DAS configuration file and in the Sun StorEdge SAM-FS `mcf` file.

Include the following types of keyword = value parameters in the ADIC/Grau parameters file:

- `client =` client_id. For client_id, specify the name of the client as defined in the DAS configuration file. This is a required parameter.

- `server =` server_id. For server_id, specify the host name of the server running the DAS server code. This is a required parameter.

- `acidrive` drive_id = path. For drive_id, specify the name of the drive as configured in the DAS configuration file. For path, specify the path to the drive as entered in the Equipment Identifier field of the Sun StorEdge SAM-FS `mcf` file. There must be one `acidrive` line for every drive assigned to the client.

Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.

If the ADIC/Grau library contains various media types, then there is a media changer for each media type. Each media changer has a unique client name in the DAS configuration, a unique library catalog, and a unique parameters file.

The following code examples show two ADIC/Grau parameters files. CODE EXAMPLE 4-39 and CODE EXAMPLE 4-40 define one ADIC/Grau automated library supporting DLT tape and one ADIC/Grau automated library supporting a Hewlett Packard optical drive.

CODE EXAMPLE 4-39 shows the parameters file for library `grau50`.

CODE EXAMPLE 4-39 Parameters File `/etc/opt/SUNWsamfs/grau50`
    # This is file: /etc/opt/SUNWsamfs/grau50
    #
    client = DASclient
    server = DAS-server
    #
    # the name "drive1" is from the DAS configuration file
    #
    acidrive drive1 = /dev/rmt/0cbn     # a comment
    #
    # the name "drive2" is from the DAS configuration file
    #
    acidrive drive2 = /dev/rmt/1cbn     # a comment

CODE EXAMPLE 4-40 shows the parameters file for `grau60`.

CODE EXAMPLE 4-40 Parameters File `/etc/opt/samfs/grau60`
    # This is file: /etc/opt/SUNWsamfs/grau60
    #
    client = DASclient
    server = DAS-server
    acidrive DH03 = /dev/samst/c1t1u0
    #
    # the name "DH03" is from the DAS configuration file

5. Repeat this procedure and create a parameters file for each ADIC/Grau library that you want to configure.

CODE EXAMPLE 4-34 in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File shows the `mcf` file that corresponds with the ADIC/Grau network-attached automated library parameters file example that was created in this procedure. The example `mcf` points to files `grau50` and `grau60` in the `/etc/opt/SUNWsamfs` directory.

#### Diagnostic Information

The following directory contains diagnostic information that can be useful when troubleshooting:

    /var/opt/SUNWsamfs/.grau

The system creates files in this directory that are named `graulog-`eq, where eq is the Equipment Ordinal as defined in the `mcf` file. For more information on this, see the `grauaci`(7) and the `mcf`(4) man pages.

### Fujitsu LMF Automated Libraries

The Fujitsu LMF automated library operates in Sun StorEdge SAM-FS environments through the LMF interface supplied by Fujitsu. The `fujitsulmf` interface is the interface between the Sun StorEdge SAM-FS software and the Fujitsu LMF automated libraries. For more information on LMF, see the LMF MTL Server/Client User's Guide or the LMF SAM-FS Linkage Operations Guide. You can obtain both of these publications from the Fujitsu Corporation.

To Configure the Parameters File for a Fujitsu LMF Automated Library

The Fujitsu LMF parameters file identifies the drives in the automated library. Create one parameters file for each automated library.

1. Ensure that the Fujitsu LMF automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.

Ensure that the following are true:

- The Fujitsu LMF automated library is operational.

- The Fujitsu LMF software package is installed and working.

2. Use the `cd`(1) command to change to the `/etc/opt/SUNWsamfs` directory.

The parameters file can be written to any directory, but Sun recommends that you write it to `/etc/opt/SUNWsamfs`.

When you created your `mcf` file, in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File, you included the full path name to the parameters file in the `mcf` file. Make sure that the `mcf` file points to the correct location for the parameters file you create in this procedure.

3. Use `vi`(1) or another editor to open a file.

It is a good idea to name the new file to correspond to the library you are configuring. For example, you could invoke `vi`(1) as follows:

    # vi lmf50

4. Edit the Fujitsu LMF parameters file to consist of a list of drivename = value parameter lines.

The parameters file consists of `lmfdrive` drivename = value definition lines and comment lines. There must be one `lmfdrive` line for each drive assigned to the client automated library. Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.

All drivename and value information is case sensitive. TABLE 4-8 shows the values you can specify for drivename and value.

TABLE 4-8 The drivename and value Arguments
Argument | Definition
--- | ---
drivename | The name of the drive according to the LMF configuration.
value | The path to the drive. This path must match the Equipment Identifier field of the `mcf` file.

CODE EXAMPLE 4-41 shows a parameters file for a Fujitsu LMF automated library.

CODE EXAMPLE 4-41 Parameters File `/etc/opt/SUNWsamfs/lmf50`
    #
    # This is file /etc/opt/SUNWsamfs/lmf50
    #
    # The name "LIB001DRV000" is from the LMF configuration.
    #
    lmfdrive LIB001DRV000 = /dev/rmt/0cbn   # defines first drive
    #
    # the name "LIB001DRV001" is from the LMF configuration
    #
    lmfdrive LIB001DRV001 = /dev/rmt/1cbn  # defines second drive

5. Repeat this procedure and create a parameters file for each Fujitsu LMF library that you want to configure.

CODE EXAMPLE 4-35 in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File shows the `mcf` file that corresponds with the Fujitsu LMF network-attached automated library parameters file that was created in this procedure. The example `mcf` file points to file `lmf50` in the `/etc/opt/SUNWsamfs` directory.

### IBM 3494 Automated Libraries

The IBM 3494 automated tape library operates in Sun StorEdge SAM-FS environments with the assistance of the IBM `lmcpd` daemon package. You can obtain the IBM `lmcpd` daemon package from IBM.

To Configure the Parameters File for an IBM 3494 Automated Library

The IBM 3494 automated library can be used as a single physical library or as multiple logical libraries. If you divide this library into multiple logical libraries, create a parameters file for each logical library.

1. Ensure that the IBM 3494 automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.

Ensure that the following are true:

- The IBM 3494 automated library is operational.

- The IBM `lmcpd` daemon package is installed and working.

- The `/etc/ibmatl.conf` file is configured and working.

2. Use the `cd`(1) command to change to the `/etc/opt/SUNWsamfs` directory.

The parameters file can be written to any directory, but Sun recommends that you write it to `/etc/opt/SUNWsamfs`.

When you created your `mcf` file, in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File, you included the full path name to the parameters file in the `mcf` file. Make sure that the `mcf` file points to the correct location for the parameters file you create in this procedure.

3. Use `vi`(1) or another editor to open a file.

It is a good idea to name the new file to correspond to the library you are configuring. For example, you could invoke `vi`(1) as follows:

    # vi ibm50

4. Edit the IBM 3494 parameters file to consist of a list of keyword = value and pathname = value pairs.

All arguments are case-sensitive. TABLE 4-9 shows how to specify the parameters.

TABLE 4-9 IBM 3494 Parameters File Arguments
Parameter | Meaning
--- | ---
`name =` name | This is the name assigned by you, the system administrator, and specified in the `/etc/ibmatl.conf` file. This is also the symbolic name of the library. This parameter must be supplied, there is no default.
`category =` hexnumber | The category is a hexadecimal number such that `0x0001` < hexnumber < `0xfeff`. The Sun StorEdge SAM-FS software sets the `category` to this hexnumber for media under its control. The default is `4`. If you have divided your physical library into multiple logical libraries, create a parameters file for each logical library and make sure that the `category =` hexnumber parameter is different in each logical library. This parameter determines which tapes are assigned to which library. When you import media into the library, it is added to the catalog, and its `category=` value is changed to the value specified by this `category` = hexnumber parameter.
`access =` permission | For permission, specify either `shared` or `private`. Specify `private` if you are using the library as one physical library. Default. Specify `shared` if you are dividing the library into multiple logical libraries.
device-pathname = device-number [ `shared` ]
| Specify a device-pathname entry for every drive in the library attached to this machine. Each device-pathname must match the Equipment Identifier of an entry in the `mcf` file. The device-number is the device number as described in the IBM documentation. You can derive this number by running the IBM `mtlib` utility obtained from IBM. The `shared` parameter is optional. You can specify it if the drive is shared with other Sun StorEdge SAM-FS servers. For more information about shared drives, see Shared Drives.

CODE EXAMPLE 4-42 shows an example `/etc/ibmatl.conf` file. Information for this file was obtained from the `mtlib` utility supplied by IBM.

CODE EXAMPLE 4-42 Example `/etc/ibmatl.conf` File
    #
    # This is file: /etc/ibmatl.conf
    # Set this file up according the documentation supplied by IBM.
    3493a   198.174.196.50  test1

After the `lmcpd` daemon is running, you can use IBM's `mtlib` utility to get the device numbers. CODE EXAMPLE 4-43 shows output from `mtlib`.

CODE EXAMPLE 4-43 Output From `mtlib`
    # mtlib -l 3493a -D
    0, 00145340 003590B1A00
    1, 00145350 003590B1A01

CODE EXAMPLE 4-44 shows a sample parameters file and `mcf` entries for an IBM 3494 library.

CODE EXAMPLE 4-44 Parameters File `/etc/opt/SUNWsamfs/ibm50`
    #
    # This is file: /etc/opt/SUNWsamfs/ibm50
    #
    name = 3493a                     # From /etc/ibmatl.conf
    /dev/rmt/1bn = 00145340          # From mtlib output
    /dev/rmt/2bn = 00145350 shared   # From mtlib output
    access=private
    category = 5

5. Repeat this procedure and create a parameters file for each IBM 3494 library that you want to configure.

You must create a parameters for file for each physical or logical library you want to include in the Sun StorEdge SAM-FS environment.

CODE EXAMPLE 4-36 in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File shows the `mcf` file that corresponds with the IBM 3494 network-attached automated library parameters file that was created in this procedure. The example `mcf` file points to file `ibm50` in the `/etc/opt/SUNWsamfs` directory.

### Sony Network-Attached Automated Libraries

A Sony network-attached automated library operates within the Sun StorEdge SAM-FS environment through the DZC-8000S Application Interface Library package. This software package provides the application programmer interface (API) to the PetaSite Controller (PSC). For more information on the DZC-8000S interface, see the Sony PetaSite Application Interface Library DZC-8000S, which is available from Sony.

Note - The information in this section applies only to Sony automated libraries that are network-attached through a Sony DZC-8000S interface. If you want to include Sony direct-attached B9 and B35 automated libraries or Sony direct-attached 8400 PetaSite automated libraries, you do not need this information because you do not need to create a parameters file for your library.

To Configure the Parameters File for a Sony Network-Attached Automated Library

1. Ensure that the Sony network-attached automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.

Ensure that the following are true:

- The Sony network-attached automated library is operational.

- The Sony PSC configuration file is installed and working.

2. Use the `cd`(1) command to change to the `/etc/opt/SUNWsamfs` directory.

The parameters file can be written to any directory, but Sun recommends that you write it to `/etc/opt/SUNWsamfs`.

When you created your `mcf` file, in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File, you included the full path name to the parameters file in the `mcf` file. Make sure that the `mcf` file points to the correct location for the parameters file you create in this procedure.

3. Use `vi`(1) or another editor to open a file.

For example, you could invoke `vi`(1) as follows:

    # vi sonyfile

4. Edit the Sony parameters file to consist of a list of keyword = value parameter lines.

The Sony parameters file consists of a list of keyword = value parameter lines. The various keyword values identify the Sony automated libraries, the drives associated with the libraries, and the host name. All keyword and value entries are case sensitive, so enter them exactly as used in the configuration file and in the Sun StorEdge SAM-FS `mcf` file.

TABLE 4-10 shows the keyword = value parameters that must appear in the Sony parameters file. All parameters are required.

TABLE 4-10 Sony Network-Attached Automated Library Parameters
Parameter | Meaning
--- | ---
`userid` = user-id | For user-id, specify a number in the range 0 user-id 65535. If you specify a number other than 0, it must be the PSC ID. The `userid` parameter identifies the user during initialization of the PetaSite automated library functions.
`server` = server_id | For server_id specify the host name of the server running the PSC server code.
`sonydrive` drive_id = path [shared]
| There must be one `sonydrive` line for every drive defined in the `mcf` file. For drive_id, specify the drive bin number as configured in the PSC configuration file. For path, specify the path to the drive as entered in the Equipment Identifier field of the Sun StorEdge SAM-FS `mcf` file. The `shared` keyword is optional. You can configure this library to share its media drives with two or more Sun StorEdge SAM-FS processes from two or more hosts. For more information on implementing shared drives, see Shared Drives or see the `sony`(7) man page.

Comments can appear anywhere on any line, but they must begin with a pound sign (#). The system ignores characters to the right of the pound sign.

CODE EXAMPLE 4-45 shows the parameters file, `/etc/opt/SUNWsamfs/sonyfile`.

CODE EXAMPLE 4-45 Parameters File `/etc/opt/SUNWsamfs/sonyfile`
    #
    # This is file: /etc/opt/SUNWsamfs/sonyfile
    #
    # The userid identifies the user during initialization of
    # the PetaSite library functions
    #
    userid = 65533
    #
    # europa is the hostname for the server running
    # the DZC-8000S server code.
    #
    server = europa
    #
    # The bin numbers 1001 and 1002 are from the PSC
    # configuration file.
    #
    sonydrive 1001 = /dev/rmt/1cbn
    sonydrive 1002 = /dev/rmt/2cbn shared

5. Repeat this procedure and create a parameters file for each Sony network-attached library that you want to configure.

CODE EXAMPLE 4-37 in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File shows the `mcf` file that corresponds with the Sony network-attached automated library parameters file that was created in this procedure. The example `mcf` file points to file `sonyfile` in the `/etc/opt/SUNWsamfs` directory.

### StorageTek ACSLS-Attached Automated Libraries

In many respects, the Sun StorEdge SAM-FS systems interoperate with a StorageTek ACSLS-attached automated library in a manner similar to direct-attached automated libraries. However, a StorageTek ACSLS-attached automated library requires additional steps in the installation and configuration procedure as compared to a direct-attached automated library.

The ACSLS software package supplied by StorageTek controls the automated library. Daemon software controls the StorageTek automated library through the ACSAPI interface.

To Configure the Parameters File for a StorageTek ACSLS-Attached Automated Library

1. Ensure that the StorageTek ACSLS-attached automated library is prepared for inclusion in a Sun StorEdge SAM-FS environment.

Ensure that the following are true:

- The StorageTek ACSLS automated library is operational.

- The StorageTek ACSLS software package is installed and working.

2. Use the `cd`(1) command to change to the `/etc/opt/SUNWsamfs` directory.

The parameters file can be written to any directory, but Sun recommends that you write it to `/etc/opt/SUNWsamfs`.

When you created your `mcf` file, in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File, you included the full path name to the parameters file in the `mcf` file. Make sure that the `mcf` file points to the correct location for the parameters file you create in this procedure.

3. Use `vi`(1) or another editor to open a file.

For example, you could invoke `vi`(1) as follows:

    # vi stk50

4. Edit the StorageTek parameters file to consist of a list of keyword = value parameter lines.

Each line of the parameters file must begin with a keyword or a comment. TABLE 4-11 shows the keywords to use.

TABLE 4-11 StorageTek ACSLS-Attached Automated Library Parameters
Parameter | Meaning
--- | ---
`access =` userid | Specifies the user identification. For userid, enter the userid used by StorageTek for access control. This is an optional entry to the parameters file. If the `access =` parameter is not supplied, the access control string is a null string. This indicates that there is no userid.
`hostname` `=` hostname | Specifies the host name of the server. For hostname, enter the host name of the server running the StorageTek ACSLS interface.
`portnum =` portnum | Specifies the port number used for communication between ACSLS and the Sun StorEdge SAM-FS software. For information on what to enter for the portnum argument, see the `stk`(7) man page.
`ssihost` = hostname | Specifies the name of the server when you are using a multihomed Sun StorEdge SAM-FS server. This is the name of the Sun StorEdge SAM-FS server on the LAN that connects to the ACSLS host. Specify this directive only if you are including a multihomed Sun StorEdge SAM-FS server in your environment. The default is the name of the local host.
`csi_hostport` = csi_port | This firewall environment variable specifies the port to which the SSI sends its ACSLS requests on the ACSLS server. Setting this variable eliminates queries to the portmapper on the ACSLS server. Instead, it sends requests to this port on the ACSLS server. For csi_port, specify either 0 or a value such that 1024 csi_port 65535. Setting this variable to zero or leaving it unset causes the system to query the portmapper on the ACSLS server.
`capid` = ( `acs =` acsnum, `lsm =` lsmnum, `cap =` capnum )
| Specifies the CAP (Cartridge Access Port), in terms of the StorageTek library, to be used when the `export`(1M) `-f` command is specified. The `capid` description starts with an open parenthesis followed by three `keyword` `=` value pairs followed by a closing parenthesis. Use a comma (as shown), a colon, or a space to separate the keyword = value pairs. For acsnum, specify the ACS number for this CAP as configured in the StorageTek library. For lsmnum, specify the LSM number for this CAP as configured in the StorageTek library. For capnum, specify the CAP number for this CAP as configured in the StorageTek library.
`capacity =` ( index = value[, index = value ] . . . )
| Sets the capacity of the cartridges supported by StorageTek. Use a comma to separate the index = value pairs and enclose them in parentheses. For index, specify the index of the `media_type` file supplied by StorageTek and located in the following ACSLS directory: `/export/home/ACSSS/data/internal/mixed_media/media_types.dat` For value, enter the capacity of the cartridge type in units of 1024 bytes. TABLE 4-12 shows the capacity defaults that were current at the time of the Sun StorEdge SAM-FS 4.1 release. In general, it is necessary only to supply a capacity entry for an index of new cartridge types or to override the capacity supported by StorageTek.
device_path_name`=` ( `acs =` value, `lsm =` value, `panel =` value, `drive =` value ) [ `shared` ]
| Specifies the path to the device on the client. Specify one device_path_name = entry for each drive attached to this client. This parameter describes the drive within the StorageTek automated library. This description starts with an open parenthesis followed by four keyword = value pairs and a closing parenthesis. Use a comma (as shown), a colon, or a space to separate the keyword = value pairs. For the value arguments, use the information supplied by the ACSLS query drive command. TABLE 4-13 shows the value specifications. The `shared` keyword can follow the specification for the device path name. This specifies that the drive can be shared between two or more Sun StorEdge SAM-FS processes from two or more hosts. For more information on implementing shared drives, see Shared Drives or see the `stk`(7) man page.

TABLE 4-12 shows the capacity defaults.

TABLE 4-12 Capacity Defaults
index | Type | Capacity
--- | --- | ---
0 | 3480 | 210 MB (215040)
1 | 3490E | 800 MB (819200)
2 | DD3A | 10 GB (10485760)
3 | DD3B | 25 GB (26214400)
4 | DD3C | 50 GB (52428800)
5 | DD3D | 0 (DD3 cleaning tape)
6 | DLTIII | 10 GB (10485760)
7 | DLTIV | 20 GB (20971520)
8 | DLTIIIXT | 15 GB (15728640)
9 | STK1R (9840) | 20 GB (20971520)
10 | STK1U | 0 (STK1R cleaning tape)
11 | EECART | 1.6 GB (16777216)
12 | JCART | 0 GB (foreign label)
13 | STK2P (T9940A) | 60 GB (62914560)
14 | STK2W | 0 GB (T9940A cleaning tape)
15 | KLABEL | 0 GB (unsupported)
16 | LTO-100G | 100 GB (104857600)
17 | LTO-50G | 50 GB (52428800)
18 | LTO-35G | 35 GB (36700160)
19 | LTO-10G | 10 GB (10485760)
20 | LTO-CLN2 | 0 GB (cleaning tape)
21 | LTO-CLN3 | 0 GB (cleaning tape)
22 | LTO-CLN1 | 0 GB (cleaning tape)
23 | SDLT | 110 GB (115343360)
24 | LTO-CLNU | 0 GB (cleaning tape)
25 | Virtual | 0 GB (unsupported)
26 | LTO-200G | 200 GB (209715200)

TABLE 4-13 shows the value specifications.

TABLE 4-13 The value Specifications
Value | Content
--- | ---
`acs` | ACS number for the drive as configured in the StorageTek library
`lsm` | LSM number for the drive as configured in the StorageTek library
`panel` | PANEL number for the drive as configured in the StorageTek library
`drive` | DRIVE number for the drive as configured in the StorageTek library

CODE EXAMPLE 4-46 shows a parameters file for a StorageTek ACSLS-attached automated library:

CODE EXAMPLE 4-46 Parameters File `/etc/opt/SUNWsamfs/stk50`
    #
    #  This is file: /etc/opt/SUNWsamfs/stk50
    #
    hostname = baggins
    portnum = 50014
    access = some_user  # No white space allowed in user_id
    capacity = ( 7 = 20971520, 9 = 20971520 )
    ssi_inet_port = 0
    csi_hostport = 0
    capid = (acs=0, lsm=1, cap=0)
    /dev/rmt/0cbn = (acs=0, lsm=1, panel=0, drive=1) shared
    /dev/rmt/1cbn = (acs=0, lsm=1, panel=0, drive=2)

5. Repeat this procedure and create a parameters file for each ACSLS-attached library that you want to configure.

CODE EXAMPLE 4-38 in Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File shows the `mcf` file that corresponds with the StorageTek ACSLS-attached automated library parameters file that was created in this procedure. The example `mcf` file points to file `stk50` in the `/etc/opt/SUNWsamfs` directory.

### Shared Drives

Typically, the Sun StorEdge SAM-FS processes have exclusive control over a library's drives as declared in the host system's `mcf` file. In many cases, drives are defined in individual `mcf` files that are used by independent copies of Sun StorEdge SAM-FS processes. If a process is not using a drive, the drive stays idle.

The shared drives capability enables two or more `mcf` files to define the same drive, and this makes the drive available to more than one Sun StorEdge SAM-FS process. The shared drives capability enables each Sun StorEdge SAM-FS process to share a drive, but it does not allow the processes to share media. Each Sun StorEdge SAM-FS process must still maintain its own set of VSNs. Processes cannot share a single piece of media.

This feature can be useful, for example, if a library is attached to more than one host system in a Sun StorEdge SAM-FS environment. The shared drives capability enables you to keep the drives in a library busy. The Sun StorEdge SAM-FS processes coordinate the use of the drive.

You can configure some network-attached libraries to share one or all media drives between multiple Sun StorEdge SAM-FS processes on multiple host systems. The following types of libraries support shared drives:

- IBM 3494 libraries that use the `lmcpd` interface

- StorageTek ACSLS-attached libraries

Each of the preceding libraries requires you to create a parameters file. To implement one or more shared drives, make sure that the `shared` keyword is specified in the parameters file for each drive that is to be shared. The placement of the `shared` keyword is specific to each manufacturer's library, so see the preceding vendor-specific sections for more information.

By default, a cartridge in a shared drive can be idle for 60 seconds before being unloaded. To change this timing, specify the `shared_unload` directive in the `defaults.conf` file. For more information on this directive, see the `defaults.conf`(4) man page.

##

Initializing the Sun StorEdge SAM-FS Environment

This procedure initializes the environment.

Use the `samd`(1M) `config` command to initialize the Sun StorEdge SAM-FS environment.

For example:

    # samd config

##

(Optional) Checking the Drive Order

Perform this task if you are archiving to removable media.

The main objective of this task is to develop a list of drive number identifiers and the tape devices to which they are correlated. Because every automated library is a little different, this step in Sun StorEdge SAM-FS configuration process differs from library to library.

The drive order check procedure differs depending on whether your automated library has a front panel and whether it has tape or magneto-optical drives. Use one of the following procedures to check the drive order of each library:

- To Check the Drive Order of Tape or Magneto-Optical Libraries With a Front Panel

- To Check the Drive Order of Tape Libraries Without a Front Panel

- To Check the Drive Order of Magneto-Optical Libraries Without a Front Panel

### To Check the Drive Order of Tape or Magneto-Optical Libraries With a Front Panel

This procedure has two main phases:

- Mapping the drives to SCSI target IDs. This is accomplished through the following:

- Visual examination of the automated library's front panel.

- Physical examination of the drives.

For information on the order in which the drives appear in the front panel, consult the documentation from the vendor. This differs from library to library.

- Mapping the SCSI target IDs to tape devices by using output from the `ls`(1M) command. CODE EXAMPLE 4-47 shows example `ls`(1M) output with drive identification information.

CODE EXAMPLE 4-47 Using `ls` (1) to Retrieve Tape Device Information
    230-gort# ls -l /dev/rmt/?
    lrwxrwxrwx   1 root     root          42 Jan 10  2000 /dev/rmt/0 ->
    ../../devices/pci@1f,4000/scsi@2,1/st@2,0:
    lrwxrwxrwx   1 root     root          42 Jan 10  2000 /dev/rmt/1 ->
    ../../devices/pci@1f,4000/scsi@4,1/st@5,0:
    lrwxrwxrwx   1 root     root          42 Jan 10  2000 /dev/rmt/2 ->
    ../../devices/pci@1f,4000/scsi@4,1/st@6,0:
    lrwxrwxrwx   1 root     other         40 Dec 13  2000 /dev/rmt/3 ->
    ../../devices/pci@1f,4000/scsi@4/st@1,0:
    lrwxrwxrwx   1 root     root          40 Jun 20  2001 /dev/rmt/4 ->
    ../../devices/pci@1f,4000/scsi@4/st@2,0:
    lrwxrwxrwx   1 root     root          40 Jun 20  2001 /dev/rmt/5 ->
    ../../devices/pci@1f,4000/scsi@4/st@3,0:
    lrwxrwxrwx   1 root     root          40 Jun 20  2001 /dev/rmt/6 ->
    ../../devices/pci@1f,4000/scsi@4/st@4,0:
    lrwxrwxrwx   1 root     root          40 Sep 14  2001 /dev/rmt/7 ->
    ../../devices/pci@1f,4000/scsi@2/st@2,0:
    lrwxrwxrwx   1 root     root          40 Sep 14  2001 /dev/rmt/8 ->
    ../../devices/pci@1f,4000/scsi@2/st@3,0:
    lrwxrwxrwx   1 root     root          40 Sep 14  2001 /dev/rmt/9 ->
    ../../devices/pci@1f,4000/scsi@2/st@4,0:
    231-gort#

The procedure that follows is a framework for an iterative process. The actual steps you perform differ depending on your specific library. Consult your vendor documentation and follow this procedure to check the order of tape and magneto-optical drive devices for libraries with a front panel.

1. Use the `samd`(1M) `start` command to start the Sun StorEdge SAM-FS software.

For example:

    # samd start

2. Verify the order of the drives.

If the automated library contains more than one drive, list the drives in the `mcf` file in the same order that the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the `/var/adm/messages` file.

3. Verify the order in which the drives are recognized by the automated library's controller.

Check the SCSI target IDs or world wide numbers displayed by the control panel of the automated library. For optical drives, read the SCSI target IDs displayed on the control panel for your automated library. The order in which the drive targets are reported should be the order in which they are configured in the mcf file.

To determine whether the drives become active when loaded with a cartridge, you can visually inspect the drives or you can use the `samu`(1M) utility's `r` display.

Refer to your hardware maintenance manual for instructions on identifying and setting target addresses.

### To Check the Drive Order of Tape Libraries Without a Front Panel

1. Use the `samd`(1M) `start` commaned to start the software.

For example:

    # samd start

2. Use the `samcmd`(1M) `unavail` command to make the drive state unavailable to the Sun StorEdge SAM-FS file system.

Use this command in the following format:

    samcmd unavail eq

For eq, specify the Equipment Ordinal, as specified in the `mcf` file, of the drive you are testing.

For more information about the `samcmd`(1M) command's format, see the `samcmd`(1M) man page.

3. Use the `samload`(1M) command to load a cartridge into the drive.

Use this command in one of the following formats:

    samload mediatype.vsn deq

or:

    samload eq:slot deq

TABLE 4-14 shows the arguments for these commands.

TABLE 4-14 Arguments for `samcmd` (1M) `load`
Argument | Meaning
--- | ---
eq | The Equipment Ordinal of the automated library being addressed as defined in the `mcf` file.
slot | The number of a storage slot in an automated library as recognized in the library catalog.
media_type | The media type. For a list of valid media types, see the `mcf`(4) man page.
vsn | The volume serial name assigned to the volume.
deq | The destination drive you are testing.

For more information about the `samload`(1M) command's format, see the `samload`(1M) man page.

4. Use the `mt`(1) command to determine if the correct drive responds while under Sun StorEdge SAM-FS control.

Use this command in the following format:

    mt -f /dev/rmt/x status

For x, specify the raw tape device entry as specified in the `mcf` file.

CODE EXAMPLE 4-48 shows `mt`(1) command output that indicates that a tape is in the drive.

CODE EXAMPLE 4-48 Status Message Showing that a Tape is in a Drive
    # mt -f /dev/rmt/0 status
    DLT 7000 tape drive tape drive:
       sense key(0x2)= Not Ready   residual= 0   retries= 0
       file no= 0   block no= 0

If the tape did not load or the drive did not return a status, the drive might not be listed in the proper order in the `mcf`. Make sure the order is correct in the `mcf` file, and repeat this test.

5. Repeat this procedure for each drive in the library.

If your automated library contains more than one drive, list the drives in the `mcf` file in the same order that the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the `/var/adm/messages` file.

Make sure you check each drive in a library.

If you change any information in the `mcf` file as a result of this procedure, you must propagate the changes to the rest of the system. For information on propagating `mcf` file changes, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.

### To Check the Drive Order of Magneto-Optical Libraries Without a Front Panel

1. Use the `samd`(1M) `start` command to start the software.

For example:

    # samd start

2. Use the `samcmd`(1M) `unavail` command to make the drive state unavailable to the Sun StorEdge SAM-FS file system.

Use this command in the following format:

    samcmd unavail eq

For eq, specify the Equipment Ordinal, as specified in the `mcf` file, of the drive you are testing.

For more information about the `samcmd`(1M) command's format, see the `samcmd`(1M) man page.

3. Use the `samload`(1M) command to load a cartridge into the drive.

Use this command in one of the following formats:

    samload mediatype.vsn deq

or:

    samload eq:slot deq

TABLE 4-14 shows the arguments for these commands.

TABLE 4-15 Arguments for `samcmd` (1M) `load`
Argument | Meaning
--- | ---
eq | The Equipment Ordinal of the automated library being addressed as defined in the `mcf` file.
slot | The number of a storage slot in an automated library as recognized in the library catalog.
media_type | The media type. For a list of valid media types, see the `mcf`(4) man page.
partition | A side of a magneto-optical disk. The partition must be 1 or 2.
vsn | The volume serial name assigned to the volume.
deq | The destination drive you are testing.

For more information about the `samload`(1M) command's format, see the `samload`(1M) man page.

4. Use the `dd`(1M) command to determine if the correct drive reponds while under Sun StorEdge SAM-FS control.

Use this command in the following format:

    /bin/dd if=device_path bs=2k iseek=3374 of=/tmp/foo count=10

For device_path, specify the `samst` device entry as specified in the `mcf` file.

CODE EXAMPLE 4-49 shows a status message that indicates that an optical catridge is in the selected device:

CODE EXAMPLE 4-49 `dd` (1M) Showing a Cartridge in a Drive
    # dd if=/dev/samst/c0t3u0 bs=2k iseek=3374 of=/tmp/junk count=10
    10+0 records in
    10+0 records out

CODE EXAMPLE 4-50 shows a status message that indicates that an optical catridge is not in the selected device:

CODE EXAMPLE 4-50 `dd` (1M) Showing That a Cartridge is Not in the Drive
    # dd if=/dev/samst/c0t5u0 bs=2k iseek=3374 of=/tmp/junk1 count=10
    read: I/O error
    0+0 records in
    0+0 records out

If the optical catridge did not load or if the device returned messages like those in CODE EXAMPLE 4-50, the drives might not be listed in the correct order in the `mcf` file. Make sure the order is correct in the `mcf` file, repeat this test.

5. Repeat this procedure for each drive in the library.

If your automated library contains more than one drive, list the drives in the `mcf` file in the same order that the drives are viewed by the automated library's controller. The drive order that the media changer controller recognizes can be different from the order of the devices as reported in the `/var/adm/messages` file.

Make sure you check each drive in a library.

If you change any information in the `mcf` file, you must propagate the changes to the rest of the system. For information on propagating `mcf` file changes, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.

##

(Optional) Creating the `archiver.cmd` File

The archiver copies files from a Sun StorEdge SAM-FS file system to volumes on removable media cartridges or to disk partitions in another file system. You can tune the archiver operations to suit the types of files at your site and your site's data protection needs by creating an archiver command file to reside in `/etc/opt/SUNWsamfs/archiver.cmd`. This installation task guides you through the process of configuring an `archiver.cmd` file.

By default, the archiver automatically archives all files under all Sun StorEdge SAM-FS mount points. You are not required to create an `archiver.cmd` file, but archiver efficiency and performance increases if you tune the archiver to your site. The default settings for the archiver are as follows:

- The archiver archives all files to all available volumes in all configured libraries.

- The archiver makes one copy of each file.

- The archive age for all files is four minutes.

- The archive interval is 10 minutes.

### To Create an `archiver.cmd` File

1. Use `vi`(1) or another editor to create file `/etc/opt/SUNWsamfs/archiver.cmd`.

2. Add directives to satisfy the archiving needs at your site.

You can divide your `archiver.cmd` file into two main areas, as follows:

- The first part of this file is for global directives that apply to all file systems defined in your `mcf` file. You specify these directives at the top of the file.

- The second part of this file is for file-system specific directives that apply to only one file system. These directives must come after the global directives. For an individual file system, these directives override the global directives. The file-system specific directives are specified toward the bottom and are headed by an `fs=`name directive for each file system mentioned.

Certain directives are typically specified globally and others are typically specified only for individual file systems.

CODE EXAMPLE 4-51 shows a simple `archiver.cmd` file.

CODE EXAMPLE 4-51 Simple `archiver.cmd` File
    # archiver.cmd
    # One file system = samfs
    # One automated media library with 5 sg drives = aml
    archivemeta = off  # Do not archive meta data
    archmax = sg 2G  # A reasonable size for tarballs
    fs = samfs
    logfile = /var/opt/SUNWsamfs/log/archiver.samfs
    data .
       1 -norelease 10m
       2 -norelease 30m
    params
    # Start scheduling archive requests in a timely, efficient manner
    allsets -startage 20m -startcount 1000 -startsize 100G
    # Assure that the Archive Sets are not mixed on the tapes
    allsets -reserve set
    # Recycling has lower priority
    allsets -priority rearchive -10
    # Use multiple tape drives efficiently
    allsets -drivemin 10G -drivemax 20G -tapenonstop
    allsets.1 -drives 3
    allsets.2 -drives 2
    endparams
    vsns
    # Use all available volumes
    allsets sg .*
    endvsns

CODE EXAMPLE 4-51 shows a simple `archiver.cmd` file that you can add to or change as needed. A site should need to add directives only to accommodate more archive sets, copies, and VSN usage. CODE EXAMPLE 4-54 shows a more complex `archiver.cmd` file.

For information on some directives that are commonly found in `archiver.cmd` files, see Archiver Command File Directives. For comprehensive information on the `archiver.cmd` directives, see the `archiver.cmd`(4) man page and see the information on the archiver in the Sun StorEdge SAM-FS Storage and Archive Management Guide.

3. Close the `archiver.cmd` file.

4. Verify the `archiver.cmd` file for correctness.

Enter the following command:

    # archiver -lv

5. Correct any errors in the `archiver.cmd` file before proceeding to the next task in this installation and configuration procedure.

### Archiver Command File Directives

This section shows some of the recommended `archiver.cmd` file directives.

#### Specifying a Log File: `logfile=`pathname Directive

This directive specifies the file to which the archiver writes log messages. This log file contains information about each file that is archived, rearchived, or automatically unarchived. The log consists of a list of all archived files and their location on archive media. Specify this directive as a global directive so it affects all file systems configured in your `mcf` file. This archiver log information is important in disaster recovery situations if recent metadata is not available or not trustworthy.

#### Determining the Number of Archive Copies: copy_number
[ `-norelease` ] [ archive_age ] Directive

By default, the archiver creates one archive copy of each file. For better data protection, however, you should define two archive copies for each file and write the copies to physically different pieces of media.

The copy_number portion of this directive can be `1`, `2`, `3`, or `4`, which specifies that the archiver write from one to four archive copies. If you create more than one archive copy on more than one type of media, your data is better protected in the event that a piece of media is found to be faulty.

This directive also allows you to specify a `-norelease` option. The `-norelease` option prevents a file from being released from disk cache until all archive copies are made. By default, the releaser begins freeing up online disk cache when one archive copy is made. By specifying `-norelease`, you can avoid disk cache thrashing.

The archive_age specification for this directive allows you to specify the interval between the last time the file is written and when the file is archived. The interval is specified with an integer number and one of `s`, `m`, `h`, `d`, `w`, `y` to signify seconds, minutes, hours, days, weeks, or years.

#### Reserving Volumes: `vsns` and `endvsns` Directives

A set of reserved VSNs specifies individual VSN identifiers. These are the VSNs to be used as archive media for an archive set. As CODE EXAMPLE 4-52 shows, the `vsns` and `endvsns` directives surround the VSN identifiers.

CODE EXAMPLE 4-52 Fragment of an `archiver.cmd` File Showing Reserved VSNs
    vsns
    builds.2   sg   .*
    builds.3   li   .*
    support.2   sg   .*
    support.3   li   .*
    archive.2   sg   .*
    archive.3   li   .*
    samdev.1   sg   .*
    samdev.2   li   .*
    endvsns

You can accomplish the goal of creating archive copies on two different types of media by using reserved VSNs.

#### Determining Whether Metadata Is Archived: `archivemeta=on`|`off` Directives

Depending on your file system characteristics, you might want to archive file system metadata frequently and to multiple volumes, or you might not want to archive it at all. By default, `archivemeta=on` is enabled.

File system metadata changes when files are moved to different directories or when files are renamed. If this directory information changes rapidly and is important to your site, you might want to archive it frequently and to different media types.

Depending on how frequently you want the metadata archived, the result can be excessive drive activity as archive media is loaded and unloaded. If frequent loading and unloading is not desirable, you can go to the other extreme and specify that metadata not be archived by using the `archivemeta=off` directive.

#### Defining Archive Sets: the Archive Set Naming Directive

By default, files are archived as part of an archive set that has the same name as the file system. You can associate files into more meaningful groups by defining archive sets. This directive has the following format:

    archive_set_name path

CODE EXAMPLE 4-53 shows archive set assignment directives that assign files to archive sets `audiofiles` and `xrayfiles`.

CODE EXAMPLE 4-53 Archive Set Assignment Directives
    xrayfiles medical/radiology/rochester/xrays
    audiofiles net/home/cleveland/audio

#### Setting the Maximum Archive File Size: `archmax=`media size Directive

The `archmax=` directive specifies the maximum size of an archive file. The archiver groups user files to form this archive file. The maximum possible size of this archive file depends on your archive media's capacity, as follows:

- For tapes, the default is `archmax=512M`, which is 512 megabytes.

- For magneto-optical disks, the default is `archmax=5M`, which is 5 megabytes.

Depending on your archive media, you might want to specify that a larger or smaller archive file be written. Using the `archmax` directive can improve archiver performance by reducing the number of starts and stops to write tape marks.

#### Setting Miscellaneous Directives

The `archiver.cmd` file supports several other miscellaneous directives for tuning your site's archive policies. Directives are available for specifying an archive interval, the number of drives to use when archiving, and many other activities.

In addition, other directives in the `archiver.cmd` file control staging, releasing, and recycling behavior in conjunction with the `stager.cmd`, `recycler.cmd`, and `releaser.cmd` files.

For more information on all the directives that can appear in the `archiver.cmd` file, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.

### Advanced Archiver Command File Example

CODE EXAMPLE 4-51 shows a simple `archiver.cmd` file. CODE EXAMPLE 4-54 shows a more advanced `archiver.cmd` file.

CODE EXAMPLE 4-54 An Advanced `archiver.cmd` File
    ### Fri Jun  8 14:44:30 CDT 2001     ####
    ### Implemented ReservedVSNs feature ####
    ### using VSNs CFX.*                 ####
    interval = 1h
    logfile = /opt/logs/archive.log
    archmax = li 5G
    archmax = sg 2G
    archmax = lt 3500M
    archmax = at 1G
    #
    #  mounted on /support
    #
    fs = samfs2
            1 7y
    no_archive tmp
    support .
            2 -norelease 4h
            3 -norelease 4h
    # mounted on /builds
    #
    fs = samfs3
            1 10y
    interval = 2h
    no_archive daily
    builds  .
            2 8h
            3 8h
    #
    # mounted on /archive
    #
    fs = samfs4
            1 7y
    archive .
            2 1h
            3 1h
    #
    # mounted on /samdev
    #
    fs = samfs6
            1 7y
    samdev  .
            1 -norelease 1h
            2 -norelease 1h
    # We're not doing .inode copies.  File system data is archived
    # yearly.  Plan to use samfsdumps for restores when needed.
    params
    #allsets -offline_copy stageahead
    allsets -offline_copy direct
    builds.2 -drives 2
    builds.2 -reserve set
    support.2 -reserve set
    samdev.1 -reserve set
    samdev.1 -offline_copy none
    samdev.2 -offline_copy none
    endparams
    vsns
    builds.2        sg      .*
    builds.3        li      .*
    #builds.4       at     -pool rmt_pool
    #
    support.2       sg      .*
    support.3       li      .*
    #support.4      at     -pool rmt_pool
    #
    archive.2       sg      .*
    archive.3       li      .*
    #archive.4      at      -pool rmt_pool
    #
    samdev.1        sg      .*
    samdev.2        li      .*
    #
    samfs2.1        i7      TAPE19
    samfs3.1        i7      TAPE19
    samfs4.1        i7      TAPE19
    samfs6.1        i7      TAPE19
    endvsns

##

(Optional) Enabling Disk Archiving

Disk archiving is the process of writing archive copies of file data to online disk in another file system. The file system to which the archive copies are written can be any UNIX file system. The destination file system does not have to be a Sun StorEdge SAM-FS file system, but the host system to which archive files are written must have at least one Sun StorEdge SAM-FS file system installed on it.

Disk archiving differs from traditional archiving in several ways. For example, it does not use automated libraries or removable media cartridges. You can, however, specify that one set of archive copies be written to disk and another set be written to other archive media. For additional information on disk archiving, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.

If you plan to enable disk archiving, complete the following procedures:

- To Enable Disk Archiving on the Host That Contains the Files to Be Archived. Perform this procedure on the host system that contains the files to be archived.

- (Optional) To Enable Disk Archiving on the Host to Which the Archive Copies Will Be Written. Perform this procedure on the host system to which the archive copies will be written. There must be at least one Sun StorEdge SAM-FS file system created on this host. If you want to create your source files and write your archive copies to the same host system, you do not need to perform this procedure.

### To Enable Disk Archiving on the Host That Contains the Files to Be Archived

1. Become superuser on the host system that contains the files you want to archive.

2. Use `vi`(1) or another editor to create (or to open) file `/etc/opt/SUNWsamfs/archiver.cmd`.

If you are archiving to disk only, or if you have not yet created an `archiver.cmd` file, you create the `archiver.cmd` file in this step.

If you created an `archiver.cmd` file in (Optional) Creating the archiver.cmd File, you reopen the file in this step.

3. Edit the `archiver.cmd` file to add disk archive set directives.

CODE EXAMPLE 4-55 shows a fragment from an `archiver.cmd` file that defines disk archive sets.

CODE EXAMPLE 4-55 `/etc/opt/SUNWsamfs/archiver.cmd` on the Client
    # This is the part of the archiver.cmd file that defines
    # disk archive sets.
    #
    params
    archset1.1 -disk_archive disk01
    archset2.1 -disk_archive disk02
    archset3.1 -disk_archive disk03
    endparams

For more information on specifying archive sets, see the `archiver.cmd`(4) man page or see the Sun StorEdge SAM-FS Storage and Archive Management Guide.

4. Save and close the `archiver.cmd` file.

5. Use `vi`(1) or another editor to create a file named `diskvols.conf`.

The `diskvols.conf` file specifies the online disk directories to which the archive copies will be written.

Note - If you are configuring a Sun StorEdge SAM-FS file system for the first time at your site, write the archive copies to disk in a file system that is on the same host that the source files reside on. This is because you have not yet installed the Sun StorEdge SAM-FS software on another host. If you configure a Sun StorEdge SAM-FS file system on another host at a later time, you can modify your configuration files.

CODE EXAMPLE 4-56 shows an example `diskvols.conf` file:

CODE EXAMPLE 4-56 Example `diskvols.conf` File on the Client
    # This is file sourceserver:/etc/opt/SUNWsamfs/diskvols.conf
    # on the client.
    #
    # VSN_name [host_name:] path
    #
    disk01 otherserver:/sam/archset1
    disk02 otherserver:/sam/archset2
    disk03 /sam/archset3

CODE EXAMPLE 4-56 shows a `diskvols.conf` file that archives files from three archive sets. The disk volumes named `disk01` and `disk02` reside in a file system on the server system named `otherserver`. Disk volume `disk03` resides on the same host as the files to be archived.

As CODE EXAMPLE 4-56 shows, the `diskvols.conf` file can contain comment lines that begin with a pound character (`#`), and it must contain data in two fields: the VSN name field and the path field. You can leave the host name field blank if you are archiving to a file system that resides on the same host system as the source files, but if specified, it must be followed by a colon character (:). TABLE 4-16 shows the information that must appear in this file.

TABLE 4-16 Format of the `diskvols.conf` File
Field Name | Content
--- | ---
VSN Name | A unique alphanumeric name for the disk VSN to receive the archive copies. Can be up to 31 characters long.
Host Name | The name of the host to which archive copies will be written. This is an optional field. If you are archiving to disk on another host, you must use this field to specify the name of the destination server to receive the archive copies. If a host name is specified, it must be followed by a colon (`:`). If you are archiving to a file system that resides on the same server as the source file system, you do not need to specify the host name.
Path | The full path, relative to the mount point, to the directory to receive the archive files. This directory must be in place before archiving can commence, and the destination file system must be mounted. The Path should be specified relative to the mount point. For example, if archive copies are to be written to the `vsns` directory in the `archivefs1` file system, you would specify `/archivefs1/vsns` in the Path field. Sun Microsystems recommends that the destination directory be created with write permission granted only to `root`.

For more information about the `diskvols.conf` file, see the `diskvols.conf`(4) man page.

The following additional rules pertain to the `diskvols.conf` file:

- You can include comments in the `diskvols.conf` file. A pound character (#) indicates a comment, and all text to the right of the # is ignored.

- You can continue lines. To continue a line, put an apostrophe character (`'`) at the end.

6. Save and close the `diskvols.conf` file.

7. Create directories in the file system to which the archive copies will be written.

CODE EXAMPLE 4-57 shows the commands to create the directories to which archive copies will be written.

CODE EXAMPLE 4-57 Creating Archive Copy Directories
    # mkdir sam
    # cd sam
    # mkdir archset1
    # mkdir archset2

8. Use the `archiver`(1M) command with its `-lv` options to verify the correctness of the `archiver.cmd`(4) file.

Enter the following command:

    # archiver -lv

The preceding command verifies the `archiver.cmd` file syntax for errors. If any are found, correct them before proceeding.

### (Optional) To Enable Disk Archiving on the Host to Which the Archive Copies Will Be Written

Perform this procedure only if you are writing your archive copies to a host system that is different from the host system upon which the source files reside. In this situation, you are creating a client/server environment:

- The client is the host that contains the source files.

- The server is the host to which the archive copies are written. There must be at least one Sun StorEdge SAM-FS file system created on the server host.

Note - If you are installing a Sun StorEdge SAM-FS file system for the first time at your site, you cannot use this procedure because you cannot enable the writing of archive copies to a different host. If you configure a Sun StorEdge SAM-FS file system on another host at a later time, you can modify your configuration files.

1. Become superuser on the server system.

This is the system to which the archive copies will be written.

2. Use the `cd`(1) command to change to the file system to which you want to write the archive copies.

For example:

    # cd /ufs1

3. Create directories in the file system to which the archive copies will be written.

CODE EXAMPLE 4-58 shows the commands to create the directories to which archive copies will be written.

CODE EXAMPLE 4-58 Creating Archive Copy Directories
    # mkdir sam
    # cd sam
    # mkdir archset1
    # mkdir archset2

4. Use `vi`(1) or another editor to create file `/etc/opt/SUNWsamfs`/`diskvols.conf`.

This file contains the `clients` and `endclients` directives and names the client system upon which the the files to be archived reside.

For more information on disk archiving, see the Sun StorEdge SAM-FS Storage and Archive Management Guide.

CODE EXAMPLE 4-59 Example `diskvols.conf` File on the Server
    # This is
    # file destination_server:/etc/opt/SUNWsamfs/diskvols.conf
    # on the server
    #
    clients
    sourceserver
    endclients

5. Save and close the `diskvols.conf` file.

##

(Optional) Editing the `defaults.conf` File

The `/opt/SUNWsamfs/examples/defaults.conf` file contains directives that control automated library actions in a Sun StorEdge SAM-FS environment. You can change these settings at any time after the initial installation. If you change the information in the `defaults.conf` file after the system is up and running, for example, to accommodate changes in your site's library information, you must issue commands to propagate the `defaults.conf` file changes to the file system. The procedures for propagating the `defaults.conf` file changes are described in the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.

CODE EXAMPLE 4-60 shows lines from an example `defaults.conf` file. This file shows several parameters that can affect the configuration of an automated library.

CODE EXAMPLE 4-60 Example `defaults.conf` File
    exported_media = unavailable
    attended = yes
    tape = lt
    log = LOG_LOCAL7
    timeout = 300
    # trace
    # all on
    # endtrace
    labels = barcodes_low
    lt_delay = 10
    lt_unload = 7
    lt_blksize = 256

Another sample file is located in `/opt/SUNWsamfs/examples/defaults.conf`.

### To Customize Default Values for Your Site

1. Read the `defaults.conf`(4) man page to determine the defaults you want to change.

2. Use the `cp`(1) command to copy `/opt/SUNWsamfs/examples/defaults.conf` to its functional location.

For example:

    # cp /opt/SUNWsamfs/examples/defaults.conf /etc/opt/SUNWsamfs/defaults.conf

3. Use `vi`(1) or another editor to edit the file.

Edit the lines that control aspects of the system that you want to change. Remove the pound character (`#`) from column 1 of the lines you change.

4. Use the `pkill`(1M) command to send a SIGHUP signal to the `sam-fsd`(1M) daemon.

For example:

    # pkill -HUP sam-fsd

This command restarts the `sam-fsd`(1M) daemon and enables the daemon to recognize the changes in the `defaults.conf`(4) file.

### Features You Can Control From `defaults.conf`

The following sections describe two of the more common features you can control from this file. For more information on the `defaults.conf`(4) file, see the `defaults.conf`(4) man page.

#### Barcodes

If you have a tape library that uses a barcode reader, you can configure the system to set the tape label equal to the first or last characters of the barcode label. You can accomplish this by setting the `labels` directive in the `defaults.conf` file, as shown in TABLE 4-17.

TABLE 4-17 The `labels` Directive in the `defaults.conf` File
Directive | Action
--- | ---
`labels = barcodes` | Uses the first six characters of the barcode as the label. This setting enables the archiver to label new media on blank media automatically if the tape is chosen. Default.
`labels = barcodes_low` | Uses the last six characters of the barcode as the label.
`labels = read` | Reads the label from the tape. This setting prevents the archiver from labeling new media automatically.

If `labels = barcodes` or `labels = barcodes_low` is in effect, the Sun StorEdge SAM-FS system writes a label before the write is started for any tape that is mounted for a write operation that is write enabled, unlabeled, and has a readable barcode.

#### Drive Timing Values

You can set the load, unload, and unload wait time for devices using the dev`_delay` and dev`_unload` directives, respectively. These directives allow you to set these times to an interval that meets your site's requirements.

The format of the dev`_delay` directive is as follows:

    dev_delay = seconds

For dev, specify the device type as specified in the `mcf`(4) man page.

For seconds, specify an integer number specifying the minimum elapsed time between a cartridge being loaded and the same cartridge's ability to be unloaded. The default is `30`.

The format of the dev`_unload` parameter is as follows:

    dev_unload = seconds

For dev, specify the device type as specified in the `mcf`(4) man page.

For seconds, specify an integer number for the amount of time to wait after an `unload` command is issued. This gives the automated library time to eject the cartridge, open the door, and perform other operations before the cartridge is removed. The default is `0`.

For example:

    hp_delay = 10
    lt_unload = 7

##

Verifying the License and `mcf` Files

At this point in the installation and configuration process, the following files exist on your Sun StorEdge SAM-FS server:

- `/etc/opt/SUNWsamfs/LICENSE.4.2`

- `/etc/opt/SUNWsamfs/mcf`

The procedures in this task show you how to verify the correctness of these configuration files.

### To Verify the License File

Enter the `samcmd`(1M) `l` (lowercase L) command to verify the license file.

The `samcmd`(1M) output includes information on features that are enabled. If the output you receive is not similar to that shown in CODE EXAMPLE 4-61, return to Enabling the Sun StorEdge SAM-FS Software License.

CODE EXAMPLE 4-61 Using `samcmd` (1M)
    # samcmd l
    License information samcmd     4.1.71 Fri Aug 27 16:24:12 2004
    License: License never expires.
    hostid = xxxxxxxx
    License never expires
    Remote sam server feature enabled
    Remote sam client feature enabled
    Migration toolkit feature enabled
    Fast file system feature enabled
    Data base feature enabled
    Foreign tape support enabled
    Segment feature enabled
    Shared filesystem support enabled
    SAN API support enabled
    Robot type ATL 2640, P1000, or Sun L1000 Library is present and licensed
        0 tp slots not licensed
        30 lt slots present and licensed
    Robot type STK ACSLS Library is present and licensed
        0 tp slots not licensed
        500 sg slots present and licensed
        500 li slots licensed

### To Verify the `mcf` File

Enter the `sam-fsd`(1M) command to verify the `mcf` file.

If your `mcf` file is free from syntax errors, the `sam-fsd`(1M) output includes information about the file systems, archiving, and other system information. If your `mcf` file contains syntax or other errors, however, the output is similar to that shown in CODE EXAMPLE 4-62.

CODE EXAMPLE 4-62 Example `sam-fsd` (1M) Output
    # sam-fsd
    13: /dev/dsk/c1t1d0s0   10      md      samfs1  on      /dev/rdsk/c1t1d0s0
     *** Error in line 13: Equipment name '/dev/dsk/c1t1d0s0' already in use by eq 10
    72: /dev/rmt/3cbn       45      ug      l1000   on
     *** Error in line 72: Equipment name '/dev/rmt/3cbn' already in use by eq 44
    2 errors in '/etc/opt/SUNWsamfs/mcf'
    sam-fsd: Read mcf /etc/opt/SUNWsamfs/mcf failed.

If your `mcf` file has errors, refer to Defining the Sun StorEdge SAM-FS Configuration By Creating the mcf File and to the `mcf`(4) man page for information on how to create this file correctly.

##

(Optional) Labeling Removable Media Cartridges

If you have standalone tape or optical devices, or if your automated library has no barcode reader, you must perform this task.

To prepare cartridges, use the tplabel(1M) command for tapes or use the odlabel(1M) command for optical disks. These commands create a cartridge label that the Sun StorEdge SAM-FS software can read.

The tplabel(1M) command has the following format:

    tplabel -new -vsn new_vsn eq:slot

TABLE 4-18 Arguments for the `tplabel` (1M) Command
Argument | Meaning
--- | ---
new_vsn | The new volume serial name.
eq | The Equipment Ordinal of the automated library or manually loaded drive being addressed as defined in the `mcf` file.
slot | The number of a storage slot in an automated library as recognized in the library catalog. This argument is not applicable for manually loaded drives.

The `odlabel`(1M) command has the following format:

    # odlabel -new -vsn new_vsn eq:slot:partition

TABLE 4-19 Arguments for the `odlabel` (1M) Command
Argument | Meaning
--- | ---
new_vsn | The new volume serial name.
eq | The Equipment Ordinal of the automated library or manually loaded drive being addressed as defined in the `mcf` file.
slot | The number of a storage slot in an automated library as recognized in the library catalog. This argument does not apply to manually loaded drives.
partition | A side of a magneto-optical disk. The partition must be 1 or 2.

You can use the cartridges after you issue these commands. Both the `tplabel`(1M) and the `odlabel`(1M) commands accept a `-old` option that you can use to relabel previously labeled cartridges. For more information about these commands, see the `tplabel`(1M) and `odlabel`(1M) man pages.

Example 1. The following command labels a tape:

    # tplabel -vsn TAPE01 -new 50:0

Example 2. The following command labels one side of an optical disk:

    # odlabel -vsn OPTIC01 -new 30:1:1

If you are not using an automated library with a barcode reader, label all cartridges manually before using the Sun StorEdge SAM-FS system.

If your library uses barcodes, `labels = barcodes` is set by default, and the result is that the first six characters are used for the VSN.

If your library uses barcodes, and you want the last six characters to become the VSN for the cartridge, edit the `/etc/opt/SUNWsamfs/defaults.conf` file and include the following line:

    labels = barcodes_low

When the software loads a barcoded cartridge for a write operation, it writes a label on the cartridge before the write begins. The cartridge must be write enabled, unlabeled, and have a readable barcode.

##

(Optional) Populating the Catalog

Perform this task if you have a network-attached automated library configured in your Sun StorEdge SAM-FS environment.

After you mount the Sun StorEdge SAM-FS file systems, the software creates catalogs for each automated library configured in the `mcf` file. If you have a network-attached automated library, however, you need to populate the library's catalog. There are several ways to populate an automated library. The appropriate method depends on the number of volumes you want to include in the catalog.

The following sections describe various methods for populating an automated library's catalog:

- To Populate an Automated Library With Many Volumes. You can use this procedure for ADIC/Grau, Fujitsu LMF, Sony Network-Attached, StorageTek ACSLS-Attached, and IBM 3494 automated libraries.

- To Populate an Automated Library With a Small Number of Volumes. You can use this procedure for ADIC/Grau, Fujitsu LMF, Sony Network-Attached, StorageTek ACSLS-Attached, and IBM 3494 automated libraries.

- To Populate an IBM 3494 Automated Library. This is an additional procedure for populating an IBM 3494 library. You can use this procedure only if you are using the library as one physical library (`access=private` in the `mcf` file). Do not use this procedure if you divided the library into multiple logical libraries.

- To Populate a Library Quickly (StorageTek ACSLS-Attached Libraries Only). This is an alternative, and in some cases faster, method of populating the catalog of a StorageTek ACSLS-attached automated library.

Note - The slot position of a tape in a network-attached automated library has no relationship to the slot number of the volume in a Sun StorEdge SAM-FS library catalog.

### To Populate an Automated Library With Many Volumes

1. Use `vi`(1) or another editor to create an input file that contains the slot number, the volume's VSN, the barcode number, and the media type.

Note the following when creating the input file:

- The file has four fields in each row. Each row identifies a volume. For each volume, specify the slot number, the VSN, the bar code, and the media type.

- Use a space character or a tab character to separate the fields in this file.

- If a VSN contains one or more space characters, enclose the VSN name in quotation marks (" ").

CODE EXAMPLE 4-63 shows example file `input_vsns`.

CODE EXAMPLE 4-63 Example File `input_vsns`
    0 TAPE01  "TAPE 01" lt
    1 TAPE02  TAPE02  lt
    2 TAPE03  TAPE03  lt

2. Use the `build_cat`(1M) command to create the catalog.

The syntax for the `build_cat`(1M) command is as follows:

    build_cat input-file catalog-file

Argument | Content
--- | ---
input-file | Specify the name of an input file. Typically, this is a file containing a list of VSNs.
catalog-file | Specify the full path to the library catalog. By default, the Sun StorEdge SAM-FS software creates a catalog and writes it to `/var/opt/SUNWsamfs/catalog/`family-set-name, where family-set-name is derived from the `mcf` file entry for this automated library. Alternatively, if you have specified a catalog name in the Additional Parameters field of the `mcf` file, use that catalog file name for catalog-file.

For example, you can specify the following `build_cat`(1M) command:

    # build_cat input_vsns /var/opt/SUNWsamfs/catalog/grau50

For more information on the `build_cat`(1M) command, see the `build_cat`(1M) man page.

### To Populate an Automated Library With a Small Number of Volumes

1. Use the `import`(1M) command to import catalog entries into the default catalog.

The syntax for the `import`(1M) command is as follows:

    import -v VSN eq

Argument | Content
--- | ---
VSN | Specify the VSN identifier for a volume. If a VSN name contains one or more space characters, enclose the VSN name in quotation marks (" ").
eq | Specify the Equipment Ordinal as specified for the device in the `mcf` file.

For example:

    # import -v TAPE01 50

In the preceding `import`(1M) command, note the following:

- `TAPE01` is the VSN.

- `50` is the Equipment Ordinal of the automated library as specified in the `mcf` file.

The cartridges must be physically present in the automated library for the `import`(1M) commands to be successful. If a cartridge is not present, the entry goes into the historian.

For more information on the `import`(1M) command, see the `import`(1M) man page.

2. Repeat Step 1 for each cartridge you want to include in the catalog.

### To Populate an IBM 3494 Automated Library

Insert the media cartridges you want to include in this library's catalog through the mail slot.

The library automatically builds a catalog that includes the media that you put into the slot.

Note - Do not use this method to populate an IBM 3494 automated library that has been divided into multiple logical libraries. Use this method only if `access=private` in the IBM 3494 parameters file. If you have an IBM 3494 library that is divided into multiple logical libraries (`access=shared` in the IBM 3494 parameters file), use one of the following methods to populate the catalog: To Populate an Automated Library With Many Volumes or To Populate an Automated Library With a Small Number of Volumes.

### To Populate a Library Quickly (StorageTek ACSLS-Attached Libraries Only)

If you have an ACSLS-Attached library, you can use the `import`(1M) command with its `-c` and `-s` options to import from a pool of VSNs. This procedure is a faster method for populating a library catalog than the methods described in To Populate an Automated Library With Many Volumes and To Populate an Automated Library With a Small Number of Volumes.

For more information on this, see the `import`(1M) man page. You can use this method only if you have a StorageTek ACSLS-attached automated library.

### StorageTek ACSLS-Attached Automated Libraries -- Common Problems and Error Messages

If errors exist in the configuration files for StorageTek ACSLS-attached automated library, the system generates several error messages. The following examples show common problems and the messages that the system generates.

Example 1. CODE EXAMPLE 4-64 shows the messages generated when there are syntax errors in the StorageTek parameters file. Check your StorageTek parameters file for syntax errors and remember that each line must begin with a keyword or a comment. For more information on the StorageTek parameters file, see the `stk`(7) man page.

CODE EXAMPLE 4-64 Errors From an Incorrect StorageTek Parameters File
    May 23 09:26:13 baggins stk-50[3854]: initialize: Syntax error in stk configuration file line 4.
    May 23 09:26:13 baggins stk-50[3854]: initialize: Syntax error in stk configuration file line 5.

Example 2. Assume that you receive two sets of error messages. CODE EXAMPLE 4-65 shows the first set.

CODE EXAMPLE 4-65 Error Messages from a Misconfigured StorageTek Library
    May 23 09:29:48 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize
    May 23 09:29:59 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize
    May 23 09:30:39 baggins stk-50[3854]: main: Waiting for 2 drive(s) to initialize

The following is the second set:

    May 23 09:31:19 baggins stk-50[3854]: main: 2 drive(s) did not initialize.

CODE EXAMPLE 4-66 shows the `samu`(1M) utility's `:r` display.

CODE EXAMPLE 4-66 Output Shown in `samu` (1M)'s `:r` Display
    ty   eq  status      act  use  state    vsn
    sg   51  ---------p    0   0%  off
            drive set off due to ACS reported state
    sg   52  ---------p    0   0%  off
            drive set off due to ACS reported state
    lt   61  ---------p    0   0%  off
            drive set off due to ACS reported state
    tp   62  ----------    0   0%  off
            empty

Drives that are hung in an initializing state or that do not initialize usually indicate a configuration error. Verify that ACSLS is up and running. Verify the host name. Determine whether you can you ping the host name using the `ping`(1M) command.

Check the `portnum` specification in the StorageTek parameters file. In ACSLS 5.3, for example, the default port number, 50004, is used for a different application. Try a higher port number, such as 50014.

Example 3. CODE EXAMPLE 4-67 shows messages generated after the `import`(1M) command was used to import a VSN to the library catalog, but the VSN was not in the StorageTek automated library. The cartridge must be present in the ACSLS-managed automated library before the `import`(1M) command can be successful.

CODE EXAMPLE 4-67 Message Generated After an Attempted `import` (1M)
    May 20 15:09:33 baggins stk-50[6117]: view_media returned:STATUS_VOLUME_NOT_IN_LIBRARY
    May 20 15:09:33 baggins stk-50[6117]: add_to_cat_req: view_media: failed:STATUS_VOLUME_NOT_IN_LIBRARY. A

The `sam-stkd` daemon uses the `ssi.sh` script to ensure that a copy of the SSI daemon, `ssi_so`, is running. If `ssi_so` exits, the daemon starts another. If your site has its own version of `ssi.sh`, you should modify it to wait for a `SIGTERM` signal and then exit. The daemon sends a `SIGTERM` signal to stop the process. File `/opt/SUNWsamfs/examples/ssi.sh` contains an example `ssi.sh` script. The system copies the `ssi.sh` script to `/etc/opt/SUNWsamfs/scripts/ssi.sh` during installation if one does not already exist.

##

(Optional) Creating the `samfs.cmd` File

You can create the `/etc/opt/SUNWsamfs/samfs.cmd` file as the place from which the system reads mount parameters. If you are configuring multiple Sun StorEdge SAM-FS systems with multiple mount parameters, consider creating this file.

You can specify mount parameters in the following ways:

- On the `mount`(1M) command. Mount options specified here override those specified in the `/etc/vfstab` file and in the `samfs.cmd` file.

- In the `/etc/vfstab` file. Mount options specified here override those specified in the `samfs.cmd` file.

- In the `samfs.cmd` file.

For more information about the `/etc/vfstab` file, see Updating the /etc/vfstab File and Creating the Mount Point. For more information on the `mount`(1M) command, see the `mount_samfs`(1M) man page.

### To Create the `samfs.cmd` File

Use `vi`(1) or another editor to create the `samfs.cmd` file.

Create lines in the `samfs.cmd` file to control mounting, performance features, or other aspects of file system management. For more information on the `samfs.cmd` file, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide, or see the `samfs.cmd`(4) man page.

##

Updating the `/etc/vfstab` File and Creating the Mount Point

The example in this task assumes that `/samfs1` is the mount point of the `samfs1` file system.

### To Update the `/etc/vfstab` File and Create the Mount Point

1. Use `vi`(1) or another editor to open the `/etc/vfstab` file and create an entry for each Sun StorEdge SAM-FS file system.

CODE EXAMPLE 4-68 shows header fields and entries for a Sun StorEdge SAM-FS file system.

CODE EXAMPLE 4-68 Example `/etc/vfstab` File Entries for a Sun StorEdge SAM-FS File System
    #DEVICE    DEVICE   MOUNT   FS    FSCK  MOUNT    MOUNT
    #TO MOUNT  TO FSCK  POINT   TYPE  PASS  AT BOOT  PARAMETERS
    #
    samfs1     -        /samfs1 samfs  -    yes      high=80,low=60

TABLE 4-20 shows the various fields in the `/etc/vfstab` file and their content.

TABLE 4-20 `/etc/vfstab` File Fields
Field | Field Title and Content
--- | ---
1 | Device to mount. The name of the Sun StorEdge SAM-FS file system to mount. This must be the same as the file system's Family Set name specified in the `mcf` file.
2 | Device to `fsck`(1M). Must be a dash (`-`) character. The dash indicates that there are no options. This prevents the Solaris system from performing an `fsck`(1M) on the Sun StorEdge SAM-FS file system. For more information about this process, see the `fsck`(1M) or `samfsck`(1M) man page.
3 | Mount point. For example, `/samfs1`.
4 | File system type. Must be `samfs`.
5 | `fsck`(1M) pass. Must be a dash (-) character. A dash indicates that there are no options.
6 | Mount at boot. Specifying `yes` in this field requests that the Sun StorEdge SAM-FS file system be mounted automatically at boot time. Specifying `no` in this field indicates that you do not want to mount the file system automatically. For information about the format of these entries, see the `mount_samfs`(1M) man page.
7 | Mount parameters. A list of comma-separated parameters (with no spaces) that are used in mounting the file system. You can specify mount options on the `mount`(1M) command, in the `/etc/vfstab` file, or in a `samfs.cmd` file. Mount options specified on the `mount`(1M) command override those specified in the `/etc/vfstab` file and in the `samfs.cmd` file. Mount options specified in the `/etc/vfstab` file override those in the `samfs.cmd` file. For a list of available mount options, see the `mount_samfs`(1M) man page.

2. Use the `mkdir`(1M) command to create the mount point.

For example:

    # mkdir /samfs1

##

Initializing the File System

This task shows how to use the `sammkfs`(1M) command and the Family Set names that you have defined to initialize a file system.

Note - The `sammkfs`(1M) command sets one tuning parameter, the disk allocation unit (DAU). You cannot reset this parameter without reinitializing the file system. For information about how the DAU affects tuning, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide or see the `sammkfs`(1M) man page.

### To Initialize the File System

Use the `sammkfs`(1M) command to initialize a file system for each Family Set name defined in the `mcf` file.

CODE EXAMPLE 4-69 shows the command to initialize a file system with the Family Set name of `samfs1`.

CODE EXAMPLE 4-69 Initializing Example File System `samfs1`
    # sammkfs samfs1
    sammkfs: Configuring file system
    Building 'samfs1' will destroy the contents of devices:
                    /dev/dsk/c2t0d0s3
                    /dev/dsk/c2t0d0s7
    Do you wish to continue? [y/N] y
    total data kilobytes       = 16777728
    total data kilobytes free  = 16777152
    #

The actual numbers returned vary from file system to file system.

| Caution - Running the `sammkfs`(1M) command creates a new file system. It removes all data currently contained in the partitions associated with the file system in the `/etc/opt/SUNWsamfs/mcf` file.

##

Mounting the File System

The `mount`(1M) command mounts a file system and reads the `/etc/vfstab` configuration file. For information on the `mount`(1M) command, see the `mount_samfs`(1M) man page.

### To Mount the File System

1. Use the `mount`(1M) command to mount the file system.

Specify the file system mount point as the argument. For example:

    # mount samfs1

2. Use the `mount`(1M) command with no arguments to verify the mount.

This step confirms whether the file system is mounted and shows how to set permissions. CODE EXAMPLE 4-70 shows the output from a `mount`(1M) command issued to verify whether example file system `samfs1` is mounted.

CODE EXAMPLE 4-70 Using the mount(1M) Command to Verify that a File System is Mounted
    # mount
    <<< information deleted >>>
    /samfs1 on samfs1 read/write/setuid/intr/largefiles/onerror=panic/dev=8001e3 on Thu Feb  5 11:01:23 2004
    <<< information deleted >>>

3. (Optional) Issue the `chmod`(1) and `chown`(1) commands to change the permissions and ownership of the file system's root directory.

If this is the first time the file system has been mounted, it is typical to perform this step. CODE EXAMPLE 4-71 shows the commands to use to change file system permissions and ownership.

CODE EXAMPLE 4-71 Using `chmod` (1M) and `chown` (1M) to Change File System Permissions and Ownership
    # chmod 755 /samfs1
    # chown root:other /samfs1

##

(Optional) Sharing the File System With NFS Client Systems

Perform this task if you want the Sun StorEdge SAM-FS file system to be NFS shared.

Run the Sun Solaris `share`(1M) command to make the file system available for mounting by remote systems. The `share`(1M) commands are typically placed in the `/etc/dfs/dfstab` file and are executed automatically by the Sun Solaris OS when you enter `init`(1M) state 3.

### To NFS Share the File System

1. Use `vi`(1) or another editor to add a `share`(1M) command to the `/etc/dfs/dfstab` file.

For example, add a line like the following to direct the Solaris OS to NFS share the new Sun StorEdge SAM-FS file system:

    share -F nfs -o rw=client1:client2 -d "SAM-FS" /samfs1

2. Use the `ps`(1) command to determine whether or not `nfs.server` is running.

CODE EXAMPLE 4-72 shows these commands and their output.

CODE EXAMPLE 4-72 Commands and Output Showing NFS Activity
    # ps -ef | grep nfsd
        root   694     1  0   Apr 29 ?        0:36 /usr/lib/nfs/nfsd -a 16
    en17     29996 29940  0 08:27:09 pts/5    0:00 grep nfsd
    # ps -ef | grep mountd
        root   406     1  0   Apr 29 ?       95:48 /usr/lib/autofs/automountd
        root   691     1  0   Apr 29 ?        2:00 /usr/lib/nfs/mountd
    en17     29998 29940  0 08:27:28 pts/5    0:00 grep mountd

In CODE EXAMPLE 4-72, the lines that contain `/usr/lib/nfs` indicate that the NFS server is mounted.

3. (Optional) Start the NFS server.

Perform this step if `nfs.server` is not running.

Use the following command:

    # /etc/init.d/nfs.server start

4. (Optional) Type the `share`(1M) command at a `root` shell prompt.

Perform this step if you want to NFS share the file system immediately.

If there are no NFS shared file systems when the Sun Solaris OS boots, the NFS server is not started. CODE EXAMPLE 4-73 shows the commands to use to enable NFS sharing. You must change to run level 3 after adding the first share entry to this file.

CODE EXAMPLE 4-73 NFS Commands
    # init 3
    # who -r
    .       run-level 3  Dec 12 14:39     3    2  2
    # share
    -          /samfs1  -   "SAM-FS"

Some NFS mount parameters can affect the performance of an NFS mounted Sun StorEdge SAM-FS file system. You can set these parameters in the `/etc/vfstab` file as follows:

- `timeo =` n. This value sets the NFS timeout to n tenths of a second. The default is eleven tenths of a second. For performance purposes, Sun Microsystems recommends using the default value. You can increase or decrease the value appropriately to your system.

- `rsize =` n. This value sets the read buffer size to n bytes. In NFS 2, change the default value (8192) to 32768. In NFS 3, retain the default value of 32768.

- `wsize =` n. This value sets the write buffer size to n bytes. In NFS 2, change the default value (8192) to 32768. In NFS 3, retain the default value of 32768.

For more information on these parameters, see the `mount_nfs`(1M) man page.

### To Mount the File System on Clients

On the client systems, mount the server's Sun StorEdge SAM-FS file system at a convenient mount point.

1. On the client systems, use `vi`(1) or another editor to edit the `/etc/vfstab` file and add a line to mount the server's Sun StorEdge SAM-FS file system at a convenient mount point.

The following example line mounts `server:/samfs1` on the `/samfs1` mount point:

    server:/samfs1   -   /samfs1   nfs   -   yes   hard,intr,timeo=60

In this example,`server:/sam`fs1 is mounted on `/samfs1`, and information is entered into the `/etc/vfstab` file.

2. Save and close the `/etc/vfstab` file.

3. Enter the `mount`(1M) command.

For example:

    client# mount /samfs1

The automounter can also do this, if you prefer. Follow your site procedures for adding `server :/samfs1` to your automounter maps. For more information on automounting, see the `automountd`(1M) man page.

Note - At times, there might be a significant delay in the Sun StorEdge SAM-FS file system's response to NFS client requests. This can occur if a requested file resides on a cartridge that must be loaded into a DLT tape drive, if all tape drives are full, or if drives are slow. As a consequence, the system might generate an error instead of retrying until the operation completes. To avoid this situation, Sun recommends that clients mount the file system with either the `hard` option enabled or with the `soft`, `retrans`, and `timeo` options enabled. If you use the `soft` option, also specify `retrans=120` (or greater) and `timeo=3000`.

##

Writing Periodic Dump Files By Using `samfsdump`(1M)

It is important to use the `samfsdump`(1M) command periodically to create a metadata dump file.

When using the `samfsdump`(1M) command, please note the following:

- The `samfsdump`(1M) command dumps file names and inode information, not data. That is, the dump file does not include the archive data stored in your file system. The dump file does include the inode and directory structure information necessary to quickly locate the data on your archive media. This information is necessary for recovering from a file system failure. For more information on this, see the`samfsdump`(1M) man page.

- You can use the `-u` option to the `samfsdump`(1M) command to dump metadata and file data for files that have not yet been archived. A `samfsdump`(1M) dump taken using the `-u` option can be very large. The `samfsdump`(1M) command does not have any tape management or estimations as does `ufsdump`(1M). You need to weigh the tradeoffs of space and unarchived data when using the `-u` option. For more information about these commands, see the `samfsdump`(1M) and `ufsdump`(1M) man pages.

- You can use the `samfsrestore`(1M) command to restore the metadata dump file after initializing the file system if a failure occurs.

For more information about using the `samfsdump`(1M) command, see the `samfsdump`(1M) man page. Also see the information on metadata, disaster preparation, and recovery in the Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.

The following sections describe procedures for issuing this command both automatically and manually.

### To Run the `samfsdump`(1M) Command Automatically

1. Make an entry in the root user's `crontab` file so the `cron` daemon runs the `samfsdump`(1M) command periodically.

CODE EXAMPLE 4-74 shows a cron(1) entry.

CODE EXAMPLE 4-74 `cron` (1) Entry to Run `samfsdump` (1M) Automatically
    0 0 * * * find /csd.directory/sam -type f -mtime +7 \
    -print| xargs -l1 rm -f; cd /sam; \
    /opt/SUNWsamfs/sbin/samfsdump -f \
    /csd.directory/sam/`date +\%y\%m\%d`

This example `crontab` entry uses a Sun StorEdge SAM-FS file system mounted on `/sam`. Replace `/csd.directory` with an existing directory of your choice. This entry causes the commands to execute each day at midnight. First, the old dumps are renamed and a new dump is created in `/csd.directory/sam/`yymmdd. After that, `cron`(1M) emails the `samfsdump`(1M) output to `root`.

2. (Optional) Using the previous step as a guide, make similar `crontab` entries for each file system.

If you have multiple Sun StorEdge SAM-FS file systems, make similar entries for each. Make sure you save each dump in a separate file.

### To Run the `samfsdump`(1M) Command Manually

1. Use the `cd`(1) command to go to the directory that contains the mount point for the file system.

For example:

    # cd /samfs1

In this example, `samfs1` is a Sun StorEdge SAM-FS mount point.

2. Use the `samfsdump`(1M) command to write the output to a file system outside of the one you are dumping.

For example:

    # samfsdump -T -u -f /dumpster/dump.file

In this example, `dump.file` is the newly created dump structure.

##

(Optional) Backing Up Configuration Files

Sun StorEdge SAM-FS regularly accesses several files that have been created as part of this installation and configuration procedure. Back up these files regularly to a file system that is outside the file system in which they reside. In the event of a disaster, you can restore these files from your backup copies.

Note - Sun Microsystems strongly recommends that you back up your environment's configuration files because they will be needed in the event of a file system disaster.

The following files are among those that you should back up regularly and whenever you modify them:

- `/etc/opt/SUNWsamfs/mcf`

- `/etc/opt/SUNWsamfs/LICENSE.4.2`

- `/etc/opt/SUNWsamfs/samfs.cmd`

- /etc/opt/SUNWsamfs/archiver.cmd

For more information on the files you should protect, see the Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.

##

(Optional) Configuring the Remote Notification Facility

The Sun StorEdge SAM-FS software can be configured to notify you when potential problems occur in its environment. The system sends notification messages to a management station of your choice. The Simple Management Network Protocol (SNMP) software within the software manages the exchange of information between network devices such as servers, automated libraries, and drives.

The Sun StorEdge QFS and Sun StorEdge SAM-FS Management Information Base (MIB) defines the types of problems, or events, that the Sun StorEdge QFS software can detect. The software can detect errors in configuration, `tapealert`(1M) events, and other atypical system activity. For complete information on the MIB, see `/opt/SUNWsamfs/mibs/SUN-SAM-MIB.mib`.

The following sections describe how to enable and how to disable remote notification.

### To Enable Remote Notification

1. Ensure that the management station is configured and known to be operating correctly.

(Optional) Verifying the Network Management Station describes this prerequisite.

2. Use `vi`(1) or another editor to open file `/etc/hosts`.

Examine the `/etc/hosts` file to ensure that the management station to which notifications should be sent is defined.

For example, CODE EXAMPLE 4-75 shows an `/etc/hosts` file that defines a management station. In this example, the management station's hostname is `mgmtconsole`.

CODE EXAMPLE 4-75 Example `/etc/hosts` File
    999.9.9.9       localhost
    999.999.9.999   loggerhost      loghost
    999.999.9.998   mgmtconsole
    999.999.9.9     samserver

3. Save your changes to `/etc/hosts` and exit the file.

4. Use `vi`(1) or another editor to open file `/etc/opt/SUNWsamfs/scripts/sendtrap`.

5. Locate the `TRAP_DESTINATION=`hostname`` directive in `/etc/opt/SUNWsamfs/scripts/sendtrap`.

This line specifies that the remote notification messages be sent to port 161 of the server upon which the Sun StorEdge SAM-FS software is installed. Note the following:

- If you want to change the hostname or/and port, replace the `TRAP_DESTINATION` directive line with `TRAP_DESTINATION="`management-console-name`:`port`"`. Note the use of quotation marks (`" "`) rather than apostrophes (`` ``) in the new directive.

- If you want to send remote notification messages to multiple hosts, specify the directive in the following format:

    TRAP_DESTINATION="mgmt_console_name:port [ mgmt_console_name:port]"

For example:

    TRAP_DESTINATION="localhost:161 doodle:163 mgmt_station:1162"

6. Locate the `COMMUNITY="public"` directive in `/etc/opt/SUNWsamfs/scripts/sendtrap`.

This line acts as a password. It prevents unauthorized viewing or use of SNMP trap messages. Examine this line and determine the following:

- If your management station's community string is also set to `public`, you do not have to edit this value.

- If your management station's community string is set to a value other than `public`, edit the directive and replace `public` with the value that is used in your management station.

7. Save your changes to `/etc/opt/SUNWsamfs/scripts/sendtrap` and exit the file.

### To Disable Remote Notification

The remote notification facility is enabled by default. If you want to disable remote notification, perform this procedure.

1. (Optional) Use the `cp`(1) command to copy file `/opt/SUNWsamfs/examples/defaults.conf` to `/etc/opt/SUNWsamfs/defaults.conf`.

Perform this step if file `/etc/opt/SUNWsamfs/defaults.conf` does not exist.

2. Use `vi`(1) or another editor to open file `/etc/opt/SUNWsamfs/defaults.conf`.

Find the line in `defaults.conf` that specifies SNMP alerts. The line is as follows:

    #alerts=on

3. Edit the line to disable SNMP alerts.

Remove the `#` symbol and change `on` to `off`. After editing, the line is as follows:

    alerts=off

4. Save your changes to `/etc/opt/SUNWsamfs/defaults.conf` and exit the file.

5. Use the `pkill`(1M) command to send a SIGHUP signal to the `sam-fsd`(1M) daemon.

The format for this command is as follows:

    # pkill -HUP sam-fsd

This command restarts the `sam-fsd`(1M) daemon and enables the daemon to recognize the changes in the `defaults.conf` file.

##

(Optional) Adding the Administrator Group

By default, only the superuser can execute the Sun StorEdge SAM-FS administrator commands. However, during installation you can supply an administrator group name. The `pkgadd`(1M) process prompts you for this group name during Sun StorEdge SAM-FS installation.

Members of the administrator group can execute all administrator commands except for `star`(1M), `samfsck`(1M), `samgrowfs`(1M), `sammkfs`(1M), and `samd`(1M). The administrator commands are located in `/opt/SUNWsamfs/sbin`.

You can use the `set_admin`(1M) command to add or remove the administrator group after installing the package. This action performs the same function that occurs when you select an administrator group during the package install. You must be logged in as superuser to use the `set_admin`(1M) command. You can also undo the effect of this selection and make the programs in `/opt/SUNWsamfs/sbin` executable only by the superuser. For more information on this command, see the `set_admin`(1M) man page.

### To Add the Administrator Group

1. Choose a group name or select a group that already exists within your environment.

2. Use the `groupadd`(1M) command, or edit the `/etc/group` file.

The following is an entry from the group file designating an administrator group for the Sun StorEdge SAM-FS software. In this example, the `samadm` group consists of both the `adm` and `operator` users.

    samadm::1999:adm,operator

##

Configuring System Logging

The Sun StorEdge SAM-FS systems log errors, cautions, warnings, and other messages using the standard Sun Solaris `syslog`(3) interface. By default, the Sun StorEdge SAM-FS facility is `local7`.

### To Enable Logging

1. Use vi(1) or another editor to open the `/etc/syslog.conf` file.

Read in the line from the following file:

`/opt/SUNWsamfs/examples/syslog.conf_changes`

The line is similar, if not identical, to the following line:

    local7.debug  /var/adm/sam-log

Note - The preceding entry is all one line and has a TAB character (not a space) between the fields.

This step assumes that you want to use `local7`, which is the default. If you set logging to something other than `local7` in the `/etc/syslog.conf` file, edit the `defaults.conf` file and reset it there, too. For more information, see the `defaults.conf`(4) man page.

2. Use commands to append the logging line from`/opt/SUNWsamfs/examples/syslog.conf_changes` to your `/etc/syslog.conf` file.

CODE EXAMPLE 4-76 shows the commands to use to append the logging lines.

CODE EXAMPLE 4-76 Using `cp` (1) and `cat` (1) to Append Logging Lines to `/etc/syslog.conf`
    # cp /etc/syslog.conf /etc/syslog.conf.orig
    # cat /opt/SUNWsamfs/examples/syslog.conf_changes >> /etc/syslog.conf

3. Create an empty log file and send the `syslogd` a HUP signal.

CODE EXAMPLE 4-77 shows the command sequence to create a log file in `/var/adm/sam-log` and send the HUP to `syslogd`.

CODE EXAMPLE 4-77 Creating an Empty Log File and Sending a HUP Signal to `syslogd`
    # touch /var/adm/sam-log
    # pkill -HUP syslogd

For more information, see the `syslog.conf`(4) and `syslogd`(1M) man pages.

4. (Optional) Use the `log_rotate.sh`(1M) command to enable log file rotation.

Log files can become very large, and the `log_rotate.sh`(1M) command can help in managing log files. For more information, see the `log_rotate.sh`(1M) man page.

##

(Optional) Configuring Other Sun StorEdge Products

The Sun StorEdge SAM-FS installation and configuration process is complete. You can configure other Sun StorEdge SAM-FS products at this time. For example, if you want to configure Sun SAM-Remote, see the Sun SAM-Remote Administration Guide.

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.