| Document Audience: | INTERNAL |
| Document ID: | I0586-1 |
| Title: | The hardware and software requirement to use the onboard SOC+ the I/O boards to connect the A3500FC. |
| Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
| Update Date: | 2004-01-07 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)FIN #: I0586-1
Synopsis: The hardware and software requirement to use the onboard SOC+ the I/O boards to connect the A3500FC.Create Date: Jun/22/00
Keywords:
The hardware and software requirement to use the onboard SOC+ the I/O boards to connect the A3500FC.
Top FIN/FCO Report: No
Products Reference: StorEdge A3500FC connectivity
Product Category: Storage / Documentation
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- E3000 ALL Ultra Enterprise 3000 -
- E3500 ALL Ultra Enterprise 3500 -
- E4000 ALL Ultra Enterprise 4000 -
- E4500 ALL Ultra Enterprise 4500 -
- E5000 ALL Ultra Enterprise 5000 -
- E5500 ALL Ultra Enterprise 5500 -
- E6000 ALL Ultra Enterprise 6000 -
- E6500 ALL Ultra Enterprise 6500 -
X-Options Affected
------------------
SG-XARY360B-90G - - ASSY,TOP OPT,1X5X9,MIN,9GB,10K -
SG-XARY360B-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
SG-XARY362B-180G - - X-OPT,2X7X9,MIN,FCAL,9G10K -
SG-XARY374B-273G - - ASSY,TOP OPT,3X15X9,MIN,9GB,10K -
SG-XARY380B-182G - - X-OPT,FC-SN,1X5X18MIN,18GB10K -
SG-XARY380B-1092G - - ASSY,FC-SNL,1X5X18MAX,18G10K -
SG-XARY382B-364G - - ASSY,FC-SN,2X7X18,MIN,18GB,10K -
SG-XARY384B-546G - - ASSY,FC,3X15X18,MIN,18GB -
SG-XARY381B-364G - - ASSY,FC-SN,1X5X36MIN,36G10K -
SG-XARY381B-1456G - - ASSY,FC-SN,1X5X36MAX,36B10K -
SG-XARY383B-728G - - ASSY,FC-SN,2X7X36MIN,36B10K -
SG-XARY385B-1092G - - ASSY,FC-SN,3X15X36MIN,36B10K -
UG-A3500-FC-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
CU-A3500-FC-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
UG-A3500FC-182-10K - - FCTY,A3500FC/SCSI,1X5X18MIN,18/10K -
CU-A3500FC-182-10K - - FCTY,A3500FC/SCSI,1X5X18MIN,18/10K -
UG-A3500FC-364-10K - - FCTY,A3500FC/SCSI,2X7X18MIN,18/10K -
CU-A3500FC-364-10K - - FCTY,A3500FC/SCSI,2X7X18MIN,18/10K -
UG-A3500FC-546-10K - - FCTY,A3500FC/SCSI,3X15X18MIN 18G10K -
CU-A3500FC-546-10K - - FCTY,A3500FC/SCSI,3X15X18MIN 18G10K -
UG-A3K-A3500FC - - ASSY,UPGRADE,A3500FC/TABASCO -
UG-A3500-A3500FC - - ASSY,UPGRADE,A3500FC/DILBERT -
X6538A - - X-OPT,A3500FC CONTROLLER -
X2611A - - OPT INT I/O BD FOR EXX00 -
X2612A - - OPT INT I/O BD EXX00 W/FC-AL -
X2622A - - OPT INT GRAPHICS I/O BD EXX00 -
Parts Affected:
Part Number Description Model
----------- ----------- -----
704-6708-10 CD, SUN STOREDGE RAID MGR 6.22 -
References:
BugId: 4310474
PatchId: 103346-25 or higher
DOC: 805-7758-11: Sun StorEdge RAID Manager 6.22 Release Notes
805-4981-13: Sun StorEdge A3500/A3500FC Hardware Configuration
GuideIssue Description:
This FIN is intended to clarify the hardware and software requirement
to connect the onboard SOC+ device on I/O boards used in Enterprise Server
E3X00 through E6X00 with an A3500FC StorEdge Array.
The Sun StorEdge RAID Manager 6.22 Release Notes has a statement
saying that the onboard SOC+ is not yet supported on A3500FC
controller. This was because at the time when the A3500FC was
introduced, Network Storage Quality Assurance group (QAST) had not yet
qualified the use of onboard SOC+ with A3500FC. There have been numerous
requests from customers to ES Field Service Representatives regarding the
timeframe of supporting the onboard SOC+ with the A3500FC controller.
Now Network Storage QAST has qualified the use of onboard SOC+ device with
A3500FC. This FIN is intended to inform the field of the types of I/O board
with onboard SOC+ that are supported with A3500FC. This fin also provides
the patch requirement and the procedure to check and load the required
fcode to the onboard SOC+. The Sun StorEdge RAID Manager 6.22 Release
Notes will be updated to include the onboard SOC+ support information
on the next release which is targeted to release in Q2, FY01.
The following is the Hardware and Fcode requirements:
Supported host platforms: E3X00 through E6X00.
The following types of I/O boards have onboard SOC+ that are supported:
I/O board with SOC+:
X2611 (501-4266-06) I/O type 4, 83 MHz Gigaplane.
X2612 (501-4883-05) I/O type 4, 83/90/100 MHz Gigaplane.
I/O Graphic board with SOC+:
X2622 (501-4884-05) I/O type 5, 83/90/100 MHz Gigaplane.
Minimum Fcode requirement for supported I/O boards: 1.8.25Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---Corrective Action:
Enterprise Customers and authorized Field Service Representatives may
avoid the above mentioned problem by following the recommendations
as shown below.
First you need to load patch 103346-25 or higher. After loading the
patch, use the following command to verify fcode version:
# ./flash-update-
Where corresponds to the Version number of patch 103346.
Example: # ./flash-update-25
This command returns a list of system boards and its PROM revisions.
Look for the supported I/O type 4 or type 5 boards and it's corresponding
Fcode revison. If the Fcode revision on these boards are below 1.8.25 then
you need to proceed with a "y" when prompted to flash update your firmware.
Caution: Make sure don't connect the A3500FC to the I/O type 1 or type 2
boards from the list.
The following example shows how to check and update the fcode on the
onboard SOC+. Note that board 1 and board 3 are the supported I/O type
type 4 that need a firmware update to be able to connect to an A3500FC.
--------------------------- Beginning of an Example ---------------------------
# cd 103346-25
# ls
README.103346-25 README.CheckSums.103346-25 flash-update-25
README.ARCHIVE dwlist
# ./flash-update-25
Extracting files
Loading flashprom driver
Creating devlinks
Current System Board PROM Revisions:
------------------------------------
Board 0: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 2: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 4: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 6: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 8: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 10: CPU/Memory OBP 3.2.22 1999/05/12 15:34 POST 3.9.22 1999/05/12 15:37
Board 1: I/O Type 4 FCODE 1.8.22 1999/05/12 15:33 iPOST 3.4.22 1999/05/12 15:37
Board 3: I/O Type 4 FCODE 1.8.22 1999/05/12 15:33 iPOST 3.4.22 1999/05/12 15:37
Board 13: I/O Type 3 FCODE 1.8.24 1999/12/23 17:30 iPOST 3.0.24 1999/12/23 17:34
Available 'Update' Revisions:
-----------------------------
CPU/Memory OBP 3.2.25 2000/03/29 14:52 POST 3.9.25 2000/03/29 14:56
I/O Type 1 FCODE 1.8.25 2000/03/29 14:51 iPOST 3.4.25 2000/03/29 14:55
I/O Type 2 FCODE 1.8.25 2000/03/29 14:51 iPOST 3.4.25 2000/03/29 14:55
I/O Type 3 FCODE 1.8.25 2000/03/29 14:51 iPOST 3.0.25 2000/03/29 14:56
I/O Type 4 FCODE 1.8.25 2000/03/29 14:51 iPOST 3.4.25 2000/03/29 14:55
I/O Type 5 FCODE 1.8.25 2000/03/29 14:52 iPOST 3.4.25 2000/03/29 14:55
Verifying Checksums: Okay
Do you wish to flash update your firmware? y/[n] : y
Are you sure you wish to continue? y/[n] : y
Updating Board 0: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 2: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 4: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 6: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 8: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 10: Type 'cpu' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 1: Type 'dual-sbus-soc+' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 3: Type 'dual-sbus-soc+' (PromID=20e2)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Updating Board 13: Type 'dual-pci' (PromID=1a4)
1 Erasing ................................ Done.
1 Verifying Erase ................................ Done.
1 Programming ................................ Done.
1 Verifying Program ................................ Done.
Unloading flashprom driver
The new firmware will not take effect until the system is power-cycled.
Do you wish to halt the system now? yes or no?
--------------------------- End of an Example -------------------------
Comments:
Both onboard soc+ connections on an I/O board are supported. It is
recommended that each controller on an enclosure be connected to
different I/O boards for HA and serviceability reasons.
--------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------