Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • EMS log reports the event "sas.port.down:warning"
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/EMS_log_reports_the_event_sas_port_down_warning
      [?] Mon Jun 01 20:49:22 CEST [node_name: pmcsas_intrd: sas.port.down:warning]: SAS port "0b" went down. [?] Mon Jun 01 20:49:40 CEST [node_name: dsa_worker5: ses.IOMLogCrash:debug]: Encountered a cras...[?] Mon Jun 01 20:49:22 CEST [node_name: pmcsas_intrd: sas.port.down:warning]: SAS port "0b" went down. [?] Mon Jun 01 20:49:40 CEST [node_name: dsa_worker5: ses.IOMLogCrash:debug]: Encountered a crash in Exception Log on IOM module B SN [serial_number] FW 0181, channel 0b.03.99 shelf ID 3 shelf SN [serial_number]. [?] Mon Jun 01 20:49:49 CEST [node_namee: pmcsas_timeout_0: sas.cable.degraded:warning]: Cable attached to SAS port "0b" is functioning in a degraded mode.
    • E-Series How to map LSI/Avago based SAS adapters in Auto port mode
      https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E_Series_How_to_map_LSI_Avago_based_SAS_adapters_in_Auto_port_mode
      SAS based hosts can lose the data path to the array due to SAS ports to change and to come up in different order. Each SAS port exist of four single ports, each port has it's own SAS address. SAS HBA'...SAS based hosts can lose the data path to the array due to SAS ports to change and to come up in different order. Each SAS port exist of four single ports, each port has it's own SAS address. SAS HBA's should operate in Wide mode by default but native SAS LSI/Avago Host Bus Adapters (HBA) operate in default Auto port mode instead. This causes indicator to host mapping to fail as the mapping is based on the SAS port address.
    • ONTAP - How to re-enable a disabled SAS port
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/ONTAP_-_How_to_re-enable_a_disabled_SAS_port
      Applies to ONTAP 9 Description This procedure enables a SAS port that has been disabled The port may have been disabled during troubleshooting to stop port flapping The disabled port will carry over a...Applies to ONTAP 9 Description This procedure enables a SAS port that has been disabled The port may have been disabled during troubleshooting to stop port flapping The disabled port will carry over across reboots and SAS card swaps The port will show offline both at the Cluster prompt and in Maintenance Mode
    • How to map SAS cable connecting to which port on IOM3/IOM6 from command line
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_map_SAS_cable_connecting_to_which_port_on_IOM3_IOM6_from_command_line
      Applies to DS2246 DS4243 DS4246 DS4486 I/O Module (IOM) 3 I/O Module (IOM) 6 Description This article explains how to map SAS cable connecting to which port on IOM3/IOM6 from command line.
    • SAS port offline on ATTO bridge
      https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/SAS_port_offline_on_ATTO_bridge
      Applies to ATTO7500N Issue One of the SAS links on the ATTO bridge goes down. The following health alert is observed: Health Monitor process schm: StorageBridgePortDown_Alert
    • SAS ADAPTER INITIALIZATION FAILED alert reported in EMS logs
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SAS_ADAPTER_INITIALIZATION_FAILED_alert_reported_in_EMS_logs
      SAS adapter initialization failed error is reported in the EMS logs along with firmware fault and the SAS adapter is taken offline: Mon Feb 21 14:56:06 +0530 [NODE03: pmcsas_asyncd_1: sas.adapter.exce...SAS adapter initialization failed error is reported in the EMS logs along with firmware fault and the SAS adapter is taken offline: Mon Feb 21 14:56:06 +0530 [NODE03: pmcsas_asyncd_1: sas.adapter.exception:debug]: SAS adapter driver encountered error "Failed to Reset" on adapter 0c. Mon Feb 21 14:56:06 +0530 [NODE03: pmcsas_asyncd_1: callhome.sas.init.failed:error]: Callhome for SAS ADAPTER INITIALIZATION FAILED, Port: .
    • System is in mixed path due to fault seen on SAS HBA
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/System_is_in_mixed_path_due_to_fault_seen_on_SAS_HBA
      Applies to NetApp AFF and FAS systems ONTAP 9 Issue Drives are missing a path to the node due to a faulty port on a SAS card Shelf stack is not seen through IO Module A/B and drives connected through ...Applies to NetApp AFF and FAS systems ONTAP 9 Issue Drives are missing a path to the node due to a faulty port on a SAS card Shelf stack is not seen through IO Module A/B and drives connected through IO Modules A/B are not seen by the Node, refer to the additional information section
    • The SAS port went down followed by a software crash of the IOM modules
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/The_SAS_port_went_down_followed_by_a_software_crash_of_the_IOM_modules
      Sun Apr 20 04:50:35 [node01: storlog_admin: sla.shelf.mod.reboot.unexp:error]: Unexpected reboot event reported by module B in shelf: 3b.01.99.1, log: Thu Jan 1 00:00:00 1970 ( 0+00:00:00.191); 020000...Sun Apr 20 04:50:35 [node01: storlog_admin: sla.shelf.mod.reboot.unexp:error]: Unexpected reboot event reported by module B in shelf: 3b.01.99.1, log: Thu Jan 1 00:00:00 1970 ( 0+00:00:00.191); 02000093; U?; HAL; hal; 04; Module Reboot: Startup type 5-Crash reset
    • HOST PORT FAIL Disabled due to excessive invalid dword error - Autosupport Message
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/HOST_PORT_FAIL_Disabled_due_to_excessive_invalid_dword_error_-_AutoSupport_Message
      Disk shelf fault LED is on, and EMS log shows error information about disk shelf. There could be  multiple possible causes and requires further analysis to identify a port or SAS cable issue