Skip Navigation Links | |
Exit Print View | |
Sun Storage Common Array Manager Software Release Notes, Release 6.9.0 Update |
1. Sun Storage Common Array Manager Software Release Notes
What You Get with the Software
Licensing Optional Premium Features
Best Practices for Browser Performance
2500 Array Support for VMware ESX 4.1 with Firmware 07.35.55.10 and later
6540, 6140, and FLX380 Arrays Upgrade
Sun Storage F5100 Flash Array Notes
Create Snapshot fails using CLI
Controller Smart battery replacement procedure
Array loses communication during registration when IPV6 is enabled
Ancient I/O rebooting due to cache block size
Battery nears expiration: 06.xx write back cache should not be disabled
Both RAID controllers reboot after 828.5 days--2500/6000 arrays
Reboots occur due to ancient I/O being aborted in large configurations
Volume error—evShowVol output: Initialization: Not Completed
Reregister Auto Service Request for CAM
Auto Service Request advisory note: DTS Listener transfer
Array name remains unchanged after a full array reset
No email notification for critical and above events
Access Configuration: Cascaded J4400 issues
Access Configuration: Sun Storage 6Gb SAS HBA—OS hangs
Access Configuration fails with error: java.util.HashMap cannot be cast to java.util.Properties
Access Configuration: non-zoned SAS2 wide port aggregation FRU Report display—F5100 + 6Gb/sec HBA
Array lock key must be set before configuration files are imported
ComponentInsertEvent not generated for disk drive inserted into J4200
Current Jobs page can take more than five minutes to display
Expander firmware 5.3.73 does not persist a SAS zone group
Replication status incorrect when primary volume fails
Service Advisor: replacing failed SIM with dual path configurations
Volumes not deleting from the Single Page window
Attempt to delete partner replication set on secondary array fails
Incorrect sscs add notification description in CLI guide
2500 Series Release Notes: Simplex vs. Duplex Configurations
Disk Locked description is inaccurate in online help
Firmware upgrade fails with error: FWR_UPGRADE_FAILURE,6 for J4200/J4400 arrays
Firmware upgrade fails on J4400 SATA drives
Firmware upgrade fails when expander and disks are upgraded together
Firmware upgrade not recognized by GUI until agent runs
Sun Blade 6000 firmware upgrade fails with down-level expander
Sun Blade 6250 and 6270—upgrading network expansion modules fails
Installation and Upgrade Issues
Error occurs when upgrading 2510 controller and drive firmware
Installation fails on SUSE 10.3 32-bit and 64-bit hosts
Performance Enhancer for 2500-M2
Enabling Try and Buy license using the CLI
“Require-Stop” not working in SUSE11.1 innserv jexec init.d script
Logging in to CAM on SUSE11 using invalid password
Adding or removing SATA drives requires host boot
Sun Storage J4000 and F5100 Flash arrays—Linux hot plug issues
Solaris with Veritas DMP or other host type
Error—”no execute access to opt/SMgr/agent/ notifysmagent.sh”—occurs during system boot-up
UTM LUNs Controlled by “Solaris Traffic Manager” 6000/2500 arrays
Add License error using the CLI
Support Data does not save using Windows 2008 R2 SP1 Servers
This section addresses security vulnerability CVE-2012-4681 as it applies to the Oracle Java SE 6 Update 20 that is installed as part of Sun Storage Common Array Manager Software 6.9 (CAM 6.9). As reported in the Oracle Security Alert for CVE-2012-4681 http://www.oracle.com/technetwork/topics/security/alert-cve-2012-4681-1835715.html, this vulnerability can be exploited only through untrusted Java Web Start applications and untrusted Java applets.
CAM 6.9 installs Java SE 6 Update 20 in a private CAM directory to run configuration and monitoring functions, and to provide BUI and CLI user interfaces. These functions are implemented as Java SE applications, not applets, so the applet security vulnerability described by CVE-2012-4681 does not affect the parts of Java SE that CAM uses. This version of Java SE is used only by CAM. It is distinct from the Java SE installed in default locations on the server for use by other applications.
The user is responsible for installing an updated Java SE for use by other applications, such as web browsers, running on the CAM management host. Details are specified in the Oracle Security Alert mentioned above. A user can verify that their browser is running an updated Java SE by checking the java deployment property file as described in the Java Plug-in and Applet Architecture (http://docs.oracle.com/javase/6/docs/technotes/guides/jweb/applet/applet_execution.html ).