Attention MDR Customers: New Case Submission Flow

As of March 18, 2025, there is an updated process flow to submit MDR-related cases. Please visit this article for details.

Views:

SPFS

Both issues are caused by the client IP sent from Netapp as always 0.0.0.0. Netapp should send the user IP address as the client IP to SPFS.

This issue has been fixed by Netapp patch release.

Keywords: SPFS,integration issues,integration problems,Fxs,FSx,Netapp ONTAP,Netapp issue,client IP 0000,IP 0.0.0.0

Issues encountered when integrating Server Protect For Storage (SPFS) with FSX for NetApp ONTAP

ServerProtect For Storage6.0

Last updated: 2023/02/23

Solution ID: KA-0013154

Category: Configure

This article will discuss the resolution for the following issues:

The User Name in Storage Scan Result tab would always be 0.0.0.0, while it should be the Internet Protocol (IP) address of the user who caused a virus-infection on the Storage server.
The user who caused a virus-infection cannot see the warning message box when “Notify a device client upon infection” is enabled.

SPFS

Both issues are caused by the client IP sent from Netapp as always 0.0.0.0. Netapp should send the user IP address as the client IP to SPFS.

This issue has been fixed by Netapp patch release.

Was this article helpful?