Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_replacement_controller_does_not_complete_boot_up_process
      After a Controller Replacement the replacement controller does not complete Start-Of-Day (SOD). 05/27/22-13:28:41 (sntpEventTask): NOTE: sntpEventHandler:SOD not complete; skipping NTP sync. 05/27/22-...After a Controller Replacement the replacement controller does not complete Start-Of-Day (SOD). 05/27/22-13:28:41 (sntpEventTask): NOTE: sntpEventHandler:SOD not complete; skipping NTP sync. 05/27/22-13:29:04 (tRAID): NOTE: ACS: autoCodeSync(): Waiting for Dom0 image transfer to complete. The Alternate original Controller will show the following during the SOD process for the replacement: 05/27/22-11:12:49 (iacTask5): NOTE: ACS: Acs Needed on Alt: Yes, StateCode: 1, ReasonCode = 4
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_controller_replacement__fails_when_running_SANtricity_OS_11.70.4x
      Simplex E-Series (i.e SG57xx) replacement where the original controller was running 11.70.4x or higher but replacement is running pre-11.70.4x 02/02/23-17:55:54 (tRAID): WARN: void acs::Image::determi...Simplex E-Series (i.e SG57xx) replacement where the original controller was running 11.70.4x or higher but replacement is running pre-11.70.4x 02/02/23-17:55:54 (tRAID): WARN: void acs::Image::determineDiskBlockSize(acs::Image::ExtentList&): Could not find a drive to set the block size 02/02/23-17:55:54 (tRAID): WARN: UINT32 acs::Image::getDiskBlockSize() const: DISK_BLOCK_SIZE has not been set yet!
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Autocode_synchronization_drive_image_write_failure_after_enabling_FDE
      Applies to E-Series Issue Customer reported multiple instances of ACS, Autocode synchronization, drive image write failure messages in MEL after FDE enabled on multiple Volume Groups. Example MEL entr...Applies to E-Series Issue Customer reported multiple instances of ACS, Autocode synchronization, drive image write failure messages in MEL after FDE enabled on multiple Volume Groups. Example MEL entries: Autocode synchronization drive image write failure. Drive image write retry exhausted
    • https://kb.netapp.com/Cloud/Astra/Trident/How_to_setup_regular_CSI_snapshots_on_Trident_provided_PV_ONTAP_volumes
      Astra Control Center (ACC) and the "in the cloud" version called Astra Control Service (ACS) provide the possibility to create scheduled CSI-Snapshot backups on the provided PVs, including the option ...Astra Control Center (ACC) and the "in the cloud" version called Astra Control Service (ACS) provide the possibility to create scheduled CSI-Snapshot backups on the provided PVs, including the option to transfer to a mirror or vault destination, and create a PVC of a Snapshot, or even a pod clone. the existance of CSI Snapshots block the removal of the PVC until the CSI Snapshots are removed