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}}.

Access Denied. Open mode conflict; user {{userName}}.   Description:  Access Denied on '{{operation}}' operation due open mode conflict.  Desired access mask: {{desiredCifsAccessMaskName}},  open mode mask: {{openModeAccessBitsName}},  client: {{clientIpAddr}},  user: {{userName}},  file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}.

Access Denied. Conflict with share mode; NAS Volume {{nasContainerIdIntegerName}}.   Description:  Access Denied: User {{userName}} accessing from client {{clientIpAddr}} tried to open file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}, which is opened with conflicting share mode by another user.

Access denied. File marked for deletion; File {{dsidPath}}.   Description:  Access denied: the file is marked for deletion.  Client: {{clientIpAddr}}, user: {{userName}}, file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}.

SMB client login to {{TenantName}} failed. Password expired for user {{userName}}.   Description:  SMB client login failure: Password expired for client {{clientIpAddr}} user name '{{userName}}'. NAS Controller {{nasControllerId}} of {{TenantName}}.

SMB client login to {{TenantName}} failed. The user {{userName}} could not be found.   Description:  SMB client login failure: The login username '{{userName}}' could not be found for client {{clientIpAddr}}. NAS Controller {{nasControllerId}} of {{TenantName}}.

Share-level permissions denied access; share {{cifsShare}}.   Description:  SMB access denied on '{{cifsOp}}' operation: share-level permission applied for the share {{cifsShare}} prohibits such actions. Desired access mask: {{desiredCifsAccessMaskName}}, client: {{clientIpAddr}}, user: {{userName}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}}.

SMB access denied. User {{cifsUser2Name}} has insufficient privileges.   Description:  SMB access denied: accessing user does not have required privileges {{cifsPrivileges}} to perform '{{cifsOp}}', client: {{clientIpAddr}}, user: {{cifsUser2Name}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}}.

SMB access denied. User {{cifsUser2Name}} has insufficient privileges   Description:  SMB access denied: accessing user does not have required privileges {{cifsPrivileges}} to perform '{{cifsOp}}', client: {{clientIpAddr}}, user: {{cifsUser2Name}}, file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}

Missing netgroup '{{netgroupName}}' could not be found by {{TenantName}}.   Description:  Nested netgroup '{{netgroupName}}' of parent netgroup '{{parentNetgroupName}}' was not found while resolving recursive definitions of export access list during NFS mount operation on {{TenantName}}. Missing netgroup was ignored.   Action Items:  Please check the content of the NIS/LDAP external repository and fix the definition of broken netgroup.

Netgroup '{{netgroupName}}' has too many levels of nesting on {{TenantName}}.   Description:  Circular netgroup definitions alert: netgroup has too many levels of nesting. Netgroup '{{netgroupName}}' exceeded the limit of {{netgroupThreshold}} levels of nesting on {{TenantName}}.   Action Items:  Consider reviewing your NIS/LDAP external repository for circular netgroup definitions.

Due to SMB high memory access denied on open file operation   Description:  SMB access denied on open file operation for user: {{cifsUser2Name}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}} due to SMB high memory consumption on NAS controller {{nasControllerId}}.

Due to SMB high resource usage new sessions not allowed.   Description:  Due to SMB high resource usage new sessions are not allowed on NAS controller {{nasControllerId}}.

NFS RPCSECGSS user authentication failure for user {{userName}} on {{TenantName}}.   Description:  NFS RPCSECGSS authentication for user '{{userName}}' failed, client {{clientIpAddr}}, NAS controller {{nasControllerId}} of {{TenantName}}.

Due to SMB too many open files denied open file operation.   Description:   SMB access denied on open file operation due to SMB too many open files on NAS controller {{nasControllerId}}. Allowed number of open files per node is {{maxOpenFilesPerNode}}.

SMB access denied. Extension {{fileExtension}} is denied on share {{cifsShare}}.   Description:  SMB access denied: Extension based access is configured on share {{cifsShare}} on NAS volume {{nasContainerIdIntegerName}}, and extension {{fileExtension}} of file {{nasContainerPath}} is denied. User {{cifsUser2Name}} is not a member of the users groups to be excluded from filtering.

Error on creation home directory for user {{cifsUser2Name}}.   Description:  Auto home directory creation failed for user {{cifsUser2Name}} on NAS volume {{nasContainerIdIntegerName}} with path {{nasContainerPath}}. NT error code {{cifsErrorCode}}.

NFS mount Denied. Path denied {{mountPath}} on subnet {{clusterVIP}}    Description:  NFS client {{clientIpAddr}} was trying to mount NFS export with path {{mountPath}} via cluster VIP {{clusterVIP}} but access from this subnet is not allowed by this NFS export. Access was denied. Client was accessing the export in blind mode that can be considered as security issue.

Access from disallowed subnet to share {{cifsShare}} was denied   Description:  Connection for user '{{userName}}' to share {{cifsShare}} denied because access from this subnet is not allowed by SMB share settings, client {{clientIpAddr}}, NAS Controller {{nasControllerId}}, NAS Volume {{nasContainerIdIntegerName}}.

NFS access denied. Root privileges on export needed for {{operation}}.   Description:  NFS Access Denied: Client {{clientIpAddr}} can't execute operation {{operation}} with volume {{nasContainerIdIntegerName}} because root privileges are required for the client in the relevant NFS export.

FTP user log-in to {{TenantName}} failed   Description:  FTP access to {{TenantName}} from {{clientIpAddr}} is denied for user {{userName}}.   Action Items:  When the client attempts FTP connection but provides bad account details, this event is generated. Possible reasons: wrong password, bad username, disabled anonymous access, account is disabled, password is expired and needs to be changed. The user should verify account details.

FTP user log-in to {{TenantName}} failed due to problematic account   Description:  FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to problematic account   Action Items:  When the client makes FTP connection but provided account has problems, this event is generated. Possible reasons: account is locked, account is expired, logon with this account is disabled. System administrator might provide support to the user to fix the account problem.

FTP user log-in to {{TenantName}} failed due to an internal problem   Description:  FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to internal problem   Internal Information:  {{internalInfo}}

FTP user logged into {{TenantName}}   Description:  FTP client {{clientIpAddr}} user {{userName}} logged into {{TenantName}}   Action Items:  When the client makes FTP connection and successfully logs in, this event is generated

FTP Anonymous user logged into {{TenantName}}   Description:  FTP Anonymous user logged into {{TenantName}} with email {{userEmail}} from {{clientIpAddr}}.   Action Items:  We register an event for every anonymous user logins.

FTP user log-in to {{TenantName}} failed due to wrong TLS version   Description:  FTP client {{clientIpAddr}} log-in to {{TenantName}} failed due to TLS protocol version mismatch   Action Items:  Please make sure FTP client software supports encryption method version TLS 1.{{tlsVersion}}

Reached Maximum FTP connections on NAS controller {{nasControllerId}} of {{TenantName}}. Maximum connection allowed per controller is {{maxConnections}}   Action Items:  This failure is common when there are too many FTP connections to the same fsd.

FTP user log-in to {{TenantName}} failed due to missing landing path   Description:  FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to missing landing directory '{{baseLandingPath}}' on volume {{nasContainerIdIntegerName}}}.   Action Items:  When the client makes FTP connection and successfully logs in but landing directory does not exist, this event is generated. Please create the landing directory.

FTP user log-in to {{TenantName}} failed due to missing home landing path   Description:  FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to missing home directory '{{suffixLandingPath}}' within base landing directory '{{baseLandingPath}}' on volume {{nasContainerIdIntegerName}}   Action Items:  When the client makes FTP connection and successfully logs in but home landing directory does not exist, this event is generated. FTP does not create home folders automatically. Please create them manually.

Reached maximum HDFS connections   Description:  Reached Maximum HDFS connections.   Action Items:  This failure is common when there are too many HDFS connections to the same fsd.

HDFS user name was not found in any of the repositories of {{TenantName}}   Description:  HDFS access from {{clientIpAddr}} provided the user name {{userName}}, but a corresponding user was not found in any of the repositories of {{TenantName}}

Snapshot Access denied by {{TenantName}} due to restriction   Description:  Snapshot access to the HDFS landing directory of NAS Volume {{nasContainerIdIntegerName}} of {{TenantName}} was denied due to '.snapshots' restriction. client: {{clientIpAddr}}, user: {{userName}}, path: '{{baseLandingPath}}'.

GPO Policy was not applied on {{TenantName}}. Took too much time.   Description:  Policy {{policyGuid}} {{policyName}} was not applied on {{TenantName}}. Took to much time.

GPO Policy was not applied on {{TenantName}} due to system error.   Description:  Policy {{policyGuid}} {{policyName}} was not applied on {{TenantName}} due to system error.

GPO Policy was applied successfully on {{TenantName}}.   Description:  Policy {{policyGuid}} {{policyName}} was applied successfully on {{TenantName}}.

GPO Policy on target on {{TenantName}} was not applied due to system error   Description:  Policy {{policyGuid}} {{policyName}} on target {{policyTargetPath}} was not applied due to system error on {{TenantName}}.

GPO Do Not Replace was not applied on {{TenantName}} due to system error.   Description:  Do not replace logic was not applied in Policy {{policyGuid}} {{policyName}} on target {{policyTargetPath}} due to system error on {{TenantName}}.

GPO Policy .inf file read failure on {{TenantName}}.   Description:  {{TenantName}} failed to read the .inf file {{filePath}} of the Policy {{policyGuid}} {{policyName}}

Central Access Policy LDAP query failure on {{TenantName}}.   Description:  LDAP query for Central Access Policy objects {{searchedObjects}} failed on {{TenantName}}.

Central Access Policy rule parsing failure on {{TenantName}}.   Description:  Parsing of the Central Access Policy rule {{ruleDN}} of the policy {{policyDN}} failed on {{TenantName}}.

Central Access policy parsing failure on {{TenantName}}.   Description:  Parsing of the Central Access policy {{policyDN}} failed on {{TenantName}}.

Administrator password was reset from the console.   Description:  Administrator password was reset from the console.

Due to SMB high resource usage disabling Large MTU.   Description:  Due to SMB high resource usage disabling Large MTU on NAS controller {{nasControllerId}}.

Due to SMB high resource usage new connections not allowed.   Description:  Due to SMB high resource usage new connections are not allowed on NAS controller {{nasControllerId}}.

File open or lock denied due to lack of internal resources.   Description:  NAS controller {{nodeId}} is low on resources and cannot serve SMB and NFSv4 file open and lock requests. Disconnect existing connections to free resources.

NFSv4 session was denied. Too many sessions currently in use   Description:  No resources available for new NFSv4 sessions as too many sessions are currently in use. NAS controller {{nodeId}}.

NFS mount failure. Internal mount error {{mountPath}}.   Description:  NFS mount failure: Internal mount error for the client {{clientIpAddr}} while mounting path {{mountPath}}.   Internal Information:   NFS error code: {{nfsErrorCode}}

NFS/SMB partial service   Description:  Access to {{serverKind}} directory service is limited or service is temporary unavailable   Action Items:  This scenario usually happens after directory changes (UNIX database re-configuration, Active Directory join, etc). The problem can occur due poor performance of newly configured directory; please wait some time until new directory will be fully initialized. In case of unexpected or persistent problem please check the operability of directory and network connectivity to directory service. Also problems with '{{service}}' internal service can cause this issue - please check for problematic services.

Security change errors bypassed   Description:  Errors due to chmod/chown/chgrp on volumes with windows security style now bypassed

Security change errors returned   Description:  Errors due to chmod/chown/chgrp on volumes with windows security style now returned

File Access Notifications were dropped.   Description:  {{droppedNotificationsCounter}} File Access Notifications were dropped due to internal issues

File Access Notifications were dropped.   Description:  {{droppedNotificationsCounter}} File Access Notifications were dropped due to auditing server issues

File Access Notification encryption failed   Description:  Failed initializing encrypted connection to the auditing server. encryption credentials configuration may be invalid

NFS mount failure. Wrong port was used for secure export {{nfsExport}}.   Description:  NFS mount failure: Client {{clientIpAddr}} attempted to mount the secure export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}} but used port {{nfsClientPort}} instead of a well-known port (under 1024) on the client side.   Action Items:  Secure exports require that the client accessing them will perform the mount using a well-known port (under 1024). This is done as a security measure.

NFS mount failure. The path {{mountPath}} is not exported by {{TenantName}}.   Description:  NFS mount failure: Client {{clientIpAddr}} attempted to mount the path ({{mountPath}}) from {{TenantName}} which is not exported to NFS clients.   Action Items:   This failure is commonly caused by spelling mistakes done on the client machine or when accessing the wrong server. List all available exports on the NAS and verify everything is as expected, all the needed exports exist and nothing has been changed unintentionally.

NFS mount failure. Non existent mount path {{mountPath}}.   Description:  NFS mount failure: Client {{clientIpAddr}} tried to mount nonexistent mount path {{mountPath}} on NAS Volume {{nasContainerIdIntegerName}}.

NFS mount failure. Access denied during mount {{mountPath}}.   Description:  NFS mount failure: Access denied for the client {{clientIpAddr}} while mounting path {{mountPath}} on NAS Volume {{nasContainerIdIntegerName}}.

NFS mount failure. Access attempt to limited export {{nfsExport}}   Description:  NFS mount failure: Client {{clientIpAddr}} is not allowed to access export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}}, with defined export options: {{nfsExportOptions}}.   Action Items:   This error is caused by a client which accesses a limited export. The export was defined with clients limitations (network or netgroup or IP) that did not include the accessing client.

NFS mount failure. Netgroups could not be attained {{nfsExport}}.   Description:  NFS mount failure: Client {{clientIpAddr}} failed to mount export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}} since the required netgroup information could not be attained. Export options: {{nfsExportOptions}}.   Action Items:  Check availability of NIS/LDAP server. This error is usually the outcome of a communication error between the NAS and the NIS/LDAP server. It could be caused by a network issue, directory server overload or a software malfunction in one of environment components.

Client authentication failed on {{TenantName}} due to client clock skew.   Description:  Kerberos authentication failed because of the client clock skew between client {{clientIpAddr}} and NAS controller {{nasControllerId}} of {{TenantName}}.   Action Items:  Fix client clock. Your client clock must be within 5 minutes range from the Kerberos server (i.e. AD) clock. Configure the used AD as an NTP server for this client to avoid clock skews errors.

Client connect failure. Share {{cifsShare}} points to invalid directory.   Description:  SMB client connection failure: Client {{clientIpAddr}} accessed a nonexistent share {{cifsShare}} which refers to an inexistent directory {{nasContainerPath}} in NAS Volume {{nasContainerIdIntegerName}}.   Action Items:  List all available shares on the NAS and identify the problematic share. It should have an indication that it is not accessible.

SMB client login to {{TenantName}} failed. Wrong password for user {{userName}}.   Description:  SMB client login failure: Client {{clientIpAddr}} with user name '{{userName}}' supplied the wrong password. NAS Controller {{nasControllerId}} of {{TenantName}}.

SMB client login to {{TenantName}} failed. Authorization failed for user {{userName}}.   Description:  Authorization for user '{{userName}}' failed, client {{clientIpAddr}}, NAS controller {{nasControllerId}} of {{TenantName}}.   Internal Information:   {{internalInfo}}

SMB client connection failure. Unavailable share {{cifsShare}} on {{TenantName}}.   Description:  SMB client connection failure: Client {{clientIpAddr}} attempted to connect to an unavailable share {{cifsShare}} of {{TenantName}}.   Action Items:  This failure is commonly caused by spelling mistakes done on the client machine or by a user trying to access the home share of a different user.

End-user license agreement (EULA) was not accepted by user.   Description:  FluidFS version {{FluidFsVersion}} has a new end user license agreement. You must accept this agreement in order to use the system.   Action Items:  To accept the end user agreement go to User Interface System menu.

FluidFS Health Scan found an inconsistency in the system.   Description:  FluidFS Health Scan found an inconsistency in the system. Please contact Support.   Internal Information:  FluidFS Health Scan has found an error in {{category}} on level {{level}}

FluidFS Health Scan finished a scanning cycle.   Description:  FluidFS Health Scan finished a scanning cycle of the entire system

Failed to delete {{Name}} by {{userName}}. {{retcodeString}}.

EQL fabric route {{networkId}} modified by {{userName}}.

EQL fabric route {{networkId}} deleted by {{userName}}.

iSCSI IPv4 fabric {{Name}} created by {{userName}}.

iSCSI IPv4 fabric {{Name}} created by {{userName}}. {{retcodeString}}

iSCSI IPv4 fabric {{Name}} modified by {{userName}}.

iSCSI IPv4 fabric {{Name}} modified by {{userName}}. {{retcodeString}}

iSCSI IPv4 fabric {{Name}} deleted by {{userName}}.

EQL storage group modified by {{userName}}.

iSCSI storage portals modified by {{userName}}.

Failure to modify iSCSI storage portals by {{userName}}. {{retcodeString}}

Example {{Name}} was deleted by {{userName}}, but with a warning: {{retcodeString}}.

Time configuration was modified by {{userName}}

User {{userName}} set the appliance ID {{applianceId}} blink state for the 1st controller to {{blink1}} and the 2nd controller to {{blink2}}.

User {{userName}} rebooted NAS controller {{controllerId}}.

Client or router with {{ClientIp}} IP, which referred to {{AccessIp}} IP, was moved to controller{{NodeId}} by {{userName}}.

Client or router with {{ClientIp}} IP, which referred to {{AccessIp}} IP was restricted to the required controller (pin state is {{PinState}}) by {{userName}}.

{{userName}} had performed failback of all the clients to their preferred controller.

{{userName}} had performed a rebalance of all the clients between the controllers.

NDMP configuration was modified by {{userName}}.

Failed to modify time configuration by {{userName}}. {{retcodeString}}.

The user {{userName}} updated the antivirus hosts.

The user {{userName}} updated the cluster identifier.

The user {{userName}} renamed the cluster to {{ClusterName}}.

The user {{userName}} backed up the cluster configuration to file.

Route to {{destinationNetworkID}}/{{destinationPrefix}} with gateway IP {{routeGateway}}  was successfully created by {{userName}}.

The user {{userName}} destroyed the cluster.

The user {{userName}} updated the Enterprise Manager recipients.

The user {{userName}} created {{FabricName}} Fibre Channel fabric.

The user {{userName}} updated {{FabricName}} Fibre Channel fabric.

The user {{userName}} deleted {{FabricName}} Fibre Channel fabric.

The user {{userName}} updated the FTP configuration.

The user {{userName}} updated the file system health scan configuration.