HQT-4420: Hitachi Content Platform InstallationDemo

HCP node replacement uses console access with the install account and the applicable SSH key. HCP documentation identifies install as the account for installation and node-management procedures, and notes that SSH keys are updated when nodes are swapped.

An HCP S31 maximum configuration consists of one 4U100 base enclosure and eight 4U106 expansion enclosures. The 4U100 serves as the base tray, while the eight 4U106 trays provide the supported maximum expansion.

An HCP S Series software update uses a two-step process: upload the update file, then apply it. Hitachi documentation specifies that this procedure can be performed in the HCP S Series Management Console or by using the management API. Among the available choices, the Management Console is the applicable method.

HCP 10GbE front-end connectivity supports XFP optical interfaces and SFP+ interfaces with either optical transceivers or copper Twinax cables. It does not use a Base-T interface or XFP copper cabling for this connection type.

HCP G11 supports 25 Gb network connectivity on both its front-end and back-end networks. The applicable support is specific to G11, so both G11 port combinations are valid.

Supported HCP G11 configurations include 10 GbE SFP+ connectivity for both the Front-End and Back-End networks, and a 25 GbE SFP+ Front-End with a 10 GbE SFP+ Back-End. The documented 1 GbE back-end configuration is paired with 10G BASE-T front-end ports, rather than with a 10 GbE SFP+ Front-End.

An HCP S10 node is equipped with 10 GbE SFP+ network interfaces and 1 GbE RJ45 management interfaces. XFP and non-plus SFP are not the specified S10 port types.

Data At Rest Encryption is configured cluster-wide during the initial HCP cluster configuration. It cannot be enabled afterward at an individual tenant level, through the service SSH key, or solely during node operating-system installation.

Host group security on Fibre Channel attached storage is configured with the host ports’ World Wide Port Names (WWPNs). A WWNN identifies the node, while host access authorization is applied to the individual port WWPNs.

An HCP S11 Compute Storage (CS) tray has two Intel-based server controllers, six SSD disks, and 30 HDD disks as its base configuration. A 42-HDD base configuration belongs to an expansion-storage tray rather than the CS tray.

For an HCP G10 node with six internal drives, the required layout is one RAID group containing one logical volume. This provides the node’s supported local-storage configuration across all six drives.

HCP G11 hardware is supported beginning with HCP software version 9.0. A mixed expansion that adds G11 nodes to an existing G10 system therefore requires HCP 9.0 at minimum.

Replacing an entire HCP G10 node can introduce hardware with BIOS settings that differ from the required HCP configuration. Validating the BIOS ensures the replacement node has the required platform and boot settings before it is returned to service.

HCP node additions are initiated through the HCP Configuration Menu’s HCP Setup workflow, and HCP upgrades may be performed online or offline. Capacity redistribution is not automatic: the Capacity Balancing service moves objects to balance storage after nodes are added and must be started manually by an authorized HCP service provider.

The HCP System Management Console URL format is https://admin.<hcp-domain-name>:8000; therefore, the applicable address is https://admin.hcp001.acme.com:8000.

HCP G10 metadata acceleration depends on the SSD option in each node to accelerate that node’s internal metadata and index workload. Installing SSDs on every node ensures metadata acceleration is available cluster-wide; nodes without SSDs would continue to handle that work on HDDs.

HCP data-at-rest encryption is enabled during installation by running the install program with root privileges. After it has been enabled, the encryption setting cannot be disabled. The encryption key is shown only once during installation, and SSH is not required to enable the feature.

Rawrite32 writes the installation ISO as a raw image to the USB drive, creating the required bootable installation media.

An HCP system with internal storage has a four-node starter configuration, and its isolated back-end network uses two redundant back-end Ethernet switches to connect the nodes. The HCP G10 is supported as a server model for HCP systems with internal storage.

Appliance OS installation configures each node’s front-end network by assigning its front-end IP address and specifying the front-end gateway IP address. External NTP server information is configured later as part of HCP system time settings, while BMC addressing is separate from the front-end Appliance OS network configuration.

The initial Hitachi Content Platform console credential uses the password Chang3Me!, including the uppercase C.