|
15.634 bytes |
Service Hints & Tips |
Document ID: MCGN-45MLEA |
Netfinity 5500 / 5500 M10 / 7000 / 7000 M10 - System Update: Replacement of Netfinity Fibre Channel Controller (ECA029)
Applicable to: World-Wide
Source: RETAIN ECA029 / Record Number H166312
Abstract: ECA029: Replacement of Netfinity Fibre Channel Controller
Purpose:
This ECA provides for the replacement of the Netfinity Fibre Channel RAID Controller (Standard Controller shipped in the 3526) and the Netfinity Fibre Channel Failsafe RAID Controller.
Product evaluations at IBM have revealed that you may experience Fibre Controller hangs, reboots, a failed controller and possibly incorrect data with or without an error message when using the Netfinity Fibre Channel RAID Controller and/or the Netfinity Channel Failsafe RAID Controller.
Customers should replace the Netfinity Fibre Channel Controller, and, if installed, the Netfinity Fibre Channel Failsafe RAID Controller as soon as possible.
This ECA is "MANDATORY".
Features:
|
Type, |
With |
Machines Affected |
B/M to be |
Service |
System |
|
3526 |
B/M0000000 |
FIBRE CHAN. CONTROLLER |
B/M37L0412 |
00.5 |
00.3 |
Physical check:
The system is any of the following IBM servers:
The system is connected to a Netfinity Fibre Channel RAID Controller Unit, Type 3526, Model 1RU or 1RX.
There is not a visible FRU Label on the front of a suspect controller or the Failsafe RAID Controller when the controller is fully seated in the 3526 unit. A good controller will have a FRU Label visible from the front, when the controller is fully seated in the controller unit.
Prerequisites:
IBM recommends that the customer backup his data prior to the installation of these parts.
The following applies only if the 3526 has more than one (1) controller installed:
If both of the controllers in the 3526 are identified as needing to be replaced, you must have two (2) new controllers on hand -- one for each, so that both are replaced at the same time.
Note: You cannot replace one now and one later, it is a technical requirement that they both be replaced at the same time.
Companion: NONE
Concurrent: NONE
Detail:
Replace the Netfinity Fibre Channel RAID Controller (FRU p/n10L6993), and if installed, the Netfinity Fibre Channel Failsafe RAID Controller (FRU p/n10L6993) with p/n37L0412.
Instructions for replacement are as follows:
1. Identify the mode of the controllers.
a. Open SYMplicity Maintenance and Tuning application
b. Click on Options
c. Click on Controller Mode
d. If Controller Mode is grayed out (i.e. you cannot click on it) write down mode=Active Active. If you can click on it, write down which controller is Active (A or B).
2. Ensure that the server is using the latest device driver for the Netfinity Fibre PCI Adapter.
Note: These drivers can be found at the following URL: http://www.pc.ibm.com/searchfiles.html Search on "Fibre Drivers".
If they are not using the latest device driver, upgrade to the newest device driver. Pages 8 & 9 of the "Netfinity Fibre Channel PCI Adapter Software Installation Guide" describes the procedure for Updating the currently installed Windows NT Driver.
Note: The "Netfinity Fibre Channel PCI Adapter Software Installation Guide" is available in .pdf format from the following URL:
ftp://ftp.infania.net/pccbbs/pc_servers/24l8026.pdf
|
3. Stop all applications before powering off the servers.
Note: If in a cluster environment be sure to take down all servers one at a time.
4. Power off the 3526.
Note: Be sure to turn off the 3526 using the two (2) power switches on the back of the 3526.
5. Remove the old Netfinity Fibre Channel RAID Controller(s).
Note: If there is a second (failsafe) controller installed, and it also meets the ECA identification standards set forth in the Physical Check section of this ECA (i.e. lack of FRU label visible when fully seated) then both controllers must be replaced at the same service call.
6. Once the Controller(s) have been replaced, power on the 3526 (two (2) power switches on the back).
Important: You must wait at least 2 minutes before powering on the servers. It takes 2 minutes for the controller to come up.
7. After waiting at least 2 minutes, power up the servers as you would normally. In a clustering environment this would mean bringing up one (1) server Node at a time.
8. Once the servers are up and running do the following:
a. On a server, open up a DOS window.
b. Change directory to c:\program files\symsm
c. Type "clean -all" and press return.
d. Close the DOS window.
e. Open SYMplicity Maintenance and Tuning application
f. Repeat steps a-e on all remaining servers connected to the 3526.
9. Now ensure that the controllers are set to the same mode as was identified in Step 1.
a. Open SYMplicity Maintenance and Tuning application
b. Click on Options
c. Click on Controller Mode
d. If Controller Mode is grayed out, then continue on to the next step.
Note: If it is not grayed out, and was before, then click on the Active/Active button on the bottom left of the screen. Otherwise it is in an Active Passive mode, and ensure the same controller that was Identified as Active in Step 1d is also identified as active now. If it is not then press the Switch Active/Passive button in the lower middle of the window.
10. In addition once the controllers have been replaced and the system is functioning correctly, do the following to determine if there has been any incorrect data written:
This is done by running the Manual Parity Check/Repair option in the Recovery Application outlined in the IBM Netfinity SYMplicity Storage Manager User's Handbook. The highlights of this are given below for convenience.
Running Manual Parity Check
1. Use the following procedure to run Parity Check/Repair manually.
2. Start the Recovery application.
3. Select the RAID Module containing the LUNs you want to check (or select ALL RAID Controllers).
4. Click the Manual Parity Check/Repair button or select Options -> Manual Parity Check/Repair from the drop-down menus.
5. After you have selected all the LUNs to check, click Start Parity Check/Repair.
6. As each LUN is checked, a histogram bar appears on the screen indicating the Parity Check/Repair progress on that LUN.
7. When Parity Check/Repair is completed, you will see a message indicating if any errors were found.
Notes:
TRADEMARKS:
Other company, product and service names may be the trademarks or service marks of others.
NOTES:
This ECA is "MANDATORY".
This ECA is scheduled to be withdrawn January 31, 2000.
Parts in "Features" Section, under "B/M to be Installed" column, MAY BE Ordered CODE "A".
The only part number which can be ordered for this ECA is the B/M p/n37L0412, which will contain the FRU p/n37L6077.
USA:
IBM PSS/TSS CE's should record all time and parts to Service Code 33, ECA029, Other Office 990.
Travel Time = 0.8Hrs.
USA Business Partners:
Warranty claims for ECA Reimbursement should be submitted via ECLAIM using Type Service 0E. Refer to the Service Support Guide (SSG) for details.
EMEA:
IBM PSS CE's should record all time and parts to Service Code 33, ECA029, (M/T number) Other Office 990. Travel Time = 0.8Hrs.
EMEA Business Partners:
Refer to Warranty Claim System; Use Emergency Claim 5 (ECA) and enter into CPPS: ECA Number 029
Machine Type as required (number).
SAS KEYWORDS:
|
Search Keywords |
| |
|
Document Category |
ECA, RAID, Retain | |
|
Date Created |
03-03-99 | |
|
Last Updated |
28-04-99 | |
|
Revision Date |
29-04-2000 | |
|
Brand |
IBM PC Server | |
|
Product Family |
Netfinity 5500, Netfinity 7000, Netfinity 7000 M10, Netfinity 5500 M10 | |
|
Machine Type |
All, 8660, 8651, 8680, 8661 | |
|
Model |
All | |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
Retain tip H166312 / ECA029 | |
|
Reverse Doclinks |
Date last altered: A99/04/15 |