A P P E N D I X A - SAM-QFS Manager Software Notes

A P P E N D I X A

SAM-QFS Manager Software Notes

This appendix section contains additional information on using the SAM-QFS Manager. It includes the following topics:

Creating Additional Administrator and User Accounts

Removing the SAM-QFS Manager Software

Messages

Log and Trace Files

Management Software Remote Procedure Call (RPC) Daemon Information

Creating Additional Administrator and User Accounts

You can create additional administrator and guest accounts at any time after the initial SAM-QFS Manager configuration. These guest accounts are local to the management station.

Aftering installing the Sun StorEdge SAM-QFS Manager, it creates the following two Solaris operating system (OS) login accounts and the following role:

Accounts: samadmin, samuser

Role: SAMadmin

The user account samadmin is assigned the SAMadmin role. This user has administrator privileges (read and write) for managing the SAM-QFS Manager, the Sun StorEdge QFS software, and the Sun StorEdge SAM-FS software.

The user account samuser is assigned only Guest privileges. This user has read-only access to Sun StorEdge QFS and Sun StorEdge SAM-FS operations.

If you remove the SAM-QFS Manager software, the system removes both the samadmin and samuser Solaris accounts and the SAMadmin role. However, the removal scripts do not remove any additional accounts that you create manually. It is your responsibility to use one or both of the following procedures to administer any accounts you add manually.

To Create Additional Administrator Accounts

An administrator account holder has administrator priviledges (read and write) for managing the SAM-QFS Manager, the Sun StorEdge QFS software, and the Sun StorEdge SAM-FS software.

1. Log into the management station.

2. Type useradd username.

3. Type passwd username.

4. Type in the password as instructed on the screen.

5. Type usermod -R SAMadmin username.

Note - Do not use root as the username.

To Create Additional Guest Accounts

A guest account holder has read-only access to Sun StorEdge QFS and Sun StorEdge SAM-FS operations.

1. Log into the management station.

2. Type useradd account_name.

3. Type passwd account_name.

4. Type in the password as instructed on the screen.

Removing the SAM-QFS Manager Software

The following procedures describe how to remove the SAM-QFS Manager software from a Sun StorEdge QFS or Sun StorEdge SAM-FS environment. The following procedure shows you how to remove the SAM-QFS Manager software from the Sun StorEdge QFS or Sun StorEdge SAM-FS server.

To Remove the SAM-QFS Manager Software from the Sun StorEdge QFS or Sun StorEdge SAM-FS Server

1. Log into the server upon which the SAM-QFS Manager software is installed.

This is the host upon which you ran the samqfsmgr_setup script at installation time.

2. Become superuser.

3. Remove the SAM-QFS Manager software.

To remove all the applications that are installed with the SAM-QFS Manager software, type the following command:

# /var/sadm/samqfsui/samqfsmgr_uninstall

This script asks you to confirm removal of the TomCat Web Server and JRE packages.

Messages

This section shows some of the messages you might see when using the SAM-QFS Manager software.

Message:

An unrecoverable error occurred during the page display.If the problem persists, please restart the web server.

Click the HOME button to return to the Server Selection page, which is the default page of the SAM-QFS Manager 1.0 Application.

If the system cannot display the Server Selection page, enter the following command to restart the Web Server:

# /usr/sbin/smcwebserver restart

Message:

HTTP 500 Internal server error

Run the following command to restart the Web Server:

# /usr/sbin/smcwebserver restart

Message:

The page cannot be displayed.

Run the following command to restart the Web Server:

# /usr/sbin/smcwebserver restart

Message:

Starting Sun(TM) Web Console Version 2.0.2.Startup failed. See /var/log/webconsole/console_debug_log for detailed error information.

Examine the contents of the following file:

/var/log/webconsole/console_debug_log

If the log says the port(6789) is in use by some other process, type commands shown in CODE EXAMPLE A-1.

CODE EXAMPLE A-1 Restarting the Web Console
# `pkill -9 noaccess` # `/usr/sbin/smcwebserver restart`

Message:

Failed to create the filesystemmount_samfs: fopen(mnttab) error: : Too many open files

The system generates this message if you are trying to create a file system with a large number of LUNs. To remedy this problem, use the following procedure:

1. Use the ps(1) and grep(1) commands to find the process ID for the sam-mgmtrpcd process.

For example:

# ps -ef | grep sam-mgmtrpcd

2. Use the plimit(1) command to increase the descriptors for the process.

For example:

# plimit -n 512 process-id

For process-id, specify the process number.

3. Create the file system.

Log and Trace Files

The SAM-QFS Manager software enables logging after it is installed, but if you want tracing, you have to enable it manually. You do not need to create or modify any logging or tracing files for the SAM-QFS Manager software unless you want to enable logging for native code. Log rotation is not supported for log or trace files.

TABLE A-1 lists the files that the SAM-QFS Manager uses for logging and tracing.

TABLE A-1 SAM-QFS Manager Log and Trace Files
Activity	File Location	Created by the User?
SAM-QFS Manager Logging	`/var/log/webconsole/samqfsui.log`	No
TomCat Web Console Logging	`/var/log/webconsole/console_debug_log`	No
Logging for native code	`/var/log/webconsole/samqfsui.trace_syslog`	Yes
Stack trace file	/var/log/webconsole/localhost_log.yyyy-mm-dd.txt	No
Tracing	`/var/webconsole/samqfsui.trace_`mmdd`_`time	No

The following sections describe the log and trace files.

SAM-QFS Manager Logging

The SAM-QFS Manager software creates the samqfsui.log log file when the application starts. It records information about operations that the user performs, and whether those operations were successful. Do not delete or modify this file. If you delete or modify this file, logging stops. When the webserver restarts, it erases the contents of this file and creates a new samqfsui.log file.

The SAM-QFS Manager software uses an additional file, /var/webconsole/samqfsui.log.lck, to ensure that only one process at a time writes to the log file. Do not delete or modify this lock file.

TomCat Web Server Logging

The Sun Common Console Framework creates the /var/webconsole/console_debug_log file. It includes console-specific information such as environment variable setting that the console uses and a record of users logged into the console.

If this file becomes too large, you can delete this file. The system creates another instance of this file the next time the web server restarts.

Tracing

The SAM-QFS Manager trace file records the following information:

Messages regarding whether operations were successful.

Functions invoked with the application stack. This can be verbose.

Messages that are important to developers for debugging purposes.

Tracing is not enabled by default. Use the the following command to enable tracing or to adjust the tracing level:

# /opt/SUNWsamqfsui/bin/ui_tracelevel trace_level

For trace_level, specify one of the values shown in TABLE A-2.

TABLE A-2 Arguments for *trace_level*
trace_level	Tracing Requested
`off`	Disables tracing.
1	Enables tracing for very important messages only. This includes severe errors that occur within the application.
2	Enables tracing for moderately important messages. This includes level 1 messages as well as debugging statements within the application that are useful for developers.
3	Enables tracing for all messages. This includes level 1 and level 2 messages as well as entry and exit points of functions within the application on the stack.

The ui_tracelevel command creates the trace file. The trace file's name includes date and time extensions that indicate the date and time that the web server started. For example, trace file samqfsui.trace_0317_1838 is the name of the trace file created when the web server was restarted on March 17 at 6:38 PM. Do not delete this file until a different instance of a web server (for example, a web server that restarted after 6:38 PM) is running.

You can enable and disable tracing dynamically during run time by using the ui_tracelevel script.

To Enable Logging and Tracing for SAM-QFS Manager Native Code

The syslog daemon performs detailed tracing of the native code. Use the following procedure to enable detailed tracing of native code.

1. Use the touch(1) command to create the trace file.

For example:

# touch /var/log/webconsole/samqfsui.trace_syslog

2. Use vi(1) or another editor to add the following line to the /etc/syslog.conf file:

local6.debug   /var/log/webconsole/samqfsui.trace_syslog

Use a tab character to separate the two fields in this line.

3. Type the following command:

# pkill -HUP syslogd

4. Enable log file rotation. (Optional)

Log files can become very large. Use logadm(1M) to manage the log file for the SAM-QFS Manager.

Note - You cannot use the log_rotate.sh(1M) script to manage the log file for the SAM-QFS Manager.

Management Software Remote Procedure Call (RPC) Daemon Information

The following procedure provides troubleshooting information for the RPC daemon, sam-mgmtrpcd(1M).

To Determine Whether the RPC Daemon is Running

Perform the following procedure to verify whether or not the RPC daemon is running.

1. Log in to the Sun StorEdge QFS or Sun StorEdge SAM-FS server.

2. Become superuser.

3. Type the ps(1) command and examine the output.

For example:

# ps -ef | grep rpc

In the ps(1) output, if you see a line with sam-mgmtrpcd(1M) in it, then the RPC daemon is up and running.

If the output shows that the RPC daemon is not running, type the following commands to start the RPC daemon and the web server:

# /opt/SUNWsamfs/sbin/sam-mgmtrpcd