A P P E N D I X F |
Installation Troubleshooting |
This appendix provides information related to installation problems and removing the software from the server:
TABLE F-1 describes potential issues that could occur during installation of Sun Storage Common Array Manager.
CAM version mismatch alarm is generated when customers register the different platform types. Example alarm scenario:
Description: Revision mismatch between data host and management host. The data host agent is at version 6.7.0.13 but the management station is at version 6.7.0.12 Probable Cause: A data host agent is running a version of the Sun Storage Common Array Manager software that is different from the management host. |
|
Using an invalid array password might result in configuration error messages. |
|
Description: Install fails when MegaRAID/MegaCLI is present since both use the same library location. Workaround: Install on MegaCLI version 8.00.23 and MSM 8.00-05 or older, available at: http://www.lsi.com/support/sun/sg_x_sas6-r-int-z.html |
|
Installation fails due to missing TEMP--Windows platforms only |
Windows users should investigate TEMP, TMP, and USERPROFILE environment variable settings, rather than follow the directions in the pop-up window. |
Installation fails when user account control is On--Windows 2008 |
Description: Users with Administrative privileges who install Sun Storage Common Array Manager on Windows 2008 must have User Account Control turned off. Workaround: From the Control Panel, select User Accounts, and then turn the User Account Control OFF. |
Upgrading from version 6.2.0.15: arrays must be removed/re-registered |
After upgrading Sun Storage Common Array Manager software on Windows, manually restart fms on Windows using the following commands. |
Description: Communication lost with Win2k8 SP2 remote data host after OS reboot. |
|
Stop all applications that are running a java.exe or javaw.exe before running the uninstaller. |
|
Application support data files cannot be saved using Windows 2008 R2 SP1 servers. |
Support data for an array is collected and saved in the Common Array Manager by selecting array > General Configuration > Support Data. On the Windows 2008 server, disable “Do not save encrypted pages to disk.” Go to Tools > Internet Options > Advanced > Security and uncheck "Do not save encrypted pages to disk." |
Description: Linux kernel:mptbase(Abort) occurs when SATA drives are added or removed. This issue has been discovered on both RedHat 5.2 and SuSE 10. Adding or removing SATA drives to a Linux host yields the following message: kernel: mptsas: ioc2: removing sata device: fw_channel 0, fw_id 4, phy 4, sas_addr 0x500163600010a390 kernel: mptbase: ioc1: LogInfo(0x31120101): Originator={PL}, Code={Abort}, SubCode(0x0101) The following message is also common: multipathd: sdd: checker msg is “tur checker reports path is down” Normally the (kernel: mptsas) messages are seen for zoning operations but when the (kernel:mptbase) message is also seen, only a reboot will recover the hosts’ ability to properly see the drives. |
|
Do not use SMTP required authentication for email notification. To learn how to disable authentication in Sendmail in Red Hat Enterprise Linux 4, go to: |
|
Sun Storage J4000 and F5100 Flash arrays--Linux hot plug issues |
Two categories of J4x00/F5100 hot plug issues have been identified: |
The dependency boot sequence LSB comment for “Require-Stop” is missing in the /etc/init.d jexec script. This generates warnings when an administrator installs other unrelated products such as RPMS, HBA management applications, and failover RDAC packages. |
|
After invalid password is entered on SUSE11, login ceases to work even when valid password is provided |
Close the browser, then open it again and log in using the correct password. |
|
|
|
|
Generally, the workaround is to reboot the array between any cable changes. |
|
Error--”no execute access to opt/SMgr/agent/notifysmagent.sh”--occurs during system boot-up |
Description: This error occurs when /opt(SMagent install directory) is built on a disk partition other than root partition. Though event notification is lost as a result, there are no adverse effects because the SMagent detects the disk device(UTM volume) during re-scan. The notifysmagent.sh script should be available to the syseventd since the script is located in the same directory of SMagent startup script. |
Solaris runtime and RAID array proxy agent packages install on wrong architectures |
Description: If you perform installation using the incorrect package, Sun Storage Common Array Manager installs but does not run. For example, if the in-band proxy agent packages are being delivered as architecture-dependent (SPARC and x86 for Solaris), then the SPARC package installation should not succeed on an x86 platform. The risk of this happening is low. Workaround: Install the correct package. See the Sun Storage Common Array Manager Software Installation and Setup Guide for instructions. |
Solaris Target Port Group Support (TPGS) is not a supported host type at this time. Do not select this host type until Solaris provides the necessary support. |
|
Upgrading Solaris to version 10 or higher might disable Oracle Java Web Console connections |
After performing the upgrade, open port 6789 for incoming connections: Check current status of port 6789: Typical output is: *.6789 *.* 0 0 49152 0 LISTEN # svccfg -s svc:/system/webconsole setprop options/tcp_listen = true |
UTM LUNs Controlled by “Solaris Traffic Manager”--6000/2500 arrays |
Description: After you upgrade to S10U3 (or later), the in-band management UTM LUNs are controlled by Solaris Traffic Manager (MPxIO). In most cases, in-band management will not fail as a result of this; however, it is best practice to ensure that the UTM LUNs are not controlled by MPxIO. Workaround: Use the format inquire command to get the eight-character Vendor (VID) and Product IDs. Follow this procedure: The following line should read: device-type-scsi-options-list = “SUN Universal Xport”, “disable-option”; disable-option = 0x7000000 Respond to the prompts as follows: WARNING: This operation will require a reboot. Do you want to continue? [y/n] (default: y) y The changes will result when the system is rebooted. Reboot the system now? [y/n] (default: y) y |
You can verify the success of the installation or problems that might have occurred during installation by reviewing the installation logs. Note that the installation logs are mainly intended for debugging by developers. By scrolling to the end of the installation log, you can verify the successful installation message or any error messages.
1. Review the requirements in Verify System Requirements.
2. Review the Readme.txt file located in the installation directory (see the Sun Storage Common Array Manager) for late-breaking information, and attempt a reinstallation.
3. Consult the installation logs.
4. Verify that you made the firewall changes after you finished the installation.
1. Log into the CAM CLI by entering the following command:
% sscs login -h cam-hostname -u username
cam-hostname is the management host machine where you installed the software.
username is one of the users defined in the management host software. See Adding Users And Assigning Roles.
3. Review the installation logs as noted in Reviewing the Installation Logs.
If you need to remove Sun Storage Common Array Manager from your system, there are wizards and scripts to uninstall the software for Solaris OS, Linux, and Windows platforms.
1. Log in to the management host as root.
2. Change to the bin directory in the installation directory for the appropriate OS (see TABLE 2-3).
cd /var/opt/CommonArrayManager/Host_Software_6.x.x.x/bin
5. From the Review Selections window, select the software to be uninstalled, and click the Uninstall button.
When the uninstall completes, the View Results screen is displayed.
1. Log in to the management host as root.
2. Change to the bin directory in the installation directory for the appropriate OS (see TABLE 2-3).
cd /var/opt/CommonArrayManager/Host_Software_6.x.x.x/bin
3. Execute the uninstall command
4. Follow the prompts in the install console dialog.
If for any reason the uninstall failed, run the uninstall script with the -f option:
6. From the Review Selections window, select the software to be uninstalled, and click the Uninstall button.
When the uninstall completes, the View Results screen is displayed.
Note - Before you uninstall Sun Storage Common Array Manager from a Windows platform, stop all applications that are running a java.exe or javaw.exe process. |
1. Navigate to the bin directory:
<system drive>:\Sun\CommonArrayManager\Host_Software_6.x.x.x\bin
2. Click the uninstall.bat icon.
To run the uninstaller in console mode, enter: uninstall.bat -c
To clean up (remove all associated files), enter: uninstall.bat -f
Alternatively, you can remove the software using the Control Panel - Add/Remove Programs.
3. Follow the uninstall wizard steps as described in the Uninstalling on Solaris OS or Linux Using the Uninstall GUI.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved.