About the individual HCP G Series Node pages
On the General Node page contains information about the node’s hardware status and events.
page you can click any of the general nodes to go to their individual page. TheHardware status
The Hardware Status section of an individual General Node page summarizes the current operating conditions of various components of the node you’re examining, and provides links to more detailed information about each component.
To display more detailed information about a given component, click the table row containing the component summary. To hide the details, click on the row again.
If any component is malfunctioning, the Hardware Status section automatically displays detailed information about that component.
Logical volume usage details
When you click Logical volume usage, the Console displays the following information for each logical volume that’s managed by the node you’re currently viewing:
Volume ID
The logical volume type and ID and, for NFS volumes, the share path and the name of the extended storage pool that contains the NFS volume. The volumes are not necessarily listed in numeric order.
Status
The logical volume status.
Capacity
The total number of bytes of storage on the logical volume.
Used
The number of bytes of storage that are currently in use on the volume. This number includes bytes occupied by parts of in-progress multipart uploads, including replaced parts, parts uploaded for aborted multipart uploads, and unused parts of completed multipart uploads until these parts are automatically deleted by the Garbage Collection service.
Percent Used
The percentage of storage space that’s currently in use on the volume.
For HCP SAIN systems that also have internal storage, this display does not include the logical volumes on the internal drives.
Core hardware details
When you click Core hardware, the Console displays the following information about the core hardware for the node you’re currently examining:
Platform Hardware
The type of hardware used for the node:
- For a standalone server, this is the type of server, as reported by the server.
- For a blade in a CB 320 server, this is Hitachi Compute Blade 320.
- For a node in an HCP-VM system, this is VMware Virtual Platform.
Status
The status of the node. Possible values are:
Available
The node is running.
Unavailable
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.
Migrating
The Migration service is currently migrating data out of the storage managed by the node.
If the status of a node changes spontaneously from available to unavailable and the node does not restart automatically, contact your authorized HCP service provider. Do not attempt to restart the node manually; doing so could cause the loss of information needed to diagnose the problem.
Last Status Update Time
The time of the last update to the node status.
Node ID
The number assigned to the node.
[hcp_system]
All IPv4 and IPv6 addresses assigned to the node for the [hcp_system] network.
[hcp_management]
All IPv4 and IPv6 addresses assigned to the node for the [hcp_management] network.
[hcp_backend]
The IP address assigned to the node for the [hcp_backend] network.
Boot Time
The date and time the node last started.
Usage/Capacity
The total amount of storage space on all of the primary storage volumes managed by the node and the amount of that primary storage space that’s currently in use.
Memory
The amount of RAM in the node.
Swap
The status of the swappable memory in the node:
Using
The amount of storage set aside for swappable memory, in GB, and the percentage of that amount that’s currently in use
Pages In
The number of pages currently swapped in
Pages Out
The number of pages currently swapped out
Load Average
The average process workload on the node over the past minute, five minutes, and 15 minutes. The load average is based on all processes, regardless of their current state (for example, running, waiting for CPU time, or sleeping).
CPU
Make and model of the CPUs in the node, listed one per line. The CPUs are numbered and are listed in numeric order starting with CPU 0.
File systems on storage devices managed by a node
The Hardware Status section on the Storage Node page for any given node shows the number of file systems the node supports on primary storage and the number of physical storage devices to which those file systems are mapped. When you click x file systems on y storage devices, the Console displays the following information for each file system on the physical storage that’s managed by the node you’re currently examining:
- The directory path that identifies the file system
- Whether or not the file system is currently mounted
- Each level of mapping that ultimately associates the file system with one or more low-level block devices
- Some device diagnostic information, if available. For example, for configurations that include SSDs, the SSD expected write life remaining.
- Additional RAID-specific information, if available
Additionally, for SAIN systems, the details include this information for each low-level block device: vendor, array type, serial number, device number, and worldwide port number.
For SAIN systems, if multipathing is degraded, one or more of the low-level block devices will be missing from the display details.
IPMI information
Intelligent Platform Management Interface (IPMI) is a specification that defines a method of monitoring the internal hardware components of a server. If IPMI is implemented on a node, sensors in that node can detect abnormal conditions such as a high fan speed or a failed power supply.
The IPMI data that’s displayed on the Storage Node page for a given node is organized by sensor type. The list of sensors that you see for each sensor type depends on the specific IPMI implementation.
The details displayed, by sensor type, are:
Temperatures
For each temperature sensor, the current temperature reading, and for some sensors, the normal range for the temperature.
Power Supplies
For each power supply sensor, a text string read from the applicable power supply. If only one power supply is working, this section displays the message, No redundancy
Fans
For each fan sensor, the current fan speed.
Processors
For each processor sensor, a text string giving the status of the applicable processor.
Voltages
For each voltage sensor, the current voltage reading.
HCP does not report IPMI information for nodes in HCP-VM systems.
Network interface cards (NICs)
Each HCP node has two pairs of bonded ports:
- One pair of ports is used for connecting to the front-end networks, including the [hcp_system] network and all user-defined networks. These ports share all front-end network IPv4 and IPv6 addresses assigned to the node.
- One pair of ports is used for connecting to the back-end network. These ports share the back-end IP address assigned to the node.
The name assigned to each front-end and back-end port includes the NIC port number (for example, eth0 and eth1). By default, HCP uses the lower-numbered port in each bonded pair. If the lower-numbered port for a network fails, HCP automatically switches to the other port in the pair.
Optionally, depending on your HCP system hardware configuration, an HCP node may have an extra port connected to the management network. The name assigned to the management port is eth4.
On the Storage Node page for a given node, the Console displays information about each of the NICs in the node. The NIC information is organized by network. For each port assigned to a network, the Console displays these details:
Interface
The name assigned to the port.
Active
An indication of whether the port is available for use. Possible values are true and false.
Duplex
An indication of whether the port is full-duplex (full) or half-duplex (half).
Active in Bond
An indication of whether the port is currently the one being used. Possible values are true, false, and N/A.
Speed
The current rate of data transmission through the port.
Maximum Supported Speed
The maximum supported rate of data transmission for the port.
File system status
Each node in an HCP system has multiple file systems on its primary storage. At installation time, a fixed amount of space and a fixed number of inodes are allocated to each of those file systems. Each NFS volume associated with a node has a single file system with a fixed amount of space and a fixed number of inodes.
Inodes determine the total number of files and directories a file system can have. (These files and directories do not have a direct correspondence to the objects and directories that users create.)
On the Storage Node page for a given node, when you click the row that shows the file system status summary, the Console displays the following information about each file system on each primary storage volume and NFS volume that’s managed by the node:
Path
The directory path
Free 1K Blocks
The amount of available storage associated with the file system, in one-KB blocks
Total 1K Blocks
The total amount of storage associated with the file system, in one-KB blocks
Block Usage
The percent of the storage blocks currently in use
Inode Usage
The percent of the allocated inodes currently in use
Node events
The Node Events section on the Storage Node page for a given General Node lists all event messages logged for that node since the HCP system was installed. The list of messages in this section is a subset of the messages in the HCP system log. You can view all the messages in the system log in the All Events panel on the System Events page.
By default, the messages are listed ten at a time in reverse chronological order.