Skip to main content
NetApp Knowledge Base

SAS port has disabled PHY

Views:
6,180
Visibility:
Public
Votes:
4
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • serial-attached SCSI (SAS)

Issue

  • SAS port show Amber LED
  • SAS port PHY disabled alert in system health alert show.

Clutser1::> system health alert show
               Node: Node1
           Resource: Port 0b
           Severity: Major
    Indication Time: Fri Jan 03 01:07:42 2020
           Suppress: false
        Acknowledge: false
     Probable Cause: SAS port 0b on controller Node1 has 1 disabled
                     PHYs.
    Possible Effect: Inactive PHYs might cause degraded link performance.
Corrective Actions: 1. Verify that SAS port 0b has disabled PHYs by using the "storage port show -node Node1 -port 0b" command.
                     2. If the disk shelves connected to port 0b have multiple path to the node, reset port 0b by using the (privilege: advanced) "storage port reset -node Node1 -port 0b" command.
                     3. Verify that the physical cable connection is secure and operational. If the disk shelves are multipathed, reseat the cable.
                     4. If the connected disk shelf is multipathed, replace
                     the SAS cable.

  • Disabled PHY in sysconfig -a.

slot 0: SAS Host Adapter 0b (PMC-Sierra PM8070 rev. C, SAS, <UP>)
        Firmware rev:       03.08.09.00
        Base WWN:           5:00a098:003abb6:34
        Phy State:          [4] Disabled
                            [5] Enabled, 12.0 Gb/s
                            [6] Enabled, 12.0 Gb/s
                            [7] Enabled, 12.0 Gb/s

 

  • EMS log report error:

ERROR sasmon.adapter.phy.disable: Phy 14 of HBA 0a will be disabled due to excessive number of running disparity errors.

or
ERROR sasmon.adapter.phy.disable: Phy 2 of HBA 0a will be disabled due to burst of invalid dword errors.

Note: that the issue might be seen on the other side of the connection (ie on the IOM)

  • Cluster::*> storag shelf show -shelf 6.76

(...)
SAS Ports:
                                      -- Port Speeds Gb/s -- Power  Port
Phy # IOM Port Type WWPN              Operational Negotiated Status Status
----- --- --------- ----------------- ----------- ---------- ------ -----------
(...)
    8  B  Host      500a098007d72e84         12.0          - -      Enabled
    9  B  Host      500a098007d72e84         12.0          - -      Enabled
   10  B  Host      500a098007d72e84         12.0          - -      Enabled
   11  B  Host      500a098007d72e84            -          - -      phy_dis_inval_dword

  • Cluster::*> event log show -node node2|node1 -event *ds.sas*

Time                Node      Severity      Event
------------------- ------ ------------- ---------------------------
5/2/2022 12:18:22   node2     ALERT         ds.sas.hostphy.disableErr: Port [HST2] on channels 9d shelf ID 76 IOM B disabled due to excessive invalid dword error.
5/2/2022 12:17:46   node2     DEBUG         ds.sas.running.disparity: [HST2] on channels 9d shelf ID 76 IOM B bay - reports running disparity errors.
5/2/2022 12:15:40   node2     DEBUG         ds.sas.running.disparity: [HST2] on channels 9d shelf ID 76 IOM B bay - reports running disparity errors.
5/2/2022 12:15:04   node2     DEBUG         ds.sas.running.disparity: [HST2] on channels 9d shelf ID 76 IOM B bay - reports a running

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.