| Problem Document
|
Synopsis
|
Last Modified Date
|
| 1916789.1 |
Sun Storage 3000 Arrays: JBOD SES Device Links Are Missing |
2014-09-04
|
| 1020286.1 |
Sun Storage 3000 Arrays: Smaller Stripesizes May Cause Slow Logical Drive (LD) Rebuild Time |
2014-03-12
|
| 1020033.1 |
Sun Storage 3000 Arrays: After Growing a Logical Drive (LD), New Size is not Reflected on Host |
2014-03-18
|
| 1012774.1 |
On Sun StorEdge 35xx Arrays running 3.27R firmware, setting the value 'Auto Global Spare' to enabled may result in existing Logical Drives to be lost |
2013-08-12
|
| 1012692.1 |
Sun StorEdge 351x Array: How to Resolve Devices Missing from the se3kxtr "show_frus" and "show_ses-devices" Output |
2013-08-12
|
| 1012603.1 |
Sun StorEdge[TM] 3000 series array: controller panic with message "WARNING: BBU cached data error!" |
2013-08-12
|
| 1012505.1 |
Sun Storage 3000 Arrays May Lose Data Host Access After Reporting "Memory Not Sufficient to Fully Support Current Config" |
2013-08-12
|
| 1012309.1 |
Sun Storage 3310 SCSI Array: Resolving SCSI Bus Resets and Transport Errors When Using the Ultra320 Host Bus Adapter |
2018-03-06
|
| 1012156.1 |
Systems connected to Sun StorEdge 3310 SCSI array may experience SCSI resets and errors when SSCS and sccli are run in-band at the same time |
2017-12-11
|
| 1011981.1 |
Sun StorEdge[TM] 3310:Unable to see a 3310 After Installing Patches and Rebooting |
2013-08-12
|
| 1011232.1 |
Recovering From a Failed SAF-TE Firmware Update on Sun Storage 33x0 RAID Arrays |
2013-08-12
|
| 1010855.1 |
Sun Storage 3310/3320/3510/3511 Arrays: Identifying and Resolving an Incorrect "Controller Unique Identifier" |
2013-08-12
|
| 1010521.1 |
Sun StorEdge 3310/3320/3510/3511: Running sccli command may result in SCSI timeouts |
2018-04-24
|
| 1010467.1 |
Sun StorEdge[TM] 33x0 and 35x0:Symptom:SCCLI Fails to Find Controller |
2017-01-04
|
| 1009967.1 |
Sun Storage 3000 Arrays: sccli Utility Reports "network connection setup failed" |
2013-11-12
|
| 1009497.1 |
Sun StorEdge 3310/3510/3511/3320: Resolving Data Unavailability issues due to different default Cylinder/Head/Sector settings after firmware upgrade. |
2013-08-12
|
| 1009430.1 |
Sun StorEdge[TM] 3310/3510/3120/3511 Array: Monitoring from more than one host using Sun StorEdge[TM] Configuration Service can cause the controller to not respond |
2013-08-12
|
| 1009395.1 |
Sun StorEdge[TM] 3310: Some sccli commands run in-band give error: "this operation is only supported on RAID primary controllers" |
2016-03-01
|
| 1009343.1 |
SUNWjfca HBA will not have any bug fixes |
2018-01-08
|
| 1009322.1 |
Sun StorEdge[TM] 3310/3320/3510/3511 Array: Running concurrent/simultaneous se3kxtr scripts, may cause the array to hangup. |
2017-07-31
|
| 1008956.1 |
Sun StorEdge[TM] 3310 (SE3310) - Solaris[TM] unable to see any mapped LUNs, or LUNs other than LUN 0 |
2013-08-12
|
| 1008359.1 |
Sun StorageTek[TM] 3xxx Arrays - Unable to change controller assignment on LogicalDisk |
2013-08-12
|
| 1008108.1 |
Sun StorEdge 3310, 3510 and 3511: Avoiding double drive failure conditions on 3.x firmware |
2013-08-12
|
| 1007982.1 |
Sun StorEdge[TM] 3310 without configured lun0 shows narrow channel setting. |
2013-08-12
|
| 1007691.1 |
[3310] ssmon can generate ASC: 0x29 (power on, reset, or bus reset occurred) |
2018-01-03
|
| 1006888.1 |
Sun Storage 3310 Array Connected with Ultra320 SCSI HBA: Fujitsu (Allegro) Drives Can Cause SCSI Bus Resets and Transport Errors |
2018-03-06
|
| 1006649.1 |
Sun StorEdge[TM] 3000 Arrays: 3.2x and 4.x Firmware Differences in Handling Media Errors |
2016-04-14
|
| 1006542.1 |
Sun StorEdge[TM] 3310 SCSI Array/JBODs: Connecting to the onboard SCSI port on Sun Enterprise[TM] 3x00/4x00/5x00/6x00 servers may give SCSI errors |
2013-08-12
|
| 1006445.1 |
Sun StorEdge[TM] 3310 SCSI Array: SCSI error message "f/w initiated BDR fails" |
2013-08-12
|
| 1006414.1 |
Sun StorEdge 351x/33x0 Arrays: Mute Button Held During Reset of Array Will Cause False Battery Failure Messages |
2017-12-11
|
| 1004867.1 |
Sun Storage 3310 Not Seen When Connected to LVD SCSI-3 HBA (Jasper) |
2016-06-30
|
| 1004263.1 |
Sun StorEdge[TM] 3310 SCSI Array: Unrecoverable media errors not passed to the host |
2013-08-12
|
| 1003771.1 |
Sun StorEdge[TM] Diagnostic Reporter: "Server not online" error |
2013-08-12
|
| 1003736.1 |
Avoiding SCSI Transport Errors while Running Explorer/Extractor/Sccli with Sun Storage 3310 Arrays |
2017-01-04
|
| 1003547.1 |
Sun StorEdge[TM] 3510/3511/3310/3320: Getting "soft errors" reported by iostat |
2017-03-06
|
| 1003518.1 |
Resolving "NVRAM CRC Error: NVRAM Must be Reinitialized" on Sun StorEdge[TM] 3510 Array |
2015-05-08
|
| 1002403.1 |
Sun StorEdge[TM] 3310 Array: Controller Unique Identifier not properly updated with 1159/1170 SAF-TE firmware installed |
2014-07-08
|
| 1002332.1 |
Sun Storage 3000 Arrays: Checking the Actual Cache Status |
2013-08-12
|
| 1002296.1 |
Sun StorEdge[TM] 3310/3320/3510/3511: Duplicate disk entries from show disks output |
2014-05-09
|
| 1002220.1 |
Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged" |
2017-08-01
|
| 1001846.1 |
Sun StorEdge[TM] 3510/3511 FC Array/3310/3320 SCSI Array: Battery Display on Firmware GUI Appears to Be Incorrect |
2013-08-12
|
