Search

Troubleshooting port connectivity issues on E-Series arrays
https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Troubleshooting_port_connectivity_issues_on_E-Series_arrays
Applies to E-Series Storage Arrays E-Series Controller Firmware 6.xx E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx SAN Protocols - iSCSI, FC (Fibre Channel), Infiniband, SAS Stor...Applies to E-Series Storage Arrays E-Series Controller Firmware 6.xx E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx SAN Protocols - iSCSI, FC (Fibre Channel), Infiniband, SAS StorageGRID Appliance Issue The is article is intended to assist with port connectivity issues on E-Series Arrays. If there are any questions about the content, contact NetApp Support for assistance. Port connectivity issues can have one of the following symptoms: Performance or delays in data retrieval
What is the difference between online and parallel drive firmware upgrades for E-Series?
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/What_is_the_difference_between_online_and_parallel_drive_firmware_upgrades_for_E_Series
If the drive is not assigned to a volume group or disk pool (or is a standby Hot Spare), then its firmware might be updated by the Online or the Parallel method. If the drive is not assigned to a volu...If the drive is not assigned to a volume group or disk pool (or is a standby Hot Spare), then its firmware might be updated by the Online or the Parallel method. If the drive is not assigned to a volume group or disk pool (or is a standby Hot Spare), then its firmware might be updated by the Online, or the Parallel method. All: You can select All to download firmware to all the drives included in the selection list, regardless of the state of the volume group or disk pool.
E-Series by-passed drive recovery
https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_by-passed_drive_recovery
Error reported by recovery guru: 'Failure Entry 1: BYPASSED_DRIVE-Recovery Failure Type Code: 64' Several possible hardware can cause this issue
How to perform a non-disruptive change between Active-Passive (RDAC) and ALUA host types on E-Series arrays connected to ONTAP 7-Mode systems
https://kb.netapp.com/Legacy/ONTAP/7Mode/How_to_perform_a_non_disruptive_change_between_Active_Passive_RDAC
The following procedure for changing the E-Series host type from RDAC to ALUA must be completed prior to upgrading to 8.25 and later. This article describes a non-disruptive procedure to convert the h...The following procedure for changing the E-Series host type from RDAC to ALUA must be completed prior to upgrading to 8.25 and later. This article describes a non-disruptive procedure to convert the host type on the NetApp E-Series array connected to Data ONTAP systems. You can use this non-disruptive procedure to perform the following for the E-Series arrays connected to the Data ONTAP system:
How to retrieve a core dump on an E-Series storage system
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/How_to_retrieve_a_core_dump_on_an_E-Series_storage_system
Applies to NetApp E-Series Description Caution: Perform this procedure only under the guidance of NetApp Support. Note: Core dump operations can only be performed on E5400, E2700, E5500, E2800, E5700 ...Applies to NetApp E-Series Description Caution: Perform this procedure only under the guidance of NetApp Support. Note: Core dump operations can only be performed on E5400, E2700, E5500, E2800, E5700 and higher Controller models. Retrieve a core dump under the following conditions: If you receive notification of a Major Event Log (MEL) event that a core dump has been automatically generated. If you generate a core dump manually.
Write-back caching forcibly disabled alert with controller firmware versions 08.25.11.00 and 08.30.20.00
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Write-back_caching_forcibly_disabled_alert_with_controller_firmware_versions_08.25.11.00_and_08.30.20.00
Applies to E-Series Controller Firmware 8.xx E-Series Platforms: E2700, E5500, E5600, EF550 and EF560 Issue Check Active IQ if this impacts your systems An AutoSupport case is generated for “Write-bac...Applies to E-Series Controller Firmware 8.xx E-Series Platforms: E2700, E5500, E5600, EF550 and EF560 Issue Check Active IQ if this impacts your systems An AutoSupport case is generated for “Write-back caching forcibly disabled”. If AutoSupport is not enabled, the issue can be identified by storage array being in a Needs Attention state with an entry in the Recovery Guru (SANtricity) for Write-back caching forcibly disabled.
How to decode MEL event 2044: IO shipping implicit volume transfer
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/How_to_decode_MEL_event_2044__IO_shipping_implicit_volume_transfer
Applies to E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx SANtricity Description E-Series MEL event 0x2044 occurs when IO shipping has resulted in an implicit volume transfer. The...Applies to E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx SANtricity Description E-Series MEL event 0x2044 occurs when IO shipping has resulted in an implicit volume transfer. There is additional data in the MEL raw data that can be decoded for additional information about the event.
Potential E-Series system performance degradation during SSD internal NAND recovery
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Potential_E-Series_system_performance_degradation_during_SSD_internal_NAND_recovery
Users may experience performance degradation during internal die (NAND) recovery. An SSD drive is composed of many dies (NANDs) that are equal in size. The size of a die (NAND) may vary depending on t...Users may experience performance degradation during internal die (NAND) recovery. An SSD drive is composed of many dies (NANDs) that are equal in size. The size of a die (NAND) may vary depending on the drive model. Drive returned check condition with SENSE data of 1/18/0 and/or 1/18/ff indicate the drive is undergoing an internal recovery (reconstruction) of a die. The drive returned check conditions can be found in the E-Series system event log: Description: Drive returned CHECK CONDITION
How to upgrade E-Series ESM (IOM) Firmware 07.xx and 08.xx CFW
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/How_to_upgrade_E_Series_ESM_IOM_Firmware_07_xx_and_08_xx_CFW
Applies to E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx Description This article describes the procedure to upgrade E-Series ESM (IOM) (Environment Services Module (Input/Output...Applies to E-Series Controller Firmware 7.xx E-Series Controller Firmware 8.xx Description This article describes the procedure to upgrade E-Series ESM (IOM) (Environment Services Module (Input/Output Module)) Firmware.
What are Linux host operating system considerations when using SCSI UNMAP with E-Series thin volumes
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/What_are_Linux_host_operating_system_considerations_when_using_SCSI_UNMAP_with_E-Series_thin_volumes
UNMAP is a SCSI command that can be issued to the storage array by a host system to reclaim space on a thin volume after disk blocks have been deleted by an application or OS. The Storage Administrati...UNMAP is a SCSI command that can be issued to the storage array by a host system to reclaim space on a thin volume after disk blocks have been deleted by an application or OS. The Storage Administration Guide topic 'Freeing Unused Filesystem Blocks' recommends running /sbin/wiper.sh weekly to batch the unmap activity; see SUSE Doc Storage Administration Guide
E-Series reporting degraded drive channel on single drive
https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_reporting_degraded_drive_channel_on_single_drive
Recovery GURU reports the following: DEGRADED_DRIVE_CHANNEL-Recovery Failure Type Code: 71 and similar other entries. This KB provides information on what causes this issue and the solution for this i...Recovery GURU reports the following: DEGRADED_DRIVE_CHANNEL-Recovery Failure Type Code: 71 and similar other entries. This KB provides information on what causes this issue and the solution for this issue.