| Alert
|
Synopsis
|
Last Modified Date
|
| 1022281.1 |
Using Common Array Manager (CAM) 6.6.0.11 to Create a New Initiator may Result in the Incorrect Host Type Being Used |
2015-07-17
|
| 1019331.1 |
Controller Firmware for SE6130, ST6140 and ST6540 on Solaris may not Failover Array LUNs |
2013-07-02
|
| 1019006.1 |
Collecting Support Data Using Common Array Manager while Drives are Bypassed May Cause Controllers to Reboot |
2014-01-24
|
| 1019002.1 |
Collecting Support Data On Certain Arrays May Cause One or Both Array Controllers to Reboot |
2016-06-01
|
| 1018999.1 |
Disk Drive Off Lines and Fail modes Without Recent Firmware Updates |
2013-12-19
|
| 1017338.1 |
Sun StorageTek 6000 Arrays May Report "Trays Not Grouped by Type" Message |
2013-04-17
|
| 1000797.1 |
"Support Data Collection" Procedure on Certain Sun StorEdge and Sun StorageTek Arrays May Cause SATA Drive Failures |
2012-07-27
|
| 1000690.1 |
Unmapping a Volume or Snapshot on a Sun StorEdge 6130 Array May Cause One of The Array Controllers to Reset |
2012-07-27
|
| 1000556.1 |
Insertion or Removal of a RAID Controller on Sun StorEdge 5310 or 6130 Array May Cause the Alternate Controller to Reboot |
2012-07-27
|
| 1000373.1 |
Vdisk Failure on a Sun StorEdge 6130 May Cause All the Volumes on the Same Controller to Become Inaccessible |
2012-07-27
|
| 1000356.1 |
Certain sscs(1M) Commands, Array/StorEdge 3900SL CLI Commands, or Certain StorEdge 3900SL/6320/6130 GUI Actions May Cause Loss of Connectivity to a Host(s) |
2012-07-27
|
| 1000338.1 |
LAN Congestion may Result in Dual Controller Reboot on a Sun StorEdge 6130 Array |
2012-07-27
|
| 1000043.1 |
Changing the Array Volume-to-LUN Mappings May Cause Array Controllers to Initiate a Boot-Loop |
2012-07-27
|
