C H A P T E R 2

Pre-installation Tasks

This chapter explains the system requirements for the Sun StorEdge SAM-FS software and the tasks you must complete before you begin to install and configure your software.

This chapter contains the following sections:

- Hardware and Software Requirements

- Determining Disk Space Requirements

- Obtaining the Release Files

- Setting Up the Network Management Station

##

Hardware and Software Requirements

The Sun StorEdge SAM-FS software can be installed either on a Sun server based on UltraSPARC® technology or on a server based on AMD Opteron x64 technology.

If you plan to install the File System Manager browser interface tool, there are additional requirements for the server that you want to use as the web server host. For more information about these requirements, see Verifying Requirements for File System Manager.

The Sun StorEdge SAM-FS software package runs on many Sun workstations and servers. Before installation, you should verify the compatibility of the hardware, the level of the Solaris Operating System (OS), and the patch release installed. To install the Sun StorEdge SAM-FS software, you also must ensure that you have root-level access to your system.

### Operating System Requirements

Sun StorEdge QFS software package runs in the following operating system environments:

- Solaris 9 04/03 or later

- Solaris 10

Before installation, you should verify the applicability of the hardware, the level of the operating system, and the patch release installed. To install the Sun StorEdge SAM-FS software, you also must ensure that you have root-level access to your system.

Note - The Sun StorEdge SAM-FS software always supports the two most recent versions of the Solaris OS. When a new version of the Solaris OS is released, Sun StorEdge SAM-FS adds support of the new version and drops support of the oldest version. The only exception to this policy occurs when the new Solaris OS version is released right near the time of the Sun StorEdge SAM-FS software release. In this case, three Solaris OS versions may be supported temporarily until the next Sun StorEdge SAM-FS software release.

To Verify the Environment

Repeat these steps for each host on which you want to install the Sun StorEdge SAM-FS software.

1. Verify that your system has a CD-ROM drive or that it can access the release package at the Sun Download Center.

The Sun Download Center is at the following URL:

`http://www.sun.com/software/downloads`

2. Log in to your system as root.

You must have superuser access to install the software.

3. Verify your system's Solaris OS level.

The software relies on properly configured Solaris software at one of the following minimum release levels:

- Solaris 9 4/03

- Solaris 10

### Installing Solaris OS Patches

Sun Microsystems provides Solaris OS patches to customers with a maintenance contract by means of CD-ROM, anonymous FTP, and the Sun Microsystems SunSolve web site (`http://sunsolve.sun.com`).

To install a patch after you install the Sun StorEdge SAM-FS release packages, load the CD-ROM or transfer the patch software to your system. Follow the instructions outlined in the Patch Installation Instructions and Special Install Instructions in the README file included in the patch or jumbo patch cluster.

### Sun StorEdge SAM-FS Software Host Requirements

If you plan to install the Sun StorEdge SAM-FS software in a multihost environment, for example in a Sun SAM-Remote configuration, all host systems must have the same Sun StorEdge SAM-FS software release level installed and operational. Hosts can be running different releases of the Solaris OS, but make sure that the same patch collection for the applicable release is installed on all hosts with the release that you want to include in the configuration.

### Verifying Third-Party Compatibilities

The Sun StorEdge SAM-FS software interoperates with many different hardware and software products from third-party vendors. Depending on your environment, you might need to upgrade other software or firmware before installing or upgrading the Sun StorEdge SAM-FS package. Consult the Sun StorEdge QFS and Sun StorEdge SAM-FS 4.5 Release Notes for information pertaining to library model numbers, firmware levels, and other compatibility information.

### Verifying Requirements for File System Manager

Perform this verification if you want to use File System Manager browser interface to configure, control, monitor, or reconfigure a Sun StorEdge SAM-FS environment through a web server.

You can install the File System Manager software in one of the following configurations:

- As a standalone management station to manage one or more Sun StorEdge SAM-FS hosts.

- As additional software on the Sun StorEdge SAM-FS host.

After the File System Manager software is installed, you can invoke File System Manager from any machine on the network that is allowed access to its web server.

If you plan to use File System Manager, the host upon which you are configuring the File System Manager software must meet the requirements described in the following subsections:

- Hardware Requirements

- Browser Requirements

- Operating System Requirements

- Web Software Requirements

#### Hardware Requirements

The minimum hardware requirements for the File System Manager software are as follows:

- SPARC 400 MHz (or more) or x64 AMD CPU

- 1 gigabyte of memory

- One 20-gigabyte disk

- At least 250 Mbytes free space in `/tmp`

- At least 100 Mbytes free space in `/` (the root partition)

- One 10/100/1000Base-T Ethernet port

#### Browser Requirements

Ensure that your installation meets the following browser requirements:

- One of the following browsers, at the minimum level indicated, must be installed on the web server:

- Netscape 7.x / Mozilla 1.4 on the Solaris OS or Microsoft Windows 98, SE, ME, 2000 or XP operating system

- Internet Explorer 6.0 on Microsoft Windows 98, SE, ME, 2000, or XP operating system

- You must enable JavaScript technology in your browser. In Mozilla, for example, click through the following menus to get to a panel showing whether JavaScript technology is enabled: `Edit`, `Preferences`, `Advanced`, and `Scripts & Plugins`.

- You must clear the browser cache before using File System Manager for the first time if you are upgrading from an earlier version.

#### Operating System Requirements

Make sure that one of the following minimum levels of the Solaris OS is installed on the web server:

- Solaris 9 4/03

- Solaris 10

#### Web Software Requirements

The File System Manager installation packages include revisions of the following software at the minimum levels indicated:

- Java 2 Standard Edition version 1.4.2

- JavaHelp 2.0

- JATO 2.1.2

- Tomcat version 4.0.5

During the installation procedure, you will be asked to answer questions. Based on your answers, the installation software can install the correct revisions for you if the compatible revisions of these software packages are not present.

Note - File System Manger is registered in the Sun Java Web Console and can co-exist with other applications that use the same console. The Java Web Console uses port 6789. This is an IANA reserved port, so no application other than Java Web Console should use this port.

##

Determining Disk Space Requirements

The Sun StorEdge SAM-FS software package requires a certain amount of disk cache (file system devices) in order for it to create and manage data files and directories.

The Sun StorEdge SAM-FS file system requires only a single partition. If Sun StorEdge QFS is also installed, the file system requires either one or two partitions. The Sun StorEdge QFS file system is described in the Sun StorEdge QFS Installation and Upgrade Guide. See that manual for Sun StorEdge QFS disk space requirements.

The disk devices or partitions do not require any special formatting. You might see better performance if you configure multiple devices across multiple interfaces (HBAs) and disk controllers.

| Caution - Make sure that the disks and partitions that you plan to use are not currently in use and do not contain any existing data. Any existing data will be lost when you create the Sun StorEdge SAM-FS file system.

The disks must be connected to the server through a Fibre Channel (FC) or SCSI controller. You can specify individual disk partitions for a disk, or you can use the entire disk as a disk cache. The software supports disk arrays, including those under the control of volume management software, such as Solstice DiskSuite, Solaris Volume Manager, and other volume management software products.

### To Estimate Disk Cache Requirements

1. Estimate the minimum disk cache requirements for Sun StorEdge SAM-FS software (file systems plus the storage and archive manager).

Use the following guidelines to estimate the disk cache needed for Sun StorEdge SAM-FS file systems:

- Disk cache = largest file (in bytes) + amount of space needed for working files

- Metadata cache

Use the following information to estimate the metadata cache requirements. The metadata cache must have enough space to contain the following data:

- Two copies of the superblock (16 Kbytes each)

- Reservation maps for metadata space plus data space
  ((metadata + file data)/DAU/32,000) * 4 Kbytes

- Inode space
  (number of files + number of directories) * 512 bytes

- Indirect blocks - a minimum of 16 Kbytes each

- Directory data space
  (number of directories * 16 Kbytes)

2. Enter the `format`(1M) command to verify that you have sufficient disk cache space.

The `format`(1M) command shows how the disks are partitioned and the size of each partition.

Note - EFI labels are required on all shared disks if you are using a Sun StorEdge QFS shared file system configuration that contains both the Solaris 10 OS on x64 platforms and the Solaris 9 or Solaris 10 OS on SPARC platforms. See Configuring EFI Labels for Shared x64 and SPARC Volumes for information on relabeling disks.

### Example 1 - Using the `format`(1M) Command on Fibre-Channel-Attached Disks

CODE EXAMPLE 2-1 shows six disks attached to a server. There are two internal disks connected by means of controller 0 on targets 10 and 11 (`c0t10d0` and `c0t11d0`). The other disks are external.

For the sake of clarity, the `format`(1M) command output in CODE EXAMPLE 2-1 has been edited.

CODE EXAMPLE 2-1 `format` (1M) Command for Fibre-Channel-Attached Disks
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
           0. c0t10d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
              /sbus@3,0/SUNW,fas@3,8800000/sd@a,0
           1. c0t11d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
              /sbus@3,0/SUNW,fas@3,8800000/sd@b,0
           2. c9t60020F2000003A4C3ED20F150000DB7Ad0 <SUN-T300-0118 cyl 34530 alt 2 h
    d 48 sec 128>
              /scsi_vhci/ssd@g60020f2000003a4c3ed20f150000db7a
           3. c9t60020F2000003A4C3ED215D60001CF52d0 <SUN-T300-0118 cyl 34530 alt 2 h
    d 48 sec 128>
              /scsi_vhci/ssd@g60020f2000003a4c3ed215d60001cf52
           4. c9t60020F2000003A4C3ED21628000EE5A6d0 <SUN-T300-0118 cyl 34530 alt 2 h
    d 48 sec 128>
              /scsi_vhci/ssd@g60020f2000003a4c3ed21628000ee5a6
           5. c9t60020F2000003A4C3ED216500009D48Ad0 <SUN-T300-0118 cyl 34530 alt 2 h
    d 48 sec 128>
              /scsi_vhci/ssd@g60020f2000003a4c3ed216500009d48a
    Specify disk (enter its number):^d
    #
    # format /dev/rdsk/c9t60020F2000003A4C3ED216500009D48Ad0s2
    # format f
    partition> p
    Part      Tag    Flag     Cylinders         Size            Blocks
      0 unassigned    wm       0 -  4778       14.00GB    (4779/0/0)   29362176
      1 unassigned    wm    4779 -  9557       14.00GB    (4779/0/0)   29362176
      2     backup    wu       0 - 34529      101.16GB    (34530/0/0) 212152320
      3 unassigned    wm    9558 - 14336       14.00GB    (4779/0/0)   29362176
      4 unassigned    wm   14337 - 19115       14.00GB    (4779/0/0)   29362176
      5 unassigned    wm   19116 - 23894       14.00GB    (4779/0/0)   29362176
      6 unassigned    wm   23895 - 28673       14.00GB    (4779/0/0)   29362176
      7 unassigned    wm   28674 - 33452       14.00GB    (4779/0/0)   29362176
    partition> ^D
    #

### Example 2 - Using the `format`(1M) Command on SCSI-Attached Disks

CODE EXAMPLE 2-2 shows four disks attached to a server. There are two internal disks connected by means of controller `0` on targets `0` (`c0t0d0`) and `1` (`c0t1d0`). There are two external disks connected by means of controller `3` on targets `0` (`c3t0d0`) and `2` (`c3t2d0`).

CODE EXAMPLE 2-2 `format` (1M) Command for SCSI-Attached Disks
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
           0. c0t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
              /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0
           1. c0t1d0 <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
              /sbus@1f,0/SUNW,fas@e,8800000/sd@1,0
           2. c3t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
              /sbus@1f,0/QLGC,isp@0,10000/sd@0,0
           3. c3t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
              /sbus@1f,0/QLGC,isp@0,10000/sd@2,0
    Specify disk (enter its number): 1
    selecting c0t1d0
    [disk formatted]
    Warning: Current Disk has mounted partitions.
    FORMAT MENU:
            disk       - select a disk
            type       - select (define) a disk type
            partition  - select (define) a partition table
            current    - describe the current disk
            format     - format and analyze the disk
            repair     - repair a defective sector
            label      - write label to the disk
            analyze    - surface analysis
            defect     - defect list management
            backup     - search for backup labels
            verify     - read and display labels
            save       - save new disk/partition definitions
            inquiry    - show vendor, product and revision
            volname    - set 8-character volume name
            !<cmd>     - execute <cmd>, then return
            quit
    format> par
    PARTITION MENU:
            0      - change `0' partition
            1      - change `1' partition
            2      - change `2' partition
            3      - change `3' partition
            4      - change `4' partition
            5      - change `5' partition
            6      - change `6' partition
            7      - change `7' partition
            select - select a predefined table
            modify - modify a predefined partition table
            name   - name the current table
            print  - display the current table
            label  - write partition map and label to the disk
            !<cmd> - execute <cmd>, then return
            quit
    partition> pri
    Current partition table (original):
    Total disk cylinders available: 2733 + 2 (reserved cylinders)
    Part      Tag    Flag     Cylinders        Size            Blocks
      0        var    wm       0 - 2732        1.98GB    (2733/0/0) 4154160
      1 unassigned    wm       0               0         (0/0/0)          0
      2     backup    wm       0 - 2732        1.98GB    (2733/0/0) 4154160
      3 unassigned    wm       0               0         (0/0/0)          0
      4 unassigned    wm       0               0         (0/0/0)          0
      5 unassigned    wm       0               0         (0/0/0)          0
      6 unassigned    wm       0               0         (0/0/0)          0
      7 unassigned    wm       0               0         (0/0/0)          0
    partition> q

### Verifying Disk Space

The software requires a disk cache consisting of RAID devices, JBOD devices, or both. It also requires a certain amount of disk space in the `/` (root), `/opt`, and `/var` directories. The actual amount needed varies depending on the packages you install. TABLE 2-1 shows the minimum amount of disk space required in these various directories.

TABLE 2-1 Minimum Disk Space Requirements
Directory | Sun StorEdge SAM-FS | File System Manager
--- | --- | ---
`/` (root) directory | 2 Mbytes | 25 Mbytes
`/opt` directory | 21 Mbytes | 5 Mbytes
`/var` directory | 6 Mbytes | 2 Mbytes
`/usr` directory | 2 Mbytes | 7 Mbytes
`/tmp` directory | 0 Kbytes | 200 Mbytes

Note - The space requirements for the `/var` directory take into account the fact that the archiver data directory, the archiver queue files, and the log files are written to the `/var` directory.

To Verify Disk Space

The following procedure shows how to verify whether there is enough disk space on your system to accommodate the `SUNWsamfsu` and `SUNWsamfsr` software packages.

1. Enter the following command to verify that there are at least 2 Mbytes available in the `avail` column for the `/` directory.

    # df -k /
    Filesystem        kbytes  used    avail capacity   Mounted on
    /dev/dsk/c0t1dos0 76767   19826   49271    29%     /

2. Enter the following command to verify that there are at least 21 Mbytes in the `avail` column for the `/opt` directory.

    # df -k /opt
    Filesystem        kbytes  used    avail capacity   Mounted on
    /dev/dsk/c0t1dos4 192423  59006  114177    35%     /opt

3. Verify that there are at least 6 Mbytes available in the `/var` directory.

A quantity of 30 Mbytes or more is recommended to allow for the growth of log files and other system files.

4. If there is not enough room for the software under each directory, repartition the disk to make more space available to each file system.

To repartition a disk, see your Sun Solaris system administration documentation.

### Verifying Archive Media

If you plan to perform disk archiving (to archive to disk space in another file system), verify the following:

- That the host system to which the disks are attached has at least one file system created on it that is compatible with the Sun StorEdge SAM-FS software.

- That there is enough space available on the disk to accommodate the archive copies.

If you plan to archive to removable media devices, your environment must include the following:

- At least one removable media device for archiving files. This device can be a single tape or optical drive, or it can be multiple devices, such as the drives within an automated library.

- Tape or magneto-optical cartridges to which archive files can be written. For most SCSI-attached and FC-attached libraries, the Sun StorEdge SAM-FS software supports only one media type. If you have a tape library that can be partitioned logically into two or more libraries, you can have one media type in one logical library and a different media type in another. The Sun StorEdge SAM-FS software records the cartridges used for each library in a library catalog. You cannot mix the tape media types in a library catalog, so plan to use only one media type per library or logical library.

The Sun StorEdge SAM-FS environment supports a wide variety of removable media devices. You can obtain a list of currently supported drives and libraries from your Sun Microsystems sales or support staff. To make sure that your devices are attached and enumerated in an easily retrieved list, perform one or both of the following procedures:

- If your removable media devices are not attached to your server, perform the procedure in To Attach Removable Media Devices.

- Enumerate your devices using the instructions in To Create a List of Devices. You will use this list again in the Installing the Software Packages.

To Attach Removable Media Devices

The following steps are general guidelines for attaching removable media hardware to a server. For explicit instructions on connecting these peripherals to a server, refer to the hardware installation guide supplied by the vendor with the automated library and drives.

1. Ensure that you are on a console connection to the server.

2. Power off the server.

3. Ensure that the removable media devices and the disks to be used for the Sun StorEdge SAM-FS file system are connected and properly addressed.

4. If you have libraries attached to the host system through a SCSI interface, ensure that the SCSI target IDs are unique for each SCSI initiator (host adapter).

Avoid setting SCSI target IDs for peripherals to already used IDs. In addition, if you are using a SCSI host adapter with a previously attached disk drive, any additional peripheral connected to this bus must have a different ID. Typically, the initiator uses ID `7`, and the internal disk drive uses ID 3 for SPARC systems and ID 0 for UltraSPARC systems.

5. Power on the peripherals according to the manufacturer's recommended sequence.

Typically, you power on the outermost peripherals first, working toward more central components in sequence.

6. Disable autobooting.

At the `>ok` prompt, enter the following command to disable autobooting:

    >ok setenv auto-boot? false

7. Type `reset` at the next prompt:

    >ok reset

8. Do one of the following:

- If you have libraries attached to the host system through a SCSI interface, use the `probe-scsi-all` command to conduct an inventory of target IDs and LUNs for each device connected to the host system. Save the output. You will use the information in this output for the next procedure, To Create a List of Devices.

For example:

    {0} ok probe-scsi-all
    /pci@6,400/scsi@2,1
    Target 0
      Unit 0   Removable Device type 8     STK 9730        1700
    Target 1
      Unit 0   Removable Tape   type 7     QUANTUM DLT7000 2565
    Target 2
      Unit 0   Removable Tape   type 7     QUANTUM DLT7000 2565
    /pci@1f,4000/scsi@3
    Target 0
      Unit 0   Disk     SEAGATE ST318404LSUN18G 4207
    Target 6
      Unit 0   Removable Read Only device   TOSHIBA XM6201TASUN32XCD1103

- If you have libraries or tape drives attached to the host system through an FC interface, conduct an inventory of target IDs and LUNs for each device connected to the host system. Save the output. You will use the information in this output for the next procedure, To Create a List of Devices.

For example:

    {0} ok show-devs
    /SUNW,ffb@1e,0
    /SUNW,UltraSPARC-II@2,0
    /SUNW,UltraSPARC-II@0,0
    /counter-timer@1f,1c00
    /pci@1f,2000
    /pci@1f,4000
    /virtual-memory
    /memory@0,a0000000
    /aliases
    /options
    /openprom
    /chosen
    /packages
    /pci@1f,2000/SUNW,qlc@1
    /pci@1f,2000/SUNW,qlc@1/fp@0,0
    /pci@1f,2000/SUNW,qlc@1/fp@0,0/disk
    /pci@1f,4000/SUNW,ifp@2
    /pci@1f,4000/scsi@3,1
    /pci@1f,4000/scsi@3
    /pci@1f,4000/network@1,1
    /pci@1f,4000/ebus@1
    /pci@1f,4000/SUNW,ifp@2/ses
    {0} ok select /pci@1f,2000/SUNW,qlc@1
    {0} ok show-children
    LiD HA LUN  --- Port WWN ---  ----- Disk description -----
     2  7e   0  500104f00041182b  STK     L700            0236
    7c  7e   0  500104f00043abfc  STK     9840            1.28
    7d  7e   0  500104f00045eeaf  STK     9840            1.28
    6f  7e   0  500104f000416304  IBM     ULT3580-TD1     16E0
    6e  7e   0  500104f000416303  IBM     ULT3580-TD1     16E0

If the server does not acknowledge all the known devices (disk drives, tape or optical drives, the automated library, and so on), check the cabling. Do not proceed until all devices appear when probed.

9. Reenable autobooting, and then boot the system:

    >ok setenv auto-boot? true
    >ok boot

10. Review system files.

Review the following files:

- `/var/adm/messages` to ensure that all devices were recognized

- `/dev/rmt` for expected tape devices

- `/dev/dsk` and `/dev/rdsk` for expected disks

Due to special driver requirements, no device information appears in `/var/adm/messages` for magneto-optical devices or libraries until after you install the Sun StorEdge SAM-FS software packages.

11. Disable autocleaning and autoloading.

If your automated library supports autocleaning or autoloading, disable those features when using that library with the Sun StorEdge SAM-FS software. Consult the documentation from your library's manufacturer for information on disabling autocleaning and autoloading.

Note - The only times you can use autoloading are during the initial loading of cartridges and when the Sun StorEdge SAM-FS software is not running. Remember to disable autoloading when the Sun StorEdge SAM-FS system is running.

### Creating a List of Devices

The devices that you intend to use must be attached and recognized by the server upon which you intend to install the Sun StorEdge SAM-FS software. To configure the Sun StorEdge SAM-FS software, you need to know the following about your devices:

- The device type, manufacturer, and model number.

- The mechanism by which the device is attached to the server. You can attach devices in one of the following ways:

- Drives can use either a SCSI attachment or an FC attachment. Each drive accepts either tape cartridges or magneto-optical cartridges.

For SCSI-attached drives, you need to know each drive's SCSI target ID and logical unit number (LUN).

For FC-attached drives, you need to know each drive's LUN and node World Wide Name (WWN).

- Automated libraries can use a SCSI attachment, an FC attachment, or a network attachment.

Libraries that use SCSI or FC attachments are called direct attached libraries. For SCSI-attached libraries, you need to know each library's SCSI target ID and LUN. For FC-attached libraries, you need to know each library's LUN and node WWN.

Libraries that use a network attachment are called network attached libraries. You cannot configure network attached libraries in the existing system configuration files; instead, you must create a parameters file for each network attached library. This is explained later in the installation process.

To Create a List of Devices

Fill in TABLE 2-2 to include the name, manufacturer, model, and connection types for each device that you want to include in your Sun StorEdge SAM-FS environment. Retain this list for use again later in the configuration procedure.

TABLE 2-2 Devices to Be Configured
Device Name, Manufacturer, and Model | Target ID | LUN | Node WWN
--- | --- | --- | ---
SCSI-attached tape drives |  |  |
|  |  | Not applicable
|  |  | Not applicable
|  |  | Not applicable
FC-attached tape drives |  |  |
| Not applicable |  |
| Not applicable |  |
| Not applicable |  |
SCSI-attached magneto-optical drives |  |  |
|  |  | Not applicable
|  |  | Not applicable
|  |  | Not applicable
FC-attached magneto-optical drives |  |  |
| Not applicable |  |
| Not applicable |  |
| Not applicable |  |
SCSI-attached automated libraries |  |  |
|  |  | Not applicable
|  |  | Not applicable
|  |  | Not applicable
FC-attached automated libraries |  |  |
| Not applicable |  |
| Not applicable |  |
| Not applicable |  |

##

Obtaining the Release Files

Make sure that you have a copy of the release software. You can obtain the Sun StorEdge SAM-FS software from the Sun Download Center or on a CD-ROM. Contact your authorized service provider (ASP) or your Sun sales representative if you have questions on obtaining the software.

After the release, upgrade patches are available from the following URL:

`http://sunsolve.sun.com`

| Caution - If you have not read the Sun StorEdge QFS and Sun StorEdge SAM-FS 4.5 Release Notes, please do so before continuing. You can access the Sun StorEdge QFS and Sun StorEdge SAM-FS 4.5 Release Notesfor this release at any time from one of the documentation web sites described in this manual's preface.

### To Obtain the Software From the Sun Download Center

1. Enter the following URL in your browser:

`http://www.sun.com/software/download/sys_admin.html`

2. Click the Sun StorEdge SAM-FS software package you want to receive.

3. Follow the instructions on the web site for downloading the software.

### Software Licensing

You must agree to all binary and right-to-use (RTU) software license agreements before installing Sun StorEdge SAM-FS software. Beginning with version 4, update 3, of the software, all media kits and software license options are delivered online, and license keys are no longer required.

##

Setting Up the Network Management Station

Perform this procedure if you want to monitor your configuration through Simple Network Management Protocol (SNMP) software.

You can configure the Sun StorEdge SAM-FS software to notify you when potential problems occur in its environment. The SNMP software manages information exchange between network devices such as servers, automated libraries, and drives. When the Sun StorEdge SAM-FS software detects potential problems in its environment, it sends information to a management station, which enables you to monitor the system remotely.

The management stations you can use include the following:

- Sun Storage Automated Diagnostic Environment (StorADE)

- Sun Management Center (Sun MC)

- Sun Remote Server (SRS)

- Sun Remote Services Net Connect

If you want to enable SNMP traps, make sure that the management station software is installed and operating correctly before installing the Sun StorEdge SAM-FS software. Refer to the documentation that came with your management station software for information on installation and use.

The types of problems, or events, that the Sun StorEdge SAM-FS software can detect are defined in the Sun StorEdge SAM-FS Management Information Base (MIB). The events include 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` after the packages are installed.

The Sun StorEdge SAM-FS software supports the TRAP SNMP (V2c) protocol. The software does not support `GET-REQUEST`, `GETNEXT-REQUEST`, and `SET_REQUEST`.

Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.