Applies to ONTAP 9 Anti Ransomware Issue When trying to generate attack report, the command failed as below: clus01::> security anti-ransomware volume attack generate-report -volume vol1 -dest-path sv...Applies to ONTAP 9 Anti Ransomware Issue When trying to generate attack report, the command failed as below: clus01::> security anti-ransomware volume attack generate-report -volume vol1 -dest-path svm1:vol1/ -vserver svm1 Error: command failed: Failed to copy report file for volume "vol1" in Vserver "svm1". Reason: Path "svm1:vol1/" does not exist in volume "vol1" in vserver "svm1". clus01::>
HA Group Notification from NETAPP01 (volume1 (UUID: baaa57df-c736-11ea-9401-XXXXXXXXXXXX) vserver1(UUID: 5d7c5692-b755-11e6-a10f-XXXXXXXXXXXX)) ALERT [Node-01: svc_queue_thread: callhome.arw.activity....HA Group Notification from NETAPP01 (volume1 (UUID: baaa57df-c736-11ea-9401-XXXXXXXXXXXX) vserver1(UUID: 5d7c5692-b755-11e6-a10f-XXXXXXXXXXXX)) ALERT [Node-01: svc_queue_thread: callhome.arw.activity.seen:alert]: Call home message for POSSIBLE RANSOMWARE ACTIVITY DETECTED, Volume: volume1 (UUID: baaa57df-c736-11ea-9401-XXXXXXXXXXXX) in Vserver: verver1 (UUID: 5d7c5692-b755-11e6-a10f-XXXXXXXXXXXX)
Applies to ONTAP 9 FabricPool Issue ONTAP loses connectivity to StorageGRID after a failover event on the StorageGRID system ARP tables within ONTAP do not show the accurate MAC address for the active...Applies to ONTAP 9 FabricPool Issue ONTAP loses connectivity to StorageGRID after a failover event on the StorageGRID system ARP tables within ONTAP do not show the accurate MAC address for the active StorageGRID connection: ::> set advanced ::*> network arp active-entry show
Applies to ONTAP Issue After takeover/giveback or upgrade, clients lose network access to resources on the storage controller Some of the LIFs become unreachable via ping The issue resolves by itself ...Applies to ONTAP Issue After takeover/giveback or upgrade, clients lose network access to resources on the storage controller Some of the LIFs become unreachable via ping The issue resolves by itself after a few minutes