Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/One_or_more_1_PHYs_on_expander_0_11a222_333333b_cc_are_in_a_bad_state
      PHYs on expander are in a bad state and the following events are reported: [Node-01: pmcsas_timeout_0: sas.adapter.debug:info]: params: {'adapterName': '0a', 'debug_string': 'One or more (1) PHYs on e...PHYs on expander are in a bad state and the following events are reported: [Node-01: pmcsas_timeout_0: sas.adapter.debug:info]: params: {'adapterName': '0a', 'debug_string': 'One or more (1) PHYs on expander 5:00a098:0081de3:3f are in a bad state.'} The output of storage show fault reports a disk status as noncritical: The STORAGE-SHELF section of the autosupport reports unknown status for the affected disk: Id State Value (ms) (Gb/s) Count Count Count Problem Count Count
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/AutoSuppor_reports_DualControllerHa_Alert_ALERT
      Applies to ONTAP 9 Issue ADualControllerHa_Alert ALERT: Example: hostname (Health Monitor process schm: DualControllerHa_Alert[ ]) ALERT PHYs on expander are in a bad state: Example [hostname: pmcsas_...Applies to ONTAP 9 Issue ADualControllerHa_Alert ALERT: Example: hostname (Health Monitor process schm: DualControllerHa_Alert[ ]) ALERT PHYs on expander are in a bad state: Example [hostname: pmcsas_timeout_3: sas.adapter.debug:info]: params: {'debug_string': 'One or more (1) PHYs on expander are in a bad state.', 'adapterName': '0c'}