Dell PowerFlex 4.5.x Alerts and Events Reference Guide
File services core alerts
All alerts in this section apply to the file subsystem. These alerts do not have SCG symptom IDs, except where noted.
| Code | Name | Description | Severity | System impact | Repair flow | SNMP code |
|---|---|---|---|---|---|---|
| 50101b02 | CEPP_SOME_SERVER_UNREACHABLE | Some of the publishing pools of the {{nasServer}} NAS server are not working properly. | MINOR | Events on the affected publishing pools on the {{nasServer}} NAS server may not be available for the CEPA server. | Check the NAS server network connectivity. Check NAS server publishing pool and CEPA server configuration. | file-events-publisher.cepp-some-server-unreachable |
| 50101b03 | CEPP_ALL_SERVERS_UNREACHABLE | All the publishing pools of the {{nasServer}} NAS server are unavailable. | MAJOR | Events on the publishing pools of the {{nasServer}} NAS server may not be available for the CEPA server. | Check the NAS server network connectivity. Check NAS server publishing pool and CEPA server configuration. | file-events-publisher.cepp-all-servers-unreachable |
| 50101601 | CLUSTER_FS_FREESPACE_LOW | The root file system in the NAS cluster object (fsid {{fsid}}) is low on free space. | MINOR | The file system is running low on free space. Creations and modifications of NAS objects may start failing. | Contact your service provider. | nas-cluster-config.cluster-fs-freespace-low |
| 50101701 | CLUSTER_FS_STORAGE_DEVICE_POTENTIALLY_IMPACTED | Recovery is recommended on the root file system in the NAS cluster object (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Contact your service provider. | nas-cluster-config.cluster-fs-storage-device-potentially-impacted |
| 50102601 | NODE_AUTO_RECOVERY_AUTOMATIC_NODE_RECOVERY_DISABLED | Automatic node recovery disabled. | MINOR | Node will not be automatically started if it fails. | nas-cluster-config.node-auto-recovery-automatic-node-recovery-disabled | |
| 50103703 | CLUSTER_DATA_SERVICE_CLUSTER_DATA_SERVICE_ENABLED_NO_RECOVERY | Cluster data service state enabled but automatic recovery is disabled. | MAJOR | Cluster data service state is enabled but automatic NAS server recovery is disabled for service procedure. NAS servers which go completely down will not be recovered automatically to prevent rolling panic. | Enable data service recovery after all issues are resolved. | nas-cluster-config.cluster-data-service-enabled-no-recovery |
| 50103704 | CLUSTER_DATA_SERVICE_CLUSTER_DATA_SERVICE_ENABLED_VERIFY_DATA_LOSS | Cluster is in state when block storage reports potential data loss for all user NAS servers. | MAJOR | Restore from data loss procedure is in progress. Data service is enabled cluster-wide but all user NAS servers reports potential data loss on mount. | After recovery is complete clear the cluster-wide flag which enables data loss verification. | nas-cluster-config.cluster-data-service-enabled-verify-data-loss |
| 50103c01 | CLUSTER_SQL_CACHE_CLUSTER_SQLCACHE_DISABLED | The SQL cache has been disabled due to DB internal issue. | MAJOR | The SQL cache is disabled due to internal issue. The REST-API server is working now in degraded mode, filtering and paging are unavailable, slow response could be expected. | Check the Filesystem or the LUN hosting the SQL database using svc_recover service command. | nas-cluster-config.cluster-sql-cache-cluster-sqlcache-disabled |
| 50104201 | CLUSTER_MODIFY_REQUESTS_CLUSTER_MODIFY_REQUESTS_DISABLED | Storage server management modify operations are temporarily disabled by service provider request. | MINOR | Storage server management modify operations are temporarily disabled by service provider request. Storage provisioning or modification operations are not available at the moment. | nas-cluster-config.cluster-modify-requests-disabled | |
| 50100102 | DNS_SERVICE_SOME_SERVER_UNREACHABLE | The DNS client of the {{nasServer}} NAS server is unable to connect to some of the configured DNS servers. | MINOR | The DNS client is unable to connect to some of the configured DNS server however it is still operational. This may happen when the NAS server cannot reach the peer DNS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured DNS server running the 'svc_cifssupport -checkup' or 'svc_nas -dns' command from the NAS conainer. | file-dns-servers.dns-service-some-server-unreachable |
| 50100103 | DNS_SERVICE_ALL_SERVERS_UNREACHABLE | The DNS client of the {{nasServer}} NAS server is unable to connect to all configured DNS servers. | MAJOR | The DNS client is unable to contact any DNS server and so is not operational. This may happen when the NAS server cannot reach the peer DNS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured DNS server running the 'svc_cifssupport -checkup' or 'svc_nas -dns' command from the NAS container. | file-dns-servers.dns-service-all-servers-unreachable |
| 50101815 | IMPORT_SESSION_ERROR_INITIAL_PROVISIONING | Import session '{{importSessionName}}' ({{importSessionId}}) failed to complete initial provisioning. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed to complete the initial provisioning stage. The error occurred while preparing the target NAS server and the source system for the import (error {{errorCode}}). The import process is suspended. See the report on the import session for details. | Use Resume action to retry initial provisioning and continue the import process. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-initial-provisioning |
| 50101816 | IMPORT_SESSION_ERROR_INITIAL_COPY | Import session '{{importSessionName}}' ({{importSessionId}}) failed to complete the initial data copy. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the initial (baseline) data copy stage. The data transfer may be suspended for some of the file systems (error {{errorCode}}). See the report on the import session for details. | Use Resume action to retry and continue with the initial data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-initial-copy |
| 50101817 | IMPORT_SESSION_ERROR_IMPORTING_CONFIG | Import session '{{importSessionName}}' ({{importSessionId}}) failed to import the configuration. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the configuration import stage. The error occurred while retrieving settings from the source system and applying them to the target NAS server (error {{errorCode}}). The import process is suspended. See the report on the import session for details. | Use Resume action to retry importing the configuration and continue the process. Skip Failed Step option allows to ignore the failed operation and continue to the next import step if possible. This option can cause an inconsistency in the configuration and even data unavailability after cutover. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-importing-config |
| 50101818 | IMPORT_SESSION_ERROR_CUTTING_OVER | Import session '{{importSessionName}}' ({{importSessionId}}) failed to cutover. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the cutover stage. The error occurred while trying to reconnect clients from the source to the target NAS server (error {{errorCode}}). Clients may experience data unavailability. See the report on the import session for details. | Use Cutover action again to retry. Manual intervention may be required to restore the client data access. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-cutting-over |
| 50101819 | IMPORT_SESSION_ERROR_INCREMENTAL_COPY | Import session '{{importSessionName}}' ({{importSessionId}}) failed to complete the incremental data copy. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the incremental data copy stage. The data transfer may be suspended for some of the file systems. Clients may experience data unavailability. See the report on the import session for details. | Use Resume action to retry and continue with the incremental data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-incremental-copy |
| 5010181a | IMPORT_SESSION_ERROR_INCREMENTAL_COPY_RESUME | Import session '{{importSessionName}}' ({{importSessionId}}) failed to resume the incremental data copy. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the incremental data copy stage. The error occurred while trying to resume the data transfer. The transfer may be suspended for some of the file systems. Clients may experience data unavailability. See the report on the import session for details. | Use Resume action to retry and continue with the incremental data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-incremental-copy-resume |
| 5010181b | IMPORT_SESSION_ERROR_INCREMENTAL_COPY_RETRIEVE_FS_IMPORT_STATUS | Import session '{{importSessionName}}' ({{importSessionId}}) failed to complete the incremental data copy. Cannot retrieve file system import status from the target NAS server's node. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the incremental data copy stage. The error occurred while trying to retrieve the status from the target NAS server's node. The transfer may be suspended for some of the file systems. Clients may experience data unavailability. See the report on the import session for details. | Use Resume action to retry and continue with the incremental data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-incremental-copy-retrieve-fs-import-status |
| 5010181c | IMPORT_SESSION_ERROR_COMMITTING | Import session '{{importSessionName}}' ({{importSessionId}}) failed to commit. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the committing stage. The error occurred while finalizing the import process, stopping data synchronization, and cleaning up the source system (error {{errorCode}}). The system state may be inconsistent. See the report on the import session for details. | Use Commit action to attempt a retry. Using Force option ignores errors on the source system. This option can be used only if the incremental copy was completed and the session was ready to commit. | file-import-sessions.import-session-error-committing |
| 5010181d | IMPORT_SESSION_ERROR_CANCELLING | Import session '{{importSessionName}}' ({{importSessionId}}) failed to cancel. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the canceling stage. The error occurred while trying to roll back the import process (error {{errorCode}}). The system state may be inconsistent. Clients may experience data unavailability. See the report on the import session for details. | Use Cancel action to attempt a retry. Using Force option ignores errors on the source system. | file-import-sessions.import-session-error-cancelling |
| 5010181e | IMPORT_SESSION_ERROR_PAUSING_INITIAL_COPY | Import session '{{importSessionName}}' ({{importSessionId}}) failed to pause the initial data copy. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed when pausing the initial (baseline) data copy. The state of data transfer may be inconsistent for some of the file systems. Communication with the source system may still produce a load. See the report on the import session for details. | Use Pause action to retry or Resume action to continue the initial data copy. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-pausing-initial-copy |
| 5010181f | IMPORT_SESSION_ERROR_PAUSING_INCREMENTAL_COPY | Import session '{{importSessionName}}' ({{importSessionId}}) failed to pause the incremental data copy. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed when pausing the incremental data copy. The state of data transfer may be inconsistent for some of the file systems. Communication with the source system may still produce a load. See the report on the import session for details. | Use Pause action to retry or Resume action to continue the incremental data copy. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-pausing-incremental-copy |
| 50101820 | IMPORT_SESSION_ERROR_INTERNAL | Import session '{{importSessionName}}' ({{importSessionId}}) failed due to an internal error. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has encountered an internal error due to an unexpected failure (error {{errorCode}}). The target system state may be inconsistent. | Try to repeat the last operation. Contact your service provider if the issue persists. | file-import-sessions.import-session-error-internal |
| 50101821 | IMPORT_SESSION_ERROR_SIMULATED_FAILURE | Import session '{{importSessionName}}' ({{importSessionId}}) failed due to a simulated failure ({{file}}:{{line}}). | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed due to a simulated failure at {{file}}:{{line}}. Fault injection mechanism caused this error. | Contact your service provider if you see this error. | file-import-sessions.import-session-error-simulated-failure |
| 50101822 | IMPORT_SESSION_ERROR_CLUSTER_CONTROLLER_FAILOVER | Import session '{{importSessionName}}' ({{importSessionId}}) failed due to a restart of the cluster controller. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has been interrupted because the cluster controller was restarted on the target system. This may be due to a node failure or an intentional role transfer. The import session will be recovered and resumed once the cluster controller is fully operational. | Wait until the import session is recovered. Retry the last operation if it is not resumed automatically. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-cluster-controller-failover |
| 50101823 | IMPORT_SESSION_ERROR_CONNECTING_DATA_NODE | Import session '{{importSessionName}}' ({{importSessionId}}) failed to connect to the target NAS server's node. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed due to unavailability of the target NAS server's node. The system health status may provide more details. | Check the system health status, ensure that the target NAS server's node is operational and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-connecting-data-node |
| 50101824 | IMPORT_SESSION_ERROR_CONNECTING_CLUSTER_CONTROLLER | Import session '{{importSessionName}}' ({{importSessionId}}) failed to connect to the cluster controller. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed due to unavailability of the cluster controller on the target system. The system health status may provide more details. | Check the system health status, ensure that the cluster controller is operational and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-connecting-cluster-controller |
| 50101825 | IMPORT_SESSION_ERROR_SAVE_CHANGES | Import session '{{importSessionName}}' ({{importSessionId}}) failed to save changes to the persistent storage. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed when saving changes to the persistent storage on the target system. The import state may be inconsistent. The system health status may provide more details. | Check the system health status, ensure that the issues with the storage are resolved and try to repeat the last operation. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-save-changes |
| 50101826 | IMPORT_SESSION_ERROR_INITIAL_COPY_FAILED_TO_PING_SOURCE_SYSTEM | Import session '{{importSessionName}}' ({{importSessionId}}) failed to complete the initial data copy. Failed to ping the source system. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed to proceed with the initial (baseline) data copy from source NAS server '{{sourceNasServerName}}'. The error occurred while trying to ping the source system. The data transfer is suspended. | Check connection to the source system. Ensure that ICMP traffic is not blocked. Use Resume action to retry and continue with the initial data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-initial-copy-failed-to-ping-source-system |
| 50101827 | IMPORT_SESSION_ERROR_INCREMENTAL_COPY_FAILED_TO_PING_SOURCE_SYSTEM | Import session '{{importSessionName}}' ({{importSessionId}}) failed to resume the incremental data copy. Failed to ping the source system. | MAJOR | Import session '{{importSessionName}}' ({{importSessionId}}) has failed during the incremental data copy from source NAS server '{{sourceNasServerName}}'. The error occurred while trying to ping the source system. The data transfer is suspended. Clients may experience data unavailability. | Check connection to the source system. Ensure that ICMP traffic is not blocked. Use Resume action to retry and continue with the incremental data copy for failed file systems. The operation is attempted automatically if possible. The import process can be canceled at any moment using Cancel action. | file-import-sessions.import-session-error-incremental-copy-failed-to-ping-source-system |
| 50101d09 | FS_IMPORT_ERROR_UNRECOVERABLE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to a general error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) encountered a general error. It is not possible to continue the data copy. Import session '{{importSessionName}}' ({{importSessionId}}). | Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-unrecoverable |
| 50101d0a | FS_IMPORT_ERROR_UNRECOVERABLE_DEST_FSCKED | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the file system recovery process has modified the target file system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the file system recovery process has modified the target file system. It is not possible to continue the data copy. Import session '{{importSessionName}}' ({{importSessionId}}). | Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-unrecoverable-dest-fscked |
| 50101d0b | FS_IMPORT_ERROR_UNRECOVERABLE_APP_LOG_FAIL | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to an unsuccessful failover recovery. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to an unsuccessful failover recovery. There was an unsuccessful attempt to restart the import after a failure. It is not possible to continue the data copy. Import session '{{importSessionName}}' ({{importSessionId}}). | Use Resume action to restart the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-unrecoverable-app-log-fail |
| 50101d0c | FS_IMPORT_ERROR_CONNECTION | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the data connection to the source system was terminated. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. The data connection between the source and the target system was terminated. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the network connectivity between the target system and the source system, and resolve potential issues that might prevent establishing a connection. Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-connection |
| 50101d0d | FS_IMPORT_ERROR_DHSM_AUTH | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because DHSM HTTP connection encountered an authentication error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. DHSM HTTP connection encountered an authentication error. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the provided source DHSM username and password. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-dhsm-auth |
| 50101d0e | FS_IMPORT_ERROR_DHSM_SSL_CONNECTION | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because DHSM HTTP connection encountered an SSL error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. DHSM HTTP connection encountered an SSL error. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the connectivity between the target system and the source system, and resolve potential issues that might prevent establishing an SSL connection. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-dhsm-ssl-connection |
| 50101d0f | FS_IMPORT_ERROR_DHSM_BAD_REQUEST_RESPONSE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because a bad request or response was transferred over the DHSM HTTP connection. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. A bad request or response was transferred over the DHSM HTTP connection. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the status of the DHSM server on the source system and resolve any issues. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-dhsm-bad-request-response |
| 50101d10 | FS_IMPORT_ERROR_DESTINATION_IO | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to an I/O error on the target system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) encountered an I/O error on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-destination-io |
| 50101d11 | FS_IMPORT_ERROR_DESTINATION_QUOTA_EXCEEDED | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because a quota of the target file system was exceeded. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. A quota of the file system was exceeded on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the quota of file system '' on the target system. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-destination-quota-exceeded |
| 50101d12 | FS_IMPORT_ERROR_DESTINATION_NO_SPACE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because there was no free space available on the target file system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. There was no free space available on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the size of the target file system to avoid the low-on-space health condition. Then, use Resume action to retry and continue the data copy. Extra space may be required on the target file system to complete the import due to metadata differences between the source and the target file systems. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-destination-no-space |
| 50101d13 | FS_IMPORT_ERROR_DESTINATION_READ_ONLY | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the target file system became read-only. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. The file system became read-only on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Make target file system '' writable. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-destination-read-only |
| 50101d14 | FS_IMPORT_ERROR_DESTINATION_LOW_SPACE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the target file system became low on space. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. The file system on the target system became low on space. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the size of the target file system to avoid the low-on-space condition. Then, use Resume action to retry and continue the data copy. Extra space may be required on the target file system to complete the import due to metadata differences between the source and the target file systems. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-destination-low-space |
| 50101d15 | FS_IMPORT_ERROR_SOURCE_IO | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to an I/O error on the source system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) encountered an I/O error accessing the file system on the source side. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the network connectivity between the target system and the source system, and resolve potential issues that might prevent establishing a connection. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-source-io |
| 50101d16 | FS_IMPORT_ERROR_SOURCE_QUOTA_EXCEEDED | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because a quota of the source file system was exceeded. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. A quota of the file system was exceeded on the source system. Write mirroring is required to ensure the data consistency on the source side in case a rollback is performed. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the quota of file system '' on the source system. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-source-quota-exceeded |
| 50101d17 | FS_IMPORT_ERROR_SOURCE_NO_SPACE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because there was no free space available on the source file system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. There was no free space available on the source system. Write mirroring is required to ensure the data consistency on the source side in case a rollback is performed. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the size of the source file system. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-source-no-space |
| 50101d18 | FS_IMPORT_ERROR_SOURCE_NAME_TOO_LONG | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because a file path on the source file system is too long. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. A file path on the source file system exceeds the permitted length and cannot be imported. Import session '{{importSessionName}}' ({{importSessionId}}). | Cancel this import session, ensure that file path on source file system '' do not exceed 1023 UTF-16 code units, and then create another import session. Alternatively, contact your service provider. | file-systems.fs-import-error-source-name-too-long |
| 50101d19 | FS_IMPORT_ERROR_INTERNAL_ERROR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed due to an internal error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) encountered an internal error. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the system health status and the report on the import session. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-internal-error |
| 50101d1a | FS_IMPORT_ERROR_NOT_STARTED | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. The error occurred while trying to start the data transfer. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the system health status and the report on the import session. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-not-started |
| 50101d1b | FS_IMPORT_ERROR_ABORTED | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) was aborted. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) was aborted and has to be started over. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the system health status and the report on the import session. Use Resume action to retry the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-aborted |
| 50101d1c | FS_IMPORT_ERROR_GET_INFO | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to get the status from the target NAS server's node. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to get the status from the target NAS server. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the system health status and the report on the import session. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-get-info |
| 50101d1d | FS_IMPORT_ERROR_STARTING_BUSY | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because a previous attempt did not complete gracefully. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because a previous attempt to import this file system did not complete gracefully. Import session '{{importSessionName}}' ({{importSessionId}}). | Use Resume action to resume the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-busy |
| 50101d1e | FS_IMPORT_ERROR_STARTING_DHSM_AUTH | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start due to a DHSM HTTP authentication error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The DHSM HTTP connection encountered an authentication error. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the provided source DHSM username and password. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-auth |
| 50101d1f | FS_IMPORT_ERROR_STARTING_DHSM_SSL_NEGOTIATE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the DHSM SSL negotiation was unsuccessful. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. SSL negotiation was unsuccessful while establishing a secure DHSM connection. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the connectivity between the target system and the source system, ensure that SSL is enabled for DHSM server on the source system, and resolve potential issues that might prevent establishing an SSL connection. Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-ssl-negotiate |
| 50101d20 | FS_IMPORT_ERROR_STARTING_DHSM_SEND_REQUEST | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because there was a problem sending a DHSM HTTP request. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. There was a problem sending a DHSM HTTP request. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the connectivity between the target system and the source system, and resolve potential issues. Then, use Resume action to continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-send-request |
| 50101d21 | FS_IMPORT_ERROR_STARTING_DHSM_CLIENT | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the DHSM HTTP client is not available. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The DHSM HTTP client is not available. Import session '{{importSessionName}}' ({{importSessionId}}). | Reduce the system load and memory usage on the target system. Then, use Resume action to resume the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-client |
| 50101d22 | FS_IMPORT_ERROR_STARTING_DHSM_CNX_INIT | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the DHSM HTTP client was not initialized properly. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The DHSM HTTP client was not initialized properly. Import session '{{importSessionName}}' ({{importSessionId}}). | Verify that the system parameter 'imt.remoteDhsmPort' is set to a nonzero value. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-cnx-init |
| 50101d23 | FS_IMPORT_ERROR_STARTING_LOCAL_FILE_SYSTEM_NOT_FOUND | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the target file system could not be found. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the file system could not be found on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-local-file-system-not-found |
| 50101d24 | FS_IMPORT_ERROR_STARTING_LOCAL_FILE_SYSTEM_THAW | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the access to the target file system could not be restored. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The access to the file system could not be restored on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-local-file-system-thaw |
| 50101d25 | FS_IMPORT_ERROR_STARTING_NO_CONNECTION_TO_REMOTE_FILE_SYSTEM | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the source file system is inaccessible. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The source file system is inaccessible from the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the network connectivity between the target system and the source system. Ensure that the source file system is accessible to the target system using NFS/SMB file-sharing protocols, depending on the import type. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-no-connection-to-remote-file-system |
| 50101d26 | FS_IMPORT_ERROR_STARTING_QUERY_SRC_ROOT_FILE_HANDLE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the source file system could not be queried. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The root file handle of the source file system could not be queried. Import session '{{importSessionName}}' ({{importSessionId}}). | Ensure that the source file system is accessible to the target system using NFS/SMB file-sharing protocols, depending on the import type. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-query-src-root-file-handle |
| 50101d27 | FS_IMPORT_ERROR_STARTING_EXCESSIVE_SERVER_TIME_DELTA | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the time difference between the source and the target systems exceeds the limit. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The time difference between the source system and the target system is too significant to continue the import. Import session '{{importSessionName}}' ({{importSessionId}}). | Synchronize the time on the source system and the target system. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-excessive-server-time-delta |
| 50101d28 | FS_IMPORT_ERROR_STOPPING_HAS_DIRTY_FILES | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop because the data could not be synchronized with the source system. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop. The file system has dirty files with changes that could not be mirrored to the source system and will be lost if the import is canceled. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status and the availability of the source system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. Forcing the Cancel action will cause data loss. | file-systems.fs-import-error-stopping-has-dirty-files |
| 50101d29 | FS_IMPORT_ERROR_STOPPING_INTERNAL | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop due to an internal error. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop due to an internal error. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the system health status and the report on the import session. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-stopping-internal |
| 50101d2a | FS_IMPORT_ERROR_STOPPING_LOCAL_FILE_SYSTEM_FREEZE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop because the access to the target file system could not be suspended. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop. The access to the file system could not be suspended on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-stopping-local-file-system-freeze |
| 50101d2b | FS_IMPORT_ERROR_STOPPING_LOCAL_FILE_SYSTEM_THAW | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop because the access to the target file system could not be restored. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop. The access to the file system could not be restored on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-stopping-local-file-system-thaw |
| 50101d2c | FS_IMPORT_ERROR_STOPPING_LOCAL_FILE_SYSTEM_NOT_FOUND | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop because the target file system could not be found. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop. The file system could not be found on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-stopping-local-file-system-not-found |
| 50101d2d | FS_IMPORT_ERROR_STARTING_DESTINATION_IS_READ_ONLY | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the target file system became read-only. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. The file system became read-only on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Make target file system '' writable. Then, use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-destination-is-read-only |
| 50101d2e | FS_IMPORT_ERROR_STOPPING_DESTINATION_IS_READ_ONLY | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop because the target file system became read-only. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to stop. The file system became read-only on the target system. Cleaning up the migration database is not possible. Import session '{{importSessionName}}' ({{importSessionId}}). | Make target file system '' writable. Then, retry the action to continue. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-stopping-destination-is-read-only |
| 50101d2f | FS_IMPORT_ERROR_STARTING_DESTINATION_LOW_SPACE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because the target file system was low on space. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed. The file system on the target system was low on space. Import session '{{importSessionName}}' ({{importSessionId}}). | Increase the size of the target file system to avoid the low-on-space condition. Then, use Resume action to retry and continue the data copy. Extra space may be required on the target file system to complete the import due to metadata differences between the source and the target file systems. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-destination-low-space |
| 50101d30 | FS_IMPORT_ERROR_STARTING_FAILED_TO_MIGRATE_DHSM_CONNECTIONS | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because an error occurred while importing the DHSM connections. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start due to an unsuccessful attempt to import the DHSM connections of the file system. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the health status of the target system. Use Resume action to retry and continue the data copy. The Resume action is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-failed-to-migrate-dhsm-connections |
| 50101d31 | FS_IMPORT_ERROR_STARTING_DHSM_BAD_REQUEST_RESPONSE | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start because a bad request or response was transferred over the DHSM HTTP connection. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed to start. A bad request or response was transferred over the DHSM HTTP connection. Import session '{{importSessionName}}' ({{importSessionId}}). | Check the status of the DHSM server on the source system and resolve any issues. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-starting-dhsm-bad-request-response |
| 50101d32 | FS_IMPORT_ERROR_LOW_ON_RESOURCES | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because the target system is low on resources. | MAJOR | The import of file system '{{targetFilesystemName}}' ({{targetFilesystemId}}) failed because of excessive load on the target system. Import session '{{importSessionName}}' ({{importSessionId}}). | Reduce the system load and memory usage on the target system. Then, use Resume action to retry and continue the data copy. The operation is attempted automatically if possible. The import session can be canceled at any moment using Cancel action. | file-systems.fs-import-error-low-on-resources |
| 50100501 | LDAP_SERVICE_CONFIG_FAILED | The LDAP service configuration of the NAS server {{nasServer}} for domain {{domain}} failed. | MAJOR | The LDAP service configuration of the NAS server {{nasServer}} for domain {{domain}} failed. The LDAP client is not operational. | Run the 'svc_cifssupport -checkup' or 'svc_nas -ldap' command from the NAS container for diagnostics. | file-ldap-servers.ldap-service-config-failed |
| 50100502 | LDAP_SERVICE_IS_BADLY_CONFIGURED | LDAP client settings on NAS server {{nasServer}} are not valid within domain {{domain}}. | MAJOR | You have configured a LDAP service in server {{nasServer}} for the domain {{domain}}. But the LDAP service encounters some configuration issue. So you could get some unexpected issue using this name resolver. | On NAS server check LDAP configuration for domain . Check binding and access rights to this LDAP server, in particular the username and password used to connect to the server. Run the 'svc_cifssupport -checkup' or 'svc_nas -ldap' command from the NAS container for diagnostics. | file-ldap-servers.ldap-service-is-badly-configured |
| 50100504 | LDAP_SERVICE_SOME_SERVERS_UNREACHABLE | The LDAP client of the NAS server {{nasServer}} is unable to connect to some of the configured LDAP servers. | MINOR | The LDAP client of the NAS server {{nasServer}} is unable to connect to some of the configured LDAP server for domain {{domain}}, however it is still operational. This may happen when the NAS server cannot reach the peer LDAP server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured LDAP server running the 'svc_cifssupport -checkup' command from the NAS container. | file-ldap-servers.ldap-service-some-servers-unreachable |
| 50100505 | LDAP_SERVICE_ALL_SERVERS_UNREACHABLE | No LDAP servers configured for NAS server {{nasServer}} are responding. | MAJOR | In the NAS server {{nasServer}}, LDAP service could not provide mapping anymore. All configured LDAP servers for domain {{domain}} are now out of order. | In the NAS server, check the availability of LDAP servers configured for domain . At least one of the configured LDAP server need to be operational. Check for LDAP service status or for connectivity issue. It is recommended to configure at least two LDAP servers per domain. Or check the availability of the configured LDAP server running the 'svc_cifssupport -checkup' command from the NAS container. | file-ldap-servers.ldap-service-all-servers-unreachable |
| 50100c01 | NAS_SERVER_OUT_OF_SERVICE | NAS server {{vdmname}} is down. | CRITICAL | NAS server {{vdmname}} doesn't provide service on any of NAS cluster nodes. | Contact your service provider in case the NAS server will not be up in a near future. | nas-servers.nas-server-out-of-service |
| 50100c02 | NAS_SERVER_DEGRADED | NAS server {{vdmname}} fault tolerance is degraded. | MAJOR | NAS server {{vdmname}} is serving, but its fault tolerance is degraded. The service might be disrupted in case of unexpected failure. | Contact your service provider in case the NAS server will not become fault tolerant in a near future. | nas-servers.nas-server-degraded |
| 50100c03 | NAS_SERVER_EVACUATED_DURING_UPGRADE | NAS server {{vdmname}} service fault tolerance is degraded due to a maintenance procedure on a peer NAS cluster node. | MINOR | NAS server {{vdmname}} service fault tolerance is degraded due to a maintenance procedure (either Upgrade, planned maintenance or recovery) on a peer NAS cluster node. | No actions required. Once the procedure is finished fault tolerance should be restored automatically. Contact your service provider in case the NAS server will not become fault tolerant in a near future after the maintenance window. | nas-servers.nas-server-evacuated-during-upgrade |
| 50100c05 | NAS_SERVER_IN_MAINTENANCE | NAS server {{vdmname}} is in maintenance mode. | CRITICAL | NAS server {{vdmname}} is in maintenance mode for recovery. | Contact your service provider. | nas-servers.nas-server-in-maintenance |
| 50100c07 | NAS_SERVER_NAS_SERVER_RESTARTING | The NAS server {{vdmname}} is restarting | MINOR | The NAS server {{vdmname}} is restarting | N/A | nas-servers.nas-server-restarting |
| 50100c06 | NAS_SERVER_NAS_SERVER_CLUSTER_DATA_SERVICE_STOPPED | NAS server {{vdmname}} is down due to stopped service. | MAJOR | NAS server {{vdmname}} is stopped because administrator has requested to stop all data services on the NAS cluster. | nas-servers.nas-server-cluster-data-service-stopped | |
| 50100c08 | NAS_SERVER_NAS_SERVER_IS_MOVING | NAS server {{vdmname}} service might be briefly interrupted due to a currently running management operation. | MINOR | NAS server {{vdmname}} service might be interrupted due to the fact that NAS server is being moved between NAS Cluster nodes. | nas-servers.nas-server-is-moving | |
| 50100c09 | NAS_SERVER_NAS_SERVER_UNRECOVERABLE | The NAS server {{vdmname}} is in an unrecoverable state after its deletion that have failed. | CRITICAL | Deletion of the NAS server failed, some resouces are left in the system, manual intervention is likely needed. | Contact your service provider. | nas-servers.nas-server-unrecoverable |
| 50101101 | NAS_SERVER_FS_FREESPACE_LOW | The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) is low on free space. | MINOR | The file system is running low on free space. Creations and modifications of node objects may start failing. | Contact your service provider. | nas-servers.nas-server-fs-freespace-low |
| 50101202 | NAS_SERVER_FS_STATE_UNMOUNTED_IO_ERROR | The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) is offline due to receiving an I/O error. | CRITICAL | The file system has received an I/O error and is unmounted. There may be a problem with the storage device. | Please contact support. | nas-servers.nas-server-fs-state-unmounted-io-error |
| 50101203 | NAS_SERVER_FS_STATE_UNMOUNTED_CORRUPTION_DETECTED | The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) is offline after discovering corruption. | CRITICAL | The file system has discovered internal corruption and is unmounted. The NAS server is offline. | Contact your service provider. | nas-servers.nas-server-fs-state-unmounted-corruption-detected |
| 50101204 | NAS_SERVER_FS_STATE_SERVICE_UNMOUNTED | The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) has been taken offline for service. | MAJOR | The file system has been taken offline for service. | Complete the planned service procedure and remount the FS with 'svc_recover -action mount' service command. | nas-servers.nas-server-fs-state-service-unmounted |
| 50101205 | NAS_SERVER_FS_STATE_RECOVERED_OK | The {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}) has completed recovery and is waiting to be restarted. | MAJOR | The file system has completed recovery and is waiting to be restarted. | Contact your service provider. | nas-servers.nas-server-fs-state-recovered-ok |
| 50101206 | NAS_SERVER_FS_STATE_RECOVERY_FAILED | Recovery failed on the {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | Recovery failed on the file system, manual intervention is likely needed. | Contact your service provider. | nas-servers.nas-server-fs-state-recovery-failed |
| 50101301 | NAS_SERVER_FS_STORAGE_DEVICE_POTENTIALLY_IMPACTED | Recovery is recommended on the {{fsname}} file system in NAS server {{vdmname}} (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Run recovery on the FS with 'svc_recover -action recover' and remount it with 'svc_recover -action mount'. | nas-servers.nas-server-fs-storage-device-potentially-impacted |
| 50104001 | NAS_SERVER_CONFIG_SNAP_NAS_SERVER_CONFIG_SNAP_REFRESH_FAILED | The configuration filesystem snap refresh on the NAS server {{vdmname}} has failed with the following error {{error}}. | MAJOR | While starting the NAS server in destination mode, the refresh of the configuration filesystem snap has failed. This may be due to an issue with the configuration filesystem which might be corrupted. If the NAS server is still up in non production mode, the configuration information might be stale. | The refresh snap issue must first be fixed. If the problem happened during a switchover, you must complete it with svc_dataprotection service command from the former source side: - svc_dataprotection nasServer -vdmoid xxxx -action switchoversession -fsoid xxxx for each user file system replication switchoversession - svc_dataprotection nasServer -vdmoid xxxx -action switchtodestinationmode to start the NAS server in destination mode | nas-servers.nas-server-config-snap-refresh-failed |
| 50104102 | NAS_SERVER_FILE_INTERFACE_SOME_NAS_SERVER_INTERFACES_IN_FAILURE | One or more file interfaces on the NAS server {{vdmname}} are in failure. | MAJOR | One or more file interfaces on the NAS server {{vdmname}} are wrongly configured. | Get the file interfaces list for the NAS server and modify their configuration accordingly to the network environment. | nas-servers.nas-server-file-interface-some-nas-server-interfaces-in-failure |
| 50104103 | NAS_SERVER_FILE_INTERFACE_ALL_NAS_SERVER_INTERFACES_IN_FAILURE | All file interfaces on the NAS server {{vdmname}} are in failure. | MAJOR | All file interfaces on the NAS server {{vdmname}} are wrongly configured. | Get the file interfaces list for the NAS server and modify their configuration accordingly to the network environment. | nas-servers.nas-server-file-interface-all-nas-server-interfaces-in-failure |
| 50100402 | NIS_SERVICE_SOME_SERVERS_UNREACHABLE | The NIS client is unable to connect to some of the configured NIS servers. | MINOR | The NIS client is unable to connect to some of the configured NIS server however it is still operational. This may happen when the NAS server cannot reach the peer NIS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured NIS server running the 'svc_cifssupport -checkup' or 'svc_nas -nis' command from the NAS container. | file-nis-servers.nis-service-some-servers-unreachable |
| 50100403 | NIS_SERVICE_ALL_SERVERS_UNREACHABLE | The NIS client is unable to connect to all configured NIS servers. | MAJOR | The NIS client is unable to contact any NIS server and so is not operational. This may happen when the NAS server cannot reach the peer NIS server because of network problems. | Check the NAS server network interface and the router configuration. Or check the availability of the configured NIS server running the 'svc_cifssupport -checkup' or 'svc_nas -nis' command from the NAS conainter. | file-nis-servers.nis-service-all-servers-unreachable |
| 50101901 | NFS_SERVER_JOINED_NO | The NFS server of the NAS server {{nasServer}} is configured with nfs secure using the SMB configuration, but is currently not registered in SMB AD KDC. | MAJOR | In order to work, a NFS server which is configured with nfs secure using the SMB configurqtion must be registered into the KDC of the windows domain. No user can actually connect. | Register the NFS server in the SMB KDC with join rest api call. | nfs-servers.nfs-server-joined-no |
| 50100d01 | NODE_DOWN | NAS node {{node}} is temporarily down. | MAJOR | NAS node {{node}} is temporarily down, but should be back up shortly. | Contact your service provider in case the failed node will not be recovered in a near future. | nas-nodes.node-down |
| 50100d02 | NODE_DOWN_DURING_UPGRADE | NAS node {{node}} is down as part of NAS cluster upgrade. | MINOR | NAS node {{node}} is down as part of NAS cluster upgrade. | nas-nodes.node-down-during-upgrade | |
| 50100d03 | NODE_RECOVERY_FAILED | NAS node {{node}} is down and its automatic recovery has failed. | CRITICAL | NAS node {{node}} is down and its automatic recovery has failed. | Contact your service provider in case the failed node will not be recovered in a near future. | nas-nodes.node-recovery-failed |
| 50100d05 | NODE_DOWN_AND_AUTOMATIC_RECOVERY_DISABLED | NAS Node {{node}} is down and automatic node recovery is disabled. | MINOR | NAS Node {{node}} is down and will not be recovered due to disabled state of automatic node recovery. | nas-nodes.node-down-and-automatic-recovery-disabled | |
| 50100d06 | NODE_DOWN_WHILE_TEMPORARY_DISABLED | NAS node {{node}} is down while it is temporary disabled. | MINOR | NAS node {{node}} is down while it is temporary disabled. | nas-nodes.node-down-while-temporary-disabled | |
| 50101401 | NODE_FS_FREESPACE_LOW | The root file system in NAS node {{node}} (fsid {{fsid}}) is low on free space. | MINOR | The file system is running low on free space. Creations and modifications of node objects may start failing. | Contact your service provider. | nas-nodes.node-fs-freespace-low |
| 50101501 | NODE_FS_STORAGE_DEVICE_POTENTIALLY_IMPACTED | Recovery is recommended on the root file system in NAS node {{node}} (fsid {{fsid}}). | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Contact your service provider. | nas-nodes.node-fs-storage-device-potentially-impacted |
| 50102501 | NODE_DATA_SERVICE_DATA_SERVICE_DISABLED_FOR_NODE_DUE_TO_DP_NW | Data services were not enabled for NAS node {{node}}. | MINOR | Data services were not enabled for NAS node {{node}} because some of the existing Data Protection Networks need to be reconfigured first. | Please modify Data Protection Network(s) configurations to accommodate new NAS node and then enable Data Services for it. | nas-nodes.node-data-service-data-service-disabled-for-node-due-to-dp-nw |
| 50103602 | STORAGE_SERVER_COMMUNICATION_STORAGE_SERVER_COMMUNICATION_FAILURE | The NAS node {{node}} is unable to contact the storage server {{ip}}. | MAJOR | The network connectivity between the NAS node {{node}} and the storage server {{ip}} is in failure. | Verify that the network infrastructure which routes the traffic between the node system interface and the storage server is functionning properly. | nas-nodes.storage-server-communication-failure |
| 50103001 | REMOTE_SYSTEM_COMMUNICATION_REMOTE_SYSTEM_COMMUNICATION_DOWN | Unable to reach remote NAS system '{{remoteSystemName}}' (id:{{remoteSystemId}}). | MAJOR | Verify that the remote system is running and that there are no network issues. Resolve any issues found. | NAS replication management is impacted. NAS data protection may be impacted. | file-remote-systems.remote-system-communication-down |
| 50102810 | NON_RECOVERABLE_ERRORS_PRI_UPDATE_DB_REC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) is inactive. System could not insert or update replication session database. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-update-db-rec-failed |
| 5010280f | NON_RECOVERABLE_ERRORS_PRI_DELETE_DB_REC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) is inactive. System could not delete replication session database. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-delete-db-rec-failed |
| 50102815 | NON_RECOVERABLE_ERRORS_SEC_UPDATE_DB_REC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) is inactive. System could not insert or update replication session database. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-sec-update-db-rec-failed |
| 50102813 | NON_RECOVERABLE_ERRORS_SEC_DELETE_DB_REC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) is inactive. System could not delete replication session database. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-sec-delete-db-rec-failed |
| 5010280c | NON_RECOVERABLE_ERRORS_PRI_RECOVERY_FAILED | File system replication session (id:{{fsReplicationSessionId}}), recovery failed. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-recovery-failed |
| 5010280d | NON_RECOVERABLE_ERRORS_PRI_STARTING_SEC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) failed to start on the destination. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-starting-sec-failed |
| 5010280b | NON_RECOVERABLE_ERRORS_PRI_PREEVT_FAILED | File system replication session (id:{{fsReplicationSessionId}}) starting transfer failed. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-preevt-failed |
| 50102811 | NON_RECOVERABLE_ERRORS_PRI_ACCESSING_DB_FAILED_INACTIVATE | File system replication session (id:{{fsReplicationSessionId}}) is inactive due to database access error. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-accessing-db-failed-inactivate |
| 50102812 | NON_RECOVERABLE_ERRORS_SEC_ACCESSING_DB_FAILED_INACTIVATE | File system replication session (id:{{fsReplicationSessionId}}) is inactive due to database access error. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-sec-accessing-db-failed-inactivate |
| 5010280e | NON_RECOVERABLE_ERRORS_PRI_STOPPING_SEC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) failed to stop on the destination. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-stopping-sec-failed |
| 5010280a | NON_RECOVERABLE_ERRORS_PRI_POSTEVT_FAILED | File system replication session (id:{{fsReplicationSessionId}}) transfer failed. Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-pri-postevt-failed |
| 50102801 | NON_RECOVERABLE_ERRORS_PRISCH_RECOVER_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-prisch-recover-failed |
| 50102803 | NON_RECOVERABLE_ERRORS_PRISCH_REFRESH_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-prisch-refresh-failed |
| 50102805 | NON_RECOVERABLE_ERRORS_PRISCH_COPY_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-prisch-copy-failed |
| 50102806 | NON_RECOVERABLE_ERRORS_PRISCH_CANCEL_COPY_FAILED | (Deprecated) Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-prisch-cancel-copy-failed |
| 50102807 | NON_RECOVERABLE_ERRORS_PRISCH_ABORT_SEC_FAILED | (Deprecated) Session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-prisch-abort-sec-failed |
| 50102802 | NON_RECOVERABLE_ERRORS_SECSCH_RECOVER_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-secsch-recover-failed |
| 50102804 | NON_RECOVERABLE_ERRORS_SECSCH_REFRESH_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-secsch-refresh-failed |
| 50102814 | NON_RECOVERABLE_ERRORS_SEC_RECOVERY_FAILED | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. | file-replication-sessions.non-recoverable-errors-sec-recovery-failed |
| 50102809 | NON_RECOVERABLE_ERRORS_DATA_OOS_WAITINGONADMIN | File system replication session (id:{{fsReplicationSessionId}}) recovery failed and session is inactive. | MAJOR | Data protection is impacted. | Pause and Resume NAS server replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning NAS server policy. If issue persists, contact your service provider. | file-replication-sessions.non-recoverable-errors-data-oos-waitingonadmin |
| 50102b02 | DATA_NETWORK_PRI_XPER_DATACNXDOWN_RETRY | Data connection is down while file system replication session (id:{{fsReplicationSessionId}}) is transferring and retry failed. | MINOR | Data protection is impacted. | Check connectivity with remote system. Verify and Update if required. | file-replication-sessions.data-network-pri-xper-datacnxdown-retry |
| 50102b01 | DATA_NETWORK_PRI_XPER_DATACNX_DOWN | Data connection is down while file system replication session (id:{{fsReplicationSessionId}}) is transferring. | MINOR | Data protection is impacted. | Check connectivity with remote system. Verify and Update if required. | file-replication-sessions.data-network-pri-xper-datacnx-down |
| 50102c01 | DEST_SPACE_PRI_DOINGPREEVT_SECNOSPACE | File system replication session (id:{{fsReplicationSessionId}}) is unable to transfer data because destination has no space available. | MAJOR | Data protection is impacted. | Add additional storage to the destination appliance or move storage resources within the cluster to another appliance. | file-replication-sessions.dest-space-pri-doingpreevt-secnospace |
| 50102a02 | CTRL_NETWORK_PRI_SEND_DOPREEVT_FAILED | Failed to start data transfer for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data protection is impacted. | Verify and update the remote system. Resolve any outstanding alerts. If the issue persists, contact your service provider. | file-replication-sessions.ctrl-network-pri-send-dopreevt-failed |
| 50102a01 | CTRL_NETWORK_PRI_SEND_DOPOSTEVT_FAILED | Failed to confirm transfer completion for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data protection may be impacted. | Verify and update the remote system. Resolve any outstanding alerts. If the issue persists, contact your service provider. | file-replication-sessions.ctrl-network-pri-send-dopostevt-failed |
| 50102a03 | CTRL_NETWORK_PRI_SEND_START_SEC_FAILED | File system replication session (id:{{fsReplicationSessionId}}) failed to start on the destination due to network issues. | MINOR | Data protection is impacted. | Verify and update the remote system. Resolve any outstanding alerts. If the issue persists, contact your service provider. | file-replication-sessions.ctrl-network-pri-send-start-sec-failed |
| 50102a04 | CTRL_NETWORK_PRI_SEND_STOP_SEC_FAILED_RETRY | File system replication session (id:{{fsReplicationSessionId}}) failed to pause on the destination due to network issues. | MINOR | Data protection is impacted. | Verify and update the remote system. Resolve any outstanding alerts. If the issue persists, contact your service provider. | file-replication-sessions.ctrl-network-pri-send-stop-sec-failed-retry |
| 50102901 | SCHEDULING_RPO_SCH_BECOME_OUT_OF_SYNC | File system replication session (id:{{fsReplicationSessionId}}) is out of sync due to a missed RPO. | MINOR | Data is not synchronized for this RPO cycle. | If the issue recurs, consider updating RPO settings. | file-replication-sessions.scheduling-rpo-sch-become-out-of-sync |
| 50102902 | SCHEDULING_RPO_SCH_TOO_MANY_CONSECUTIVE_OUT_OF_SYNC_WINDOWS | File system replication session (id:{{fsReplicationSessionId}}) is out of sync due to a missed RPO for multiple consecutive transfer windows. | MAJOR | Data transfers are not meeting RPO. | If the issue recurs, consider updating RPO settings. If the issue persists after updating RPO values, contact your service provider for assistance. | file-replication-sessions.scheduling-rpo-sch-too-many-consecutive-out-of-sync-windows |
| 50102904 | SCHEDULING_RPO_SECREMOUNT_FAILED | Failed to remount file system ID {{dstFSId}} on destination. | MINOR | File System session failover and access is impacted. | Retry the NAS server failover operation. If issue persists, contact your service provider. | file-replication-sessions.scheduling-rpo-secremount-failed |
| 50102003 | REPLICATION_SESSION_COMMAND_IN_PROGRESS | Replication session (id:{{replicationSessionId}}) operation is in progress. | MINOR | Replication session (id:{{replicationSessionId}}) operation is in progress. | file-replication-sessions.replication-session-command-in-progress | |
| 50102004 | REPLICATION_SESSION_PARTIAL_DELETED | Replication session (id:{{replicationSessionId}}) is in a partially deleted state. | MINOR | Replication session (id:{{replicationSessionId}}) is partially deleted. | Automatic retry of session delete is attempted. If condition persists, contact your service provider. | file-replication-sessions.replication-session-partial-deleted |
| 50102005 | REPLICATION_SESSION_DEGRADED | Replication session (id:{{replicationSessionId}}) is in Error state. | MAJOR | One or more file system sessions are in Error state, impacting data protection on the replication sessions. | Pause and Resume replication session. If the replication session cannot be resumed successfully, delete and recreate the replication session by unassigning and reassigning the policy. | file-replication-sessions.replication-session-degraded |
| 50102008 | REPLICATION_SESSION_PARTIAL_ACTIVE | Replication session (id:{{replicationSessionId}}) is in Partial Paused state. | MINOR | Some of the replication sessions are not paused. | Retry the Pause operation. If the issue persists, contact your service provider for assistance. | file-replication-sessions.replication-session-partial-active |
| 50102009 | REPLICATION_SESSION_PARTIAL_FAILEDOVER | Replication session (id:{{replicationSessionId}}) is in Partial Failed Over state. | MINOR | One or more replication sessions did not failover. | Retry the Failover operation. If the issue persists, contact your service provider for assistance. | file-replication-sessions.replication-session-partial-failedover |
| 5010200a | REPLICATION_SESSION_PARTIAL_SWITCHEDOVER | Replication session (id:{{replicationSessionId}}) is in Partial Failed Over state. | MINOR | One or more replication sessions did not failover. | Retry the Failover operation. If the issue persists, contact your service provider for assistance. | file-replication-sessions.replication-session-partial-switchedover |
| 5010200b | REPLICATION_SESSION_PARTIAL_REPROTECTED | Replication session (id:{{replicationSessionId}}) is in Partial Reprotected state. | MINOR | One or more replication sessions are not reprotected. | Retry the reprotect operation. If the issue persists, contact your service provider for assistance. | file-replication-sessions.replication-session-partial-reprotected |
| 50103301 | FS_STATE_FS_REPLICATION_SESSION_PRISCH_REFRESH_FAIL_FS_NOTMOUNTED | Failed to start the scheduled data transfer because source file system is offline. | MINOR | File system data protection is impacted. | Contact your service provider for assistance. | file-replication-sessions.fs-state-fs-replication-session-prisch-refresh-fail-fs-notmounted |
| 50102701 | FS_REPLICATION_SESSIONS_SOME_NOT_CREATED | One or more file system replication sessions were not created for NAS server replication session (id:{{replicationSessionId}}). | MINOR | Data protection is impacted for one or more file system sessions. | Update of NAS server replication session will be initiated automatically. | file-replication-sessions.fs-replication-sessions-some-not-created |
| 50102d01 | DATA_SYNC_STATE_DATA_OOS_SYNCQUEUE | Data transfer is waiting for resource availability for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data transfer for the file system replication session is impacted. | No action is required. The data transfer will resume automatically. | file-replication-sessions.data-sync-state-data-oos-syncqueue |
| 50102d03 | DATA_SYNC_STATE_DATA_OOS_SYSFRACTURE | Data transfer is paused for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data transfer for the paused session is impacted. | When synchronization occurs, transfer will automatically resume. | file-replication-sessions.data-sync-state-data-oos-sysfracture |
| 50102d02 | DATA_SYNC_STATE_DATA_SYNC_SYSFRACTURE | Data transfer is paused for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data transfer for the paused session is impacted. | When synchronization occurs, transfer will automatically resume. | file-replication-sessions.data-sync-state-data-sync-sysfracture |
| 50102d04 | DATA_SYNC_STATE_DATA_SYNC_SYNCREP_SYNCING | Data transfer is onging for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Replication data protection is not synchronized. | No action is required. | file-replication-sessions.data-sync-state-data-sync-syncrep-syncing |
| 50102d08 | DATA_SYNC_STATE_DATA_SYNC_SYNCQUEUE | Data transfer is waiting for resource availability for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data transfer for the file system replication session is impacted. | No action is required. The data transfer will resume automatically. | file-replication-sessions.data-sync-state-data-sync-syncqueue |
| 50102d0a | DATA_SYNC_STATE_DATA_OOS_NDUPAUSED | Data transfer is paused for file system replication session (id:{{fsReplicationSessionId}}) due to NDU. | MINOR | Data transfer is paused for replication session during NDU. | Wait for the NDU to complete. The data transfer will resume automatically. | file-replication-sessions.data-sync-state-data-oos-ndupaused |
| 50102d0b | DATA_SYNC_STATE_DATA_OOS_SIZEMISMATCH | Data transfer failed due to a mismatch in file system size between source and destination for file system replication session (id:{{fsReplicationSessionId}}). | MINOR | Data transfer will not be performed. | Update source file system size to match the destination. Data transfer will resume automatically. | file-replication-sessions.data-sync-state-data-oos-sizemismatch |
| 50103401 | DST_FREESPACE_FS_REPLICATION_SESSION_DESTINATION_EXPAND_FAILED | Source scheduler failed to expand on destination | MAJOR | The system could not expand on destination as backend is out of space. | Add additional backend storage on destination. The destination will be expanded in subsequent RPO cycle after fixing the issue. | file-replication-sessions.dst-freespace-fs-replication-session-destination-expand-failed |
| 50102f01 | CLUSTER_COMMUNICATION_CLUSTER_COMMUNICATION_DOWN | NAS server replication session (id:{{replicationSessionId}}) is unable to reach the remote NAS node. | MINOR | NAS replication management and data protection may be impacted. | Verify File mobility network communication between source and destination NAS nodes. | file-replication-sessions.cluster-communication-down |
| 50103101 | NAS_SERVER_STATE_REPLICATION_SESSION_NAS_DOWN | Replication session (id:{{replicationSessionId}}) running on NAS server with (id:{{nasGuid}}) is down. | MAJOR | Data protection is impacted on the NAS server. | Contact your service provider to recover NAS server. | file-replication-sessions.nas-server-state-replication-session-nas-down |
| 50103201 | NAS_SERVER_STATE_FS_REPLICATION_SESSION_VDM_DOWN | File system replication session (id:{{fsReplicationSessionId}}) running on NAS server with (id:{{nasGuid}}) is down. | MAJOR | Data protection is impacted on the File system. | Check and resolve any related outstanding alerts. If issue persists, contact your service provider. | file-replication-sessions.nas-server-state-fs-replication-session-vdm-down |
| 50103502 | PEER_VDM_STATUS_PEERVDM_IN_MAINTENANCE | NAS server is in maintenance mode for replication session (id:{{replicationSessionId}}). | MAJOR | NAS server and data protection are not available. | Contact your service provider for assistance. | file-replication-sessions.peer-vdm-status-peervdm-in-maintenance |
| 50102102 | PEER_VDM_INTFDEVICE_MATCH_PEER_VDM_INTFDEVICE_NOT_MATCH | Remote NAS server network configuration is different than local side for replication session (id:{{replicationSessionId}}). | MINOR | File interface will not be reachable after failover, unless override settings are specified, and data access may be impacted. | Verify NAS file interface configuration on remote NAS server. If required, select override settings of the file interface on remote NAS server. | file-replication-sessions.peer-vdm-intfdevice-match-peer-vdm-intfdevice-not-match |
| 50104401 | REPLICATION_SCHEDULER_CONTROLER_SCH_IN_SYNC_DISABLED | All filesystem replication sessions disabled initial sync for NAS server replication session '{{replicationSessionName}}'. | MINOR | All filesystem replication sessions disabled initial sync for NAS server replication session '{{replicationSessionName}}' ({{replicationSessionId}}). | Please set scheduler enabled through replication modify action. | file-replication-sessions.replication-scheduler-controler-sch-in-sync-disabled |
| 50100801 | FS_FREESPACE_FS_LOW_SPACE | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is low on free space. | MINOR | The file system is running low on free space. New data writes and file creations may start failing. | Provision additional storage to the file system, or increase its size. | file-systems.fs-freespace-fs-low-space |
| 50100803 | FS_FREESPACE_FS_SPACE_WARNING | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is running out of space. | MAJOR | The file system is running out of space. | New data writes and file creations may start failing, provision additional storage to the storage resource, or balance data usage with other storage resources on the system. | file-systems.fs-freespace-fs-space-warning |
| 50100902 | FS_STATE_UNMOUNTED_IO_ERROR | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is offline due to receiving an I/O error. | CRITICAL | The file system has received an I/O error and is unmounted. There may be a problem with the storage device. | Contact your service provider. | file-systems.fs-state-unmounted-io-error |
| 50100903 | FS_STATE_UNMOUNTED_CORRUPTION_DETECTED | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is offline after discovering corruption. | CRITICAL | The file system has discovered internal corruption and is unmounted. | Contact your service provider. | file-systems.fs-state-unmounted-corruption-detected |
| 50100904 | FS_STATE_SERVICE_UNMOUNTED | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) has been taken offline for service. | MAJOR | The file system has been taken offline for service. | Complete the planned service procedure and remount the FS using 'svc_recover -action mount'. | file-systems.fs-state-service-unmounted |
| 50100905 | FS_STATE_RECOVERED_OK | File system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) has completed recovery and is waiting to be remounted. | MAJOR | The file system has completed recovery and is waiting to be remounted. | Remount the FS using 'svc_recover -action mount' | file-systems.fs-state-recovered-ok |
| 50100906 | FS_STATE_RECOVERY_FAILED | Recovery failed on file system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | Recovery failed on the file system, manual intervention is likely needed. | Contact your service provider. | file-systems.fs-state-recovery-failed |
| 50100907 | FS_STATE_CREATE_FAILED_COULD_NOT_CLEANUP | File system {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The file system create has failed, the object is not usable. | Attempt to delete the file system object at a later time. | file-systems.fs-state-create-failed-could-not-cleanup |
| 50100908 | FS_STATE_SNAP_CREATE_FAILED_COULD_NOT_CLEANUP | Snap {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The snap create has failed, the object is not usable. | Attempt to delete the snap object at a later time. | file-systems.fs-state-snap-create-failed-could-not-cleanup |
| 50100909 | FS_STATE_CLONE_CREATE_FAILED_COULD_NOT_CLEANUP | Clone {{fsname}} in NAS server {{vdmname}} failed creation but could not cleanup the object completely. The object is not usable and can only be deleted. | CRITICAL | The clone create has failed, the object is not usable. | Attempt to delete resulting file system object at a later time. | file-systems.fs-state-clone-create-failed-could-not-cleanup |
| 5010090a | FS_STATE_FS_DELETE_PARTIALLY_FAILED | File system {{fsname}} in NAS server {{vdmname}} partially failed delete. The object is likely no longer fully usable and can only be deleted. | CRITICAL | The file system delete has partially failed, the object is not usable. | Attempt to delete the file system object again at a later time. | file-systems.fs-state-fs-delete-partially-failed |
| 5010090b | FS_STATE_SNAP_DELETE_PARTIALLY_FAILED | Snap {{fsname}} in NAS server {{vdmname}} partially failed delete. The object is likely no longer fully usable and can only be deleted. | CRITICAL | The snap delete has partially failed, the object is not usable. | Attempt to delete the snap object again at a later time. | file-systems.fs-state-snap-delete-partially-failed |
| 50100a01 | FS_STORAGE_DEVICE_POTENTIALLY_IMPACTED | Recovery is recommended on file system {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | The file system's backing storage LUN has reported a potential impact; recovery is recommended on the FS. | Contact your service provider. | file-systems.fs-storage-device-potentially-impacted |
| 50101a01 | FS_BLOCKIO_FS_BLOCKIO_NOT_MATCH_ALLOCATON_SIZE | File system {{fsname}} in NAS server {{vdmname}} I/O patterns do not match the allocation size ({{actualSize}} bytes). | MINOR | The applications using the file system are not doing I/O in the optimal block size for the file system. | Review application settings to match file system allocation size, or consider provisioning a new file system for the existing application using suggested allocation unit size of %(suggestedSize) bytes. | file-systems.fs-blockio-not-match-allocaton-size |
| 50101a03 | FS_BLOCKIO_FS_BLOCKIO_NOT_ALIGNED | File system {{fsname}} in NAS server {{vdmname}} I/O patterns are not aligned with the allocation size ({{actualSize}} bytes). | MINOR | The applications using the file system are doing unaligned I/O to the file system. | Host I/O patterns are not using 8K multiples. Set the host I/O patterns to match file system allocation size. | file-systems.fs-blockio-not-aligned |
| 50103a01 | FS_SNS_CORRUPTION_SNS_DB_NOT_READABLE | One or more namespaces couldn't be read from unifiedNamespace DB. | MAJOR | One or more namespaces couldn't be read from unifiedNamespace DB on filesystem '{{fsName}}' in NAS server '{{vdmName}}'. | Use svc_uns checkDBStructure tool for further information. | file-systems.fs-sns-corruption-sns-db-not-readable |
| 50101c01 | SECURITY_NO_CA_CLUSTER_CERT | The CA cluster certificate cannot be generated: {{errormsg}}. | CRITICAL | The cluster instance cannot generate the CA certificate: {{errormsg}}. As a consequence, data nodes cannot join the NAS cluster. | Contact your service provider. | tbd.security-no-ca-cluster-cert |
| 50101c02 | SECURITY_NO_NODE_CERT | The node {{node_id}} certificate cannot be generated: {{errormsg}}. | CRITICAL | The node {{node_id}} cannot generate his certificate: {{errormsg}}. As a consequence, the node cannot join the NAS cluster. | Contact your service provider. | tbd.security-no-node-cert |
| 50103e01 | CLUSTER_LOCKBOX_OPEN_CLUSTER_LOCKBOX_FAILURE | The lockbox file cannot be opened: {{errormsg}} | CRITICAL | The lockbox file containing all the credentials, including the passwords, cannot be opened. So this node cannot communicate anymore with storage backend and infrastructure server. | N/A | nas-cluster-config.open-cluster-lockbox-failure |
| 50103e02 | CLUSTER_LOCKBOX_INVALID_CLUSTER_LOCKBOX_ENTRY | The lockbox file contains some invalid entries. | MAJOR | The lockbox file containing all the credentials, including the passwords, contains one or several incorrect entries. Depending of these entries, some features, including the connection to the storage backend or infrastructure server, are impacted. | N/A | nas-cluster-config.invalid-cluster-lockbox-entry |
| 50103f04 | NODE_LOCKBOX_OPEN_NODE_LOCKBOX_FAILURE | The lockbox file for node {{node_id}} cannot be opened: {{errormsg}} | CRITICAL | The lockbox file for node {{node_id}} containing all the credentials, including the passwords, cannot be opened. So this node cannot communicate anymore with storage backend and infrastructure server. | N/A | nas-nodes.open-node-lockbox-failure |
| 50103f05 | NODE_LOCKBOX_INVALID_NODE_LOCKBOX_ENTRY | The lockbox file for node {{node_id}} contains some invalid entries. | MAJOR | The lockbox file for node {{node_id}} containing all the credentials, including the passwords, contains one or several incorrect entries. Depending of these entries, some features, including the connection to the storage backend or infrastructure server, are impacted. | N/A | nas-nodes.invalid-node-lockbox-entry |
| 50100201 | SMB_DC_NO_MORE_DC | The NAS server {{nasServer}} in the domain {{domain}} can't reach any Domain Controller. | MAJOR | The domain controllers are not reachable. An SMB server needs to communicate with a domain controller to work properly. | Check that the Domain Controllers are up and running and check the connectivity with the Domain Controllers. | smb-servers.smb-dc-no-more-dc |
| 50100301 | SMB_SERVER_JOINED_NO | The SMB server of the NAS server {{nasServer}} is configured to be joined to the domain {{domain}}, but is currently not joined. | MAJOR | In order to work, an SMB server which is not standalone must be joined to the active directory of the MS Windows domain. The SMB server can not accept client connections in this state. | Join the SMB server with join rest api call. This may also be due to a bad DNS configuration. | smb-servers.smb-server-joined-no |
| 50100e03 | SNAP_FREESPACE_WARNING | File system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is running out of space. | MINOR | The snap is running out of space. | New data writes and file creations may start failing, provision additional storage to the storage resource, or balance data usage with other storage resources on the system. | file-systems.snap-freespace-warning |
| 50100f02 | SNAP_STATE_UNMOUNTED_IO_ERROR | File system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is offline due to receiving an I/O error. | CRITICAL | The snap has received an I/O error and is unmounted. There may be a problem with the storage device. | Contact your service provider. | file-systems.snap-state-unmounted-io-error |
| 50100f03 | SNAP_STATE_UNMOUNTED_CORRUPTION_DETECTED | File system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) is offline after discovering corruption. | CRITICAL | The snap has discovered internal corruption and is unmounted. | Contact your service provider. | file-systems.snap-state-unmounted-corruption-detected |
| 50100f04 | SNAP_STATE_SERVICE_UNMOUNTED | File system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) has been taken offline for service. | MAJOR | The snap has been taken offline for service. | Complete the planned service procedure and remount the snap using 'svc_recover -action mount'. | file-systems.snap-state-service-unmounted |
| 50100f05 | SNAP_STATE_RECOVERED_OK | File system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}) has completed recovery and is waiting to be remounted. | MAJOR | The snap has completed recovery and is waiting to be remounted. | Remount the snap with 'svc_recover -action mount' | file-systems.snap-state-recovered-ok |
| 50100f06 | SNAP_STATE_RECOVERY_FAILED | Recovery failed on file system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}. | CRITICAL | Recovery failed on the snap, manual intervention is likely needed. | Contact your service provider. | file-systems.snap-state-recovery-failed |
| 50101001 | SNAP_STORAGE_DEVICE_POTENTIALLY_IMPACTED | Recovery is recommended on file system snapshot {{fsname}} in NAS server {{vdmname}} (fsid {{fsid}}). | CRITICAL | The snap's backing storage LUN has reported a potential impact; recovery is recommended on the snap. | Contact your service provider. | file-systems.snap-storage-device-potentially-impacted |
| 50102e02 | SNAP_SCHED_HEALTH_ERROR_FOR_SOME_FILE_SYSTEMS | Snap schedule {{schedname}} ({{schedoid}}) has errors creating some file system snaps. | MINOR | The snap schedule is having problems creating snapshots for some file systems attached to the schedule. | Check logs for information as to why the snaps are not being created properly. Contact service provider if issue can not be resolved. | file-systems.snap-sched-health-error-for-some-file-systems |
| 50102e03 | SNAP_SCHED_HEALTH_ERROR_FOR_ALL_FILE_SYSTEMS | Snap schedule {{schedname}} ({{schedoid}}) has errors creating snaps of all attached file systems. | MAJOR | The snap schedule is having problems creating snapshots for all file systems attached to the schedule. | Check logs for information as to why the snaps are not being created properly. Contact service provider if issue can not be resolved. | file-systems.snap-sched-health-error-for-all-file-systems |
| 50103d02 | SNAP_SCHED_OVERRUN_SCHEDULE_DELAYED | Snap schedule {{schedname}} ({{schedoid}}) had to delay creating a new set of snaps because it had not yet completed creating the previous set of snaps. | MINOR | The snap schedule had to delay creating a new set of snaps because it had not yet completed creating the previous set of snaps. | Check logs for information as to why the snaps were not being created in a timely manner. Contact service provider if issue can not be resolved. | file-systems.snap-sched-overrun-schedule-delayed |
| 50103806 | SNS_SMB_CONFIG_SMB_NO_SERVER | The unifiedNamespace '{{unifiedNamespace}}' SMB access can not be configured without an SMB server. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' SMB access can not be properly configured without an SMB server. | Create an SMB server and then issue a restoreAccess action on the namespace. | file-unified-namespaces.sns-smb-config-smb-no-server |
| 50103807 | SNS_SMB_CONFIG_SMB_NO_SHARE | The unifiedNamespace '{{unifiedNamespace}}' SMB access is not properly configured. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' SMB access is not properly configured. The SMB share {{share}} was not found. | Issue a restoreAccess action on the namespace. | file-unified-namespaces.sns-smb-config-smb-no-share |
| 50103808 | SNS_SMB_CONFIG_SMB_NO_DFS_ENABLED | The unifiedNamespace '{{unifiedNamespace}}' SMB access is not properly configured. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' SMB access is not properly configured. The SMB share {{share}} was found but it is not dfsEnabled. | Issue a restoreAccess action on the namespace. | file-unified-namespaces.sns-smb-config-smb-no-dfs-enabled |
| 5010390b | SNS_NFS_CONFIG_NFS_NO_SERVER | The unifiedNamespace '{{unifiedNamespace}}' NFS access can not be configured without an NFS server. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' NFS access can not be properly configured without an NFS server. | Create an NFS server with NFSv4 enabled and then issue a restoreAccess action on the namespace. | file-unified-namespaces.sns-nfs-config-nfs-no-server |
| 5010390c | SNS_NFS_CONFIG_NFS_NO_NFSV4 | The unifiedNamespace '{{unifiedNamespace}}' NFS access can not be configured without NFSv4 support. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' NFS access can not be properly configured without NFSv4 support on the NFS server. | Modify the NFS server on this nasServer to enable NFSv4. | file-unified-namespaces.sns-nfs-config-nfs-no-nfsv4 |
| 5010390d | SNS_NFS_CONFIG_NFS_NO_EXPORT | The unifiedNamespace '{{unifiedNamespace}}' NFS access is not properly configured. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' NFS access is not properly configured. The NFS export {{nfsExport}} was not found. | Issue a restoreAccess action on the namespace. | file-unified-namespaces.sns-nfs-config-nfs-no-export |
| 50103b01 | SNS_HEALTH_NS_PATH_NOT_FOUND | The unifiedNamespace '{{unifiedNamespace}}' path is not valid. | MAJOR | The unifiedNamespace '{{unifiedNamespace}}' path '{{path}}' saved in the namespace metadata was not found or can't be opened. | Use svc_uns tool for further information. | file-unified-namespaces.sns-health-ns-path-not-found |
| 50103b02 | SNS_HEALTH_NS_INACTIVE_CLONE_FOUND | The namespace {{unifiedNamespace}} is not activated namespace clone. | MINOR | The namespace {{unifiedNamespace}} is detected as not activated namespace clone and it is not functional. | Use REST API activate /instances/unifiedNamespace/{id}/action/activateClone to activate the namespace. | file-unified-namespaces.sns-health-ns-inactive-clone-found |
| 50103b03 | SNS_HEALTH_NS_LOAD_FAILED | The namespace {{unifiedNamespace}} load failed. | MAJOR | The namespace {{unifiedNamespace}} load failed. | Use svc_uns tool for further information. | file-unified-namespaces.sns-health-ns-load-failed |
| 50103b04 | SNS_HEALTH_NS_LINK_NOT_ALL_TARGETS_LOADED | The namespace {{unifiedNamespace}} links load failed. | MAJOR | The namespace {{unifiedNamespace}} links load failed. The link(s) metadata can be corrupted or the link(s) path can't be opened. | Use svc_uns tool for further information. | file-unified-namespaces.sns-health-ns-link-not-all-targets-loaded |
| 50100601 | TREEQUOTA_SOFT_LIMIT_CROSSED | Total space usage for file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit. | MINOR | The soft quota limit has been crossed for the quota tree specified in the error message. | The soft quota for the quota tree specified in the error message has been crossed. Users must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the soft quota limit for the quota tree. | file-tree-quotas.treequota-soft-limit-crossed |
| 50100602 | TREEQUOTA_SOFT_LIMIT_GRACE_EXPIRED | Total space usage for file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit, and the grace period has expired. | MAJOR | The soft quota limit has been crossed and the grace period has expired for the quota tree specified in the error message. All further write operations for the quota tree will fail. | The soft quota for the quota tree specified in the error message has been crossed and the grace period has expired. All further write operations for the quota tree will fail. Users must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the block soft quota limit for the quota tree. | file-tree-quotas.treequota-soft-limit-grace-expired |
| 50100603 | TREEQUOTA_HARD_LIMIT_EXCEEDED | Total space usage for file system {{fs}}, quota tree {{treePath}} has reached the hard quota limit. Users can no longer write to the quota tree unless this issue is addressed. | MAJOR | The hard quota limit has been reached or exceeded for the quota tree specified in the error message. All further write operations for the quota tree will fail. | The hard quota for the quota tree specified in the error message has been reached and all further write operations for the quota tree will fail. Users must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the hard quota limit for the quota tree. | file-tree-quotas.treequota-hard-limit-exceeded |
| 50100604 | TREEQUOTA_MULTIPLE_SOFT_LIMIT_BREACH | Total space usage for file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit {{softViolations}} times. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MINOR | Soft quota has been crossed multiple times for the specified tree in the error message. | Too much space has been consumed on the specified quota tree. You should delete unwanted files and directories from the quota tree. Alternatively, the administrator can increase the soft quota limit for the quota tree. | file-tree-quotas.treequota-multiple-soft-limit-breach |
| 50100605 | TREEQUOTA_MULTIPLE_HARD_LIMIT_BREACH | Total space usage for file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit, grace period, and hard quota limit. Soft quota limit crossed {{softViolations}} times, grace period expired {{softGraceExpiredViolations}} times, hard quota limits reached {{hardViolations}} times. Users can no longer write to the quota tree unless this issue is addressed. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MAJOR | Hard quota limits have been reached multiple times for the specified tree in the error message. If usage still exceeds quota limits, then all further write operations for the specified tree will fail. | Too much space has been consumed on the specified quota tree. Users must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the hard quota limits for the quota tree. | file-tree-quotas.treequota-multiple-hard-limit-breach |
| 50100701 | USERQUOTA_FS_SOFT_LIMIT_CROSSED | Space usage by user {{userName}} in file system {{fs}} has exceeded the preferred (soft quota) limit.EXPIRED | MINOR | The soft quota limit has been crossed for the user in the file system specified in the error message. | The soft quota for the user in the file system specified in the error message has been crossed. The user must delete unwanted files or directories, reducing the percentage of used space. Alternatively, the administrator may increase the block soft quota limit for the affected user. | file-user-quotas.userquota-fs-soft-limit-crossed |
| 50100702 | USERQUOTA_FS_SOFT_LIMIT_GRACE_EXPIRED | Space usage by user {{userName}} in file system {{fs}} has exceeded the preferred (soft quota) limit, and the grace period has expired. The user can no longer write to the file system unless this issue is addressed. | MAJOR | The soft quota limit has been crossed and the grace period has expired for the user in the file system specified in the error message. All further write operations for the specified user will fail. | The soft quota for the user in the file system specified in the error message has been crossed and the grace period has expired. All further write operations for the specified user will fail. The user must delete unwanted files or directories, reducing the percentage of used space. Alternatively, the administrator may increase the block soft quota limit for the affected user. | file-user-quotas.userquota-fs-soft-limit-grace-expired |
| 50100703 | USERQUOTA_FS_HARD_LIMIT_EXCEEDED | Space usage by user {{userName}} in file system {{fs}} has reached the hard quota limit. The user can no longer write to the file system unless this issue is addressed. | MAJOR | The hard quota limit has been reached or exceeded for user in the file system specified in the error message. All further write operations for the specified user will fail. | The hard quota for the user in the file system specified in the error message has been reached. All further write operations for this user will fail. The user must delete unwanted files or directories, reducing the percentage of used space. Alternatively, the administrator may increase the hard quota limit for the affected user. | file-user-quotas.userquota-fs-hard-limit-exceeded |
| 50100704 | USERQUOTA_TREE_SOFT_LIMIT_CROSSED | Space usage by user {{userName}} in file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit. | MINOR | The soft quota limit has been crossed for the user in the quota tree specified in the error message. | The soft quota for the user in the quota tree specified in the error message has been crossed. The user must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the block soft quota limit for the user in the specified quota tree. | file-user-quotas.userquota-tree-soft-limit-crossed |
| 50100705 | USERQUOTA_TREE_SOFT_LIMIT_GRACE_EXPIRED | Space usage by user {{userName}} in file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit, and the grace period has expired. The user can no longer write to the quota tree unless this issue is addressed. | MAJOR | The block soft quota limit has been crossed and the grace period has expired for the user in the quota tree specified in the error message. All further write operations for the specified user in the quota tree will fail. | You have used too much space in the specified quota tree and will no longer be able to write to it unless you delete unwanted files and directories to reduce the percentage of used space. Alternatively, the administrator can increase your soft quota limit for that quota tree. | file-user-quotas.userquota-tree-soft-limit-grace-expired |
| 50100706 | USERQUOTA_TREE_HARD_LIMIT_EXCEEDED | Space usage by user {{userName}} in file system {{fs}}, quota tree {{treePath}} has reached the hard quota limit. The user can no longer write to the quota tree unless this issue is addressed. | MAJOR | The hard quota limit has been reached for the user and quota tree specified in the error message. All further write operations in the quota tree for this user will fail. | The user must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the block hard quota limit for the user in the specified quota tree. | file-user-quotas.userquota-tree-hard-limit-exceeded |
| 50100707 | USERQUOTA_MULTIPLE_FS_SOFT_LIMIT_BREACH | Space usage by user {{user}} in file system {{fs}} has exceeded the preferred (soft quota) limit {{softViolations}} times. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MINOR | Soft quota has been crossed multiple times for the specified user in the error message. | The specified user must delete unwanted files or directories, reducing the percentage of used space. Alternatively, the administrator can increase the soft quota limit for the user. | file-user-quotas.userquota-multiple-fs-soft-limit-breach |
| 50100708 | USERQUOTA_MULTIPLE_FS_HARD_LIMIT_BREACH | Space usage by user {{user}} in file system {{fs}} has exceeded the preferred (soft quota) limit, grace period, and hard quota limit. Soft quota limit exceeded {{softViolations}} times, grace period expired {{softGraceExpiredViolations}} times, hard quota limits reached {{hardViolations}} times. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MAJOR | Soft and hard quota limits have been reached or exceeded multiple times for the specified user in the error message. If usage still exceeds quota limits, then all further write operations for the specified user will fail. | You have used too much space in the specified file system and will no longer be able to write to the file system unless you delete unwanted files and directories from it. Alternatively, the administrator can increase your quota limits for the file system. | file-user-quotas.userquota-multiple-fs-hard-limit-breach |
| 50100709 | USERQUOTA_MULTIPLE_TREE_SOFT_LIMIT_BREACH | Space usage by user {{user}} in file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit {{softViolations}} times. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MINOR | The soft quota limit has been crossed multiple times for the tree and user identified in the brief description. | The soft quota for the user in the quota tree specified in the error message has been crossed. The user must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the soft quota limit for the affected user in the quota tree. | file-user-quotas.userquota-multiple-tree-soft-limit-breach |
| 5010070a | USERQUOTA_MULTIPLE_TREE_HARD_LIMIT_BREACH | Space usage by user {{user}} in file system {{fs}}, quota tree {{treePath}} has exceeded the preferred (soft quota) limit, grace period, and hard quota limit. Soft quota limit crossed {{softViolations}} times, grace period expired {{softGraceExpiredViolations}} times, hard quota limits reached {{hardViolations}} times. First violation {{firstViolation}}, most recent violation {{lastViolation}}. | MAJOR | Soft and hard quota limits have been reached or exceeded multiple times for the specified user and tree in the error message. If usage still exceeds quota limits, then all further write operations for the specified user in this tree will fail. | The specified user must delete unwanted files or directories in the quota tree, reducing the percentage of used space. Alternatively, the administrator may increase the block hard quota limit for user in the quota tree. | file-user-quotas.userquota-multiple-tree-hard-limit-breach |
| 5010070d | USERQUOTA_BLOCK_TREE_QUOTA_ON_CHECK_HARD_LINK_FOUND | Tree quota creation in filesystem {{fs}} on path {{treePath}} failed because a hard link (inode number: {{inum}}) was found. Delete the hard links and try again. | MAJOR | The create tree quota operation failed because a hard link was found in the current tree quota path. Hard links are not supported for tree quotas. Delete the hard links and try creating the tree quota again. | Hard link is not supported in tree quota. To create tree quota on the directory, please: 1) Find all the hard links in dirctory and delete them. 2) Create tree quota again. | file-user-quotas.userquota-block-tree-quota-on-check-hard-link-found |
| 5010070e | USERQUOTA_BLOCK_QUOTA_CREATION_CHECK_FAILED | The system could not create a quota for file system {{fs}} in path {{treePath}}. | MINOR | The system could not create a quota for a file system. | Please retry the operation. | file-user-quotas.userquota-block-quota-creation-check-failed |
| 50100b02 | VIRUS_CHECKER_ALL_SERVERS_UNREACHABLE | No virus checker server is available. | MAJOR | Virus checking is not operational until a virus checker server becomes available. | Make sure the virus checker servers are online. | file-virus-checkers.virus-checker-all-servers-unreachable |
| 50100b03 | VIRUS_CHECKER_SOME_SERVERS_UNREACHABLE | One or more virus checker servers are currently unavailable. | MAJOR | One or more virus checker servers are currently unavailable. | file-virus-checkers.virus-checker-some-servers-unreachable |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\