|
System Event Message |
Description/Meaning or Action |
|
System Event = Type 1 |
|
System requires a Restore Manager (RM) recovery. |
|
|
System failed basic initialization. |
|
|
HTTP Service failed. Web services will be unavailable. |
|
|
HTTP Service started. |
Informational message. No user intervention is required. |
|
HTTP Service is available now. |
Informational message. No user intervention is required. |
|
Diagnostics collection service failed. |
|
|
Diagnostic collection service started. |
Informational message. No user intervention is required. |
|
Diagnostics collection service re-started. |
Informational message. No user intervention is required. |
|
Configuration Service started. |
Informational message. No user intervention is required. |
|
Configuration Service is not healthy. |
|
|
Configuration Service is healthy. |
Informational message. No user intervention is required. |
|
Configuration Service failed to start. |
|
|
Unsupported RAID Configuration detected. |
|
|
No Fault Tolerant RAID configuration found. |
|
|
Data volume not present. |
Check all drives are inserted and powered up. |
|
Unable to detect filesystem type on data volume. |
|
|
Non certified disk drive detected. Disk needs to be pulled out for the system to become operational. |
Disk needs to be pulled out for the system to become operational. |
|
NVRAM devices not found. |
Check card is seated properly. |
|
Invalid/Unsupported Network Configuration detected. |
Use CLI "network --restart" to re-configure network cards. |
|
Some of the network cards are not part of the bond configuration. |
|
|
No IP address has been assigned to the system. |
|
|
No valid hostname has been assigned to the system. |
Use "system --setname" to set hostname. |
|
No valid system name found in configuration Database. |
Use "maintenance --configuration --restore" to recover from backup configuration. |
|
No valid system configuration file(s) found in configuration database. |
Use "maintenance --configuration --restore" to restore from backup configuration. |
|
Data volume filesystem is not yet initialized. |
|
|
Backup configuration file is missing. |
Contact Technical Support. |
|
Working configuration file is missing. |
Use "maintenance --configuration --restore" to restore configuration from backup. |
|
Working configuration file is corrupted. |
Use "maintenance --configuration --restore" to restore configuration from backup. |
|
NVRAM signature is missing. |
If NVRAM device was replaced use "maintenance --hardware --reinit_nvram" to initialize NVRAM. |
|
Windows Active Directory client module failed to start. Active Directory support will not be available. |
|
|
Windows Active Directory client module started. |
Informational message. No user intervention is required. |
|
Windows Server module started. |
Informational message. No user intervention is required. |
|
Windows Server module re-started. |
Informational message. No user intervention is required. |
|
Windows Server module is down. Windows client access will be disrupted. |
|
|
Windows Server module has been disabled because of multiple crashes. |
|
|
System initialization is required. |
Informational message. No user intervention is required. |
|
Filesystem server maintenance requested. |
|
|
Filesystem server re-started. |
Informational message. No user intervention is required. |
|
Filesystem server started. |
Informational message. No user intervention is required. |
|
Filesystem server re-started, in Read-Only mode. |
Informational message. No user intervention is required. |
|
Filesystem server started, in Read-Only mode. |
Informational message. No user intervention is required. |
|
Filesystem server is not healthy. Client access will be interrupted. |
|
|
Filesystem scan triggered. |
|
|
Filesystem check re-started. |
Informational message. No user intervention is required. |
|
Filesystem check continued from previous boot. |
Informational message. No user intervention is required. |
|
Filesystem checker is not healthy, will be re-started. |
|
|
Filesystem checker terminated with unexpected error. |
|
|
Filesystem checker crashing multiple times, entering support mode. |
Please contact Technical Support. |
|
Diagnostics collection module failed to start. |
Reboot the system to recover. If problem persists contact Technical Support. |
|
Hardware Health Monitor module failed to start. |
Reboot the system to recover. If problem persists contact Technical Support. |
|
System is exiting Support Mode. |
Informational message. No user intervention is required. |
|
De-dupe engine dictionary is corrupted. |
Use "maintenance --configuration --reinit_dictionary" to re-init. |
|
Not enough memory to validate NVRAM contents. |
System reboot is required. |
|
Failed to complete basic system initialization. |
|
|
Unable to detect filesystem type on the Name Space Volume. |
|
|
Name Space Volume is not mounted. |
|
|
iSCSI server started. |
Informational message. No user intervention is required. |
|
iSCSI server re-started. |
Informational message. No user intervention is required. |
|
iSCSI server is not healthy. |
|
|
iSCSI server is crashing repeatedly. |
Contact Technical Support. |
|
NDMP tape server started. |
Informational message. No user intervention is required. |
|
NDMP tape server re-started. |
Informational message. No user intervention is required. |
|
NDMP tape server is not healthy. |
|
|
NDMP tape server has crashed repeatedly. |
Contact Technical Support. |
|
Virtual Tape Library daemons started successfully. |
Informational message. No user intervention is required. |
|
Virtual Tape Library daemons re-started successfully. |
Informational message. No user intervention is required. |
|
Virtual Tape Library daemons are not healthy. |
|
|
Virtual Tape Library daemons have crashed repeatedly. All Virtual Tape functionality will not be available. |
|
|
Failed to process deleted files and containers. |
Contact Technical Support. |
|
Internal failure processing ingest log. |
Contact Technical Support for assistance or intervention. |
|
Hardware Health Monitor Database is corrupted. |
Use "maintenance --hardware --restore_hw_db". |
|
Unable to communicate with Hardware Health Monitor. |
Informational message. No user intervention is required. |
|
Unable to communicate with NVRAM device. Check hardware. |
Verify that the NVRAM card is seated properly in the DR Series system appliance. Contact Technical Support for assistance or intervention. |
|
Capacitor is disconnected from NVRAM. If problem persist after reboot, replace NVRAM card. |
Contact Technical Support for assistance or intervention. |
|
SSD is disconnected from NVRAM device. If problem persist after reboot, replace NVRAM card. |
Contact Technical Support for assistance or intervention. |
|
NVRAM capacitor is not charging. If problem persist after 5 minutes of power shutdown, replace NVRAM card. |
Contact Technical Support for assistance or intervention. |
|
NVRAM has failed to backup or restore data during the last boot. |
Contact Technical Support for assistance or intervention. |
|
NVRAM is not yet ready to accept write commands. |
Wait for NVRAM to become ready. |
|
NVRAM hardware has failed. |
Contact Technical Support for assistance or intervention. |
|
Filesystem server is crashing repeatedly. Entering Maintenance mode to run filesystem scan utility. |
|
|
System is not initialized. |
Use "system --init" to initialize the system. |
|
NVRAM does not match the data volume. |
If this is a newly replaced NVRAM, use "maintenance --hardware --reinit_nvram" to initialize. |
|
Software upgrade is in progress. |
Informational message. No user intervention is required. |
|
Upgrade did not complete. |
Retry upgrade after rebooting the appliance. |
|
Upgrade completed successfully. Reboot required. |
Reboot the system. |
|
Upgrade completed successfully. System coming online. |
Informational message. No user intervention is required. |
|
Unable to set Filesystem Scan Markers. |
Reboot the system. If problem persist contact Technical Support. |
|
Not enough space to run Filesystem Scan. |
Please clean-up older diagnostics file(s) and reboot the system. On reboot, execute "maintenance --filesystem --start_scan" to start filesystem scan. If the file system scan fails with not enough space, please contact Technical Support. |
|
Filesystem server is crashing repeatedly in Maintenance Mode. |
Please contact Technical Support. |
|
One or more software package is incompatible, please upgrade the appliance to rectify the issue. |
Please upgrade the system appliance to rectify the issue. Upgrade the DR Series system appliance (in the Software Upgrade page, click Start Upgrade). |
|
NVRAM Controller detected a memory failure |
|
|
NVRAM Health check in progress, please wait for it to complete before using the system. |
Informational message. No user intervention is required. |
|
NVRAM Health check is required, system will perform a quick health check |
Informational message. No user intervention is required. |
|
Failed to start NVRAM Health check, please reboot the appliance to recover from this state |
Reboot the system. |
|
Appliance encountered O/S issues. Please reboot the appliance to recover from this condition. |
Reboot the system. |
|
High system memory usage detected, system performance will be sluggish. |
|
|
System memory usage has returned to an optimal level. |
Informational message. No user intervention is required. |
|
A high level of system process usage has been detected, if it persists, please collect system diagnostics. |
Informational message. No user intervention is required. |
|
System process usage has returned to an optimal level. |
Informational message. No user intervention is required. |
|
A high-temperature reading has been detected on the NVRAM PCI controller. System will operate only in a read-only mode. Please check system airflow. |
Informational message. No user intervention is required. |
|
A high-temperature reading has been detected on the NVRAM PCI controller. System will not become operational until the temperature reduces to an ambient value of 55 degrees Celsius (131 degrees Fahrenheit). |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention. |
|
The next NVRAM capacitor health check is scheduled for <variable>. |
Informational message. No user intervention is required. |
|
Windows Active Directory client is unable to contact the Active Directory domain server. |
Informational message. No user intervention is required. |
|
Active Directory domain server connectivity is restored. |
Informational message. No user intervention is required. |
|
Storage enclosure <variable> is authorized. |
Informational message. No user intervention is required. |
|
Storage enclosure <variable> is de-commissioned. |
Informational message. No user intervention is required. |
|
The system IP address has changed from <variable> to <variable>. |
Informational message. No user intervention is required. |
|
Refresh NHM Inventory |
|
|
One or more storage enclosures have gone offline, please power-off the appliance, fix the connectivity issues and power-on the appliance. |
Please power off the appliance, check whether all required storage enclosure(s) are powered-up, fix connectivity issues, and power on the appliance. |
|
Data Volume has become in-accessible. |
Contact Technical Support. |
|
Data Volume has become read-only. |
Contact Technical Support. |
|
Namespace Volume has become in-accessible, please call Technical support. |
Contact Technical Support. |
|
Namespace Volume has become read-only. |
Contact Technical Support. |
|
Core Volume has become in-accessible. |
Contact Technical Support. |
|
Invalid storage appliance memory configuration. |
|
|
Storage Enclosure with Service Tag <variable> added successfully. |
Informational message. No user intervention is required. |
|
One of the storage enclosure has become offline. |
Power-off the appliance, fix the connectivity issues and power-on the appliance. |
|
Data Volume has become read-only. |
Contact Technical Support. |
|
Upgrade did not complete. Retry upgrade. |
Retry to upgrade. If the problem persists, contact Technical Support. |
|
Filesystem scan completed, restarting filesystem for normal operation. |
Informational message. No user intervention is required. |
|
Storage enclosure license(s) are missing. |
If Restore Manager (RM) recovery was performed recently, please re-apply the license(s) and reboot. |
|
BIOS System ID is incorrect for correct operation of this storage appliance. The storage appliance requires service. |
|
|
System clock has drifted more than 24 hours, from the last filesystem start. |
Please check your clock settings and reboot. |
|
This DR4x00 Virtual Machine usage time limit has expired. |
Please contact your DR4x00 Sales representative to get the Hardware Version. |
|
This DR4x00 Virtual Machine is for evaluation purpose only. Evaluation period ends on <variable>. |
Informational message. No user intervention is required. |
|
This DR4x00 Virtual Machine requires an evaluation license. |
Please contact your DR4x00 Sales representative. |
|
This DR4x00 Virtual Machine is designed to work only with 4 CPU(s) and 8GB of memory. |
Informational message. No user intervention is required. |
|
This DR2000v requires a license to operate. |
Please install an evaluation license or register the DR2000v with a DR4000/DR4100/DR6000 series hardware appliance. |
|
This DR2000v is unable to contact the license server to validate the license usage. |
Please rectify the connectivity issues and reboot the system. |
|
This DR2000v Virtual appliance usage time limit has expired. |
Contact your DR Series Sales representative to get a permanent license. |
|
This DR2000v Virtual appliance usage time limit will expire on <variable>. |
Informational message. No user intervention is required. |
|
System Asset Tag information has non-printable characters. |
Please use the iDRAC interface console and fix the issue. |
|
This DR2000v has been deleted at license server. |
Register using the CLI command "virtual_machine --register" again. |
|
This DR4300e requires a license to operate, please install storage usage license. |
DR4300e comes with a 30-day trial license. Then you need to install a capacity license. Contact Technical Support for assistance. |
|
Internal storage license(s) are missing, if Restore Manager (RM) recovery was performed recently, please re-apply the license(s). |
Re-add the old capacity license(s) after recovering the system. Contact Technical Support for assistance. |
|
DR4300e data storage expanded successfully. |
Informational message. Storage on DR4300e has now been expanded to 9TB after the addition of a second 4.5TB license. No user intervention is required. |
|
Filesystem scan requested. Switching to Maintenance Mode. Filesystem has read-only access. |
Informational message. No user intervention is required. |
|
NVRAM not detected. |
Ensure card is seated properly. |
|
NVRAM capacitor is disconnected. |
Contact Technical Support. |
|
NVRAM capacitor has degraded. |
Contact Technical Support. |
|
NVRAM SSD is disconnected. |
Contact Technical Support. |
|
NVRAM has failed to backup/restore data during last boot. |
Contact Technical Support. |
|
NVRAM hardware failure. |
Contact Technical Support. |
|
Data volume is not present. Check that all drives are inserted and powered up. |
Contact Technical Support for assistance or intervention. |
|
Filesystem server failed to start after multiple attempts. |
Contact Technical Support for assistance or intervention. |
|
Filesystem server crashed multiple times. System is now entering Maintenance mode. |
Contact Technical Support for assistance or intervention. |
|
Insufficient disk space. Filesystem switched to read-only mode. |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention. |
|
Unable to detect filesystem type on the Data Volume. |
Contact Technical Support for assistance or intervention. |
|
Unable to detect filesystem type on the Namespace Volume. |
Contact Technical Support for assistance or intervention. |
|
Filesystem scan discovered inconsistencies. |
Please check report and take the recommended action. Contact Technical Support for assistance or intervention. |
|
NVRAM does not match data volume. |
If this is a newly replaced NVRAM device, use the CLI maintenance --hardware --reinit_nvram command. For more information, see the DR Series System Command Line Reference Guide. |
|
Storage usage is approaching the DR Series system capacity. |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention. |
|
Replication re-sync cannot proceed because the Namespace depth has reached its maximum. |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention. |
|
Filesystem has reached the maximum allowable file(s) and directories limit. New file and directory creation will be denied until sufficient space exists. |
Please clean up the filesystem. If issue persists, contact Technical Support for assistance or intervention. |
|
Filesystem is reaching the maximum allowable file(s) and directories limit. New file and directory creation will be denied after the limit has been reached. |
Please clean up the filesystem. If issue persists, contact Technical Support for assistance or intervention. |
|
Replication has encountered an unexpected error. |
Contact Technical Support for assistance or intervention. |
|
DataCheck has detected a potential corruption. |
Run data consistency checks at the first available opportunity. If this issue persists, contact Technical Support for assistance or intervention. |
|
Datacheck detected potential namespace inconsistency. |
Run filesystem scan as soon as possible. ("maintenance --filesystem --start_scan") |
|
Datacheck detected inconsistency in lsu image. |
Run filesystem scan as soon as possible. ("maintenance --filesystem --start_scan verify_rda_metadata") |
|
Datacheck detected potential corrupt lsu info. |
Run filesystem scan as soon as possible. ("maintenance --filesystem --start_scan verify_rda_metadata") |
|
Temperature warning detected on NVRAM PCI controller. |
Please check the data center air conditioning, rack ventilation, and internal cooling fans for any issues. Ensure that there is proper air flow through the system appliance, and clean the system cooling vents as needed. If issue persists, contact Technical Support for assistance or intervention. |
|
Filesystem Name Space partition has reached its maximum allowable limit. |
Please delete any old, unused file(s) or disable replication(s). If issue persists, contact Technical Support for assistance or intervention. |
|
Filesystem Name Space partition is reaching its maximum allowable limit. |
New replication resynch(s) will be stopped. If issue persists, contact Technical Support for assistance or intervention. |
|
One or more software package is incompatible. |
Please upgrade the appliance to rectify the issue. |
|
Filesystem volume has become in-active. |
Please contact Technical Support for assistance or intervention. |
|
Filesystem server response time exceeded max threshold. |
Informational message. No user intervention is required. |
|
The memory capacity of the storage appliance is below the minimum required for correct operation. The storage appliance requires service. |
|
|
An OST container quota is exceeded. |
Check the event for container details. |
|
One of the storage enclosure has become offline. |
Please power-down the appliance and rectify the issue. |
|
One or more storage enclosure(s) are missing/offline. |
Please check whether the storage enclosure(s) are powered-up and connected to the appliance. |
|
Storage enclosure license(s) are missing. |
If Restore Manager (RM) recovery was performed recently, please re-apply the license(s) and reboot. |
|
System has a huge backlog of book keeping work. Filesystem cleaner will be enabled outside of schedule setting and performance impact will be observed. |
Informational message. No user intervention is required. |
|
System clock has drifted more than 24 hours, from the last filesystem start. |
Please check your clock settings and reboot. |
|
Replication is disconnected on one or more containers. |
Please check event log or replication stats for details. |
|
One or more replication target systems are running low in space. |
Please check event log or replication stats for details. |
|
Filesystem scan completed with no inconsistencies. Switching back to operational mode. |
Informational message. No user intervention is required. |
|
Replication detected potential inconsistency. |
Run filesystem scan with data verification check as soon as possible. ("maintenance --filesystem --start_scan verify_data") |
|
Seeding device became full. |
Add new seeding device to continue. |
|
Seeding cannot contact the target device. |
Check to make sure that the target device is available and write-enabled. Then remove and re-add the target device. |
|
Seeding process complete. |
Informational message. No user intervention is required. |
|
System has reached space full condition, seeding will be stopped. |
Informational message. No user intervention is required. |
|
Seeding failed to create Zero log entries. |
Switch to maintenance mode to correct the issue. |
|
Found corrupted stream on seeding device. This error will be rectified during replication re-sync done on this seed data. |
Informational message. No user intervention is required. |
|
Seeding device metadata info file missing, unable to import. |
|
|
Seeding device mount not accessible. |
|
|
Seeding export paused as the device contains data from another seeding job. |
Cleanup the device and re-add to continue seeding. |
|
Seeding encountered error. |
|
|
Unable to decrypt the Seeding data. |
Please check that the "password" and "encryption type" matches the Seeding export job. |
|
System diagnostics partition is running low on space. |
Please copy out the old diagnostics bundles and delete for future auto diagnostics collection. |
|
Appliance available storage level is below the set threshold. |
Please schedule filesystem cleaner or expire older backups. |
|
Primary Keystore corruption detected. |
Run filesystem scan with data verification check. |
|
System Event = Type 2 |
|
Data check configuration successful. |
Informational message. No user intervention is required. |
|
Successfully <variable> system marker. |
Informational message. No user intervention is required. |
|
<variable> OPDUP encryption updated to <variable> |
Informational message. No user intervention is required. |
|
System storage usage alert has been set at <level>. |
Informational message. No user intervention is required. |
|
Successfully <variable> container <variable> with the following marker(s) "<markers>". |
Informational message. No user intervention is required. |
|
Container <name> created successfully. |
Informational message. No user intervention is required. |
|
Container <name> marked for deletion. |
For more information, see Deleting Containers. Use the DR Series system CLI maintenance --filesystem --reclaim_space command to recover this storage space. |
|
Container <name> has been deleted. |
Informational message. No user intervention is required. |
|
Successfully renamed container <name> as <name>. |
Informational message. No user intervention is required. |
|
Container <name> is configured to access over <variable> by the following clients: <clients> ('*' means access for everyone). |
Informational message. No user intervention is required. |
|
Container <name> is updated to access over <variable> by the following clients: <clients> ('*' means access for everyone). |
Informational message. No user intervention is required. |
|
Disabled access for Container <name> over <variable> for the following clients: <clients> ('*' means disabled access for everyone). |
Informational message. No user intervention is required. |
|
Successfully added connection entry for container <name>: type <variable> clients <variable>. |
Informational message. No user intervention is required. |
|
Successfully updated connection entry for container <name>: type <variable> clients <variable>. |
Informational message. No user intervention is required. |
|
Successfully deleted connection entry for container <name>: type <variable> clients <variable>. |
Informational message. No user intervention is required. |
|
Replication entry created successfully for container <name>: role <variable> peer <variable> peer container <variable>. |
Informational message. No user intervention is required. |
|
Replication configuration updated successfully for container <name>: role <variable> peer <variable>. |
Informational message. No user intervention is required. |
|
Replication marked for deletion for Container <name>: peer <variable> peer container <name>. |
Informational message. No user intervention is required. |
|
Replication deleted for container <name>. |
Informational message. No user intervention is required. |
|
Successfully initiated replication re-sync on Container <name>. |
Informational message. No user intervention is required. |
|
Replication <variable> defaults successfully updated: role <variable> peer <variable>. |
Informational message. No user intervention is required. |
|
Successfully updated replication bandwidth limit for <variable> to <variable>. |
Informational message. No user intervention is required. |
|
Successfully removed replication bandwidth limit for <variable>. |
Informational message. No user intervention is required. |
|
Successfully set <variable> replication bandwidth limit. |
Informational message. No user intervention is required. |
|
Replication enabled for container <name> with role <role>. |
Informational message. No user intervention is required. |
|
Replication disabled for container <name> with role <role>. |
Informational message. No user intervention is required. |
|
Snapshot <variable> → <variable> created successfully. |
Informational message. No user intervention is required. |
|
Snapshot <variable> → <variable> successfully updated. |
Informational message. No user intervention is required. |
|
Snapshot <variable> → <variable> successfully deleted. |
Informational message. No user intervention is required. |
|
Client <client> authorized to access NDMP Tape Server. |
Informational message. No user intervention is required. |
|
Successfully updated NDMP to use port <number>. |
Informational message. No user intervention is required. |
|
De-authorized NDMP client - <client>. |
Informational message. No user intervention is required. |
|
NDMP password successfully updated. |
Informational message. No user intervention is required. |
|
OST password updated successfully. |
Informational message. No user intervention is required. |
|
OST state updated successfully. |
Informational message. No user intervention is required. |
|
OST client <variable> with mode <variable> added successfully |
Informational message. No user intervention is required. |
|
OST client <variable> deleted successfully. |
Informational message. No user intervention is required. |
|
OST client <variable> with mode <variable> updated successfully. |
Informational message. No user intervention is required. |
|
OST client <variable> deleted successfully. |
Informational message. No user intervention is required. |
|
OST client <variable> with mode <variable> updated successfully. |
Informational message. No user intervention is required. |
|
Successfully updated <variable> schedule. |
Informational message. No user intervention is required. |
|
System compression level set to <variable>. |
Informational message. No user intervention is required. |
|
System configuration backup failed. |
|
|
Rapid Data Access (RDA) password updated successfully. |
Informational message. No user intervention is required. |
|
Rapid Data Access (RDA) state updated successfully. |
Informational message. No user intervention is required. |
|
Rapid Data Access (RDA) client <variable> with mode <variable> added successfully. |
Informational message. No user intervention is required. |
|
Rapid Data Access (RDA) client <variable> deleted successfully. |
Informational message. No user intervention is required. |
|
Rapid Data Access (RDA) client <variable> with mode <variable> updated successfully. |
Informational message. No user intervention is required. |
|
DR2000v with UUID <variable> IP Address <variable> Hostname <variable> registered successfully. |
Informational message. No user intervention is required. |
|
DR2000v with UUID <variable> IP Address <variable> Hostname <variable> unregistered successfully. |
Informational message. No user intervention is required. |
|
System Event = Type 3 |
|
System is entering Maintenance mode. |
Informational message. No user intervention is required. Contact Technical Support for assistance or intervention. |
|
System entering Support Mode. |
Contact Technical Support for assistance or intervention. |
|
Internal failure—OFS client initialization failure. |
Contact Technical Support for assistance or intervention. |
|
Internal failure—mtab initialization failure for container <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal failure—cannot initialize node mtab. |
Contact Technical Support for assistance or intervention. |
|
Internal failure retrieving configuration for container ID <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal failure deleting container ID <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal failure stopping container ID <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal failure adding connection <variable> for container ID <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal failure deleting connection <variable> for container ID <variable>. |
Contact Technical Support for assistance or intervention. |
|
Name space volume nearing low space condition. To prevent faster exhaustion of space, snapshot required for replication seeding for container <variable> will be paused until Name space volume recovers from low space conditions. |
|
|
Replication started as per schedule, will be active until <variable>. |
Informational message. No user intervention is required. |
|
Replication stopped as per schedule, will restart at <variable>. |
Informational message. No user intervention is required. |
|
Container replay failed for container <variable>. |
Informational message. No user intervention is required. Contact Technical Support for assistance or intervention. |
|
Internal failure—Name Space subsystem initialization failed. |
Informational message. No user intervention is required. Contact Technical Support for assistance or intervention. |
|
Inconsistencies were found in the Name Space. |
Please schedule a filesystem consistency check using the DR Series system CLI maintenance --filesystem --start_scan command. |
|
System entering Maintenance mode—Name Space log replay failed. |
Contact Technical Support for assistance or intervention. |
|
System entering Maintenance Mode—Name Space transaction failure. |
Contact Technical Support for assistance or intervention. |
|
Internal failure—failed to commit Name Space transaction. |
Contact Technical Support for assistance or intervention. |
|
Filesystem has reached the maximum supported number of Name Space entries. |
Please clean up the filesystem to allow new file and directory create operations. If this condition persists, contact Technical Support for assistance or intervention. |
|
Filesystem has recovered from a lack of available Name Space entries. |
Filesystem create operations will now be allowed. Contact Technical Support for assistance or intervention. |
|
Internal attributes of some files were found to be corrupt. The DR Series system will not allow the setting or removing of Attributes or ACLs on files that have corrupt attributes. |
To find all files with corrupt attributes and to clear the state, please perform a maintenance scan using the DR Series system CLI maintenance --filesystem --start_scan command. Contact Technical Support for assistance or intervention. |
|
System entering maintenance mode - Name Space Log Rotation failed |
|
|
File/Directory Statistics table out of sync. Switching to maintenance mode. |
|
|
Root inode of container, id <variable>, was found to be inconsistent. Fixed the attribute, ACL on root inode needs to be manually verified and fixed. |
|
|
Replication re-sync started for container <variable>. |
Informational message. No user intervention is required. |
|
Replication internal re-sync started for container <variable>. |
Informational message. No user intervention is required. |
|
Replication re-sync completed for container <variable>. |
Informational message. No user intervention is required. |
|
Replication internal re-sync completed for container <variable>. |
Informational message. No user intervention is required. |
|
Internal failure creating replication snapshot for container <variable>. |
If condition persists, reduce number of inodes, or contact Technical Support for assistance or intervention. |
|
Internal failure deleting replication snapshot for container <variable>. |
If condition persists, reduce number of inodes, or contact Technical Support for assistance or intervention. |
|
Replication client connected for container <variable>. |
Informational message. No user intervention is required. |
|
Replication client disconnected for container <variable>. |
Verify that the ports for replication (9904, 9911, 9915, and 9916) and OST (10011 and 11000) operations have been enabled. If issue persists, contact Technical Support for assistance or intervention. |
|
Replication server connected for container <variable>. |
Verify that the ports for replication (9904, 9911, 9915, and 9916) and OST (10011 and 11000) operations have been enabled. If issue persists, contact Technical Support for assistance or intervention. |
|
Replication server disconnected for container <variable>. |
Informational message. No user intervention is required. |
|
Replication Name Space oplog full for container <variable>. |
Verify that the ports for replication (9904, 9911, 9915, and 9916) and OST (10011 and 11000) operations have been enabled. If issue persists, contact Technical Support for assistance or intervention. |
|
Replication switching to re-sync due to corrupt replication Name Space oplog for container <variable>. |
|
|
Replication data operations log (oplog) full for container <variable>. |
The DR Series system should self-correct itself. If condition persists, reduce number of inodes, or contact Technical Support for assistance or intervention. |
|
Replication switching to re-sync due to corrupt replication data oplog for container <variable>. |
|
|
Replication transmit log (txlog) full for container <variable>. |
The DR Series system should self-correct itself. If condition persists, reduce number of inodes, or contact Technical Support for assistance or intervention. |
|
System entering Maintenance mode due to corrupt replication txlog for container <variable>. |
Collect a diagnostics log file, and open a Support record with Technical Support for assistance. |
|
System entering Maintenance mode due to replication txlog commit error <variable> for container <variable>. |
Collect a diagnostics log file, and open a Support record with Technical Support for assistance. |
|
Unable to make progress on filesystem replication for container <variable>. |
Collect a diagnostics log file, and open a Support record with Technical Support for assistance. |
|
Replication syncmgr exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication syncmgr event for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Name Space replicator exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication data replicator exited for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication protocol version mismatch for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication protocol version mismatch detected for container <variable>. Replication will continue with downgraded source protocol version. |
|
|
Replication delete cleanup failed for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication target system <variable> is running low on space. Replication cannot proceed further on container <variable>. |
Informational message. Contact Technical Support for assistance or intervention. |
|
Replication misconfiguration detected for container <variable>. Replication relationship might have been deleted forcibly on target system <variable>. |
Informational message. Contact Technical Support for assistance or intervention. |
|
Replication failed for container <variable> error <variable>. |
Collect a diagnostics log file bundle, and open a Support record with Technical Support for assistance. |
|
Replication server failed to commit blockmap for container <variable>. System is entering Maintenance mode. |
The DR Series system should self-correct itself. If condition persists, reduce number of inodes, or contact Technical Support for assistance or intervention. |
|
Container <variable> replication is paused, cleaner on replica is reclaiming space. |
Run the Cleaner on the replica container. If condition persists, contact Technical Support for intervention or assistance. |
|
Found mismatch in system software version with peer <variable>. Replication on source container <variable> would be stalled. |
|
|
Replication stalled on source container <variable> due to a mismatch in system software version or network issue with peer <variable>. |
|
|
Found mismatch in system software version with peer <variable>. Backup or replication on some or all target containers would be stalled. |
|
|
Received a garbled message from peer <variable>. Connection would be dropped. |
|
|
Container <variable> replication encountered encryption setup error. |
|
|
NFS client successfully mounted <variable>. |
Informational message. No user intervention is required. |
|
Maximum NFS connection limit <variable> reached, active NFS connections <variable>. |
You have reached the threshold limit. Reduce the number of connections. |
|
NFS client <variable> successfully unmounted <variable>. |
Informational message. No user intervention is required. |
|
NFS client <variable> successfully unmounted all containers. |
Informational message. No user intervention is required. |
|
CIFS client successfully connected to container <variable>. |
Informational message. No user intervention is required. |
|
CIFS client <variable> session successfully disconnected from container <variable> . |
Informational message. No user intervention is required. |
|
Maximum <variable> connection limit <variable> reached. |
You have reached the threshold limit for the specified protocol. Reduce the number of connections. |
|
CIFS server failed to start <variable>. |
Reboot the DR Series system. If issue persists, contact Technical Support for assistance or intervention. |
|
CIFS client connected <variable> times to container <variable>. |
Reboot the DR Series system. If issue persists, contact Technical Support for assistance or intervention. |
|
CIFS server started successfully. |
Informational message. No user intervention is required. |
|
NFS server started successfully. |
Informational message. No user intervention is required. |
|
Storage usage approaching system capacity. |
Informational message. No user intervention is required. |
|
Online data verification (DataCheck) started. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) suspended. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) stopped. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) resumed. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) detected <variable> corruption. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) detected <variable> corruptions. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Online data verification (DataCheck) failed to start. |
Informational message. If issue persists, contact Technical Support for assistance or intervention. |
|
Seeding device became full. |
Add new seeding device to continue. |
|
Seeding cannot contact the target device. |
Check to make sure that the target device is available and write-enabled. Then remove and re-add the target device. |
|
Seeding process complete. |
Informational message. No user intervention is required. |
|
System has reached space full condition, seeding will be stopped. |
|
|
Seeding failed to create Zero log entries. |
Switch to maintenance mode to correct the issue. |
|
Found corrupted stream on seeding device. This error will be rectified during replication re-sync done on this seed data. |
Informational message. No user intervention is required. |
|
Seeding device metadata info file missing, unable to import. |
|
|
Seeding device mount not accessible. |
|
|
Seeding export paused as the device contains data from another seeding job. |
Clean up the device and re-add to continue seeding. |
|
Seeding encountered error. |
|
|
Unable to decrypt the Seeding data. |
Please check that the "password" and "encryption type" matches the Seeding export job. |
|
Seeding device deleted. |
Informational message. No user intervention is required. |
|
Seeding device added. |
Informational message. No user intervention is required. |
|
Seeding started. |
Informational message. No user intervention is required. |
|
Seeding stopped. |
Informational message. No user intervention is required. |
|
Container <variable> added to seeding. |
Informational message. No user intervention is required. |
|
Container <variable> is removed while seeding is in progress. |
Informational message. No user intervention is required. |
|
Container <variable> removed from seeding. |
Informational message. No user intervention is required. |
|
Seeding job created. |
Informational message. No user intervention is required. |
|
Seeding job deleted. |
Informational message. No user intervention is required. |
|
Seed space reclamation triggered. |
Informational message. No user intervention is required. |
|
Unable to use old seed dict. Creating a new dict. |
Informational message. No user intervention is required. |
|
Unable to read bmap scid. Retry seeding after running filesystem scan. |
Retry seeding after running filesystem scan. |
|
Unable to read DS scid. Retry seeding after running filesystem scan. |
Retry seeding after running filesystem scan. |
|
Seeding device mount not accessible. Check the CIFS mount and re-add the device to continue. |
Check the CIFS mount and re-add the device to continue. |
|
System Event = Type 4 |
|
Internal Error. Unable to load deduplication dictionary <variable>. |
Use the DR Series system CLI maintenance --configuration --reinit_dictionary command. If this issue persists, contact Technical Support for assistance or intervention. |
|
Internal Error. Unable to locate deduplication dictionary <variable>. |
Use the DR Series system CLI maintenance --configuration --reinit_dictionary command. If issue persists, contact Technical Support for assistance or intervention. |
|
Filesystem cleaner run <variable> started. |
Informational message. No user intervention is required. |
|
Filesystem cleaner run <variable> completed in <variable> milliseconds (ms). |
Informational message. No user intervention is required. |
|
Filesystem cleaner process encountered input/output (I/O) errors. |
Maintenance-based issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. Contact Technical Support as needed. |
|
Failure to sync NVRAM <variable>. |
NVRAM hardware issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. |
|
Failure reading from NVRAM <variable>. |
NVRAM hardware issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. |
|
Failure writing to NVRAM <variable>. |
NVRAM hardware issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. |
|
Failure to write sync NVRAM <variable>. |
NVRAM hardware issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. |
|
Internal Error. Datastore <variable> length mismatch <variable>. |
Maintenance-based issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. Contact Technical Support as needed. |
|
Data volume capacity threshold reached. |
Informational message. No user intervention is required. |
|
Out of space. Rollback of updates on object <variable> failed. Restarting file server. |
Maintenance-based issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. Contact Technical Support as needed. |
|
Failure reading from data volume. |
Maintenance-based issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. Contact Technical Support as needed. |
|
Failure writing to data volume. |
Maintenance-based issue with the DR Series system. Check status using Maintenance mode or DR Series system CLI commands. Contact Technical Support as needed. |
|
Checksum verification on metadata failed. |
Contact Technical Support for assistance or repair the filesystem. For repairs, see About The DR Series Maintenance Mode. |
|
Internal Error. Optimization engine log replay failed. |
Contact Technical Support for assistance or repair the filesystem. For repairs, see About The DR Series Maintenance Mode. |
|
Decompression of datastore failed <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal Error. Failed to clean active datastore <variable>. |
Contact Technical Support for assistance or intervention. |
|
Internal Error. Negative reference on datastore <variable>. Record type: <variable>. Count: <variable>. |
Contact Technical Support for assistance or repair the filesystem. For repairs, see the topic, “About the DR Series Maintenance Mode.” |
|
Internal Error. Data store <variable> contains negative stream reference count. Record type: <variable>. Count: <variable>. |
Informational message. No user intervention is required. |
|
Internal Error. Data store <variable> total reference count reached threshold. Record type: <variable>. Count: <variable>. |
Informational message. No user intervention is required. |
|
Data store[%s] stream(s) marked bad. |
A chunk of data on the system failed consistency check. An attempt will be made to correct this chunk of data. |
|
Internal Error. Entering Maintenance mode due to failure in processing logs. |
Contact Technical Support for assistance or intervention. |
|
Internal Error. Failed to acquire optimizer pipeline. Error: <variable>. |
Contact Technical Support for intervention or assistance. |
|
Internal Error. Failed to create optimizer event. Type: <variable>, Error: <variable>. |
Contact Technical Support for intervention or assistance. |
|
Internal Error. Task execution in fiber <variable> timed out after <variable> milliseconds (ms). Restarting file server. |
Filesystem restarted. Collect diagnostics log file bundle, and upload diagnostics log file bundle to Technical Support. |
|
Internal Error. Memory allocation failure. |
Collect diagnostics log file bundle. |
|
Background compression started. |
Informational message. No user intervention is required. |
|
Background compression completed. |
Informational message. No user intervention is required. |
|
Optimization initialized on container <variable>. |
Informational message. No user intervention is required. |
|
Optimization terminated on container <variable>. |
Informational message. No user intervention is required. |
|
Cleaner aborted at <variable>. |
The DR Series system should enter Maintenance mode, and Cleaner process will restart. |
|
Internal Error. Moving data from NVRAM to disk failed. System is entering its Maintenance mode. |
Informational message. No user intervention is required. |
|
System entering Maintenance Mode due to corrupt encryption keystore. Triggering key import. |
Run filesystem scan with verify data enabled |
|
Key rotation successful in internal mode |
Informational message. No user intervention is required. |
|
Key limit reached, reusing the last key |
Informational message. No user intervention is required. |
|
Filesystem encryption setting changed |
Informational message. No user intervention is required. |
|
Filesystem Cleaner process started as per schedule (will be active until <variable>). |
Informational message. No user intervention is required. |
|
Filesystem Cleaner process stopped as per schedule (will restart at <variable>). |
Informational message. No user intervention is required. |
|
Filesystem cleaner is paused, to speed up disk maintenance (e.g. Rebuild / Background Init) activities. |
Informational message. No user intervention is required. |
|
System entering Support Mode due to keystore repair failure, both primary and backup keystore are corrupt |
|
|
System entering Support Mode due to keystore empty failure, both primary and backup keystore are empty or removed |
|
|
System Event = Type 5 |
|
System shutdown initiated by administrator. |
Informational message. No user intervention is required. |
|
System reboot initiated by administrator. |
Informational message. No user intervention is required. |
|
Start system upgrade to version <variable>. |
Informational message. No user intervention is required. |
|
System name changed to <variable>. |
Informational message. No user intervention is required. |
|
System date changed to <variable>. |
Informational message. No user intervention is required. |
|
System time zone changed to <variable>. |
Informational message. No user intervention is required. |
|
Password changed for user: administrator. |
Informational message. No user intervention is required. |
|
NTP server <variable> added. |
Informational message. No user intervention is required. |
|
NTP server <variable> deleted. |
Informational message. No user intervention is required. |
|
NTP service enabled. |
Informational message. No user intervention is required. |
|
NTP service disabled. |
Informational message. No user intervention is required. |
|
User data destroyed using CLI command. |
Informational message. No user intervention is required. |
|
User <variable> enabled. |
Informational message. No user intervention is required. |
|
User <variable> disabled. |
Informational message. No user intervention is required. |
|
Networking interfaces restarted. |
Informational message. No user intervention is required. |
|
DHCP enabled: IP address assigned by DHCP. |
Informational message. No user intervention is required. |
|
Static IP address <variable> assigned. |
Informational message. No user intervention is required. |
|
Network interface bonding mode set to <variable>. |
Informational message. No user intervention is required. |
|
Network MTU size set to <variable>. |
Informational message. No user intervention is required. |
|
System name set to <variable>. |
Informational message. No user intervention is required. |
|
Email relay host set to <variable> for email alerts. |
Informational message. No user intervention is required. |
|
Recipients for email alerts set to <variable>. |
Informational message. No user intervention is required. |
|
Recipient <variable> added to receive email alerts. |
Informational message. No user intervention is required. |
|
Recipient <variable> is no longer receiving email alerts. |
Check whether email recipient still exists, or if mailbox is full. |
|
Administrator information set to <variable> for email alerts. |
Informational message. No user intervention is required. |
|
Test email sent. |
Informational message. No user intervention is required. |
|
Joined the Windows Active Directory domain <variable>. |
Informational message. No user intervention is required. |
|
Left the Windows Active Directory domain <variable>. |
Informational message. No user intervention is required. |
|
System diagnostics package <variable> deleted. |
Informational message. No user intervention is required. |
|
All diagnostic packages deleted. |
Informational message. No user intervention is required. |
|
System diagnostic package <variable> is copied off the system. |
Informational message. No user intervention is required. |
|
System statistics reset by administrator. |
Informational message. No user intervention is required. |
|
System diagnostic package <variable> is collected. |
Informational message. No user intervention is required. |
|
System diagnostics space usage exceeded threshold. Auto cleaning oldest package: <variable>. |
Informational message. No user intervention is required. |
|
Internal Error. CIFS server cannot access file service. |
Contact Technical Support for intervention or assistance. Collect diagnostics log file bundle, and upload to Technical Support. |
|
Host <variable> added to SNMP alert recipient list. |
Informational message. No user intervention is required. |
|
Host <variable> deleted from SNMP alert recipient list. |
Informational message. No user intervention is required. |
|
Host <variable> enabled for SNMP alerts. |
Informational message. No user intervention is required. |
|
Host <variable> disabled for SNMP alerts. |
Informational message. No user intervention is required. |
|
User <variable> logged into the system. |
Informational message. No user intervention is required. |
|
CIFS user <variable> added. |
Informational message. No user intervention is required. |
|
CIFS user <variable> deleted. |
Informational message. No user intervention is required. |
|
Password changed for CIFS user <variable>. |
Informational message. No user intervention is required. |
|
System upgrade completed <variable>. |
Informational message. No user intervention is required. |
|
Cleared foreign configuration on disk <variable>. |
Informational message. No user intervention is required. |
|
User <variable> logged into the system. |
Informational message. No user intervention is required. |
|
Disk <variable> configured as hot spare. |
Informational message. No user intervention is required. |
|
Telnet service enabled. |
Informational message. No user intervention is required. |
|
Telnet service disabled. |
Informational message. No user intervention is required. |
|
DNS settings updated with primary <variable>, secondary <variable>, and suffix <variable>. |
Informational message. No user intervention is required. |
|
System initialized successfully. |
Informational message. No user intervention is required. |
|
<variable> added with entitlement id <variable>. |
Informational message. No user intervention is required. |
|
Security privilege(s) changed for <variable>. |
Informational message. No user intervention is required. |
|
User <variable> logged into the administrative web interface. |
Informational message. No user intervention is required. |
|
Network interface(s) <variable> enabled. |
Informational message. No user intervention is required. |
|
Network interface(s) <variable> disabled. |
Informational message. No user intervention is required. |
|
SMBD backup traffic interface(s) <variable> do not have an IP. |
|
|
DR2000v registered successfully. |
Informational message. No user intervention is required. |
|
DR2000v unregistered successfully. |
Informational message. No user intervention is required. |
|
DR2000v data storage expanded by 1 TiB. |
Informational message. No user intervention is required. |
|
Miscellaneous Invalid/Last Event. |
Informational message. No user intervention is required. |
|
System Event = Type 6 |
|
File system check started. |
Informational message. No user intervention is required. |
|
File system check completed successfully. No inconsistencies were found. |
Informational message. No user intervention is required. |
|
File system check found some inconsistencies. |
The DR Series system Maintenance mode repair process should resolve this. If the problem persists, contact Technical Support for assistance or intervention. |
|
File system repair started. |
Informational message. No user intervention is required. |
|
File system repair completed. |
Informational message. No user intervention is required. |
|
File system check stop requested. |
Informational message. No user intervention is required. |
|
One (or more) file(s) were deleted as part of the repair process. |
Informational message. No user intervention is required. To verify, please use the DR Series system CLI maintenance --filesystem --repair_history verbose command. |
|
One or more file(s) were deleted as part of the repair process for container <variable>. Replication will be stopped for this container. |
Informational message. No user intervention is required. |
|
One or more file(s) were deleted as part of the repair process for container <variable>. Re-sync has been initiated for this container. |
Informational message. No user intervention is required. |
|
System Event = Type 7 |
|
RDA server started successfully. |
Informational message. No user intervention is required. |
|
RDA server failed to start. |
Restart the RDA server. If issue persists, contact Technical Support for assistance or intervention. |
|
RDA server stopped successfully. |
Informational message. No user intervention is required. |
|
<Variable> client authentication failed. |
Retry the OST client authentication. If issue persists, contact Technical Support for assistance or intervention. |
|
<Variable> Logical Storage Unit (LSU) quota exceeded <variable>. |
Informational message. Reduce the number of LSUs. If issue persists, contact Technical Support for assistance or intervention. |
|
<Variable> backup failed <variable>. |
Retry the OST backup operation. If issue persists, contact Technical Support for assistance or intervention. |
|
<Variable> Opdup failed <variable>. |
The OST optimized duplication process failed. If issue persists, contact Technical Support for assistance or intervention. |
|
<Variable> Restore failed <variable>. |
The OST restore process failed. If issue persists, contact Technical Support for assistance or intervention. |
|
RDA connections exceeded the maximum limit; count: <variable>, maximum limit: <variable>. |
Informational message. Reduce the number of OST connections. If issue persists, contact Technical Support for assistance or intervention. |
|
Connection from the <variable> client <variable> aborted. |
Informational message. No user intervention is required. |
|
RDA client protocol version is not supported. |
Informational message. No user intervention is required. Check for the supported OST client versions in the DR Series System Interoperability Guide. |
|
System is entering the Maintenance mode: <variable> LSU information file is corrupted. |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention. |
|
System is entering the Maintenance mode: <variable> image information is corrupted. |
Informational message. No user intervention is required. If issue persists, contact Technical Support for assistance or intervention |
|
<variable> client connection was reset. |
Informational message. No user intervention is required. |
|
System is entering the Maintenance mode: RDA meta directory is corrupted. |
Informational message. No user intervention is required. |
|
RDA server initialization failed. |
Informational message. No user intervention is required. |
|
RDA server initialization was successful. |
Informational message. No user intervention is required. |
|
System entering Maintenance Mode - RDA txlog full, LSU <variable>. |
Informational message. No user intervention is required. |
|
System entering Maintenance Mode - RDA txlog operation error <variable>, LSU <variable>. |
Informational message. No user intervention is required. |
|
System entering Maintenance Mode - RDA txlog roll-forward error <variable>, LSU <variable>. |
Informational message. No user intervention is required. |
