| Problem Document
|
Former IBIS ID
|
Synopsis
|
Last Modified Date
|
| 1294674.1 |
|
The Factory Defaults File on the Sun Storage[TM] 6000 IOM Expansion Tray does not Match |
2011-02-18
|
| 1283914.1 |
|
Troubleshooting Sun Storage[TM] Array Unknown Battery Status |
2011-06-08
|
| 1164893.1 |
|
Copy back not starting after replacing a faulty drive in a Sun StorageTek[TM] 2500; 6140; 6540; 6580; 6780 and Flexline 380 |
2010-08-06
|
| 1020676.1 |
262728 |
2500 and 6000 Arrays Show 0MB Cache Memory Size |
2009-10-14
|
| 1019826.1 |
246986 |
Critical Faults for Unreadable Sectors on a Sun Storage[TM] RAID Array |
2011-05-10
|
| 1012932.1 |
217727 |
Sun Storage[TM] RAID Arrays Cannot See Drives in User Interface After Powering on the Subsystem |
2010-09-16
|
| 1012657.1 |
217409 |
Sun Storage[TM] 2500 and 6000 RAID Arrays: Cannot Create or Change a Volume Mapping |
2011-04-20
|
| 1011457.1 |
215699 |
Sun StorEdge[TM] 6130/Sun StorageTek[TM] 6140/6540: Secondary Array in Remote Replication Pair Logs Alarm Against Primary Volume |
2010-08-26
|
| 1011207.1 |
215399 |
Sun StorageTek[TM] Common Array Manager: Login Causes Core with BSM Enabled |
2010-01-03
|
| 1009673.1 |
213309 |
Sun StorageTek[TM] Common Array Manager 5.0 : "Register" or "Upgrade Firmware" fails in the GUI with an Application Error |
2010-10-28
|
| 1009316.1 |
212895 |
Stale or Obsolete Device Label for a Storage Device in Solaris[TM] |
2009-12-04
|
| 1008161.1 |
211215 |
Access to Volumes Cause ASC/ASCQ Codes 0x94/0x01 for Sun StorageTek[TM] and Sun Storage[TM] RAID Arrays |
2011-05-26
|
| 1008072.1 |
211115 |
Sun StorageTek[TM] Common Array Manager Fails with an Internal Error when FMS Is Not Running |
2011-05-30
|
| 1006168.1 |
208637 |
Solaris[TM] Errors During Boot with "Failed to create nodes for pwwn" |
2011-05-09
|
| 1005371.1 |
207485 |
Array Firmware Upgrade Errors with "Could not make connection to the controller" in Sun StorageTek[TM] Common Array Manager |
2011-05-10
|
| 1002778.1 |
203796 |
Sun StorageTek [TM] Common Array Manager Reports a "Fault Management Service authentication communication error" |
2009-12-02
|
