Skip to main content
Hitachi Vantara Knowledge

Overview page alerts

The System Management Console uses system health icons for alerts that appear on the Overview page. These alerts are described in the following table. The alerts are listed alphabetically by their hover text.

  • Abnormal temperature

    GUID-BD512ED3-8789-401D-A100-80AFF5A74BED-low.png

    IPMI sensors are detecting one or more nodes with temperature readings outside the recommended range.

  • Abnormal voltage

    GUID-7D7A553A-F7F9-454D-9896-532FA6C2078E-low.png

    IPMI sensors are detecting one or more nodes with voltage readings outside the recommended range.

  • Active Directory certificates expire soon

    GUID-53115CEA-7AB7-4F4E-8D67-C05EEE838404-low.png

    One or more AD SSL certificates will expire within 90 days. If a certificate expires, communication with AD may fail.

    To ensure that communication with AD is not disrupted, export a new SSL certificate from AD and upload it to HCP.

  • Active Directory certificates expire soon

    GUID-439E7235-9F21-4789-A4F2-B2283B739693-low.png

    One or more AD SSL certificates will expire within 30 days. If a certificate expires, communication with AD may fail.

    To ensure that communication with AD is not disrupted, export a new SSL certificate from AD and upload it to HCP.

  • Active Directory secure connection issue

    GUID-6CE483B4-5A75-42A9-95FF-C7408C7E7EC2-low.png

    HCP could not communicate with AD due to a problem with the AD SSL server certificate uploaded to HCP.

    Make sure that you have the correct certificate. Then upload the certificate again on the Active Directory page in the HCP System Management Console.

    If the problem persists, contact your authorized HCP service provider.

  • AD credentials invalid

    GUID-75209176-7E36-49D4-AE3D-0B9D8C534BF8-low.png

    The credentials for the HCP computer account used to query AD for groups are invalid. Reconfigure support for AD on the Active Directory page in the HCP System Management Console.

    The recommended procedure is to specify an HCP computer account that does not already exist in AD, thereby allowing the account to be created automatically.

  • AD partially configured

    GUID-5DCAB35E-3E50-4A6A-8EF3-C88DA286083A-low.png

    AD authentication is enabled only for the default namespace and is not currently supported for HCP namespaces. This can happen after an upgrade, where the CIFS protocol was enabled for the default namespace with AD authentication before the upgrade occurred.

    To enable support for AD for HCP namespaces, enable HCP support for AD on the Active Directory page in the HCP System Management Console.

  • All metadata is intact

    GUID-33A8F784-B26C-48E0-A9DB-DE4C4068CB96-low.png

    HCP policies have found no problems with object metadata.

  • All objects are intact

    GUID-2C528E0F-C55F-410B-B349-D15762E72D92-low.png

    HCP services have found no problems with object data.

  • All operation-types operations are disabled

    GUID-08E48519-748B-4CF3-917A-A624DF5E8C7B-low.png

    The indicated types of operations are currently not allowed. This alert appears when any permissions are disabled in the systemwide permission mask.

  • An unrecoverable error has occurred

    GUID-24E6AB75-4925-48C2-A3BC-04E101F890B6-low.png

    HCP is experiencing a problem it cannot fix by itself.

    Contact your authorized HCP service provider.

  • Authentication of HDDS user failed

    GUID-14AE2153-240B-4D7F-89A8-ED9937C6CE7C-low.png

    HDDS cannot validate the username and password specified for the HDDS search facility statistics user.

    On the Search page in the HCP System Management Console, specify valid credentials for an HDDS user account in the Administrator group.

    This alert appears only while the HDDS search facility is enabled.

  • Back-end switch error

    GUID-863FD3B7-84D7-41FF-AE64-D39F35B79A1E-low.png

    One or more back-end switches are not operating normally. contact your authorized HCP service provider.

  • BBU charging

    GUID-A078909C-1748-4765-A331-708598AE53D3-low.png

    For RAIN systems only, the battery backup unit in one or more nodes is charging.

  • BBU degraded; charging

    GUID-F1BD1E10-1585-4284-AD57-26765C4DD8DB-low.png

    For RAIN systems only, the battery backup unit in one or more nodes is charging.

    The write-cache is disabled on those nodes.

  • BBU degraded; discharging

    GUID-BCACDFD1-C27D-4075-A0FE-C2D80AFB106B-low.png

    For RAIN systems only, the battery backup unit in one or more nodes is discharging.

    The write-cache is disabled on those nodes.

  • BBU discharging

    GUID-AEB1DBE8-C676-431A-A024-5D36AEED90F5-low.png

    For RAIN systems only, the battery backup unit in one or more nodes is discharging.

  • BBU failed

    GUID-2A0D98B9-E191-4AC7-9BA9-1FB7B0743601-low.png

    For RAIN systems only, the battery backup unit in one or more nodes has failed.

    The write-cache is disabled on those nodes.

    If this alert appears for more than a few hours, contact your authorized HCP service provider.

  • BBU in learn cycle

    GUID-D29D4548-3754-404F-BE43-C67B81DB18C5-low.png

    For RAIN systems only, the battery backup unit in one or more nodes is in a learn cycle.

    System performance may be temporarily degraded.

  • Below metadata protection level. Repairing...

    GUID-9539D49C-FBC8-482A-B738-AE0063FAA716-low.png

    Primary running storage contains too few copies of metadata for one or more objects.

    The ingest tier metadata DPL defined for the namespace that contains each object is higher than the number of copies of metadata for that object currently found in primary running storage.

    The Protection service is in the process of repairing this problem.

  • Broken fan

    GUID-ABFFEAF7-AED1-4034-8F12-B594EB972692-low.png

    IPMI sensors are detecting one or more nodes or CB 320 server chassis with fan speeds outside the recommended range.

  • Cannot access Key Distribution Center

    GUID-CB80874A-6572-47E1-965A-F12740AC1ED3-low.png

    HCP cannot access the Key Distribution Center in the AD domain specified in the HCP AD configuration.

    Check that both the AD domain controller and the network connection between HCP and that server are healthy.

    If they both appear to be working properly, contact your authorized HCP service provider.

  • Cannot access LDAP server

    GUID-0B131FEE-680E-47EA-B829-BFF760C907C1-low.png

    HCP cannot access the LDAP server for the AD domain specified in the HCP AD configuration.

    Check that both the LDAP server and the network connection between HCP and that server are healthy.

    If they both appear to be working properly, contact your authorized HCP service provider.

  • Cannot communicate with chassis

    GUID-A6C7E77C-738F-400E-99AB-183065473D13-low.png

    The storage node specified in the CB 320 server chassis configuration cannot communicate with one or more chassis. Ensure that the chassis configuration is correct.

    If it is, contact your authorized HCP service provider.

  • Cannot connect to AD server

    GUID-742B6C59-EC29-4350-8BFA-11DC797A7D74-low.png

    HCP cannot connect to the server for the AD domain specified in the HCP AD configuration.

    Make sure both the AD domain controller and the network connection between HCP and that server are healthy. Also make sure that AD is correctly configured in your DNS.

    If the problem persists, contact your authorized HCP service provider.

  • CIFS AD access disabled

    GUID-3CFE5CCE-E7F4-4468-97D8-F7656D6CECC3-low.png

    One of these conditions is true:

    • The SPN attribute for one or more HCP nodes is missing from the AD domain.
    • An internal error with the CIFS protocol occurred on one or more HCP nodes. In either case, reconfigure HCP support for AD on the Active Directory page in the HCP System Management Console.
    If the problem persists, contact your authorized HCP service provider.
  • CIFS/NFS limit exceeded

    GUID-4BBAE438-F96B-4944-B9B8-6FCB29085D2B-low.png

    The number of namespaces with the CIFS or NFS protocol enabled is above the maximum supported by HCP. System performance may be slower as a result.

    If this is an issue, ask one or more tenant administrators to disable CIFS and NFS for one or more of their namespaces.

  • CIFS/NFS limit reached

    GUID-74BD11C7-8444-499C-AD76-8825BC4A1D8C-low.png

    The number of namespaces with the CIFS or NFS protocol enabled is at the maximum supported by HCP.

    Enabling CIFS or NFS for additional namespaces may slow system performance.

  • Conflicting CIFS settings detected

    GUID-24AB97BB-0A14-48C4-A3D8-4525DBECB77F-low.png

    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.

  • Content verification repair disabled

    GUID-FD397FFD-3465-48A2-AF08-B2F7B0132858-low.png

    The Content Verification service is currently not checking for or repairing objects with corrupted data.

    This alert appears when Do not check and repair objects is selected on the Content Verification page.

  • Data access failover

    GUID-093B26F1-A998-4A9B-9FCE-51928185BFAF-low.png

    For SAIN systems with zero-copy failover enabled, a node has taken over management of storage normally managed by another node. contact your authorized HCP service provider.

  • Degraded network assigned

    GUID-23A9CEF1-FB08-45DE-9F2F-AB96622F2E8B-low.png

    One or more tenants are associated with a degraded network for management or data access purposes. A degraded network presents a single point of failure for clients accessing HCP over that network.

    Check the Networks page for degraded networks that are associated with tenants. Then reconfigure each network to assign IP addresses to one or more additional nodes.

  • Empty network assigned

    GUID-F8B15E6F-4FC6-4A0D-B1D4-871E87CCB14A-low.png

    One or more tenants are associated with an empty network for management or data access purposes.

    A tenant with an empty management network cannot be accessed through the Tenant Management Console or HCP management API.

    Namespaces belonging to a tenant with an empty data access network are inaccessible.

    Check the Networks page for empty networks that are associated with tenants. Then reconfigure each network to assign IP addresses to one or more nodes.

  • Erasure coding error

    GUID-407A3B57-874D-44F4-B42F-FEAAE4A230AB-low.png

    One or more of these conditions exist:

    • The protection status of the active erasure coding topology is broken.
    • The read status of an erasure coding topology is broken.
    • One or more tenants added to an erasure coding topology have not been added to one or more replication links in the topology. HCP does not report this condition for a tenant until ten minutes after the tenant was added to the topology.
    • HCP cannot find one or more replication links that are included in an erasure coding topology.
  • Erasure coding warning

    GUID-94C99E31-4CD9-4400-B093-F0E4C7207FC3-low.png

    One or more of these conditions exist:

    • The protection status of the active erasure coding topology is vulnerable.
    • The read status of an erasure coding topology is vulnerable.
    • Replication is paused for one or more tenants on one or more replication links in the active erasure coding topology.
    • The Geo-distributed Erasure Coding service is not in the active service schedule. New erasure coding activity is limited.
    • The Geo-distributed Erasure Coding service is disabled. New erasure coding activity is limited.
  • Error spinning down volume

    GUID-BFF34A43-C82E-4C0C-A58F-429652BDF9C4-low.png

    An error occurred while a logical volume was in the process of spinning down. contact your authorized HCP service provider.

  • Error spinning up volume

    GUID-09CB78D7-1A6D-4983-A85D-2CD5CAE8AE58-low.png

    An error occurred while a logical volume was in the process of spinning up. contact your authorized HCP service provider.

  • Expired Active Directory certificates

    GUID-2CB44ACB-CFF1-4DC8-A5E0-AEEA437FE342-low.png

    One or more AD SSL certificates have expired. Communication with AD may fail.

    To make sure communication with AD is not disrupted, export a new SSL certificate from AD and upload it to HCP.

  • Expired replication certificates

    GUID-4D91972B-2E72-4BD8-BFE4-87CFBE8232E0-low.png

    One or more trusted replication server certificates have expired. Replication with the systems from which the applicable certificates were obtained has stopped.

    When the other system in any of the applicable replication pairs installs a new SSL server certificate, download that certificate and upload it to this system as a trusted replication server certificate.

    For ease of maintenance, delete expired certificates from the list of trusted replication server certificates.

  • Expired SSL server certificate

    GUID-23FEA458-01C8-4358-B409-18D0C99494CC-low.png

    One or more SSL server certificates for one or more HCP domains have expired.

    If a domain has no valid certificates, clients must accept the invalid certificate presented by HCP for access to namespaces in that domain.

    If the domain associated with the replication network has no valid certificates, replication fails.

    Check the Domains and Certificates page to see which certificates have expired. Then make sure each affected domain has at least one valid certificate.

  • External storage volumes unavailable

    GUID-763869C3-B61F-4A4E-B599-4C2613F469ED-low.png

    One or more external storage volumes have a status of unavailable, broken, or initializing. Check the Storage page to see which volumes are having problems. Then make sure the devices hosting those volumes and the network connections to those devices are functioning properly.

    Also make sure the exported shares are configured correctly, that any NFS servers being used are running on each device, and that any NFS security software on the device is not blocking access by any of the HCP nodes.

    If the problem persists for a volume, remount the volume in HCP. If that doesn’t resolve the problem, contact your authorized HCP service provider for help.

  • Front-end connection error

    GUID-5CCD0206-00E5-41DD-B18B-6CE22CF84402-low.png

    All front-end connections to one or more storage nodes are unavailable.

    If this system is currently a source for replication, some objects will not be replicated.

    If the system is a replication target, replication performance is degraded.

  • Full file system

    GUID-F0DF4E9E-94A2-4DC8-ABE9-9B6DAB89DD73-low.png

    One or more file systems have no more available space or no more available inodes. contact your authorized HCP service provider.

  • Hardware functioning properly

    GUID-2C985E0C-DBD9-4057-8ADD-EB2C069B2FC2-low.png

    All of the HCP hardware is functioning normally.

  • HCP computer account missing

    GUID-15E68E3F-33BE-4DE7-AF5B-1B551DAC3DBA-low.png

    The HCP computer account is missing from the AD domain.

    Reconfigure HCP support for AD on the Active Directory page in the HCP System Management Console.

  • HCP upgrade is in progress

    GUID-13F8B4C0-D155-4540-B938-151B9348B64C-low.png

    The HCP software is being upgraded to a new release with the HCP system online (that is, without shutting down the system).

  • HDDS connection failure

    GUID-81443B3D-5BC9-476A-8E33-0478E4E88F89-low.png

    HCP cannot connect to the HDDS server.

    Make sure both the HDDS server and the network connection between HCP and that server are healthy.

    If both appear to be working properly, contact your authorized HCP service provider.

    This alert appears only while the HDDS search facility is enabled.

  • High load or swap

    GUID-0CB761BD-E3F3-4B8C-82A8-74FE83EB298D-low.png

    One or more nodes are experiencing a heavy load or a high rate of page swapping. contact your authorized HCP service provider.

  • IP mode mismatch

    GUID-591BE0C6-30D2-4291-B293-D13EC371574C-low.png

    The system-level front-end network IP mode is Dual, but the [hcp_system] network is configured to use only IPv4 addresses or only IPv6 addresses.

    Submit a request to your authorized service provider to set the system-level IP mode and set the [hcp_system] network IP mode, to provide support only for the type(s) of IP address you want to configure for user-defined networks.

  • Last HDvM update failed

    GUID-071E0825-369F-4ACC-9CBB-5766F2E0AF5A-low.png

    The most recent attempt to push information to Hitachi Device Manager was unsuccessful. For details, check the HDvM page.

  • Maximum namespaces exceeded

    GUID-D3BFA1F6-F51E-4A0E-BF23-7F82AE2BCB5A-low.png

    The number of namespaces defined in the HCP system is greater than the maximum number allowed.

    This situation can happen if one or more HCP tenants being replicated to a given HCP system have namespace quotas on their source systems that cause the total number of allocated namespaces on the target system to exceed the number allowed for an HCP system.

    While these tenants are included in their respective replication links, neither the actual number of namespaces they own nor their quotas count on the target system.

    However, if one or more of the tenants are removed from their links, the namespaces and quotas for those tenants then count on the target system. This can result in the total number of namespaces defined on the target system exceeding the total allowed for the system.

    To ensure proper system operation, if the maximum number of namespaces allowed for the system is exceeded, you should lower the number of namespaces as soon as possible. To do this, one or more tenant administrators must delete one or more of their namespaces.

  • Maximum namespaces reached

    GUID-CBFC86F3-9641-4A5A-A85F-8581F8E58D6D-low.png

    The number of namespaces defined in the HCP system is the maximum number allowed.

  • Metadata balancing...

    GUID-EC301C8E-88AC-4ABF-839E-D0B397AB2DF5-low.png

    HCP is in the process of moving object metadata between nodes to achieve a more even distribution of the metadata.

  • Migration completing - balancing metadata

    GUID-302C88F5-409E-4322-93CB-881C842D025A-low.png

    The Migration service has completed the process of copying objects during a data migration and is now in the process of moving metadata between the remaining nodes to achieve a more even distribution of the metadata.

  • Migration in progress

    GUID-238D7298-03FF-4FB9-8658-63EE15D728EA-low.png

    A data migration is in progress.

  • MQE index at 50%

    GUID-693F408D-7CEE-4906-8DBB-2B5831DB3484-low.png

    The size of the metadata query engine index is 50 to less than 80 percent of either the maximum size allowed for the index or the actual space available for the index, whichever is less. HCP can no longer optimize the space used by the index.

    As the index grows, responses to metadata query engine API requests will become slower, as will responses to searches in the Search Console when that Console is using the metadata query engine. Consider adding more storage capacity for the metadata query engine index.

    If the index includes custom metadata, you can create more space for the index by deleting and then rebuilding the index with custom metadata indexing disabled.

  • MQE index at 80%; indexing disabled

    GUID-65C89D0D-E29C-4C25-A12B-17F575C55A87-low.png

    The size of the metadata query engine index is 80 percent or more of either the maximum size allowed for the index or the actual space available for the index, whichever is less.

    Metadata query engine indexing has stopped.

    To enable indexing to continue, add more storage capacity for the metadata query engine index.

    If the index includes custom metadata, you can create more space for the index by deleting and then rebuilding the index with custom metadata indexing disabled.

  • MQE index partially unavailable

    GUID-2DD1ACA0-B2FE-44EB-A3A4-D1E93F641C6C-low.png

    At least one part of the metadata query engine index is unavailable.

    As a result, indexing has stopped, the metadata query API does not support object-based queries, and, if the metadata query engine is selected for use with the Search Console, searches in that Console return an error.

    This status can appear, for example, while an index-enabled logical volume is unavailable. When the situation is resolved, indexing resumes automatically.

  • MQE indexing unavailable

    GUID-AF75AC44-8F36-4FF2-A7AB-E973131434C9-low.png

    Metadata query engine indexing is disabled due to insufficient memory.

    Increase the system memory either by adding storage nodes or by adding memory to existing storage nodes.

  • Multipath degraded to one

    GUID-5B30BE6E-997C-454A-8333-FDF39D4E560D-low.png

    For SAIN systems configured with multipathing, the physical connection between a node and the SAN storage has failed

    Contact your authorized HCP service provider.

  • Network error

    GUID-51D81386-1D71-484E-A4B4-46D0D3F5B010-low.png

    One or more nodes are experiencing problems with one or more of their networks. Possible causes for this alert include:

    • One or more physical network connections to one or more nodes are not working. Check the Storage Node page for each indicated node to see which network interfaces show errors. Then correct any problems with the applicable physical networks. If the networks appear to be working properly, contact your authorized HCP service provider.
    • One or more network interfaces are missing in one or more nodes. Check the Networks page to see which networks have this problem. Then restart those networks. If the problem persists, contact your authorized HCP service provider.
    • One or more nodes have one or more network interfaces for networks in which the nodes do not have IP addresses. Check the Networks page to see which networks have this problem. Then restart those networks. If the problem persists, contact your authorized HCP service provider.
  • Network warning

    GUID-D0C54ADA-A2D6-4D80-A63C-B54BD7D538D8-low.png

    One or more nodes are experiencing problems with one or more of their networks. Possible causes for this alert include:

    • The current MTU for one or more networks on one or more nodes does not match the configured MTU. If the problem is with a user-defined network, restart the network. If that doesn’t resolve the problem, reboot the applicable nodes. If the problem persists, contact your authorized HCP service provider.
    • The current speed of the [hcp_system] network on one or more nodes does not match the configured speed. contact your authorized HCP service provider. (This alert does not apply if the [hcp_system] network speed is set to auto.)
    • The current speed of the [hcp_backend] network on one or more nodes is not the maximum speed possible for that network. contact your authorized HCP service provider.
  • No external time server configured

    GUID-5CD701F0-F0BC-49FF-88F9-BF43F6DEACBD-low.png

    HCP is configured to use itself as a time server. For HCP to work with AD, HCP time must be within five minutes of AD time.

    The recommended configuration is for HCP and AD to use the same external time server.

  • No Key Distribution Center found

    GUID-3365EC7D-8102-431B-9961-D4FFA1E236C1-low.png

    HCP cannot find a Key Distribution Center for the AD domain specified in the HCP AD configuration. Ensure that AD is correctly configured in your DNS.

    If the problem persists, contact your authorized HCP service provider.

  • No LDAP server found

    GUID-15AFB13D-92B5-42AD-B6AA-726292306636-low.png

    HCP cannot find an LDAP server for the AD domain specified in the HCP AD configuration. Ensure that AD is correctly configured in your DNS.

    If the problem persists, contact your authorized HCP service provider.

  • Nonreplicating object detected

    GUID-D995AD63-CEEE-428D-83E8-EF21FCE920DB-low.png

    One or more nonreplicating objects have been detected. The objects have either remained in the open state for too long or are irreparable.

    If this occurs, contact your authorized HCP service provider.

  • OpenStack Identity Service connection failure

    GUID-92BF5CAD-898C-4793-BF6C-2A4B2B97D7F9-low.png

    HCP could not connect to the OpenStack Identity Service URL. This connectivity issue could be caused by your HCP or Keystone configuration.

    On the OpenStack page, make sure your OpenStack Identity Service is enabled, your Identity Service URL and Keystone credentials are correct, and that you’re using a domain name in your Identity Service URL instead of an IP address.

    If you’re using HTTPS, make sure you have a certificate for your Server Domain and that your current one has not expired.

  • Partial network assigned

    GUID-8DA66489-B6CF-40DD-8C4F-7A5EFFF33C4F-low.png

    One or more tenants are associated with a partial network for management or data access purposes. The load from client requests for access to those tenants or their namespaces is not being fully distributed across the nodes in the HCP system.

    Check the Tenants page to see which tenants have partial networks. Then either reconfigure each network to assign IP addresses to all nodes in the HCP system, or select different networks for the affected tenants.

  • Partial network assigned to replication

    GUID-F2C4B549-3CB0-4A2B-9BEF-193EDA20E136-low.png

    The network selected for replication is a partial network. The load from replication activity is not being fully distributed across the nodes in the system.

    Check the replication Settings page to see which network is selected for replication. Then either reconfigure that network to assign IP addresses to all nodes in the HCP system, or select a different network for replication.

  • Power supply failure

    GUID-3D9C89CC-ADA5-4D31-9ADC-900071CF3ED4-low.png

    One or more power supplies are not working on one or more nodes or CB 320 server chassis.

    Contact your authorized HCP service provider.

  • Processor failure

    GUID-EC722F16-CF50-4975-92C7-711A13083B24-low.png

    IPMI sensors are detecting one or more nodes with processors that are not working.

    Contact your authorized HCP service provider.

  • Regions per node is low

    GUID-2AFA8A62-8FB7-40E7-9167-360D02DB3CA1-low.png

    HCP storage management is currently not configured for optimal performance.

    To resolve this issue, contact your authorized HCP service provider.

  • Remote storage almost full

    GUID-12E14512-11B8-4275-80B0-27D891E027E0-low.png

    Primary running storage space on the remote system for a replication link is at least 90% used.

    Consider adding more primary running storage capacity to the remote system or changing storage tiering strategies on that system to create more space in the existing primary running storage.

    For an active/active link, this alert appears only in the System Management Console for the local system.

    For an active/passive link, this alert appears only in the System Management Console for the primary system.

  • Remote storage full (link suspended)

    GUID-C96E1670-4976-457C-9C08-9F358CF48151-low.png

    Primary running storage space on the remote system for a replication link is 94% used. The remote system cannot act on any more replication data transmissions from the local system.

    HCP has automatically suspended activity on the link

    Either add more primary running storage capacity to the remote system, or change storage tiering strategies on that system to create more space in the existing primary running storage. Then resume activity on the link.

    For an active/active link, this alert appears only in the System Management Console for the local system. For an active/passive link, this alert appears only in the System Management Console for the primary system.

  • Replication certificates expire soon

    GUID-EEEC3DAD-9D39-4B73-A5FF-32CAB9160A73-low.png

    One or more trusted replication server certificates will expire within 90 days. If a certificate expires, replication with the system from which the certificate was obtained will fail.

    To ensure that replication is not disrupted, when the other system in the replication pair installs a new SSL server certificate for the domain that’s associated with the replication network, download that certificate and upload it to this system as a trusted replication server certificate.

  • Replication certificates expire soon

    GUID-1FDCFFC9-299D-4548-B596-E2F538465F6E-low.png

    One or more trusted replication server certificates will expire within 30 days. If a certificate expires, replication with the system from which the certificate was obtained will fail.

    To ensure that replication is not disrupted, when the other system in the replication pair installs a new SSL server certificate for the domain that’s associated with the replication network, download that certificate and upload it to this system as a trusted replication server certificate.

  • Replication link failure

    GUID-29E8EF15-3CC5-4734-AC6F-A03D55B669F5-low.png

    An active/active or outbound active/passive replication link is not working as expected.

    Check the network connection between the two systems involved in the link. If the connection appears to be working properly, contact your authorized HCP service provider for help.

  • Replication link has autopaused tenants

    GUID-9D4EF451-95C9-4211-947B-18C76D104D75-low.png

    HCP has automatically paused replication of one or more HCP tenants.

    For each tenant, correct the situation that caused replication to be paused. Then resume replication of the tenant.

  • Replication link pending

    GUID-8D1635D7-FA69-4102-8D46-27320CAD9123-low.png

    Either the system has sent a request for a replication link to another system and is waiting for a response, or the system has received a request for a replication link and has not yet responded.

  • Replication link stalled

    GUID-E4CFC3B0-642D-4F33-B6C9-D172F81F6C97-low.png

    Replication has unexpectedly stopped on a replication link. Check the network connection between the two systems involved in the link.

    If the connection appears to be working properly, contact your authorized HCP service provider for help.

  • Replication links shut down

    GUID-BBC7E767-DBC1-44AF-B6D4-68446D266A89-low.png

    All replication links in which this system is involved are shut down.

    No replication or recovery activity is occurring on these links, and the links cannot be used for read-from-remote or object-repair purposes.

  • Reverse IP lookup failed for Key Distribution Center

    GUID-8457F430-651B-48C5-B21A-B46713DA58C2-low.png

    HCP was able to do a reverse IP lookup of an IP address used for communication with the primary AD domain controller for the Key Distribution Center.

    However, HCP was unable to do a reverse IP lookup of an IP address used for communication with another AD domain controller in the same domain or in another domain.

    For more information about the problem, go to the Active Directory page in theHCP System Management Console.

  • Reverse IP lookup failed for Key Distribution Center

    GUID-BAFA85E3-864A-47ED-A4C4-379AAF275E54-low.png

    HCP was unable to do a reverse IP lookup of an IP address used to communicate with the primary AD domain controller for the Key Distribution Center.

    For more information about the problem, go to the Active Directory page in the HCP System Management Console.

  • Reverse IP lookup failed for LDAP server

    GUID-CF9394A7-A36A-4D1B-86A9-33C9CBE177B5-low.png

    HCP was able to do a reverse IP lookup of an IP address used to communicate with the primary AD domain controller for the LDAP server.

    However, HCP was unable to do a reverse IP lookup of an IP address used to communicate with another domain controller in the same domain or in another domain.

    For more information about the problem, go to the Active Directory page in the HCP System Management Console.

  • Reverse IP lookup failed for LDAP server

    GUID-9C9C993D-0229-4BD5-89B9-11C75059B327-low.png

    HCP was unable to do a reverse IP lookup of an IP address used to communicate with the primary AD domain controller for the LDAP server.

    For more information about the problem, go to the Active Directory page in the HCP System Management Console.

  • S Series Balancing service is missing from current schedule

    GUID-E02FD4BC-9774-443C-9EF2-CA4C23BC2B49-low.png

    The S Series Balancing service is not included in the current schedule.

  • SSD RAID degraded

    GUID-2A2CEDCC-F1F4-41B4-BC41-5AFD148CCEF6-low.png

    An SSD is experiencing errors or has failed completely.

    Contact your authorized HCP service provider for help.

  • SSD RAID rebuilding

    GUID-EC735937-5698-4B19-8C3F-07C94EE1052F-low.png

    The SSD RAID volume is rebuilding. It cannot be accessed until the rebuild process is complete.

  • Single sign-on issue

    GUID-CA51C9DC-F7EF-4EBE-ABA5-173F81A48B65-low.png

    The SPN attribute for one or more tenants or namespaces is missing from the AD domain.

    If the HCP system is involved in replication, these tenants and namespaces could be defined in any system in the replication topology.

    For information about which tenants are involved, see the Status section on the Active Directory page in the HCP System Management Console.

    If the missing SPN attribute is for a namespace, have the administrator for the tenant that owns the namespace disable and reenable AD single sign-on for the namespace.

    If the missing SPN attribute is for a tenant, disable and reenable AD authentication for the tenant. If the issue is still not resolved, reconfigure HCP support for AD on the Active Directory page in the HCP System Management Console.

    If the problem persists, contact your authorized HCP service provider.

  • Some nodes not using the correct time source

    GUID-B9E3F44B-CCFF-4EB0-BFCF-995C1C64F9CD-low.png

    One or more nodes are using a time source other than what is configured for the system. That is, they are using internal time when external time is configured, or they are using external time when internal time is configured.

  • Spindown storage usage is percent used

    GUID-DA1C2F4F-F342-43FE-92FC-49AC3D38D40A-low.png

    For SAIN systems with spindown storage, spindown storage is less than 75 percent full.

  • Spindown storage usage is percent used

    GUID-20875BF9-3A4A-403B-A69C-D738DE2FD5F6-low.png

    For SAIN systems with spindown storage, spindown storage is 75 to less than 90 percent full. Consider adding more spindown storage capacity to the HCP system.

  • Spindown storage usage is percent used

    GUID-77CDE34F-3D18-4838-A821-BE0AB48960F8-low.png

    For SAIN systems with spindown storage, spindown storage is 90 or more percent full.

    HCP will not move any more objects to spindown storage until either objects are removed from spindown storage or spindown storage capacity is increased.

  • Storage Tiering service is missing from the current schedule

    GUID-5F2648FF-EC8F-4D3B-A252-BEC00D9357B9-low.png

    The HCP system includes the Storage Tiering service which should be, but is not scheduled. No objects will be moved to spindown or external storage.

  • SSL server certificate expires soon

    GUID-610627D5-0587-443E-84DF-57A6FDE14EA5-low.png

    One or more SSL server certificates for one or more HCP domains will expire within 90 days

    If a domain has no valid certificates, clients must accept the invalid certificate presented by HCP for access to namespaces in that domain.

    If the domain associated with the replication network has no valid certificates, replication fails.

    Check the Domains and Certificates page to see which certificates are expiring. Then make sure each affected domain has at least one certificate that will be valid when the expiring certificates expire.

  • SSL server certificate expires soon

    GUID-DD0A2B80-DB1E-433B-9817-E8E0FAFA9E82-low.png

    One or more SSL server certificates for one or more HCP domains will expire within 30 days.

    If a domain has no valid certificates, HTTPS access to namespaces in that domain is not allowed. If the domain associated with the replication network has no valid certificates, replication fails.

    Check the Domains and Certificates page to see which certificates are expiring. Then make sure each affected domain has at least one certificate that will be valid when the expiring certificates expire.

  • Storage device reporting errors

    GUID-2D598E6E-BC62-4667-A1CA-C7236B0F6986-low.png

    One or more physical drives are experiencing problems.

    Contact your authorized HCP service provider.

  • Storage license has expired

    GUID-C7261FBE-A2AE-4681-A145-45B9430E9153-low.png

    The storage license is past its expiration date and no longer valid.

    Contact HCP support to procure a new license.

  • Storage license is not a valid license for this system

    GUID-85534412-0F01-4F02-8304-A94AF27BEE6F-low.png

    The HCP system serial number does not match the serial number on the storage license. A new storage license must be uploaded with a matching serial number.

    Contact HCP support to procure a new license.

  • Storage usage is percent used

    GUID-B21C878C-089E-4284-B4E0-836033BF4996-low.png

    The storage managed by the storage nodes is less than 75 percent full.

    In a SAIN system with spindown storage, this value applies only to running storage.

  • Storage usage is percent used

    GUID-D769B1A2-7B7D-4EAE-B307-D03D7CECF3D1-low.png

    The storage managed by the storage nodes is 75 to less than 90 percent full. Consider adding more storage capacity to the HCP system.

    In a SAIN system with spindown storage, this value applies only to running storage.

  • Storage usage is percent used

    GUID-5490C5DE-4905-463F-8F74-5A8FC65FCDB5-low.png

    The storage managed by the storage nodes is 90 or more percent full.

    When storage usage is 95 or more percent full, HCP will not store any new objects or any new or replacement custom metadata. It will, however, continue to allow metadata changes.

    In a SAINsystem with spindown storage, this value applies only to running storage.

  • Default service plan DPL setting is 1

    GUID-4EAD9C5C-AD69-49D3-9483-9BBCBD1F0A3D-low.png

    For RAIN systems only, the ingest tier DPL defined for namespaces by the default service plan is 1 (one). To ensure that stored data is protected, all HCP namespaces that use the default service plan should be replicated.

    Additionally, if the default namespace uses the default service plan, all directories in that namespace should be replicated.

  • System is starting

    GUID-E2950380-E4C3-4060-B22F-36A0C686C572-low.png

    The HCP system is in the process of starting up.

  • Tenants inaccessible due to network configuration

    GUID-A0FF7759-4C72-4594-A477-9F8573BCBE75-low.png

    One or more tenants are associated with a network other than [hcp_system], but virtual network management is disabled. A tenant with a management network other than [hcp_system] cannot be accessed through the Tenant Management Console or HCP management API.

    Namespaces belonging to a tenant with a data access network other than [hcp_system] are inaccessible.

    This error can occur when tenants on an HCP system that has virtual network management enabled are replicated to a system that does not.

    To have virtual network management enabled, contact your authorized HCP service provider.

  • Tenants inaccessible due to network configuration

    GUID-D5C7DA96-37CB-4B0D-BE5D-8B50D2506F48-low.png

    One or more networks specified as the management or data access network for one or more tenants do not exist. A tenant with a nonexistent management network cannot be accessed through the Tenant Management Console or HCP management API.

    Namespaces belonging to a tenant with a nonexistent data access network are inaccessible.

    This error can occur on an HCP system that’s a replication target when a network defined on a source system is not defined on the target system.

    Check the Networks page for the list of nonexistent networks that are associated with tenants. For each listed network, create a network with the same name.

  • Time out of sync between replicating systems

    GUID-2EBD9A6D-D715-48EF-816D-9BDF5F3C2DFF-low.png

    The system time on this system is more than one minute out of sync with the system time on one or more other systems with which this system participates in a replication link.

    The recommended practice is to have all HCP systems in a replication topology use the same external time server.

  • Unavailable nodes

    GUID-4F269BD4-7FCA-470B-886F-D170B685FC03-low.png

    One or more nodes are unavailable.

    If the status of a node changes spontaneously from available to unavailable and the node does not restart automatically, contact your authorized HCP service provider.

    Do not try to restart the node manually, as that may cause the loss of information needed to diagnose the problem.

  • Unavailable objects

    GUID-823123C0-94B0-4C5C-8AE4-96FF791B0A2D-low.png

    One or more unavailable objects have been detected. These objects cannot be replicated until they are repaired.

    If the objects cannot be recovered, they become irreparable.

    If this occurs, contact your authorized service provider.

  • Usage has exceeded license capacity for the storage

    GUID-12729A9D-A7D4-474A-A64A-872331953EAE-low.png

    The storage capacity of the storage license has been exceeded.

    Contact HCP support to procure a new license.

  • Username mapping invalid

    GUID-7027090A-06B5-4CF1-A068-CB9BEC1C0CD6-low.png

    In the username mapping file used by the CIFS protocol for the default namespace, one or more usernames map to the same UID.

    Only one username can map to any given UID.

 

  • Was this article helpful?