Search

Auto code synchronization failed OE: Operational Error L5: ACS failure
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Auto_code_synchronization_failed_OE__Operational_Error_L5__ACS_failure
Applies to StorageGRID appliances SG5600 and SG5700 NetApp E-Series Simplex (Single controller) Configurations Issue Controller 7-segment LED showing OE L5
Unable to reclaim space from a thin provision volume
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Unable_to_reclaim_space_from_a_thin_provision_volume
When trying to reclaim deleted blocks or space from E-Series thin provisioned volume, space is not reclaimed and the host SCSI UNMAP operation returns with an error. SCSI UNMAP was first introduced in...When trying to reclaim deleted blocks or space from E-Series thin provisioned volume, space is not reclaimed and the host SCSI UNMAP operation returns with an error. SCSI UNMAP was first introduced in E-Series controller firmware starting 8.25.05, which means deleted blocks will not be reclaimed on a volume that was created prior to this release. Once the controller firmware level support this feature, SCSI UNMAP should be enabled on each thin-provisioned volume created prior to 8.25.05.
E-Series how to download SANtricity OS to a controller in lockdown state
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_how_to_download_SANtricity_OS_to_a_controller_in_lockdown_state
Applies to NetApp E-Series SANtricity System Manager Description This article describes the procedure to use upgrade SANtricity OS of an E-Series controller in Lockdown state.
E-Series Upgrade Pre-Check Fails due to "Too many Page 2C Events"
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_Upgrade_Pre_Check_Fails_due_to_Too_many_Page_2C_Events
Applies to NetApp E-Series Issue When attempting to upgrade Controller Firmware, a message indicating too many page 2c events is displayed, and the firmware upgrade does not continue. In the Health ch...Applies to NetApp E-Series Issue When attempting to upgrade Controller Firmware, a message indicating too many page 2c events is displayed, and the firmware upgrade does not continue. In the Health check logs we can see the entry: {"result":"failed","type":"melEventCheck","severityLevel":"medium","resultsData":"","warningMessages":["Too many page 2C events","Too many destination driver events"],"successful":false},"dbSubRecordsValidation":
E-Series failed disk pool volumes on pre-8.40.40.00/8.52.00.00 releases due to power or connectivity issues
https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_failed_disk_pool_volumes_on_pre-8.40.40.00_or_8.52.00.00_releases_due_to_power_or_connectivity_issues
Applies to NetApp E-Series Dynamic Disk Pool (DDP) Controller Platforms: E26xx, E54xx, E55xx, E56xx, E28xx, E57xx and all associated EF-Series SANtricity OS Controller Software pre- 8.40.40.00 (11.40....Applies to NetApp E-Series Dynamic Disk Pool (DDP) Controller Platforms: E26xx, E54xx, E55xx, E56xx, E28xx, E57xx and all associated EF-Series SANtricity OS Controller Software pre- 8.40.40.00 (11.40.4 ; Not Equal) SANtricity OS Controller Software pre- 8.52.00.00 (11.50.2; Not Equal) All other prior family releases: 8.30, 8.25 and 8.20 Issue Failed volumes in DDP due to one of the following conditions: Power outage Loss of connectivity to external drive trays
E-Series controller hits panic while deleting initiator entry for the host
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_Controller_hits_panic_while_deleting_initiator_entry_for_the_host
E-Series The controller resets in the MAJOR-EVENT-LOG: B:5/21/20, 8:54:20 PM (20:54:20) 886 4010 Controller reset - Shelf 99, Bay B ----> Reboot Reason : REBOOT_VKI_SIGSEGV The Core dump has been capt...E-Series The controller resets in the MAJOR-EVENT-LOG: B:5/21/20, 8:54:20 PM (20:54:20) 886 4010 Controller reset - Shelf 99, Bay B ----> Reboot Reason : REBOOT_VKI_SIGSEGV The Core dump has been captured as the controller rebooted in the excLogShow of the STATE-CAPTURE-DATA: ---- Log Entry #0 (Core 0) Apr-30-2020 02:26:31 AM ---- WARNING: Reset by alternate controller ---- Log Entry #1 (Core 0) May-21-2020 02:55:30 PM ---- 2020-05-21 20:53:30.227168 SIGSEGV Received
How to upgrade E-Series SANtricity firmware using SANtricity System Manager (SAM)
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/How_to_upgrade_E_Series_SANtricity_firmware_using_SANtricity_System_Manager_SAM
Several storage array components contain software or hardware that you might want to upgrade occasionally. This KB articles describes in detail, how to upgrade controller firmware, IOM, and NVSRAM usi...Several storage array components contain software or hardware that you might want to upgrade occasionally. This KB articles describes in detail, how to upgrade controller firmware, IOM, and NVSRAM using SANtricity System Manager.
E-Series array not sending AutoSupport displaying "ASUP Upload Host InetSocketAddress is unresolved"
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_Array_Not_Sending_Auto-supports_displaying_ASUP_Upload_Host_InetSocketAddress_is_unresolved
Receive the following error during AutoSupport test (Support > Support Center > AutoSupport > Configure AutoSupport Delivery Method > Test Configuration): The following exceptions are logged in the ma...Receive the following error during AutoSupport test (Support > Support Center > AutoSupport > Configure AutoSupport Delivery Method > Test Configuration): The following exceptions are logged in the management software log web-server-trace-log-A.txt or web-server-trace-log-B.txt in Support Data: 2025-03-12 02:58:13,843 ERROR [SMMonitorTask-4401] trace [ASUPHTTPClient.java:1399] [requestId=0, deviceId=N/A] ASUP Upload Host InetSocketAddress is unresolved.
E-Series controller may reboot due to interaction with Brocade FC switch
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_controller_may_reboot_due_to_interaction_with_Brocade_FC_switch
Applies to E-Series controllers using 16Gb or 32Gb fibre channel host interfaces Controllers running firmware prior to 8.30.4X.XX, 11.30.4, 8.40.1X.XX, and 11.40.1 Brocade FC switch connected to contr...Applies to E-Series controllers using 16Gb or 32Gb fibre channel host interfaces Controllers running firmware prior to 8.30.4X.XX, 11.30.4, 8.40.1X.XX, and 11.40.1 Brocade FC switch connected to controllers In rare cases, a controller may reboot when connected to a Brocade switch and running a controller firmware version less than listed above. Controller may report the following in the exception log: Page Fault errCode: 0 pc: 0xffffffff83a2b87a (with the following contained in the backtrace)
E-Series stale drive recovery status prevents volume reconstruction and redistribution
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_stale_drive_recovery_status_prevents_volume_reconstruction_and_redistribution
Applies to NetApp E-Series NetApp SANtricity OS pre-11.50.3 Issue Users cannot redistribute the volumes in SANtricity Management Software. The following error is returned: Error 825 - operation cannot...Applies to NetApp E-Series NetApp SANtricity OS pre-11.50.3 Issue Users cannot redistribute the volumes in SANtricity Management Software. The following error is returned: Error 825 - operation cannot be completed because a drive is undergoing a service operation Reconstruction started event is reported in the major event log, but no completion status: Disk pool drive reconstruction started
Performance Degradation with Data Assurance enabled Volumes and iSCSI
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Performance_Degradation_with_Data_Assurance_enabled_Volumes_and_iSCSI
11.5x), the Data Assurance (DA; T10 PI) feature is now available with iSCSI on controllers models E28xx and E57xx/EF57x and enabled by default on volumes. Due to a hardware limitation of the QLogic Hi...11.5x), the Data Assurance (DA; T10 PI) feature is now available with iSCSI on controllers models E28xx and E57xx/EF57x and enabled by default on volumes. Due to a hardware limitation of the QLogic Hilda chipset, having DA enabled on an iSCSI volume can cause a performance degradation in read scenarios. When using an iSCSI initiator to issue Reads to an iSCSI volume with DA enabled, you may experience Read performance degradation compared to a non-DA enabled iSCSI volume.