3.270 bytes

Service Hints & Tips

Document ID: MIGR-477KUF

This document is provided to IBM and our Business Partners to help sell and/or service IBM products. It is not to be distributed beyond that audience or used for any other purpose.

Netfinity 3500 - 1962 POST caused by incorrect installation of SCSI cable

Applicable to: World-Wide

Abstract: 1962 POST caused by incorrect installation of SCSI cable.

Symptoms:



Problem isolation aids:
The system is a Netfinity 3500 server, Type 8644, any model.

The system is configured with the following option(s):



The system has the described symptoms.

Fix:
Secure the end connector of the cable to the planar board.

Route cable so that the center connector #3 is positioned at the Bay 6 HDD.

Remove the Velcro tape backing from connector 3 and press connector onto the Bay 6 HDD.

Note: The velcro will adhere to the HDD case.

Route the terminator end of the cable under the crossbar toward the top of the chassis.

Note: The terminator will be fastened to the top of the chassis using the velcro on the terminator.

Remove the velcro tape and press in place.

Note: Position approximately 1.5 inches from the power supply and center between the chassis sides.

Ensure all connections are secure and excessive strain is not being applied to the SCSI cable.

Details:
A new cable is being shipped in the Netfinity 3500. If this cable is not installed correctly system could experience 1962 errors from cable coming loose.

When the velcro is not properly utilized, the cable will not function correctly. Connections to SCSI devices (including boot devices) can be lost.

SAS keywords:
PSY2, D/T8644, NETFINITY, SERVICER ONLY, 3500, CABLE, SCSI, 02K1416, 01K1481, 1962, POST, ERROR






Search Keywords

Document Category

Retain

Date Created

22-04-99

Last Updated

21-04-99

Revision Date

22-04-2000

Brand

IBM PC Server

Product Family

Netfinity 3500

Machine Type

8644

Model

10U; All; 10X; 20U; 20X; 21U; 21X; 30U; 30X; A0U; B0U; B1U; 39U; RR1; 29U; 300; 30A

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes