| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide |    
|
| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide |
|
| C H A P T E R 5 |
|
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. Enabling the SAM-QFS Manager (Optional) describes enabling the tool and shows the configuration steps you can perform by using the tool.
For most of the procedures in this chapter, you must have root access.
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:
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.
|
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:
3. Use the pkgadd(1M) command to add the SUNWsamfsr and SUNWsamfsu packages.
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 also 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. 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:
Perform this procedure 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 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:
This task includes the following procedures:
|
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-2, do so now. For the rest of the procedures in this installation, this manual refers to TABLE 1-2 as your inventory list.
The procedures in this task include an example that assumes your inventory list is as shown in TABLE 5-1.
|
Note - The device names in TABLE 5-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:
|
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.
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.
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:
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 5-1 shows how the st.conf file looks at this point.
... 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:
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 5-2 shows the lines now contained in the st.conf file.
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:
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 5-3 shows how the st.conf file looks at this point.
... 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:
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 5-2 shows the tape drive configuration lines now contained in the st.conf file.
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 5-6 shows the st.conf file after you have added definitions for the Quantum DLT 7000, the StorageTek 9840, and the IBM ULT3580 tape drives.
17. Replace the comma (,) at the end of the last device definition line with a semicolon (;).
CODE EXAMPLE 5-6 shows the resulting st.conf file if you have multiple devices configured.
18. Save your changes and proceed to To Verify or Add a Target Device, LUN, or World Wide 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.
|
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 To Add Tape Devices to the /kernel/drv/st.conf File (Optional).
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. Use vi(1) or another editor to open file /kernel/drv/st.conf. (Optional)
If you left the file open for editing from the previous procedure (To Add Tape Devices to the /kernel/drv/st.conf File (Optional)), you do not need to perform this step.
2. Find the list of SCSI target IDs and LUNs in the st.conf file. (Optional)
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:
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 5-7 shows the two lines that correspond to those interfaces.
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. Create a line for the SCSI target and LUN that you need. (Optional)
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. Create lines for each device attached through a Fibre Channel interface. (Optional)
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:
For lun, specify the LUN for the drive.
For world-wide-name, specify the World Wide Name for drive.
For example, CODE EXAMPLE 5-8 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.
8. Save your changes and exit the st.conf file.
Proceed to To Verify or Add Device Support in the samst.conf File (Optional) if you have any of the following devices in your inventory list:
|
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.
2. Use vi(1) or another editor to open the /kernel/drv/samst.conf file.
3. Find the list of SCSI targets and LUNs in the samst.conf file. (Optional)
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:
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:
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. Create a line for the SCSI target and LUN that you need. (Optional)
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. Create lines for the first device in your inventory list that is attached through a Fibre Channel interface. (Optional)
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:
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:
9. Repeat Step 8 for each device that is attached through a Fibre Channel interface. (Optional)
10. Save your changes and exit the samst.conf file.
|
Issue a cfgadm(1M) command to verify the devices included in the Sun StorEdge SAM-FS environment.
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 5-10.
Despite the error, the cfgadm(1M) command completely processes the request.
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:
CODE EXAMPLE 5-11 shows the device log messages that correspond to the sam-log message.
The preceding messages indicate that the appropriate changes have not been made to /kernel/drv/st.conf.
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.
|
1. Create the /etc/opt/SUNWsamfs/LICENSE.4.1 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.1 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.1 file.
|
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. For users, such as superusers, who need to access the administrator commands, add /opt/SUNWsamfs/sbin to the PATH variable.
3. For users who need to access the Sun StorEdge SAM-FS man pages, add /opt/SUNWsamfs/man to the MANPATH variable.
4. 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 5-12 shows how your .profile file might look after editing.
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:
CODE EXAMPLE 5-13 shows how the MANPATH in your .login file might look like after editing.
setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\ share/man:/usr/share/man:/opt/SUNWsamfs/man |
|
Note - Failure to reboot the system at this time can cause the st and samst modules to remain unconfigured. |
|
Reboot the server by issuing the touch(1) and init(1M) commands.
CODE EXAMPLE 5-14 shows the commands to use to reboot.
Changes to the st.conf, samst.conf, and the /etc/name_to_sysnum files are enabled at this time.
Perform this step 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:
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.
|
1. Ensure that you have met the installation requirements described in Verifying Requirements for the SAM-QFS Manager (Optional).
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.
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:
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.
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:
After installing the packages, it starts the TomCat Web Server, enables logging, and creates the SAMadmin role.
7. Log into the Sun StorEdge SAM-FS server and become superuser.
8. Use the ps(1) and grep(1) commands to make sure that the rpcbind service is running.
9. Examine the output from the preceding commands.
The output should contain a line similar to the following:
If rpcbind does not appear in the output, enter the following command:
10. Start the sam-mgmtrpcd daemon. (Optional)
Perform this step if you did not elect to have this daemon started automatically.
Enter the following command to start the sam-mgmtrpcd daemon:
The system automatically restarts this daemon every time you reboot the server. If you kill this daemon, it restarts.
The syslogd daemon performs detailed tracing of the native code. For more information on tracing, see SAM-QFS Manager Software Notes.
|
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:
Only the Sun StorEdge SAM-FS adminstrator should log in using the SAMadmin role. All other users should log in as samuser.
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.
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.
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 on 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.
8. Click on Sun StorEdge SAM-QFS Manager 1.0.
You are now logged into the SAM-QFS Manager.
|
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 on Help, in the upper right corner of the screen, to access the SAM-QFS Manager online documentation.
2. Configure your parameters file for network-attached libraries. (Optional)
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 Creating Parameters Files for Network-Attached Automated Libraries (Optional).
3. Complete the configuration tasks.
Perform the configuration tasks in TABLE 5-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 5-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.
|
Creating Parameters Files for Network-Attached Automated Libraries (Optional) |
||
|
Defining the Sun StorEdge SAM-FS Configuration by Creating the mcf File |
||
TABLE 5-2 describes several installation steps as optional. The only required installation steps that you still must perform using Solaris OS commands are as follows:
The other installation steps in TABLE 5-2 are necessary -- or are highly recommended-- depending on your environment. For example, if you have network-attached automated libraries, you must perform Populating the Catalog (Optional). Read through the documentation for the tasks described in the preceding list and decide which steps you need to perform.
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:
|
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.
|
|
When you create the mcf file, follow these guidelines:
CODE EXAMPLE 5-15 shows the mcf file fields.
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:
TABLE 5-3 shows the information to be contained in each field and whether or not the field is a required or optional field.
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 5-16 shows, each SCSI peripheral has three lines. Note that the third line wraps to the next line in CODE EXAMPLE 5-16 and that the sixth field, samst2, indicates that these lines are associated with each other.
|
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.
Assume that the following equipment is to be included in a Sun StorEdge SAM-FS configuration:
This equipment is connected to three SCSI buses with the following SCSI targets:
CODE EXAMPLE 5-17 shows the output from the Sun Solaris format(1M) command. It reports how the disks are partitioned.
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.
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 5-18 shows the mcf with the file systems defined.
The HP Model C1716T is target ID 2 on the internal SCSI bus.
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE 5-19 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.
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:
The preceding ls(1) command searches for a symbolic link that points to the hardware path shown in CODE EXAMPLE 5-20.
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:
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).
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.
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE 5-21 shows these messages.
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 5-22 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 5-21.
# 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 5-23 shows the mcf file entries.
/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).
When configuring DLT drives, be sure to add the DLT definitions to the /kernel/drv/st.conf file (see Verifying and Updating the st.conf and samst.conf Files (Optional)). DLT drives are not part of the standard Sun Solaris configuration, and the software does not recognize them if they are configured incorrectly.
1. Examine the /var/adm/messages file to find the messages for these devices.
CODE EXAMPLE 5-24 shows the /var/adm/messages file lines that refer to the manual DLT drive.
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 5-25 shows the ls(1) and grep(1) commands to use to locate the DLT drive identified as scsi@5.
# 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 5-26 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.
3. Use vi(1) or another editor to open the /etc/opt/SUNWsamfs/mcf file.
4. Add the /etc/opt/SUNWsamfs/mcf entry.
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.
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.
1. Examine the /var/adm/messages to find the messages for these devices.
CODE EXAMPLE 5-27 shows the /var/adm/messages file.
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 5-28 shows the ls(1) and grep(1) commands to use to locate the symbolic links.
# 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 5-29 that the automated library does not have this additional link.
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 5-30 shows the mcf file entries for this 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. Add the DLT definitions to the /kernel/drv/st.conf file. (Optional)
Perform this step if you are configuring DLT drives.
Verifying and Updating the st.conf and samst.conf Files (Optional) shows how to add definitions to the /kernel/drv/st.conf file. DLT drives are not part of the standard Sun Solaris configuration.
TABLE 5-7 shows the completed mcf file.
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 Creating Parameters Files for Network-Attached Automated Libraries (Optional).
Example 1. CODE EXAMPLE 5-31 shows the mcf file for an ADIC/Grau network-attached automated library.
Example 2. CODE EXAMPLE 5-32 shows the mcf file for a Fujitsu LMF network-attached automated library.
Example 3. CODE EXAMPLE 5-33 shows the mcf file for an IBM 3494 network-attached automated library.
Example 4. CODE EXAMPLE 5-34 shows the mcf file for a Sony network-attached automated library.
Example 5. CODE EXAMPLE 5-35 shows the mcf file for a StorageTek ACSLS-attached automated library.
For more information, see the mcf(4) man page. There are example mcf files located in /opt/SUNWsamfs/examples/mcf.
Perform this step 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:
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. |
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.
|
|
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:
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:
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:
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 5-36 and CODE EXAMPLE 5-37 define one ADIC/Grau automated library supporting DLT tape and one ADIC/Grau automated library supporting a Hewlett Packard optical drive.
CODE EXAMPLE 5-36 shows the parameters file for library grau50.
CODE EXAMPLE 5-37 shows the parameters file for grau60.
5. Repeat this procedure and create a parameters file for each ADIC/Grau library that you want to configure.
CODE EXAMPLE 5-31 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.
The following directory contains diagnostic information that can be useful when troubleshooting:
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.
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.
|
|
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:
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:
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 5-8 shows the values you can specify for drivename and value.
|
The path to the drive. This path must match the Equipment Identifier field of the mcf file. |
CODE EXAMPLE 5-38 shows a parameters file for a Fujitsu LMF automated library.
5. Repeat this procedure and create a parameters file for each Fujitsu LMF library that you want to configure.
CODE EXAMPLE 5-32 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.
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.
|
|
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:
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:
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 5-9 shows how to specify the parameters.
|
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. |
|
|
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. |
|
|
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 5-39 shows an example /etc/ibmatl.conf file. Information for this file was obtained from the mtlib utility supplied by IBM.
# # 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 5-40 shows output from mtlib.
# mtlib -l 3493a -D 0, 00145340 003590B1A00 1, 00145350 003590B1A01 |
CODE EXAMPLE 5-41 shows a sample parameters file and mcf entries for an IBM 3494 library.
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 5-33 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.
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.
|
|
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:
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:
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 5-10 shows the keyword = value parameters that must appear in the Sony parameters file. All parameters are required.
|
For user-id, specify a number in the range 0 |
|
|
For server_id specify the host name of the server running the PSC server code. |
|
|
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 5-42 shows the parameters file, /etc/opt/SUNWsamfs/sonyfile.
5. Repeat this procedure and create a parameters file for each Sony network-attached library that you want to configure.
CODE EXAMPLE 5-34 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.
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.
|
|
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:
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:
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 5-11 shows the keywords to use.
|
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. |
|
|
Specifies the host name of the server. For hostname, enter the host name of the server running the StorageTek ACSLS interface. |
|
|
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. |
|
|
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. |
|
|
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 |
|
|
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. |
|
|
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 5-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 5-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 5-12 shows the capacity defaults.
TABLE 5-13 shows the value specifications.
CODE EXAMPLE 5-43 shows a parameters file for a StorageTek ACSLS-attached automated library:
5. Repeat this procedure and create a parameters file for each ACSLS-attached library that you want to configure.
CODE EXAMPLE 5-35 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.
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:
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.
Use the samd(1M) config command to initialize the Sun StorEdge SAM-FS environment.
Perform this step 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:
|
This procedure has two main phases:
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.
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.
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.
|
1. Use the samd(1M) start commaned to start the software.
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:
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:
TABLE 5-14 shows the arguments for these commands.
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:
For x, specify the raw tape device entry as specified in the mcf file.
CODE EXAMPLE 5-45 shows mt(1) command output that indicates that a tape is in the 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.
|
1. Use the samd(1M) start command to start the software.
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:
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:
TABLE 5-14 shows the arguments for these commands.
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:
For device_path, specify the samst device entry as specified in the mcf file.
CODE EXAMPLE 5-46 shows a status message that indicates that an optical catridge is in the selected device:
# dd if=/dev/samst/c0t3u0 bs=2k iseek=3374 of=/tmp/junk count=10 10+0 records in 10+0 records out |
CODE EXAMPLE 5-47 shows a status message that indicates that an optical catridge is not in the selected device:
# 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 5-47, 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.
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:
|
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:
Certain directives are typically specified globally and others are typically specified only for individual file systems.
CODE EXAMPLE 5-48 shows a simple archiver.cmd file.
CODE EXAMPLE 5-48 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 5-51 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.
5. Correct any errors in the archiver.cmd file before proceeding to the next task in this installation and configuration procedure.
This section shows some of the recommended archiver.cmd file directives.
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.
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.
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 5-49 shows, the vsns and endvsns directives surround the VSN identifiers.
You can accomplish the goal of creating archive copies on two different types of media by using reserved VSNs.
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.
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:
CODE EXAMPLE 5-50 shows archive set assignment directives that assign files to archive sets audiofiles and xrayfiles.
xrayfiles medical/radiology/rochester/xrays audiofiles net/home/cleveland/audio |
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:
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.
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.
CODE EXAMPLE 5-48 shows a simple archiver.cmd file. CODE EXAMPLE 5-51 shows a more advanced archiver.cmd file.
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:
|
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 Creating the archiver.cmd File (Optional), you reopen the file in this step.
3. Edit the archiver.cmd file to add disk archive set directives.
CODE EXAMPLE 5-52 shows a fragment from an archiver.cmd file that defines disk archive sets.
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.
CODE EXAMPLE 5-53 shows an example diskvols.conf file:
CODE EXAMPLE 5-53 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 5-53 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 5-16 shows the information that must appear in this file.
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:
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 5-54 shows the commands to create the directories to which archive copies will be written.
# 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.
The preceding command verifies the archiver.cmd file syntax for errors. If any are found, correct them before proceeding.
|
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:
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.
3. Create directories in the file system to which the archive copies will be written.
CODE EXAMPLE 5-55 shows the commands to create the directories to which archive copies will be written.
# 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.
# This is # file destination_server:/etc/opt/SUNWsamfs/diskvols.conf # on the server # clients sourceserver endclients |
5. Save and close the diskvols.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 5-57 shows lines from an example defaults.conf file. This file shows several parameters that can affect the configuration of an automated library.
Another sample file is located in /opt/SUNWsamfs/examples/defaults.conf.
|
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.
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.
This command restarts the sam-fsd(1M) daemon and enables the daemon to recognize the changes in the defaults.conf(4) file.
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.
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 5-17.
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.
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:
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:
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.
At this point in the installation and configuration process, the following files exist on your Sun StorEdge SAM-FS server:
The procedures in this task show you how to verify the correctness of these configuration files.
|
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 5-58, return to Enabling the Sun StorEdge SAM-FS Software License.
|
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 5-59.
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.
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:
The odlabel(1M) command has the following format:
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:
Example 2. The following command labels one side of an optical disk:
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:
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.
Perform this step 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:
|
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. |
|
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:
CODE EXAMPLE 5-60 shows 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:
For example, you can specify the following build_cat(1M) command:
For more information on the build_cat(1M) command, see the build_cat(1M) man page.
|
1. Use the import(1M) command to import catalog entries into the default catalog.
The syntax for the import(1M) command is as follows:
In the preceding import(1M) command, note the following:
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.
|
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. |
|
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.
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 5-61 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.
Example 2. Assume that you receive two sets of error messages. CODE EXAMPLE 5-62 shows the first set.
The following is the second set:
CODE EXAMPLE 5-63 shows the samu(1M) utility's :r display.
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 5-64 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.
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.
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:
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.
|
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.
The example in this procedure assumes that /samfs1 is the mount point of the samfs1 file system.
|
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 5-65 shows header fields and entries for a Sun StorEdge SAM-FS file system.
TABLE 5-20 shows the various fields in the /etc/vfstab file and their content.
2. Use the mkdir(1M) command to create the mount point.
This procedure shows how to use the sammkfs(1M) command and the Family Set names that you have defined to initialize a file system.
|
Use the sammkfs(1M) command to initialize a file system for each Family Set name defined in the mcf file.
CODE EXAMPLE 5-66 shows the command to initialize a file system with the Family Set name of samfs1.
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. |
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.
|
1. Issue the mount(1M) command to mount the file system.
Specify the file system mount point as the argument. For example:
2. Issue 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 5-67 shows the output from a mount(1M) command issued to verify whether example file system samfs1 is mounted.
3. Issue the chmod(1) and chown(1) commands to change the permissions and ownership of the file system's root directory. (Optional)
If this is the first time the file system has been mounted, it is typical to perform this step. CODE EXAMPLE 5-68 shows the commands to use to change file system permissions and ownership.
# chmod 755 /samfs1 # chown root:other /samfs1 |
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.
|
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:
2. Use the ps(1) command to determine whether or not nfs.server is running.
CODE EXAMPLE 5-69 shows these commands and their output.
In CODE EXAMPLE 5-69, the lines that contain /usr/lib/nfs indicate that the NFS server is mounted.
3. Start the NFS server. (Optional)
Perform this step if nfs.server is not running.
4. Type the share(1M) command at a root shell prompt. (Optional)
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 5-70 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.
# 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:
For more information on these parameters, see the mount_nfs(1M) man page.
Perform this task if you have shared the file system with NFS client systems.
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:
In this example, server:/samfs1 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.
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.
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:
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.
|
1. Make an entry in the root user's crontab file so the cron daemon runs the samfsdump(1M) command periodically.
CODE EXAMPLE 5-71 shows a cron(1) entry.
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. Using the previous step as a guide, make similar crontab entries for each file system. (Optional)
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.
|
1. Use the cd(1) command to go to the directory that contains the mount point for the file system.
In this example, samfs1 is a Sun StorEdge SAM-FS mount point.
2. Issue the samfsdump(1M) command.
The following command writes the output to a file system outside of the one you are dumping:
In this example, dump.file is the newly created dump structure.
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:
For more information on the files you should protect, see the Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.
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.
|
1. Ensure that the management station is configured and known to be operating correctly.
Verifying the Network Management Station (Optional) 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 5-72 shows an /etc/hosts file that defines a management station. In this example, the management station's hostname is mgmtconsole.
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 /opt/SUNWsamfs/sbin/sendtrap.
5. Locate the TRAP_DESTINATION=`hostname` directive in /opt/SUNWsamfs/sbin/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:
6. Locate the COMMUNITY="public" directive in /etc/opt/SUNWsamfs/sbin/sendtrap.
This line acts as a password. It prevents unauthorized viewing or use of SNMP trap messages. Examine this line and determine the following:
7. Save your changes to /etc/opt/SUNWsamfs/sbin/sendtrap and exit the file.
|
The remote notification facility is enabled by default. If you want to disable remote notification, perform this procedure.
1. Use the cp(1) command to copy file /opt/SUNWsamfs/examples/defaults.conf to /etc/opt/SUNWsamfs/defaults.conf. (Optional)
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:
3. Edit the line to disable SNMP alerts.
Remove the # symbol and change on to off. After editing, the line is as follows:
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:
This command restarts the sam-fsd(1M) daemon and enables the daemon to recognize the changes in the defaults.conf file.
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.
|
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.
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.
|
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:
|
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 5-73 shows the commands to use to append the logging lines.
3. Create an empty log file and send the syslogd a HUP signal.
CODE EXAMPLE 5-74 shows the command sequence to create a log file in /var/adm/sam-log and send the HUP to syslogd.
# touch /var/adm/sam-log # pkill -HUP syslogd |
For more information, see the syslog.conf(4) and syslogd(1M) man pages.
4. Use the log_rotate.sh(1M) command to enable log file rotation. (Optional)
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.
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.
| Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide | 817-4092-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
To Add the Packages
