Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

System Management Console alerts


The HCP System Management Console uses icons with hover text, called alerts, to provide high-level health status reports for specific elements of the HCP system and to identify problems that need your attention.

System Management Console alerts appear on the Overview, Hardware, Storage Node, Storage, Networks, Tenants, Domains and Certificates, and Authentication pages.

The System Management Console uses two types of alert icons:

System health icons — Indicate the current health of one or more elements of the HCP system, such as the metadata query engine or the power supplies for a storage node. These icons appear on the Overview, Hardware, Storage Node, Tenants, Domains and Certificates, and Active Directory pages. System health icons on the Overview, Storage Node, and Active Directory pages are also accompanied by text.

Error and warning icons — Indicate error and warning conditions related to one or more elements of the HCP system. This type of icon appears only when an error or warning condition exists. These icons appear on the Storage and Networks pages.

This appendix describes the alerts that can appear on the Console pages and tells you how to respond to alerts that indicate problems. The appendix does not list alerts pertaining to HCP S Series Nodes. For more information on those alerts, see HCP S Series Node Help.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

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 table below. The alerts are listed alphabetically by their hover text.

Icon Hover text Description
TemperatureBad.png

Abnormal temperature

IPMI sensors are detecting one or more nodes with temperature readings outside the recommended range. For details, see the applicable Storage Node pages.

VoltageBad.png

Abnormal voltage

IPMI sensors are detecting one or more nodes with voltage readings outside the recommended range. For details, see the applicable Storage Node pages.

SSLCertificateWarning.png

Active Directory certificates expire soon

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.

SSLCertificateCritical.png

Active Directory certificates expire soon

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.

ActiveDirectoryProblem.png

Active Directory secure connection issue

HCP could not communicate with AD due to a problem with the AD SSL server certificate uploaded to HCP. Ensure 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, please contact your authorized HCP service provider.

ActiveDirectoryProblem.png

AD credentials invalid

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.

ActiveDirectoryProblem.png

AD partially configured

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.

MetadataIntact.png

All metadata is intact

HCP policies have found no problems with object metadata.

ObjectsIntact.png

All objects are intact

HCP services have found no problems with object data.

PermissionsWarning.png

All operation-types operations are disabled

The indicated types of operations are currently not allowed. This alert appears when any permissions are disabled in the systemwide permission mask. For information on the systemwide permission mask, see Setting the systemwide permission mask.

IrreparableObjects.png

An unrecoverable error has occurred

HCP is experiencing a problem it cannot fix by itself. Please contact your authorized HCP service provider.

HDDSAuthenticationFailed.png

Authentication of HDDS user failed

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.

BackEndSwitchProblem.png

Back-end switch error

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

BBUCharging.png

BBU charging

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

BBUDegradedCharging.png

BBU degraded; charging

For RAIN systems only, the battery backup unit in one or more nodes is charging. The write-cache is disabled on those nodes.

BBUDegradedDischarging.png

BBU degraded; discharging

For RAIN systems only, the battery backup unit in one or more nodes is discharging. The write-cache is disabled on those nodes.

BBUDischarging.png

BBU discharging

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

BBUFailed.png

BBU failed

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, please contact your authorized HCP service provider.

BBULearn.png

BBU in learn cycle

For RAIN systems only, the battery backup unit in one or more nodes is in a learn cycle. System performance may be temporarily degraded.

MetadataBelowMDPL.png

Below metadata protection level. Repairing...

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.

FansBad.png

Broken fan

IPMI sensors are detecting one or more nodes or CB 320 server chassis with fan speeds outside the recommended range. For details, see the applicable Storage Node pages (for nodes) or the Hardware page (for chassis).

ActiveDirectoryProblem.png

Cannot access Key Distribution Center

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, please contact your authorized HCP service provider.

ActiveDirectoryProblem.png

Cannot access LDAP server

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, please contact your authorized HCP service provider.

ChassisCommunicationBad.png

Cannot communicate with chassis

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, please contact your authorized HCP service provider.

ActiveDirectoryProblem.png

Cannot connect to AD server

HCP cannot connect to the server for 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. Also ensure that AD is correctly configured in your DNS. If the problem persists, please contact your authorized HCP service provider.

ActiveDirectoryProblem.png

CIFS AD access disabled

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, please contact your authorized HCP service provider.

CIFSNFSExceeded.png

CIFS/NFS limit exceeded

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.

CIFSNFSReached.png

CIFS/NFS limit reached

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.

FullFileSystem.png

Conflicting CIFS settings detected

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.

ContentVerificationDisabled.png

Content verification repair disabled

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. For information on this option, see Configuring the content verification service.

FailedOverNodes.png

Data access failover

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

DegradedNetworkAssigned.png

Degraded network assigned

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.

EmptyNetworkAssigned.png

Empty network assigned

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.

ErasureCodingErrorAlert.png Erasure coding error

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.

ErasureCodingWarningAlert.png Erasure coding warning

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.

SpindownStorageErrorDown.png

Error spinning down volume

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

SpindownStorageErrorUp.png

Error spinning up volume

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

SSLCertificateExpired.png

Expired Active Directory certificates

One or more AD SSL certificates have expired. 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.

TrustedCertificateExpired.png

Expired replication certificates

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.

SSLCertificateExpired.png

Expired SSL server certificate

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 ensure that each affected domain has at least one valid certificate.

ExternalStorageUnavailable.png

External storage volumes unavailable

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 ensure that the devices hosting those volumes and the network connections to those devices are functioning properly. Also ensure that 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., as described in Remounting an NFS volume. If that doesn’t resolve the problem, contact your authorized HCP service provider for help.

ReplicationFrontEndNICError.png

Front-end connection error

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.

FullFileSystem.png

Full file system

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

HardwareGood.png

Hardware functioning properly

All of the HCP hardware is functioning normally.

ActiveDirectoryProblem.png

HCP computer account missing

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.

OnlineUpgradeInProgress.png

HCP upgrade is in progress

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

HDDSConnectionFailed.png

HDDS connection failure

HCP cannot connect to the HDDS server. Check that both the HDDS server and the network connection between HCP and that server are healthy. If both appear to be working properly, please contact your authorized HCP service provider.

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

HighLoadSwap.png

High load or swap

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

NICFailure.png

IP mode mismatch

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.

HDvMFailed.png

Last HDvM update failed

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

SystemNamespaceQuotaExceeded.png

Maximum namespaces exceeded

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, you need to have one or more tenant administrators delete one or more of their namespaces.

SystemNamespaceQuotaReached.png

Maximum namespaces reached

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

MetadataBalancing.png

Metadata balancing...

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

MetadataBalancing.png

Migration completing - balancing metadata

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.

MigrationInProgress.png

Migration in progress

A data migration is in progress. For information on data migrations, see Migration service.

MQEIndex50.png

MQE index at 50%

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.

MQEIndex80.png

MQE index at 80%; indexing disabled

The size of the metadata query engine index is 80 or more percent 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.

MQEIndexBad.png

MQE index partially unavailable

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 automatically resumes.

MQEIndexBad.png

MQE indexing unavailable

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.

MultipathBad.png

Multipath degraded to one

For SAIN systems configured with multipathing, the physical connection between a node and the SAN storage has failed. Please contact your authorized HCP service provider.

NetworkError.png

Network error

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, please 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, please 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, please contact your authorized HCP service provider.

NetworkWarning.png

Network warning

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, please 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. Please 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. Please contact your authorized HCP service provider.

ExternalTimeServer.png

No external time server configured

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.

ActiveDirectoryProblem.png

No Key Distribution Center found

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, please contact your authorized HCP service provider.

ActiveDirectoryProblem.png

No LDAP server found

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, please contact your authorized HCP service provider.

IrreparableObjects.png Nonreplicating object detected

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, please contact your authorized service provider.

HDDSConnectionFailed.png

OpenStack Identity Service connection failure

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, check that your OpenStack Identity Service is enabled, that 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, check that you have a certificate for your Server Domain, or that your current one has not expired.

PartialNetworkAssigned.png

Partial network assigned

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.

PartialNetworkAssigned.png

Partial network assigned to replication

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.

PowerSupplyBad.png

Power supply failure

One or more power supplies are not working on one or more nodes or CB 320 server chassis. Please contact your authorized HCP service provider.

ProcessorBad.png

Processor failure

IPMI sensors are detecting one or more nodes with processors that are not working. Please contact your authorized HCP service provider.

RegionsPerNodeLow.png

Regions per node is low

HCP storage management is currently not configured for optimal performance. To resolve this issue, please contact your authorized HCP service provider.

ReplicaCapacityWarning.png

Remote storage almost full

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.

ReplicaCapacityBad.png

Remote storage full (link suspended)

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.

TrustedCertificateWarning.png

Replication certificates expire soon

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.

TrustedCertificateCritical.png

Replication certificates expire soon

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.

ReplicationLinkBroken.png

Replication link failure

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.

ReplicationAutopausedTenantsAlert.png

Replication link has autopaused tenants

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.

ReplicationLinkPending.png

Replication link pending

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.

ReplicationLinkStalled.png

Replication link stalled

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.

ReplicationLinksShutDown.png

Replication links shut down

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.

ADWarningBig.png

Reverse IP lookup failed for Key Distribution Center

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 on the problem, go to the Active Directory page in the HCP System Management Console.

ActiveDirectoryProblem.png

Reverse IP lookup failed for Key Distribution Center

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 on the problem, go to the Active Directory page in the HCP System Management Console.

ADWarningBig.png

Reverse IP lookup failed for LDAP server

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 on the problem, go to the Active Directory page in the HCP System Management Console.

ActiveDirectoryProblem.png

Reverse IP lookup failed for LDAP server

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 on the problem, go to the Active Directory page in the HCP System Management Console.

SSDRAIDDegraded.png SSD RAID degraded An SSD is experiencing errors or has failed completely. Please contact your authorized HCP service provider for help.
ssd-warning.png SSD RAID rebuilding The SSD RAID volume is rebuilding. It cannot be accessed until the rebuild process is complete.
ActiveDirectoryProblem.png

Single sign-on issue

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 on 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, please contact your authorized HCP service provider.

WrongTimeSource.png

Some nodes not using the correct time source

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.

SpindownStorageGood.png

Spindown storage usage is percent-used

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

SpindownStorageWarning.png

Spindown storage usage is percent-used

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.

SpindownStorageCritical.png

Spindown storage usage is percent-used

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.

StorageTieringUnscheduled.png

Storage tiering service is missing from the current schedule.

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.

SSLCertificateWarning.png

SSL server certificate expires soon

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 ensure that each affected domain has at least one certificate that will be valid when the expiring certificates expire.

SSLCertificateCritical.png

SSL server certificate expires soon

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 ensure that each affected domain has at least one certificate that will be valid when the expiring certificates expire.

DrivesBad.png

Storage device reporting errors

One or more physical drives are experiencing problems. Please contact your authorized HCP service provider.

LicenseCapacitywarningAlert.png

Storage license has expired

The storage license is past its expiration date and no longer valid. Please contact HCP support to procure a new license.

LicenseCapacitywarningAlert.png

Storage license is not a valid license for this system

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. Please contact HCP support to procure a new license.

StorageUsageGood.png

Storage usage is percent-used

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.

StorageUsageWarning.png

Storage usage is percent-used

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.

StorageUsageBad.png

Storage usage is percent-used

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 SAIN system with spindown storage, this value applies only to running storage.

SystemDPL1.png

Default service plan DPL setting is 1

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.

SystemStarting.png

System is starting

The HCP system is in the process of starting up.

VirtualNetworkingDisabled.png

Tenants inaccessible due to network configuration

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.

NewtworkMissingLarge.png

Tenants inaccessible due to network configuration

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.

TimeOutOfSync.png

Time out of sync between replicating systems

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.

UnavailableNodes.png

Unavailable nodes

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, please 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.

IrreparableObjects.png Unavailable objects

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, please contact your authorized service provider.

LicenseViolationWarningAlert.png

Usage has exceeded license capacity for the storage

The storage capacity of the storage license has been exceeded. Please contact HCP support to procure a new license.

ActiveDirectoryProblem.png

Username mapping invalid

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.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Hardware page alerts


The System Management Console uses system health icons for alerts that appear on the Hardware page. These alerts are described in the table below. The alerts are listed alphabetically by their hover text. Alerts with text beginning with a number are listed first, in alphabetical order by the variable that represents the number.

Icon Hover text Description
FanSpeedCritical.png

bad-fan-count of fan-count chassis fans indicating problems

One or more fans in one or more CB 320 server chassis are not functioning properly. Please contact your authorized HCP service provider.

PowerSupplyBad.png

bad-power-supply-count of power-supply-count chassis power supplies indicating problems

One or more power supplies in one or more CB 320 server chassis are not functioning properly. Please contact your authorized HCP service provider.

FanSpeedNormal.png

fan-count of fan-count chassis fans operating normally

All fans on all CB 320 server chassis are functioning properly.

PowerSupplyGood.png

power-supply-count of power-supply-count chassis power supplies operating normally

All power supplies on all CB 320 server chassis are functioning properly.

BBUCharging.png

BBU charging

For RAIN systems only, the battery backup unit in the node is charging.

BBUDegradedCharging.png

BBU degraded; charging

For RAIN systems only, the battery backup unit in the node is charging. The write-cache is disabled on the node.

BBUDegradedDischarging.png

BBU degraded; discharging

For RAIN systems only, the battery backup unit in the node is discharging. The write-cache is disabled on the node.

BBUDischarging.png

BBU discharging

For RAIN systems only, the battery backup unit in the node is discharging.

BBUFailed.png

BBU failed

For RAIN systems only, the battery backup unit in the node has failed. The write-cache is disabled on the node. If this alert appears for more than a few hours, please contact your authorized HCP service provider.

FanSpeedCritical.png

Fan speed critical

IPMI sensors are detecting one or more fans with critically high or low speeds. Shut down the node and contact your authorized HCP service provider. For instructions on shutting down the node, see Restarting an individual node.

FanSpeedWarning.png

Fan speed out of normal range

IPMI sensors are detecting one or more fans with speeds above or below the recommended range, but not critically so. Monitor the fan speeds on the Storage Node page. If they do not return to normal, please contact your authorized HCP service provider.

FileSystemsBad.png

File system failure

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

MQEUnavailableOnNode.png

Metadata query engine failure

The metadata query engine is not running on the node, most likely because the node is unavailable. When the node becomes available again, the engine should automatically restart on it. If it doesn’t, disable and then reenable metadata query engine indexing. If the problem persists, please contact your authorized HCP service provider.

MultipathBadNode.png

Multipath degraded

For SAIN systems configured with multipathing, the physical connection between the node and the SAN storage has failed. Please contact your authorized HCP service provider.

NICFailure.png

NIC failure

The node is experiencing problems with one or more of its networks. Possible causes for this alert include:

One or more physical network connections to the node are not working. Check the Storage Node page for the 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, please contact your authorized HCP service provider.

The node is missing one or more network interfaces. Check the Networks page to see which networks have this problem. Then restart those networks. If the problem persists, please contact your authorized HCP service provider.

The node has one or more network interfaces for networks in which it does not have IP addresses. Check the Networks page to see which networks have this problem. Then restart those networks. If the problem persists, please contact your authorized HCP service provider.

ChassisFanCommunicationBad.png

No IPMI status available for chassis fans

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, please contact your authorized HCP service provider.

ChassisPowerSupplyCommunicationBad.png

No IPMI status available for chassis power supplies

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, please contact your authorized HCP service provider.

NodeRemoved.png

Node has been removed

The node has been permanently removed from the HCP system. You cannot reuse its back-end IP address for any nodes you subsequently add to the system.

CoreHardwareBad.png

Node problem

The node is experiencing a heavy load or a high rate of page swapping. Please contact your authorized HCP service provider.

PowerSupplyBad.png

Power supply error

The node has only one power supply working normally. Please contact your authorized HCP service provider.

SSDRAIDDegraded.png SSD RAID degraded An SSD is experiencing errors or has failed completely. Please contact your authorized HCP service provider for help.
ssd-warning.png SSD RAID rebuilding An SSD device is rebuilding. It cannot be accessed until the rebuild process is complete.
StorageDevicesBad.png

Storage failure

One or more physical storage devices managed by the node are not functioning properly. If this alert is raised by a removed or a failed drive, it can take up to an hour before it appears on the Hardware page of the System Management Console. Please contact your authorized HCP service provider for assistance.

TemperatureCritical.png

Temperature critical

IPMI sensors are detecting one or more components with critically high or low temperature readings. Shut down the node and contact your authorized HCP service provider. For instructions on shutting down the node, see Restarting an individual node.

TemperatureWarning.png

Temperature out of normal range

IPMI sensors are detecting one or more components with high or low, but not critical, temperature readings. Monitor the temperature readings on the Storage Node page. If they do not return to normal, please contact your authorized HCP service provider.

TemperatureNormal.png

Temperature within normal range

IPMI sensors are not detecting any components with temperature readings outside the normal range.

VoltageCritical.png

Voltage critical

IPMI sensors are detecting one or more components with critically high or low voltage readings. Shut down the node and contact your authorized HCP service provider. For instructions on shutting down the node, see Restarting an individual node.

VoltageWarning.png

Voltage out of normal range

IPMI sensors are detecting one or more components with high or low, but not critical, voltage readings. Monitor the voltage readings on the Storage Node page. If they do not return to normal, please contact your authorized HCP service provider.

VoltageNormal.png

Voltage within normal range

IPMI sensors are not detecting any components with voltage readings outside the normal range.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Storage Node page alerts


The System Management Console uses system health icons for alerts that appear on the Storage Node page for each node. These alerts are described in the table below. The alerts are listed alphabetically by their hover text. Alerts with text beginning with a number are listed first, in alphabetical order by the variable that represents the number.

Icon Hover Text Description
NICsBad.png

bad-interface-count of interface-count network interfaces are not functioning properly

One or more NICs in the node are not functioning properly. Please contact your authorized HCP service provider.

StorageDevicesBad.png

bad-storage-device-count of storage-device-count storage devices are not functioning correctly

One or more physical storage devices managed by the node are not functioning properly. Please contact your authorized HCP service provider.

StorageDevicesGood.png

file-system-count file systems on storage-device-count devices

The node has the indicated number of file systems, which map to the indicated number of physical storage devices.

IPMIBad.png

sensor-count IPMI sensors are indicating problems

The indicated number of IPMI sensors are detecting one or more problems in the node. For more information, review the IPMI details.

FileSystemsGood.png

All file-system-count file systems have sufficient space and inodes

All the file systems on the node have space and inodes available for storing additional objects.

IPMIGood.png

All IPMI sensors report normal operation

All components monitored by IPMI are functioning normally.

NICsGood.png

All network interfaces are functioning properly

All NICs in the node are functioning properly.

CoreHardwareGood.png

Core hardware is functioning normally

The load and rate of page swapping on the node are within the acceptable range.

CoreHardwareBad.png

Core hardware may need attention

The node is experiencing a heavy load or a high rate of page swapping. Please contact your authorized HCP service provider.

FileSystemsBad.png

File system is running out of space or inodes

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

LogicalVolumeUsage.png

Logical volume usage

The logical volumes managed by the node have the status, capacity, and used space shown when you expand the alert.

MultipathBadNode.png

Multipath degraded

For SAIN systems configured with multipathing, a physical connection between the node and the SAN storage has failed. Please contact your authorized HCP service provider.

NoIPMI.png

No IPMI status is available

The node does not contain IPMI sensors.

NodeRemoved.png

Node has been removed

The node has been permanently removed from the HCP system. You cannot reuse its back-end IP address for any nodes you subsequently add to the system.

CoreHardwareBad.png

Node is not available

The node is unavailable for one of these reasons:

It is starting up but not yet able to perform HCP functions.

It is shutting down and no longer able to perform HCP functions.

It is not running or is unable to communicate with the rest of the HCP system.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Storage page alerts


The System Management Console uses warning and error icons for alerts that appear on the Storage page.

The icon used to indicate a warning condition is a white circle containing an orange exclamation point. When this icon appears in a table row, that row is highlighted in orange.

The icon used to indicate an error condition is a white triangle containing a red exclamation point. When this icon appears in a table row, that row is highlighted in red.

The warning and error alerts that appear on the Storage page are described in separate sections below.

Storage page warning alerts

Warning alerts that appear on the Storage page are described in the table below. These alerts are listed alphabetically by their hover text.

Icon Hover text Description
Storage components list
ExternalVolumeProblem.png

One or more volumes in this storage pool have problems

One or more of the external storage volumes in the external storage pool have a status other than available. To see which volumes have problems, open the panel for the storage pool. For more information on problem volumes, check the HCP system log.

Storage pools list
ExternalVolumeProblem.png

External volume volume-id on node node-number - volume-status

The external storage volume has a status other than available. For information on the cause, check the HCP system log.

If the status is broken, check the export configuration and verify that the NFS server is running. If the configuration is correct and the NFS server is running, ensure that the device is functioning properly and that the network connecting HCP to the device is healthy. For additional possible resolutions to the problem, see NFS storage pools.

If the status is unavailable and does not change to available or broken within a short amount of time, try remounting the volume, as described in Remounting an NFS volume.

If this alert persists, contact your authorized HCP service provider for help.

Storage page error alerts

Error alerts that appear on the Storage page are described in the table below. These alerts are listed alphabetically by their hover text.

Icon Hover text Description
Storage components list
ExternalVolumeProblem.png

One or more volumes in this storage pool have problems

One or more of the external storage volumes in the external storage pool have a status other than available. To see which volumes have problems, open the panel for the storage pool. For more information on problem volumes, check the HCP system log.

Storage pools list
ExternalVolumeProblem.png

External volume volume-id on node node-number - volume-status

The external storage volume has a status other than available. For information on the cause, check the HCP system log.

If the status is broken, check the export configuration and verify that the NFS server is running. If the configuration is correct and the NFS server is running, ensure that the device is functioning properly and that the network connecting HCP to the device is healthy. For additional possible resolutions to the problem, see NFS storage pools.

If the status is unavailable and does not change to available or broken within a short amount of time, try remounting the volume, as described in Remounting an NFS volume.

If this alert persists, contact your authorized HCP service provider for help.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Networks page alerts


The System Management Console uses error and warning icons for alerts that appear on the Networks page.

The icon used to indicate an error condition is a white triangle containing a red exclamation point. When this icon appears in a table row, that row is highlighted in red.

The icon used to indicate a warning condition is a white circle containing an orange exclamation point. When this icon appears in a table row, that row is highlighted in orange.

The error and warning condition alerts that appear on the Networks page are described in two separate sections below.

Networks page error condition alerts

Error condition alerts that appear on the Networks page are described in the table below. These alerts are listed alphabetically by their hover text

Hover text Description

Network has no node IP addresses

The network is empty; that is, no nodes have any IP addresses defined for the network. Clients cannot access the HCP system over an empty network.

Configure the network to assign IP addresses to one or more nodes. Each node must have a separate IP address on each subnet defined for the network.

Network not functioning properly

The network is experiencing problems on one or more nodes. Possible causes for this error condition alert include:

One or more physical network connections to one or more nodes are not working. Check the Storage Node page for each 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, please contact your authorized HCP service provider.

The network interface for the network is missing in one or more nodes. Restart the network. If the problem persists, please contact your authorized HCP service provider.

One or more nodes have network interfaces for the network but do not have IP addresses in the network. Restart the network. If the problem persists, please contact your authorized HCP service provider.

Networks page warning condition alerts

Warning condition alerts that appear on the Networks page are described in the table below. These alerts are listed alphabetically by their hover text

Hover text Description

Network disabled

The network has been manually disabled by a system administrator. Clients cannot access the HCP system over a disabled network and tenants and namespaces cannot be replicated over a disabled network.

Check the Tenants page to determine whether the disabled network is assigned to any tenants. Also check the replication Settings page to determine whether the disabled network is selected as the replication network.

If the network is assigned to one or more tenants, take one of these actions:

On the Tenants page, reconfigure the affected tenants to use only enabled networks for data and management access.

On the Networks page, click on the gear icon next to the disabled network to display the network Settings panel. Then select the option to enable the network and click on Update Settings.

If the network is selected as the replication network, take one of these actions:

On the replication Settings page, select a different network for replication.

On the Networks page, click on the gear icon next to the disabled network to display the network Settings panel. Then select the option to enable the network and click on Update Settings.

If the network is not assigned to any tenants, and is not used for replication, no action is required. You can use the Networks page to reconfigure, reenable, or delete the network at any time without affecting access to the HCP system.

IP mode mismatch

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.

Network has only one node IP address

The network is degraded; that is, only one node has IP addresses defined for the network. A degraded network presents a single point of failure for clients accessing HCP over that network.

Reconfigure the network to assign IP addresses to one or more additional nodes.

Network is missing node IP addresses

The network is a partial network; that is, at least two nodes have IP addresses defined for the network and at least one node does not. The load from client requests over a partial network is not fully distributed across the nodes in the HCP system.

Reconfigure the network to assign IP addresses to all the nodes in the HCP system. Each node must have an IP address on each subnet defined for the network.

Network not functioning properly

The network is experiencing problems on one or more nodes. Possible causes for this warning condition alert include:

The current MTU for the network 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, please contact your authorized HCP service provider.

For the [hcp_system] network, the current speed of the network on one or more nodes does not match the configured speed. Please contact your authorized HCP service provider. (This does not apply if the speed is set to auto.)

For the [hcp_backend] network, the current speed of the network on one or more nodes is not the maximum speed possible for that network. Please contact your authorized HCP service provider.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Tenants page alerts


The alerts in the table below are listed alphabetically by their hover text.

Icon Hover text Description
NetworkDegradedSmall.png

Degraded network assigned

The tenant is associated with a degraded network for management or data access purposes. A degraded network presents a single point of failure for clients accessing the tenant or its namespaces over that network.

Take one of these actions:

On the Tenants page, reconfigure the affected tenant to use only networks that have IP addresses defined for at least two nodes in the HCP system.

On the Networks page, reconfigure each degraded network to assign IP addresses to one or more additional nodes.

NetworkEmptySmall.png

Empty network assigned

The tenant is associated with an empty network for management or data access purposes. If the management network is empty, the tenant cannot be accessed through the Tenant Management Console or HCP management API. If the data access network is empty, namespaces belonging to a tenant are inaccessible.

Take one of these actions:

On the Tenants page, reconfigure the affected tenant to use only networks that have IP addresses defined for at least two nodes in the HCP system.

On the Networks page, configure each empty network to assign IP addresses to one or more nodes. Each node must have a separate IP address on each subnet defined for the network.

TenantNetworkInaccessible.png

Inaccessible due to network configuration

The management and/or data access network specified for the tenant does not exist. If the management network does not exist, the tenant cannot be accessed through the Tenant Management Console or HCP management API. If the data access network does not exist, namespaces belonging to a tenant 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.

For each undefined network, create a network with the name of the undefined network.

TenantNamespaceQuotaExceeded.png

Namespace quota exceeded

The number of namespaces owned by the tenant is greater than the namespace quota for the tenant.

This situation can happen if the tenant is included in an active/active replication link. With this type of link, namespaces can be created for the tenant independently on each system involved in the link. Namespaces from both systems can then be added to the link such that the total number of namespaces replicated on the link exceeds the namespace quota for the tenant. As a result, the total number of namespaces for the tenant on each system exceeds the namespace quota for the tenant.

TenantNamespaceQuotaReached.png

Namespace quota reached

The number of namespaces owned by the tenant equals the namespace quota for the tenant.

NamespaceNonReplicatingObjects.png Nonreplicating Objects The tenant contains objects that are not replicating. Please contact your HCP system administrator.
NetworkPartialSmall.png

Partial network assigned

The tenant is associated with a partial network for management or data access purposes. The load from client requests for access to the tenant or its namespaces is not being fully distributed across the nodes in the HCP system.

Take one of these actions:

On the Tenants page, reconfigure the affected tenant to use only networks that have IP addresses defined for all nodes in the HCP system.

On the Networks page, reconfigure each partial network to assign IP addresses to all nodes in the HCP system. Each node must have a separate IP address on each subnet defined for the network.

ReplicationReadOnly.png

Read-only, set by replication

For HCP tenants only, the tenant is read-only because it’s included in an active/passive link and one of the following is true:

The current system is the replica for the link, and normal replication is occurring on the link.

The current system is the primary system for the link, and the initial stage of data recovery is occurring on the link.

The current system is either the primary system or the replica for the link, and the final stage of data recovery is occurring on the link.

SoftQuotaExceeded.png

Soft quota exceeded

For HCP tenants only, 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.

FullFileSystem.png

Tenant has namespace-count namespace(s) configured for CIFS with authenticated access only, but CIFS authenticated access is not currently supported

One or more of the tenant's namespaces are configured for CIFS authenticated access only, but the system is not configured to support the use of authenticated CIFS. As a result, CIFS cannot be used for access to those namespaces.

Reconfigure the affected namespace(s) to support both anonymous and authenticated access with CIFS.

IrreparableObjects-TenNS.png

Tenant tenant-name has irreparable-object-count irreparable objects

One or more of the tenant's namespaces contain the indicated total number of irreparable objects. Please contact your authorized HCP service provider.

IrreparableObjects-TenNS.png

Tenant tenant-name has irreparable-object-count irreparable objects and unavailable-object-count unavailable objects

One or more of the tenant's namespaces contain the indicated total number of irreparable objects, and one or more of the tenant's namespaces contain the indicated total number of unavailable objects. Please contact your authorized HCP service provider.

IrreparableObjects-TenNS.png

Tenant tenant-name has unavailable-object-count unavailable objects

One or more of the tenant's namespaces contain the indicated total number of unavailable objects. This is most likely due to one or more nodes being unavailable, If the situation persists, please contact your authorized HCP service provider.

DefaultTenantDPL1SomeDirRep.png

Tenant may have directories that are not being replicated

For the default tenant in RAIN systems only, the default namespace has a DPL of one and at least one of the directories in it is being replicated. When the default namespace has a DPL of one, all directories in it should be replicated to ensure that the stored data is protected.

DPL1Namespace.png

Tenant with DPL 1 namespaces that are not replicating

In RAIN systems only:

For HCP tenants, the tenant owns one or more namespaces that have a DPL of one and are not being replicated. All HCP namespaces with a DPL of one should be replicated to ensure that the stored data is protected.

For the default tenant, the default namespace has a DPL of one and none of the directories in it are being replicated. When the default namespace has a DPL of one, all directories in it should be replicated to ensure that the stored data is protected.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Domains and Certificates page alerts


The alerts in the table below are listed alphabetically by their hover text.

Icon Hover text Description
Domain list
CertificateRedExclamation.png

All certificates for domain are invalid

All the certificates associated with the domain have either an expiration date in the past or a start date in the future. Add a valid certificate to the domain.

CertificateYellowExclamation.png

All valid certificates for the domain are expiring

All the valid certificates associated with the domain will expire within 30 days. Ensure that the domain has at least one certificate that will be valid when the expiring certificate expires.

Certificate list
CertificateHourglass.png

Certificate has a start date in the future

The start date for the certificate is in the future, so the certificate is currently invalid. Ensure that the domain has at least on valid certificate.

CertificateRedExclamation.png

Certificate is expired

The certificate has expired and is no longer valid. Delete the certificate.

CertificateYellowExclamation.png

Certificate is expiring

The certificate will expire within 90 days. Ensure that the domain has at least one certificate that will be valid when this certificate expires.

CertificateRedExclamation.png

Common name for certificate does not match domain name

The common name of the certificate does not represent a subdomain of the domain with which the certificate is associated. The certificate is invalid. 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.

Ensure that domain has at least one valid certificate. Then delete the certificate with the common name mismatch.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Active Directory page alerts


The alerts in the table below are listed alphabetically by their hover text.

Icon Hover text Description
ADSystemBad.png

Active Directory enabled for default namespace only.

Either:

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.

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.

ADSystemBad.png

Active Directory secure connection issue

HCP could not communicate with AD due to a problem with the AD SSL server certificate uploaded to HCP. Ensure 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, please contact your authorized HCP service provider.

ADSystemBad.png

Cannot access Key Distribution Center

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 AD domain controller are healthy. If they both appear to be working properly, please contact your authorized HCP service provider.

ADSystemBad.png

Cannot access LDAP server

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, please contact your authorized HCP service provider.

ADSystemBad.png

Could not establish connection with Active Directory - add certificate again.

HCP could not communicate with AD due to a problem with the AD SSL server certificate uploaded to HCP. Ensure 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, please contact your authorized HCP service provider.

ADDNSGood.png

DNS correctly configured.

HCP is configured to use DNS.

ADDNSBad.png

DNS is not enabled. Active Directory requires DNS be enabled.

HCP is not configured to use DNS. For HCP to work with AD, HCP must be configured as a subdomain in your DNS. For instructions on configuring the HCP subdomain, see Configuring DNS for HCP.

ADSystemBad.png

HCP computer account missing.

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.

ADSystemBad.png

IP lookup failed for Active Directory server server-name.

HCP was unable to do an IP lookup of an IP address used to communicate with the AD domain controller for either the Key Distribution Center or the LDAP server. Ensure that the DNS configuration includes all A and AAAA records needed to resolve the IP addresses that HCP uses to communicate with the indicated domain controller.

ADTimeServerBad.png

No external time server configured. Active Directory recommends an external time server.

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.

ADSystemBad.png

No Key Distribution Center found

HCP cannot find a Key Distribution Center in the AD domain specified in the HCP AD configuration. Ensure that AD is correctly configured in your DNS. If the problem persists, please contact your authorized HCP service provider.

ADSystemBad.png

No LDAP server found

HCP cannot find an LDAP server in the AD domain specified in the HCP AD configuration. Ensure that AD is correctly configured in your DNS. If the problem persists, please contact your authorized HCP service provider.

ADNodesGood.png

Nodes correctly configured.

All of these conditions are true:

The computer accounts for all nodes are present in the AD domain. These accounts are created automatically when you configure HCP to support AD.

All nodes have valid credentials for the HCP computer account used to query AD for groups.

All nodes can connect to AD.

ADNodesBad.png

Nodes misconfigured.

At least one of these conditions is true:

The computer account for one or more nodes is missing from the AD domain. These accounts are created automatically when you configure HCP to support AD.

The credentials for the HCP computer account used to query AD for groups and other information are invalid on one or more nodes.

One or more nodes cannot connect to AD.

To resolve these issues, reconfigure support for AD on the Active Directory page in the HCP System Management Console. If the problem persists, please contact your authorized HCP service provider.

ADNodesBad.png

Reverse IP lookup failed for Active Directory server server-name. Record for server-ip-address not found.

Given the indicated IP address, HCP was unable to do a reverse IP lookup of the hostname of the AD domain controller. Ensure that your DNS includes a PTR record for that IP address that specifies the correct domain controller hostname.

ADNodesBad.png

Reverse IP lookup mismatch for Active Directory server server-name. Record for server-ip-address points to server other-server-name.

HCP was able to do a reverse IP lookup of an IP address used to communicate with the AD domain controller, but the PTR record identifies a different domain controller. Ensure that your DNS configuration includes a PTR record for the indicated IP address that specifies the correct domain controller hostname.

ADNodesBad.png

Service principal names are missing.

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.

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, please contact your authorized HCP service provider.

ADNodesGood.png

System correctly configured.

All of the following are true:

No HCP components are missing from the AD domain.

The HCP configuration of AD support is complete (that is, it’s not configured only for the CIFS protocol for the default namespace).

The username mapping file used by the CIFS protocol does not contain any invalid mappings.

ADTimeServerGood.png

Time server correctly configured.

HCP is configured to use an external time server.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.