| FAB
|
Implementation
|
Synopsis
|
Last Modified Date
|
| A0222-1 |
U
|
Seagate Cheetah 4 FCAL and SCSI disk drives may experience higher than expected failure rate. |
Jan 04 2006
|
| A0199-2 |
C
|
Seagate Cheetah 3 FCAL disk drives in A5x00 and T3 Storage Arrays may experience higher than expected failure rate. |
Sep 02 2003
|
| A0172-1 |
C
|
Delorean racks shipped before July 12, 1999 may have unusable Anti-Tip rails. |
Feb 27 2001
|
| A0164-1 |
C
|
Systems with FC100/P cards (QL2100 PCI FC-AL HBA) having Molex optical transceivers, may cause increasing numbers of loop errors, excessive LIPs, and SCSI parity errors as they age. |
May 12 2000
|
| A0156-1 |
C
|
StorEdge A5200 with -03 backplane may fail the LBF test in Stortools after adding or replacing 9GB or 18GB 10K RPM disk drives. |
Dec 17 1999
|
| A0144-3 |
M
|
Vixel GBIC may experience excessive CRC or scsi parity errors, offline and/or timeout messages on the StorEdge A5x00 and the Ultra Enterprise 3500. |
Oct 06 1999
|
| A0138-1 |
C
|
SBus/FC SOC+ Host Adapters may experience recoverable data transfer read errors. |
May 14 1999
|
| I0897-1 |
R
|
StorEdge A5200 disks may appear in the output of 'format' with non-standard addresses. |
2005-04-14
|
| I0836-1 |
R
|
Seagate ST336752FC (36.4GB)) disk drives should not be installed into non-RAID configurations |
2002-06-11
|
| I0777-1 |
R
|
In some configurations, after a FC loop disruption the SOC+ HBA intermittently takes the FC loop down |
2002-02-25
|
| I0712-1 |
R
|
Finisar GBIC problems on the storage array products |
2001-08-29
|
| I0711-1 |
R
|
The problem with Incorrectly mounted brackets on the switch |
2001-10-10
|
| I0704-1 |
R
|
Field handling procedure on non-Sun supported GBICs |
2001-09-18
|
| I0701-1 |
R
|
FWC 2.0 & II 2.0 require correct version of Java for proper operation |
2001-07-30
|
| I0700-1 |
R
|
FC Switch f/w level must be checked to install or replace StorEdge Network FC Switch into a SAN Config. |
2001-07-27
|
| I0630-1 |
R
|
Problem with mishandling a fiber optical device |
2001-03-30
|
| I0575-1 |
R
|
When used on a heavily loaded system to monitor multiple enclosures, Component Manager response time can be longer than expected. |
2000-04-27
|
| I0554-1 |
R
|
Support of hubs with A5x00 and Veritas Volume Manager version |
2000-02-18
|
| I0541-2 |
R
|
Restrictions on multi-initiator config using FC100/P card on A5x00 |
2001-08-02
|
| I0533-1 |
R
|
A minute quantity of ST39102FC 9GB FC-AL disk drives may be susceptible to low amplitude head failures. |
1999-11-19
|
| I0506-1 |
R
|
Confusion in the field over the requirement of a 2" gap between 72" Expansion Cabinets containing A5x00 Storage Arrays. |
1999-06-29
|
| I0502-1 |
R
|
Visual identification of -02 and -03 GBICs without physically removing from system. |
1999-06-18
|
| I0501-1 |
R
|
The backplane part# revision for A5X00 arrays may differ from the rev. level that is dynamically reported by the array. |
1999-06-17
|
| I0400-2 |
R
|
UPDATED FIN. Empty Backplane/incorrect configuration on StorEdge A5x00 can Cause Errors. |
1999-11-19
|
| A0222-1 |
U
|
Seagate Cheetah 4 FCAL and SCSI disk drives may experience higher than expected failure rate. |
Jan 04 2006
|
| A0199-2 |
C
|
Seagate Cheetah 3 FCAL disk drives in A5x00 and T3 Storage Arrays may experience higher than expected failure rate. |
Sep 02 2003
|
| A0172-1 |
C
|
Delorean racks shipped before July 12, 1999 may have unusable Anti-Tip rails. |
Feb 27 2001
|
| A0164-1 |
C
|
Systems with FC100/P cards (QL2100 PCI FC-AL HBA) having Molex optical transceivers, may cause increasing numbers of loop errors, excessive LIPs, and SCSI parity errors as they age. |
May 12 2000
|
| A0156-1 |
C
|
StorEdge A5200 with -03 backplane may fail the LBF test in Stortools after adding or replacing 9GB or 18GB 10K RPM disk drives. |
Dec 17 1999
|
| A0144-3 |
M
|
Vixel GBIC may experience excessive CRC or scsi parity errors, offline and/or timeout messages on the StorEdge A5x00 and the Ultra Enterprise 3500. |
Oct 06 1999
|
| A0138-1 |
C
|
SBus/FC SOC+ Host Adapters may experience recoverable data transfer read errors. |
May 14 1999
|
