Datahost RevisionDeltaEvent Mismatch alarm

CAM version mismatch alarm is generated when customers register the different platform types.

Example alarm scenario:
Linux - CAM Management Host 6.7.0.12
Patched Windows - CAM proxy data host 6.7.0.13

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.

General Password Mismatch error

Using an invalid array password might result in configuration error messages.

Workaround: Use the correct array password.

Installation fails when MegaRAID / MegaCLI is present

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

Windows platforms

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.

C:\sc stop Sun_STK_FMS

C:\sc start Sun_STK_FMS

Windows proxy does not run after reboot

Description: Communication lost with Win2k8 SP2 remote data host after OS reboot.

Workaround: Re-execute proxycfg.bat enable.

Uninstaller-stop applications before running--Windows only

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."

Linux platforms

Adding or removing SATA drives requires host boot

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.

Workaround: Reboot host.

Email notification not working on RH4

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:

http://kbase.redhat.com/faq/docs/DOC-4113

Sun Storage J4000 and F5100 Flash arrays--Linux hot plug issues

Two categories of J4x00/F5100 hot plug issues have been identified:

• Those that require a Linux host reboot.
• Those in which the hot plug is not supported.

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.

Add the following line in /etc/init.d/jexec:

# Required-Stop: $local_fs

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.

Issues that require a Linux host reboot:

• The array or any of its components are not recognized after changes such as cable re-configurations, firmware upgrades
• StorageTek SAS RAID HBA hot plug is not supported.
• Sun StorageTek SAS RAID HBA is inconsistent with reports and missing FRU disk information. This is expected J4x00 registration behavior during SAS bus re-scan.
• Firmware upgrade failed for Sun Blade 6000 Disk Module.
• J4x00--Name issues during registration and upgrade connected to B0/B1 side.
• J4x00--Linux J4x00 registration sg_map -i must be clear of all errors or it fails; leads to host reboot to clear sg_map.
• Newly added or removed targets (i.e. disks) due to changes in Access Configuration, cable re-configuration, firmware upgrades, or the addition of new storage can potentially cause the host to hang or panic due to known Linux kernel issues.

• After Linux hot plug, the JBOD is no longer monitored by the management software.
• J4200/J4400: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SuSE 9 SP4: Multipath (device mapper): Alternate SIM failure causes host to hang.
• J4200/J4400: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SLES9SP4: Multipath: Lost Communication to JBOD after Sun Storage Common Array Manager software SIM firmware upgrade.
• Cannot register J4x00 on Linux until host reboot3.
• MPT 3.16.00.00 HBA SAS cable insert, expander reset or power cycle hang x86 host until reset.
• OS does not see zoning filtering through to proxy server correctly. This issue is specific to Linux hosts.
• As a result of JBOD expander firmware upgrade, expander reset might hang Linux OS.
• 1.26.03.00: linux missing targets, fdisk -l and sg_map -i hangs after JBOD second power cycle.

Sun StorageTek SAS RAID HBA hot plug is not supported:

Generally, the workaround is to reboot the array between any cable changes.

• J4x00 failed disk drive (Sun StorageTek SAS RAID HBA) not reported.
• J4x00 Windows agent (Sun StorageTek SAS RAID HBA) 0.0 MB reported; drive FRU missing unique identifier.

Solaris platforms

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) not supported

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:

#netstat -an | grep 6789

Typical output is: *.6789 *.* 0 0 49152 0 LISTEN

Enable port 6789:

# svccfg -s svc:/system/webconsole setprop options/tcp_listen = true

# smcwebserver restart*

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:

1. Edit the file /kernel/drv/scsi_vhci.conf

The following line should read:

device-type-scsi-options-list = “SUN Universal Xport”, “disable-option”; disable-option = 0x7000000

1. Run the stmsboot -u command.

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

Solaris

/var/sadm/install/se6000/

Linux

/var/opt/cam/

Windows
32-bit

\Program Files\Common Files\Sun Microsystems\se6000

Windows
64-bit

\Program Files (x86)\Common Files\Sun Microsystems\se6000