| Sun StorEdge SAM-FS Installation and Upgrade Guide |    
|
| Sun StorEdge SAM-FS Installation and Upgrade Guide |
|
| 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:
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.
Sun StorEdge QFS software package runs in the following operating system environments:
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.
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:
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.
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.
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.
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:
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:
The minimum hardware requirements for the File System Manager software are as follows:
Ensure that your installation meets the following browser requirements:
Make sure that one of the following minimum levels of the Solaris OS is installed on the web server:
The File System Manager installation packages include revisions of the following software at the minimum levels indicated:
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.
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.
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.
|
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:
Use the following information to estimate the metadata cache requirements. The metadata cache must have enough space to contain the following data:
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. |
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-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).
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.
|
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. |
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.
If you plan to perform disk archiving (to archive to disk space in another file system), verify the following:
If you plan to archive to removable media devices, your environment must include the following:
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:
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.
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.
At the >ok prompt, enter the following command to disable autobooting:
7. Type reset at the next prompt:
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:
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.
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:
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).
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.
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.
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:
|
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.
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.
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:
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.
| Sun StorEdge SAM-FS Installation and Upgrade Guide | 819-4330-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Verify the Environment
