Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 23 results
    • https://kb.netapp.com/Support/NSS/System_Registration
      System Registration Other Resources Recently Created Recently Updated
    • https://kb.netapp.com/Support/NSS/Licensing
      Licensing Other Resources Recently Created Recently Updated
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/High_latency_in_VM
      Applies to MetroCluster IP Issue High latency found for VM (virtual machines) whose data is stored in MetroCluster LUNs Multiple VM affected After node reboot, latency is in a good range but increases...Applies to MetroCluster IP Issue High latency found for VM (virtual machines) whose data is stored in MetroCluster LUNs Multiple VM affected After node reboot, latency is in a good range but increases again (can take weeks)
    • https://kb.netapp.com/Support/NSS/Installed_Products
      Installed Products Other Resources Recently Created Recently Updated
    • https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/Unable_to_view_details_for_FSx_working_environment_in_BlueXP
      Applies to BlueXP Amazon FSx for NetApp ONTAP Issue Error when loading FSx in BlueXP:
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/HA_Group_Notification_from_Write_Verification_Error__Port_0m_0v_Failed_EMERGENCY
      Applies to MetroCluster IP NetApp validated IP switches Issue EMS log entries like: HBAFLD:HA Group Notification from [Node name] (Write Verification Error: Port 0m Failed) EMERGENCY HBAFLD:HA Group N...Applies to MetroCluster IP NetApp validated IP switches Issue EMS log entries like: HBAFLD:HA Group Notification from [Node name] (Write Verification Error: Port 0m Failed) EMERGENCY HBAFLD:HA Group Notification from [Node name] (Write Verification Error: Port 0v Failed) EMERGENCY
    • https://kb.netapp.com/Support/NSS/AutoSupport
      AutoSupport Other Resources Recently Created Recently Updated How to enable AutoSupport for each NetApp ProductTue, 25 Jul 2023 How are SAP IB records updated by incoming AutoSupport messages?Fri, 09 ...AutoSupport Other Resources Recently Created Recently Updated How to enable AutoSupport for each NetApp ProductTue, 25 Jul 2023 How are SAP IB records updated by incoming AutoSupport messages?Fri, 09 Jun 2023 How to enable AutoSupport for each NetApp ProductThu, 17 Aug 2023 How are SAP IB records updated by incoming AutoSupport messages?Fri, 09 Jun 2023
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/CRC_errors_on_Broadcom_switch
      CRC errors on node port: Total frames: 1217k | Frames/second: 1214 | Total bytes: 4821m Bytes/second: 4807k | Total errors: 72 | Errors/minute: 4 CRC errors: 72 | Runt frames: 0 | Fragment: 0 Bad UDP6...CRC errors on node port: Total frames: 1217k | Frames/second: 1214 | Total bytes: 4821m Bytes/second: 4807k | Total errors: 72 | Errors/minute: 4 CRC errors: 72 | Runt frames: 0 | Fragment: 0 Bad UDP6 cksum: 0 | Bad TCP cksum: 0 | Bad TCP6 cksum: 0 Mcast v6 solicit: 0 | Lagg errors: 0 | Lacp errors: 0 Total frames: 936k | Frames/second: 934 | Total bytes: 1578m HW UDP6 cksums: 0 | HW TCP cksums: 769k | HW TCP6 cksums: 0 RX errors in peer port (switch): 0/11 0/11-Lane1 N/A N/A N/A N/A N/A N/A N/A
    • https://kb.netapp.com/Support/NSS/Support_Site
      Support Site Other Resources Recently Created Recently Updated
    • https://kb.netapp.com/Support/NSS/Entitlement
      Entitlement Other Resources Recently Created Recently Updated
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Unable_to_delete_Oracle_clone_after_SC_4.8_upgrade
      Applies to SnapCenter Server (SC) 4.8 SnapCenter Plug-in for Oracle (SCO) 4.8 Microsoft Defender Antivirus Issue Unable to delete Oracle clones after upgrading to SnapCenter 4.8 The following error is...Applies to SnapCenter Server (SC) 4.8 SnapCenter Plug-in for Oracle (SCO) 4.8 Microsoft Defender Antivirus Issue Unable to delete Oracle clones after upgrading to SnapCenter 4.8 The following error is seen when trying to delete a clone: Failed to unmount the filesystem '<Clone_Name>', reason: umount: <Clone_Name>: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))