| 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 3 |
|
Sun StorEdge QFS Initial Installation Procedure |
This chapter describes the procedure for installing and configuring Sun StorEdge QFS standalone software for the first time. Use this procedure if this is the initial installation of the Sun StorEdge QFS standalone software package at your site. If you are upgrading Sun StorEdge QFS software on an existing server, see the Sun StorEdge QFS Upgrade Procedure.
The procedure in this chapter describes obtaining the packages, installing the software packages on your server or node, and configuring the software to match the hardware at your site.
You can install and configure your Sun StorEdge QFS file system entirely using Solaris operating system (OS) commands, or you can use a combination of commands and the 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.
You must be logged in as superuser to complete most of the procedures in this chapter.
The chapter called System Requirements and Preinstallation Tasks describes the items you need to verify before you install and configure the Sun StorEdge QFS 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 QFS 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 SUNWqfsr and SUNWqfsu packages.
4. Enter yes or y as the answer to each of the questions.
You need a license key to run the Sun StorEdge QFS software. For information on obtaining license keys, see Obtaining a Software License Key.
The Sun StorEdge QFS file system uses an encrypted license key. The license key consists of an encoded alphanumeric string.
|
1. Create the /etc/opt/SUNWsamfs/LICENSE.4.1 file.
2. Starting in column one, place the license key you have obtained from your ASP or from Sun Microsystems on the first line 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 QFS 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 QFS 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 3-1 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 3-2 shows how the MANPATH in your .login file might after you are finished editing.
setenv MANPATH /usr/local/man:opt/SUNWspro/man:/$OPENWINHOME/\ share/man:/usr/share/man:/opt/SUNWsamfs/man |
|
Reboot the server by issuing the touch(1) and init(1M) commands.
CODE EXAMPLE 3-3 shows the commands to use to reboot.
Changes to the /etc/name_to_sysnum file 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 QFS 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 install requirements 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 QFS 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 QFS 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 OS 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 QFS 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. Complete the configuration tasks.
TABLE 3-1 shows the rest of the steps you must perform to install and configure a Sun StorEdge QFS file system and the means by which you can accomplish each task.
Perform the configuration steps in TABLE 3-1 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.
|
Defining the Sun StorEdge QFS Configuration by Creating the mcf File |
||
|
Mounting the File System on the NFS Client Systems (Optional) |
||
TABLE 3-1 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 3-1 are necessary -- or are highly recommended-- depending on your environment.
Each Sun StorEdge QFS environment is unique. The system requirements and hardware used differ from site to site. It is up to you, the system administrator at your site, to set up the specific configuration for your Sun StorEdge QFS environment.
The master configuration file, /etc/opt/SUNWsamfs/mcf, defines the topology of the equipment managed by the Sun StorEdge QFS file system. This file specifies the devices and file systems included in the environment. You assign each piece of equipment a unique Equipment Identifier in the mcf file.
To configure Sun StorEdge QFS devices, create an mcf file in /etc/opt/SUNWsamfs/mcf that contains a line for each device and family set in your configuration. The mcf contains information that enables you to identify the disk slices to be used and to organize them into Sun StorEdge QFS file systems.
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. |
The following section describe activities related to creating and maintaining the mcf file:
|
Note - The instructions for creating the mcf file differ depending on whether you are creating a Sun StorEdge QFS environment or a Sun SAM-QFS environment.
|
|
When you create the mcf file, follow these guidelines:
CODE EXAMPLE 3-4 shows the fields of each line entry in the mcf file.
TABLE 3-2 shows the information to be contained in each field and whether or not the field is a required or optional field.
For more information on this file, see the mcf(4) man page. There is an example of an mcf file located in /opt/SUNWsamfs/examples/mcf.
CODE EXAMPLE 3-5 shows file system entries in an mcf file for a Sun StorEdge QFS file system.
Depending on the type of storage you specify, a file system installed on a node in a Sun Cluster environment has the potential to be local, global, or highly available. Writing an mcf file for a local or global Sun StorEdge QFS file system on a Sun Cluster node is no different from writing any other kind of mcf file, but the disk devices behave differently depending on how you specify them in the Equipment Identifier field. This section explains what to specify in the Equipment Identifier field.
The characteristics of local, global, and highly available file systems are as follows:
If you are creating a Sun StorEdge QFS file system as a local or global file system in a Sun Cluster environment, use the information in TABLE 3-3 when writing the Equipment Identifier field for a local or global file system in a Sun Cluster. TABLE 3-3 contains information on the kinds of disks that can be used to configure a Sun StorEdge QFS file system.
|
Global devices are accessible from all nodes in a Sun Cluster, even if these devices are not physically attached to all nodes. |
|
|
Note - For more information on using Sun StorEdge QFS file systems in a Sun Cluster environment, see the README file or see the Sun StorEdge QFS and Sun StorEdge SAM-FS 4.1 Release Notes. |
The following configuration examples are for a local Sun StorEdge QFS file system installed in a Sun Solaris OS.
This example shows how to configure two Sun StorEdge QFS file systems using a server that has a Sun StorEdge Multipack desktop array connected by a SCSI attachment.
You can use the format(1M) command to determine how the disks are partitioned. CODE EXAMPLE 3-6 shows the format(1M) command's output.
Begin writing the mcf file for this configuration example by defining the file system and its disk partitions, as follows:
a. Make an ma entry for the first file system.
b. Make an mm entry listing the partition(s) that comprise the metadata for the qfs1 file system.
c. Make a series of mr entries listing the partitions that comprise the file data for the qfs1 file system.
d. Make similar entries for the second (qfs2) file system.
The finished mcf file defines the following two file systems:
CODE EXAMPLE 3-7 shows the resulting mcf file.
|
Note - Modifying the /etc/vfstab file is a later step in this chapter's configuration procedure. This step shows the /etc/vfstab file modifications only for completeness' sake. |
2. Modify the /etc/vfstab file.
Make entries in the /etc/vfstab file for the qfs1 and qfs2 file systems you defined in the mcf file. The last two lines in CODE EXAMPLE 3-8 show entries for these new file systems.
|
Note - Modifying the /etc/vfstab file is a later step in this chapter's configuration procedure. This step shows the /etc/vfstab file modifications only for completeness' sake. |
This example illustrates a Sun StorEdge QFS file system that uses round-robin allocation on four disk drives.
This example assumes the following:
This example introduces the round-robin data layout. For more information on data layout, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.
CODE EXAMPLE 3-9 shows the mcf file for this round-robin disk configuration.
|
Note - Modifying the /etc/vfstab file and using the sammkfs(1M) command are later steps in this chapter's configuration procedure. This step shows these steps only for completeness' sake. |
2. Modify the /etc/vfstab file.
Edit the /etc/vfstab file to explicitly set round-robin on the file system by specifying stripe=0 in the mount params field. CODE EXAMPLE 3-10 shows stripe=0 for the qfs3 file system.
3. Run the sammkfs(1M) command.
Initialize the Sun StorEdge QFS file system by using the sammkfs(1M) command. The default DAU is 64 kilobytes, but the following example sets the DAU size to 128 kilobytes:
This example illustrates a Sun StorEdge QFS file system. It stripes file data to four disk drives. This example assumes the following:
Write the mcf file using the disk configuration assumptions. CODE EXAMPLE 3-11 shows a sample mcf file for a striped disk configuration.
|
Note - Modifying the /etc/vfstab file and using the sammkfs(1M) command are later steps in this chapter's configuration procedure. This step shows these steps only for completeness' sake. |
2. Modify the /etc/vfstab file.
Set the stripe width by using the stripe= option. CODE EXAMPLE 3-12 shows the /etc/vfstab file with a mount parameter of stripe=1 set for the qfs4 file system.
The stripe=1 specification stripes file data across all four of the mr data disks with a stripe width of one disk allocation unit (DAU). Note that the DAU is the allocation unit you set when you use the sammkfs(1M) command to initialize the file system.
3. Run the sammkfs(1M) command.
Initialize the Sun StorEdge QFS file system by using the sammkfs(1M) command. The following example sets the DAU size to 128 kilobytes:
With this striped disk configuration, any file written to this file system is striped across all of the devices in increments of 128 kilobytes. Files less than the aggregate stripe width times the number of devices still use 128 kilobytes of disk space. Files larger than 128 kilobytes have space allocated for them as needed in total space increments of 128 kilobytes. The file system writes metadata to device 41 only.
Striped groups allow you to group RAID devices together for very large files. With striped groups, however, there is only one DAU per striped group. This method of writing huge DAUs across RAID devices saves system update time. Striped groups are useful for writing very large files to a group of RAID devices.
The devices within a striped group must be the same size. It is not possible to increase the size of a striped group. You can add additional striped groups to the file system, however.
This example configuration illustrates a Sun StorEdge QFS file system that separates the metadata onto a low-latency disk. The mcf file defines two striped groups on four drives. This example assumes the following:
Write the mcf file by using the disk configuration assumptions. CODE EXAMPLE 3-13 shows a sample mcf file for a striped group configuration.
|
Note - Modifying the /etc/vfstab file and using the sammkfs(1M) command are later steps in this chapter's configuration procedure. This procedure shows these steps only for completeness' sake. |
2. Modify the /etc/vfstab file.
Use the the stripe= option to set the stripe width. CODE EXAMPLE 3-14 shows the /etc/vfstab file with a mount parameter of stripe=0, which specifies a round-robin allocation from striped group g0 to striped group g1.
3. Run the sammkfs(1M) command.
Initialize the Sun StorEdge QFS file system by using the sammkfs(1M) command. The -a option is not used with striped groups because the DAU is equal to the size of an allocation, or the size, of each group.
In this example, there are two striped groups, g0 and g1. With stripe=0 in /etc/vfstab, devices 12 and 13 are striped; devices 14 and 15 are striped; and files are round robined around the two striped groups. You are actually treating a striped group as a bound entity. After you configure a stripe group, you cannot change it without issuing another sammkfs(1M) command.
|
Type the samd(1M) config command to initialize the Sun StorEdge QFS environment.
The /opt/SUNWsamfs/examples/defaults.conf file contains default settings for the Sun StorEdge QFS environment. You can change these settings at any time after the initial installation. To determine if you want to change any default settings now, examine the defaults.conf(4) man page to discern the types of behaviors this file controls.
|
1. Read the defaults.conf(4) man page and examine this file to determine if you want to change any of the defaults.
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 file.
At this point in the installation and configuration process, the following files exist on your Sun StorEdge QFS server:
This procedure shows 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 3-15, return to Enabling the Sun StorEdge QFS Software License.
|
Enter the sam-fsd(1M) command to verify the mcf file.
Examine the output for errors, as follows:
If your mcf file has errors, refer to Defining the Sun StorEdge QFS Configuration by Creating the mcf File and to the mcf(4) man page for information on how to create this file correctly.
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 QFS systems with multiple mount parameters, consider creating this file.
You can specify mount parameters in the following ways:
You can manage certain features more easily from a samfs.cmd file. These features include the following:
For more information on 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.
CODE EXAMPLE 3-17 shows a samfs.cmd file for a Sun StorEdge QFS file system.
The example in this procedure assumes that /qfs1 is the mount point of the qfs1 file system.
|
1. Use vi(1) or another editor to open the /etc/vfstab file and create an entry for each Sun StorEdge QFS file system.
CODE EXAMPLE 3-18 shows header fields and entries for a local Sun StorEdge QFS file system.
TABLE 3-4 shows the various fields in the /etc/vfstab file and their contents.
2. Use the mkdir(1) command to create the file system mount point.
The mount point location differs depending on where the file system is to be mounted, as follows:
The following examples illustrate this.
Example 1. This example assumes that /qfs1 is the mount point of the qfs1 file system. This is a local file system. It can exist on a standalone server or on a local node in a Sun Cluster. For example:
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 defined in the mcf file.
CODE EXAMPLE 3-19 shows the command to use to initialize a file system with the Family Set name of qfs1.
Enter y in response to this message to continue the file system creation process.
The mount(1M) command mounts a file system. It also reads the /etc/vfstab and samfs.cmd configuration files. 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 3-20 shows the output from a mount(1M) command issued to verify whether example file system qfs1 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 3-21 shows the commands to use to change file system permissions and ownership.
# chmod 755 /qfs1 # chown root:other /qfs1 |
Perform this procedure if you want a local Sun StorEdge QFS 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 QFS file system:
2. Use the ps(1) and grep(1) commands to determine whether or not nfs.server is running.
CODE EXAMPLE 3-22 shows these commands and their output.
In CODE EXAMPLE 3-22, the lines that contain /usr/lib/nfs indicate that the NFS server is mounted.
3. Start the NFS server. (Optional)
Perform this step if the nfs.server server is not running. Use the following command:
4. Type the share(1M) command at a root shell prompt. (Optional)
Perform this step if you want to NFS share the new Sun StorEdge QFS 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 3-23 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 - /qfs1 - "QFS" |
Some NFS mount parameters can affect the performance of an NFS mounted Sun StorEdge QFS 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 procedure if you have shared the file system with NFS client systems.
On the client systems, mount the server's Sun StorEdge QFS 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 QFS file system at a convenient mount point.
The following example line mounts server:/qfs1 on the /qfs1 mount point:
In this example, server:/qfs1 is mounted on /qfs1, and information is entered into the /etc/vfstab file.
2. Save and close the /etc/vfstab file.
3. Enter the mount(1M) command.
The following mount(1M) command mounts the qfs1 file system:
The automounter can also do this, if you prefer. Follow your site procedures for adding server:/qfs1 to your automounter maps. For more information on automounting, see the automountd(1M) man page.
File systems are made up of directories, files, and links. The Sun StorEdge QFS file system keeps track of all the files in the .inodes file. The .inodes file resides on a separate metadata device. The file system writes all file data to the data devices.
It is important to use the qfsdump(1M) command periodically to create a dump file of metadata and file data. The qfsdump(1M) command saves the relative path information for each file contained in a complete file system or in a portion of a file system. This protects your data in the event of a disaster.
Create dump files at least once a day. The frequency depends on your site's requirements. By dumping file system data on a regular basis, you can restore old files and file systems. You can also move files and file systems from one server to another.
The following are some guidelines for creating dump files:
You can run the qfsdump(1M) command manually or automatically. Even if you implement this command to be run automatically, you might need to run it manually from time to time depending on your site's circumstances. In the event of a disaster, you can use the qfsrestore(1M) command to recreate your file system. You can also restore a single directory or file. For more information, see the qfsdump(1M) man page and see the Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide.
For more information on creating dump files, see the qfsdump(1M) man page. The following sections describe procedures for issuing this command both manually and automatically.
|
1. Make an entry in root's crontab file so that the cron daemon runs the qfsdump(1M) command periodically.
This entry executes the qfsdump(1M) command at 10 minutes after midnight. It uses the cd(1) command to change to the mount point of the qfs1 file system, and it executes the /opt/SUNWsamfs/sbin/qfsdump command to write the data to tape device /dev/rmt/0cbn.
2. Using the previous step as a guide, make similar crontab file entries for each file system. (Optional)
Perform this step if you have more than one Sun StorEdge QFS file system.
Make sure you save each dump file in a separate file.
|
1. Use the cd(1) command to go to the directory that contains the mount point for the file system.
2. Create a dump file by issuing the qfsdump(1M) command and writing the output to a file system outside of the one you are dumping.
Sun StorEdge QFS regularly accesses several files that have been created as part of this installation and configuration procedure. You should 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 QFS 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 examine file /etc/hosts.
For example, CODE EXAMPLE 3-24 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 |
Examine the /etc/hosts file to ensure that the management station to which notifications should be sent is defined. If it is not defined, add a line that defines the appropriate host.
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 QFS 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 Sun StorEdge QFS administrator commands. However, during installation you can create an administrator group. 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.
After installing the package, you can use the set_admin(1M) command to add or remove the administrator group. 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 an administrator 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 /etc/group file that designates an administrator group for the Sun StorEdge QFS software. In this example, the samadm group consists of both the adm and operator users.
The Sun StorEdge QFS system logs errors, cautions, warnings, and other messages using the standard Sun Solaris syslog(3) interface. By default, the Sun StorEdge QFS 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 3-25 shows the commands to use to append the logging lines.
3. Create an empty log file and send the syslogd process a HUP signal.
CODE EXAMPLE 3-26 shows the command sequence to create a log file in /var/adm/sam-log and send the HUP to the syslogd daemon.
# 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 QFS installation and configuration process is complete. You can configure other Sun StorEdge QFS products at this time. For example, if you want to configure a Sun StorEdge QFS shared file system, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System 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 Enable the Sun StorEdge QFS Software License
