Tenant scope event. Tenant {{TenantName}} (ID={{TenantId}}): {{generalEventText}}.

The user {{username}} paused the replication from {{replicationSource}} to {{replicationDestination}}.

The user {{username}} resumed the replication from {{replicationSource}} to {{replicationDestination}}.

The user {{username}} started immediate replication from {{replicationSource}} to {{replicationDestination}}.

The user {{username}} detached the destination NAS volume {{replicationDestination}} from source NAS volume {{replicationSource}}.

The user {{username}} attached the destination NAS volume {{replicationDestinationVolume}}@{{replicationDestinationCluster}} to NAS volume {{replicationSourceVolume}}.

NAS Volume scope event. NAS Volume {{VolumeName}} (ID={{FSID}}): {{generalEventText}}.

The user {{username}} added a new replication partner named {{trustedCluster}}.

The user {{username}} updated the replication partner configuration for {{trustedCluster}}.

The user {{username}} removed the cluster {{trustedCluster}} from the list of replication partners.

{{packageName}} bundle installation completed successfully.

Firmware DellFluidFS-{{spVersion}} installation started   Description:  Firmware DellFluidFS-{{spVersion}} installation started   Action Items:  You should follow the installation process in the CLI / WUI and the event log to verify it successfully completes

Firmware DellFluidFS-{{spVersion}} failed to install.   Description:  Firmware DellFluidFS-{{spVersion}} failed to install, reason: {{spError}}.   Action Items:  System may be in inconsistent state, please check system validation in CLI / WUI.[[nl]]If system is in unstable state (i.e. some controllers are reported down) then escalate to resolve the situation.

Successfully upgraded to firmware DellFluidFS-{{spVersion}}.

{{generalEventText}}

{{generalEventText}}

{{generalEventText}}

{{generalEventText}}

{{username}} cancelled the replication from {{replicationSource}} to {{replicationDestination}}.

Replication-policy of NAS volumes {{replicationSource}} and {{replicationDestination}} was disabled.   Description:  The user {{username}} disabled the replication-policy of the destination NAS volume {{replicationDestination}} and the source NAS volume {{replicationSource}}.

Replication-policy of NAS volumes {{replicationSourceVolume}} and {{replicationDestinationVolume}} was enabled.   Description:  The user {{username}} enabled replication: re-attached NAS volume {{replicationDestinationVolume}} on cluster {{replicationDestinationCluster}} to local NAS volume {{replicationSourceVolume}}.

The user {{username}} logged in to {{ui}}.

Format failed during execution of File System Structures Initialization phase.   Internal Information:  mkfs.sh failed with error code {{ErrCode}}

Incremental Format failed during execution of File System Structures Initialization phase.   Internal Information:  mkfs.sh failed with error code {{ErrCode}}

Auto attach of NAS controller {{controllerId}} in appliance {{applianceId}} has started.   Action Items:  You should follow the attachment process in the CLI / WUI to verify it successfully completes.

Auto detach of NAS controller {{controllerId}} in appliance {{applianceId}} has started.   Action Items:  You should follow the detachment process in the CLI / WUI to verify it successfully completes.

Create of NAS Appliance {{applianceId}} ({{applianceServiceTag}}) has started.   Action Items:  You should follow the appliance create process in the CLI / WUI to verify it successfully completes.

Escalation access was enabled for {{escalationPeriodInMinutes}} minutes.

User {{username}} created {{objectName}} exceeding the maximum recommended count {{recommendedMaxCount}}.

Attach of NAS controller {{controllerId}} has started by {{username}}.

Attach of NAS controller {{controllerId}} has completed successfully.

Detach of NAS controller {{controllerId}} was started by {{username}}.

Detach of NAS controller {{controllerId}} has completed successfully.

Join of NAS Appliance {{applianceId}} was started by {{username}}.   Action Items:  You should follow the appliance join process in the CLI / WUI to verify it successfully completes.

Join of NAS Appliance {{applianceId}} has completed successfully.

Antivirus host {{host}}:{{port}} accessibility is restored.   Description:  Antivirus host {{host}}:{{port}} accessibility is restored.

Antivirus host {{host}}:{{port}} is not accessible.   Description:  Antivirus host {{host}}:{{port}} is not accessible.

Antivirus host {{host}}:{{port}} returns license error.   Description:  Antivirus host {{host}}:{{port}} returns license error.

No antivirus hosts are accessible.   Description:  No antivirus hosts are accessible. Virus scanning is not possible. SMB Shares with AV scan configured will not be accessible.

AntiVirus servers are not configured.   Description:  SMB share {{shareName}} is configured to use antivirus checking but no AV servers are configured yet. Access to the files inside the share is denied.   Action Items:  AntiVirus servers must be configured to provide AntiVirus facility

Antivirus scan for file {{FSIDName}}/{{dsidPath}} took too long   Description:  Scanning for viruses for file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} took too long: {{scanningDuration}} seconds (must be less than {{scanningDurationThreshold}}), scanning facility '{{scanningFacility}}'.   Action Items:  Please check network availability and current load on problematic AntiVirus facility.

Virus was found in file {{FSIDName}}/{{dsidPath}} but quarantine is not applicable.   Description:  Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Quarantine action is not possible for this file, access to file is denied.   Internal Information:  Reason why quarantine action is not possible: {{accessDeniedReason}}

An error occurred while scanning the file {{FSIDName}}/{{dsidPath}} for viruses.   Description:  An error occurred during AV scan of the file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Access to file is denied.   Internal Information:  Error details: {{accessDeniedReason}}

Error occurred while scanning for viruses.   Description:  AV server returned unexpected error during the scan for file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Access is denied.   Internal Information:  ICAP protocol issue: unexpected ICAP status code {{icapStatus}} returned by facility {{server}}:{{port}}

Virus was found in file {{FSIDName}}/{{dsidPath}} but quarantine action has failed.   Description:  Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Quarantine action failed for this file, access to file is denied.   Internal Information:  Quarantine action error details: {{accessDeniedReason}}

Virus was found in file {{FSIDName}}/{{filePath}}, quarantine action is applied.   Description:  Virus ({{virusDescription}}) was found in file {{filePath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. File is moved to quarantine (new path is {{dsidPath}}).

Infected file {{FSIDName}}/{{dsidPath}} was repaired.   Description:  Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. The file was repaired automatically.

Access denied: file {{FSIDName}}/{{dsidPath}} is too large for AV verification.   Description:  File {{dsidPath}} (which is {{fileSizeMb}} MB) on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} cannot be scanned for viruses because it exceeds the maximum scan size ({{largeFileSizeLimitMb}} Mb). This share is configured to block access to un-scanned files.   Action Items:  Increase the maximum scan size for AV scanning or change the policy to allow un-scanned files for access. Please note, Anti-virus scan of large files may delay the initial open request.

Access allowed: file {{FSIDName}}/{{dsidPath}} was opened without AV verification.   Description:  File {{dsidPath}} (which is {{fileSizeMb}} MB) on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} was not scanned for viruses because it exceeds the maximum scan size ({{largeFileSizeLimitMb}} MB).   Action Items:  Increase the maximum file size for AV scan or change the policy to deny un-scanned files for access. Please note, Anti-virus scan of large files may delay the initial open request.

NFS user {{nfsUserName}} access to a file denied. Insufficient permissions.   Description:  NFS access denied: user {{nfsUserName}} does not have sufficient permissions for the file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}. Desired/granted access mask: {{desiredNfsAccessMaskHrf}} / {{grantedNfsAccessMaskHrf}}.    Internal Information:   {{internalInfo}}

NFS access denied. Attempt to modify a read-only export {{nfsExport}}.   Description:  NFS Access Denied: User {{nfsUserName}} accessing from {{clientIpAddr}} tried to perform modifications on a read-only export: {{nfsExport}}, NAS Volume {{nasContainerIdIntegerName}}.    Action Items:  Verify that the relevant export definition of read-only was done intentionally. Contact the user who is responsible for this access or for application access to understand the reason for using read-only export with write operations.

NFS access denied. Secured port must be used; export {{nfsExport}}.   Description:  NFS Access Denied: User {{nfsUserName}} tried to access from {{clientIpAddr}} to a secure export {{nfsExport}}, NAS Volume {{nasContainerIdIntegerName}} using a non secure port {{nfsClientPort}}.    Action Items:  Secure exports require that the client accessing them will use a well-known port (under 1024). This is done as a security measure. Identify the relevant export and the checkbox that marks it as secure/requires secure port.  If there is no need for a secure export (e.g. the network is not public) make the export insecure by unchecking the secure export option and try again.  If the export must remain secure, please refer to the NFS client documentation in order to change the currently used NFS client port to a well-known port (under 1024).

Access denied. Attempt to modify a read-only NAS volume {{nasContainerIdIntegerName}}.   Description:  Access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to modify the file {{dsidPath}} with operation '{{nfsOp}}' on a read-only NAS volume {{nasContainerIdIntegerName}}.

Access denied. Attempt to modify a snapshot; NAS volume {{nasContainerIdIntegerName}}.   Description:  Access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to modify the file {{dsidPath}} on NAS volume {{nasContainerIdIntegerName}} that is located in a snapshot.   Action Items:  Snapshot is an exact representation of the NAS volume data at the time of the snapshot creation. For that reason, and by definition, snapshot data can't be modified.  Contact the user and instruct him to limit any modifications to the current work area in the NAS volume.

NFS access denied. Operation not permitted on {{volumeStyle}} volume {{nasContainerIdIntegerName}}.   Description:  NFS access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to '{{nfsOp}}' on a {{volumeStyle}} NAS volume {{nasContainerIdIntegerName}}, file {{dsidPath}}. [[nl]] Choosing a volume security style dictates which protocol will be used to set permissions on files in this volume. This also sets certain limitations on operations which are not allowed for this security style: [[nl]]1.  Setting an ACL for a file in a NAS volume defined with UNIX  Security style. [[nl]]2.  Setting mode for a file in a NAS volume defined with NTFS Security style. [[nl]]3.  Changing the read-only flag for a file in a NAS volume defined with UNIX  Security style. [[nl]]4.  Setting SID/GSID ownership on UNIX Security style [[nl]]5.  Setting UID/GID ownership on NTFS Security style. [[nl]]A user might try to perform one of the above actions and get an 'Access denied' error without understanding why.   Action Items:  The NAS Volume security style should be chosen according to the main intended usage. If a user needs to perform a security related activity which is forbidden, consider splitting the data into two separate NAS Volumes based on the access pattern.

NFS access denied. User {{nfsUserName}} not owner of file.   Description:  NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't perform owner restricted operation {{nfsOp}} on file {{dsidPath}}, NAS Volume {{nasContainerIdIntegerName}}, file owner {{userOwnerName}} : {{groupOwnerName}}.

NFS access denied. Root privileges needed to give ownership.   Description:  NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't give ownership away by operation {{nfsOp}} on file {{dsidPath}} to {{userOwnerName}} because root privileges are required for that, NAS Volume {{nasContainerIdIntegerName}}.

NFS access denied. Root privileges needed to give ownership.   Description:  NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't give ownership away by operation {{nfsOp}} on file {{dsidPath}} to {{groupOwnerName}} because root privileges are required for that, NAS Volume {{nasContainerIdIntegerName}}.

NFS access denied. File and group owner are inconsistent.   Description:  NFS Access Denied: both file owner and group owner must be from the same identity type (NTFS vs UNIX), attempt to set different identity types was detected.  Client {{clientIpAddr}} User: {{nfsUserName}}, file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}, setting ownership: {{userOwnerName}} ({{userIdentityType}}) : {{groupOwnerName}} ({{groupIdentityType}}).   Action Items:  It is impossible to change file owner id to UID if the original file ownership is SID/GSID. If the user wants to change the ownership of the file to UNIX ownership, he must set UID and GID at same time. For example:  user chown michael:group and not chown michael.

SMB access denied. Operation not permitted on {{volumeStyle}} volume.   Description:  Access Denied: User {{nfsUserName}} tried to '{{nfsOp}}' on a {{volumeStyle}} NAS Volume {{nasContainerIdIntegerName}}, file {{dsidPath}}. [[nl]]Choosing a volume security style dictates which protocol will be used to set permissions on files in this volume. This also sets certain limitations on operations which are not allowed for this security style: [[nl]]1.  Setting an ACL for a file in a NAS volume defined with UNIX  Security style. [[nl]]2.  Setting mode for a file in a NAS volume defined with NTFS Security style. [[nl]]3.  Changing the read-only flag for a file in a NAS volume defined with UNIX  Security style. [[nl]]4.  Setting SID/GSID ownership on UNIX Security style [[nl]]5.  Setting UID/GID ownership on NTFS Security style. [[nl]]A user might try to perform one of the above actions and get an 'Access denied' error without understanding why.   Action Items:  The NAS Volume security style should be chosen according to the main intended usage.  If a user needs to perform a security related activity which is forbidden, consider splitting the data into two separate NAS Volumes based on the access pattern.

Share {{cifsShare}} ACL's denied access to user {{userName}}.   Description:  Connection for user '{{userName}}' to share {{cifsShare}} denied due to share ACL permissions, client {{clientIpAddr}}, NAS Controller {{nasControllerId}}, NAS Volume {{nasContainerIdIntegerName}}.

Access denied.  Insufficient permissions, user {{userName}}.   Description:  Access denied on '{{cifsOp}}' operation.  Desired access mask: {{desiredCifsAccessMaskName}}, missing bits: {{missedCifsAccessBitsName}}, client: {{clientIpAddr}}, user: {{userName}}, file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}.   Internal Information:   {{internalInfo}}

Write Access to pseudo-fs of {{TenantName}}, user {{userName}}.   Description:  Write Access denied to user {{userName}}. Attempted modification of NFS4 Pseudo File System of {{TenantName}}). Client IP: {{clientIpAddr}}.