Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

About the Hardware page


The Hardware page of the HCP System Management Console lists all the nodes in the HCP system, including HCP S Series Nodes, and provides general information about each one. If the nodes in the system are blades in Hitachi CB 320 servers, the page shows the status of the fans and power supplies in the CB 320 chassis under its own subsection labeled, chassis.

The Hardware page also shows the status of all other hardware components of the HCP system that can be monitored in the System Management Console.

To display the Hardware page, click on Hardware in the top-level menu.

RoleWebHelp.png

Roles: To view the Hardware page, you need the monitor, administrator, security, service, or compliance role.

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

About the Nodes page


The Hardware Nodes page lists all of the HCP General Nodes and HCP S Series Nodes in the HCP system. General Nodes remain listed on this page regardless of whether they’re running, starting up, stopping, or not running at all. Nodes that have been permanently removed from the system do not appear on the list.

For each node in the HCP system, the General Node list on the Hardware Nodes page shows:

Node ID — The unique number assigned to the node.

Model — The type of node. Possible models are:

oG10 — A Quanta D51B-2U server which can exist in both a RAIN or SAIN system

o300 — A server other than a Quanta D51B-2U server that exists in an HCP RAIN system

o500 — A server other than a Quanta D51B-2U server that exists in an HCP SAIN system

o500XL — A server other than a Quanta D51B-2U server that exists in an HCP SAIN system

oVM — A server running an HCP-VM system

Status — The node status. Possible values are:

oAvailable — The node is running.

oUnavailable — The node is either not running, starting up but not yet able to perform HCP functions, or shutting down and no longer able to perform HCP functions. If a node is unavailable due to a hardware problem, you may be able to determine the cause by reviewing the Hardware Status section on the individual Storage Node page.

oMigrating — The node is available, and the migration service is currently migrating data off the storage managed by the node.

oAlert — The node is unavailable, and HCP can detect which components are experiencing problems. In this case, one or more alerts identifying the problems appear in the Alerts column for the node.

ImportantWebHelp.png

Important: 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.

Alerts — None, one, or more icons representing components that are experiencing problems. To see the text that accompanies an icon, hover over the icon.

For more information on any problems that are occurring, click on the node number.

For information on the alerts that can appear on the Hardware Nodes page, see Hardware page alerts.

Logical Volumes — The status of the logical volumes managed by the node. Each logical volume can be one of these:

oData volume — Primary running storage that stores object data, but does not store the metadata query engine index. Primary running storage is storage that’s managed by the nodes in the HCP system and consists of continuously spinning disks.

Data volumes have numeric IDs in the range 1 (one) through 63 and 92 through 95.

oIndex volume (SAIN systems only) — Primary running storage that stores only the metadata query engine index. All storage nodes should have the same number of index volumes.

Index volumes have numeric IDs in the range 64 through 91.

oShared volume — Primary running storage that stores both object data and the metadata query engine index. All storage nodes have one shared volume.

The shared volume for each node has a numeric ID in the same range as data volumes.

oSpindown volume (SAIN systems only) — Primary spindown storage that’s used for tiering purposes. Primary spindown storage is storage that’s managed by the nodes in the HCP system and consists of disks that can be spun down and spun up as needed. Primary spindown storage stores object data, but does not store the metadata query engine index. All storage nodes should have the same number of spindown volumes.

Spindown volumes have numeric IDs in the range 96 through 127. The volume numbering starts from 96 and goes up.

A SAIN system can have spindown volumes only if both of these conditions are true:

One or more logical volumes used by the system are capable of being spun down. This means that they are on storage arrays that support spindown.

For information on storage arrays that support spindown, see the applicable array documentation.

The system is configured to use one or more of the spindown-capable logical volumes as primary spindown storage.

oNFS volume (also called an external volume)— Extended storage that’s accessed using an NFS mount point. Extended storage is storage that’s managed by devices outside of the HCP system and is used for storage tiering purposes. NFS storage is one of six types of extended storage that HCP can be configured to use. NFS storage can be used to store object data only.

NFS volumes have numeric IDs in the range 96 through 127. The volume numbering starts from 127 and goes down.

oDatabase volume — A volume that holds database transaction logs and indexes. Optional rear mounted SSD volumes are also available for G10 nodes. SSD volumes store only indexes.

For information on primary running storage and primary spindown storage, see Storage tiering service. For information on the metadata query engine index, see ………Metadata query engine index. For information on NFS volumes and other types of extended storage, see Storage for HCP systems.

The Logical Volumes column displays a status icon for each logical volume managed by the node. The hover text for each icon shows the volume type, volume ID, and, for NFS volumes, the share path and the name of the extended storage pool that contains the NFS volume.

The table below describes the logical volume status icons.

Icon Volume type Volume status
VolumeDataAvailable.png Data Available — The volume is available and functioning properly.
VolumeDataUnavailable.png Data Unavailable — The volume is unavailable, most likely because the node is not running. If the volume does not become available soon, contact your authorized HCP service provider for help.
VolumeDataShuttingDown.png Data Shutting down — The volume is shutting down and is no longer available for access.
VolumeDataBroken.png Data Broken — The volume is experiencing errors (or has failed completely) and needs to be replaced. Contact your authorized HCP service provider for help.
VolumeDataMigrating.png Data Migrating — The migration service is migrating data off the volume.
VolumeDatabaseAvailable.png Database Available — The volume is available and functioning properly.
VolumeDatabaseDegraded.png Database Degraded — The volume is experiencing errors (or has failed completely). Contact your authorized HCP service provider for help.
DatabaseInitialized.png Database Initialized — The volume has started up and is available for access.
DatabaseInitializing.png Database Initializing — The volume is starting up but is not yet available for access.
DatabaseMigrating.png Database Migrating — The migration service is migrating data off the volume.
DatabaseRebuilding.png Database Rebuilding — The volume is rebuilding and cannot be accessed.
DatabaseUnavailable.png Database Unavailable — The volume is unavailable, most likely because the node is not running. If the volume does not become available soon, contact your authorized HCP service provider for help.
VolumeIndexAvailable.png Index Available — The volume is available and functioning properly.
VolumeIndexUnavailable.png Index Unavailable — The volume is unavailable, most likely because the node is not running. If the volume does not become available soon, contact your authorized HCP service provider for help
VolumeIndexInitializing.png Index Initializing — The volume is starting up but is not yet available for access.
VolumeIndexShuttingDown.png Index Shutting down — The volume is shutting down and is no longer available for access.
VolumeIndexBroken.png Index Broken — The volume is experiencing errors (or has failed completely) and needs to be replaced. Contact your authorized HCP service provider for help.
VolumeIndexMigrating.png Index Migrating — The migration service is migrating data off the volume.
VolumeSharedAvailable.png Shared Available — The volume is available and functioning properly.
VolumeSharedUnavailable.png Shared Unavailable — The volume is unavailable, most likely because the node is not running. If the volume does not become available soon, contact your authorized HCP service provider for help.
VolumeIndexInitializing.png Shared Initializing — The volume is starting up but is not yet available for access.
VolumeSharedShuttingDown.png Shared Shutting down — The volume is shutting down and is no longer available for access.
VolumeSharedBroken.png Shared Broken — The volume is experiencing errors (or has failed completely) and needs to be replaced. Contact your authorized HCP service provider for help.
VolumeSharedMigrating.png Shared Migrating — The migration service is migrating data off the volume.
VolumeSpindownAvailable.png Spindown Available — The volume is spun up, available, and functioning properly.
VolumeSpindownSpunDown.png Spindown Spun down — The volume is spun down.
VolumeSpindownUnavailable.png Spindown Unavailable — The volume is unavailable, most likely because the node is not running. If the volume does not become available soon, contact your authorized HCP service provider for help.
VolumeSpindownInitializing.png Spindown Initializing — The volume is starting up but is not yet available for access.
VolumeSpindownShuttingDown.png Spindown Shutting down — The volume is shutting down and is no longer available for access.
VolumeSpindownSpinningUp.png Spindown Spinning up — The volume is in the process of spinning up but is not yet available for access.
VolumeSpindownSpinningDown.png Spindown Spinning down — The volume is in the process of spinning down and is no longer available for access.
VolumeSpindownErrorSpinningUp.png Spindown Error spinning up — The volume is experiencing errors while in the process of spinning up. Contact your authorized HCP service provider for help.
VolumeSpindownErrorSpinningDown.png Spindown Error spinning down — The volume is experiencing errors while in the process of spinning down. Contact your authorized HCP service provider for help.
VolumeSpindownBroken.png Spindown Broken — The volume is experiencing errors (or has failed completely) and needs to be replaced. Contact your authorized HCP service provider for help.
VolumeSpindownMigrating.png Spindown Migrating — The migration service is migrating data off the volume.
VolumeExternalAvailable.png NFS (External) Available — The volume is mounted, available, and functioning properly.
VolumeExternalInitializing.png NFS (External) Initializing — The volume is starting up but is not yet available for access.
VolumeExternalBroken.png NFS (External)

Broken — HCP can cannot mount the volume, most likely because the exported share is not configured correctly or because the NFS server is not running on the device. 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 this status persists, contact your authorized HCP service provider for help.

VolumeExternalUnavailable.png NFS (External)

Unavailable — HCP is in the process of mounting, updating, or deleting the volume. If you just created or updated the volume and the volume status does not change to available or broken within a short amount of time, try remounting the volume.

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

These considerations apply to the logical volume display:

oEach node also has a logical volume for the operating system, but that logical volume is not included in this display.

oFor HCP SAIN systems that also have internal storage, this display does not include the logical volumes on the internal drives.

oWhen a logical volume is removed from a node, the System Management Console may not show the change immediately. Heavy read or write activity causes more access to HCP storage and, therefore, results in faster detection of the volume removal.

Volume Usage — A graphical representation of the amount of primary storage that’s currently in use compared to the total amount of primary storage that’s managed by the node. The Volume Usage column also displays text indicating the total number of bytes of primary storage and the percent of primary storage space that’s currently in use.

For each node that has been permanently removed from the system, the first column in the display shows Removed.

For each HCP S Series Node associated with the HCP system, the S Series Nodes list on the Hardware Nodes page shows:

Name — The name of to the S Series Node.

Serial Number — The serial number of the HCP S Series Node.

Model — The type of S Series Node. Possible models are:

oS10

oS30

Status — The node status. Possible values are:

oNormal — The S Series Node is running and has no problems that require attention.

oDegraded — The S Series Node has one or more noncritical problems that may require attention.

oCritical — The S Series Node has one or more critical problems that require attention.

oUnavailable — The S Series Node is either not running, starting up but not yet able to perform functions, or shutting down and no longer able to perform functions. If an S Series Node is unavailable due to a hardware problem, you may be able to determine the cause by reviewing the Hardware Status section on the individual Overview page.

Alerts — None, one, or more icons representing components that are experiencing problems. To see the text that accompanies an icon, hover over the icon.

Capacity — A graphical representation of the amount of storage that’s currently in use compared to the total amount of storage that’s on the node. The Capacity column also displays text indicating the total number of bytes of storage and the percent of storage space that’s currently in use.

For more information on working with HCP S Series Nodes, see Isolating networks for storage tiering.

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

Monitoring individual HCP General Nodes


Each HCP General Node has its own page on the HCP System Management Console which shows detailed information about the node. The page title indicates the node number and the node status.

NoteWebHelp.png

Note: To view an individual HCP General Node page, you need the monitor, administrator, security, service, or compliance role.

To open the Storage Node page, go to the Hardware Nodes page and click on the node that you want to examine. For information on the Hardware page, see About the Hardware page.

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

Monitoring individual HCP S Series Nodes


The Overview panel on the page for an individual HCP S Series Node provides information about various components of the node. The pie chart at the top right of the page shows the total storage capacity of the S Series Node (dark blue) and the total storage capacity used (light blue).

The Server Modules section lists the names and statuses of HCP S Series Node server modules. Server modules run the software that manages the HCP S Series Node, provide data access, and ensure data protection.

The Enclosure section lists names and statuses of S Series Node enclosures. The enclosure is a container for the power, cooling, and server modules, along with the hard disk drives inside the node. S10 nodes have only one enclosure. S30 nodes support up to 16 enclosures.

The Events section shows the messages about warning-level and error-level alerts that occur on the HCP S Series Nodes. The messages in this panel are a subset of all the messages on the HCP system log.

To see more detailed information about the HCP S Series Node, click on the HCP S Series Node URL located above the pie chart. This opens the HCP S Series Management Console.

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

Modifying HCP S Series Nodes


To modify an HCP S Series Node:

1.On the Hardware Nodes page, click on the Settings tab.

2.In the Name field, type the new name you want to give the S Series Node.

3.In the Description field, type the new description you want to give the S Series Node.

4.Optionally, if Storage Network field is visible, select a network for tiering. For more information on selecting a network, see Isolating networks for storage tiering.

5.In the Domain Name or Virtual IP field, type the new domain or virtual IP address of the S Series Node.

6.Select Compliant if the S Series Node meets the compliancy expectations of your service plan.

7.Select Use HTTPS for management to use HTTP with SSL security for S Series Node management requests.

8.Click on Update Settings.

Clicking Advanced Settings redirects you to the Advanced tab on the S Series Node Storage Components page. For more information about advanced settings, see Modifying advanced component settings.

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

About the Switches page


On the Hardware Switches page you can add, delete, and monitor your HCP system switches. With the Service role enabled you can add and delete switches. With the Administrator role you can monitor the status of existing switches, but you cannot add or delete them.

For each switch, the page displays the following information:

Type — The type of component.

Model — The make and model of the component (for example, Dell® PowerConnect™ 2824).

IP address — The IP address of the switch.

Status — The status of the component. Possible values are:

oNormal — The component is available and functioning properly.

oWarning — The component has detected an error. For switches, possible causes include:

A fan in the switch is not operating normally.

A sensor in the switch is detecting an abnormal temperature.

One of two power supplies in the switch is not connected.

One or more ports in the switch are malfunctioning.

oUnavailable — HCP does not have connectivity to the component.

HCP also reports a component as unavailable if it has not yet contacted the component for status information. To determine whether this is the reason for the unavailable status, refresh the Hardware Switches page in five minutes.

If the status of a component is unhealthy or if a component remains unavailable for more than five minutes, contact your authorized HCP service provider for help.

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

Adding a switch


To add a switch:

1.Click on the drop down menu located in the top right of the Switches tab and select the switch type you want to add.

2.Click on Add.

A new switch, highlighted in green, appears in the window.

3.Click on the Model drop down menu in the new switch, and select the applicable model.

4.Type the IP address.

5.Click on Update Settings.

Switches can be deleted by clicking on the garbage can icon on the left hand side of the switch and confirming that you want the switch removed.

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

About the Chassis tab


For HCP SAIN systems that use CB 320 servers, the HardwareChassis page shows the IPMI sensor information for the fans and power supplies on the server chassis. For information on IPMI sensor information, see IPMI information.

NoteWebHelp.png

Note:  HCP uses SNMP to retrieve the IPMI sensor information from the CB 320 servers. To enable this, for each server, you need to add the lowest-numbered storage node in the HCP system to the list of SNMP managers in the server configuration. To identify the node, use a valid [hcp_system] network IP address for the node. For the community name, use public.

If the lowest-numbered node changes at any time (for example, due to prolonged node unavailability or the addition of a node with a lower number), you need to update the each CB 320 server configuration accordingly.

For information on configuring CB 320 servers, see the applicable Hitachi documentation.

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