Understanding the HCP system log
While the Overview page in the System Management Console gives you a view of the system as a whole, the HCP system log lets you monitor system activity on a more detailed level. The log records system events such as:
•Nodes and services starting
•Changes to the system configuration
•Logical volume failures
•User logins to the HCP System Management Console
Each recorded entry about an event is called a message. The system log contains all the messages written to it since the HCP system was installed.
The System Management Console provides several views of the log:
•The All Events panel on the System Events page displays all the messages in the system log that your roles allow you to see.
•The Security panel on the System Events page displays only messages about attempts to log into the System Management Console with an invalid username. Only users with the security role can see this panel.
•The Logs section on the Resources page displays all the messages in the system log that your roles allow you to see.
•The Major Events section on the Overview page displays only messages about major events (for example, the addition or failure of a node).
•The Events section on the Storage Node page displays only messages about events that relate to a particular node.
•The Service Events section on the Schedule page displays only messages related to HCP services that can be scheduled to run at specific times.
For information about the messages that can appear in the system log and how to respond to them, see HCP system log messages.
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.
Viewing the complete event log
The All Events panel on the System Events page lists all event messages logged since the HCP system was installed. By default, the panel displays 20 messages at a time in reverse chronological order.
![]() |
Roles: To view the All Events panel, you need the monitor, administrator, security, service, or compliance role. However, only users with the security role can see messages about attempts to log into the System Management Console with an invalid username. |
To display the All Events panel:
1.In the top-level menu of the System Management Console, select Monitoring ► System Events.
2.On the left side of the System Events page, click All Events.
For a description of the information provided by each log message, see Understanding log messages. For information about managing the message display, see Managing the message list.
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.
Viewing the system security log
The Security Events panel on the System Events page lists all messages about attempts to log into the System Management Console with an invalid username that have occurred since the HCP system was installed. By default, the panel displays 20 messages at a time in reverse chronological order.
![]() |
Roles: To view the Security Events panel, you need the security role. |
To display the Security Events panel:
1.In the top-level menu of the System Management Console, select Monitoring ► System Events.
2.On the left side of the System Events page, click Security Events.
For a description of the information provided by each log message, see Understanding log messages. For information about managing the message display, see Managing the message list.
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.
Understanding log messages
Each message displayed in the All Events and Security Events panels includes this information about an event:
•The username of the event initiator:
oFor user-initiated events, this is the username currently associated with the user account used by the user who initiated the event. These considerations apply:
–For an HCP user account, if the account has been deleted, the username is followed by the letter D in parentheses.
–For an AD user account, if the account has been deleted or if HCP currently cannot contact AD, the username for the message is blank.
oFor system-initiated events, the username is [internal].
oFor events initiated through SNMP, the username is [snmp].
oFor events initiated by HCP service or support personnel by means other than the System Management Console or SNMP, the username is [service].
•The severity of the event. Possible values are:
oNotice — The event is normal and requires no special action. Events of this severity are informational only. Examples are:
–Node started
–Protection service finished: run complete
–Syslog settings changed
oWarning — The event is out of the ordinary and may require manual intervention. Examples are:
–Storage capacity warning
–Protection service beginning repairs
–Remote authentication server error
oError — The event is serious and most likely requires manual intervention. Examples are:
–Storage capacity critical
–Volume failure
–Network interface down
•The date and time at which the event occurred, shown for the time zone in which the HCP system is located.
•A short description of the event.
To view more details about an event, click anywhere in the row containing the event message. To hide the details, click again in the row.
The details displayed for an event are:
•The user ID of the event initiator
•For user-initiated events, the port through which HCP received the event request
•For user-initiated events, the IP address from which the event request was sent
•The message ID
•The number of the node on which the event occurred
•If the event applies to a specific logical volume, the volume ID
•The full text of the event message
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.
Managing the message list
You can take the following actions in any of the views of the system log:
•To display details for all the listed events, click expand all. To hide all details, click collapse all.
•To view a different number of messages per page, select the number you want in the Items field.
•To page forward or backward through the messages, click the next ( ) or back (
) control, respectively.
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.
HCP system log messages
HCP maintains a log that records messages about events that happen in the system. The table in this appendix lists the messages HCP can write to the system log. The messages are listed in order by message ID.
For each message, the table shows:
•The message ID
•The short form of the message, which identifies the event to which the message applies
•An explanation of the message
•The action, if any, you should take in response to the message
•The message severity
For more information about the system log, see Understanding the HCP system log.
ID |
Event |
Explanation |
Action |
Severity |
1000 |
HCP started |
The HCP system started. |
No action is required. |
Notice |
1001 |
HCP shutting down |
The HCP system is shutting down. |
If any nodes do not power off automatically, wait a few minutes and then power them off manually. |
Notice |
1002 |
Node started |
A node started. |
No action is required. |
Notice |
1003 |
Node shut down |
A node shut down. |
If this event is unexpected and the node does not restart automatically, contact your authorized service provider. Do not try to restart the node manually, as that may cause the loss of information needed to diagnose the problem. |
Notice |
1004 |
Volume started |
A logical volume came online. |
No action is required. |
Notice |
1005 |
Volume shut down |
A logical volume went offline. |
Contact your authorized service provider. |
Notice |
1006 |
Volume failure |
A logical volume failed. |
Contact your authorized service provider. |
Error |
1007 |
Node removed |
A node has been permanently removed from the HCP system. |
No action is required. |
Notice |
1008 |
Time sync problem |
The internal clock on a node is out of sync with the clocks on the nodes in the rest of the HCP system. |
If the problem persists, contact your authorized service provider. |
Error |
1009 |
Node added |
A new node has been added to the HCP system. |
No action is required. |
Notice |
1010 |
Previously removed node re-added |
A node that was removed from the system has been powered on again. |
Remove the node again. |
Error |
1012 |
Metadata DPL is 1 |
The system was configured with metadata DPL 1. |
No action is required. |
Warning |
1013 |
Failover |
A node in a cross-mapped pair failed. The other node has taken over management of the logical volumes previously managed by the failed node. |
If the failed node does not restart automatically, contact your authorized service provider. Do not try to restart the node manually, as that may cause the loss of information needed to diagnose the problem. |
Error |
1014 |
HCP rebooting |
The HCP system is restarting. |
No action is required. |
Notice |
1015 |
Failover |
A node in a cross-mapped pair failed. The other node will take over management of the logical volumes previously managed by the failed node. |
If the failed node does not restart automatically, contact your authorized service provider. Do not try to restart the node manually, as that may cause the loss of information needed to diagnose the problem. |
Error |
1016 |
Volume recovered |
A logical volume recovered. |
No action is required. |
Notice |
1017 |
Node down for an extended amount of time |
A node has been unavailable for an extended amount of time. |
Contact your authorized service provider. |
Error |
1018 |
HCP is read-only |
The HCP system has become read-only due to metadata unavailability. Configuration changes and changes to namespace content are not allowed. Services have been suspended. |
Contact your authorized service provider. |
Error |
1019 |
HCP is no longer read-only |
The previously unavailable metadata has become available, so the HCP system is no longer read-only due to metadata unavailability. |
No action is required. |
Notice |
1020 |
Region-count setting is invalid |
The region count was changed to a value that is either too large, too small, or not a number. The actual number of regions has not changed. |
Contact your authorized service provider. |
Error |
1021 |
Region count is changing |
The region count was set to a new value. |
No action is required. |
Notice |
1022 |
Region count has changed |
The region count has finished changing to a new value. |
No action is required. |
Notice |
1023 |
Region-count change has been canceled |
The region-count change was canceled. |
No action is required. |
Notice |
1024 |
Support for DPL 1 changed |
Support for DPL 1 was either enabled or disabled. |
No action is required. |
Warning |
1025 |
External storage volume added |
A user added an external storage volume. |
No action is required. |
Notice |
1026 |
External storage volume updated |
A user updated an external storage volume. |
No action is required. |
Notice |
1027 |
External storage volume deleted |
A user deleted an external storage volume. |
No action is required. |
Notice |
1028 |
External storage volume missing necessary permissions |
The share for a new or updated external storage volume was exported without permissions that HCP needs in order to mount the volume. |
Ensure that the share is exported with the necessary permissions. |
Warning |
1029 |
Cannot mount external storage volume |
HCP was unable to mount a new or updated external storage volume. |
Ensure that the share is exported with the correct configuration on the external device. For more information about this event, see the mount command output displayed with the log message. |
Warning |
1030 |
Cannot mount external storage volume |
HCP was unable to mount a new or updated external storage volume. |
Ensure that the share is exported with the correct configuration on the external device. |
Warning |
1031 |
External volume started |
An external storage volume became available. |
No action is required. |
Notice |
1032 |
External volume unavailable |
An external storage volume is unavailable. |
Ensure that the share is exported with the correct configuration on the external device and that the HCP node managing the volume is available. |
Notice |
1033 |
External volume failure |
HCP was unable to connect to an external storage volume. |
Ensure that the share is exported with the correct configuration on the external device and that all HCP nodes are allowed to mount the share. |
Error |
1034 | External volume remounted | a user remounted an external volume. | No action is required. | Notice |
1035 | External storage volume missing necessary file naming support | The share for a new or updated external storage volume was exported without file naming support that HCP needs in order to mount the volume. | Ensure that the share is exported with the necessary file naming support. | Warning |
1036 | Node rebooting | A node is restarting. | No action is required. | Notice |
1050 |
Storage pool created |
A user created a storage pool. |
No action is required. |
Notice |
1051 |
Storage pool updated |
A user updated a storage pool. |
No action is required. |
Notice |
1052 |
Storage pool deleted |
A user deleted a storage pool. |
No action is required. |
Notice |
1053 |
Storage component created |
A user created a storage component. |
No action is required. |
Notice |
1054 |
Storage component updated |
A user updated a storage component. |
No action is required. |
Notice |
1055 |
Storage component deleted |
A user deleted a storage component. |
No action is required. |
Notice |
1056 |
Storage component abandoned |
A user abandoned a storage component. |
No action is required. |
Notice |
1057 |
SSL certificate downloaded |
A user downloaded an SSL server certificate for storage tiering. |
No action is required. |
Notice |
1058 |
New SSL certificate added |
A user added a new storage tiering client certificate. |
No action is required. |
Notice |
1059 |
SSL certificate deleted |
A user deleted a storage tiering client certificate. |
No action is required. |
Notice |
1060 |
New storage license added |
A user added a new storage license. |
No action required. |
Notice |
1061 |
Storage license expired |
A storage license expired. |
Upload a new storage license. |
Warning |
1062 |
Storage license exceeded |
Storage usage exceed licensed capacity. |
Delete or relocate objects within the repository or add more licensed capacity. |
Warning |
1063 |
OpenStack SSL certificate downloaded |
An SSL server certificate for OpenStack has been downloaded. |
No action is required. |
Notice |
1064 |
New OpenStack SSL certificate added |
A user has created OpenStack SSL certificate. |
No action is required |
Notice |
1065 |
OpenStack SSL certificate deleted |
An existing OpenStack SSL certificate has been deleted. |
No action is required |
Notice |
1066 |
Storage license invalid |
HCP serial number does not match storage license. |
Upload a new storage license. |
Warning |
1067 | Storage component status changed | Storage component status was changed. | No action is required. | Notice |
1068 | Storage component updated | A user updated a storage component. | No action is required. | Notice |
1100 |
Storage capacity warning |
The amount of free storage on the HCP storage nodes is low. |
Consider adding storage capacity to the HCP system before the amount of free storage becomes critically low. |
Warning |
1101 |
Storage capacity critical |
The amount of free storage on the HCP storage nodes may be insufficient to support the addition of new objects. |
Increase the amount of free storage by adding more storage capacity or deleting objects from the repository. |
Error |
1104 |
Internal SLAB process down |
The internal SLAB process is not running. The node will reboot automatically in order to restart the process. |
No action is required. If this problem persists, contact your authorized service provider. |
Error |
1105 |
IPMI status became unavailable |
A hardware condition has rendered IPMI status unavailable. |
No action is required. |
Warning |
1107 |
Adding logical volumes |
New logical volumes are being added to a node. |
No action is required. |
Notice |
1108 |
Logical volumes added |
New logical volumes were added to a node, thereby increasing the storage capacity of the node. |
No action is required. |
Notice |
1109 |
Logical volumes added |
New logical volumes were added to a node. These are standby volumes for zero-copy failover. |
No action is required. |
Notice |
1110 |
Failed to add logical volumes |
The addition of new logical volumes to a node failed. |
Contact your authorized service provider. |
Error |
1111 |
Front-end communication status became unavailable |
A hardware condition has rendered front-end communication status unavailable. |
No action is required. |
Warning |
1112 |
Storage status became unavailable |
A hardware condition has rendered storage status unavailable. |
No action is required. |
Warning |
1113 |
Spindown capacity warning |
The amount of free spindown storage on the HCP storage nodes is low. |
Consider adding spindown storage capacity to the HCP system before the amount of free spindown storage becomes critically low. |
Warning |
1114 |
Spindown capacity critical |
The amount of free spindown storage on the HCP storage nodes may be insufficient to support the addition of new objects. |
Increase the amount of free spindown storage by adding more storage capacity or deleting objects from the repository. |
Error |
1115 | Moving database | The database is being moved to new logical volumes on a node. | No action is required. | Notice |
1116 | Database moved | The database has been moved to new logical volumes on a node. | No action is required. | Notice |
1117 | Failed to move database | The database move to new logical volumes on a node has failed. | Contact your authorized service provider. | Error |
1118 | Old database deleted | The old database has been deleted. | No action is required. | Notice |
1119 | Moving database | The database is being moved to the new dedicated logical volume on a node. | No action is required. | Notice |
1120 | Database moved | The database has been moved to the new dedicated logical volume on a node. | No action is required. | Notice |
1200 |
Last update sent to HDvM was unsuccessful |
HCP is unable to communicate with the HDvM server. |
Ensure that you have correctly configured HDvM in the System Management Console and that the HDvM server is healthy. |
Error |
1201 |
Log handler test message |
A user sent a test message to the syslog servers or SNMP managers. |
No action is required. |
Notice |
1202 |
About to change syslog settings |
A user changed the settings for syslog logging. |
No action is required. |
Notice |
1203 |
Syslog settings changed |
A user changed the settings for syslog logging. |
No action is required. |
Notice |
1204 |
About to change SNMP settings |
A user changed the settings for SNMP logging. |
No action is required. |
Notice |
1205 |
SNMP settings changed |
A user changed the settings for SNMP logging. |
No action is required. |
Notice |
1206 |
Email notification failed |
SMTP or email settings may be incorrect. |
Check the SMTP and email settings. If the settings are correct, contact your SMTP administrator for help. |
Warning |
1220 |
Successfully downloaded logs |
The HCP internal logs have been successfully downloaded. |
No action is required. |
Notice |
1221 |
Started to download logs |
A user has requested a download of the HCP internal logs. |
No action is required. |
Notice |
1222 |
Failed to download logs |
The requested download of the HCP internal logs has failed. |
Try to download the logs again. If that fails, contact your authorized service provider. |
Warning |
1223 |
Started to download logs for node |
HCP has started downloading the internal logs on a node. |
No action is required. |
Notice |
1224 |
Successfully downloaded logs for node |
HCP has finished downloading the internal logs on a node. |
No action is required. |
Notice |
1225 |
Failed to download logs for node |
HCP failed to download the internal logs from a node and is continuing with the next node. |
No action is required. |
Warning |
1226 |
Logs marked |
A user inserted a message into the HCP internal logs. |
No action is required. |
Notice |
1227 |
Log encryption key uploaded |
A user uploaded an encryption key for use when downloading the HCP internal logs. |
No action is required. |
Notice |
1228 |
Log encryption key deleted |
A user deleted an encryption key that was used when downloading the HCP internal logs. |
No action is required. |
Notice |
1229 |
Log download preparation started |
A user has requested a download of the HCP internal logs. |
No action is required. |
Notice |
1230 |
Log download preparation complete |
Log download preparation is complete, and the HCP internal logs are ready to be download. |
No action is required. |
Notice |
1231 |
Log download started |
The HCP internal logs have begun streaming to an HTTP client. |
No action is required. |
Notice |
1232 |
Log download complete |
The HCP internal logs have been downloaded. |
No action is required. |
Notice |
1233 |
Log download preparation complete with issues |
Log download preparation finished with issues. The unaffected HCP internal logs are ready to be downloaded. |
Download one or more of the available logs. Check the nodes identified in the error message. |
Warning |
1500 |
Successfully downloaded health check reports |
The HCP health check reports have been successfully downloaded. |
No action is required. |
Notice |
1501 |
Started to download health check reports |
A user has requested a download of the HCP health check reports. |
No action is required. |
Notice |
1502 |
Failed to download health check reports |
The requested download of the HCP health check reports has failed. |
Try to download the health check again. If that fails, contact your authorized service provider. |
Warning |
1503 |
Started to download health check for node |
HCP has started downloading the internal health check on a node. |
No action is required. |
Notice |
1504 |
Successfully downloaded health check for node |
HCP has finished downloading the internal health check on a node. |
No action is required. |
Notice |
1505 |
Failed to download health check for node |
HCP failed to download the internal health check from a node and is continuing with the next node. |
No action is required. |
Warning |
1506 |
Health check report download preparation started |
The HCP system has started to prepare the HCP health check reports for downloading. |
No action is required. |
Notice |
1507 |
Health check report download preparation complete |
The HCP system has finished preparing the health check reports. The reports are now ready to be downloaded. |
No action is required. |
Notice |
1508 |
Health check report streaming started |
The HCP health check reports have begun streaming to an HTTP client. |
No action is required. |
Notice |
1509 |
Health check report streaming complete |
The HCP health check reports have been downloaded. |
No action is required. |
Notice |
1510 |
Health check report download preparation complete with issues |
Health check report download preparation finished with issues. The unaffected HCP health check reports are ready to be downloaded. |
Download one or more of the available health check reports. Check the nodes identified in the error message. |
Warning |
1905 |
Service start skipped |
A service was not started because the time remaining until a scheduled stop was less than the minimum runtime for the service. |
No action is required. |
Notice |
1906 |
Scheduled service time period too short |
A scheduled time period for a service is shorter than the minimum runtime for the service. The service will not run in that time period. |
Increase the length of the applicable time period in the service schedule. |
Warning |
1980 |
Service schedule activated |
A user activated a service schedule. |
No action is required. |
Notice |
1981 |
Service schedule activation failed |
A user tried to activate a service schedule, but the activation failed. |
Check that the schedule has not been deleted. If the schedule has not been deleted, contact your authorized service provider. |
Error |
1982 |
Service schedule created |
A user created a service schedule. |
No action is required. |
Notice |
1983 |
Service schedule updated |
A user updated a service schedule. |
No action is required. |
Notice |
1984 |
Service schedule deleted |
A user deleted a service schedule. |
No action is required. |
Notice |
2000 |
Protection service started |
The Protection service has started. |
No action is required. |
Notice |
2001 |
Protection service stopped: run complete |
The Protection service finished successfully. |
No action is required. |
Notice |
2002 |
Protection service stopped without finishing |
The Protection service was interrupted without validating all objects or object parts. |
No action is required. |
Notice |
2003 |
Protection service stopped without finishing |
The Protection service was interrupted without validating all objects or object parts. |
No action is required. |
Warning |
2004 |
Protection service changed protection sets |
The Protection service changed protection sets. |
No action is required. |
Notice |
2005 | HCP found an unavailable object or object part | HCP could not repair an object or object part because the object or object part was unavailable. | Contact your HCP system administrator. | Warning |
2006 | HCP found an irreparable object or object part | HCP found a broken object or object part it could not repair. | Contact your HCP system administrator. | Error |
2007 |
Protection service beginning repairs |
Protection service is beginning object or object part repairs. |
No action is required. |
Warning |
2008 |
Protection service: irreparable object or object part |
The Protection service detected a violation it could not fix. |
Contact your authorized service provider. |
Error |
2009 |
Protection service: unavailable object |
The Protection service detected a violation it could not fix. |
Contact your authorized service provider. |
Warning |
2010 |
Garbage Collection service started |
The Garbage Collection service has started. |
No action is required. |
Notice |
2011 |
Garbage Collection service finished: run complete |
The Garbage Collection service finished successfully. |
No action is required. |
Notice |
2012 |
Garbage Collection stopped without finishing |
The Garbage Collection service stopped without completing its run. The service will resume automatically at a later time. |
No action is required. |
Notice |
2013 |
Garbage Collection stopped without finishing |
The Garbage Collection service stopped without completing its run. The service will resume automatically at a later time. |
No action is required. |
Warning |
2017 |
Garbage Collection service beginning repairs |
The Garbage Collection service has begun fixing violations. |
No action is required. |
Notice |
2020 |
Scavenging service started |
The Scavenging service has started. |
No action is required. |
Notice |
2021 |
Scavenging service stopped: run complete |
The Scavenging service finished successfully. |
No action is required. |
Notice |
2022 |
Scavenging service stopped: run bypassed object(s) or object part(s) |
The Scavenging service finished successfully. Some objects or object parts were not scavenged in this run. |
No action is required. |
Notice |
2023 |
Scavenging service stopped without finishing |
The Scavenging service stopped without completing its run. Scavenging will resume at a later time. |
No action is required. |
Warning |
2024 |
Scavenging service stopped without finishing |
The Scavenging service stopped without completing its run. The service will resume at a later time. |
No action is required. |
Notice |
2027 |
Scavenging service beginning repairs |
The Scavenging service has begun repairs. |
No action is required. |
Warning |
2028 | HCP found an irreparable object or object part | HCP was unable to repair the object. The repair may be retried at a later time. | Contact your HCP system administrator. | Error |
2029 |
Scavenging service irreparable object |
The Scavenging service was unable to repair the object. The repair may be retried at a later time. |
Use the System Management Console to verify the health of the system. If the problem persists, contact your authorized service provider. |
Error |
2030 |
Capacity Balancing service started |
The Capacity Balancing service has started. |
No action is required. |
Notice |
2031 |
Capacity Balancing service stopped: run complete |
The Capacity Balancing service finished successfully. |
No action is required. |
Notice |
2032 |
Capacity Balancing service stopped: run bypassed object(s) or object part(s) |
Some objects or object parts were bypassed during this run of the Capacity Balancing service. Those objects or object parts will be handled in a future run. |
No action is required. |
Notice |
2033 |
Capacity Balancing service stopped without finishing |
The Capacity Balancing service stopped without completing its run. |
No action is required. |
Warning |
2034 |
Capacity Balancing service stopped without finishing |
The Capacity Balancing service stopped without completing its run. |
No action is required. |
Notice |
2037 |
Capacity Balancing service beginning repairs |
Capacity Balancing service has begun repairs. |
No action is required. |
Warning |
2040 |
Content Verification service started |
The authentication service has started. |
No action is required. |
Notice |
2041 |
Content Verification service stopped: run complete |
The authentication service finished successfully. |
No action is required. |
Notice |
2042 |
Content Verification service stopped without finishing |
The Content Verification service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Notice |
2043 |
Content Verification service stopped without finishing |
The Content Verification service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Warning |
2044 | HCP found an unavailable object or object part | HCP could not repair an object or object part because the object or object part was unavailable. | Contact your HCP system administrator. | Warning |
2045 |
Content Verification service: unavailable object |
The Content Verification service detected a violation it could not fix. |
Contact your authorized service provider. |
Warning |
2046 | HCP found an irreparable object or object part | HCP found a broken object or object part it could not repair. | Contact your HCP system administrator. | Error |
2047 |
Content Verification service beginning repairs |
The Content Verification service has begun repairs. |
No action is required. |
Warning |
2048 |
Content Verification service: irreparable object or object part |
The Content Verification service detected a violation it could not fix. |
Contact your authorized service provider. |
Error |
2049 | Annotation no longer present | One or more objects no longer have a previously added annotation. | If annotations were not intentionally deleted, contact your authorized service provider. | Warning |
2050 |
Duplicate Elimination service started |
The Duplicate Elimination service has started. |
No action is required. |
Notice |
2051 |
Duplicate Elimination service stopped: run complete |
The Duplicate Elimination service finished successfully. |
No action is required. |
Notice |
2052 |
Duplicate Elimination service stopped: run bypassed object(s) or object part(s) |
The Duplicate Elimination service finished successfully. Some objects or object parts were not checked during this run. They will be checked in a future run. |
No action is required. |
Notice |
2053 |
Duplicate Elimination service stopped without finishing |
The Duplicate Elimination service stopped during its merge phase without completing its run. The service will resume at some point in the future. |
No action is required. |
Warning |
2054 |
Duplicate Elimination service stopped without finishing |
The Duplicate Elimination service stopped during its merge phase without completing its run. The service will resume at some point in the future. |
No action is required. |
Notice |
2057 |
Duplicate Elimination service beginning repairs |
The Duplicate Elimination service has begun merging objects and object parts. |
No action is required. |
Notice |
2058 |
Service beginning repairs from a remote system |
A service has begun making repairs from a remote system. |
No action is required. |
Notice |
2059 | Fast Object Recovery service started | The Fast Object Recovery service has started. | No action is required. | Notice |
2060 | Fast Object Recovery service stopped: run complete | The Fast Object Recovery service finished successfully. | No action is required. | Notice |
2061 | Fast Object Recovery service stopped without finishing | The Fast Object Recovery service stopped without completing its run. The service will resume at some point in the future. | No action is required. | Notice |
2062 | Fast Object Recovery service stopped without finishing | The Fast Object Recovery service stopped without completing its run. The service will resume at some point in the future. | No action is required. | Warning |
2064 | Fast Object Recovery service beginning repairs | TheFast Object Recovery service has begun repairs. | No action is required. | Warning |
2065 | Fast Object Recovery service: irreparable object | The Fast Object Recovery service detected a violation it could not fix. | Contact your authorized service provider. | Error |
2066 | Fast Object Recovery service: failure limit reached | The Fast Object Recovery service experienced successive failures. | Contact your authorized service provider. | Error |
2070 | Object or object part has been shredded | An object or object part was shredded. | No action is required. | Notice |
2079 |
Compression/Encryption service stopped without finishing |
The Compression/Encryption service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Notice |
2080 |
Compression/Encryption service started |
The Compression/Encryption service has started. |
No action is required. |
Notice |
2081 |
Compression/Encryption service stopped: run complete |
The Compression/Encryption service finished successfully. |
No action is required. |
Notice |
2082 |
Compression/Encryption service stopped without finishing |
The Compression/Encryption service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Warning |
2083 |
Service could not start |
A service was requested to run but could not start for some reason. |
No action is required. |
Warning |
2084 |
Disposition service started |
The Disposition service has started. |
No action is required. |
Notice |
2085 |
Disposition service stopped: run complete |
The Disposition service finished successfully. |
No action is required. |
Notice |
2086 |
Disposition service stopped without finishing |
The Disposition service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Warning |
2091 |
Disposition service stopped without finishing |
The Disposition service stopped without completing its run. The service will resume at some point in the future. |
No action is required. |
Notice |
2105 |
Replication link created |
A user created a replication link. |
No action is required. |
Notice |
2106 |
Replication link suspended |
A replication link has been suspended. |
No action is required. |
Notice |
2107 |
Replication link resumed |
A suspended replication link has been resumed. |
No action is required. |
Notice |
2108 |
Replication link failure |
A replication link is not working. |
Check network connectivity to the remote system. |
Error |
2109 |
Replication link deleted |
A replication link was deleted. |
If this event is unexpected, contact your authorized service provider. |
Warning |
2110 |
Replication link read-only |
The tenants and directories included in a replication link are now read-only on this system. |
No action is required. |
Notice |
2111 |
Replication link authorized |
A replication link was authorized. |
No action is required. |
Notice |
2112 |
Replication link updated |
A user updated the configuration of a replication link. |
No action is required. |
Notice |
2113 |
Replication link failed over |
A user failed over a replication link. The replicated tenants and directories are now read-write on the replica and read-only on the primary system. |
Redirect client requests to the replica. |
Notice |
2114 |
Replication link failed back |
A user failed back a replication link. |
No action is required. |
Notice |
2115 |
Replication data recovery started |
Data recovery has started on a replication link. The replicated tenants and directories are read-write on the replica and read-only on the primary system. |
Monitor the recovery progress in the System Management Console. |
Warning |
2116 |
Replication data recovery completed |
Data recovery has completed on a replication link. The replicated tenants and directories are now read-write on the primary system and read-only on the replica. |
Redirect client requests to the primary system. |
Warning |
2117 |
Replication link missing on remote system |
A replication link configured on this system is missing on the remote system. The link has been suspended. |
Restore the replication link to begin the recovery process. |
Error |
2118 |
Object replicated with collisions |
An object being replicated conflicts with an existing object on the target system. The object has been stored in the .lost+found directory on the target system. |
No action is required. |
Warning |
2119 |
Object did not replicate |
An object was not replicated. |
Contact your authorized service provider. |
Error |
2120 |
Object or object part did not replicate; will retry later |
An object or object part was not replicated. Replication of the object or object part will be retried later. |
Monitor the remote system to see whether this object or object part is eventually replicated. If the object or object part does not replicate within one week, contact your authorized service provider. |
Warning |
2121 |
Duplicate Elimination service sort started |
The Duplicate Elimination service has started the sort phase of its run. |
No action is required. |
Notice |
2122 |
Duplicate Elimination service sort finished |
The Duplicate Elimination service successfully finished the sort phase of its run. |
No action is required. |
Notice |
2123 |
Duplicate Elimination service sort stopped without finishing |
The Duplicate Elimination service stopped during its sort phase without completing its run. The service will resume at some point in the future. |
No action is required. |
Notice |
2126 |
Replica capacity limit reached |
HCP suspended a replication link due to insufficient capacity on the replica. |
Add storage capacity to the replica and resume the replication link. |
Warning |
2127 |
Time sync problem |
The time on this system is not in sync with the time on the other system in a replication link in which this system participates. |
Ensure that time is synchronized on all the HCP systems in the replication topology. |
Warning |
2128 |
Collisions occurred on replication link |
One or more collisions occurred on a replication link in the last 24 hours. |
No action is required. |
Warning |
2129 |
Replication link failed over automatically |
A replication link failed over automatically because communication was disrupted for an extended period of time. The replicated tenants and directories are now read-write on the replica and read-only on the primary system. |
Redirect client requests to the replica. |
Notice |
2130 |
Replication link failed over automatically |
A replication link failed over automatically because communication was disrupted for an extended period of time. |
No action is required. |
Notice |
2131 |
Replication link final data recovery started automatically |
Final data recovery has started automatically on a replication link. The replicated tenants and directories are now read-only on both the primary system and the replica. |
No action is required. |
Warning |
2132 |
Replication link automatically failed back |
A replication link failed back automatically. |
No action is required. |
Notice |
2133 | Objects in one or more namespaces could not be replicated; will retry later | One or more objects could not be replicated. Another attempt to replicate these objects will be made later. | Monitor the remote system to see whether these objects are eventually replicated. If the objects are not replicated within one week, contact your authorized service provider. | Warning |
2134 | Replication link is candidate for auto failover | Replication link is candidate for auto failover because communication is disrupted for an extended period of time. | No action is required. | Warning |
2140 |
Replication SSL certificate downloaded |
A user downloaded an SSL server certificate for replication. |
No action is required. |
Notice |
2141 |
New replication SSL certificate uploaded |
A user uploaded a new replication client certificate. |
No action is required. |
Notice |
2142 |
Replication SSL certificate deleted |
A user deleted a replication client certificate. |
No action is required. |
Notice |
2143 |
Replication link progress checkpoints reset |
A user set the replication progress checkpoints to a specified time. Replication will begin from this new point in time. |
No action is required. |
Warning |
2144 |
Replication link rejected |
A replication link was rejected. |
If this event is unexpected, contact your authorized service provider. |
Warning |
2145 |
Replication link final data recovery pass started |
The final data recovery pass has started on a replication link. The replicated tenants and directories are now read-only on both the primary system and the replica. |
No action is required. |
Warning |
2146 |
Replication link suspended automatically |
A replication link was suspended because of a problem. |
Ensure that the primary system, the replica, and the network are healthy. Then resume the link. |
Error |
2147 |
Replication adversely affected due to failed network connections |
A front-end network connection is unavailable. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2148 |
Replication automatically paused for a tenant due to error |
Replication was automatically paused for a tenant due to a problem from which HCP could not recover by itself. |
Ensure that the primary system, the replica, and the network are healthy and that no tenant collisions have occurred. Then resume replication for the paused tenant. |
Error |
2149 |
Replication paused for a tenant |
A user paused replication of a tenant. |
No action is required. |
Notice |
2150 |
Replication resumed for a tenant |
A user resumed replication of a tenant. |
No action is required. |
Notice |
2151 |
Replication link suspended according to schedule |
A replication link was suspended according to schedule. |
No action is required. |
Notice |
2152 |
Replication link performance level changed according to schedule |
The performance level of a replication link changed according to schedule. |
No action is required. |
Notice |
2153 |
Replication link schedule updated |
The schedule for a replication link was updated. |
No action is required. |
Notice |
2156 | Replication has been stopped for this tenant | Replication of the tenant was stopped for the indicated reason. | If the cause is one or more namespace name collisions, rename each indicated namespace. If the cause is that the replica does not support the DPL of one or more namespaces, lower the DPL of each indicated namespace. Alternatively, in either case, you can deselect the namespace from being replicated. After you make the necessary changes, notify your HCP system administrator that the problem has been resolved. | Error |
2157 | Namespace replication collision detected | A namespace replication collision was detected, possibly requiring intervention from the tenant administrator. | If the cause is one or more namespace name collisions, rename each indicated namespace. If the cause is that the replica does not support the DPL of one or more namespaces, lower the DPL of each indicated namespace. Alternatively, in either case, you can deselect the namespace from being replicated. After you make the necessary changes, notify your HCP system administrator that the problem has been resolved. | Notice |
2158 | Additional top-level directories selected for replication | The indicated top-level directories were selected for replication. | No action is required. | Notice |
2159 | One or more top-level directories removed from replication | The indicated top-level directories were removed from replication. | No action is required. | Notice |
2160 | User account replicated with collisions | Either or both of two user accounts with the same user ID on a 4.x system were modified on that system, resulting in conflicting values for one or more properties. On replication to this system, the values for those properties were taken from the account with roles. | Ensure that the user account is configured correctly. | Warning |
2161 |
All replication links shut down |
A user shut down all replication links. |
No action is required. |
Notice |
2162 |
All replication links reestablished |
A user reestablished all replication links. |
No action is required. |
Notice |
2163 |
Replication stalled |
Replication stalled while replicating an object or object part. |
If the problem persists, contact your authorized service provider. |
Error |
2164 | Replication link failed over | A user failed over a replication link. | Redirect client requests to this system. | Notice |
2165 | Replication link failed over | A user failed over a replication link. | Redirect client requests to the remote system. | Notice |
2166 | Stalled replication link has recovered | Previous stalled replication has recovered. | No action is required. | Notice |
2167 | The broken replication link recovered | The broken replication link has been repaired. | No action is required. | Notice |
2168 | Replication automatically paused for tenant on link outside active erasure coding topology | A tenant in the active erasure coding topology is also on a replication link that is not part of the topology. | Either remove the tenant from the link, or remove the tenant from the active erasure coding topology. | Error |
2200 |
Storage Tiering service started |
The Storage Tiering service has started. |
No action is required. |
Notice |
2201 |
Storage Tiering service stopped: run complete |
The Storage Tiering service finished successfully. |
No action is required. |
Notice |
2203 |
Storage Tiering service stopped without finishing |
The Storage Tiering service was interrupted without examining all objects. |
No action is required. |
Warning |
2204 |
Storage Tiering service stopped without finishing |
The Storage Tiering service was interrupted without examining all objects. |
No action is required. |
Notice |
2250 | Geo-distributed Erasure Coding service started | The Geo-distributed Erasure Coding service has started. | No action is required. | Notice |
2251 | Geo-distributed Erasure Coding service stopped: run complete | The Geo-distributed Erasure Coding service finished successfully. | No action is required. | Notice |
2253 | Geo-distributed Erasure Coding service stopped without finishing | The Geo-distributed Erasure Coding service was interrupted without examining all objects. | No action is required. | Warning |
2254 | Geo-distributed Erasure Coding service stopped without finishing | The Geo-distributed Erasure Coding service was interrupted without examining all objects. | No action is required. | Notice |
2300 |
User account created |
A user created a user account. |
No action is required. |
Notice |
2301 |
User account updated |
A user updated a user account. |
No action is required. |
Notice |
2302 |
User account deleted |
A user deleted a user account. |
No action is required. |
Notice |
2303 |
User authenticated |
A user login to the System Management Console was successfully authenticated. |
No action is required. |
Notice |
2304 |
Authentication attempt by unknown user |
A user tried to log in with an unknown username. |
Have the user log in with a valid username and password. |
Warning |
2305 |
Account reenabled by timer |
A disabled security user account has been automatically reenabled. |
No action is required. |
Notice |
2306 |
Account is disabled |
A user tried to log in with a disabled account. |
Reenable the user account to allow the user to log in. |
Warning |
2307 |
Account has been inactive for too long |
A user tried to log in with an account that was disabled due to inactivity. |
Reenable the user account to allow the user to log in. |
Warning |
2308 |
Account does not include the required roles |
A user tried to log in with an account that does not include a required role. |
Update the account to include the required role to allow the user to log in. |
Warning |
2309 |
Password is invalid |
A user tried to log in with an invalid password. |
Have the user log in with a valid username and password. |
Warning |
2310 |
Remote authentication server error |
The login for a remotely authenticated user failed due to an error communicating with a RADIUS server. |
Check the health of the RADIUS servers and the connections to them. If you cannot detect any problems, contact your authorized service provider. |
Warning |
2311 |
Password changed |
A user changed the password for a user account. |
No action is required. |
Notice |
2312 |
Account enabled |
A user account has been enabled. |
No action is required. |
Notice |
2313 |
Account disabled |
A user account has been disabled. |
No action is required. |
Notice |
2314 |
Account disabled due to too many failed logins |
A user account was automatically disabled due to too many failed login attempts. |
Reenable the user account and have the user log in with a valid username and password. |
Warning |
2315 |
Account will be reenabled |
A security user account will be reenabled automatically after a waiting period. |
No action is required. |
Notice |
2316 |
All accounts reset |
A user reset user accounts to their initial configuration. All accounts have been deleted and the initial accounts have been recreated. |
No action is required. |
Warning |
2317 |
User authenticated |
A user login to the Search Console was successfully authenticated. |
No action is required. |
Notice |
2319 |
Active Directory server error |
A user tried to log in with an invalid Active Directory username or password. |
Have the user log in with a valid username and password. |
Warning |
2330 |
RADIUS server created |
A user configured a new RADIUS server. |
No action is required. |
Notice |
2331 |
RADIUS server updated |
A user updated the configuration of a RADIUS server. |
No action is required. |
Notice |
2332 |
RADIUS server deleted |
A user deleted a RADIUS server. |
No action is required. |
Notice |
2333 |
RADIUS server promoted |
A user moved a RADIUS server up in the list. |
No action is required. |
Notice |
2334 |
RADIUS server demoted |
A user moved a RADIUS server down in the list. |
No action is required. |
Notice |
2335 |
All RADIUS servers deleted |
A user deleted all RADIUS servers. The list of RADIUS servers is now empty. |
No action is required. |
Warning |
2340 |
An exception occurred while removing Service Principal Name from Active Directory |
HCP failed to remove a Service Principal Name from Active Directory. |
Verify that the Service Principal Name was removed from Active Directory. |
Warning |
2341 | An exception occurred while removing Service Principal Name from Active Directory | HCP failed to remove a Service Principal Name from Active Directory. | Verify that the Service Principal Name was removed from Active Directory. | Warning |
2342 |
Successfully added Service Principal Name to Active Directory |
HCP successfully added a Service Principal Name to Active Directory. |
No action is required. |
Notice |
2344 |
Failed to add Service Principal Name to Active Directory |
HCP failed to add a Service Principal Name to Active Directory. |
Verify that the Service Principal Name was added to Active Directory. |
Warning |
2346 |
An exception occurred while adding Service Principal Name to Active Directory |
HCP failed to add a Service Principal Name to Active Directory. |
Verify that the Service Principal Name was added to Active Directory. |
Warning |
2350 |
Group account created |
A user created a group account. |
No action is required. |
Notice |
2352 |
Group account updated |
A user updated a group account. |
No action is required. |
Notice |
2354 |
Group account deleted |
A user deleted a group account. |
No action is required. |
Notice |
2356 |
Active Directory SSL certificate downloaded |
A user downloaded an SSL server certificate for Active Directory. |
No action is required. |
Notice |
2357 |
Incompatible namespace setting for authenticated CIFS |
One or more namespaces are configured for CIFS authenticated access only, but the system is not configured to support authenticated CIFS. As a result, CIFS cannot be used for access to those namespaces. |
Either enable authenticated CIFS support for the system or have the tenant administrators reconfigure the affected namespaces to support both anonymous and authenticated access with CIFS. |
Warning |
2358 |
Incompatible namespace setting for authenticated CIFS |
A namespace is configured for CIFS authenticated access only, but the system is not configured to support authenticated CIFS. As a result, CIFS cannot be used for access to that namespace. |
Reconfigure the affected namespace to support both anonymous and authenticated access with CIFS. |
Warning |
2359 |
Active Directory authentication enabled |
A user enabled Active Directory authentication for the HCP system. |
No action is required. |
Notice |
2360 |
Active Directory authentication disabled |
A user disabled Active Directory authentication for the HCP system. |
No action is required. |
Notice |
2361 |
Active Directory cache cleared |
A user cleared the Active Directory cache. |
No action is required. |
Notice |
2362 |
Active Directory partially configured |
CIFS configuration is not complete on the indicated node. |
Reconfigure support for Active Directory in the System Management Console. |
Warning |
2363 |
Active Directory computer account is invalid |
The Active Directory computer account is invalid. |
Reconfigure support for Active Directory in the System Management Console. |
Warning |
2364 |
Active Directory communication disrupted |
The CIFS services are no longer running on the indicated node. |
Reconfigure support for Active Directory in the System Management Console to restart the CIFS service. |
Warning |
2365 |
Attempt to access the Active Directory server failed |
A connection issue occurred while the indicated node was trying to access the Active Directory server. |
No action is required. |
Warning |
2366 |
Active Directory configuration restored |
A user updated the Active Directory configuration. |
No action is required. |
Notice |
2367 |
Active Directory computer account restored |
A user updated the Active Directory computer account. |
No action is required. |
Notice |
2368 |
Active Directory communication restored |
The indicated node can now communicate with the Active Directory server. HCP can again service CIFS requests. |
No action is required. |
Notice |
2369 |
Communication restored when trying to access the Active Directory server |
The indicated node can now communicate with the Active Directory server. |
No action is required. |
Notice |
2370 |
Could not establish secure connection to the Active Directory server |
The Active Directory computer account credentials are invalid, or there is no current Active Directory SSL server certificate. |
Update the Active Directory credentials or SSL server certificate. |
Notice |
2371 |
Secure connection to Active Directory server restored |
A user updated the Active Directory computer account credentials or SSL server certificate. |
No action is required. |
Notice |
2372 |
Active Directory single sign-on misconfigured |
The Active Directory SPN for a tenant and or namespace does not exist. |
Update the Active Directory single sign-on setting for the tenant and or namespace. For information about which tenants are involved, see the Status section on the Active Directory page in the HCP System Management Console. |
Warning |
2373 |
Active Directory single sign-on restored |
The Active Directory SPN was created for the misconfigured tenants and or namespaces. |
No action is required. |
Warning |
2375 |
Active Directory service record lookup failed |
The Active Directory service record lookup failed for the indicated domain. |
Check the DNS configuration. |
Warning |
2376 |
Active Directory DNS reverse lookup succeeded |
The Active Directory DNS reverse lookup succeeded for the indicated domain. |
No action is required. |
Notice |
2377 |
Active Directory DNS reverse lookup failed |
The Active Directory DNS reverse lookup failed for the indicated domain. |
Check the DNS configuration. |
Warning |
2378 |
Active Directory service records were not found. |
The Active Directory service records were not found during an Active Directory health check. |
Check the DNS configuration. |
Warning |
2379 |
Winbind unavailable |
Winbind was found to be unavailable during an Active Directory health check. |
Update your Active Directory configuration. |
Warning |
2380 |
Failed to check Active Directory service account and connectivity |
Exception occurred while validating service account and connectivity for Active Directory during health check. |
Check the Active Directory connection and service account. |
Warning |
2381 |
Samba not running |
HCP could not get the status of Samba during an Active Directory health check. |
Update your Active Directory configuration. |
Warning |
2382 |
Missing SPN(s) on Active Directory Server |
One or more tenant/namespace SPN/s are missing from the Active Directory database. |
Update your Active Directory configuration. |
Warning |
2383 |
Active Directory LDAP service record lookup succeeded |
HCP successfully looked up the LDAP service record for the indicated Active Directory domain. |
No action is required. |
Notice |
2384 |
Active Directory LDAP service record lookup failed |
Failed to look up the LDAP service record for Active Directory domain. |
Check that the DNS server is configured to publish LDAP service records. |
Warning |
2385 |
Active Directory kerberos service record lookup succeeded |
HCP successfully looked up the Kerberos service record for the indicated Active Directory domain. |
No action is required. |
Notice |
2386 |
Active Directory Kerberos service record lookup failed |
Failed to look up the Kerberos service record for Active Directory domain. |
Check that the DNS server is configured to publish Kerberos service record and Kerberos server is running. |
Warning |
2387 |
Active Directory service account creation successful |
HCP successfully created an Active Directory service account on the indicated Active Directory server. |
No action is required. |
Notice |
2388 |
Failed to create Active Directory service account |
HCP failed to create the Active Directory service account for the domain. |
Check that the Active Directory domain user's name and password are correct. Also make sure the domain user has sufficient permissions to create the service account. |
Warning |
2389 |
Active Directory node account created |
An Active Directory node account was successfully created for the indicated node. |
No action is required. |
Notice |
2390 |
Active Directory has been disabled |
HCP has disabled Active Directory because a change to the DNS settings affected Active Directory connectivity. |
No action is required. |
Notice |
2391 |
Failed to disable Active Directory |
A user attempt to disable Active Directory configuration failed. |
Check that the Active Directory server was running and not already disabled. |
Warning |
2392 |
Active Directory node account deleted |
Active Directory node account was successfully deleted. |
No action is required. |
Notice |
2393 |
Active Directory service user password updated |
Automatic password updated because password refresh period elapsed. |
No action is required. |
Warning |
2394 |
Failed to update Active Directory service user password |
HCP may not have sufficient permissions to update the service user password. |
Update Active Directory configuration and provide a domain user with sufficient permissions for password update. |
Warning |
2395 |
Successfully removed Service Principal Name from Active Directory. |
Successfully removed Service Principal Name from the Active Directory. |
No action is required. |
Notice |
2397 | Failed to remove Service Principal Name from the Active Directory | Failed to remove Service Principal Name from the Active Directory. | Verify that Active Directory Service Principal Name is cleaned up. | Warning |
2400 |
New SSL server certificate uploaded |
A user uploaded an SSL server certificate. |
No action is required. |
Notice |
2401 |
New SSL server certificate signing request generated |
A user requested a new certificate signing request. |
No action is required. |
Notice |
2402 |
New SSL server certificate generated |
A user requested the creation of a new SSL server certificate. |
No action is required. |
Notice |
2403 |
SSL server certificate expires soon |
The SSL server certificate for this system expires soon. If the certificate expires, HTTPS access to the system will fail, and replication will fail. |
Install a new SSL server certificate with a later expiration date. |
Warning |
2404 |
SSL server certificate expired |
The SSL server certificate for this system has expired. HTTPS access to the system is not allowed, and replication has stopped. |
Install a new SSL server certificate with a later expiration date. |
Error |
2405 |
Trusted replication server certificate expires soon |
The indicated trusted replication server certificate expires soon. If the certificate expires, replication with the system from which the certificate was obtained will fail. |
When the other system in the replication pair installs a new SSL server certificate, obtain that certificate and upload it to this system as a trusted replication server certificate. |
Warning |
2406 |
Trusted replication server certificate expired |
The indicated trusted replication server certificate has expired. Replication with the system from which the certificate was obtained has stopped. |
When the other system in the replication pair installs a new SSL server certificate, obtain that certificate and upload it to this system as a trusted replication server certificate. |
Error |
2407 |
Active Directory server certificate expires soon |
The Active Directory SSL server certificate expires soon. If the certificate expires, access to the Active Directory server may fail. |
Install a new Active Directory SSL server certificate with a later expiration date. |
Warning |
2408 |
Active Directory server certificate expired |
The Active Directory SSL server certificate has expired. Access to the Active Directory server may fail. |
Install a new Active Directory SSL server certificate with a later expiration date. |
Error |
2409 |
SSL server certificate deleted |
A user deleted an SSL server certificate. |
No action is required. |
Notice |
2410 |
SSL server certificate signing request downloaded |
A user downloaded an SSL certificate signing request. |
No action is required. |
Notice |
2411 |
Active Directory service account deletion successful |
HCP successfully deleted an Active Directory service account on the indicated Active Directory server. |
No action is required. |
Notice |
2412 |
Failed to delete the Active Directory service account for the listed user and organization unit. Received response. |
The Active Directory server is either unreachable or the service account does not exist. |
Please manually delete the HCP computer service account from the Active Directory domain it belongs to, if it exists. |
Warning |
2413 |
Failed to join domain and create Active Directory node account |
The Active Directory server is either unreachable or the node account does not exist. |
Check that the user name and password are correct, and that the server is reachable. |
Warning |
2414 |
Failed to leave domain and delete the Active Directory node account for the listed node. Received response. |
The Active Directory server is either unreachable or the node account does not exist. |
Check that the user name and password are correct, and that the server is reachable. |
Warning |
2415 |
Active Directory domain resolution successful |
HCP successfully resolved an Active Directory domain. |
No action is required. |
Notice |
2416 |
Active Directory domain resolution failed |
The DNS server may not be configured to return Active Directory server IP addresses. |
Check that the DNS server is configured to resolve domain name of the Active Directory server. |
Warning |
2417 |
Active Directory domain join failed |
The Active Directory domain may be unreachable, or the user account may be invalid. |
Check that the KDC, LDAP, and Global Catalog servers are running on the domain controller, and that the service account is valid. |
Warning |
2418 |
An error occured while communicating with Active Directory |
The Active Directory domain may be unreachable, or the service user account may be invalid. |
Check that the service account is valid and the Active Directory server is reachable. |
Warning |
2500 |
PGP private key uploaded |
A user uploaded a PGP private key. |
No action is required. |
Notice |
2501 |
PGP encryption key uploaded |
A user uploaded a PGP encryption key. |
No action is required. |
Notice |
2502 |
PGP key deleted |
A user deleted a PGP private or encryption key. |
No action is required. |
Notice |
2600 |
Node shutdown requested from System Management Console |
A user shut down a node from the System Management Console. |
No action is required. |
Notice |
2601 |
HCP shutdown requested from System Management Console |
A user shut down HCP from the System Management Console. |
No action is required. |
Notice |
2602 |
Service started |
A user started a service from the System Management Console. |
No action is required. |
Notice |
2603 |
Service stopped |
A user stopped a service from the System Management Console. |
No action is required. |
Notice |
2604 |
Service enabled |
A user enabled a service from the System Management Console. |
No action is required. |
Notice |
2605 |
Service disabled |
A user disabled a service from the System Management Console. |
No action is required. |
Notice |
2606 |
Configuration changed |
A user changed a configuration value of an HCP component. |
No action is required. |
Notice |
2607 |
Version upgraded |
A user completed a software upgrade by updating the internal messaging version. |
No action is required. |
Notice |
2609 |
Irreparable object acknowledged |
A user acknowledged an irreparable object. |
No action is required. |
Warning |
2610 |
All irreparable objects acknowledged |
A user acknowledged all irreparable objects. |
No action is required. |
Warning |
2611 |
Eject CD requested from System Management Console |
A user requested the ejection of the CD tray from a node. |
No action is required. |
Notice |
2614 |
Unauthorized action |
A user has requested an operation that is not authorized for the user account. |
If the user should be allowed to perform this operation, add the required role to the user account. |
Warning |
2615 |
Configuration changed |
A user changed a configuration value of an HCP component. |
No action is required. |
Notice |
2616 |
Upgrade started |
A user has started an upgrade of the HCP software. |
No action is required. |
Notice |
2617 |
Node restart requested from System Management Console |
A user restarted a node from the System Management Console. |
No action is required. |
Notice |
2618 |
HCP restart requested from System Management Console |
A user restarted HCP from the System Management Console. |
No action is required. |
Notice |
2619 |
Restart or shutdown command could not be executed |
An attempt to restart or shut down a node was could not be executed. The node may already be down. |
No action is required. |
Notice |
2620 |
Upgrade completed successfully |
An upgrade of the HCP software completed successfully. |
No action is required. |
Notice |
2621 |
OpenStack Identity Service cache cleared |
A user cleared the OpenStack Identity Service cache. |
No action is required. |
Notice |
2622 |
OpenStack Identity Service authentication enabled |
A user enabled OpenStack Identity Service authentication for the HCP system. |
No action is required |
Notice |
2623 |
OpenStack Identity Service authentication disabled |
A user disabled OpenStack Identity Service authentication for the HCP system. |
No action is required. |
Notice |
2624 |
Connection to OpenStack Identity Service failed |
HCP could not connect to the OpenStack Identity Service. |
Check the health of the OpenStack Identity Service and the network connecting HCP to that server |
Notice |
2625 |
Connection to OpenStack Identity Service restored |
The connection to the OpenStack Identity Service has been restored. |
No action is required |
Notice |
2626 | Unavailable object detected | HCP detected unavailable objects. | This state is often caused by a temporary outage and should be resolved within 24 hours. | Warning |
2700 |
Simple search query performed |
A user performed a simple search. |
No action is required. |
Notice |
2701 |
Advanced search query performed |
A user performed an advanced search. |
No action is required. |
Notice |
2702 |
Connection to HDDS server failed |
HCP could not connect to the HDDS server. |
Check the health of the HDDS server and the network connecting HCP to that server. |
Notice |
2703 |
Connection to HDDS server restored |
The connection to the HDDS server has been restored. |
No action is required. |
Notice |
2704 |
HDDS statistics credentials authentication failed |
HDDS authentication failed using the configured statistics credentials. |
Ensure that the statistics credentials specified for the HDDS search facility are valid. |
Notice |
2705 |
HDDS statistics credentials authentication successful |
HDDS authentication succeeded using the configured statistics credentials. |
No action is required. |
Notice |
2706 |
Search facility configuration changed |
A user changed the search facility configuration. |
No action is required. |
Notice |
2707 |
Search Console disabled |
A user changed the search facility selection for the Search Console to none, thereby disabling the ability to perform searches in that Console. |
No action is required. |
Notice |
2800 |
Network interface down |
A network interface went down. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2801 |
Network interface up |
A network interface came up. |
No action is required. |
Notice |
2802 |
Temperature sensor alarm |
A temperature sensor is reporting a temperature that is out of the recommended range. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2803 |
Temperature sensor alarm removed |
A temperature sensor is reporting a return to an acceptable operating temperature. |
No action is required. |
Notice |
2804 |
Fan sensor alarm |
A fan sensor is reporting a fan speed that is out of the recommended range. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2805 |
Fan sensor alarm removed |
A fan sensor is reporting a return to an acceptable fan speed. |
No action is required. |
Notice |
2806 |
Voltage sensor alarm |
A voltage sensor is reporting a voltage that is out of the recommended range. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2807 |
Voltage sensor alarm removed |
A voltage sensor is reporting a return to an acceptable operating voltage. |
No action is required. |
Notice |
2808 |
File system alarm |
A file system has reached the capacity warning threshold. |
Consider adding storage capacity to the HCP system before the amount of free storage becomes critically low. |
Error |
2809 |
File system alarm removed |
A file system has fallen below the capacity warning threshold. |
No action is required. |
Notice |
2810 |
Disk device alarm |
A disk device is reporting that it is not in a fully functional state. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2811 |
Disk device alarm removed |
A disk device is reporting that it has returned to a fully functional state. |
No action is required. |
Notice |
2812 |
Power supply alarm |
A power supply is indicating a problem. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2813 |
Power supply alarm removed |
A power supply is reporting that it has returned to a fully functional state. |
No action is required. |
Notice |
2814 |
Processor alarm |
A processor is indicating a problem. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2815 |
Processor alarm removed |
A processor is reporting that it has returned to a fully functional state. |
No action is required. |
Notice |
2816 |
Multipath degraded |
Redundant fibre channel connections to storage are not functioning correctly. |
Check the connections to the storage. If a problem exists, contact your authorized service provider. |
Error |
2817 |
Multipath restored |
Redundant access to the underlying storage has been restored. |
No action is required. |
Notice |
2818 | Failure trimming one or more volumes | Attempt to trim one or more volumes failed. | Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. | Warning |
2819 | SSD RAID is degraded | An SSD device went down | Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider | Error |
2820 |
IP configuration information changed |
A user changed network configuration settings through the System Management Console. |
No action is required. |
Notice |
2830 |
Time is unsynchronized |
Neither the external nor internal time servers could be reached for synchronization. |
Check that network and time settings are correct. |
Warning |
2831 |
Using internal time server |
The external time server could not be reached for synchronization. |
If your system is configured to use the internal time server, no action is required. Otherwise, check that network and time settings are correct. |
Notice |
2832 |
Using external time server |
The external time server was successfully contacted for synchronization. |
No action is required. |
Notice |
2833 |
Lost connection to external time server |
The external time server could not be contacted for synchronization. |
Check that network and time settings are correct. |
Notice |
2834 |
System time changed due to resynchronization with external time server |
When HCP started, the system time was resynchronized to an external time server because the system time was off by more than 1000 seconds. This time change may affect object retention. |
Check that network and time settings are correct. |
Warning |
2835 |
Battery backup unit failed |
A battery backup unit sensor is reporting that a BBU has failed. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2836 |
Battery backup unit restored |
A battery backup unit sensor is reporting that a BBU has returned to a fully functional state. |
No action is required. |
Notice |
2837 |
Battery backup unit degraded |
A battery backup unit sensor is reporting that the BBU is degraded. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2843 |
Front-end Ethernet communication error |
A network switch may have become unavailable. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2844 |
Front-end Ethernet communication restored |
The front-end Ethernet interface has returned to a normal state. |
No action is required. |
Notice |
2845 |
Network interface degraded |
Either the network interfaces in a bonded network interface are not operating at the same speed, or they are not operating at the requested speed. |
Check that the hardware is functioning properly. If the problem persists, contact your authorized service provider. |
Error |
2846 |
Network interface recovered |
A network interface is now operating correctly. |
No action is required. |
Notice |
2847 |
Network interface not functioning properly |
Either a network interface is missing, or a network interface exists on a node with no IP address assigned. |
Check that the physical network is functioning properly. If it is, try resetting the network. If the problem persists, contact your authorized service provider. |
Error |
2848 |
Network interface recovered |
A network interface is now operating correctly. |
No action is required. |
Notice |
2849 |
Network interface degraded |
A network interface is not operating at the requested MTU. |
Check that the hardware is functioning properly. If it is, try resetting the network. If the problem persists, contact your authorized service provider. |
Error |
2850 |
Network interface recovered |
A network interface is now operating correctly. |
No action is required. |
Notice |
2851 |
Front-end IPv6 communication error |
A network switch may have become unavailable, or IPv6 may not be functioning on the indicated interface. |
Check that the hardware is functioning properly. If a problem exists, contact your authorized service provider. |
Error |
2852 |
Front-end IPv6 communication restored |
IPv6 communication through the indicated front-end Ethernet interface has been restored. |
No action is required. |
Notice |
2853 | High load alarm | The node is experiencing a heavy load. | Please contact your authorized HCP service provider. | Notice |
2854 | High load alarm removed | The node is no longer experiencing a heavy load. | No action is required. | Notice |
2855 | Insufficient quantity of RAM installed | A node with an insufficient quantity of RAM for this software version may result in performance degradation and node failures. | Install the recommended amount of RAM on this node. | Warning |
2856 | Sufficient quantity of RAM installed | The node has the recommended amount of RAM installed. | No action is required. | Notice |
2857 | Disk swap alarm | The node is experiencing a high rate of page swapping. | Please contact your authorized HCP service provider. | Notice |
2858 | Disk swap alarm removed | The node is no longer experiencing a high rate of page swapping. | No action is required. | Notice |
2860 | SSD RAID rebuilding | SSD RAID is rebuilding. | No action is required | Warning |
2861 | SSD storage capacity warning | The amount of free SSD storage on the HCP storage nodes is low. | Please contact your authorized HCP service provider. | Warning |
2862 | SSD storage capacity critical | The amount of free SSD storage on the HCP storage nodes is critically low. | Please contact your authorized HCP service provider. | Error |
2910 | Retention class missing | HCP system detected a missing retention class. | Contact your authorized service provider. | Error |
3000 |
System updated |
HCP system properties have been updated. |
No action is required. |
Notice |
3001 |
Tenant created |
A user created a tenant. |
No action is required. |
Notice |
3002 |
Tenant updated |
A user updated a tenant. |
No action is required. |
Notice |
3003 |
Tenant deleted |
A user deleted a tenant. |
No action is required. |
Notice |
3007 | Namespace purged | A user purged a namespace. | No action is required. | Notice |
3026 |
Tenant over soft quota |
The amount of storage used by all namespaces owned by a tenant exceeds the soft quota configured for the tenant. |
Contact the tenant administrator about increasing the hard quota for the tenant. |
Warning |
3027 |
Tenant under soft quota |
The amount of storage used by all namespaces owned by a tenant is under the soft quota configured for the tenant. |
No action is required. |
Warning |
3029 |
Installed new HCP version |
A new version of the HCP software was successfully installed. |
No action is required. |
Notice |
3030 |
Tenant at namespace quota |
The number of namespaces owned by the tenant is equal to the namespace quota for the tenant. |
No action is required. |
Warning |
3031 |
Tenant over namespace quota |
The number of namespaces owned by the tenant is greater than the namespace quota for the tenant. |
Either increase the namespace quota for the tenant or have the tenant administrator delete one or more namespaces. |
Warning |
3034 |
Namespace maximum reached |
The current number of namespaces is the maximum allowed for the HCP system. |
No action is required. |
Warning |
3035 |
Namespace maximum exceeded |
The current number of namespaces is greater than the maximum allowed for the HCP system. |
Have the administrators for one or more tenants delete one or more namespaces to reduce the total number of namespaces to at or below the maximum allowed for the HCP system. |
Warning |
3036 |
Username conflict |
The indicated tenant has multiple user accounts with the same name. For any given tenant, all user accounts must have a unique username. |
Have the administrator for the tenant rename one account or merge duplicate accounts together. |
Warning |
3038 | Minimum data access permissions updated | The minimum data access permissions for a namespace have been updated. | No action is required. | Notice |
3500 |
Running migration |
The Migration service has begun migrating data. |
No action is required. |
Notice |
3501 |
Migration complete |
The Migration service has completed the data migration. |
To remove the decommissioned hardware, contact your authorized service provider. |
Notice |
3502 |
Pausing migration |
A user paused the data migration. |
No action is required. |
Notice |
3503 |
Preparing migration |
The Migration service has begun preparing to migrate data. |
No action is required. |
Notice |
3504 |
Verifying migration |
The Migration service has begun verifying the data migration. |
No action is required. |
Notice |
3505 |
Migration service stopped |
The Migration service is no longer running. |
No action is required. |
Notice |
3506 |
Migration service performance level updated |
A user changed the Migration service performance level. |
No action is required. |
Notice |
3507 |
Migration description updated |
A user changed the migration description. |
No action is required. |
Notice |
3509 |
Migration service: irreparable object or object part |
The Migration service was unable to migrate an object or object part and has marked it irreparable. |
Contact your authorized service provider. |
Error |
3510 |
Pausing migration |
The Migration service automatically paused the data migration because the HCP system does not have enough available space for the objects being migrated. |
Contact your authorized service provider. |
Error |
3511 |
Error completing migration |
The Migration service encountered an unrecoverable error while trying to complete the data migration. |
Contact your authorized service provider. |
Error |
4106 |
Ingest-time override setting has been changed |
The ingest-time override setting was changed. |
No action is required. |
Warning |
4107 |
Chassis communication error |
HCP cannot communicate with the indicated chassis through SNMP. |
Check network connectivity to the chassis. Also check that the chassis is configured to accept SNMP requests from the lowest-numbered available storage node in the HCP system. |
Error |
4108 |
Communication from unknown node |
Nodes from another HCP system were detected on the network. |
Check the back-end network. A back-end network can support only one HCP system. |
Error |
4109 |
Communication from node at previous version |
Nodes from another HCP version were detected on the network, and no upgrade is in process. |
Check the back-end network. A back-end network can support only one HCP system. |
Error |
4110 |
Metadata query engine indexing started |
A user enabled metadata query engine indexing. |
No action is required. |
Notice |
4111 |
Metadata query engine indexing stopped |
A user disabled metadata query engine indexing. |
No action is required. |
Warning |
4112 |
Metadata query engine is available |
The metadata query engine is running on the indicated node. |
No action is required. |
Notice |
4113 |
Metadata query engine is not available |
The metadata query engine is not running on the indicated node. As a result, the query API is unavailable for object-based queries. If the Search Console is using the query engine, searching through the Console is also unavailable. |
No action is required. If this situation persists, contact your authorized service provider. |
Warning |
4116 |
Metadata query engine index capacity warning |
The size of the metadata query engine index has reached a warning threshold. |
Increase the maximum size allowed for the metadata query engine index. |
Warning |
4117 |
Metadata query engine index capacity error |
The size of the metadata query engine index has reached an error threshold. |
Increase the maximum size allowed for the metadata query engine index. |
Error |
4118 |
Metadata query engine index capacity reached |
The size of the metadata query engine index has reached the maximum threshold. |
Increase the maximum size allowed for the metadata query engine index. |
Error |
4119 |
Metadata query engine index partially unavailable |
Part of the metadata query engine index is unavailable due to one or more logical volumes being unavailable. Indexing is temporarily paused, and queries cannot be serviced. |
Make the unavailable logical volumes available. Alternatively, rebuild the index by first deleting it and then reenabling indexing. Note that rebuilding the index can take a significant amount of time. |
Error |
4120 |
Metadata query engine out of memory for indexing |
No more memory is available for metadata query engine indexing. Indexing was automatically disabled. |
Add memory to the system by adding nodes or upgrading existing nodes. Then reenable metadata query engine indexing. |
Error |
4129 | Objects in namespace could not be replicated; will retry later | One or more objects could not be replicated. Another attempt to replicate these objects will be made later. | Monitor the remote system to see whether these objects are eventually replicated. If the objects are not replicated within one week, contact your authorized service provider. | Warning |
4200 |
RAID group spun down |
A RAID group was spun down. |
No action is required. |
Notice |
4201 |
RAID group spun up |
A RAID group was spun up. |
No action is required. |
Notice |
4202 |
Error spinning down RAID group |
An error occurred while spinning down a RAID group. |
Contact your authorized service provider. |
Error |
4203 |
Error spinning up RAID group |
An error occurred while spinning up a RAID group. |
Contact your authorized service provider. |
Error |
4204 |
Back-end switch communication failure |
A back-end switch is not communicating with HCP. |
Check that the switch is functioning properly. If the problem persists, contact your authorized service provider. |
Error |
4205 |
Back-end switch failure |
A back-end switch is reporting a problem. |
Check that the switch is functioning properly. If the problem persists, contact your authorized service provider. |
Error |
4206 |
Back-end switch restored |
A back-end switch is reporting a return to a functional state. |
No action is required. |
Notice |
4207 |
Objects read from spindown storage |
For the indicated tenant, one or more clients read objects from spindown storage. |
Ensure that the service plan in use is appropriate for the data usage pattern. |
Notice |
4208 |
Objects read from spindown storage |
For the indicated namespace, one or more clients read objects from spindown storage. |
Ensure that the service plan in use is appropriate for the data usage pattern. |
Notice |
4209 |
Time server changed |
A user changed the time server for the HCP system. |
No action is required. |
Notice |
4210 |
Current time changed |
A user changed the current time for the HCP system. |
No action is required. |
Notice |
4211 |
Time zone changed |
A user changed the time zone for the HCP system. |
No action is required. |
Notice |
4212 |
Service plan created |
A user created a service plan. |
No action is required. |
Notice |
4213 |
Service plan updated |
A user updated a service plan. |
No action is required. |
Notice |
4214 |
Service plan deleted |
A user deleted a service plan. |
No action is required. |
Notice |
4215 |
Failover completed |
A node in a cross-mapped pair became unavailable. The other node in the pair has finished taking over management of the logical volumes previously managed by the unavailable node. |
No action is required. |
Warning |
4216 |
Failback started |
A previously unavailable node in a cross-mapped pair has become available again and has begun the process of taking back management of its logical volumes from the other node in the pair. |
No action is required. |
Warning |
4217 |
Failback completed |
A node in a cross-mapped pair has finished taking back management of its logical volumes, which had previously failed over to the other node in the pair. |
No action is required. |
Notice |
4218 |
Monitored component added |
A user added a monitored component. |
No action is required. |
Notice |
4219 |
Monitored component deleted |
A user deleted a monitored component. |
No action is required. |
Notice |
4221 |
Tenant tags updated |
A user updated the tags for a tenant. |
No action is required. |
Notice |
4222 |
Time settings compliance mode changed |
A user changed the time settings compliance mode for the HCP system. |
No action is required. |
Notice |
4223 |
Failover completed |
A node in a cross-mapped pair became unavailable. The other node in the pair has finished taking over management of the logical volumes previously managed by the unavailable node. |
No action is required. |
Warning |
4224 |
Failback started |
A previously unavailable node in a cross-mapped pair has become available again and has begun the process of taking back management of its logical volumes from the other node in the pair. |
No action is required. |
Notice |
5000 | Time is unsynchronized between nodes | The HCP system detected an issue while checking the times on the nodes. | Contact your authorized service provider. | Warning |
5100 |
Network created |
A user created a network. |
No action is required. |
Notice |
5101 |
Network updated |
A user updated a network. |
No action is required. |
Notice |
5102 |
Network deleted |
A user deleted a network. |
No action is required. |
Notice |
5103 |
Network alias created |
A user created a network alias. |
No action is required. |
Notice |
5104 |
Network alias updated |
A user updated a network alias. |
No action is required. |
Notice |
5105 |
Network alias deleted |
A user deleted a network alias. |
No action is required. |
Notice |
5106 |
Network IP address assigned to node |
A user assigned a network IP address to a node. |
No action is required. |
Notice |
5107 |
Node IP address changed |
A user changed a network IP address for a node. |
No action is required. |
Notice |
5108 |
Network IP address removed from node |
A user removed a network IP address from a node. |
No action is required. |
Notice |
5109 |
Network reset |
A user reset a network. |
No action is required. |
Notice |
5110 |
Domain created |
A user created a domain. |
No action is required. |
Notice |
5111 |
Domain deleted |
A user deleted a domain. |
No action is required. |
Notice |
5112 |
Network status changed |
The status of a network changed due to one or more node IP addresses being added or removed. |
No action is required. |
Notice |
5113 |
Replication network changed |
A user chose a new replication network. |
No action is required. |
Notice |
5114 |
Domain renamed |
A user renamed a domain. |
No action is required. |
Notice |
5115 |
Objects read from external storage |
For the indicated tenant, one or more clients read objects from external storage. |
Ensure that the service plan in use is appropriate for the data usage pattern. |
Notice |
5116 |
Objects read from external storage |
For the indicated namespace, one or more clients read objects from external storage. |
Ensure that the service plan in use is appropriate for the data usage pattern. |
Notice |
5117 |
System IP mode updated |
A user updated advanced network settings. |
No action is required. |
Notice |
5118 |
Virtual network management updated |
A user updated advanced network settings. |
No action is required. |
Notice |
5119 |
Failure accessing cloud storage |
The HCP system encountered errors while accessing cloud storage. |
Check network connectivity to the cloud storage. Also check account credentials and permissions. |
Warning |
5120 |
Service plans created during upgrade |
New retired service plans were created during upgrade to satisfy namespace DPL requirements. |
Review your service plans. |
Notice |
5121 |
Running retirement |
The retirement service has begun storage volume retirement. |
No action is required. |
Notice |
5122 |
Retirement service performance level updated |
A user changed the retirement service performance level. |
No action is required. |
Notice |
5123 |
Pausing retirement |
A user paused the retirement service. |
No action is required. |
Notice |
5124 |
Retirement service off |
The retirement service is no longer running. |
No action is required. |
Notice |
5125 | HCP S Series Node warning message received | The component may not be functioning correctly. | Check that the HCP S Series Node is functioning properly. If a problem exists, contact your authorized service provider. | Warning |
5126 | HCP S Series Node error message received | The component may not be functioning correctly. | Check that the HCP S Series Node is functioning properly. If a problem exists, contact your authorized service provider. | Error |
5127 | Downstream DNS mode updated | A user updated downstream DNS mode. | No action is required. | Notice |
5128 | DNS server configuration reverted to BASIC Downstream DNS mode configuration. | System detected invalid DNS server configuration at reboot and reverted to BASIC Downstream DNS mode configuration. | Verify that Downstream DNS configuration for all front-end networks is correct. | Error |
5129 | Failure accessing cloud storage | The HCP system encountered errors while accessing cloud storage. | Check network connectivity to the cloud storage. Also check account credentials and permissions. | Warning |
5130 | Storage retirement canceled | A user canceled a storage retirement operation. | No action is required. | Notice |
5200 |
Default protocol optimization setting updated |
A user updated the default protocol optimization setting. |
No action is required. |
Notice |
5201 |
Namespaces optimized |
A user optimized namespaces for cloud protocols. |
No action is required. |
Notice |
5301 | Storage space reclamation failed | Error encountered during trimming operation | Check that the data LUNs support trimming and are configured properly. | Warning |
5400 | Erasure coding topology created | A user created an erasure coding topology. | No action is required. | Notice |
5401 | Erasure coding topology updated | A user updated an erasure coding topology. | No action is required. | Notice |
5402 | Erasure coding topology deleted | An erasure coding topology has been deleted. | If this event is unexpected, contact your authorized service provider. | Notice |
5403 | Erasure coding topology protection status changed | Some or all of the tenants in the erasure coding topology are not replicating to all systems in the topology. | Check the status of the replication links in the erasure coding topology. | Error |
5404 | Erasure coding topology protection status changed | An additional replication link failure could result in some or all tenants not replicating to all systems in the erasure coding topology. | Check the status of the replication links in the erasure coding topology. | Warning |
5405 | Erasure coding topology protection status changed | All tenants in the erasure coding topology are now replicating to all systems in the topology. | No action is required. | Notice |
5406 | Erasure coding topology read status changed | Erasure-coded objects in the erasure coding topology cannot be read. | Check the status of the replication links in the erasure coding topology. | Error |
5407 | Erasure coding topology read status changed | An additional replication link failure could result in the inability to read erasure-coded objects. | Check the status of the replication links in the erasure coding topology. | Warning |
5408 | Erasure coding topology read status changed | Erasure-coded objects in the erasure coding topology can now be read. | No action is required. | Notice |
5409 | Replication paused for tenant in erasure coding topology | The erasure coding topology includes a tenant for which replication was paused either automatically or by a user. | Resume replication of the tenant. | Warning |
5410 | Replication paused for tenants in erasure coding topology | The erasure coding topology includes tenants for which replication was paused either automatically or by a user. | Resume replication of the tenants. | Warning |
5411 | Replication no longer paused for tenants in erasure coding topology | All tenants in the erasure coding topology are now replicating. | No action is required. | Notice |
5412 | Erasure coding topology replication link not found | A replication link in the erasure coding topology could not be found. | Recover the missing replication link. | Error |
5413 | Erasure coding topology replication links not found | Replication links in the erasure coding topology could not be found. | Recover the missing replication links. | Error |
5414 | Erasure coding topology replication links no longer missing | All missing links in the erasure coding topology were recovered. | No action is required. | Notice |
5415 | Tenant in erasure coding topology not on replication link | A tenant was not automatically added to a replication link in the erasure coding topology. | Add the tenant to the replication link. | Error |
5416 | Tenants in erasure coding topology not on replication link | Tenants were not automatically added to a replication link in the erasure coding topology. | Add the tenants to the replication link. | Error |
5417 | Tenants added to erasure coding topology replication link | All tenants in the erasure coding topology are on the replication link. | No action is required. | Notice |
6001 | Replication verification setting changed | Replication verification setting was changed |
No action is required. |
Notice |
6002 |
Replication verification run complete |
Replication verification run completed successfully. | No action is required. | Notice |
6003 | Nonreplicating object | An object could not be replicated because it is open, irreparable, or unavailable. | Contact your authorized service provider. | Error |
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.