Sun Storage Common Array Manager Software Release Notes, Release 6.7.0 Part No.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Contents Sun Storage Common Array Manager Software Release Notes About the Software 2 How to Get the Software 2 What You Get with the Software 3 Licensing Optional Premium Features What’s New in This Release 4 4 Selecting Maximum Volume Size Using the CLI Updated os-type Values in CLI 8 Supported Arrays 8 Supported Web Browsers 9 Best Practices for Browser Performance Supported Languages 9 9 10 Supported Platforms Firmware 6 7 System Requirements Patches 5 5 Deleting Volumes/Virtu
6540, 6140, and FLX380 arrays J4000 arrays 12 Sun Blade 6000 Disk Module Sun Storage F5100 Flash array Supported Expansion Modules Notable Fixes 13 13 13 14 Sun Storage Common Array Manager Software 14 Sun Storage F5100 array FMod (D11B firmware) 15 6000 Series arrays (7.60.53.10 firmware) 16 6000 Series arrays (7.60.36.10 firmware) 16 2500 Series arrays (7.35.55.11 firmware) 18 2500 Series arrays (7.35.55.
Sun Storage Common Array Manager Software Release Notes Use this document for instructions about how to download Oracle’s Sun Storage Common Array Manager software and learn about new features, related documentation, system requirements, notable bug fixes, and known issues for the 6.7.0 product release. For installation, configuration, and other instructions, see “Documentation” on page 7.
About the Software Sun Storage Common Array Manager software provides an easy-to-use interface from which you can configure, manage, and monitor storage arrays. The software includes a distributed architecture enabling you to designate local and remote domains through which you can configure and manage your storage environment for optimal efficiency and productivity.
. In the Release field, expand Sun Storage Common Array Manager (CAM), check the release and patches you want to download, and then click Close. 8. Click Search. Available patches for the release you selected are displayed. 9. Select a patch for your operating system. 10. Click ReadMe for a patch description and installation instructions. 11. Click Download for a single patch, or Add to Plan to download a group of patches. What to do next...
Licensing Optional Premium Features There are a variety of premium features for which you can purchase licenses. When you order licenses, they are sent to you with instructions on how to activate the features. For more information, search the online help pages for these topics: ■ About Licensed Features ■ Adding a License ■ Managing Licenses Note – You must name arrays before adding licenses.
Selecting Maximum Volume Size Using the CLI When creating a new volume using the “create volume” command, there are two ways to specify using all available space on a virtual disk (vdisk): ■ If creating a new volume and vdisk simultaneously, use the -F,--fill-vdisk option. This creates the largest possible vdisk that matches the attributes of the specified pool. ■ If creating a new volume on an existing vdisk, specify the “max” value for the -s,--size option.
TABLE 2 os-type Values Legacy os-type New os-type win2k_clustered W2KNETCL win2k_non_clustered_dmp W2KNETNCLDMP win2k_clustered_dmp W2KNETCLDMP aix AIX aixavt AIXAVT hpux HPX linux LNX netware_failover NWRFO Deleting Volumes/Virtual Disks Enhancement Beginning with version 6.7, and to improve usability, the Graphical User Interface (GUI)/Browser User Interface (BUI) will retain a virtual disk when deleting the last volume on that virtual disk.
Documentation For hardware information, refer to the array’s release notes and hardware installation guide. Online help and man pages are incorporated into the software. The following table lists other documentation related to Sun Storage Common Array Management software. You can search for documentation at: http://www.oracle.
System Requirements System requirements for Sun Storage Common Array Manager software are described in the following sections: ■ “Supported Arrays” on page 8 ■ “Supported Web Browsers” on page 9 ■ “Supported Languages” on page 9 ■ “Patches” on page 10 ■ “Supported Platforms” on page 11 Supported Arrays Sun Storage Common Array Management software supports the following Sun storage systems: 8 ■ Sun Storage 6180 array ■ Sun Storage 6580 array ■ Sun Storage 6780 array ■ StorEdge 6130 array
Supported Web Browsers TABLE 4 Supported Web Browsers Browser Supported Version Firefox 3.0 and higher Microsoft Internet Explorer 6.0 Best Practices for Browser Performance For best web browser performance: ■ Enable pop-up windows. ■ Specify No Proxy for the Sun Storage Common Array Manager host to avoid situations where your browser might hang, time out, or generate error messages.
Man pages are available in: ■ English ■ Japanese Patches See “How to Get the Software” on page 2 for instructions on downloading patches. Oracle’s Sun Storage Common Array Manager 6.7 patches include a new Fishwrap library for Windows systems, new Sun Storage F5100 Flash Array expander firmware version 5.04.05 for all applications, firmware updates, and updates appropriate for your OS and configuration. To obtain patches using Solaris, install Solaris 10 Update 8 or 9.
Supported Platforms TABLE 5 Supported Platforms Platform Operating System SPARC server or workstation Solaris 9 OS Solaris 10 OS OpenSolaris 2009.06 Windows Servers Windows Windows Windows Windows x64 computer Red Hat Linux 4.7 Red Hat Linux 5.4 SuSE Linux Enterprise Server 11 SuSE Linux Enterprise Server 10 SP3 Oracle Enterprise Linux 5.4 Oracle VM 2.2 x86 computer Solaris 10 OS OpenSolaris 2009.
Firmware Firmware delivered with Sun Storage Common Array Manager software can be installed using the Install Firmware Baseline feature. However, moving from one major firmware release to another might require special procedures. If you attempt an upgrade and it fails, contact Support at: https://support.oracle.com For baseline firmware information, such as controller, NVSRAM, IOM, disk drive, version, and firmware file, see Sun Storage Array Baseline Firmware, part number 8210136.
Sun Blade 6000 Disk Module Before beginning the firmware upgrade process, review this document: SAS-1/SAS-2 Compatibility Upgrade Guide (part number 821-1800). This guide contains information required for a successful firmware upgrade. Service Advisor does not include this information. Sun Storage F5100 Flash array The FMod firmware upgrade process requires a manual enclosure power cycle. Onsite upgrade to 5.04.05 firmware baseline with the CAM 6.7 patch is not possible.
TABLE 7 Supported Expansion Module: 2500 Series arrays Array Controller Supported Expansion Module StorageTek 2510. 2530. 2540 2501 Note: Only Simplex 2501 expansion modules may be attached to a Simplex 2500 series controller tray.
6804689 -Change volumes/vdisk deletion process. See “Deleting Volumes/Virtual Disks Enhancement” on page 6. 6833055 -Volume creation fails when the profile uses a finite number of disks. 6910817 -6.5.0.10: OS Type specified is not valid, even though it is described in man page. 6932431 -6.5.0 sscs list commands sometimes fail with “Unauthorized client connection” message. 6935284 -Host Type selected in the GUI does not match the correct host region used by the array.
6959533 -FMOD becomes unresponsive after hundreds of power cycles (900+) with cache flush. Every power cycle preceded by at least one write or SMART query will deplete resources. Amount of run time between power cycles is not relevant. Performance will degrade and ultimately FMOD will become unresponsive (zombie), rendering data unrecoverable. Fix allows resources to be recovered during power up of the device. 6000 Series arrays (7.60.53.
6868517 -Controller reboot loop “PANIC: OGM:commit EventList backlog queue is full.” 6877026 -LSI RFE to dump the stack trace on watchdog timeout. 6891452 -After firmware update to 7.60.18.10, write cache is suspended on one controller. 6892704 -ccmShowState reports incorrect controller in the output. 6897209 -Repeating “ssid <&eq; INVALID_LUN” panics fill MEL. 6899612 -During big block sequential I/O(128k, 256k), the controller might reboot and fail the test.
2500 Series arrays (7.35.55.11 firmware) 7012554 -Seagate drive failure may also cause controller reboots. 2500 Series arrays (7.35.55.10 firmware) 6895450 -Multipathing support on 2510 with VMWARE ESX 3.5 and later. 6925370 -Duplex mismatch issue caused by a bug in the Ethernet driver. 6927505 -2530 when collecting ddc for Ancient IO, only ddcDq logs, trace part not available. 6931813 -Controller reboot due to a lack of buffer handling the required reads from the snapshot directory DB.
Array Issues Drives that have Mechanical Positioning Errors may Cause a RAID Controller to Reboot when the Controllers Attempt to Fail that Drive Bugs 6978258, 7012554, and 7013681–Drives that have mechanical positioning errors may cause a RAID controller in FLX380, 6140, 6540, 6180, 6540, 6580, or 6780 to reboot when the controllers attempt to fail that drive. The drive will be marked as failed when the controller completes SOD.
Symptoms: ■ The disk drives are failing due to a mechanical positioning error as seen in the array event logs, similar to the following: B:10/27/10 7:11:30 AM : 4050 : 0/0/0 : 6008 : Internal : Drive : Tray 33, Slot 16 : Stable storage drive unusable A:10/27/10 7:10:47 AM : 4051 : 4/15/1 : 100A : Error : Drive : Tray 33, Slot 16 : Drive returned CHECK CONDITION : Mechanical Positioning Error A:10/27/10 7:10:49 AM : 4053 : 0/0/0 : 6008 : Internal : Drive : Tray 33, Slot 16 : Stable storage drive unusable Se
Note – There is no redundancy for failover in a simplex 2500 configuration or any duplex configuration where a controller is already offline for any reason. Both RAID controllers reboot after 828.5 days --2500/6000 arrays Bugs 6872995, 6949589 –Both RAID controllers reboot after 828.5 days of continuous operation. A timer in the firmware (vxWorks) called “vxAbsTicks” is a 32-bit (double word) integer that keeps count in the 0x0000 0000 format.
Oracle Java Web Console 3.0.2 goes into maintenance mode Bug 6657309 –After several minutes of inactivity, the Oracle Java Web Console Version 3.0.2 goes into maintenance mode and yields errors similar to the following: m4000 gconfd (noaccess-2277): I can't write to '/var/tmp/orbit-noaccess', ORB init failed Reason: Method failed. See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log Impact: This service is not running.
■ Creation of storage partitions mappings ■ Hot spare assignments ■ Snapshot volume creation Performance Monitoring page does not display in-band statistics Bug 6681582 –Performance Monitoring page lists the Performance statistics as Unavailable. Workaround –Check the physical connectivity from the management host to the array. If the connectivity is good, try un-registering and then re-registering this array.
If the storage array supports multiple performance tiers, performance will suffer after the next storage array reboot unless the condition is resolved and the array is brought into compliance. Solution –See “Licensing Optional Premium Features” on page 4 for general information.
Access Configuration: localhost SAS domain and fmods disappear Bug 6965605 –When the local (not remote) data host is registered, FMS removes the host report from the localhost. Workaround –Re-register the array using the localhost address. This second re-adds the missing SAS domain, HBA and disks. To prevent removal of host reports, register the remote data hosts first and register the localhost last.
CLI - sscs service locate --off reports a false Success status Bug 6960316 –Executing sscs service -a locate on a Sun Storage F5100 works as expected; however, sscs service locate --off does not turn the F5100 locate LED off even though it reports a Successful status. Workaround –Use Service Advisor to execute this command. CLI - sscs service locate with -t option yields error message Bug 6955577 Workaround–Run the cli command from the host that owns the target or use Service Advisor.
Expander firmware 5.3.73 does not persist a SAS zone group Bug 6938593 -Sun Storage F5100 Flash array expander firmware 5.3.73 does not persist a SAS zone group in the case where an initiator’s SAS address changes. Initiator SAS address change can be caused by a host reboot or when a new initiator is plugged into a previously zoned F5100 port.
online 18:24:16 svc:/system/fmservice:default OR RunMe.bin -k from CAM image. Free capacity does not add up Bug 6800666 – Storage Utilization on Storage System Free Capacity does not add up. Works as designed –When computing the Storage System free capacity, Sun Storage Common Array Manager sums the precise free capacity of each disk and not the less precise values displayed on the page.
Service Advisor - replacing failed SIM with dual path configurations If you have dual paths to hosts in zones with cascaded JBODs and you need to replace a failed SIM, you might encounter a problem when you have to plug in the SAS cables to the new SIM. This is because the new SIM is not zoned and all hosts see all disks until the old zone is restored. Workaround –Before you replace a failed SIM, be sure to stop all I/O - even in dual path configurations.
Volume segment size, when changed, requires a new profile with a variable number of disks Bug 6599933 –Changing a volume to a different segment size requires that you create a new profile with the desired segment size, create a pool using that profile, and apply the new pool to the volume. However, if the original profile was created using a fixed number of disks instead of a variable number of disks, an error is returned.
CLI Guide error --help command example In Table 1-2 of the Sun Storage Common Array Manager CLI Guide for version 6.7.0, incorrect sample output is given for displaying syntax for a command/subcommand pair for a specific array type or array name.
Firmware upgrade fails on J4400 SATA drives Bug 6939824 Workaround –Move affected disks to another slot before upgrading so they do not remain in a degraded state. Firmware upgrade fails when expander and disks are upgraded together Bug 6916355 Workaround –Power-cycle the array and re-run the firmware install wizard. Then resume the disk drive firmware upgrade. Firmware upgrade not recognized by GUI until agent runs Bug 6873568 Workaround –Wait 5 minutes for the agent to run or run the agent manually.
Installation Issues Datahost RevisionDeltaEvent Mismatch alarm Bug 6999384 –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.
Installation fails when user account control is On - Windows 2008 Bug 6753949 Workaround –Users with Administrative privileges that are used to 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. Uninstaller -stop applications before running- Windows only Bug 6769156 –Stop all applications that are running a java.exe or javaw.
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 (kernal: 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.
Bug 6918422 –After Linux hot-plug, the JBOD is no longer monitored by the management software. Bug 6731595 –J4200/J4400: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SuSE 9 SP4: Multipath (device mapper): Alternate SIM failure causes host to hang. Bug 6732411 –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.
Solaris Issues Error--”no execute access to opt/SMgr/agent/notifysmagent.sh”-- occurs during system boot-up Bug 6934913 –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.
UTM LUNs Controlled by “Solaris Traffic Manager” -6000/2500 arrays 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.
