Skip to main content
Hitachi Vantara Knowledge

Tenants page alerts

Tenant page alerts are listed alphabetically by their hover text.

  • Degraded network assigned

    GUID-1F0CA4C9-597D-46C1-B8F9-447F8008D4DF-low.png

    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.
  • Empty network assigned

    GUID-CBF1FA0F-E9FA-4D63-9C30-B81EF35F5F14-low.png

    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.
  • Inaccessible due to network configuration

    GUID-04476258-04A1-48CA-8961-C541AD9AE721-low.png

    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.

  • Namespace quota exceeded

    GUID-CA2A042D-D0A7-408E-A2DE-99AC148F3805-low.png

    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.

  • Namespace quota reached

    GUID-0A5D4AC7-A766-44B7-8336-109EDFC14EAC-low.png

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

  • Nonreplicating objects

    GUID-F14FA2A2-625A-4845-80A4-AAA47B722DF8-low.png

    The tenant contains objects that are not replicating. Contact your HCP system administrator.

  • Partial network assigned

    GUID-6ADA8942-7006-4DDA-B11D-0CB5E28C9897-low.png

    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.
  • Read-only, set by replication

    GUID-2E476EFA-620A-4DD4-9ED6-8864CD04E87D-low.png

    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.
  • Soft quota exceeded

    GUID-5E10EB63-8DBA-4F1C-B1D0-4C4A5EEFF653-low.png

    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.

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

    GUID-6C7D3AE1-B67F-47F0-975D-D3B195BA7DAA-low.png

    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.

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

    GUID-6C7D3AE1-B67F-47F0-975D-D3B195BA7DAA-low.png

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

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

    GUID-D8E94ADE-0E2F-420C-AEAD-63B3199AFBE8-low.png

    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. Contact your authorized HCP service provider.

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

    GUID-4067B5E8-6B3D-4550-A9E4-14E200593D4D-low.png

    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.

  • Tenant may have directories that are not being replicated

    GUID-389CEA18-2405-4A5B-9B7F-AE21890C5098-low.png

    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.

  • Tenant with DPL 1 namespaces that are not replicating

    GUID-7C5588F1-2E77-4DA5-9E69-F96876962D02-low.png

    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.

 

  • Was this article helpful?