Sun 2500, 2500-M2, and 6000 Arrays: Resolving Error "Data rate negotiation failed on controller"

Asset ID:	1-72-1597843.1
Update Date:	2016-07-23
Keywords:

Solution Type Problem Resolution Sure

Solution 1597843.1 : Sun 2500, 2500-M2, and 6000 Arrays: Resolving Error "Data rate negotiation failed on controller"

Applies to:

Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 6540 Array - Version All Versions and later
Sun Storage 6780 Array - Version All Versions and later
Sun Storage Flexline 240 Array - Version Not Applicable and later
Sun Storage 6580 Array - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Sun Storage Common Array Manager (CAM) may raise an alarm similar to the following:

Alarm ID : alarm28
Description: Data rate negotiation failed on controller Tray.85.Controller.A, channel 0.
Severity : Critical
Element : t85ctrl1
GridCode : 70.66.1073
Date : 2013-09-30 08:26:43

Cause

Grid codes are comprised of three parts:

Two-digit array code
Two-digit event type
Four-digit description

For more details about grid codes, see <Document 1498053.1> How to Decode Common Array Manager Alarms using the Event or Grid Code.

You can use the ras_admin command to view a grid code's possible causes and recommended actions. Since ras_admin is only displaying the event code explanation and not an actual alarm, things like component IDs will not match the actual configuration or alarm of your array.

The ras_admin command can be found in the following locations:

   Solaris: /opt/SUNWsefms/bin
   Linux: /opt/sun/cam/private/fms/bin
   Windows: <Drive>: \Program Files\Sun\Common Array Manager\Component\fms\bin

Here is an example of the portion of ras_admin output showing possible causes for the grid code example in the Symptoms section of this document.

# ras_admin advisor -e 70.66.1073
Event Code         : 70.66.1073
Event Type         : 2540.ProblemEvent.REC_SPEED_NEG_ERROR
Severity           : 0
Sample Description : Data rate negotiation failed on controller {0}, channel {1}.
Probable Cause     : The automatic negotiation for the data rate on the
                     specified port has failed. The port is down and will not
                     transfer any data.

                     Possible causes include:
                     - There are disconnected or faulty cables.
                     - A host adapter or SFP is not functioning properly or has failed.
                     - A Hub or Fabric switch is not functioning properly or has failed.

[ . . . . ]

The ras_admin output uses the term event code to refer to what CAM alarms refer to as grid code. Each array's event code begins with a two-digit code for array type, as follows:

Event Code         : 48.66.1073
Event Type         : 6130.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 57.66.1073
Event Type         : 6140.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 59.66.1073
Event Type         : flx380.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 63.66.1073
Event Type         : 6540.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 69.66.1073
Event Type         : 2530.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 70.66.1073
Event Type         : 2540.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 72.66.1073
Event Type         : flx280.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 73.66.1073
Event Type         : 2510.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 74.66.1073
Event Type         : flx240.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 79.66.1073
Event Type         : 6580.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 80.66.1073
Event Type         : 6780.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 90.66.1073
Event Type         : 6180.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 92.66.1073
Event Type         : 2530m2.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 92.66.1073
Event Type         : 2530m2.ProblemEvent.REC_SPEED_NEG_ERROR

Event Code         : 93.66.1073
Event Type         : 2540m2.ProblemEvent.REC_SPEED_NEG_ERROR

Solution

The ras_admin command shown above in the Cause section also displays recommended actions. For example:

[ . . . .]

Recommended Action :
                     - Reseat any cables that are not securely connected.
                     - Replace any faulty cables.
                     - Replace any HBAs or SFPs that are not functioning correctly.
                     - Verify that any hubs or switches in the data path are operating correctly.

Attachments

This solution has no attachment