HCP S10 Node v2 2 0 Maintenance FE-HCPS002-17

Hitachi Content Platform S Series Node
2.2.0
HCP S10 Node Maintenance

This book is the service guide for the HCP S10 Node. The book contains instructions for maintaining the
physical components of an HCP S10 Node and for upgrading or reinstalling the HCP S Series operating
system and software. The book includes instructions for adding drives to increase capacity and for replacing
faulty components. The book also contains information about monitoring HCP S10 Nodes. Additionally, the
book describes the physical specifications of and environmental requirements for HCP S10 Nodes.
FE-HCPS002-17
July 2021
© 2014, 2021 Hitachi Vantara LLC. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording, or
stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Vantara LLC
(collectively, “Hitachi”). Licensee may make copies of the Materials, provided that any such copy is: (i) created as an essential step in utilization of the
Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials.
"Materials" mean text, data, photographs, graphics, audio, video, and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the
most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about
feature and product availability, or contact Hitachi Vantara LLC at https://support.hitachivantara.com/en_us/contact-us.html.
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi
products is governed by the terms of your agreements with Hitachi Vantara LLC.
By using this software, you agree that you are responsible for:
1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals; and
2. Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S.
Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply
strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and
any Compliant Products.
Hitachi and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/390,
PowerHA, PowerPC, RS6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z14, z/VM, and z/VSE are registered trademarks or trademarks
of International Business Machines Corporation.
Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook,
PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure,
Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation.
Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or web site are properties of their respective owners.
Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found at
https://www.hitachivantara.com/en-us/company/legal.html.
HCP S10 Node Maintenance 2

Contents
Preface 9
Intended audience 9
Product version 9
Release notes 9
Syntax notation 9
Related documents 10
Accessing product documentation 11
Getting help 11
Comments 11
Change list 12
Chapter 1: HCP S10 Node overview 14
HCP S Series Nodes 14
S10 Node hardware components 15
S10 Node product offerings 16
S10 Node rack options 16
S10 Node power distribution options 17
S10 Node connectivity options 18
Chapter 2: HCP S10 Node physical requirements 19

Mechanical details 19
Dimensions 19
Weights 20
Cables 21
Customer-supplied racks 22
Electrical details 24
Power system 24
Power connections 25
Electrical specifications 26
Environmental details 27
RoHS compliance 27
BNST compliance 27
Temperature, humidity, and altitude 27
Shock and vibration 28
Cooling and airflow 29

Acoustics 30
Chapter 3: Preparing for HCP S10 Node maintenance 31

HCP S Series Node tools file 31
Installing and uninstalling the VCP serial port driver 32
Installing the VCP serial port driver on your laptop computer 32
Uninstalling the VCP serial port driver on the laptop computer 33
Installing and using PuTTY on your laptop computer 33
Installing PuTTY and Pageant 34
Adding an S Series Node SSH key to your SSH keychain 35
Using a PuTTY serial connection 35
Using a PuTTY SSH connection 36
Reconfiguring your laptop computer for SSH access 37
Using PuTTY for SSH access over an Ethernet connection 38
Installing Rawrite32 on your laptop computer 39
Preparing an installation USB flash drive or DVD 40
Downloading the HCP S Series ISO image file 40
Burning the HCP S Series installation ISO image to a USB flash drive or
DVD 41
Reformatting bootable USB flash drives 42
Chapter 4: Configuring an HCP S Series Node in DNS 44

Zone definitions for an S Series Node 44
Configuring a forward lookup zone in Windows 45
Configuring a forward lookup zone in Unix 46
Verifying the DNS configuration 48
Chapter 5: Monitoring an HCP S10 Node 49

Management Console hardware information 50
Physical component status indicators 50
Enclosure LEDs 50
Power and cooling module LEDs 52
Server module LEDs 52
Enclosure audible alarm 53
Beaconing 53
Internal logs 55
Inserting comments into the internal logs 55
Downloading the internal logs 55
Configuring HCP S Series Node monitoring with the Hitachi Remote Ops
monitor agent 57
Chapter 6: Maintaining the HCP S Series operating system and software 59

Updating the HCP S Series OS and software 59

HCP S Series Node update files 60
Downloading an upgrade or hotfix file from TISC 60
Considerations for software updates 61
Step 1 (conditional): Verify the enclosure VPDs 61
Step 2: Upload the update file 64
Step 3 (conditional): Run the update prechecks 64
Step 4: Apply the update 64
Reinstalling the HCP S Series OS and software 65
What you need for reinstalling the HCP S Series OS and software 65
Step 1: Prepare for the software reinstallation 66
Step 2 (conditional): Verify the enclosure VPDs 67
Perform the OS and software reinstallation 69
Performing a default software reinstallation 70
Performing a custom software reinstallation 78
Software reinstallation prechecks 91
Step 3: Verify the software reinstallation 93
Software reinstallation in progress 94
Successful software reinstallation 94
Unsuccessful software reinstallation 95
Step 4: Run the post-install script 97
Step 5: Configure the S Series Node 99
Step 6 (conditional): Have the customer enable SSH access to the server
modules 100
Recovering a server module 101
What you need for recovering a server module 101
Step 1: Prepare for the server-module recovery 102
Step 2: Reconfigure the server module you want to recover 103
Step 3: Reinstall the HCP S Series OS on the server module 108
Step 4: Reinstall the HCP S Series software on the server module 112
Chapter 7: Maintaining data and database drives 114

Considerations for maintaining data and database drives 115
Adding data and database drives 115
What you need for adding drives 115
Step 1: Start the drive addition procedure 116
Step 2: Insert the new drives into the selected slots 117
Step 3: Verify the drive addition 119
SAS address errors 121
Removing data and database drives 122
What you need for removing drives 122
Step 1: Start the drive removal procedure 122
Step 2: Remove the drives from the selected slots 123

Step 3: Verify the drive removal 125
Replacing data and database drives 125
What you need for replacing drives 126
Step 1: Start the drive replacement procedure 126
Step 2: Replace the drives in the selected slots 127
Step 3: Verify the drive replacement 129
Chapter 8: Maintaining the enclosure 132

Replacing a power and cooling module 132
What you need for replacing a power and cooling module 133
Step 1: Remove the old power and cooling module from the enclosure 133
Step 2: Insert the new power and cooling module into the enclosure 133
Replacing the front panel and light pipe assembly 134
What you need for replacing the front panel and light pipe assembly 134
Step 1: Remove the old front panel and light pipe assembly from the
enclosure 134
Step 2: Attach the new front panel and light pipe assembly to the
enclosure 135
Replacing a cable management arm 136
What you need for replacing a cable management arm 136
Step 1: Prepare to replace the cable management arm 137
Step 2: Disconnect the power and Ethernet cables and detach the old
cable management arm 137
Step 3: Move the cables from the old cable management arm to the new
cable management arm 139
Step 4: Attach the new cable management arm and reconnect the
Ethernet and power cables 141
Replacing enclosure rails 142
What you need for replacing enclosure rails 143
Enclosure rail kit 143
Step 1: Power off the S10 Node 144
Step 2: Disconnect the power and Ethernet cables and detach the cable
management arms 145
Step 3: Remove the enclosure from the rack 147
Step 4: Separate the inner and outer rails in the new enclosure rail kit 148
Step 5: Determine which rails to replace 148
Step 6 (conditional): Replace the inner rails on the enclosure 149
Step 7 (conditional): Replace the outer rails in the rack 149
Step 8: Move the enclosure back into the rack 153
Step 9: Reattach the cable management arms and reconnect the Ethernet
and power cables 154
Replacing the enclosure 155
What you need for replacing the enclosure 155

Step 1: Start the enclosure replacement procedure 156
Step 2: Unpack the new enclosure 156
management arms 157
Step 4: Remove the old enclosure from the rack 158
Step 5: Move the inner rails from the old enclosure to the new enclosure 160
Step 6: Move the power and cooling modules from the old enclosure to
the new enclosure 160
Step 7: Move the server modules from the old enclosure to the new
enclosure 161
Step 8: Move the data and database drives from the old enclosure to the
new enclosure 162
Step 9: Swap the right sides of the enclosure covers between the two
enclosures 162
Step 10: Move the new enclosure into the rack 163
Step 11: Reattach the cable management arms and reconnect the
Ethernet and power cables 165
Step 12: Verify the enclosure replacement 166
Step 13: Verify the enclosure VPDs 167
Step 14: Check and, if necessary, update the SAS expander firmware on
the new enclosure 169
Checking and updating firmware while the S10 Node remains
available 169
Checking and updating firmware with S10 Node unavailability 170
Step 15 (conditional): Check the health of the S10 Node 171
Chapter 9: Maintaining server modules 173

Determining what to replace 173
Server module Ethernet ports 174
Degraded OS SSD 174
Nonfunctioning server module 176
Replacing a server module 177
What you need for replacing a server module 177
Step 1 (conditional): Shut down the server module you want to replace 178
Step 2: Remove the old server module from the enclosure 179
Step 3: Move the old SSDs or insert new SSDs 179
Moving the SSDs from the old server module to the new server
module 180
Inserting new SSDs into the new server module 180
Step 4: Insert the new server module into the enclosure 181
Step 5: Check and, if necessary, update the firmware on the new server
module 182
Step 6 (conditional): Recover the new server module 183
Step 7 (conditional): Check the health of the S10 Node 183

Replacing one or both SSDs in a server module 183
What you need for replacing one or both SSDs in a server module 184
Step 1: Shut down the server module 184
Step 2: Remove the server module from the enclosure 185
Step 3: Replace the SSD or SSDs 185
Step 4: Reinsert the server module into the enclosure 186
Step 5: Check and, if necessary, update the firmware on the new SSD or
SSDs 187
Step 6: Configure the new SSD or recover the server module 188
Replacing the server interconnect cable 188
What you need for replacing a server interconnect cable 189
Replace the server interconnect cable 189
Chapter 10: Maintaining PDUs 190

Hitachi Universal V2 PDUs 190
Power-cable connections with Hitachi Universal V2 PDUs 191
Power-cable connections with Hitachi Vantara-supplied horizontal PDUs 193
PDU outlet correspondences 195
Replacing a PDU 196
What you need for replacing a PDU 196
Replace the PDU 197
Removing a Hitachi Vantara-supplied horizontal PDU from a rack 198
Installing a Hitachi Vantara-supplied horizontal PDU in a rack 198
Chapter 11: Using the system service tools 200

About the system service tools 200
cluster_ssh 201
cluster_ssh parameter descriptions 201
cluster_ssh examples 203
cluster_get 206
cluster_get parameter descriptions 207
cluster_get examples 208
cluster_put 211
cluster_put parameter descriptions 211
cluster_put examples 212
Appendix: HCP S Series Node Configuration Information form 214

HCP S Series Node Configuration Information 215

Preface
This book is the service guide for the Hitachi Content Platform (HCP) S10 Node.
The book contains instructions for maintaining both the S10 Node hardware and the HCP S
Series software that's installed on the S10 Node. The book also describes the physical
specifications of and environmental requirements for an S10 Node and explains how to
gather S10 Node status information.
Intended audience
This book is intended for people who are responsible for maintaining S10 Nodes that are
deployed at customer sites. The book assumes that you have experience working with both
the hardware and software of computer systems.
Product version
This book applies to release 2.2.0 or later of the HCP S Series Node.
Release notes
Read the release notes before installing and using this product. They may contain
requirements or restrictions that are not fully described in this document or updates or
corrections to this document. Release notes are available on Hitachi Vantara Support
Connect:
https://knowledge.hitachivantara.com/Documents
Syntax notation
The table below describes the conventions used for the syntax of commands in this book.
Notation Meaning Example
boldface Type exactly as it appears in This book shows: cluster_ssh.py

the syntax (if the context is You enter: cluster_ssh.py
case insensitive, you can
vary the case of the letters
you type)
Preface
Related documents
(Continued)
Notation Meaning Example
italics Replace with a value of the This book shows: username

indicated type You enter: root
| Vertical bar — Choose one This book shows: -h|--help

of the elements on either You enter: -h
side of the bar, but not both or: --help
[] Square brackets — Include This book shows: [-v|--verbose]

none, one, or more of the You enter: -v
elements between the or: --verbose
brackets or nothing
() Parentheses — Include This book shows: (-T|--max_threads)

exactly one of the elements You enter: -T
between the parentheses or: --max_threads
Related documents
The following documents contain additional information about HCP S Series Nodes:
• HCP S Series Node Help (MK-HCPS000) — This Help system contains information
about configuring, monitoring, and managing an HCP S10 or S30 Node.The Help
includes information you need to effectively use the HCP S Series Management
Console. The Help also describes the physical specifications of and environmental
requirements for S10 and S30 Nodes. Additionally, the Help contains a complete
reference for the HCP S Series management API.
• HCP S10 and S30 Node API Reference (MK-HCPS004) — This book contains all the
information you need for using the HCP S Series management API with an HCP S10 or
S30 Node. This RESTful HTTP-based API enables you to configure, monitor, and
manage an S10 or S30 Node programmatically. The book explains how to use the
management API to retrieve information about and manipulate S10 and S30 Node
resources. The book also includes an introduction to the S Series Node concepts that
underlie the management API resources.
• HCP S30 Node Maintenance (FE-HCPS010) — This book contains instructions for
maintaining the physical components of an HCP S30 Node and for upgrading or
reinstalling the HCP S Series operating system and software. The book includes
instructions for adding drives and enclosures to increase capacity and for replacing faulty
components. The book also contains information about monitoring S30 Nodes.
Additionally, the book describes the physical specifications of and environmental
requirements for S30 Nodes.
• Cabling Enclosures in an HCP S30 Node (FE-HCPS012) — This Help system contains
diagrams showing the SAS cable connections for each possible enclosure in an HCP
S30 Node. The Help steps through the diagrams in the order in which the enclosures
should be cabled.
• HCP S Series Node Refurbishment (FE-HCPS013) — This book contains complete

instructions for refurbishing the components of an HCP S10 Node or S30 Node that has
been returned to the Hitachi Vantara distribution center. Refurbishing returns the
Preface
Accessing product documentation
components to a condition in which they can be used either in new S Series Nodes or as
replacement parts for existing S Series Nodes.
• HCP S Series Node Troubleshooting (FE-HCPS007) — This book contains information

to help you support installations of HCP S10 or S30 Nodes at customer sites. The book
describes methods for identifying and resolving issues with various S10 or S30 Node
components. The book also includes information about some internal S Series Node
processes.
Accessing product documentation

Product documentation is available on Hitachi Vantara Support Connect:
https://knowledge.hitachivantara.com/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release of
the product.
Getting help
Hitachi Vantara Support Portal is the destination for technical support of products and
solutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi Vantara
Support Connect for contact information: https://support.hitachivantara.com/en_us/contact-
us.html.
Hitachi Vantara Community is a global online community for Hitachi Vantara customers,
partners, independent software vendors, employees, and prospects. It is the destination to
get answers, discover insights, and make connections. Join the conversation today! Go to
community.hitachivantara.com/s, register, and complete your profile.
Note: If the customer purchased the HCP S Series Node from a third party, please contact
the applicable HCP support center.
Comments
Please send us your comments on this document to doc.comments@hitachivantara.com.
Include the document title and part number, including the revision (for example, -01), and
refer to specific sections and paragraphs whenever possible. All comments become the
property of Hitachi Vantara LLC.
Thank you!
Preface
Change list
The table below outlines the significant differences between this version of HCP S10 Node
Maintenance and the previous version.
Chapter Differences
Chapter 1: HCP S10 Node overview Adds the Hitachi Universal V2B rack as a racking option
Chapter 3: Preparing for HCP S10 Node • Updates PuTTY to version 0.73
maintenance
• Updates Rawrite32 to version 1.0.6.0
• Adds the option to put the HCP S Series OS and software

installation files on a DVD instead of on a USB flash drive
• Updates the format of HCP S Series OS and software

installation .ISO image file names
• Adds instructions for using Rufus to reformat bootable USB

drives
Chapter 4: Configuring an HCP S Series New chapter: explains how to configure an S Series Node in DNS
Node in DNS
Chapter 5: Monitoring an HCP S10 Node Adds information about configuring an S Series Node monitoring
with the Hitachi Remote Ops monitor agent
Chapter 6: Maintaining the HCP S Series • Explains that upgrading an S Series Node to release 2.2.0
operating system and software entails approximately 20 minutes of downtime
• Updates the formats of software upgrade and hotfix file names
• Removes information about database conversion from

considerations for software updates because that information is
no longer applicable
• Adds instructions for running update prechecks independently

of updating the HCP S Series OS and software
• Adds the "free space for update of internal database," "repair

backlog," and "services" prechecks for OS and software
updates
• Corrects the number of OS and software installation USB drives

needed for reinstalling from two drives to one
• Adds the option to use a DVD instead of a USB flash drive to

install the HCP S Series OS and software
• Changes the default for data in-flight encryption from disabled

to enabled
Change list
(Continued)
Chapter Differences
• Changes the default for SSH access from enabled to disabled
• Adds instructions for using the first-time setup wizard to

configure the S Series Node
• Adds an optional instruction to have the customer enable SSH

access after an OS and software reinstallation
• Adds instructions for recovering a server module
Chapter 7: Maintaining data and Explains that the S Series Node can continue to process drives for
database drives reuse after an add drives or replace drives operation is complete
Chapter 9: Maintaining server modules • Updates the lsscsi command used to identify OS SSDs
• Adds instructions for checking firmware versions after replacing

a single OS SSD or both OS SSDs
• Updates the part number for the server interconnect cable
Appendix: HCP S Series Node New appendix: contains a form for recording the information needed
Configuration Information form for performing a custom reinstallation of the HCP S Series OS and
software, configuring the S Series Node for the customer
environment, or recovering a server module
Change list
Chapter 1: HCP S10 Node overview
The Hitachi Content Platform (HCP) S10 Node, which is a type of HCP S Series
Node, is one of the storage products offered by Hitachi Vantara. This chapter contains a
general description of S Series Nodes and provides information about these aspects of the
S10 Node:
• Hardware components
• Product offerings
• Rack options
• Power distribution options
• Connectivity options
HCP S Series Nodes

An HCP S Series Node is a highly efficient, highly available, cost-effective storage device
that supports very large amounts of data. Each S Series Node consists of two cooperating
server modules and multiple high-density drives in some number of enclosures.
During normal operation, the two server modules in an S Series Node actively share
responsibility for all S Series Node functions. Because the server modules are peers, if one
module becomes unavailable, the other can still provide full, uninterrupted S Series Node
functionality, although performance may be degraded.
The S Series Node data storage implementation ensures that data is well-protected through
the use of erasure coding. Additionally, S Series Nodes use several internal processes to
continuously check the integrity of both the stored data and the storage media.
S Series Nodes can provide direct-write storage for HCP systems and for HCP for cloud
scale systems. S Series Nodes can also serve as storage tiering platforms for HCP
systems. A single HCP system or HCP for cloud scale system can seamlessly store data
across multiple S Series Nodes, thereby enabling scalability in both capacity and
performance.
Important: HCP and HCP for cloud scale are the only supported clients for the S Series
Node.
HCP systems and HCP for cloud scale systems use the S Series Node implementation of
the Hitachi API for Amazon S3® to write, retrieve, and otherwise manage objects in an S
Series Node. This RESTful, HTTP-based API is compatible with Amazon S3.

S10 Node hardware components
For administrative purposes, S Series Nodes provide a web-based Management Console

and a RESTful, HTTP-based management API. Using these interfaces, S Series Node
administrators and service providers can configure, manage, and monitor an S Series Node.
These interfaces can also be used to initiate and verify certain S Series Node hardware
procedures, such as adding and replacing drives.
The current S Series Node models are the S11 Node and the S31 Node. The S31 Node has
more processing power and memory than the S11 Node. Additionally, while the S11 Node
supports at most two enclosures, the S31 Node can support as many as nine, thereby
providing significantly more storage capacity than the S11 Node.
The older S Series Node models are the S10 Node and the S30 Node. The enclosures used
in S11 and S31 Nodes can hold more drives than the enclosures used in S10 and S30 Nodes
can hold. Also, S11 and S31 Nodes support higher-capacity drives than S10 and S30 Nodes
support.
The S11 and S31 Node enclosures are not interchangeable with the S10 and S30 Node
enclosures.
S10 Node hardware components

An HCP S10 Node consists of these hardware components:
• NDS-4600 enclosure — The enclosure is a container for the power and cooling
modules, server modules, and hard disk drives associated with an S10 Node.
• Rail kit — The rail kit, with left and right extension brackets, is used to mount the
enclosure in a standard nineteen-inch rack.
• Two cable management arms — The cable management arms, with left and right
extension brackets, are used to neatly arrange the power and network cables for the S10
Node and to keep the cables securely connected to the enclosure. These cables connect
the server modules and power and cooling modules in the enclosure to the power
distribution units (PDUs) and customer network.
• Front panel and light pipe assembly — The front panel and light pipe assembly
attach to the front of the enclosure.
• Two power and cooling modules — The power and cooling modules, installed in the
rear of the enclosure, provide power and cooling for the enclosure and its components.
• Two server modules — The active-active server modules, installed in the rear of the
enclosure, run the software that manages the S10 Node, provide data access, and
ensure data protection.
In the HCP S Series Management Console, in some cases, server module 1 is
represented as IOM A, and server module 2 is represented as IOM B. This convention
reflects the low-level hardware implementation.
• SATA or SAS hard disk drives (HDDs) for storing data — These SATA or SAS
drives, with drive carriers, store the data written to the S10 Node. A new S10 Node has
either 28 or 56 SATA or SAS data drives.
• Four SAS hard disk drives for storing the internal database — These SAS drives,
with drive carriers, store the internal database used by the S10 Node to hold information
such as user account and bucket definitions and various configuration settings. Like the
SATA or SAS data drives, the SAS database drives can also store data written to the
S10 Node.

S10 Node product offerings
• One-foot CAT6 Ethernet cable — The purple one-foot CAT6 Ethernet cable, which is
called the server interconnect cable, is used to connect the two server modules to each
other for synchronization and resource sharing purposes.
• Two IEC 320 C19 to IEC 320 C20 power cables — The two 2-meter C19-to-C20
power cables are used to connect the power and cooling modules in the enclosure to two
different PDUs.
An S10 Node comes with a 4GB USB flash drive and a USB-to-mini-USB cable for
authorized service personnel to use at the customer site for maintenance procedures.
Important: Be sure to keep the USB flash drive in a safe place in case the drive is needed
for a service procedure.
S10 Node product offerings

S10 Nodes are available in these configurations:
• Half-populated with twenty-eight 6TB SATA or SAS data HDDs and four 6TB SAS
database HDDs
• Fully populated with fifty-six 6TB SATA or SAS data HDDs and four 6TB SAS database
HDDs
• Half-populated with twenty-eight 10TB SAS data HDDs and four 10TB SAS database
HDDs
• Fully populated with fifty-six 10TB SAS data HDDs and four 10TB SAS database HDDs
The table below shows the total storage capacity for the possible configurations of a new
S10 Node.
S10 Node Number of Number of

configuration HDD capacity data HDDs database HDDs Total capacity
Half populated 6 TB 28 4 192 TB
Fully populated 6 TB 56 4 360 TB
Half populated 10 TB 28 4 320 TB
Fully populated 10 TB 56 4 600 TB
Note: Due to internal storage requirements, the capacity available for storing data is less
than the total capacity provided by the SATA and SAS HDDs.
S10 Node rack options

An S10 Node can be mounted in a Hitachi Universal V2B or V2 rack or a customer-supplied
rack. Customers who already have an HCP system in a rack with enough available space,
weight capacity, and power capacity can install the S10 Node in that rack.

S10 Node power distribution options
To ensure the successful installation of an S10 Node, a customer-supplied rack must meet
the requirements specified in "Customer-supplied racks" on page 22.
S10 Node power distribution options

An S10 Node is designed for redundant power systems. Therefore, the two power and
cooling modules should be connected to different PDUs. The power systems and PDUs
must deliver 200V to 240V. Each PDU should be powered from a separate, appropriately
rated circuit.
The power and cooling modules have IEC 320 C20 inlets and require PDUs with IEC 320
C19 outlets. Each power and cooling module connects to a PDU using an eight-foot (two-
meter) IEC 320 C19 to IEC 320 C20 power cable.
New PDUs supplied by Hitachi Vantara are Hitachi Universal V2 PDUs, which are installed
vertically in a rack. The PDUs supplied with older S10 Nodes were 1U horizontal PDUs.
S10 Nodes can be racked with existing HCP systems. These systems may not have PDUs
with the required IEC 320 C19 outlets. Customers can order the correct PDUs from Hitachi
Vantara.
The table below describes the Hitachi Universal V2 PDUs.
Hitachi Vantara
replacement part C13 C19
number Geography Phase Description Outlets Outlets
1P30A-8C13-3C19UL.X Americas Single 208V, 30A, NEMA L6-30P 8 3
3P30A-8C13-3C19UL.X Americas Three 208V, 30A, NEMA L15-30 8 3
1P32A-9C13-3C19CE.X EMEA/APAC Single 230V, 32A, IEC309 2P+E 9 3
3P16A-9C13-3C19CE.X EMEA/APAC Three 400V, 16A, IEC309 3P+N+E 9 3
The table below describes the Hitachi Vantara-supplied horizontal PDUs used with older S10
Nodes.
Hitachi Vantara
replacement C13 C19
part number Geography Phase Description outlets outlets
PDU-063112F10.X Americas Single 208V, 30A, NEMA L6-30 0 6
PDU-063315F10.X EMEA/APAC Single 230V, 32A, IEC 60309 0 6
Under certain circumstances, PDUs not listed in the tables above may be supported. If you
have questions about specific PDUs, check with your HCP support center.

S10 Node connectivity options
S10 Node connectivity options

An S10 Node has two networks for connecting to the customer network — an access
network and a management network:
• For the access network, each server module has two bonded 10Gb Ethernet SFP+
ports. These ports can be configured as active-active (802.3ad) or active-backup. To
create a highly available infrastructure, the ports can be connected to different physical
switches.
• For the management network, each server module has one 1Gb Ethernet 1000Base-T
port.
Both the access network and the management network can be used for management
functions. Only the access network can be used for data access.
To meet customer network connectivity requirements for the S10 Node access network,
these additional components are available from Hitachi Vantara:
• 1Gb SFP+ module — If a 1Gb Ethernet network, 1Gb SFP+ modules are required for
the access network connections. This module has an RJ45 connector. Hitachi Vantara
offers 1Gb SFP+ modules from both Brocade and Cisco.
• 10Gb SFP+ optical transceiver — If using fiber optic cables for the access network
connections, a 10Gb SFP+ optical transceiver is required on both ends of each fiber
optic cable. The 10Gb SFP+ optical transceiver has an LC type connector. Hitachi
Vantara offers a 10Gb SFP+ optical transceiver from Intel®.
• Multimode fiber optic cable — If a 10Gb Ethernet network and the distance between
the enclosure and the Ethernet switches is greater than 10 meters, fiber optic cables
must be used for the access network connections. Hitachi Vantara offers multimode
fiber optic cables in various lengths in both plenum and LSZH jacketing.
• 10Gb Twinax cable — If a 10Gb Ethernet network and the distance between the
enclosure and the Ethernet switches is less than 10 meters, Twinax cables can be used
instead of fiber optic cables for the access network connections. Hitachi Vantara offers
10Gb Twinax cables in various lengths from both Brocade and Cisco.

Chapter 2: HCP S10 Node physical requirements
This chapter describes the physical specifications of and environmental requirements for an
HCP S10 Node.
Mechanical details
The following sections describe the mechanical specifications and requirements for an S10
Node.
Dimensions
The labels in the figure below identify the faces of an S10 Node enclosure. Use this figure as
a reference for the table of dimensions that follows.

Mechanical details
The table below shows the physical dimensions of the enclosure.
Parameter Inches Millimeters
Enclosure depth — rack 34.0 863.6

mounting surface to rear
connector surface
Total depth — front surface of 40.0 (minimum) 1,016.0 (minimum)

front panel to end of cable
42.0 (with extension 1,066.8 (with extension
management arms
brackets) brackets)
Front width 16.56 420.6
Front width with rack ears 19.0 482.6
Rear width 17.6 446.0
Height (4U) 6.97 177.0
The Hitachi Universal V2B and V2 racks have the same physical dimensions as each other.
The table below shows these dimensions.
Parameter Inches mm
Width 23.63 600
Depth 47.25 1200
Height 79.06 2008
Weights
The table below shows the weights of various configurations of an S10 Node. Each weight
includes the enclosure, all the components inside the enclosure, the inner and outer
enclosure rails, and the enclosure power cables.
The weights shown do not include the PDUs or the rack required for mounting an S10 Node.
The weights of these components are shown at the end of this section.
S10 Node configuration Weight in lbs. Weight in kg
S10 Node half populated with 4TB drives 167.04 75.78
S10 Node fully populated 4TB drives 212.40 96.36
S10 Node fully populated with thirty-two 4TB drives 219.12 99.41
and twenty-eight 6TB drives
S10 Node fully populated with 6TB drives 226.56 102.78

Mechanical details
(Continued)
S10 Node configuration Weight in lbs. Weight in kg
S10 Node fully populated 10TB drives 217.00 98.45
S10 Node fully populated with thirty-two 6TB drives 222.36 100.88
and twenty-eight 10TB drives
Caution: Due to the weight of an enclosure, you should always use a lift when installing or
uninstalling an enclosure in a rack.
The table below shows the weight of an empty Hitachi Universal V2B rack, an empty Hitachi
Universal V2 rack, a Hitachi Universal V2 PDU, and a Hitachi Vantara-supplied horizontal
PDU.
Component Weight in lbs. Weight in kg
Empty Hitachi Universal V2B rack, including 234.53 106.38

accessory kit
Brake handle for Hitachi Universal V2B rack 2.00 0.91
Empty Hitachi Universal V2 rack, including accessory 225.53 102.30

kit
Americas Hitachi Universal V2 single-phase PDU 7.94 3.60
Americas Hitachi Universal V2 three-phase PDU 8.82 4.00
EMEA/APAC Hitachi Universal V2 single-phase PDU 7.05 3.20
EMEA/APAC Hitachi Universal V2 three-phase PDU 7.05 3.20
Hitachi Vantara-supplied 1U horizontal PDU 9.90 4.49
Cables
Each power cable and Ethernet cable (except the server interconnect cable) for an S10 Node
must be long enough such that 36 inches (914 mm) can be allocated to the portion of the
cable that goes from the point at which the cable is secured to the rack, through the
applicable cable management arm, to the point at which the cable connects to the back of the
enclosure. This ensures that the enclosure can be pulled partially out of the rack for servicing
without the need to disconnect the cables.
Note: The cable management arms are a required component of an S10 Node.

Mechanical details
Customer-supplied racks
Customers can mount an S10 Node in a rack that they supply. A customer-supplied rack
must meet these requirements:
• The rack must be a standard 19-inch rack.
• The rack must have square holes in the vertical EIA rails.
• The rack depth must be at least 43.3 inches (1,100 mm). The use of cable management
arms, which are required with the enclosure, forces this depth requirement.
• To support the enclosure rail kit, the distance between the front and rear vertical EIA rails
in the rack must be a minimum of 20 inches (508 mm) and a maximum of 30.5 inches
(775 mm). For maximum stability, this distance should not be less than 24 inches (610
mm).
If the distance is less than or equal to 28.5 inches (724 mm), the rails can be used
without rail extenders and cable management arm extenders. If the distance is greater
than 28.5 inches, rail extenders and cable management arm extenders are required.
• The distance between the left and right vertical EIA rails must be a minimum of 18.5
inches (470 mm) wide for the entire depth of the rack, as shown below.

Mechanical details
The figure below shows the dimensions and clearances required for mounting an S10 Node in
a customer-supplied rack. In the figure, the rails are used without the two-inch rail extenders
and two-inch cable management arm extenders, which allow the distance between the front
and rear vertical EIA rails to be two-inches greater than what the diagram shows.
The figure below shows an S10 Node installed in a rack.

Electrical details
Electrical details
The following sections describe the power requirements and electrical specifications for an
S10 Node.
Power system
For redundancy, an S10 Node has two power and cooling modules power supplies. These
modules should be connected to two different PDUs, which should be plugged into two
separate power sources. This setup ensures that the entire power system has no single point
of failure.
If only one power source is available, the two PDUs should be plugged into different circuits.
If only one circuit is available, the two power and cooling modules can be connected to the
same PDU as a last resort, assuming the PDU has two available outlets and enough power
capacity.
The power system input can be either single-phase or three-phase with single phase on the
outlets.
The table below shows the power system requirements for the Hitachi Universal V2 PDU.
Geography Phase Length Voltage Amperage
Americas Single 24.49in (622mm) 208 30
Americas Three 24.49in (622mm) 208 30
EMEA/APAC Single 23.46in (596mm) 230 32
EMEA/APAC Three 23.46in (596mm) 400 16
The table below shows the power system requirements for the Hitachi Vantara-supplied
horizontal PDU.
Hitachi Vantara
replacement
part number Geography Phase Voltage Amperage
PDU-063112F10.X Americas Single 208 30
PDU-063315F10.X EMEA/APAC Single 230 32

Electrical details
Power connections
The power connections required by the Hitachi Universal V2 PDUs differ by geography and
input phase:
• For the Americas:

¡ The single-phase, 208V, 30A PDU has a NEMA L6-30P three-wire plug, as shown
below.
¡ The three-phase, 208V, 30A PDU has a NEMA L15-30 four-wire plug, as shown
below.
• For EMEA/APAC:
¡ The single-phase, 230V, 32A PDU has an IEC 309 three-wire plug, as shown below.
¡ The three-phase, 400V, 32A PDU has an IEC309 five-wire power plug, as shown
below.

Electrical details
Electrical specifications
When an S10 Node is operating normally, each power and cooling module supplies half the
power that the S10 Node requires. However, if one power and cooling module is unavailable,
the S10 Node can run on the other power and cooling module alone.
The table below outlines the electrical specifications for a power and cooling module in an
S10 Node. The power system at the customer site should be sized appropriately for the
number of S10 Nodes installed at the site.
Parameter Value
Input voltage 190 to 264 VAC
Input frequency 47 to 63 Hz and 400 Hz
Maximum input current 12.4A RMS @ 190 VAC
Peak inrush current 50A @ 230 VAC, 25°C, 5 milliseconds

maximum
Typical input current 76.1% of maximum input current
Harmonic distortion (power factor) Per EN61000-3-2
Minimum efficiency (measured at 190 VAC 87%

and full output load); not including power
required for internal fans.
Minimum efficiency (measured at 30% and 90%

50% load and nominal line @ 208 VAC); not
including power required for internal fans
Maximum average output power 1,865 W
Maximum peak output power (one second) 2,065 W
Typical average output power 1,420 W
Maximum AC leakage current 1.7 mA at 60 Hz; 11.4 mA at 400 Hz
Emissions EN55022 10 dB margin for conducted emissions when

tested at system level
FCC 47 CFR Part 15 Class A
10 dB margin for radiated emissions when
EN55022, Class A tested at system level
EN61000-3-2 Harmonic Emissions, Class A
EN61000-3-3 Flicker Disturbance, Class A

Environmental details
(Continued)
Parameter Value
Immunity EN55024
EN61000-4-2 Electrostatic discharge
EN61000-4-3 Radiated electromagnetic field
EN61000-4-4 Burst, electrical fast transients
EN61000-4-5 Surge transients
EN61000-4-6 Conducted disturbances
EN61000-4-11 Power line interruption
The following sections describe the environmental specifications and requirements for an
S10 Node.
RoHS compliance
An HCP S10 Node, including all its components, is compliant with the European Union
Restriction of Hazardous Substances (RoHS) Directive (Directive 2002/95/EC), with no
exceptions or exemptions.
BNST compliance
Benzenamine, N-phenyl-, reaction products with styrene and 2,4,4-trimethylpentene (BNST)
is an antioxidant used as an additive in many industrial lubricants. Its use has been restricted
in Canada under the Prohibition of Certain Toxic Substances Regulations, 2012, which went
into effect on March 14, 2013. The Regulations include a two-year exemption for BNST used
in small-application lubricants in the electrical and electronics engineering industry.
In an HCP S10 Node, the components that use small-application lubricants are the fans in
the power and cooling modules, the fans in the server modules, and the hard disk drives. If
such a component is labeled with a manufacturing date of March 14, 2015 or later, the
component does not contain BNST and is in compliance with the Regulations. If such a
component is labeled with a manufacturing date earlier than March 14, 2015, the component
is not subject to the Regulations.
Temperature, humidity, and altitude

The table below shows the acceptable ranges for temperature and humidity and the derating
for altitude for a fully populated S10 Node enclosure under these conditions:
• Normal operation
• Powered off in a data center
• In transit

• In storage
Parameter Operating Powered off Transit Storage
Temperature 5°C to 35°C 5°C to 45°C -40°C to 60°C 1°C to 60°C

range* (41°F to 95°F) (41°F to 113°F) (-40°F to 140°F) (34°F to 140°F)
Relative 20% to 80% 10% to 90% 10% to 90% 10% to 90%

humidity noncondensing noncondensing noncondensing noncondensing
Altitude -200 ft to 10,000 ft (- -200 ft to 10,000 ft (- -200 ft to 40,000 ft -200 ft to 10,000 ft (-

61 m to 3048 m) 61 m to 3048 m) (-61 m to 12,192 m) 61 m to 3048 m)
*The maximum operating temperature value is specified at sea level and is derated 2.0% per 1,000 feet of
increased altitude.
Shock and vibration

The table below shows the tested limits for shock and vibration for a fully populated S10
Node enclosure.
Parameter Level Frequency range Value
Operating vibration 0.10 G zero-to- 5 to 500 Hz 1 complete sweep

peak swept sine ½ octave/min
Operating random 0.15 Grms 5 to 500 Hz 10 minutes

vibration
Operating shock 5 G zero-to-peak N/A 3 positive shocks ,

11 ms half sine 3 negative shocks
Non-operating 0.75 G zero-to- 5 to 500 Hz 1 complete sweep

vibration peak swept sine ½ octave/min
Non-operating 0.5 Grms 5 to 500 Hz 10 minutes

random vibration
Non-operating shock 10 G zero-to-peak N/A 3 positive shocks,

11 ms half sine 3 negative shocks

Cooling and airflow

The airflow in an S10 Node enclosure goes from front to rear and is driven by four 80 mm
fans, two in each of the two power and cooling modules. Air is pulled through the front, over
the drive section, and through the midplane, where it splits into two paths. Approximately half
the air travels through the server module section, while the other half enters directly from the
front of the power and cooling modules, as shown in the figure below.
The figure below shows the airflow from the perspective of the top of the enclosure.
When all four fans are at full speed, the total airflow is approximately 200 cubic feet per
minute.
When an S10 Node is powered on, the fans run at full speed for a short time to ensure that
they are fully operational. After that, under normal conditions, the fans run at half speed. The
cooling they provide is sufficient to prevent the hard disk drives and other components from
exceeding the manufacturer’s rated specifications throughout the range of the S10 Node
operating conditions.
If a single fan fails, the S10 Node continues to operate. However, this fault condition forces
the remaining fans to run at full speed until the condition is corrected.
The normal heat dissipation rate for a fully populated S10 Node enclosure is 212 BTU/hour.
The maximum heat dissipation rate is 307 BTU/hour.

Acoustics
At normal operation tested to ISO 7779, the acoustic level of a fully populated S10 Node
enclosure does not exceed an A-weighted sound power level of 77 decibels. Normal
operation is defined as an ambient temperature of 23°C, 60 I/Os per second per hard disk
drive, and all fans operational with no fault conditions. Under fault conditions, the acoustic
sound level can increase to 84.3 decibels.
Additionally, the S10 Node enclosure has an audible alarm that sounds under some fault
conditions and beeps three times when the enclosure cover is closed. This alarm operates at
a frequency of 2300 Hz, plus or minus 300 Hz, with a sound power level of 80 decibels at 10
cm from the sound source.

Chapter 3: Preparing for HCP S10 Node
maintenance
To be prepared for any type of HCP S10 Node maintenance procedure when you arrive at a
customer site, you need certain software installed on your Windows® laptop computer:
• Virtual COM port (VCP) serial port driver — Used for communication between the
laptop computer and an S10 Node server module over a serial connection.
• VCP serial port driver uninstaller — Used to uninstall the VCP serial port driver. This
uninstaller also deletes the COM ports associated with the VCP driver.
• PuTTY — Used for access to the server modules either over a serial connection or with
SSH over an Ethernet connection.
• Rawrite32 — Used to create bootable USB flash drives or DVDs that contain the HCP
S Series operating system and software installation ISO.
• Rufus — Used to reformat bootable USB flash drives so that they can be reused for
different versions of the HCP S Series operating system and software ISO.
• HCP S Series Node post-install script — Used to verify the numbers of enclosures
and drives in the S Series Node, set the S Series Node serial number, disable data-in-
flight encryption (if applicable), and disable SSH access to the S11 or S31 Node server
modules.
HCP S Series Node tools file

The software you need on your laptop computer is in a file named HCPS_Tools_release-
number.zip (for example, HCPS_Tools_2.2.0.2.zip). This file is available from the
Hitachi Vantara Technical Information Service Center (TISC).
The HCPS_Tools_release-number.zip file contains these files:
• CDM v2.12.00 WHQL Certified.exe — Installation file for the VCP serial port driver.
• CDMuninstallerGUI.exe — VCP serial port driver uninstaller.
• hcps_post_install.bat — Script used after the installation or reinstallation of the HCP S

Series software to verify the numbers of enclosures and drives in the S Series Node, set
the S Series Node serial number, disable data-in-flight encryption (if applicable), and
disable SSH access to the S11 or S31 Node server modules .
• putty-64bit-0.73-installer.msi — Installation file for PuTTY and Pageant.
• rufus-3.5.exe — Utility used to reformat bootable USB flash drives.
• rw32-setup-1.0.6.0.exe — Installation file for Rawrite32.
Chapter 3: Preparing for HCP S10 Node maintenance

Installing and uninstalling the VCP serial port driver
• S2B_3A19-orig.bin — Image used to flash the server module BIOS in an S10 or S30
Node.
• SetupImgBurn_2.5.8.0.exe — Installation file for ImgBurn. ImgBurn is used only at

HCP S Series Node distribution centers.
• VPDTool-release-number.tgz — Zipped file containing the HCP S Series Node VPD

tool. The VPD tool is used with software upgrades and enclosure replacements.
To download the HCPS_Tools_release-number.zip file to your laptop computer and unzip
the file:
1. Log in to TISC.
2. Go to The Download Center.
3. Go to Software Downloads.
4. In the And/Or Program Product Name field, select Hitachi Content Platform S
Series Node. Then click Search.
5. Click the product code for the HCP S Series Node tools file for the release you want.
6. Click the component number for the file.
7. Click Download image file.
8. Click the link for the file.
9. Download the file to the location of your choice on your laptop computer.
10. Unzip the downloaded file to the location of your choice on your laptop computer.
Installing and uninstalling the VCP serial port driver

For communication with the S10 Node server modules over a serial connection, your laptop
computer must have the VCP serial port driver installed on it. A VCP driver causes a USB
port to appear as an additional COM port on the laptop computer. Application software, such
as PuTTY, can then access this USB port in the same way as it would access a standard
COM port.
Each time you use a serial cable to connect your laptop computer to an S10 Node server
module, Windows creates a new COM port. Windows does not reuse COM ports for these
serial connections, nor does it delete such COM ports that are no longer being used. As a
result, you can have a large number of unused COM ports on your computer.
To delete the COM ports Windows created for serial connections to S10 Node server
modules, you need to uninstall the VCP serial port driver. Uninstalling the driver
automatically deletes the applicable COM ports.
After uninstalling the VCP serial port driver, you can reinstall it so that you're ready the next
time you need to use a PuTTY serial connection to an S10 Node server module.
Installing the VCP serial port driver on your laptop computer

To install the VCP serial port driver on your laptop computer:
1. In the location in which you saved the CDM v2.10.00 WHQL Certified.exe file, right-
click the file name and select Run as administrator.

Installing and using PuTTY on your laptop computer
For instructions on obtaining this file, see "HCP S Series Node tools file" on page 31.
2. In the window that opens, click Extract.
3. If the User Account Control window appears, click Yes in the window to allow the
installation program to make changes to your computer.
4. In the Device Driver Installation Wizard window, click Next.
The installation program installs the serial port driver files.
5. Click Finish.
Uninstalling the VCP serial port driver on the laptop computer

To uninstall the VCP serial port driver on your laptop computer:
1. Run the CDMuninstallerGUI.exe file.
2. If the User Account Control window appears, click Yes in the window to allow the
installation program to make changes to your computer.
3. In the CDM Uninstaller window, click Add.
The name of the VCP serial port driver appears in the list box in the window.
4. Click Remove Devices.
5. In the Remove Successful window, click OK.
6. Close the CDM Uninstaller window.
7. If the Program Compatibility Assistant window appears, click Cancel to close the
window.

For access to the S10 Node server modules either over a serial connection or with SSH over
an Ethernet connection, your laptop computer must have PuTTY 0.73 installed on it. A serial
connection lets your laptop computer function as the system console for the server module.
SSH over an Ethernet connection gives you command-line access to the server module.
To use SSH, you first need to add the applicable SSH key (root or service) to the SSH
keychain on your computer. To do this, you use the Pageant authorization agent, which is
automatically installed with PuTTY. When adding the key, you need to know the passphrase
for it.
If you are a Hitachi Vantara employee, you download the S Series Node SSH keys from the
Hitachi Vantara SharePoint® site at:
https://sharepoint.hitachivantara.com/sites/HitachiContentArchivePlatform/SitePages/Home.a
spx
If you are providing service on behalf of an authorized S Series Node distributor, you get the
SSH keys from the HCP S Series Node Product Management team.
You can store the SSH keys in the location of your choice on your laptop computer.

SSH keys differ by the distributor from which the customer got the S10 Node. Ensure that
you have the correct key before you use PuTTY to set up an SSH connection to an S10 Node
server module.
Installing PuTTY and Pageant

To install PuTTY and Pageant, you need a Windows user account that has admin privileges.
You can either log in to your laptop computer with this account before you start the
installation or enter the credentials for the account when prompted during the installation
procedure.
To install PuTTY and Pageant on your laptop computer:
1. Optionally, log in to your laptop computer with a Windows admin user account.
2. Run the putty-64bit-0.73-installer.exe file.
For instructions on getting this file, see "HCP S Series Node tools file" on page 31.
3. In the Setup - PuTTY window, click Next.
4. On the Select Destination Location page, click Next to accept the default location.
Note: Be sure to install PuTTY in the default location. If you don't, the hcps_post_
install.bat script will fail.
5. On the Select Start Menu Folder page, optionally select a different Start menu folder in
which to place the PuTTY and Pageant shortcuts. Then click Next.
6. On the Select Additional Tasks page:
¡ Optionally, select the option to create a desktop icon for PuTTY. This option also
creates a desktop icon for Pageant.
¡ Optionally, select the option to create a Quick Launch icon for PuTTY. This option
also creates a Quick Launch icon for Pageant.
¡ Leave the option to associate .PPK files selected.
Then click Next.
7. On the Ready to Install page, click Install.
8. In the User Account Control window, take one of these actions:
¡ If you logged in to the laptop computer with an admin user account, click Yes.
¡ If you did not log in to the laptop computer with an admin user account:
1. In the applicable fields, type the username and password for an admin user
account.
2. Click Yes.
The installation program installs PuTTY and Pageant.
9. On the Completing the PuTTY Setup Wizard page, optionally deselect the View
README.txt option. Then click Finish.

Adding an S Series Node SSH key to your SSH keychain

To add an S Series Node SSH key to the SSH keychain on your laptop computer:
1. Start Pageant.
When you start Pageant, the program may be automatically minimized to your system
tray. If that happens, double-click the program icon in the system tray.
2. In the Pageant Key List window, click Add Key.
3. In the Select Private Key File window, navigate to and select the file containing the S
Series Node SSH key. Then click Open.
4. In the Pageant: Enter Passphrase window, type the passphrase for the key you're
adding. Then click OK.
5. In the Pageant Key List window, click Close.
Note: SSH keys are not retained in your keychain when you close Pageant. If you restart
Pageant after closing it, you need to add the applicable SSH key to your keychain again
before you can use SSH to access an S10 Node server module.
Using a PuTTY serial connection

For a serial connection between your laptop computer and an S10 Node server module, you
need a USB-to-mini-USB cable.
To use PuTTY to access an S10 Node server module over a serial connection:
1. On your laptop computer, open Windows Device Manager.
Tip: The easiest way to open Device Manager is to enter Device Manager in the
Windows Start menu search field and then select Device Manager from the list of
matching items.
2. In the Device Manager window, expand Ports (COM & LPT).

3. Connect the USB-to-mini-USB cable into a USB port on your laptop computer and to the
mini USB port on the server module.
If this the first time you're connecting your laptop computer to the server module, the
computer does a check for the serial port driver and reports that the driver is being
installed. The computer does this even when the driver is already installed.
When the serial connection is ready to be used, the list of ports in the Device Manager
window is automatically updated to include the VCP for the USB serial port.
4. Make a note of the COM port number in the name of the COM port displayed for the USB
serial port.
5. Start PuTTY.
6. In the PuTTY Configuration window, configure the PuTTY session:
a. In the Category list, select Connection ► Serial.

b. Set the fields for the serial connection to the values shown in the table below.
Field Value
Serial line to connect to Name of COM port assigned to the

USB serial port (for example, COM57)
Speed (baud) 115200
Data bits 8
Stop bits 1
Parity None
Flow control None
c. In the Category list, select Terminal ► Keyboard.

d. For the The Function keys and keypad option, select VT100+.
e. In the Category list, select Window.
f. In the Set the size of the window area, set Columns to 100 and Rows to 34.
g. In the Category list, select Window ► Colours.
h. For the Indicate bolded text by changing option, select Both.
i. In the Category list, select Session.
j. For the Connection type option, select Serial.
7. Optionally, save the session configuration:
a. In the Saved Sessions field, type a name for the session (for example, Server
Module 1 - Serial).
b. Click Save.
After saving a session configuration, you can start a new PuTTY session with that
configuration by double-clicking the name of the session in the list of saved sessions.
8. Click Open.
A PuTTY window opens. If the window doesn't contain any text, press Enter.
If the PuTTY window contains unexpected characters, change the flow control for the
serial connection to XON/XOFF.
Caution: Do not leave the USB-to-mini-USB cable connected to your laptop computer after
you've finished using the serial connection. Leaving the cable connected may cause the S
Series Node to behave in unexpected ways.
Using a PuTTY SSH connection

For SSH access to an S10 Node server module from your laptop computer, you need either
network access to the server module or a direct Ethernet connection between your computer

and the server module. For network access, you should use the S10 Node management
network to access the server module. However, if the management network is not
connected, you can use the S10 Node access network.
For both network access and a direct Ethernet connection, you need a CAT6 Ethernet cable:
• For network access, this cable connects the Ethernet port on the laptop computer to a
port on the customer network that has connectivity to the S10 Node access or
management network. Depending on the network configuration, either the laptop
computer is automatically assigned an IP address in the customer network, or you need
to temporarily reconfigure the laptop computer to be on the customer network.
• For a direct Ethernet connection, this cable connects the Ethernet port on the laptop
computer to the management port on the server module. In this case, you need to
temporarily reconfigure the laptop computer to be on the same subnet as the S10 Node
management network.
Reconfiguring your laptop computer for SSH access
To reconfigure your laptop computer for SSH access to an S10 Node server module:
1. Connect the CAT6 Ethernet cable to the Ethernet port on the laptop computer and to a
port on the customer network or to the management port on the server module, as
applicable.
The management port is the third Ethernet port from the left on the back of the server
module.
2. On the laptop computer, open the Windows Control Panel. Then take one of these
actions:
¡ If the Control Panel shows categories, select Network and Internet ► Network
and Sharing Center ► Change adapter settings.
¡ If the Control Panel shows large or small icons, select Network and Sharing
Center ► Change adapter settings.
3. On the Network Connections page, double-click the local area connection for the port
to which you connected the CAT6 Ethernet cable. The connection you want shows the
model of the network controller in the laptop computer (for example, Intel(R) 82579LM).
4. In the Local Area Connection Status window, click Properties.
5. On the Networking page in the Local Area Connection Properties window, select
Internet Protocol Version 4 (TCP/IPv4). Then click Properties.
6. Make a note of the settings on the General page in the Internet Protocol Version 4
(TCP/IPv4) Properties window.

7. On the General page, select Use the following IP address. Then set the fields in that
section to the values shown in the table below.
Field Value
IP address For network access, an unused IP address

provided by the customer (for management
network access, this is typically the
IP address with a fourth octet of 10 on the
management network subnet)
For a direct connection, an IP address on
the management network subnet, where
that address is not in use by either server
module (typically, this is the IP address with
a fourth octet of 10)
Subnet mask For network access, the subnet provided by

the customer
For a direct connection, the management
network subnet
Default gateway For network access, the gateway address

provided by the customer
For a direct connection, the IP address with
a fourth octet of 254 on the management
network subnet
8. Click OK to close the Internet Protocol Version 4 (TCP/IPv4) Properties window.

9. Click OK to close the Local Area Connection Properties window.
10. Click Close to close the Local Area Connection Status window.
The laptop computer may take up to a minute to establish connectivity with the server
module.
Important: When you no longer need SSH access to the server module, change the network
connection properties on your laptop computer back to their original settings, as noted in step
6.
Using PuTTY for SSH access over an Ethernet connection
To use PuTTY for SSH access to an S10 Node server module over an Ethernet connection:
1. If you have not already done so, use Pageant to add the applicable S Series Node
SSH key to the SSH keychain on your laptop computer, as described in "Adding an S
Series Node SSH key to your SSH keychain" on page 35.
2. Reconfigure your laptop computer, as described in "Reconfiguring your laptop computer
for SSH access" on the previous page.
3. Start PuTTY.
4. In the PuTTY Configuration window, configure the PuTTY session:
a. In the Category field, select Session (if it's not the current category).

Installing Rawrite32 on your laptop computer
b. For the Connection type option, select SSH.

c. In the Host Name (or IP address) field, to access the left server module, type the
management network IP address of the left server module. The default management
network IP address of the left server module is 10.2.2.1.
To access the right server module, type the management network IP address of the
right server module. The default management network IP address of the right server
module is 10.2.2.2.
d. In the Category field, select Connection ► SSH ► Auth.
e. In the Authentication parameters section, select Allow agent forwarding.
5. Optionally, save the session configuration:
a. In the Category field, select Session
b. In the Saved Sessions field, type a name for the session (for example, Server
Module 1 - SSH).
c. Click Save.
After saving a session configuration, you can start a new PuTTY session with that
configuration by double-clicking the name of the session in the list of saved sessions.
6. Click Open.
A PuTTY window opens.
Note: If a message is displayed before the PuTTY window opens, click OK or Yes to
close the message window.
7. In response to the login prompt in the PuTTY window, enter the applicable username for
the procedure you want to perform.
Tip: If you're prompted for a password at this point, your SSH keychain does not include
the necessary SSH key.
Installing Rawrite32 on your laptop computer

You use Rawrite32 to create bootable USB flash drives or DVDs from the HCP S Series
operating system and software installation ISO image or to burn the VPD tool ISO image to a
USB flash drive. To install Rawrite32 on your laptop computer, you need a Windows user
account that has admin privileges. You can either log in to your laptop computer with this
account before you start the installation or enter the credentials for the account when
prompted after you start the installation.
To install Rawrite32 on your laptop computer:
2. Run the rw32-setup-1.0.2.3.exe file.

Preparing an installation USB flash drive or DVD

account.
2. Click Yes.
4. On the Choose Install Location page of the Rawrite32 Setup window, click Install to
accept the default location and install Rawrite32.
The installation program installs Rawrite32.
5. On the Completing the Rawrite32 Setup Wizard page, click Finish.

To reinstall the HCP S Series operating system and software on an S10 Node or to recover
the software on an S10 Node, you need a bootable USB flash drive or DVD that contains the
HCP S Series operating system and software installation ISO image. You use Rawrite32 to
burn the ISO image to the drive and make the drive bootable.
Rawrite32 prepares the USB flash drive or DVD from an ISO image file named HCPS_
Install_release-number.iso (for example, HCPS_Install_2.2.0.2.iso). This file is
available from the Hitachi Vantara Technical Information Service Center (TISC).
The USB flash drive you use for the HCP S Series ISO image must have a storage capacity
of at least 4 GB and must support USB 2.0 or higher (USB 3.0 is recommended).
To burn the ISO image to a DVD, you need an external DVD drive with a USB connector.
Downloading the HCP S Series ISO image file

To download the HCP S Series ISO image file to your laptop computer:
1. Log in to TISC.
2. Go to The Download Center.
3. Go to Software Downloads.
5. Click the product code for the S Series Node software for the release you want.
6. Click the component number for the software.
8. Click the link for the .zip file containing the software.
9. Open the .zip file. Then unzip the HCPS_Install_release-number.iso file to the
location of your choice on your laptop computer.

Burning the HCP S Series installation ISO image to a USB flash drive or
DVD
You use Rawrite32 to burn the HCP S Series operating system and software installation ISO
image to a USB flash drive or DVD.
Important: Burning an ISO image to a USB flash drive or DVD overwrites any existing data
on that drive. Before burning the ISO image, ensure that the USB flash drive or DVD you're
using is the one you want to use.
To run Rawrite32, you need a Windows user account that has admin privileges. You can
either log in to your laptop computer with this account before you start Rawrite32 or enter the
credentials for the account when prompted after you start Rawrite32.
To burn the HCP S Series operating system and software installation ISO image to a USB
flash drive or DVD:
1. If you are burning the ISO image to a DVD, connect the external DVDdrive to a USB port
on your laptop computer.
3. Take one of these actions, as applicable:
¡ Insert the USB flash drive into a USB port on your laptop computer.
¡ Insert the DVD into the external DVD drive that's connected to your laptop
computer.
4. If you are prompted to format the drive, click Cancel.
5. Start Rawrite32.
account.
2. Click Yes.
7. In the NetBSD Disk Image Tool window, in the Target field, select the letter for the
drive into which you inserted the USB flash drive or DVD.
Important: Rawrite32 can overwrite any removable storage device connected to the
laptop computer. Be sure to select the correct drive.
8. In the NetBSD Disk Image Tool window, click Open.

9. In the Open a file system image window:
a. Display all file types.
b. Navigate to and select the HCP S Series operating system and software installation
ISO image file.
c. Click Open.

Reformatting bootable USB flash drives
Rawrite32 calculates hash values for the file you selected.

10. Click Write to disk.
11. In response to the confirming message, click Yes.
While Rawrite32 writes the installation files to the USB flash drive or DVD, the NetBSD
Disk Image Tool window shows the progress of the operation. When the operation is
complete, the window displays a message indicating the number of bytes that were
successfully written.
12. After the operation is complete, close the NetBSD Disk Image Tool window by clicking
the close icon ( ) in the upper right corner.
13. In the Windows system tray, right-click the Safely Remove Hardware and Eject
Media icon ( ). Then, in the popup menu, select the USB flash drive or DVD, as
applicable.
¡ If you burned the ISO image to a USB flash drive, remove the USB flash drive from
the laptop computer.
¡ If you burned the ISO image to a DVD:
1. Remove the DVD from the external DVD drive.
2. Disconnect the external DVD drive from the laptop computer.

Windows 10 cannot write to a USB flash drive that was made bootable by Rawrite32.
Therefore, to burn a new version of the HCP S Series ISO image to an installation USB flash
drive, you first need to reformat the drive so that the drive is writable again. Similarly, to burn
a new version of the HCP S Series Node Hardware Setup Tool ISO image to a USB flash
drive that has an older version of the Tool, you first need to reformat the drive.
You use the Rufus utility to reformat a bootable USB flash drive. Rufus can reformat only one
USB flash drive at a time, so you need to run the utility once for each drive you want to
reformat.
Important: Do not use Rufus to burn the installation ISO image or Hardware Setup Tool ISO
image to a USB flash drive. Rufus cannot correctly handle these image files.
To run Rufus, you need a Windows user account that has admin privileges. You can either
log in to your laptop computer with this account before you start Rufus or enter the
credentials for the account when prompted after you start Rufus.
For instructions on getting Rufus, see "HCP S Series Node tools file" on page 31.
To reformat a bootable USB flash drive:
2. Insert the USB flash drive you want to reformat into a USB port on the laptop computer.
3. Run the rufus-3.5.exe file.


account.
2. Click Yes.
5. In the Rufus window:
¡ In the Device field, select the USB flash drive you want to reformat. If only one
USB flash drive is connected to the laptop computer, that drive is selected by
default.
¡ In the Boot selection field, select Non bootable.
6. Click START.
Rufus displays a warning indicating that all data on the selected USB flash drive will be
destroyed.
7. In the warning window, click OK.
Rufus starts reformatting the USB flash drive. The status bar in the Rufus window
shows the progress of the operation. When the reformatting is complete, the status bar
displays the word READY.
8. Click CLOSE.
9. In the Windows system tray, right-click the Safely Remove Hardware and Eject
Media icon ( ). Then, in the popup menu, select the USB flash drive.
10. Remove the USB flash drive from the laptop computer.

Chapter 4: Configuring an HCP S Series Node in
DNS
For an HCP S Series Node to be accessible by domain name, the S Series Node must be
configured in DNS. This chapter:
• Describes the requirements for S Series Node zone definitions
• Contains instructions for configuring forward lookup zones for an S Series Node in both
Windows and Unix
• Explains how to verify the S Series Node DNS configuration
Zone definitions for an S Series Node

To configure an S Series Node in DNS, you can take either of these actions:
• Create a forward lookup zone for the S Series Node and add host entries to that zone. In
this case, the name of the zone looks something like s-node-1.example.com.
• Add host entries for the S Series Node to an existing forward lookup zone. In this case,
the name of the zone looks something like example.com.
In either case, the zone must be configured as a primary zone.
Host entries
Each host entry for an S Series Node associates the IP address of a server module on one of
the S Series Node networks with one of the three S Series Node interfaces or with a wildcard
(*) that represents any of the interfaces.
The hostnames that correspond to the S Series Node interfaces are:
• For the Management Console: admin
• For the management API: mapi
• For the Hitachi API for Amazon S3 (the S3 compatible API): hs3
If the zone for the S Series Node has entries for both the wildcard hostname and one or more
of the specific interface hostnames:
• The interface-specific host entries are used for access to the applicable interfaces.
• The wildcard host entry is used for access to the interfaces for which no interface-
specific entry exists.
Normally, a wildcard host is associated with the virtual IP addresses for the server modules
on the access network. If that network is using IPv6, the host can be associated with only
the primary virtual IPv6 addresses or with both the primary and secondary virtual IPv6
addresses.
Chapter 4: Configuring an HCP S Series Node in DNS

Configuring a forward lookup zone in Windows
Access network disabled

If the access network is disabled for the Management Console and you want to allow access
to the Console by domain name, the zone must have entries specifically for the admin host.
These entries must specify the IP addresses for the server modules on the management
network.
Similarly, if the access network is disabled for the management API and you want to allow
the use of this API with a domain name, the zone must have entries specifically for the mapi
host. These entries must specify the IP addresses for the server modules on the
management network.
Note: HCP and S Series Nodes always communicate over the access network. If the
access network is disabled for the management API, HCP systems cannot use the S Series
Node.
Configuring a forward lookup zone in Windows

To configure a forward lookup zone in Windows, you first create the zone. Then you add host
entries to the zone.
The instructions below explain how to create a forward lookup zone specifically for an S
Series Node. You don't need to do that if you're planning to add the host entries to an existing
zone.
You can use either the GUI or a command line to configure zones in a Windows DNS server.
The instructions below are for the Windows 2019 DNS server GUI. For a Windows 2003,
2008, 2012, or 2016 DNS server, the procedure is basically the same as the procedure here.
To create a forward lookup zone for an S Series Node:
1. In the Start menu on the Windows server that's hosting the DNS server, click Server
Manager.
2. In the Server Manager window, select Tools ► DNS.
3. In the left side of the DNS Manager window, right-click Forward Lookup Zones under
the higher-level zone within which you want to create the zone for the S Series Node.
Then select New Zone.
4. In the New Zone Wizard window, click Next.
5. On the Zone Type page:
¡ Select Primary zone.
¡ If uses Active Directory, select Store the zone in Active Directory. Otherwise,
deselect this option.
Then click Next.
6. If the Active Directory Zone Replication Scope page appears, select the applicable
option for the Active Directory configuration. Then click Next.
7. In the Zone name field on the Zone Name page, type the name of the S Series Node
domain (for example, s-node-1.example.com ). Then click Next.
8. If the Zone File page appears, click Next to accept default file name.

Configuring a forward lookup zone in Unix
9. On the Dynamic Update page, select Do not allow dynamic updates. Then click
Next.
10. On the Completing the New Zone Wizard page, click Finish.
To add host entries to a forward lookup zone:
1. In the left side of the DNS Manager window, select the applicable forward lookup zone.
Then right-click the zone and select New Host (A or AAAA).
2. In the New Host window:
¡ In the Name field, type the hostname for the entry. For example:
– If you're using a forward lookup zone created specifically for the S Series Node,
type * or admin.
– If you're using a different forward lookup zone, type *.s-node-1 or admin.s-node-
1.
¡ In the IP address field, type the IP address for the entry.
¡ If you want to add the IP address to a reverse lookup zone that already exists, select
Create associated pointer (PTR) record.
Then click Add Host.
3. In response to the confirming message, click OK.
If you selected Create associated pointer (PTR) record and the reverse lookup zone
does not exist, the host entry is added to the forward lookup zone but not to a reverse
lookup zone.
4. Take either of these actions:
¡ To add another host entry, repeat steps 2 and 3.
¡ If you're done adding host entries, click Done.

With BIND in Unix, zones are defined in the /etc/named.conf file on the DNS servers. In
this file, the statement that defines the forward lookup zone to be used for an S Series Node
must include:
• A domain name:
¡ If the zone is specifically for an S Series Node, the domain name looks something
like s-node-1.example.com.
¡ If you're using an existing domain, the domain name looks something like
example.com.
• The zone type (master).
• The name of the file containing the A records for the zone. The A records specify the
host entries for the zone.
Each A record for an S Series Node associates an S Series Node interface or the
wildcard (*) with the IP address of one of the S Series Node server modules on one of the
S Series Node networks.

Each fully qualified domain name that can be used for access to an S Series Node is the
concatenation of the hostname in an A record with the specified domain name. For
example:
¡ If the domain name is s-node-1.example.com, the hostname for the Management
Console is admin by itself.
¡ If the domain name is example.com, the hostname for the Management Console is
admin.s-node-1.
• A specification not to allow dynamic updates of the A records.

Here's a sample zone statement that defines a forward lookup zone specifically for the S
Series Node with domain name s-node-1.example.com:
zone "s-node-1.example.com" {
type master;
file "/var/named/data/s-node-1.example.com";
allow-update {none;};
};
Here are sample contents for the file named in the zone statement above:
$TTL 900
@ IN SOA dnsserver.example.com. dns-admin.example.com. (
1412260762 ; serial
10800 ; refresh (3 hours)
15 ; retry (15 seconds)
304800 ; expire (1 week)
10800 ; minttl (3 hours)
)
; Name Servers
@ IN NS dnsserver.example.com.
;Zone Data
admin IN A 10.0.0.3
admin IN A 10.0.0.4
mapi IN A 10.0.0.3
mapi IN A 10.0.0.4
hs3 IN A 10.0.0.3
hs3 IN A 10.0.0.4
In the sample file above, the admin, mapi, and hs3 hosts are all associated with the virtual
IP addresses of the server modules on the access network.
If the forward lookup zone is not specifically for the S Series Node, the A records in the file
look something like this:
admin.s-node-1 IN A 10.0.0.3
admin.s-node-1 IN A 10.0.0.4
mapi.s-node-1 IN A 10.0.0.3
mapi.s-node-1 IN A 10.0.0.4
hs3.s-node-1 IN A 10.0.0.3
hs3.s-node-1 IN A 10.0.0.4

Verifying the DNS configuration
Verifying the DNS configuration

You can verify that an S Series Node primary zone is working properly from either a Windows
command-prompt window or a Unix shell. In both cases, you can use either the dig or
nslookup command, depending on which is available.
The syntax for verifying the primary zone configuration is:
(dig|nslookup) (admin|mapi|hs3|*).node-domain-name
The response to this command should be a list of the server module IP addresses specified
for the requested interface in the S Series Node forward lookup zone.
Here's an example of the command and response in Windows:
C:\>nslookup admin.s-node-1.example.com
Server: dnsserver.example.com
Address: 10.0.201.55
Name: admin.s-node-1.example.com
Addresses: 10.0.0.3
10.0.0.4
If you don't see the expected IP addresses, the zone is not defined correctly.

Chapter 5: Monitoring an HCP S10 Node
An HCP S10 Node provides information about its status through a variety of mechanisms:
• The HCP S Series Management Console displays:

¡ Information about storage usage on the Dashboard page
¡ Information about bucket usage on the System ► Buckets page
¡ Detailed information about the status of the HCP S10 Node hardware components
¡ Messages about events that occurred on the HCP S10 Node
¡ Alerts that notify you about conditions that the HCP S10 Node is currently
experiencing
Status information that's available in the Management Console is also available through
the HCP S Series management API.
• You can configure the S Series Node to send event log messages, log messages for
data access requests, and log messages for management API requests to one or more
syslog servers.
• Through the management API, you can get information about the current load on S
Series Node resources.
• Many hardware components have LEDs that light up to indicate certain conditions.
• Some LEDs serve as beacons. Beacons enable you to easily identify components in
your data center.
You can use the HCP S Series Management Console or management API to turn
beaconing on or off for individual components.
• The S Series Node internal logs contain detailed records of the status and activity of
various components of the software running on the HCP S10 Node.
You can use the HCP S Series Management Console or management API to insert
comments into or download the internal logs.
• If in use by an HCP system, the HCP S10 Node notifies that system about certain
abnormal conditions as they occur.
• If the Hitachi Remote Ops monitor agent is configured to monitor the HCP S10 Node,
the HCP S10 Node sends status information to the monitor agent in response to periodic
requests from the agent.

Management Console hardware information
Management Console hardware information

The Hardware ► Overview page in the HCP S Series Management Console displays high-
level information about the status of the S10 Node enclosure and server modules. From this
page, you can display more detailed information about the S10 Node hardware components:
• To see detailed information about the enclosure and its components, click the gear icon (
) for the enclosure on the Hardware ► Overview page. Then, in the Detailed
Enclosure Information list, click the type of component you want more information
about.
• To see detailed information about the data or database drive in a slot or about an empty
drive slot, click the slot in the top view in the enclosure diagram on the enclosure details
page.
• To see detailed information about a server module and its components, click the gear
icon ( ) for the server module on the Hardware ► Overview page. Then, in the
Detailed Server Module Information list, click the type of component you want more
information about.
Physical component status indicators

The LEDs on S10 Node enclosures, power and cooling modules, and server modules provide
information about the status of the applicable component. Some of these LEDs can also be
used for beaconing.
Additionally, enclosures have an alarm that sounds under certain conditions.
Enclosure LEDs
The front of an enclosure has eight color-coded LEDs that indicate the status of the S10
Node. The LEDs are arranged in two angled columns of four LEDs each, as shown in the
figure below.
The table below describes these LEDs.
LED Color State Description
Enclosure Green Solid The enclosure is powered on.

power
Blinking N/A
Off The enclosure is powered off.

(Continued)
Enclosure fault Amber Solid The enclosure itself or one or more components in the
enclosure are not functioning properly.
Blinking N/A
Off All components in the enclosure are functioning properly.
Enclosure Blue Solid N/A

identity
Blinking Beaconing is on for the enclosure.
Off Beaconing is off for the enclosure.
Drive fault Amber Solid One or more data or database drives in the enclosure are
not functioning properly.
Blinking The S10 Node is synchronizing the database drives.
Off All data and database drives in the enclosure are

functioning properly.
Cover open Amber Solid The enclosure cover is open.
Blinking N/A
Off The enclosure cover is closed.
Software OK Green Solid The HCP S Series software is running on the S10 Node.
Blinking The S10 Node is synchronizing the OS or database drives.
Off The HCP S Series software is not running on the S10

Node.
Software fault Amber Solid One or more components of the S10 Node are not
functioning properly.
Blinking A server module has an error condition.
Off The software is correctly installed, or the software has not

yet been installed.
Software install Blue Solid Software installation prechecks are in progress.
Blinking The software is being installed, updated, or recovered.
Off N/A

Power and cooling module LEDs

Each power and cooling module has four color-coded LEDs that indicate its status, as shown
in the figure below.
PCM fault Amber Solid The power and cooling module is not operating normally.
Blinking N/A
Off The power and cooling module is operating normally.
PCM identity Blue Solid N/A
Blinking Beaconing is on for the power and cooling module.
Off Beaconing is off for the power and cooling module.
DC OK Green Solid The power supply DC output voltages are within the normal
operating range.
Blinking N/A
Off The power supply DC output voltages are not within the
normal operating range.
AC OK Green Solid The power and cooling module is powered on, and the
AC input power is within normal operating range.
Blinking N/A
Off The power and cooling module is powered off, or the AC

input power is not within normal operating range.
Server module LEDs

Each server module has five color-coded LEDs that indicate its status, as shown in the figure
below.

Beaconing
SM reset Amber Solid N/A
Blinking The server module is in the process of restarting.
Off The server module is operating normally.
SM fault Amber Solid The server module has a fault condition.
Off The server module is operating normally.
SM identity Blue Solid N/A
Blinking The server module is in the process of restarting, or

beaconing is on for the server module.
Off Beaconing is off for the server module.
POST code Yellow Solid N/A
Off POST tests have passed, and the server module is

operating normally.
SM power Green Solid The server module is powered on.
Blinking The server module is in the process of powering on or

restarting.
Off The server module is powered off.
Enclosure audible alarm

The HCP S10 Node enclosure has an alarm that beeps three times when the enclosure cover
is closed and sounds under these conditions:
• While the enclosure cover is open.
• While a power and cooling module has a problem (such as a failed power supply or fan).
• While the enclosure contains only one power and cooling module. In this case, the alarm
is intermittent for the first five minutes and then becomes continuous.
Beaconing
The enclosure, power and cooling modules, and server modules have LEDs that can serve
as beacons. When blinking, a beaconing LED lets you easily identify the applicable
component in the customer data center. For information about the LEDs used for beaconing,
see "Physical component status indicators" on page 50.

Beaconing
If you have the administrator or service role, you can use the HCP S Series Management
Console or management API to turn beaconing on or off for a component.
In the Management Console, you manage beaconing from the enclosure diagram. This
diagram provides top, front, and back views of the enclosure.
To see:
• All three views of the enclosure diagram, on the Hardware ► Overview page, click the
gear icon ( ) for the enclosure.
• Only the back view of the enclosure diagram, on the Hardware ► Overview page, click
the gear icon ( ) for either one of the server modules.
To turn beaconing on or off for the enclosure:

1. Log in to the HCP S Series Management Console using a user account with the
administrator or service role.
2. Go to Hardware ► Overview.
3. Click the gear icon ( ) for the enclosure.
4. Click the front view of the enclosure diagram.

5. In the Enclosure window that opens, set the Beacon slider to On to turn beaconing on
or to Off to turn beaconing off.
The blue identity LED on the enclosure immediately starts to blink or stops blinking, as
applicable. The identity LED is the third LED down from the top in the left column of
LEDs on the front of the enclosure.
6. Click Close.
To turn beaconing on or off for a power and cooling module or server module:
2. Go to Hardware ► Overview.
3. Click the gear icon ( ) for either one of the server modules.
4. In the back view of the enclosure diagram, click the module for which you want to turn
beaconing on or off.
5. In the Power & Cooling Module or Server Module window that opens, set the
Beacon slider to On to turn beaconing on or to Off to turn beaconing off.
The blue identity LED on the applicable module immediately starts to blink or stops
blinking, as applicable. The identity LED on a power and cooling module is the second
LED from the left on the front of the module. The identity LED on an server module is the
middle LED on the front of the module.
6. Click Close.

Internal logs
Internal logs
HCP S Series Nodes maintain internal logs that record the status and activity of various
components of the HCP S Series software. If a problem occurs with the S Series Node, the
internal logs can assist support personnel in diagnosing and resolving the problem.
If you have the administrator, monitor, security, or service role, you can use the HCP S
Series Management Console or management API to insert comments into the S Series Node
internal logs. You can use this capability, for example, to note unusual events that occur on
the S Series Node. Comments can later assist support personnel in understanding the
symptoms that indicate a possible problem. Comments can also assist support personnel in
determining when a problem started.
To help with troubleshooting, if you have the administrator or service role, you can download
the internal logs and send them to your HCP support center. You can use the HCP S Series
Management Console or management API to download the logs. For ease of handling, the S
Series Node downloads the logs into a single packed file. Neither this file nor the logs
themselves are encrypted.
An S Series Node generally keeps internal logs for at least 120 days. However, it keeps them
for a shorter time period if not enough space is available for them. You can download the logs
for any length of time within the period for which logs exist. When downloading the logs, be
sure to include all the days on which you observed problems with the S Series Node.
Inserting comments into the internal logs

To use the HCP S Series Management Console to insert a comment into theS Series Node
internal logs:
1. Log into the Management Console using a user account with the administrator, monitor,
or service role.
2. Go to the Monitor►Internal Logs page.
3. In the field in the Mark Internal Logs section, type the comment text. This text can be
up to 1,024 characters long and can contain any valid UTF-8 characters, including white
space.
4. Click Mark.
Downloading the internal logs

Downloading the S Series Node internal logs is a two-part procedure. In the first part, the S
Series Node prepares the logs for download. In the second part, the S Series Node packs the
prepared logs into a .zip file and performs the actual download. The amount of time the S
Series Node takes to prepare the logs depends both on the length of time for which you
request the logs and on the size of the log files.
Note: Downloading the internal logs puts a heavy load on the S Series Node. Do not take
this action unless explicitly told to do so by support personnel.

Internal logs
To use the HCP S Series Management Console to download the internal logs:
Tip: To ensure that you consistently see correct status information during a log
download operation, use a physical IP address to access the Management Console.
2. Go to the Monitor ► Internal Logs page.

3. In the Download Internal Logs section:
¡ Click in the Start Date field. Then, in the calendar that opens, select the date of the
earliest logs you want to include in the download. You cannot select a start date
that's more than 120 days ago.
Logs are included starting from 12:00 a.m. on the selected date.
¡ Click in the End Date field. Then, in the calendar that opens, select the date of the
latest logs you want to include in the download.
Logs are included up to 1:00 a.m., inclusive, on the day following the selected date.
The end date must be later than the start date.
4. Click Prepare.
The S Series Node starts preparing the logs for download. While the logs are being
prepared, the Internal Logs page includes a Prepare Status section that reports the
progress of the log preparation on each of the S Series Node server modules. This
section is automatically updated every ten seconds.
You do not need to stay on the Internal Logs page while the S Series Node is preparing
the logs.
Note: While the logs are being prepared for download, do not restart a server module.
Doing so causes the logs to remain in the prepare state indefinitely. If this happens,
contact your HCP support center for help.
5. When the status of both server modules is "Ready for log download," click Download.
6. When prompted, save the .zip file containing the downloaded logs in the location of your
choice.
By default, the name of the .zip file is HCPSLogs-YYYYMMDD-hhmm.zip.
You do not need to stay on the Internal Logs page while the S Series Node is packing
and downloading the logs.
7. When the status of both server modules is "Download complete," click Reset.

Configuring HCP S Series Node monitoring with the Hitachi Remote Ops monitor agent
Configuring HCP S Series Node monitoring with the Hitachi

Remote Ops monitor agent
The Hitachi Remote Ops monitor agent (formerly called Hi-Track Monitor) is a
Hitachi Vantara product that enables remote monitoring of HCP S Series Nodes. With the
Remote Ops monitor agent, you can view detailed S Series Node status information in a web
browser. You can also configure the monitor agent to notify you by email of error conditions
as they occur. Additionally, you can configure the monitor agent to report error conditions to
Hitachi Vantara support personnel.
The Remote Ops monitor agent is for monitoring and error notification purposes only. The
monitor agent does not allow any changes to be made to the S Series Node being monitored.
The Remote Ops monitor agent is installed on and runs on a server that is separate from any
S Series Node server modules. You use the monitor agent to configure S Series Node
monitoring.
The monitor agent uses the HCP S Series management API over the access or management
network to periodically request status information from the S Series Node being monitored.
The monitor agent uses HTTPS for these requests.

Configuring HCP S Series Node monitoring with the Hitachi Remote Ops monitor agent
To configure the Remote Ops monitor agent to monitor an S Series Node, you specify this
information in the monitor agent:
• The username and password for an S Series Node user account that has the monitor
role.
Tips:
• Create an S Series Node user account specifically for use by the monitor agent.
When you create the account, deselect the option to force a password change on
the next login. Also deselect the option to have the password expire automatically.
• If you change the password for the S Series Node user account used by the monitor
agent, be sure to change the user account password in the monitor agent at the
same time.
• The IP addresses of both S Series Node server modules on the access or management
network. If you use the access network, you can specify either the physical IP
addresses or the virtual IP addresses.
Note: S Series Nodes support both IPv4 and IPv6 network connections to the monitor
agent. However, monitor-agent support for IPv6 connections varies based on the
operating system on the server where the monitor agent is running. For information about
requirements for monitor-agent servers that support IPv6 networks, see the applicable
Hitachi Remote Ops monitor agent documentation.
• One or more email addresses to which the monitor agent should send notifications of
error conditions.
• Optionally, configuration information for one or more monitor-agent transport agents. A

transport agent transfers notifications of error conditions to a target location where HCP
support personnel can access them.
For instructions on configuring S Series Node monitoring in the monitor agent, see the
applicable Hitachi Remote Ops monitor agent documentation.

Chapter 6: Maintaining the HCP S Series
operating system and software
Maintaining the HCP S Series operating system (OS) and software can entail:
• Upgrading the HCP S Series OS and software when a new HCP S Series Node release
becomes available and the customer is ready for the upgrade. Upgrades can also include
updates to S Series Node component firmware.
• Applying a hotfix when necessary to address an issue with an S Series Node at a

customer site. A hotfix is an update to the software or firmware that resolves a particular
problem.
• Reinstalling the HCP S Series OS and software, typically to convert a proof-of-concept

S Series Node to a production S Series Node.
• Recovering the HCP S Series OS and software on a single server module after replacing
both OS SSDs in the module.
• Recovering the HCP S Series OS and software on both server modules in the rare case
that an S Series Node becomes inoperable. To perform this procedure, you need to
contact your HCP support center for instructions.
Updating the HCP S Series OS and software

When a new release of the HCP S Series software becomes available, you can upgrade the
currently installed version of the HCP S Series software to that release. Software upgrades,
which can also include an upgrade of the HCP S Series OS and updates to component
firmware, are performed while the S Series Node is running.
Normally, the S Series Node remains fully functional during an upgrade. However, upgrades
to release 2.2.0 or later from a release earlier than 2.2.0 include approximately 30 minutes of
downtime while the internal database is upgraded. During this time, which occurs at the end
of the upgrade process, the S Series Node is unavailable for both management and data
access purposes.
At times, you may need to apply a hotfix to an S Series Node to resolve a particular problem.
Typically, hotfixes are applied only to S Series Nodes that are experiencing that problem. If
possible, hotfixes are applied while the S Series Node is running, with no loss of functionality
during the process.
You use the same procedure for upgrading the software and applying a hotfix. First you
upload an update file. Then you apply the uploaded update. You can perform this procedure
either in the HCP S Series Management Console or by using the HCP S Series management
API.
If you're upgrading the HCP S Series software from release 2.1.6, you need to ensure that
the vital product data (VPD) in the enclosure is correct before you perform the upgrade.
Chapter 6: Maintaining the HCP S Series operating system and software

In response to a request to apply an update, the update program automatically performs a

series of prechecks to ensure that the S Series Node is ready to be updated. If the S Series
Node passes all the prechecks, the update program automatically applies the update.
You can run the update prechecks yourself any time after you upload the update file. If the S
Series Node passes all the prechecks, you can then work with the customer to schedule a
time for performing the update itself. Regardless of whether you run the prechecks yourself,
the update program always runs them before applying an update.
If you're upgrading the HCP S Series software from release 2.1.6, be sure to verify the
enclosure VPDs before running the update prechecks.
HCP S Series Node update files

You make updates to the HCP S Series software by uploading and applying the contents of a
single update file. This can be a software upgrade file or a hotfix file.
A software upgrade file contains the files necessary for upgrading the HCP S Series
software and, if applicable, the HCP S Series OS and S Series Node component firmware.
Software upgrade files are named HCPS_Upgrade_release-number.bin (for example,
HCPS_Upgrade_2.2.0.2.bin). They are available from TISC.
A hotfix file contains the files necessary for applying a hotfix. A hotfix can update the HCP
S Series software, OS, or component firmware.
Hotfix files are named HCPS_Hotfix_release-number_HFhotfix-number.bin (for
example, HCPS_Hotfix_2.2.0.2_HF0001.bin). They are available from TISC.
Downloading an upgrade or hotfix file from TISC

To download an HCP S Series upgrade or hotfix file from TISC:
1. Log into TISC.
2. Go to The Download Center (TDC).
3. If the Internal Export Control Statement and Download Acknowledgment page
appears, select I have read and accept the above terms. Then click Continue.
4. Open Software Downloads.
6. Click the product code for the S Series Node upgrade or hotfix you want.
7. Click the component number for the upgrade or hotfix.
9. Click the link for the .zip file containing the upgrade or hotfix.
10. Optionally, save the .zip file to the location of your choice on your laptop computer.
11. Open the .zip file. Then unzip the contents of the file to the location of your choice on
your laptop computer.

Considerations for software updates

These considerations apply to updating the HCP S Series software:
• Before you start the procedure to upgrade the HCP S Series software or apply a hotfix,
both S Series Node server modules must be running and healthy.
• When you upload an update file, the file overwrites any previously uploaded update file.
• After uploading an update file, you cannot apply the update while the internal logs are
being downloaded or while a maintenance procedure is in progress.
• While the software is being updated, you can make changes to the S Series Node
configuration. However, most configuration changes don't take effect until the software
update is complete.
• Software updates occur on one server module at a time. While the software is being
updated on one server module, all S Series Node processing occurs on the other server
module.
• When a software update finishes on the first server module, that server module
automatically reboots. When the reboot is complete, the update automatically starts on
the second server module, and processing fails over from the second server module to
the first server module. While this failover is in progress, the HCP S Series Management
Console may be briefly unavailable.
When the software update is complete on the second server module, that server module
automatically reboots. When the reboot is complete, processing is again distributed
across both server modules.
• While the software on a server module is being updated, you cannot use the physical IP
address of that module to access the HCP S Series Management Console, make
management API requests, or perform data access operations.
• If you accessed the HCP S Series Management Console by using the physical
IP address of the second server module while the software on the first server module
was being updated, when failover occurs, you lose your connection to the Management
Console. At that point, you need to log in again, this time using the S Series Node
domain name, a virtual IP address, or the physical IP address of the first server module
to access the Management Console.
• At certain points during a software update that includes a firmware update, the HCP S
Series Management Console displays an alert indicating that a firmware version
mismatch exists. Depending on which server module issued the alert, the alert may
show up as informational or as indicating an error condition. In either case, no action is
required.
• If an error occurs during the apply step of an update, you can try restarting the update. If
an error occurs again, do not try to restart the update a second time. Instead, contact
your HCP support center for help.
Step 1 (conditional): Verify the enclosure VPDs

If you are upgrading the HCP S Series software from release 2.1.6, you need to use the
VPD tool to verify the VPDs in the enclosure before you run prechecks or perform the
upgrade. This tool checks the VPDs and tries to fix any errors it finds. If the tool finds but
cannot fix one or more errors, you need to contact your HCP support center for help.

To run the VPD tool:

1. If you have not already done so, add the S Series Node root SSH key to your
SSH keychain, as described in "Adding an S Series Node SSH key to your SSH
keychain" on page 35.
2. Using a file transfer tool such as WinSCP, copy the VPDTool-release-number.tgz
file from your laptop computer to the /tmp directory on server module 1.
3. From the HCP S Series Management Console, shut down server module 2:
a. On the Hardware ► Overview or Hardware ► Maintenance page, click Power
Options.
b. In the Server Module field, select Server Module 2.
c. In the Reason field, type the reason why you're shutting down the server module.
This text can be up to 1,024 characters long and can contain any valid UTF-8
characters, including white space.
d. Click Shut Down.
4. Use PuTTY to establish an SSH connection to server module 1, as described in "Using a
PuTTY SSH connection" on page 36.
5. At the login prompt, enter root .
6. Change to the /tmp directory.
7. Enter this command to unpack the VPDTool-release-number.tgz file, replacing
release-number with the applicable release number:
tar xvzf VPDTool-release-number.tgz
8. Change to the /tmp/VPDTool directory.

9. Enter this command to run the VPD tool:
./FixVPD -a
The VPD tool reports its progress as it checks and, if necessary, tries to fix the VPDs.
The tool then reports the outcome of its processing. Three outcomes are possible:
¡ The tool does not find any errors. The report looks like this:
To continue:
1. Enter exit to close the PuTTY window.
2. From the HCP S Series Management Console, restart server module 2:
a. On the Hardware ► Overview or Hardware ► Maintenance page, click
Power Options.
c. In the Reason field, type the reason why you're restarting the server
module.
d. Click Power On.

3. Wait for server module 2 to become available.

4. Proceed with the software upgrade.
¡ The tool found one or more errors and fixed them all. The report looks something like
this:
To continue, , follow the procedure above for when the VPD tool doesn't find any
errors.
¡ The tool found one or more errors it could not fix. The report looks something like
this:
To continue:
1. Using a file transfer tool such as WinSCP, copy the .log file and all the .txt files
from the /tmp/VPDTool directory to the location of your choice on your laptop
computer. HCP support personnel will need these files to resolve the VPD
errors.
Power Options.
module.
d. Click Restart.
3. Either try running the VPD tool again, or contact your HCP support center for
help. Do not try to run the tool again more than twice.
Important: Do not perform the software upgrade after the VPD tool discovers errors
that the tool cannot fix.

Step 2: Upload the update file

To use the HCP S Series Management Console to upload an update file:
1. Log in to the HCP S Series Management Console using a user account with the service
role.
2. Go to System ► Update.
3. Click Select File.
4. In the File Upload window, navigate to and select the update file (that is, the applicable
.bin file). Then click Open.
5. Click Upload.
The S Series Node uploads the update file and then verifies that the file is a valid update
file. The Console displays a progress bar for each of these processes.
When the upload is complete, the Apply Update section displays information about the
update, including what impact the update process will have on the S Series Node.
If you navigate away from the Update page while an upload is in progress, the upload
fails. In this case, you need to start the upload procedure again.
Tip: If you accidentally upload the wrong file, click Cancel to reactivate the Select and
Upload section on the Update page.
Step 3 (conditional): Run the update prechecks

To use the HCP S Series Management Console to run update prechecks, on the System ►
Update page, click Run Prechecks.
The S Series Node starts running the update prechecks. Prechecks are run sequentially. If a
precheck fails, the S Series Node reports the error and does not run any more prechecks.
If all the prechecks succeed, the S Series Node returns this message:
Update prechecks successful. The HCP S Series Node is ready to be updated.
The prechecks for an update are mostly the same as the prechecks for a software
reinstallation. For a list of prechecks, see "Software reinstallation prechecks" on page 91.
Step 4: Apply the update

To use the HCP S Series Management Console to apply an update, on the System ►
Update page, click Apply Update.
The update prechecks run. Then the update starts.
The Console displays a progress bar for each server module to show the progress of the
update on that module. If the update is to the HCP S Series software, the server module
automatically reboots after the update is 100% complete on that module.
When the update is complete on both server modules and both server modules have
rebooted, the Console refreshes the Update page.

Reinstalling the HCP S Series OS and software
If an update fails, the Restart Update button on the Update page becomes active. You can
try applying the update again by clicking Restart Update.
If an update fails more than once, contact your HCP support center for help.

On occasion, you may need to reinstall the HCP S Series OS and software on an S Series
Node at a customer site. The most common reason for doing this is to convert an S Series
Node that's being used for proof of concept to an S Series Node that can be used for
production purposes.
The reinstallation procedure you use on site is the same as the reinstallation procedure used
at the Hitachi Vantara distribution center when an initial installation fails. The same
installation files are used for both the initial installation and the reinstallation of the HCP S
Series OS and software.
Before you can perform the OS and software reinstallation, you need to connect cables to the
server modules. After the software reinstallation is complete, you need to verify its success.
If you are reinstalling the OS and software on an S Series Node that's currently at release
2.1.6, you need to run the VPD tool before you perform the reinstallation. This tool checks the
VPDs in the enclosure and tries to fix any errors it finds. If the tool finds but cannot fix one or
more errors, you need to contact your HCP support center for help.
After you reinstall the OS and software on an S Series Node, you run the HCP S Series Node
post-install script to set the S Series Node serial number and, if applicable, disable data-in-
flight encryption. You need to run this script even if the serial number and data-in-flight
encryption option were already set as part of the last OS and software installation on the S
Series Node.
After running post-install script, you use the first-time setup wizard to configure the S Series
Node for the customer environment. You need to do this configuration even if the S Series
Node was configured for the customer environment before the OS and software
reinstallation.
Tip: Before starting the reinstallation, use the HCP S Series Node Configuration Information
form on page 215 to record the customer-specific configuration settings for the S10 Node on
which you're reinstalling the OS and software. Then keep the form with you when you
perform the reinstallation so you have easy access to the information you need.
Caution: Reinstalling the OS and software on an S Series Node destroys all data stored on
the S Series Node. Reinstallation is not the way to recover the OS and software on an S
Series Node that is experiencing problems.
What you need for reinstalling the HCP S Series OS and software
For an HCP S Series software reinstallation, you need:
• If the access ports on the server modules are not connected to switches in the customer
network, two 10Gb Twinax cables.
• If the management ports on the server modules are not connected to switches in the
customer network, one CAT6 Ethernet cable.

• One bootable USB flash drive or DVD that contains the HCP S Series OS and software
installation files. For information about preparing this drive, see "Preparing an installation
USB flash drive or DVD" on page 40.
• If the HCP S Series OS and software installation files are on a DVD, an external DVD
drive with a USB connector.
• A laptop computer with:

¡ The HCP S Series Node post-install script (that is, the hcps_post_install.bat
file) installed on it. For instructions on obtaining this script, see "HCP S Series Node
tools file" on page 31.
¡ The HCP S Series Node root SSH key in the SSH keychain on the computer. For
instructions on adding this key to the keychain on your laptop computer, see "Adding
an S Series Node SSH key to your SSH keychain" on page 35.
• A USB-to-mini-USB cable.
• The HCP S10 Node BIOS password.

If you are a Hitachi Vantara employee, you download the BIOS password from the
Hitachi Vantara SharePoint site at:
https://sharepoint.hitachivantara.com/sites/HitachiContentArchivePlatform/SitePages/Ho
me.aspx
If you are providing service on behalf of an authorized S Series Node distributor, you get
the BIOS password from the HCP S Series Node Product Management team.
Step 1: Prepare for the software reinstallation

For the reinstallation of the HCP S Series OS and software, you need cables connected to
the Ethernet ports on both server modules. The server interconnect ports on the two server
modules should already be connected with the purple server interconnect cable.
The access and the management ports may already be connected to switches in the
customer network. If the applicable ports are not connected to switches, you need to cross-
connect those ports between the two server modules.
The figure below shows the locations of the Ethernet ports on the server modules.
To prepare for the HCP S Series software reinstallation:

1. Ensure that the two power and cooling modules are firmly seated in the enclosure. If
either module is not firmly seated, using the #1 Phillips screwdriver, gently tighten the
large black screw in the top center of the module. Do not overtighten the screw.

2. Ensure that the two server modules are firmly seated in the enclosure. If either module is
not firmly seated, using the #1 Phillips screwdriver, gently tighten the large black screw
in the top center of the module. Do not overtighten the screw.
3. If the access ports are not connected to the customer network and have SFP+ modules
installed in them, remove the modules from those ports.
4. Connect cables to the Ethernet ports:
¡ If the access ports on the server modules are not connected to switches in the
customer network:
– Use one Twinax cable to connect access port 1 on the left server module to
access port 1 on the right server module.
When connecting the cable to access port 1 on a server module, ensure that the
card in the connector at the end of the cable is facing access port 2 on that
server module.
– Use the other Twinax cable to connect access port 2 on the left server module
to access port 2 on the right server module.
When connecting the cable to access port 2 on a server module, ensure that the
card in the connector at the end of the cable is facing access port 1 on that
server module.
¡ If the management ports on the server modules are not connected to switches in the
customer network, using one CAT6 Ethernet cable, connect the management port
on the left server module to the management port on the right server module.
When inserting the cable into each port, push the cable in until the end clicks into
place.
Step 2 (conditional): Verify the enclosure VPDs

If the S Series Node on which you're reinstalling the HCP S Series OS and software is at
release 2.1.6, you need to run the VPD tool before you perform the reinstallation.
2. Using a file transfer tool such as WinSCP, copy the VPDTool-release-number.tgz
file from your laptop computer to the /tmp directory on server module 1.
Options.
d. Click Shut Down.


6. Change to the /tmp directory.
7. Enter this command to unpack the VPDTool-release-number.tgz file, replacing
release-number with the applicable release number:
tar xvzf VPDTool-release-number.tgz
8. Change to the /tmp/VPDTool directory.

./FixVPD -a
The tool then reports the outcome of its processing. Three outcomes are possible:
To continue:
Power Options.
module.
d. Click Power On.
4. Proceed with the software reinstallation.
this:
To continue, , follow the procedure above for when the VPD tool doesn't find any
errors.

this:
To continue:
from the /tmp/VPDTool directory to the location of your choice on your laptop
computer. HCP support personnel will need these files to resolve the VPD
errors.
Power Options.
module.
d. Click Restart.
Important: Do not perform the software reinstallation after the VPD tool discovers
errors that the tool cannot fix.
Perform the OS and software reinstallation

To reinstall the OS and software on an S Series Node, you can perform either a default
reinstallation or a custom reinstallation:
• A default reinstallation reinstalls the OS and software with all default initial S Series
Node configuration settings, including the default distributor key (Atlantic) and server
module IP addresses. With this type of installation, you don't provide any configuration
information.
• A custom reinstallation lets you specify the initial configuration settings for the S
Series Node, including the distributor key and server module IP addresses. If your
distributor key is other than Atlantic, a custom reinstallation is required.
Tip: Before starting a custom reinstallation, use the "Appendix: HCP S Series Node
Configuration Information form" on page 214 to record the customer-specific
configuration settings for the S Series Node. Then keep the form with you when you
perform the reinstallation so you have easy access to the information you need.

Performing a default software reinstallation
For a default software reinstallation, you first reconfigure the left server module and reinstall
the OS on that module. Then you reconfigure the right server module and reinstall the OS on
that module. After the OS is reinstalled on both server modules, the software reinstallation
starts automatically.
Prepare for the server module reconfiguration

To prepare for the server module reconfiguration:
1. Ensure that Ethernet cables are connected to all four ports on each S10 Node server
module, as described in Step 1: "Prepare for the software reinstallation" on page 66.
2. Use the rocker switches on the power and cooling modules to power both modules on.
Reconfigure the left server module
To reconfigure the left server module:
1. Use PuTTY to establish a serial connection to the left server module (when viewed from
the rear of the rack), as described in "Using a PuTTY serial connection" on page 35.
¡ If the HCP S Series OS and software installation files are on a USB flash drive,
insert that drive into a USB port on the left server module.
¡ If the HCP S Series OS and software installation files are on a DVD:
1. Connect the external DVD drive to a USB port on the left server module.
2. Insert the DVD into the external DVD drive.
3. Reboot the left server module in either of these ways:
¡ In the PuTTY window:
1. Right-click in the window title bar. Then select Special Command4Break.
2. Enter b.
¡ Insert the end of a paper clip into the hole for the recessed power button in the
bottom right corner of the module and then gently press the paper clip against the
power button for five seconds.

4. When you see this prompt, press Delete:
You have approximately ten seconds to do this. If you wait too long, the server module
boots using the installed OS. In this case, you need to reboot the server module again.
5. When prompted for a password, enter the BIOS password for S10 Nodes.
The Aptio Setup Utility Main page appears.
6. Arrow right to Advanced.

7. On the Advanced menu page, arrow down to USB Configuration. Then press Enter.
8. On the USB Configuration page, arrow down to USB Mass Storage Driver Support.
Then press Enter.

9. In the USB Mass Storage Driver Support popup, arrow down to Enabled. Then press
Enter.
10. Press Escape to return to the Advanced menu page.

11. Arrow right to Save & Exit.
12. On the Save & Exit page, arrow down to Save Changes and Reset. Then press Enter.

13. In response to the confirming prompt, press Enter.
The server module reboots.

14. When you see this prompt, press F7:

16. In the Please select boot device menu, arrow down to the entry for the installation
USB flash drive or DVD. Then press Enter. (The name of the drive may differ from the
name shown in the figure below.)
Reinstall the OS on the left server module

To reinstall the OS on the left server module:
1. When the HCPSOS Operating System installation window appears in the PuTTY
window, arrow up to HCPSOS Operating System under SERIAL. Then press Enter.
2. In response to the prompt for the OS installation mode, enter i.
Caution: Option I destroys all data stored on the S Series Node. If you do not want to
destroy the data, enter e to exit the reinstallation.
The OS reinstallation starts on the left server module. When the reinstallation finishes,
the server module automatically reboots. The left server module then waits for the OS
reinstallation to finish on the right server module.

3. After the left server module starts to reboot, take one of these actions, as applicable:
remove that drive from the USB port on the left server module.
¡ If the HCP S Series OS and software installation files are on a DVD, disconnect the
external DVD drive from the USB port on the left server module, but do not remove
the DVD from the external drive.
Reconfigure the right server module
To reconfigure the right server module:
1. Use PuTTY to establish a serial connection to the right server module, as described in
"Using a PuTTY serial connection" on page 35.
insert that drive into a USB port on the right server module.
¡ If the HCP S Series OS and software installation files are on a DVD, connect the
external DVD drive to a USB port on the right server module.
3. Reboot the right server module in either of these ways:
1. Right-click in the window title bar. Then select Special Command ► Break.
2. Enter b.
bottom right corner of the module and then gently pressing the paper clip against the
The BIOS Main page appears.
Then press Enter.
Enter.

boots using the installed OS. In this case, you need to reboot the server module.
15. When prompted for a password, enter the Boot Manager password for S10 and S30
Nodes.
16. In the Please select boot device menu, arrow down to the entry for the installation USB
flash drive or DVD. Then press Enter.
Reinstall the OS on the right server module and the software on both server modules
To reinstall the OS on the right server module and the software on both server modules:
window, arrow up to HCPSOS Operating System under SERIAL. Then press Enter.
3. In response to the confirming prompt, enter y.

The OS reinstallation starts on the right server module. When the OS reinstallation
finishes, the right server module automatically reboots
4. As soon as the right server module starts to reboot, take one of these actions, as
applicable:
remove that drive from the USB port on the right server module.
¡ If the HCP S Series OS and software installation files are on a DVD, remove the
DVD from the external DVD drive. Then disconnect the DVD drive from the USB
port on the right server module.
After the right server module finishes rebooting, the HCP S Series software installation
program starts on the right server module. The program first performs a series of
prechecks. If all the prechecks are successful, the program reinstalls the software on
both server modules.
When the software reinstallation finishes, both server modules automatically reboot, and
the S Series Node starts synchronizing the database drives.
For information about the installation prechecks, see "Software reinstallation prechecks"
on page 91.

Tip: You can close the PuTTY session and disconnect the laptop computer from the
server module at any time after you select the OS installation option. However, if you
want to monitor the reinstallation process, you should leave the PuTTY session open on
the right server module.
The portion of the reinstallation process that goes from the time the OS reinstallation starts
on the right server module to the time the database drive synchronization starts takes
approximately 25 minutes.
Performing a custom software reinstallation
For a custom software reinstallation, you first reconfigure the left server module and reinstall
the OS on that module. Then you reconfigure the right server module and reinstall the OS on
that module. After the OS is reinstalled on both server modules, the software reinstallation
starts automatically.
Prepare for the server module reconfiguration

To prepare for the server module reconfiguration:
1. Ensure that Ethernet cables are connected to all four ports on each S10 Node server
module, as described in Step 1: "Prepare for the software reinstallation" on page 66.
Reconfigure the left server module
To reconfigure the left server module:
1. Use PuTTY to establish a serial connection to the left server module (when viewed from
the rear of the rack), as described in "Using a PuTTY serial connection" on page 35.
insert that drive into a USB port on the left server module.
1. Connect the external DVD drive to a USB port on the left server module.
3. Reboot the left server module in either of these ways:
1. Right-click in the window title bar. Then select Special Command4Break.
2. Enter b.



Then press Enter.

Enter.




Reinstall the OS on the left server module

To reinstall the OS on the left server module:
window, with HCPSOS Operating System custom under SERIAL highlighted, press
Enter.

4. Respond to the next series of prompts with the applicable values for the customer-
specific S Series Node configuration. The table below lists the settings you are prompted
for, along with their default values. For prompts that have a default value in square
brackets, you can press Enter to accept that value.
Prompt Value
Configure a distributor SSH key? y or n

The default is n.
Distributor SSH key Name of the distributor key for the S Series
Node
The default is Atlantic.
Access network bonding mode 802.3ad or active-backup

The default is active-backup.
Access network IP mode IPv4 or IPv6

The default is IPv4.
Provide VLAN ID for access network? y or n

The default is n.
Access network VLAN ID VLAN ID for the access network

The default is 0.
For access network IP mode IPv4 only
Access network IPv4 address Access network IPv4 address for the server
module on the left
The default is 10.0.0.1
Access network IPv4 netmask Access network IPv4 subnet mask

Access network IPv4 gateway address Access network IPv4 gateway address
Access network IPv6 address Access network primary IPv6 address for the
server module on the left
No default
Access network IPv6 prefix length Access network primary IPv6 prefix length
The default is 64.
Access network IPv6 gateway address Access network primary IPv6 gateway
address
No default

(Continued)
Prompt Value
Access network secondary IPv6 address Access network secondary IPv6 address for
the server module on the left
No default
Access network secondary IPv6 prefix Access network secondary IPv6 prefix
length length
The default is 64.
Access network secondary IPv6 gateway Access network secondary IPv6 gateway
address address
No default
Management network IP mode IPv4 or IPv6

Provide VLAN ID for management y or n

network?
The default is n.
Management network VLAN ID VLAN ID for the management network

The default is 0.
For management network IP mode IPv4 only
Management network IPv4 address Management network IPv4 address for the
server module on the left
The default is
10.2.2.1.
Management network IPv4 netmask Management network IPv4 subnet mask

The default is 255.255.255.0.
Management network IPv4 gateway Management network IPv4 gateway

address address
Management network IPv6 address Management network primary IPv6 address

for the server module on the left
No default
Management network IPv6 prefix length Management network primary IPv6 prefix
length
The default is 64.
Management network IPv6 gateway Management network primary IPv6 gateway

address address
No default

(Continued)
Prompt Value
Management network secondary IPv6 Management network secondary IPv6

address address for the server module on the left
No default
Management network secondary IPv6 Management network secondary IPv6 prefix

prefix length length
The default is 64.

gateway address gateway address
No default
Server interconnect network IPv4 subnet Server interconnect network IPv4 subnet
Is this correct? No default

(if correct, enter y)
(if incorrect, enter n; in this case, you are
prompted to reenter the network values)
The OS reinstallation starts on the left server module. When the reinstallation finishes,
the server module automatically reboots. The left server module then waits for the
OS reinstallation to finish on the right server module.
5. After the left server module starts to reboot, take one of these actions, as applicable:
remove that drive from the USB port on the left server module.
¡ If the HCP S Series OS and software installation files are on a DVD, disconnect the
external DVD drive from the USB port on the left server module, but do not remove
the DVD from the external drive.
Reconfigure the right server module
To reconfigure the right server module:
1. Use PuTTY to establish a serial connection to the right server module, as described in
"Using a PuTTY serial connection" on page 35.
insert that drive into a USB port on the right server module.
¡ If the HCP S Series OS and software installation files are on a DVD, connect the
external DVD drive to a USB port on the right server module.
3. Reboot the right server module in either of these ways:
1. Right-click in the window title bar. Then select Special Command ► Break.
2. Enter b.

bottom right corner of the module and then gently pressing the paper clip against the
The BIOS Main page appears.
Then press Enter.
Enter.
boots using the installed OS. In this case, you need to the reboot the server module
again.
15. When prompted for a password, enter the Boot Manager password for S10 and S30
Nodes.
16. In the Please select boot device menu, arrow down to the entry for the installation USB
flash drive or DVD. Then press Enter.
Reinstall the OS on the right server module and the software on both server modules
To reinstall the OS on the right server module and the software on both server modules:
Enter.


4. Respond to the next series of prompts as indicated in the table below.
Prompt Value

The default is n.
Distributor SSH key Name of your distributor key



The default is n.

The default is 0.
module on the right
server module on the right
No default
The default is 64.

(Continued)
Prompt Value
Access network IPv6 gateway address Access network primary IPv6

gatewayaddress
No default
the server module on the right
No default
length length
The default is 64.
Access network secondary IPv6 gateway Access network secondary IPv6

address gatewayaddress
No default


network?
The default is n.

The default is 0.
server module on the right


address address

for the server module on the right
No default
length
The default is 64.

(Continued)
Prompt Value

address address
No default

address address for the server module on the right
No default

64

No default
Server interconnect network IPv4 subnet 10.1.1.0

The OS reinstallation starts on the right server module. When the OS reinstallation
finishes, the right server module automatically reboots.
5. As soon as the right server module starts to reboot, take one of these actions, as
applicable:
remove that drive from the USB port on the right server module.
port on the right server module.
After the right server module finishes rebooting, the HCP S Series software installation
program first performs a series of prechecks. If all the prechecks are successful, the
program reinstalls the software on both server modules.
When the software reinstallation finishes, both server modules automatically reboot, and
the S Series Node starts synchronizing the database drives.
For information about the installation prechecks, see "Software reinstallation prechecks"
on the next page.
Tip: To monitor the reinstallation process, leave the PuTTY session open on the right
server module.

The portion of the reinstallation process that goes from the time the OS reinstallation starts
on the right server module to the time the database drive synchronization starts takes
approximately 25 minutes.
Software reinstallation prechecks
Before reinstalling the HCP S Series software, the installation program performs a series of
prechecks. If any of these prechecks fail, the program does not reinstall the software.
These prechecks are also performed before an update of the OS and software on an S Series
Node.
The table below lists the prechecks that the installation program performs. For each
precheck, the table explains how the precheck can fail and what you should do in response to
a failure.
Some precheck failures identify the server modules by server interconnect network
IP address. These IP addresses are:
• Server module 1 (left) IP address: 10.1.1.1
• Server module 2 (right) IP address: 10.1.1.2
Precheck Failure description What to do
all network links An Ethernet interface is unavailable. Check that all the Ethernet cables are
correctly connected to both sever
modules and that the cables are
properly seated in their respective
ports.
disk space One or more OS partitions have Contact your HCP support center.
insufficient space available for the
installation.
DiskTypePrecheck A database drive is missing or is not a If the drive is missing, insert a drive of
supported hardware model. the correct type. If the drive is not the
correct type, replace the drive with the
correct type of drive.
firmware versions The firmware on one or more Contact your HCP support center.
components of the S10 Node is not the
correct version for the version of the
HCP S Series software you're trying to
reiinstall.
free space for upgrade of One or both server modules have Make a note of the failed precheck.
internal database insufficient free space for upgrading Then contact your HCP support center.
(checked only during an the internal database on the database
HCP S Series OS and drives the module uses.
software update)

(Continued)
node connections The installation program cannot Check that the server
communicate with one or both server interconnect cable is correctly
modules. connected to both sever modules and
that the cable is properly seated in both
ports.
If the cable is correctly connected but
the link LEDs for the applicable ports
are not lit, replace the cable.
NodeAddressPrecheck Not used as an installation precheck.
RAID synchronization The partitions on the OS drives in a Reinstall the OS on the server module.
server module are not synchronized If that doesn't resolve the issue, replace
with each other. the SSDs in the server module.
repair backlog The S Series Node has storage that If the storage is not repaired within one
(checked only during an needs repair. The upgrade cannot hour, contact your HCP support center.
HCP S Series OS and proceed until the S Series Node
software update) repairs are complete.
run location The installation program cannot Reinstall the OS on the applicable
determine which version of the OS is server module.
installed on the server module on
which the program is running.
running as install The installation program is using an Contact your HCP support center.
incorrect system-internal user account.
SAS topology A server module cannot see the For an enclosure issue, check that the
(checked only during an enclosure or one or more drives in the server module is correctly seated in its
HCP S Series OS and enclosure. slot and that the pins on the back of the
software reinstallation) server module are not damaged. If the
pins are damaged, replace the server
module. If the server module is
correctly seated, reboot it. If rebooting
the server module doesn't resolve the
issue, power the enclosure off and
back on.
For a drive issue, check that all drives
are present and properly seated in their
respective slots.
services One or more services started by the OS Start the OS and software reinstallation
on either server module is still running procedure again. If the services
after 15 minutes. precheck fails again, make a note of
the failed precheck. Then contact your
HCP support center.

(Continued)
SSH connectivity A server module is not responding to Check that both server modules are
an SSH request. powered on and that the OS is installed
on each module. Check that the server
interconnect cable is correctly
connected to both sever modules and
ports.
SSH keys A problem exists with the SSH keys Contact your HCP support center.
used by the S10 Node.
system name Not used as an installation precheck.
systemwide SSH The server modules cannot Check that both server modules are
communicate with each other through powered on and that the OS is installed
SSH. on each module. Check that the server
interconnect cable is correctly
connected to both sever modules and
ports.
versions The version of the OS installed on a Install the correct version of the OS on
server module does support the the server module.
version of the HCP S Series software
you're trying to reiinstall.
waiting for all nodes to One or both server modules are not Check that both server modules are
become available ready for the software to be reiinstalled. powered on and that the OS is installed
on each module. Check that the server
The installation program waits two
hours for both server modules to be interconnect cable is correctly
ready. After two hours, if either server connected to both sever modules and
module is not ready, the precheck fails. that the cable is properly seated in both
ports.
Step 3: Verify the software reinstallation

To verify the success of an HCP S Series software reinstallation, you need to check the
LEDs on the enclosure, on the power and cooling modules in the enclosure, and on the
server modules in the enclosure. For descriptions of these LEDs, see "Physical component
status indicators" on page 50.
For information about what these LEDs mean in terms of an OS and software reinstallation,
see:
• "Software reinstallation in progress" on the next page
• "Successful software reinstallation" on the next page
• "Unsuccessful software reinstallation" on page 95

Software reinstallation in progress
While the HCP S Series OS and software are being reinstalled, various LEDs on the
enclosure and server modules either blink or are lit solid:
• While the OS is being reinstalled, the blue identity LED on the applicable server module
blinks.
• During the software installation prechecks, the blue software install LED on the
enclosure is lit solid.
• During the software reinstallation, the blue software install LED on the enclosure blinks.
When the software reinstallation is complete, this LED turns off.
• Near the end of the software reinstallation, the green software OK LED and amber drive
fault LED on the enclosure start blinking to indicate that the S10 Node has started
synchronizing the database drives.
Successful software reinstallation
After a successful software reinstallation:
• On the front of the enclosure, the green power LED is lit solid.
• On the front of the enclosure, the green software OK LED and the amber drive fault LED
blink while the S10 Node synchronizes the database drives. This process takes
approximately 20 minutes. When the synchronization is compete, the software OK LED
is lit solid and the drive fault LED turns off.
• On each power and cooling module, the green DC OK LED and the green AC OK LED
are all both solid. No other LEDs on the power and cooling modules are lit.
• On each server module, the green power LED is lit solid. No other LEDs on the server
modules are lit.
A software reinstallation can succeed even if a problem exists with a power and cooling
module (PCM) . In this case, the enclosure fault LED is solid, and the applicable power and
cooling LEDs are either off or blinking, as described in the table below.
LEDs Meaning Action
Enclosure fault solid The power and Ensure that the power and cooling
and cooling module module is plugged in. If the module is
PCM no lights either is not plugged in, replace the module.
plugged in or is
faulty.
Enclosure fault solid The power and Replace the power and cooling module.
and cooling module is
PCM fault solid faulty.
For instructions on replacing a power and cooling module, see "Replacing a power and
cooling module" on page 132.
If, after you fix the problem with the power and cooling module, all of the following are true,
the software reinstallation was successful:
• The enclosure fault LED turns off.

• The power and cooling fault LED becomes solid.
• No other LEDs indicate a problem.

After a successful software reinstallation, you don't need to wait for the database drive
synchronization to finish before you:
• Remove the installation USB flash drives from the server modules
• Disconnect the access and management network cables from the server modules
Important: Do not disconnect the purple server interconnect cable while the database
drive synchronization is in progress. Doing so causes the software reinstallation to be
unsuccessful.
• Run the HCP S Series Node post-install script to set the S Series Node serial number
and, if applicable, enable data-in-flight encryption
However, if a database drive error occurs after you remove the USB flash drives or
disconnect the cables, you need to reconnect the cables and reinsert the flash drives in order
to reinstall the software. If a database drive error occurs after you run the HCP S Series
Node post-install script, you need to run the script again after you reinstall the software.
For instructions on running the post-install script, see Step 4: "Run the post-install script" on
page 97.
Unsuccessful software reinstallation
A reinstallation of the HCP S Series OS and software can fail for a variety of reasons,
including faulty hardware and corrupt software. If a reinstallation fails, you can use the LEDs
on the enclosure and server modules (SMs) to help determine the cause of the failure.
The table below lists LED states that indicate a failed OS or software reinstallation and
describes the actions to take in response to them. If a reinstallation fails and the LEDs do not
match any of states listed in the table, contact your HCP support center for help.
LEDs Meaning Action
Enclosure software fault solid The server Use the rocker switches on the power and cooling
and interconnect cable is modules to power both power and cooling
Enclosure software install solid faulty. modules off. Replace the server interconnect
and cable. Then perform a default software
Both SM faults blinking reinstallation or custom software reinstallation, as
applicable.
Enclosure software fault solid The OS reinstallation Try these in the order shown:
and failed.
SM fault solid in one SM 1. Prepare a new USB flash drive or DVD with
and the same software version as before. Use the
SM identity blinking in the same rocker switches on the power and cooling
SM modules to power both power and cooling
modules off. Then perform a default software
reinstallation or custom software
reinstallation, as applicable, using the new
USB flash drive or DVD.

(Continued)
LEDs Meaning Action
2. Use the rocker switches on the power and

cooling modules to power both power and
cooling modules off. Replace the SSDs in the
problem server module with new SSDs. Then
perform a default software reinstallation or
custom software reinstallation, as applicable.
3. Use the rocker switches on the power and
cooling modules to power both power and
cooling modules off. Replace the problem
server module with a new server module.
Move the SSDs from the problem server
module to the new server module. Then
perform a default reinstallation or custom
software reinstallation, as applicable.
4. Contact your HCP support center for help.
Support personnel may give you a new
version of the HCP S Series OS and software.
In this case, use the rocker switches on the
power and cooling modules to power both
power and cooling modules off. Then perform
a default software reinstallation or custom
Enclosure software fault solid Either the server Use the rocker switches on the power and cooling
and module has modules to power both power and cooling
Enclosure software install solid insufficient memory or modules off. Replace the problem server module
and a faulty Ethernet port, with a new server module. Move the SSDs from
SM fault solid in one SM or one or more the problem server module to the new server
and components of the module. Then perform a default software
SM identity blinking in the same server module have
reinstallation or custom software reinstallation, as
SM incorrect firmware
applicable.
versions.
Enclosure drive fault solid or Either the database Check the database drives inside the enclosure:
blinking drive configuration is
and invalid, the enclosure • If any database drives have a blinking blue
Enclosure software fault solid cannot read from the LED, replace those drives. Then, use the
and database drives, or rocker switches on the power and cooling
Enclosure software install solid one or more database modules to power both power and cooling
and drives are faulty. modules off. Perform a default software
Either SM fault solid installation or custom software reinstallation,
and as applicable. If the reinstallation fails again
Either SM identity blinking with the same symptoms, replace the
enclosure. Then perform a default software
reinstallation or custom software reinstallation
again, as applicable.
• If no database drives have a blinking blue

LED, replace the enclosure. Then perform a
default software reinstallation or custom

(Continued)
LEDs Meaning Action
Enclosure drive fault solid Either one or more Check the data and database drives inside the
data or database enclosure. Replace any drives that have a blinking
drives are faulty, or an blue LED. Then, use the rocker switches on the
error occurred during power and cooling modules to power both power
the database drive and cooling modules off. Perform a default
synchronization software reinstallation or custom software
process. reinstallation, as applicable.
For instructions on replacing the various components of an S10 Node, see:
• "Replacing data and database drives" on page 125
• "Replacing a server module" on page 177
• "Replacing the server interconnect cable" on page 188

For instructions on reinstalling the OS and software, see:
• "Performing a default software reinstallation" on page 70
• "Performing a custom software reinstallation" on page 78
Step 4: Run the post-install script

The HCP S Series Node post-install script:
• Sets the S Series Node serial number for the S10 Node
• Verifies that the S10 Node has the correct number of drives
• Checks for any outstanding error conditions
• If applicable, disables support for data-in-flight encryption
• Disables SSH access to the S10 Node server modules

To run the post-install script, you need to know:
• The S10 Node serial number.

The serial number is on a label in the front right corner on the top of the enclosure.
• The total number of data and database drives in the S10 Node enclosure.
A half-populated enclosure has a total of 32 data and database drives. A fully populated
enclosure has a total of 60 data and database drives.
For instructions on getting the post-install script, see.
To run the post-install script, you use your laptop computer to connect directly to the S Series
Node over the management network. This means that your laptop computer must be on the
subnet used for the management network. After a default reinstallation of the HCP S Series
OS and software, this subnet is 10.2.2.0/24.
To run the post-install script:
1. If you have not already done so, add the S Series Node root SSH key to the SSH
keychain on your laptop computer, as described in "Adding an S Series Node SSH key

to your SSH keychain" on page 35.

2. On the server modules, disconnect any cross-connected cables from the access and
management ports.
3. If you previously removed SFP+ modules from the access ports, reinsert the modules
into those ports.
4. If the management port on the left server module (when viewed from the rear of the
enclosure) is connected to a switch in the customer network, disconnect the cable from
that management port.
5. Connect CAT6 Ethernet cable to the management port on the left server module and to
the Ethernet port on your laptop computer.
The management port is the third Ethernet port from the left on the back of the server
module.
6. Reconfigure your laptop computer as described in "Reconfiguring your laptop computer

for SSH access" on page 37, but do not configure or start a PuTTY session. When you
run the post-install script, the script automatically creates a PuTTY SSH connection
between the laptop computer and the left server module.
7. On your laptop computer, open a Windows Command Prompt window.
8. Change to the directory in which you stored the hcps_post_install.bat file.
9. Enter the command to run the post-install script, using this syntax:
hcps_post_install.bat ip-address serial-number 1 number-of-drives
In this command:
¡ ip-address is the IP address of the left server module on the management
network.
¡ serial-number is the five-digit portion of the serial number for the S10 Node. This
number must match the number that follows HCPS on the serial number label.
¡ 1 (one) is the number of enclosures in the S10 Node.
¡ number-of-drives is the total number of data and database drives in the S10 Node
enclosure.
For example:
hcps_post_install.bat 10.2.2.1 12345 1 60
10. If you are prompted to cache your SSH key, enter y.

11. In response to the prompt for whether the S Series Node should allow data-in-flight
encryption:
¡ To allow data-in-flight encryption, enter y.
y is the standard response to this prompt.
¡ To prevent data-in-flight encryption, enter n.
Important: Be sure to respond correctly to this prompt. If you enter y when the S10
Node is not supposed to support data-in-flight encryption, the S Series Node will be in
violation of export control regulations.
If you enter y, a confirming prompt appears.

12. If the confirming prompt appears, enter y to confirm your response to the previous prompt
or n to try again.
After you specify whether to allow data-in-flight encryption, the post-install script verifies
the numbers of enclosures and drives, sets the serial number for the S10 Node, and, if
applicable, disables data-in-flight encryption:
¡ If any of these actions is unsuccessful, the script displays an error message and
then stops.
¡ If all these actions are successful, the script checks for outstanding error conditions.
If any such conditions exist, the script displays information about them in the form of
alerts and then stops.
¡ If all these actions are successful and no error conditions exist, the script disables
SSH login and then displays this message.
Post Install Script Complete
13. If the post-install script did not finish successfully, take the applicable actions to resolve
any reported issues. Then run the script again.
Important: After a successful run of the post-install script, you cannot run the script
again because SSH access is now disabled on the S10 Node. If you incorrectly enabled
or disabled support for data-in-flight encryption when you ran the script, you need to
reinstall the HCP S Series OS and software in order to run the script again.
Step 5: Configure the S Series Node

To configure the S Series Node:
1. On the laptop computer, open a web browser. Then, in the address field, enter the URL
below, where ip-address is the IP address of the left server module on the management
network:
https://ip-address:8000
After a default reinstallation of the HCP S Series OS and software, this IP address is
10.2.2.1.
2. When prompted, accept the self-signed HCP S Series Node SSL server certificate.
The HCP S Series Management Console opens and displays the Getting Started page
of the first-time setup wizard.

3. Click Next.
4. On the Identification page, specify the domain name and, if missing, the serial number
for the S Series Node. Then click Next.
5. On the User page, specify the password for the admin user account. Then click Next.
Note: If the customer wants to keep the password for the admin user account private,
have the customer type the password on the User page.
6. On the Access Network page, specify the access network settings. Then click Next.
7. On the Management Network page, specify the management network settings. Then
click Next.
8. On the Server Interconnect Network page, specify the subnet for the server
interconnect network. Then click Next.
9. On the DNS & Time Servers page, specify the DNS and time servers to be used by the
S Series Node. Then click Next.
10. On the Review page, review the initial S Series Node configuration settings:
¡ If all the settings are correct, click Finish.
The S Series Node reboots. When the S Series Node becomes available again, you
are automatically redirected to the Management Console.
¡ If you need to change any settings, use the Previous button to return to the
applicable page and make the corrections you want. Then return to the Review page
and, if all the settings are correct, click Finish.
11. Disconnect your laptop computer from the server module. Then change the network
connection properties on the laptop computer back to their original settings.
12. If the management port on the left server module was previously connected to a switch
in the customer network, reconnect the cable to that management port.
Step 6 (conditional): Have the customer enable SSH access to the server
modules
The post-install script disables SSH access to the S Series Node server modules. After you
configure the S Series Node, the customer can choose to enable SSH access. SSH access
facilitates troubleshooting when the customer requests support.
Alternatively, the customer can choose to leave SSH access disabled. Keeping SSH access
disabled enhances the security of the S Series Node but can increase the amount of time
required to diagnose and resolve issues.
While SSH access is disabled, this banner appears at the top of each page in the HCP S
Series Management Console:
SSH is disabled.
For users with the security role, this banner is a link to the Configuration ► Security page.
Customers who want to enable SSH access should perform the procedure themselves using
the instructions below.

Recovering a server module
To enable SSH access to an HCP S Series:

1. Log in to the HCP S Series Management Console using the initial admin user account.
For the Management Console URL:
¡ If the HCP S Series is configured in DNS, use:
https://admin.s-series-node-domain-name:8000
s-series-node-domain-name is the fully qualified domain name of the HCP S Series.

¡ If the HCP S Series is not configured in DNS, use:
https://access-network-virtual-ip-address:8000/admin
access-network-virtual-ip-address is the IPv4 or IPv6 virtual IP address of one of the

server modules on the access network. If the access network is configured for IPv6,
you can use either the primary or secondary virtual IP address.
If the virtual IP address is IPv6, enclose the IP address in square brackets.
2. Go to Configuration ► Security.
3. Change the setting for SSH enabled to ON.
4. Click Save Settings.

After you replace both OS SSDs in a server module, you need to recover that server module.
After you replace a server module, where the new server module contains two new OS
SSDs, you need to recover the new server module. Recovering a server module entails
performing a custom reinstallation of the HCP S Series OS and software on the module.
Tip: Before starting the server-module recovery, use the "Appendix: HCP S Series Node
Configuration Information form" on page 214 to record the customer-specific configuration
settings for the server module you're recovering. Then keep the form with you when you
perform the recovery so you have easy access to the information you need.
What you need for recovering a server module

For recovering a server module, you need:
• If the management ports on the server modules are not connected to switches in the
customer network, one CAT6 Ethernet cable to connect the ports to each other.
• A laptop computer with the HCP S Series Node root SSH key in the SSH keychain on
the computer. For instructions on adding this key to the keychain on your laptop
computer, see "Adding an S Series Node SSH key to your SSH keychain" on page 35.
• A USB-to-mini-USB cable.
• One bootable USB flash drive or DVD that contains the HCP S Series OS and software
installation files for the software release that's currently installed on the S10 Node.
If you don't already have an OS and software installation USB flash drive or DVD, you
need to create one, as described in "Preparing an installation USB flash drive or DVD".

• A paper clip. You need a paper clip only if the HCP S Series Management Console is
currently unavailable.
• TheHCP S10 Node BIOS password.

If you are a Hitachi Vantara employee, you download the BIOS password from the
Hitachi Vantara SharePoint site at:
https://sharepoint.hitachivantara.com/sites/HitachiContentArchivePlatform/SitePages/Ho
me.aspx
If you are providing service on behalf of an authorized S Series Node distributor, you get
the BIOS password from the HCP S Series Node Product Management team.
• This information:
¡ The name of the distributor key for the S Series Node if the key is not Atlantic.
¡ The current network configuration settings for the server module you're recovering.
You need the settings for the access network, management network, and server
interconnect network.
You can use the HCP S Series Management Console or the HCP S Series
management API to get the current network configuration settings.
¡ The domain name and serial number for the S Series Node.
Tip: Before starting the server-module recovery, use the HCP S Series Node
Configuration Information form on page 215 to record the customer-specific
configuration settings for the server module you're recovering. Then keep the form with
you when you perform the reinstallation so you have easy access to the information you
need.
Step 1: Prepare for the server-module recovery

For a server-module recovery, you need cables connected to the Ethernet ports on the server
module you're recovering. The server interconnect port on the server module should already
be connected to the applicable ports on the other server module. The access ports should
already be connected to switches in the customer network.
If the management port is not connected to a switch in the customer network, you need to
cross-connect that port with the management port on the other server module.
The figure below shows the locations of the Ethernet ports on the server modules.

To prepare to recover a server module:

1. If the management port on the server module you want to recover is not connected to a
switch in the customer network, use one CAT6 Ethernet cable to connect that port to the
management port on the other server module.
When inserting the cable into each port, push the cable in until the end clicks into place.
2. Use PuTTY to establish a serial connection to the server module you want to recover, as
described in "Using a PuTTY serial connection" on page 35.
insert that drive into a USB port on the server module you want to recover.
1. Connect the external DVD drive to a USB port on the server module you want to
recover.
Step 2: Reconfigure the server module you want to recover

To reconfigure the server module you want to recover:
1. If the server module you want to recover is powered on, reboot the module in either of
these ways:
¡ From the HCP S Series Management Console:
1. On the Hardware►Overview or Hardware►Maintenance page, click Power
Options.
2. In the Server Module field, select the server module you want to recover.
3. In the Reason field, type the reason why you're rebooting the server module.
4. Click Restart.

2. If the server module you want to recover is powered off, power on the module in either of
these ways:
¡ From the HCP S Series Management Console:
1. On the Hardware►Overview or Hardware►Maintenance page, click Power
Options.
2. In the Server Module field, select the server module you want to recover.
3. In the Reason field, type the reason why you're powering on the server module.
4. Click Power On.
power button for two seconds.



Then press Enter.
Enter.



Step 3: Reinstall the HCP S Series OS on the server module

To reinstall the HCP S Series OS on the server module you're recovering:
Enter.

2. In response to the prompt for the OS installation mode, enter: r
Caution: If the R option is not present, enter e to exit the installation. Then contact your
HCP support center for help.
Do not enter i. Option I destroys all data stored on the S Series Node.
3. In response to the prompt to preserve the database backup partition, enter y.
4. Respond to the next series of prompts with the applicable values for the customer-
specific S Series Node configuration. The table below lists the settings you are prompted
for, along with their default values. For prompts that have a default value in square
brackets, you can press Enter to accept that value.
Prompt Value

The default is n.
Distributor SSH key Name of the distributor key for the S Series
Node



The default is n.

The default is 0.

(Continued)
Prompt Value
module on the left
For the server module on the left, the
default is 10.0.0.1.
For the server module on the right, the
server module
No default
The default is 64.
Access network IPv6 gateway address Access network primary IPv6 gateway
address
No default
the server module
No default
length length
The default is 64.
Access network secondary IPv6 gateway Access network secondary IPv6 gateway
address address
No default


network?
The default is n.

(Continued)
Prompt Value

The default is 0.
server module
For the server module on the left, the
For the server module on the right, the



address address

for the server module
No default
length
The default is 64.

address address
No default

address address for the server module
No default

The default is 64.

No default
Server interconnect network IPv4 subnet Server interconnect network IPv4 subnet

(Continued)
Prompt Value

The OS reinstallation starts on the server module. When the reinstallation finishes, the
server module automatically reboots.
5. After the server module starts to reboot, take one of these actions, as applicable:
remove that drive from the USB port on the server module.
port on the server module.
6. Disconnect the USB-to-mini-USB cable from your laptop computer and from the the
server module.
Step 4: Reinstall the HCP S Series software on the server module

To reinstall the HCP S Series software on the server module you're recovering:
1. If you have not already done so, add the S Series Node root SSH key to the SSH
keychain on your laptop computer, as described in "Adding an S Series Node SSH key
to your SSH keychain" on page 35.
2. Use PuTTY to establish an SSH connection to the server module that you are not
recovering, as described in "Using a PuTTY SSH connection" on page 36.
4. At the command-line prompt, enter this command to switch to the install user and open a
bash shell:
su install -c /bin/bash
5. Enter this command to switch to the genesis directory:

cd genesis
6. Enter this command to reinstall the HCP S Series software on the server module you're
recovering:
./genesis.py server-module-recovery --target ip-address
In this command, ip-address is the server interconnect network IP address of the server
module you're recovering. For server module 1, the fourth octet in this IP address is 1.
For server module 2, the fourth octet is 2.
The HCP S Series software installation program starts on the server module. The
program first performs a series of prechecks. If all the prechecks are successful, the
program reinstalls the software on the server module.

When the software reinstallation finishes, the server module you're recovering
automatically reboots.
For information about the reinstallation prechecks and what to do in case of a software
reinstallation failure, see "Software reinstallation prechecks" on page 91.

Chapter 7: Maintaining data and database drives
You can add, remove, and replace data and database drives in an HCP S10 Node. You can
perform each operation on one or more drives at a time. However, you cannot combine
different operations in a single procedure.
For each operation you want to perform, you need to both start and end the procedure in the
HCP S Series Management Console or by using the HCP S Series management API. If you
don't start and end the procedure in this way, the HCP S10 Node does not properly recognize
that the operation has occurred. For example, if you add a drive without going through the
Management Console or management API procedure, the HCP S10 Node won't use that
drive.
A Management Console session can time out while you’re performing a hardware
maintenance procedure. If this happens, you can log back into the Console to continue the
procedure.
After you start a drive maintenance procedure, you can cancel it between steps if you're
using the Management Console to perform the procedure or at any time if you're using the
management API. After you select the target slots for a procedure, if you don't end the
procedure within four hours, the HCP S10 Node automatically cancels it.
While a procedure is in progress, it's listed in the Maintenance Procedure in Progress
section on the Management Console Hardware►Maintenance page. When a procedure
ends or is canceled, it moves to the Maintenance History list on that page. To view details
about a listed procedure, click the gear icon ( ) for it.
Similarly, while a procedure is in progress, you can use the management API to retrieve
information about it. You can also use management API to retrieve the maintenance
procedure history list.
To add, remove, or replace data or database drives, you need to open the enclosure cover.
When you open the cover, an alarm sounds intermittently. If the cover remains open for more
than five minutes, the alarm becomes continuous. The alarm stops when the cover is closed.
Important: Do not perform multiple hardware maintenance procedures at the same time (for
example, replacing the enclosure while adding data drives). Doing so can have unpredictable
results.
This chapter contains:
• Considerations for maintaining data and database drives
• Instructions for adding data and database drives to an S10 Node
• Instructions for removing data and database drives from an S10 Node
• Instructions for replacing data and database drives in an S10 Node

Considerations for maintaining data and database drives
Considerations for maintaining data and database drives

These considerations apply to maintaining data and database drives:
• You cannot remove or replace more than one database drive in a single operation.
However, in an operation in which you remove or replace a database drive, you can also
remove or replace one or more data drives.
• While the database drive in slot 29,30, or 31 is unavailable, you cannot remove or
replace the database drive in another one of those slots. However, you can remove or
replace the database drive in slot 32.
• While the database drive in slot 32 is unavailable, you can remove or replace the
database drive in only one of slots 29,30, and 31.
• If two or more database drives have failed, one or more of these drives may not appear in
the list of drives that are eligible to be removed or replaced. If this happens:
¡ For a remove drives procedure, first remove the database drives that appear in the
list. Then add new database drives to replace the drives you removed. Wait for the
S10 Node to finish synchronizing the new database drives with the existing
database drives. Then repeat the remove drives procedure to remove the remaining
failed database drives.
¡ For a replace drives procedure, first replace the database drives that appear in the
list. Wait for the S10 Node to finish synchronizing the new database drives with the
existing database drives. Then repeat the replace drives procedure to replace the
remaining failed database drives.
• If, while a new or replacement database drive is being synchronized, the database drive
with which it is being synchronized fails, the new or replacement drive also fails, and the
status of the new or replacement drive changes to "Database drive not synchronized."
To recover from this situation, use maintenance procedures to remove the replacement
drive and then add it back again.
Adding data and database drives

You can add data and database drives to an S10 Node. Typically, you add data drives to
convert a half-populated S10 Node to a fully populated S10 Node. You would also add data or
database drives to recover from a situation in which drives were incorrectly removed from
one or more slots.
DANGER: Do not leave more than one enclosure extended out of the rack at the
same time. With more than one enclosure extended, the rack can tip over, causing
personal injury to people in the area.
What you need for adding drives

For adding data or database drives to an S10 Node, you need:
• The applicable number of new data and/or database drives

Drive upgrade kit part number (contains 28 data drives):

¡ For 6TB drives: ASM-01655-02-A.P or ASM-02301-01-A.P (try ordering ASM-01655-
02-A.P first)
¡ For 10TB drives: ASM-01655-06-A.P
Individual data drive part number:
¡ For 6TB drive: ASM-01664-02-A.X or ASM-02313-01-A.X (try ordering ASM-01664-
02-A.X first)
¡ For 10TB drive: ASM-01663-03-A.X
Database drive part number:
¡ For 6TB drive: ASM-01663-02-A.X or ASM-02313-01-A.X (try ordering ASM-01663-
02-A.X first)
¡ For 10TB drive: ASM-01663-03-A.X
• A #1 or #2 Phillips screwdriver, depending on the type of screws used to secure the

enclosure to the rack
Step 1: Start the drive addition procedure

To start the procedure for adding data and database drives to an S10 Node:
1. Have the HCP S Series Node security administrator set the HCP S Series Management
Console session timeout interval to at least 60 minutes.
2. Unwrap all the new drives to be added to the S10 Node.
role.
4. Go to the Hardware ► Overview or Hardware ► Maintenance page.
5. Click Begin Maintenance.
6. In the Maintenance Procedure field, select Add Drives. Then click Go.
Tip: At any time during the maintenance procedure, you can enter new notes or edit
existing notes in the Notes field on the procedure page. To do this:
1. Click in the Notes field.
2. Type or edit the text you want. This text can be up to 1,024 characters long and can
contain any valid UTF-8 characters, including white space.
3. Click Save Notes.
7. In the Select Slots list, select the slots into which you want to insert new drives. The list
includes only empty slots. It does not include slots identified as having unavailable
drives.
Selecting the box at the left end of the heading row for the slot list selects all slots in the
list, not just the slots that are currently visible. Similarly, deselecting the box deselects
all slots in the list.
8. Click Continue.

The blue identity LED on the front of the enclosure starts blinking. Additionally, the blue
LED at the bottom of each selected slot starts blinking.
9. Optionally, click Enclosure Diagram to display a diagram that shows the layout of the
slots in the enclosure. In this diagram, the slots you selected have a dark gray outline.
Tip: To ensure that you act on the correct slots, print the enclosure diagram and bring it
with you to the S10 Node.
Step 2: Insert the new drives into the selected slots

To insert the new drives into the selected slots:
¡ If the enclosure is secured to the rack with two medium black screws on each side
of the front of the enclosure, using the #2 Phillips screwdriver, unscrew and remove
those screws.
¡ If the enclosure is secured to the rack with two small silver locking screws on each
side of the front of the enclosure, using the #1 Phillips screwdriver, unscrew those
screws until they are very loose. The screws do not come out.
2. Push in the tabs on both sides of the front of the enclosure behind the front panel and pull
the enclosure forward. Then slide the enclosure out of the rack as far as the enclosure
goes.

3. Lift both latches on the top of the enclosure and pull up to open the right side of the
enclosure cover.
4. Push down on the two release latches for the left side of the enclosure cover. Then pull
up that side to open it.
The slots you selected for the drive addition procedure have a blinking blue LED at the
bottom. Be sure to insert drives into only those slots.
If a selected slot in a half-populated enclosure contains an empty drive placeholder, the
blinking blue LED is under the placeholder. Placeholders would be in slots 27, 28, 33,
and 34.
If the LEDs for one or more selected slots are not blinking, the cause may be that those
LEDs are not functioning properly.
5. For each drive you want to insert into a slot:
a. If the slot contains an empty drive placeholder, with your finger hooked under the rim
of the hole in the top of the placeholder, pull the placeholder straight up out of the
slot.
b. Push back on the tab on the top of the drive.
The latch on the top of the drive pops open.
Caution: Do not pull the latch open past a 45-degree angle. Doing so will damage
the latch.
c. Slide the drive all the way down into the slot.
d. Close the latch, pushing down until it clicks into place.
After a few seconds, the blue LED on the top of the drive starts blinking, but at a slower
rate than that at which the LED at the bottom of the slot was blinking before the drive
was inserted into the slot.
If you remove or replace the drive in a slot that was not selected, the S10 Node
immediately starts the repair process to ensure that no data is lost and that all data is still
protected.
6. Close the left side of the enclosure cover.
7. Close the right side of the enclosure cover, pushing down until it clicks into place.

8. While pushing back the green plastic sliders at the front end of the rails on both sides of
the enclosure, push back on the enclosure to release it. Then slide the enclosure all the
way back into the rack until the enclosure clicks into place.
¡ If the enclosure was secured to the rack with four medium black screws, using the
#2 Phillips screwdriver, screw those screws back into the four screw holes on the
front of the enclosure (two on each side).
¡ If the enclosure was secured to the rack with two small silver locking screws on
each side of the front of the enclosure, using the #1 Phillips screwdriver, screw
those screws back in.
Step 3: Verify the drive addition

After you've inserted data or database drives into all the selected slots, you need to verify
that the drive addition occurred correctly. Then you need to end the drive addition
maintenance procedure.
To verify the drive addition and end the procedure, in the HCP S Series Management
Console:
1. If the current page is not the Add Drives page, as applicable:
a. Go to Hardware ► Maintenance.
b. In the Maintenance Procedure in Progress section, click the gear icon ( ) for the
add drives procedure, as applicable.
Tip: While a hardware maintenance procedure is in progress, a message to that effect

appears at the top of each page in the Management Console. To go directly to the page
for the procedure, click the procedure name in the message.
2. To allow the S10 Node time to recognize the new drives, ensure that at least 30 seconds
have elapsed since the last new drive was inserted into a slot.
3. On the Add Drives page, click Done.
4. On the Add Drives page, click Verify.
The S10 Node checks that all the selected slots have acceptable drives in them. It also
checks that no drives have been inserted into slots that were not selected for the
procedure.
Note: If you click Cancel instead of or after clicking Verify, the drive addition procedure
ends, and the S10 Node treats all the newly inserted drives as failed drives. To recover
from this, use the drive removal procedure to remove the failed drives. Then use the
drive addition procedure to insert drives into the slots from which you removed the failed
drives.
For each selected slot, each unselected slot into which a drive was inserted, and each
unselected slot in which the drive was removed or replaced, the Management Console
displays a success, warning, or error message, as applicable. These messages appear
below the Verify button.

If error messages identify any slots as containing a drive with a duplicate SAS address
or a drive that doesn't have a valid SAS address, the drives in those slots are not added
to the S10 Node. To recover from this situation, follow the instructions in "SAS address
errors" on the next page.
If any drives inserted into any of the selected slots were previously used in an S Series
Node, an Actions section appears below the messages. This section lists each such
slot with the actions you can choose to take for that slot:
¡ If the drive is a native drive (that is, it was previously used in the current S10 Node,
and the HCP S Series software has not been reinstalled since the drive was
removed), the possible actions are:
– Reuse — Use the drive as is. This action is useful, for example, if the drive was
previously unintentionally removed from the enclosure. In this case, choosing
Reuse may facilitate repairs.
– Format — Format the drive and then use it. All existing data on the drive will be
lost.
¡ If the drive is a foreign drive (that is, it was previously used in a different S Series
Node or in the current S10 Node before the HCP S Series software was reinstalled),
the possible actions are:
lost.
– Discard — Treat the drive as a failed drive. The drive can then be removed in a
new maintenance procedure and possibly reused in the S Series Node from
which it was originally removed.
If any slots that were selected for the procedure do not have drives in them, the slots
return to their previous empty state.
If any drives were removed from unselected slots, the S10 Node treats those slots as
having unavailable drives.
The S10 Node treats the following as failed drives:
¡ These types of drives inserted into selected slots:
– Previously used drives on which the S10 Node had detected errors
– Drives that are bad to start with
– Drives of an unsupported type
¡ Drives inserted into unselected slots
5. If the Actions section is present:
a. For each listed slot, select the action you want to take on the drive in that slot. To
select all the actions under the Format or Other heading, select the applicable
heading.
b. Click Confirm.
c. In the window with the confirming message, click Confirm.
The S10 Node takes the applicable action for each drive.
6. On the Add Drives page, click End Procedure.

When you add database drives, the S10 Node immediately begins synchronizing the new
drives with the existing database drives. This process takes approximately 20 minutes,
during which time, the software OK LED on the front of the enclosure blinks green and the
drive fault LED on the front of the enclosure blinks amber. When synchronization is
complete, the LED turns off.
The synchronization process has no effect on use of the S10 Node.
Note: Processing drives for reuse can take some time. After an add drives procedure is
complete, the S10 Node may continue to report drive additions or drive addition failures until
all the drives selected for reuse have been processed. This behavior is expected. While the
drives are being processed, you can continue to perform maintenance procedures, including
removing and adding back drives that failed to be added.
SAS address errors

When you verify an add drives or replace drives operation, the S10 Node may determine that
one or more new drives have duplicate SAS addresses or do not have valid SAS addresses.
In the case of duplicate addresses, the drives with the duplicate addresses may be either
other new drives or drives that are already part of the S10 Node.
When two or more drives have the same SAS address, the error messages returned in
response to the verify request may show those drives as being in the same slot. In any case,
at least one of the drives involved is marked failed. The other drives with the same address
may be unavailable or marked failed or may have no problem at all. The drives with problems
may be reported in alerts as having a slot status of installed.
Drives without a valid SAS address are unavailable.
To recover from the situation in which one or more drives have SAS address errors, you need
to remove the problem drives from the S10 Node. To do this:
1. Perform a remove drives maintenance procedure. Select all the slots for which the error
messages indicated a SAS address problem exists. Then physically remove the drives
only from the selected slots.
End the procedure by clicking End Procedure. Do not cancel the procedure, even if
error messages are returned for one or more slots.
2. If the remove drives procedure resulted in any error messages, perform a second remove
drives maintenance procedure. This time, select all the slots for which the first remove
drives procedure failed.
After removing drives with duplicate SAS addresses, you can use an add drives
maintenance procedure to add one of the removed drives back to the S10 Node. If one of the
drives was already part of the S10 Node when the problem occurred, add that drive. If the
drives involved were all new, you can add any one of them.
After removing a drive that did not have a valid SAS address, you can use an add drives
maintenance procedure to add that drive back to the S10 Node.

Removing data and database drives

You can remove data and database drives from an S10 Node. Drives that are failed,
unavailable, unresponsive, or experiencing errors are eligible to be removed. Database drives
associated with an unavailable server module are also eligible to be removed, but you should
not remove a database drive unless you know for a fact that the drive has a problem.
Typically, you remove drives to recover from a situation in which drives were incorrectly
added or replaced in one or more slots. You can also choose to remove drives that have
failed even though no replacement drives are available yet.
What you need for removing drives

For removing data or database drives from anS10 Node, you need a #1 or #2 Phillips
screwdriver, depending on the type of screws used to secure the enclosure to the rack.
Step 1: Start the drive removal procedure

To start the procedure for removing data and database drives from an S10 Node:
role.
5. In the Maintenance Procedure field, select Remove Drives. Then click Go.
6. In the Select Slots list, select the slots from which you want to remove drives. The list
includes only slots containing drives that are eligible to be removed. All the slots in the
list are selected by default, except for those containing database drives associated with
an unavailable server module.
7. Click Continue.

LED on the top of the hard disk drive in each selected slot starts blinking.
Step 2: Remove the drives from the selected slots

To remove the drives from the selected slots:
those screws.
goes.

enclosure cover.
The drives that you selected for removal have a blinking blue LED on the top. Drives that
have failed but that have not been selected for removal have a solid blue LED on the top.
Be sure to remove only the drives that have a blinking blue LED.
If the LEDs for one or more selected drives are not blinking, the cause may be that those
5. For each drive you want to remove:
a. Push back on the tab on the top of the drive.
b. Pull up the latch until it clicks into place.
Caution: Do not pull the latch open past a 45-degree angle. Doing so will damage
the latch.
c. Pull up on the latch to slide the drive out of the slot.

After a few seconds, the blue LED at the bottom of the slot starts blinking at a slower
rate than that at which the LED on the top of the drive was blinking before the drive was
removed from the slot.
If you remove the drive from a slot that was not selected, the S10 Node immediately
starts the repair process to ensure that no data is lost and that all data is still protected.

Replacing data and database drives
Step 3: Verify the drive removal

After you've removed the drives from all the selected slots, you need to verify that the drive
removal occurred correctly. Then you need to end the drive removal maintenance procedure.
To verify the drive removal and end the procedure, in the HCP S Series Management
Console:
1. If the current page is not the Remove Drives page
remove drives procedure.

2. To allow the S10 Node time to recognize the drive removal, ensure that at least 30
seconds have elapsed since the last drive was removed from a slot.
3. On the Remove Drives page, click Done.
4. On the Remove Drives page, click Verify.
The S10 Node checks that the drives have been removed from all the selected slots. It
also checks that no drives have been removed from slots that were not selected for the
procedure.
For each selected slot, each unselected slot into which a drive was inserted, and each
unselected slot in which the drive was removed or replaced, the Management Console
displays a success, warning, or error message, as applicable. These messages appear
below the Verify button.
The S10 Node continues to treat drives that were not removed from selected slots as
failed or unavailable, as applicable. It also treats the following as failed drives:
¡ Drives inserted into selected slots
If any drives were removed from unselected slots, the S10 Node treats those slots as
having unavailable drives.
5. On the Remove Drives page, click End Procedure.

You can replace data and database drives in an S10 Node. Drives that are failed,
unavailable, unresponsive, or experiencing errors are eligible to be replaced. Database drives
associated with an unavailable server module are also eligible to be replaced, but you should
not replace a database drive unless you know for a fact that the drive has a problem.

An S10 Node can operate correctly with multiple failed data drives, so you don't need to
replace failed data drives as soon as they fail. The S10 Node issues an alert when the
number of failed data drives reaches the threshold at which the drives must be replaced. This
threshold depends on the total number of data drives in the S10 Node.
You should always immediately replace failed database drives.
Before replacing a data or database drive, ensure that the replacement drive is of a supported
type for the drive you're replacing. For details, see HCP S Series Node 2.2.0 Release Notes.
What you need for replacing drives

For replacing data and database drives in anS10 Node, you need:
• The applicable number of replacement data and/or database drives

Data drive part number: ASM-01664-02-A.X, ASM-02313-01-A.X, or ASM-01663-03-A.X
(to match the part number in the failed-drive alert)
Database drive part number: ASM-01663-02-A.X, ASM-02313-01-A.X, or ASM-01663-
03-A.X (to match the part number in the failed-drive alert)
• A #1 or #2 Phillips screwdriver, depending on the type of screws used to secure the

enclosure to the rack
Step 1: Start the drive replacement procedure

To start the procedure for replacing data and database drives in an S10 Node:
2. Unwrap all the new drives to be used as replacement drives.
role.
6. In the Maintenance Procedure field, select Replace Drives. Then click Go.

7. In the Select Slots list, select the slots in which you want to replace the drives. The list
includes only slots containing drives that are eligible to be replaced. All the slots in the
list are selected by default, except for those containing database drives associated with
an unavailable server module.
8. Click Continue.
LED on the top of each selected slot starts blinking.
Step 2: Replace the drives in the selected slots

To replace the drives in the selected slots:
those screws.

goes.
enclosure cover.
The drives that you selected for replacement have a blinking blue LED on the top. Drives
that have failed but that have not been selected for replacement have a solid blue LED on
the top. Be sure to replace only the drives that have a blinking blue LED.
If the LEDs for one or more selected drives are not blinking, the cause may be that those
5. For each drive you want to replace:
a. Remove the old drive:
1. Push back on the tab on the top of the drive.
2. Pull up the latch until it clicks into place.
Caution: Do not pull the latch open past a 45-degree angle. Doing so will
damage the latch.
3. Pull up on the latch to slide the drive out of the slot.

After a few seconds, the blue LED at the bottom of the slot starts blinking at a slower
rate than the rate at which the LED on the top of the drive was blinking before the
drive was removed from the slot.
b. Insert the new drive:
1. Push back on the tab on the top of the drive.
2. Slide the drive all the way down into the slot.
3. Close the latch, pushing down until it clicks into place.
After a few seconds, the blue LED on the top of the drive starts blinking.
If you remove or replace the drive in a slot that was not selected, the S10 Node
immediately starts the repair process to ensure that no data is lost and that all data is still
protected.
Step 3: Verify the drive replacement

After you've replaced the drives in all the selected slots, you need to verify that the drive
replacement occurred correctly. Then you need to end the drive replacement procedure.
To verify the drive replacement and end the procedure, in the HCP S Series Management
Console:
1. If the current page is not the Replace Drives page
replace drives procedure.

2. To allow the S10 Node time to recognize the replacement drives, ensure that at least 30
seconds have elapsed since the last replacement drive was inserted into a slot.
3. On the Replace Drives page, click Done.

4. On the Replace Drives page, click Verify.

The S10 Node checks that the drives have been replaced in all the selected slots. It also
checks that no drives have been inserted into slots that were not selected for the
procedure and that no drives have been removed from selected slots without being
replaced.
Note: If you click Cancel instead of or after clicking Verify, the drive replacement
procedure ends, and the S10 Node treats all the replaced drives as failed drives. To
recover from this, use the drive removal procedure to remove the failed drives. Then use
the drive addition procedure to insert drives into the slots from which you removed the
failed drives.
For each selected slot, for each unselected slot into which a drive was inserted, and for
each unselected slot in which the drive was removed or replaced, the Management
Console displays a success, warning, or error message, as applicable. These messages
appear below the Verify button.
If error messages identify any slots as containing a drive with a duplicate SAS address
or a drive that doesn't have a valid SAS address, the drives in those slots are not added
to theS10 Node. To recover from this situation, follow the instructions in "SAS address
errors" on page 121.
If any drives inserted into any of the selected slots were previously used in an S Series
Node, an Actions section appears below the messages. This section lists each such
slot with the actions you can choose to take for that slot:
¡ If the drive is a native drive (that is, it was previously used in the current S10 Node,
and the HCP S Series software has not been reinstalled since the drive was
removed), the possible actions are:
– Reuse — Use the drive as is. This action is useful, for example, if the drive was
previously unintentionally removed from the enclosure. In this case, choosing
Reuse may facilitate repairs.
lost.
¡ If the drive is a foreign drive (that is, it was previously used in a different S Series
Node or in the current S10 Node before the HCP S Series software was reinstalled),
the possible actions are:
lost.
– Discard — Treat the drive as a failed drive. The drive can then be removed in a
new maintenance procedure and possibly reused in the S Series Node from
which it was originally removed.
The S10 Node continues to treat drives that were not replaced in selected slots as failed
or unavailable, as applicable. It also treats these as failed drives:
¡ These types of drives inserted into selected slots:
– Previously used drives on which the S10 Node had detected errors
– Drives that are bad to start with
– Drives of an unsupported type

If any drives were removed from selected or unselected slots and not replaced, those
slots are treated as having unavailable drives.
5. If the Actions section is present:
a. For each listed slot, select the action you want to take on the drive in that slot. To
select all the actions under the Format or Other heading, select the applicable
heading.
b. Click Confirm.
c. In the window with the confirming message, click Confirm.
The S10 Node takes the applicable action for each drive.
6. On the Replace Drives page, click End Procedure.
When you replace database drives, the S10 Node immediately begins synchronizing the new
Note: Processing drives for reuse can take some time. After a replace drives procedure is
complete, the S10 Node may continue to report drive additions or drive addition failures until
all the drives selected for reuse have been processed. This behavior is expected. While the
drives are being processed, you can continue to perform maintenance procedures, including
removing and adding back drives that failed to be added.

Chapter 8: Maintaining the enclosure
If the enclosure for an HCP S10 Node is damaged or not functioning properly, you can
replace it without having to replace the power and cooling modules and server modules in it.
If a power and cooling module is damaged or not functioning properly, you can replace just
that module. If the front panel and light pipe assembly on the enclosure are damaged or not
functioning properly, you can replace just those items. You can also replace damaged
enclosure rails and cable management arms without replacing the enclosure.
When you replace the enclosure or the enclosure rails, you need to remove the enclosure
from the rack. This requires shutting down the S10 Node.
During the replacement of a power and cooling module, the front panel and light pipe
assembly, or a single cable management arm, the enclosure remains in the rack, and the S10
Node remains fully functional. During the replacement of both cable management arms,
because the network cables need to be disconnected from both server modules, the S10
Node must be shut down.
example, replacing a server module while replacing the enclosure). Doing so can have
unpredictable results.
This chapter contains instructions for:
• Replacing a power and cooling module
• Replacing the front panel and light pipe assembly
• Replacing a cable management arm
• Replacing enclosure rails
• Replacing the enclosure
Replacing a power and cooling module

If a power and cooling module in an S10 Node enclosure fails, you need to replace that
module.
For proper cooling in an S10 Node enclosure, both power and cooling modules must be
present. When you remove one power and cooling module, the fans in the remaining module
operate at high speed, and an alarm sounds intermittently. After five minutes, if the module
isn't replaced, the alarm becomes continuous. To prevent overheating, when replacing a
power and cooling module, do not remove the old module from the enclosure until you're
ready to insert the new module.

Replacing a power and cooling module
What you need for replacing a power and cooling module

For replacing a power and cooling module in an enclosure, you need:
• The new power and cooling module

Power and cooling module part number: NDS4600-PS.X
• A #1 Phillips screwdriver
Step 1: Remove the old power and cooling module from the enclosure
To remove the old power and cooling module from the enclosure:
1. Use the rocker switch on the power and cooling module to power the module off.
2. While pushing back the small tab on the bottom of the clasp on the power cable lock, pull
the clasp away from the enclosure.
3. Press down on the tab on the side of the clasp to open the clasp.
4. Unplug the power cable from the power and cooling module, and move the cable out of
the clasp.
5. Using the #1 Phillips screwdriver, unscrew the large black screw in the top center of the
power and cooling module until the screw is very loose. The screw does not come out.
6. Pull down the handle that runs across the top of the power and cooling module. The
handle stops midway down the module.
7. Use the handle to pull the power and cooling module all the way out of the enclosure.
Step 2: Insert the new power and cooling module into the enclosure
To insert the new power and cooling module into the enclosure:
1. Ensure that the handle on the new power and cooling module is lowered as far as the
handle goes.
2. Slide the power and cooling module all the way back into the power and cooling module
slot in the enclosure. When the module reaches the back of the enclosure, the handle
pops up slightly.
3. Raise the handle all the way to the top of the power and cooling module.
4. Using the #1 Phillips screwdriver, screw in the large black screw in the top center of the
power and cooling module. Do not overtighten the screw.
5. Plug the power cable into the power and cooling module.

Replacing the front panel and light pipe assembly
6. Fit the power cable into the clasp on the power cable lock.
7. Push down on the top of the clasp to close it.
8. Push the clasp back toward the enclosure as far as the clasp goes to lock the power
cable plug in place.
9. Use the rocker switch on the power and cooling module to power the module on.

If the front panel or light pipe assembly on an S10 Node enclosure is damaged, you can
replace it.
What you need for replacing the front panel and light pipe assembly
For replacing the front panel and light pipe assembly on an enclosure, you need:
• The new front panel and light pipe assembly.

Front panel and light pipe assembly part number: ASM-01702-01-A.X
• A #1 Phillips screwdriver. You need this item only if the enclosure is secured to the rack
with small silver locking screws.
• A #2 Phillips screwdriver.
Step 1: Remove the old front panel and light pipe assembly from the
enclosure
To remove the old front panel and light pipe assembly on the enclosure:
those screws.

goes.
3. Using the #2 Phillips screwdriver, unscrew and remove the silver self-tapping screw in
each of the four corners on the back of the front of the enclosure.
4. Pull the front panel off the front of the enclosure.
5. Gently push the top of the light pipe assembly to the left and rock it to the left to free the
right side. Then push the light pipe assembly to the right side and pull the left side out of
the enclosure.
Step 2: Attach the new front panel and light pipe assembly to the
enclosure
To attach the new new front panel and light pipe assembly to the enclosure:
1. On the front of the enclosure, insert the left side of the top of the new light pipe assembly
into the bottom rectangular hole above the left column of LEDs . Then push the light pipe
assembly to the left side and insert the right side of the top of the assembly into the
bottom rectangular hole above the right column of LEDs.
2. Align the eight pipes in the light pipe assembly with the eight LEDs on the front of the
enclosure.

Replacing a cable management arm
3. Fit the new front panel onto the front of the enclosure so that:
¡ The pins in the four corners of the front of the enclosure fit into the holes in the four
corners of the back of the front panel
¡ The eight pipes in light pipe assembly fit into the eight round holes in the bottom
center of the front of the front panel
4. Using the #2 Phillips screwdriver, screw the four silver self-tapping screws that come
with the new front panel and light pipe assembly into the holes in the four corners in the
back of the front of the enclosure. Do not overtighten the screws.

If a cable management arm used in an S10 Node is damaged, you can replace it. Be sure to
use the correct replacement arm. The arm that attaches to the left outer rail (when viewed
from the front of the rack) has an L stamped on the back of the piece that attaches to the rail.
The arm that attaches to the right outer rail has an R stamped on the back of the piece that
attaches to the rail.
Tip: To keep the S10 Node available when you need to replace both cable management
arms, replace the arms one at a time.
What you need for replacing a cable management arm

For replacing a cable management arm, you need:
• A new cable management arm kit, which contains both the left and right cable
management arms.
Cable management arm part number: ASM-01659-01-A.X
• A #2 Phillips screwdriver. You need this item only if the enclosure is secured to the rack
using medium black screws.
• A paper clip.
• A Sharpie and masking tape.

Step 1: Prepare to replace the cable management arm

Before you can replace a cable management arm, you need to shut down both the server
module and the power and cooling module that are on the same side of the enclosure as the
arm you're replacing. If you're replacing both cable management arms, you need to shut
down both server modules and both power and cooling modules.
To prepare to replace the cable management arm:
3. Click Power Options.
4. In the Server Module field, select Server Module 1, Server Module 2, or Server
Modules 1 & 2, as applicable. Server module 1 is the module on the left, when viewed
from the rear of the rack. Server module 2 is the one on the right.
5. In the Reason field, type the reason why you're shutting down the server module. This
text can be up to 1,024 characters long and can contain any valid UTF-8 characters,
including white space.
6. Click Shut Down.
7. Use the rocker switch on each applicable power and cooling module to power the module
off.
Step 2: Disconnect the power and Ethernet cables and detach the old
cable management arm
To disconnect the power and Ethernet cables from the enclosure and detach the cable
management arm you want to replace:
1. Disconnect the power cable that's connected to the power and cooling module on the
side of the enclosure on which you're replacing the cable management arm. To do this:
a. While pushing back the small tab on the bottom of the clasp on the power cable lock,
pull the clasp away from the enclosure.
b. Press down on the tab on the side of the clasp to open the clasp.
c. Unplug the power cable from the power and cooling module, and move the cable out
of the clasp.

2. Disconnect the Ethernet cables from the two access ports and from the management
port on the server module on the side of the enclosure on which you're replacing the
cable management arm.
3. Using the #1 Phillips screwdriver, loosen the large black screw that attaches the cable
management arm to the middle of the enclosure until the screw is very loose. The screw
does not come out.
4. Pull the cable management arm away from the enclosure, allowing the small stud on the
left arm to slide out of the slot on the right arm.
those screws.

6. While pushing in the tabs on both sides of the front of the enclosure behind the front
panel, pull the enclosure forward a few inches out of the rack.
7. Using the #1 Phillips screwdriver, unscrew and remove the pin that attaches the cable
management arm to the outer enclosure rail or cable management arm extender, as
applicable, on the applicable side of the rack.
8. Pull the cable management arm away from the outer rail or cable management arm
extender, as applicable.
Step 3: Move the cables from the old cable management arm to the new
cable management arm
To move the cables from the old cable management arm to the new cable management arm:
1. Unwrap and remove the Velcro® strips that are wrapped around the cables in the old
cable management arm. Do not discard these strips. You will reuse them with the new
cable management arm.
2. For each Ethernet cable in the old cable management arm, move the cable out of the
arm, passing the cable out though the opening at the rack end of the arm.

3. Move the power cable out of the old cable management arm, passing the cable out
through the opening at the rack end of the arm.
4. Align the pin holes in the rail end of the new cable management arm with the pin holes at
the rear of the outer enclosure rail or cable management arm extender, as applicable.
5. Using the #1 Phillips screwdriver, screw in the pin that's used to attach the cable
management arm to the outer rail or to the cable management arm extender, as
applicable.
6. Pass the power cable through the opening at the rack end of the new cable management
arm, going from the outer side of the arm to the inner side of the arm.
7. Press the power cable into the inner side of cable management arm, starting from the
rack end of the arm.
8. For each Ethernet cable:
a. Pass the cable through the opening at the rack end of the cable management arm,
going from the outer side of the arm to the inner side of the arm.
b. Press the cable into the inner side of the cable management arm, starting from the
rack end of the arm.
9. Slide the enclosure all the way back into the rack until the enclosure clicks into place.
11. Wrap the Velcro strips from the old cable management arm around the cables in the new
cable management arm. To wrap a Velcro strip:
a. Pass the narrow end of the strip through the bottom slot on the outside of one link of
the cable management arm, letting the strip pass under the cables in the arm and out
the other side.

b. Wrap the strip around the arm once, passing the narrow end of the strip through the
slit in the wide end of the strip and pulling the strip tightly around the link.
c. Wrap the strip tightly around the arm again, passing it through the slot on the bottom
of the link.
d. Press the narrow end of the strip against the wrapped portion of the strip to hold the
strip in place.
Step 4: Attach the new cable management arm and reconnect the
Ethernet and power cables
To attach the new cable management arm and reconnect the Ethernet and power cables:
1. Position the cable management arm so that the small stud on the outside of the
enclosure end of the left arm fits into the corresponding slot in the outside of the
enclosure end of the right arm. Then align the large black screw at the end of the arm with
the applicable hole in the middle of the enclosure.

Replacing enclosure rails
2. Using the #1 Phillips screwdriver, screw in and tighten the screw. Do not overtighten the
screw.
3. Connect the management network cable to the management port on the applicable
server module.
When inserting the cable into the port, push the cable in until the end clicks into place.
4. Connect each access network cable to the applicable access port on the applicable
server module.
When inserting the cable into the port, ensure that the card in the nonmetal portion of the
connector at the end of the cable is facing the other access port on the same server
module.
9. Use the rocker switch on the applicable power and cooling module to power the module
on.
10. Insert the end of a paper clip into the hole for the recessed power button in the bottom
right corner of the applicable server module. Then gently press the paper clip against the
power button for two seconds.
If the server module does not become available again after you press the power button,
you can power the module back on by sliding it partially out of the enclosure and then
pushing it back in. For instructions on doing this, see "Replacing a server module".

If any parts of the enclosure rail kit used by an S10 Node are damaged, you can replace
them. The enclosure rail kit includes the rails that attach to the enclosure and rack and all the
accessory parts required to install the rails.

What you need for replacing enclosure rails

For replacing enclosure rails, you need:
• The new enclosure rail kit (for the contents of this kit, see "Enclosure rail kit" below).
Enclosure rail kit part number: ASM-01658-01-A.X
• A lift.
• A ¼-inch flat-head screwdriver. You need this screwdriver only if you're replacing a rail
that attaches to the rack.
Enclosure rail kit

The enclosure rail kit contains all the parts necessary for mounting an S10 Node enclosure in
a rack. The figure below identifies these parts.
The parts of the enclosure rail kit are:

A. Two outer rails. These are the rails that are installed in the rack. The rail with the letter L
stamped on its front lip attaches to the left side of the rack (when viewed from the front of
the rack). The rail with the letter R stamped on its front lip attaches to the right side of the
rack.

Each outer rail has a rail extender attached to it at the rear. The two-inch-wide rail
extenders are used to add length to the outer rails when necessary to accommodate the
depth of the rack.
Each outer rail also has a cable management arm extender attached to it at the rear. The
cable management arm extenders are used to add length to the parts of the outer rails
that the cable management arms attach to. The cable management arm extenders must
be used when the rail extenders are used.
The rail extenders and cable management arm extenders are required for mounting the
enclosure in a Hitachi Universal V2 rack.
B. Two inner rails. These are the rails that attach to the left and right sides of the enclosure.
The green plastic slider in each rail has an arrowhead at the front that points toward the
rear.
The right inner rail comes set into the right outer rail. The left inner rail comes set into the
left outer rail. The rails need to be separated before they can be installed.
C. Two chassis screws. These small silver screws are used to attach the inner rails to the
enclosure.
The package containing the chassis screws also contains four medium black screws.
These screws are used for securing the enclosure to the rack.
D. Four screw plates, with 16 medium silver screws. The screw plates are used to
strengthen the vertical mounting rails in the rack where the outer rails are attached.
E. Two shelf locking brackets, with four medium silver screws. The shelf locking brackets,
which attach to the front vertical mounting rails, have the screw holes for the top locking
screws on the enclosure.
Step 1: Power off the S10 Node

To power off the S10 Node:
4. In the Server Module field, select Server Modules 1 & 2.
5. In the Reason field, type the reason why you're shutting down the server modules. This
6. Click Shut Down.
7. Use the rocker switches on the power and cooling modules to power the modules off.

management arms
management arms:
1. Disconnect the two power cables from the power and cooling modules. To disconnect a
power cable:
of the clasp.
2. Disconnect the Ethernet cables from the two access ports and from the management
port on each server module.
3. Using a #1 Phillips screwdriver, loosen the two large black screws that attach the cable
management arms to the middle of the enclosure until the screws are very loose. The
screws do not come out.
4. Pull the cable management arms away from the enclosure.


those screws.
goes.

7. Detach the cable management arms from the outer enclosure rails or cable management
arm extenders on both sides of the rack. To detach a cable management arm:
a. Using the #1 Phillips screwdriver, unscrew and remove the pin that attaches the
cable management arm to the outer rail or to the cable management arm extender,
as applicable.
b. Pull the cable management arm away from the outer rail or cable management arm
extender, as applicable.
Step 3: Remove the enclosure from the rack

To remove the enclosure from the rack:
1. Position the lift so that the lift platform is below the enclosure.
2. Raise the platform to just below the enclosure, aligning the platform so that the bulk of
the enclosure will rest on it when the enclosure is pulled out of the rack.
3. While pressing in the green tabs on the rails on both sides of the enclosure, pull the
enclosure to release it from the rack. Then pull the enclosure completely out of the rack.
4. Optionally, use the lift to move the enclosure to a work surface. If you don't need the lift
for any other purpose, you can leave the enclosure on the lift platform.
5. Slide the extended part of each outer enclosure rail back into the rack:
¡ For the left outer rail, press down on the latch on the inner rear of the extended part to
release the part. Then push the extended part back into the rack as far as the part
goes.
¡ For the right outer rail, press up on the latch on the inner rear of the extended part to
goes.

Step 4: Separate the inner and outer rails in the new enclosure rail kit
In a new enclosure rail kit, the left and right inner rails are set inside the left and right outer
rails, respectively. ou need to separate the inner and outer rails from each other so that you
can attach the inner rails to the enclosure and the outer rails to the rack.
For more information about the enclosure rail kit, see "Enclosure rail kit" on page 143.
To separate an inner rail from its outer rail:
1. Slide the inner rail out of the front end of the outer rail as far as the inner rail goes.
2. While pressing the green tab on extended part of the outer rail, pull the inner rail to
release it from the outer rail. Then slide the inner rail all the way out of the outer rail.
Step 5: Determine which rails to replace

Depending on which rails are damaged and on whether the new enclosure rail kit is the same
model as the old enclosure rail kit, you may need to replace one or both of the inner and outer
rails on one or both sides of the enclosure and rack.
If the new enclosure rail kit is the same model as the old enclosure rail kit and:
• If only an outer rail is damaged, you need to replace both the inner and outer rails on the
applicable side of the enclosure and rack. (Alternatively, you can remove the old inner rail
from the enclosure and check whether it slides smoothly into the new outer rail. If it does,
you can replace only the outer rail.)
• If only an inner rail is damaged, check whether the new inner rail slides smoothly in the
existing outer rail on the applicable side of the rack. If it slides in smoothly, you need to
replace only the inner rail. If it doesn't, you need to replace both the inner and outer rails.
To check whether the new inner rail slides smoothly in the old outer rail:
1. With the rear of the inner rail aligned with the front of the outer rail, slide the inner rail
back into the outer until it comes to a stop.
2. While pressing the green tab on the inner rail, push the inner rail back to release it.
Then slide the inner rail all the way back into the rack.
3. Slide the inner rail out of the front end of the outer rail as far as the inner rail goes.
4. While pressing the green tab on the inner rail, pull the inner rail to release it from the
outer rail. Then slide the inner rail all the way out of the rack.
• If both the inner rail and outer rail are damaged on a given side, you need to replace both
the inner rail and rails on that side.

If the new enclosure rail kit is a different model from the old enclosure rail kit, you need to
replace both the inner and outer rails on both sides of the enclosure and rack.
Step 6 (conditional): Replace the inner rails on the enclosure

Depending on the condition of the rails, you may need to replace neither, one, or both of the
rails on the enclosure (that is, the inner rails).
To replace an inner rail on the enclosure:
1. Using the #1 Phillips screwdriver, unscrew and remove the silver chassis screw that
attaches the old rail to the enclosure.
2. While lifting the silver tab on the old rail, slide the rail toward the front of the enclosure as
far as the rail goes. Then pull the rail off the enclosure.
3. Position the new inner rail on the applicable side of the enclosure so that the green
plastic slider in the rail faces out and the studs on the enclosure fit into the holes in the
rail. Then slide the rail toward the back of the enclosure as far as the rail goes.
4. Using the #1 Phillips screwdriver, screw in and tighten one of the new silver chassis
screws that come in the enclosure rail kit.
Step 7 (conditional): Replace the outer rails in the rack

Depending on the condition of the rails, you may need to replace neither, one, or both of the
enclosure rails in the rack (that is, the outer rails). Replacing an outer rail in the rack requires
two people — one at the front of the rack and one at the rear.
To replace an outer enclosure rail in the rack:
1. Remove the old outer rail from the front and rear of the rack. To do this:
¡ At the front of the rack, using the #2 Phillips screwdriver, unscrew and remove the
six screws that attach the front of the rail to the rack.
While unscrewing the top two screws, hold onto the screw plate and shelf locking
bracket so they don't fall. While unscrewing the last screw, support the rail with your
other hand so the rail doesn't fall.
¡ At the rear of the rack, using the #2 Phillips screwdriver, unscrew and remove the
four screws that attach the back of the rail to the rack.
While unscrewing the screws, hold onto the screw plate so it doesn't fall. While
unscrewing the last screw, support the rail with your other hand so the rail doesn't
fall.
2. Based on the depth of the rack, set the new rail to the required length by adjusting the
sliding panel on the rail and, if necessary, removing the rail extender.

Tip: If you have access to the sides of the rack, you can adjust the sliding panel when
you install the rail in the rack instead of adjusting it ahead of time. However, you still
need to remove the rail extender if necessary and loosen the six silver screws that hold
the sliding panel in place before you install the rail.
The sliding panel has a small circular window that shows the length of the rail from the
front of the rail to the rear of the sliding panel, in inches. The panel has a small oblong
window that shows lines indicating ⅛-inch intervals.
For a Hitachi Universal V2 rack, set the total length of the rail plus the two-inch rail
extender to just under 29 inches. At this length, some portion of the number 27 shows in
the small circular window. (A Hitachi Universal V2 rack requires the use of the rail
extenders.)
To adjust the sliding panel:

a. Using the ¼-inch flat-head screwdriver, loosen the six silver screws that hold the
sliding panel in place. Do not remove the screws.
b. Adjust the position of the sliding panel to extend the rail to the length you want.
c. Using the ¼-inch flat-head screwdriver, tighten the six silver screws.

The rail extender is attached to the rear of the sliding panel. To remove the rail extender,
using the #2 Phillips screwdriver, unscrew and remove the four medium silver screws
that attach the extender to the rail.
Tip: To ensure a proper fit, measure the rail against the rack before attaching it to the
rack. You may need to adjust the length of the rail more than once to get it right.
3. If you removed the rail extender from the rail, remove the cable management arm
extender from the rail. To do this, using the #1 Phillips screwdriver, unscrew and remove
the pin that attaches the extender to the rail.
4. Attach the new rail to the front and rear of the rack. To do this:
¡ At the front of the rack:
1. On the front of the vertical mounting rail, position one of the screw plates so that
the bottom of the plate is aligned with the bottom of the bottom rack unit for the
enclosure.

2. On the back of the vertical mounting rail, position the outer enclosure rail such
that the bottom of the lip at the front of the outer rail is aligned with the bottom of
the screw plate and the PEM fastener on the lip sits in the sixth hole down from
the top of the screw plate.
3. Using the #2 Phillips screwdriver, screw four of the medium silver screws that
come with the screw plates into the screw plate. Start with the hole that's fourth
from the top of the screw plate, then do the bottom hole in the screw plate, and
finally do the holes that are sixth and seventh from the top of the screw plate.
Tighten the screws.
¡ At the rear of the rack:
1. On the front of the vertical mounting rail, position one of the screw plates such
that the bottom of the plate is aligned with the bottom of the bottom rack unit for
the enclosure.
2. On the back of the vertical mounting rail, position the outer enclosure rail such
that the bottom of the lip at the rear of the outer rail is aligned with the bottom of
the screw plate.
3. Using the #2 Phillips screwdriver, screw four of the medium silver screws that
come with the screw plates into the screw plate. Start with the hole that's fourth
from the top of the screw plate, then do the bottom hole in the screw plate, and
finally do the holes that are sixth and seventh from the top of the screw plate.
Tighten the screws.
5. Attach one shelf locking bracket to the each of the vertical mounting rails at the front of
the rack. To attach a shelf locking bracket:
a. On the back of the vertical mounting rail, position the shelf locking bracket so that:
– The top of the bracket is a little above the top of the screw plate
– The PEM® fastener on the bracket sits in the second hole down from the top of
the screw plate
– The two holes in the bracket are aligned with the top hole in the screw plate and
third hole down from the top of the screw plate

b. Using the #2 Phillips screwdriver, screw two of the medium silver screws that come
with the shelf locking brackets into the top hole of the screw plate and the third hole
down from the top of the screw plate. Tighten the screws.
Step 8: Move the enclosure back into the rack

To move the enclosure back into the rack:
1. Ensure that the extendable part of the outer enclosure rail is pushed back into the rack a
far as it goes.
2. If you removed the enclosure from the lift platform, move the enclosure back onto the
platform.
3. Position the lift so that the rear of the enclosure faces the front of the rack in which you're
installing the enclosure.
4. Ensure that the sliding part of each outer rail for the enclosure is pushed all the way back
into the rack.
5. Raise the lift platform to the point where:
¡ The inner rails on the enclosure are aligned with the outer rails in the rack
¡ The bottom of the guide blocks on the sides of the enclosure are aligned with the
tops of the outer rails in the rack
6. With the guide blocks on the enclosure resting on the tops of the outer rails in the rack,
slide the enclosure back into the rack until the enclosure comes to a stop.
7. Move the lift away from the rack.

Step 9: Reattach the cable management arms and reconnect the Ethernet
and power cables
To reattach the cable management arms and reconnect the Ethernet and power cables:
1. While pushing in the tabs on both sides of the front of the enclosure behind the front
panel, pull the enclosure forward a few inches out of the rack.
2. Using the #1 Phillips screwdriver, unscrew and remove the pin that's used to attach the
left cable management arm (when viewed from the rear of the rack) to the rear of the left
outer enclosure rail or cable management arm extender, as applicable.
3. Align the pin holes in the rail end of the left cable management arm with the pin holes in
the left outer rail or cable management arm extender, as applicable.
4. Using the #1 Phillips screwdriver, screw in the pin that attaches the left cable
management arm to the left outer rail or cable management arm extender, as applicable.
5. Repeat steps 2 through 4 with the right cable management arm.
6. Slide the enclosure all the way back into the rack until the enclosure clicks into place.
8. Align the large black screw at the enclosure end of the left cable management arm with
the lefthand hole in the middle of the enclosure.
screw.
10. Position the right cable management arm so that the small stud on the outside of the left
arm fits into the corresponding slot on the outside of the right arm. Then align the large
black screw at the end of the right cable management arm with the righthand hole in the
middle of the enclosure.
screw.
12. Connect each management network cable to the management port on the applicable
server module.
When inserting the cables into the ports, push the cables in until they click into place.
13. Connect each access network cable to the applicable access port on the applicable
server module.
module.
14. Plug the power cable back into the applicable power and cooling module.

Replacing the enclosure

If the enclosure for an S10 Node is damaged or not functioning properly, you can replace it.
You need to both start and end the replacement procedure from the HCP S Series
Management Console or by using the HCP S Series management API.
If you don't start and end the enclosure replacement procedure from the Management
Console or by using the management API, when you power the S10 Node back on, the S10
Node treats all data and database drives, as failed. If this happens, contact your HCP
support center for help.
A Management Console session can time out while you’re performing a hardware
maintenance procedure. If this happens, you can log back into the Console to continue the
procedure.
After you start an enclosure replacement procedure, you can cancel it between steps if
you're using the Management Console to perform the procedure or at any time if you're using
the management API. After you select the enclosure for the procedure, if you don't end the
procedure within four hours, the S10 Node automatically cancels it.
Note: If an enclosure replacement procedure is canceled after the enclosure is physically

replaced, the procedure ends unsuccessfully. To recover from this situation, you need to
contact your HCP support center.
When replacing the enclosure for an S10 Node, you need to replace the righthand cover of
the new enclosure with the righthand cover of the old enclosure. This is because the serial
number for the S10 Node is on a label attached to that cover.
After replacing the enclosure, you need to check the firmware versions on the SAS
expanders in the new enclosure. If any expanders have the wrong firmware version, you
need to perform a firmware update.
What you need for replacing the enclosure

For replacing an S10 Node enclosure, you need:
• The new enclosure (part number NDS4600-SHF-01.X)
• If the old enclosure is secured to the rack using four small silver locking screws, either of
these:
¡ If the carton containing the new enclosure also contains a package of four medium
black screws, those screws
¡ If the carton containing the new enclosure does not also contain four medium black
screws, four 8-32 x ½" machine screws
• A lift

• A ¼-inch nut driver or ¼-inch socket and socket wrench
Step 1: Start the enclosure replacement procedure

To start the procedure for replacing an S10 Node enclosure:
role.
5. In the Maintenance Procedure field, select Replace Enclosure. Then click Go.
6. In the Select Enclosures list, select the enclosure.

7. Click Continue.
The S10 Node server modules shut down, and the blue identity LED on the front of the
enclosure starts blinking.
Step 2: Unpack the new enclosure

To unpack the new enclosure:
1. Position the lift so that the lift platform is aligned with the bottom of the carton containing
the enclosure.
2. Remove the four clips on each of the two opposite ends of the carton. To remove a clip,
while squeezing the tabs on the clip, pull the clip out of the carton.
3. Lift the top off the carton.
4. Remove any accessible boxes containing additional S10 Node components from inside
the carton.
5. Lift the sides off the bottom of the carton.
6. Remove any foam packing pieces from the top of the enclosure.
7. With another person, use the straps around the enclosure to move the enclosure from the
bottom of the carton to the lift platform.
Caution: Do not try to move the enclosure by yourself. Doing so can result in personal
injury. Always use at least two people to move an enclosure.

8. If any of the foam packing pieces remain on the enclosure, remove them.
9. Use the lift to move the enclosure to a work surface that has room for both the old and
new enclosures.
10. Remove the two straps from the enclosure.
management arms
management arms:
1. Use the rocker switches on the power and cooling modules to power both modules off.
2. Disconnect the two power cables from the power and cooling modules. To disconnect a
power cable:
of the clasp.
3. Disconnect the Ethernet cables from the two access ports, the management port, and
the server interconnect port on each server module.

4. Using a #1 Phillips screwdriver, loosen the two large black screws that attach the cable
management arms to the middle of the enclosure until the screws are very loose. The
screws do not come out.
5. Pull the cable management arms away from the enclosure.
Step 4: Remove the old enclosure from the rack

To remove the old enclosure from the rack:
those screws.

goes.
3. Remove the front panel and light pipe assembly from the enclosure. To do this:
a. Using the #2 Phillips screwdriver, unscrew and remove the silver self-tapping screw
in each of the four corners on the back of the front of the enclosure.
b. Pull the front panel off the front of the enclosure.
c. Gently push the top of the light pipe assembly to the left and rock it to the left to free
the right side. Then push the light pipe assembly to the right side and pull the left side
out of the enclosure.
Set the front panel and light pipe assembly aside. You will need them for the new
enclosure.
4. Position the lift so that the lift platform is below the enclosure.
5. Raise the platform to just below the enclosure, aligning the platform so that the bulk of
the enclosure will rest on it when the enclosure is pulled out of the rack.
6. While pressing in the green tabs on the rails on both sides of the enclosure, pull the
enclosure to release it from the rack. Then pull the enclosure completely out of the rack.
7. Using the lift, move the enclosure to the work surface on which you put the new
enclosure.
8. Slide the extended part of each outer enclosure rail back into the rack:
¡ For the left outer rail, press down on the latch on the inner rear of the extended part to
goes.

¡ For the right outer rail, press up on the latch on the inner rear of the extended part to
goes.
Step 5: Move the inner rails from the old enclosure to the new enclosure
Each inner enclosure rail must be on the same side on the new enclosure as it was on the old
enclosure. To ensure that the rails are on the correct sides on the new enclosure, move the
rails one at a time.
To move an inner rail from the old enclosure to the new enclosure:
1. Using the #1 Phillips screwdriver, unscrew and remove the silver chassis screw that
attaches the rail to the enclosure.
2. While lifting the silver tab on the rail, slide the rail toward the front of the enclosure as far
as the rail goes. Then remove the rail from the enclosure.
3. Position the rail on the applicable side of the new enclosure so that the green plastic
slider in the rail faces out and the studs on the enclosure fit into the holes in the rail. Then
slide the rail toward the back of the enclosure until it clicks into place.
4. Using the #1 Phillips screwdriver, screw in and tighten the small silver chassis screw.
Step 6: Move the power and cooling modules from the old enclosure to
the new enclosure
The power and cooling modules do not need to be in the same positions in the new enclosure
as they were in the old enclosure.
To move a power and cooling module from the old enclosure to the new enclosure, with the
rear of each enclosure facing you:
power and cooling module until the screw is very loose. The screw does not come out.
2. Pull down the handle that runs across the top of the power and cooling module. The
handle stops midway down the module.

3. Use the handle to pull the power and cooling module all the way out of the enclosure.
4. Ensure that the handle on the power and cooling module is lowered as far as the handle
goes.
5. Slide the power and cooling module all the way back into one of the power and cooling
module slots in the new enclosure. When the module reaches the back of the enclosure,
the handle pops up slightly.
6. Raise the handle all the way to the top of the power and cooling module.
power and cooling module. Do not overtighten the screw.
Step 7: Move the server modules from the old enclosure to the new
enclosure
Each server module must be in the same position in the new enclosure as it was in the old
enclosure. To ensure that the modules are in the correct positions in the new enclosure,
move the modules one at a time.
Important: If the server modules are not in the same positions in the new enclosure as they
were in in the old enclosure and you later need to recover the S10 Node, the recovery
operation will cause the S10 Node not to function properly.
To move a server module from the old enclosure to the new enclosure, with the rear of each
enclosure facing you:
server module until the screw is very loose. The screw does not come out.
2. Pull down the handle that runs across the top of the server module. The handle stops
midway down the module.
3. Use the handle to pull the server module all the way out of the enclosure.
4. Ensure that the handle on the server module is lowered as far as the handle goes.
5. Slide the server module all the way back into the applicable server module slot in the new
enclosure. When the module reaches the back of the enclosure, the handle pops up
slightly.
6. Raise the handle all the way to the top of the server module.
server module. Do not overtighten the screw.

Step 8: Move the data and database drives from the old enclosure to the
new enclosure
Each database drive must be in the same slot in the new enclosure as it was in the old
enclosure. These are the drives in slots 29, 30, 31, and 32 (the two immediately to the left of
the center divider and the two immediately to the right of the center divider, all in the middle
row).
To ensure that the database drives are in the correct slots in the new enclosure, move them
one at a time.
Important: If the database drives are not in the same slots in the new enclosure as they
were in in the old enclosure, the HCP S Series software may not run when you power the
S10 Node back on. If this happens, you need to recover the S10 Node. For more information
about S10 Node recovery, contact your HCP support center.
The data drives also should be in the same positions in the new enclosure as they were in in
the old enclosure.
To move the additional data drives from the old enclosure to the new enclosure:
1. Open the covers on the old and new enclosures. To open an enclosure cover:
a. Lift both latches on the top of the enclosure and pull up to open the right side of the
enclosure cover (when viewed from the front of the enclosure).
b. Push down on the two release latches for the left side of the enclosure cover. Then
pull up that side to open it.
2. Move each data or database drive from the old enclosure to the new enclosure. To move
a data or database drive:
a. Push back on the tab on the top of the drive.
b. Pull up the latch until it clicks into place.
c. Pull up on the latch to slide the drive out of the slot.
d. Slide the drive all the way down into the applicable slot in the new enclosure.
e. Close the latch, pushing down until it clicks into place.
Step 9: Swap the right sides of the enclosure covers between the two
enclosures
The serial number label for an S10 Node is on the top right side of the enclosure cover. The
right side of the enclosure cover is the side on the right when the front of the enclosure is
facing you.
To retain the serial number label for the S10 Node, you need to swap the right sides of the
enclosure covers between the old and new enclosures.

To swap the right sides of the enclosure covers between the old enclosure and the new
enclosure:
1. On each enclosure, if the right side of the enclosure cover is not open, lift both latches on
the top of the enclosure and pull up to open the cover.
2. Remove the right side of the enclosure cover from each of the enclosures. To remove the
right side of a cover:
a. Use the ¼-inch nut driver or ¼-inch socket and socket wrench to unscrew and
remove the two small black screws in each of the three hinges on the right side of
the cover (when viewed from the front of the enclosure).
b. Lift the right side of the cover off the enclosure.
3. Swap the removed covers between the old and new enclosures.
4. Attach the swapped covers to the enclosures. To attach the right side of a cover:
a. Place the cover on the enclosure, aligning the holes in the cover hinges with the
holes on the right side of the enclosure.
b. Use the ¼-inch nut driver or ¼-inch socket and socket wrench to screw the small
black screws into the six hinge holes. Tighten the screws.
5. Close the covers on the old and new enclosures. To close an enclosure cover:
a. Close the left side of the enclosure cover.
b. Close the right side of the enclosure cover, pushing down until the cover clicks into
place.
Step 10: Move the new enclosure into the rack

To move the new enclosure into the rack:
1. Move the new enclosure onto the lift platform.
2. Position the lift so that the rear of the enclosure faces the front of the rack in which you're
installing the enclosure.
3. Ensure that the sliding part of each outer rail for the enclosure is pushed all the way back
into the rack.
4. Raise the lift platform to the point where:
¡ The inner rails on the enclosure are aligned with the outer rails in the rack
¡ The bottom of the guide blocks on the sides of the enclosure are aligned with the
tops of the outer rails in the rack
5. With the guide blocks on the enclosure resting on the tops of the outer rails in the rack,
slide the enclosure back into the rack until the enclosure comes to a stop.
6. Move the lift away from the rack.
goes.
8. On the front of the enclosure, insert the left side of the top of the light pipe assembly into
the bottom rectangular hole above the left column of LEDs. Then push the light pipe

assembly to the left and insert the right side of the top of the assembly into the bottom
rectangular hole above the right column of LEDs.
9. Align the eight pipes in the light pipe assembly with the eight LEDs on the front of the
enclosure.
10. Fit the front panel onto the front of the enclosure so that:
¡ The pins in the four corners of the front of the enclosure fit into the holes in the four
corners of the back of the front panel
¡ The eight pipes in light pipe assembly fit into the eight round holes in the bottom
center of the front of the front panel
11. Using the #2 Phillips screwdriver, screw the four silver self-tapping screws into the holes
in the four corners in the back of the front of the enclosure. Do not overtighten the
screws.
13. Take one of these actions:
¡ If the old enclosure was secured to the rack with four medium black screws, using
the #2 Phillips screwdriver, screw those screws into the four screw holes on the
front of the new enclosure.
¡ If the old enclosure was secured to the rack with four small silver locking screws
and the new enclosure comes with four medium black screws, using the #2 Phillips
screwdriver, screw the medium black screws into the four screw holes on the front
of the new enclosure.
¡ If the old enclosure was secured to the rack with four small silver locking screws
and the new enclosure does not come with medium black screws, screw four 8-32 x
½" machine screws into the screw holes on the front of the new enclosure.

Step 11: Reattach the cable management arms and reconnect the
Ethernet and power cables
To reattach the cable management arms and reconnect the Ethernet and power cables:
1. Align the large black screw at the end of the left cable management arm (when viewed
from the rear of the rack) with the lefthand hole in the middle of the enclosure.
screw.
3. Position the right cable management arm so that the small stud on the outside of the left
arm fits into the corresponding slot on the outside of the right arm. Then align the large
black screw at the end of the right cable management arm with the righthand hole in the
middle of the enclosure.
screw.
5. Connect the purple server interconnect cable to the server interconnect port on each
server module.
6. Connect each management network cable to the management port on the applicable
server module.
When inserting the cables into the ports, push the cables in until they click into place.
7. Connect each access network cable to the applicable access port in the applicable
server module.
module.

Step 12: Verify the enclosure replacement

After you've replaced the old enclosure with the new enclosure, you need to verify that the
enclosure replacement occurred correctly. Then you need to end the enclosure replacement
procedure.
To verify the enclosure replacement and end the procedure:
2. Wait for the S10 Node to finish its startup processing. This can take as long as ten
minutes.
role.
4. Go to Hardware ► Maintenance.
5. In the Maintenance Procedure in Progress section, click the gear icon ( ) for the
replace enclosure procedure.

6. On the Replace Enclosure page, click Done.

7. On the Replace Enclosure page, click Verify.
The S10 Node checks that the new enclosure:
¡ Is not the same enclosure as the one that was in use when you started the
replacement procedure
¡ Is of a supported type
¡ Is properly cabled
¡ Was recognized without any issues
If all of the above apply, the enclosure replacement procedure was successful. If any of
the above do not apply, the enclosure replacement procedure failed, and the new
enclosure is marked failed.
The S10 Node also checks that, for each drive in the new enclosure, the drive:
¡ Is in a different enclosure from the one it was in when you started the replacement
procedure
¡ Is of a supported type
¡ Has no previously detected errors
¡ Was recognized without any issues
If any of the above do not apply, the drive is marked failed. Failed drives do not cause the
enclosure replacement procedure to fail.

The Management Console displays success, warning, and error messages, as

applicable, below the Verify button.
Note: If you replace the enclosure and then click Cancel instead of or after clicking
Verify, the enclosure replacement procedure ends unsuccessfully, and the new
enclosure is marked failed.
8. On the Replace Enclosure page, click End Procedure.

After ending the procedure, to recover from a situation in which the new enclosure is
marked failed, you need to contact your HCP support center for help.
When you replace database drives, the S10 Node immediately begins synchronizing the new
Step 13: Verify the enclosure VPDs

You use the VPD tool to verify the enclosure VPDs. This tool checks the VPDs and tries to
fix any errors it finds. If the tool finds but cannot fix one or more errors, you need to contact
your HCP support center for help.
Options.
d. Click Shut Down.
5. Change to the /opt/rhino/sil/bin/VPDTool directory.
./FixVPD -a

The VPD tool then reports the outcome of its processing. Three outcomes are possible:
To continue:
Power Options.
module.
d. Click Restart.
4. Proceed to Step 14: "Check and, if necessary, update the SAS expander
firmware on the new enclosure" on the next page.
this:
To continue, follow the procedure above for when the VPD tool doesn't find any
errors.
this:
To continue:
from the /opt/rhino/sil/bin/VPDTool directory to the location of your
choice on your laptop computer. HCP support personnel will need these files to
resolve the VPD errors.


Power Options.
module.
d. Click Power On.
Important: Do not perform the SAS expander firmware step after the VPD tool
discovers errors the tool cannot fix.
Step 14: Check and, if necessary, update the SAS expander firmware on
the new enclosure
After replacing the enclosure, you need to check the firmware versions on the SAS
expanders in the new enclosure. If any of the SAS expanders have the wrong firmware
version, you need to perform a firmware update.
The procedure for checking and updating the SAS expander firmware also checks and, if
necessary, updates the firmware on all other components of the S10 Node.
You can perform a firmware update in either of these ways:
• One server module at a time. In this case, while a server module is running the update,
the module is unavailable. The whole process takes approximately ten minutes per
server module. However, during that time, the S10 Node remains available.
• Both server modules at the same time. In this case, the whole process takes
approximately ten minutes. However, during that time, the entire S10 Node is
unavailable.
Checking and updating firmware while the S10 Node remains available
With the procedure in this section, the firmware check and update run on one server module
at a time. The S10 Node remains available during the entire process.
To check and, if necessary, update S10 Node component firmware:
1. If you have not already done so, add the S Series Node service SSH key to your
2. Use PuTTY to establish an SSH connection to either server module, as described in
"Using a PuTTY SSH connection" on page 36.
3. At the login prompt, enter service.
4. Enter this command to check whether any components have firmware that needs to be
updated:
sudo firmware.py show --check

This command displays a list of all currently installed component firmware versions. The
firmware versions seen by the server module you're logged in to are shown on the left.
The firmware versions seen by the other server module are shown on the right.
The list of the currently installed component firmware versions is followed by a list of the
component firmware that needs to be updated (that is, a list of the components that failed
the firmware version check). A failure statement has this format:
component failed firmware version check- Found: current-version Expected: expected-version
If all the component firmware is up to date, this message is displayed:

All hardware components are set to the proper versions
5. If any firmware needs to be updated:

a. Enter this command to update the firmware seen by the server module you're logged
in to, as needed:
sudo firmware.py show --auto --local --tryLocalUpdate
This command shuts down HCP S Series software on the server module you're
logged in to. The firmware update then starts on that module. After the firmware
update is complete, the software restarts on that module.
b. Enter this command to verify that all the necessary updates have been made to the
firmware seen by the server module you're logged in to:
sudo firmware.py show --check --local
If the output from this command includes any failure statements, contact your HCP
If the output from this command does not include any failure statements:
1. Enter this command to determine when startup processing on the server module
is complete:
admin -t 1200 status waitUntilStarted
When startup processing is complete, the command prompt reappears.

If this command times out, contact your HCP support center for help.
2. Repeat this procedure for the other server module, starting from step 2.
Checking and updating firmware with S10 Node unavailability
With the procedure in this section:
• While the firmware check is in progress, the S10 Node remains available
• While the firmware update is in progress, the S10 Node is unavailable

To check and, if necessary, update S10 Node component firmware:

4. Enter this command to check whether any components have firmware that needs to be
updated:
This command displays a list of all currently installed component firmware versions. The
firmware versions seen by the server module you're logged in to are shown on the left.
The firmware versions seen by the other server module are shown on the right.
The list of the currently installed component firmware versions is followed by a list of the
component firmware that needs to be updated (that is, a list of the components that failed
the firmware version check). A failure statement has this format:
If all the component firmware is up to date, this message is displayed:

5. If any firmware needs to be updated:

a. Enter this command to update the firmware:
sudo firmware.py show --auto
This command shuts down HCP S Series software on both server modules. The
firmware update then starts on each module. After the firmware update is complete
on a module, the software restarts on that module.
b. Enter this command again to verify that all the necessary firmware updates have
been made:
If the output from this command includes any failure statements, contact your HCP
Step 15 (conditional): Check the health of the S10 Node

If any firmware has been updated, you need to check the health of the S10 Node.
To check the health of the S10 Node:
1. If you do not currently have an SSH connection to either server module:
a. Use PuTTY to establish an SSH connection to either server module, as described in
b. At the login prompt, enter service.
2. In the PuTTY window, enter:
/home/service/bin/install
3. When prompted, press Enter to continue.

The HCP S Series Node Service Menu appears.
4. Enter 1 to display the S10 Node status information.
5. In the status display, check that all components are running and healthy (that is, the
status is either Online, OK, or active).

An S10 Node can take up to ten minutes to become available after a firmware update. If
any components are not running and healthy and at least ten minutes have passed since
the firmware update finished, contact your HCP support center for help.
6. Enter b to return to the HCP S Series Node Service Menu.
7. Enter q to return to the command-line prompt.
8. Enter y to confirm that you want to leave the HCP S Series Node Service Menu.

Chapter 9: Maintaining server modules
When a server module in an HCP S10 Node is damaged or not functioning properly, the
module becomes unavailable. Similarly, when the server interconnect cable in an HCP S10
Node is damaged or not functioning properly, one of the server modules becomes
unavailable.
When a server module or the server interconnect cable is damaged or not functioning
properly, you can replace it. If the problem is with the internal drives (that is, the OS SSDs) in
a server module, you can replace them without replacing the entire server module.
example, replacing the enclosure while replacing a server module). Doing so can have
unpredictable results.
This chapter explains how to determine the cause of the problem when a server module is
unavailable. The chapter also contains instructions for:
• Replacing a server module
• Replacing one or both of the SSDs in a server module
• Replacing the server interconnect cable
Determining what to replace

The HCP S Series Management Console displays information about problems with server
modules on the Hardware Overview page and the pages for the individual server modules, in
alerts, and in messages in the event log. Based on this information, you can usually
determine where the problem exists and take appropriate action.
While a server module is running, it can report problems with its own components. For
example, a server module can report a problem with an Ethernet port or single OS SSD. You
can replace OS SSDs in a server module. For any other server-module component problem,
you need to replace the server module itself.
If both server modules are running but cannot communicate with each other, one of them can
report the issue. An inability to communicate may be due to a damaged or malfunctioning
server interconnect cable, in which case, you would replace the cable.
If a server module is not functioning at all, it cannot report the problem, and the other module
can report only that the nonfunctioning module is not available. In this case, the problem is
most likely that either both OS SSDs or the server module itself is not functioning properly.

Server module Ethernet ports

A server module in an S10 Node server module has these Ethernet ports:
• eth0 — Right access network port
• eth2 — Left access network port
• eth1 — Management network port
• eth3 — Server interconnect network port

The figure below shows the locations of these ports.
Degraded OS SSD
The OS SSDs in an S10 Node server module are identified as SSD0 and SSD1. SSD0 is
closer to the right side of the server module. SSD1 is closer to the left side. On the
motherboard, the card edge connector for SSD0 is labeled J11. The card edge connector for
SSD1 is labeled J10.

If a partition on an OS SSD is inaccessible, the HCP S Series Management Console

displays an alert like this:
Server module 2 operating system partition 5 is degraded (FRU part number:
ASM-01667-01-A.X).
This alert specifies which server module contains the problem SSD but not which SSD has
the problem. As a result, you cannot tell from the alert whether you need to replace SSD0 or
SSD1.
To determine which SSD you need to replace:
2. Use PuTTY to establish an SSH connection to the server module specified in the alert,
as described in "Using a PuTTY SSH connection" on page 36.
4. At the command-line prompt, enter this command:
cat /proc/mdstat
The response to this command is a list of pairs of partitions on the OS SSDs and
database drives.

Each pair of partitions is identified by the letters md followed by a partition number (for
example, md5). The pairs of partitions on the SSDs are numbered 1, 2, 5, 6, 7, 8, and 9.
The pair of partitions on the database drives is numbered 11 or 12.
Each partition in a given pair of SSD partitions is the partition with the applicable number
on one of the SSDs. Partitions are identified by the sd device name of the SSD they're
on, followed by the applicable partition number. An sd device name has the form sdletter
(for example, sda). So, for example, partition 5 on the SSD named sda is sda5.
If both partitions in a pair of partitions are accessible, the entry for that pair ends with a
string consisting of one occurrence of the letter U for each partition in the pair, enclosed
in square brackets (like this: [UU]).
If one or both partitions in a pair of partitions are inaccessible, the string in square
brackets at the end of the entry for that pair is missing one occurrence of the letter U for
each inaccessible partition.
Also, if a partition is inaccessible, either of these is true:
¡ The partition name is followed by the letter F in parentheses, as shown below for
partition 2 on an SSD with device name sdb.
¡ The partition name is missing, as shown below, where partition 6 on an SSD with
device name sdb is missing.
The SSD to replace is the one with one or more inaccessible partitions.
5. To see which OS SSD an sd device name identifies, enter this command:
lsscsi | grep -e StorFly -e VikingDisk -e VPFEM
The response to this command consists of one line for each accessible SSD.
The sd device name for each listed SSD is in the rightmost column. The value in the first
column indicates which SSD the sd device name identifies:
¡ 0:0:0:0 is SSD0.
¡ 1:0:0:0 is SSD1.
Nonfunctioning server module

To determine the cause of the problem when a server module is not functioning at all:
1. Use PuTTY to establish a serial connection to the nonfunctioning server module, as
described in "Using a PuTTY serial connection" on page 35.

Replacing a server module
2. Reboot the server module by inserting the end of a paper clip into the hole for the
recessed power button in the bottom right corner of the module and then gently pressing
the paper clip against the power button for five seconds if the module is still powered on
or two seconds if the module is powered off.
3. Monitor the server module startup process in the PuTTY window on the laptop computer:
¡ If you see a message indicating either that a boot device cannot be found or that the
server module cannot boot from a given device, both SSDs in the module are bad
and need to be replaced.
¡ If the startup process stops before you see such a message, the server module
itself has a problem and needs to be replaced.

If a server module in an S10 Node fails, you need to replace that module. If the OS SSDs in
the failed server module are still good, you can move them to the new server module. In this
case, after replacing the server module, you need to check and, if necessary, update
firmware in the new server module.
If the SSDs in the failed server module are not good, you need to insert new SSDs into the
new server module. In this case, after replacing the server module, you need to recover the
HCP S Series operating system and software on the new server module.
Notes:
• The server module replacement procedure described in this document can be used with
S Series Nodes at release 2.1.1 or later. During this procedure, the S Series Node
remains available.
If the S Series Node is at a release below 2.1.1, you need to use the server replacement
procedure described in HCP S10 Node Maintenance for the applicable release. In this
case, the procedure requires that the S Series Node be shut down.
• Typically, during a firmware update, the server module being updated is unavailable for
both management purposes and data access for approximately five minutes.
What you need for replacing a server module

For replacing a server module, you need:
• The new server module

Server module part number: ASM-01666-01-A.X

Note: Before using the new server module, check the pins on the back of the module. If
any pins are bent, do not use the module. Instead, return it to the manufacturer and
request a new one.
• If the SSDs in the old server module cannot be reused, two new SSDs
SSD part number: ASM-01667-01-A.X
• If you move the SSDs from the old server module to the new server module, a laptop
computer with:
¡ PuTTY and Pageant installed on it. For information about installing PuTTY and
Pageant on a laptop computer, see "Installing PuTTY and Pageant" on page 34.
¡ The S Series Node service SSH key in the SSH keychain on the computer. For
• If the operating system and software need to be recovered on the new server module:
¡ A USB-to-mini-USB cable.
¡ One bootable USB flash drive or DVD that contains the installation files for the
version of the HCP S Series software that's currently installed on the S10 Node.
If you don't already have an OS and software installation USB flash drive or DVD,
you need to create one, as described in "Preparing an installation USB flash drive or
DVD".
Step 1 (conditional): Shut down the server module you want to replace
If the server module you want to replace (that is, the old server module) is still running, you
need to shut it down. You can shut down a server module from the HCP S Series
Management Console or by using the management API.
To shut down the server module from the Management Console:
4. In the Server Module field, select the server module you want to shut down.
Server module 1 is the server module on the left in the enclosure when viewed from the
back. Server module 2 is the server module on the right.
6. Click Shut Down.

Step 2: Remove the old server module from the enclosure

To remove the old server module from the enclosure:
the server interconnect port on the server module.
Step 3: Move the old SSDs or insert new SSDs

If the SSDs in the old server module are still good, you can move them to the new server
module. For instructions on doing this, see "Moving the SSDs from the old server module to
the new server module" on the next page.
If the SSDs in the old server module are not good, do not move them. Instead, insert new
SSDs into the new server module. For instructions on doing this, see "Inserting new SSDs
into the new server module" on the next page.

Moving the SSDs from the old server module to the new server module
To move the SSDs from the old server module to the new server module:
1. Remove the panel from the right side of each of the old and new server modules. To
remove a panel:
a. Using the #0 Phillips screwdriver, remove the small silver screw from the top of the
panel.
b. Lift the panel out of the server module.
2. In the old server module, remove the foam drive stabilizer that's holding the SSDs in
place.
3. Pull one SSD out of the old server module. When pulling the SSD, you may need to
wiggle it from side to side to loosen it.
4. Insert the SSD from the old server module into the new server module in the same
position as the SSD was in in the old server module. To insert the SSD:
a. Align the SSD with the black card edge connector on the bottom of the server
module.
b. Push the SSD all the way down into the connector.
5. Repeat steps 3 and 4 with the second SSD.
6. In the new server module, place the foam drive stabilizer from the old server module on
the SSDs, fitting the tops of the SSDs into the slots in the stabilizer.
7. Replace the side panel on each server module. To replace a side panel:
a. Insert the bottom tab on the panel into the slot at the bottom of the panel opening.
b. Push the panel into position.
c. Using the #0 Phillips screwdriver, screw the small silver screw back into the hole in
the top of the panel. Tighten the screw.
Inserting new SSDs into the new server module
To insert two new SSDs into the new server module:

1. Remove the panel from the right side of each server module. To remove a panel:
panel.

2. In the old server module, remove the foam drive stabilizer that's holding the SSDs in
place.
3. Insert the new SSDs into the new server module. To insert an SSD:
module.
4. In the new server module, place the foam drive stabilizer from the old server module on
the SSDs, fitting the tops of the SSDs into the slots in the stabilizer.
5. Replace the side panel on each server module. To replace a side panel:
Step 4: Insert the new server module into the enclosure

To insert the new server module into the enclosure:
1. Ensure that the handle on the new server module is lowered as far as the handle goes.
2. Slide the server module all the way back into the server module slot in the enclosure.
When the module reaches the back of the enclosure, the handle pops up slightly.
The new server module should power on automatically, and the HCP S Series software
should start on it. If the software doesn't start, the cause may be that the firmware on the
server module is out of date.
Note: If you moved the SSDs from the old server module to the new server module,
while the HCP S Series software is starting on the new server module, the module
automatically reboots one time.
5. Reconnect the access network, management, and server interconnect cables to the
Ethernet ports on the new server module. Be sure to connect each cable to the same port
as the one from which you removed the cable.
When inserting each access network cable into the applicable access port, ensure that
the card in the nonmetal portion of the connector at the end of the cable is facing the
other access port on the same server module.
When inserting the management and server interconnect cables into the applicable
ports, push each cable in until the end of the cable clicks into place.

Step 5: Check and, if necessary, update the firmware on the new server
module
To check and, if necessary, update the firmware on the new server module and, if applicable,
the new OS SSDs:
2. Use PuTTY to establish an SSH connection to the new server module, as described in
4. Enter this command:
This command:
a. Checks the currently installed firmware versions on the new server module.
b. If any of the firmware needs to be updated, updates that firmware.
As part of the firmware update process, the HCP S Series software shuts down on
the new server module. Typically, the update process takes less than five minutes,
after which the software restarts. However, if the update includes the BMC
firmware, the update process can take up to 45 minutes. Also, if the update includes
the BMC firmware, at the end of the process, the new server module automatically
reboots.
c. Rechecks the currently installed firmware versions on the new server module.
If all the firmware is up to date, this message appears:
If any of the firmware is still not up to date, this failure message appears for each
piece of outdated firmware:
If any failure messages appear, contact your HCP support center for help.
5. Reboot the new server module. To do this, insert the end of a paper clip into the hole for
the recessed power button in the bottom right corner of the module and then gently press
the paper clip against the power button for five seconds.
6. Use PuTTY to a establish a new SSH connection to the new server module.

Replacing one or both SSDs in a server module
8. Enter this command to update the BIOS on the new server module, regardless of
whether any firmware was updated:
sudo firmware.py bios prod
During the BIOS update process, the new server module automatically reboots.
Step 6 (conditional): Recover the new server module

If you used the new SSDs in the new server module, you need to recover the module.
Recovering a new server module installs the HCP S Series operating system and software
on that module.
For instructions on recovering a server module, see "Recovering a server module" on
page 101.
Step 7 (conditional): Check the health of the S10 Node

If any firmware has been updated, you need to check the health of the S10 Node.
To check the health of the S10 Node:
1. If you do not currently have an SSH connection to either server module:
a. Use PuTTY to establish an SSH connection to either server module, as described in
b. At the login prompt, enter service.
2. In the PuTTY window, enter:
/home/service/bin/install
3. When prompted, press Enter to continue.

The HCP S Series Node Service Menu appears.
4. Enter 1 to display the S10 Node status information.
5. In the status display, check that all components are running and healthy (that is, the
status is either Online, OK, or active).
An S10 Node can take up to ten minutes to become available after a firmware update. If
any components are not running and healthy and at least ten minutes have passed since
the firmware update finished, contact your HCP support center for help.
6. Enter b to return to the HCP S Series Node Service Menu.
7. Enter q to return to the command-line prompt.
8. Enter y to confirm that you want to leave the HCP S Series Node Service Menu.

If one of the OS SSDs in an S10 Node server module fails, you need to replace that SSD and
then configure the new SSD. If both the OS SSDs in a server module fail, you need to
replace both SSDs. In this case, after you replace the SSDs, you need to recover the HCP S
Series operating system and software on the server module.

What you need for replacing one or both SSDs in a server module
For replacing OS SSDs, you need:
• One or two new OS SSDs, as applicable

SSD part number: ASM-01667-01-A.X
• If you're replacing a single SSD, a CAT6 Ethernet cable
• If you're replacing a single SSD, a laptop computer with:

¡ PuTTY and Pageant installed on it. For information about installing PuTTY and
Pageant on a laptop computer, see "Installing PuTTY and Pageant" on page 34.
¡ The S Series Node service SSH key in the SSH keychain on the computer. For
• If the operating system and software need to be recovered on the server module, which
is the case only when you replace both OS SSDs in the module:
¡ A USB-to-mini-USB cable.
¡ One bootable USB flash drive or DVD that contains the installation files for the
version of the HCP S Series software that's currently installed on the S10 Node.
If you don't already have an OS and software installation USB flash drive or DVD,
you need to create one, as described in "Preparing an installation USB flash drive or
DVD".
drive with a USB connector (only if replacing both OS SSDs).
Step 1: Shut down the server module
Important: Before you shut down the server module, if you're replacing only one SSD, you
need to know the location of that SSD. For information about locating an SSD, see
"Degraded OS SSD" on page 174.
To shut down the server module that contains the SSD or SSDs you want to replace:
4. In the Server Module field, select the server module you want to shut down.
Server module 1 is the server module on the left in the enclosure when viewed from the
back. Server module 2 is the server module on the right.

6. Click Shut Down.
Step 2: Remove the server module from the enclosure

To remove the server module from the enclosure:
the server interconnect port on the server module.
Step 3: Replace the SSD or SSDs

To replace one or both OS SSDs in the server module:
1. Remove the panel from the right side of the server module. To do this:
panel.
2. Remove the foam drive stabilizer that's holding the SSDs in place.

3. Pull the SSD you're replacing or both SSDs, as applicable, up out of the server module.
When pulling an SSD, you may need to wiggle it from side to side to loosen it.
4. Insert the new SSD or SSDs, as applicable, into the server module. To insert an SSD:
module.
5. Replace the foam drive stabilizer on the SSDs, fitting the tops of the SSDs into the slots
in the stabilizer.
6. Replace the side panel on the server module. To do this:
Step 4: Reinsert the server module into the enclosure

To reinsert the server module into the enclosure:
1. Ensure that the handle on the server module is lowered as far as the handle goes.
2. Slide the server module all the way back into the server module slot in the enclosure.
When the module reaches the back of the enclosure, the handle pops up slightly.
The new server module should power on automatically, and the HCP S Series software
should start on it. If the software doesn't start, the cause may be that the firmware on the
server module is out of date.

5. Reconnect the access network, management, and server interconnect cables to the
Ethernet ports on the server module. Be sure to connect each cable to the port from
which you removed the cable.
When inserting each access network cable into the applicable access port, ensure that
the card in the nonmetal portion of the connector at the end of the cable is facing the
other access port on the same server module.
When inserting the management and server interconnect cables into the applicable
ports, push each cable in until the end of the cable clicks into place.
Step 5: Check and, if necessary, update the firmware on the new SSD or
SSDs
To check and, if necessary, update the firmware on the new OS SSD or SSDs:
2. Use PuTTY to establish an SSH connection to the server module in which you replaced
the OS SSD or SSDs, as described in "Using a PuTTY SSH connection" on page 36.
4. If you replaced a single SSD in the server module, wait for the rebuild of that SSD to
finish.
To check whether the SSD rebuild has finished, enter this command:
cat /proc/mdstat
If the output for each md device looks something like this, the rebuild is complete:
md1 : active raid1 sda1[0] sdb1[1]
1045504 blocks super 1.2 [2/2] [UU]
If the output for any md device contains a line that includes something like this, the
rebuild is not yet complete:
[==>..................] recovery = 12.6%
5. Enter this command:

This command:
a. Checks the currently installed firmware versions on the new SSD or SSDs and on
other components in the server module that has the new SSD or SSDs.
b. If any of the firmware needs to be updated, updates that firmware.
As part of the firmware update process, the HCP S Series software shuts down on
the server module that has the new SSD or SSDs. Typically, the update process
takes less than five minutes, after which the software restarts. However, if the
update includes the BMC firmware, the update process can take up to 45 minutes.
Also, if the update includes the BMC firmware, at the end of the process, the new
server module automatically reboots.

Replacing the server interconnect cable
c. Rechecks the currently installed firmware versions on the new SSD or SSDs and on
other components in the server module that has the new SSD or SSDs.
If all the firmware is up to date, this message appears:
If any of the firmware is still not up to date, this failure message appears for each
piece of outdated firmware:
If any failure messages appear, contact your HCP support center for help.
Step 6: Configure the new SSD or recover the server module

After replacing a single SSD in a server module, you need to configure the new SSD. After
replacing both SSDs in a server module, you need to recover that server module. For
instructions on recovering a server module, see "Recovering a server module" on page 101.
To configure the new SSD:
1. If you haven't already done so, add the S Series Node service SSH key to your
2. Use PuTTY to establish an SSH connection to the server module in which you replaced
the SSD, as described in "Using PuTTY for SSH access over an Ethernet connection"
on page 38.
4. Enter this command to find the device name for the new SSD:
lsscsi | grep -e StorFly -e VikingDisk -e VPFEM
In the response to this command:

¡ SSD0 (attached to card edge connector J11) is identified as [0:0:0:0].
¡ SSD1 (attached to card edge connector J10) is identified as [1:0:0:0].
¡ The device name for each SSD has this format: /dev/sdletter
For example: /dev/sda
5. Enter this command to configure the new SSD:
sudo os_drive_maint.sh add device-name
For example:
sudo os_drive_maint.sh add /dev/sda

When the server interconnect cable in an S10 Node is not functioning properly, one of the
server modules is unavailable. In this case, you need to replace the cable. After you replace
the cable, you need to power the unavailable module back on.

What you need for replacing a server interconnect cable

For replacing the server interconnect cable used in anS10 Node, you need:
• A new purple one-foot CAT6 Ethernet cable (part number 541-145-001-S.X)
• A paper clip
Replace the server interconnect cable

To replace the server interconnect cable used by anS10 Node:
1. Disconnect the old server interconnect cable from the server interconnect port on each
server module.
2. Connect the new server interconnect cable to the server interconnect port on each server
module.
3. Insert the end of a paper clip into the hole for the recessed power button in the bottom
right corner of the unavailable server module. Then gently press the paper clip against
the power button for two seconds.
If the server module does not become available again after you press the power button,
you can power the module back on by sliding it partially out of the enclosure and then
pushing it back in. For instructions on doing this, see"Replacing a server module".

Chapter 10: Maintaining PDUs
The PDUs for an HCP S10 Node can be:
• Hitachi Universal V2 PDUs, which are installed vertically on the sides of a rack
• Hitachi Vantara-supplied 1U horizontal PDUs
• Customer-supplied PDUs, which can be horizontal or vertical

PDUs are installed in pairs. In each pair of vertical PDUs, one PDU is on the left side of the
rack. The other is on the right side of the rack.
The two PDUs in a pair of horizontal PDUs are installed in contiguous rack units, one on top
of the other.
A rack with only HCP S10 Nodes has three pairs of PDUs.
Hitachi Universal V2 PDUs

A Hitachi Universal V2 PDU has three color-coded sections: blue, red, and yellow. On the
Americas and EMEA/APAC PDU models used with an S10 Node:
• Each section has one breaker
• Each section has one C19 outlet next to the breaker
• The blue and red sections each have three C13 outlets
• On the Americas models, the yellow section has two C13 outlets
• On the EMEA/APAC models, the yellow section has three C13 outlets
The C13 outlets are counted separately in each section:
• Outlets in the blue section are counted starting from the end of the PDU.
• Outlets in the red section are counted starting from the end of the blue section.
• Outlets in the yellow section are counted starting from the end of the red section.
Each outlet is identified by these properties, in order:
• The section color: B (blue), R (red), or Y (yellow)
• The breaker number: always 1
• The outlet type: C19 or C13
• The number of the outlet within its section, preceded by a hyphen (-)
For example, the second C13 outlet in the red section is R1C13-2.
The power inlet cable is attached to the blue end of the PDU.

Power-cable connections with Hitachi Universal V2 PDUs
The figure below shows the layout of the PDU models used with S10 Nodes.

The diagram in this section shows the power-cable connections between the S10 Node
enclosures and the outlets on the Hitachi Universal V2 PDUs.
Reading the diagrams
The power cable connection diagram shows a single rack. The view is from the rear of the
rack.
The diagram has:
• A center column that shows all possible enclosures
• Left and right U# columns that show the rack units in which each enclosure is installed
• Left and right PDU outlet columns that show only the used outlets
• Left and right PDU configuration columns that show the number of PDUs installed on
each side of the rack and the orientation of each PDU
Each enclosure connects to the outlets that, in the diagram, are aligned with the bottom rack
unit occupied by that enclosure.

For each enclosure, the power and cooling module on the left connects to a PDU on the left
side of the rack. The power and cooling module on the right connects to a PDU on the right
side of the rack.
Diagram legend
In the power-cable connection diagram:
• Sections labeled "Empty" do not contain any enclosures.
• Rack units in italics with a gray background in the U# column show the PDU bracket
locations.
• Outlet background colors (blue, red, and yellow) correspond to the circuits on the PDUs.
• The "PWR" label on each PDU shows which end of the PDU has the power inlet cable.
The PDUs in the diagrams are not drawn to scale.
For an explanation of the outlet identifiers, see "Hitachi Universal V2 PDUs" on page 190.

Power-cable connections with Hitachi Vantara-supplied horizontal PDUs
Power-cable connection diagram
Power-cable connections with Hitachi Vantara-supplied

horizontal PDUs
The Hitachi Vantara-supplied 1U horizontal PDUs used with older S10 Nodes are installed in
pairs. In each pair, the bottom PDU is installed right side up, and the top PDU is installed
upside down.

Power-cable connections with Hitachi Vantara-supplied horizontal PDUs
This PDU model has two sets of three outlets. The set on the left is labeled M1. The set on
the right is labeled M2. In each set, the outlet on the left is labeled 1 (one), and the outlet on
the right is labeled 3. The middle outlet, outlet 2, is not labeled.
The figure below shows a pair of PDUs oriented as they would be when installed in a rack.
The table below shows the PDU outlet connections for the power and cooling modules in S10
Node enclosures. The specified locations for the power and cooling modules are as viewed
from the rear of the rack.
Power and
Enclosure cooling
rack unit module PDU pair PDU position Outlet
U37 Left Top Top M1-2
Right Top Bottom M1-2
U23 Left Middle Top M1-2
Right Middle Bottom M1-2
U11 Left Bottom Top M1-2
Right Bottom Bottom M1-2

PDU outlet correspondences
PDU outlet correspondences

The table below shows the correspondences between the outlets in a Hitachi Vantara-
supplied 1U horizontal PDU and the outlets in a Hitachi Universal V2 PDU for the purpose of
S10 Node enclosure connections. The specified locations for the Hitachi Universal V2 PDUs
are as viewed from the rear of the rack.
For an explanation of the Hitachi Vantara-supplied horizontal PDU identifiers, see "Power-
cable connections with Hitachi Vantara-supplied horizontal PDUs" on page 193. For an
explanation of the Hitachi Universal V2 PDU outlet identifiers, see "Hitachi Universal V2
PDUs" on page 190.
Enclosure Hitachi Vantara-supplied Hitachi Universal

rack unit horizontal PDU outlet V2 PDU outlet
U37 Top pair, top PDU: M1-2 Top pair, left PDU: Y1C19-1
Top pair, bottom PDU: M1-2 Top pair, right PDU: Y1C19-1
U33 Top pair, top PDU: M2-1 Top pair, left PDU: R1C19-1
Top pair, bottom PDU: M2-1 Top pair, right PDU: R1C19-1
U29 Top pair, top PDU: M2-3 Top pair, left PDU: B1C19-1
Top pair, bottom PDU: M2-3 Top pair, right PDU: B1C19-1
U23 Middle pair, top PDU: M1-2 Middle pair, left PDU: Y1C19-1
Middle pair, bottom PDU: M1-2 Middle pair, right PDU: Y1C19-1
U19 Middle pair, top PDU: M2-1 Middle pair, left PDU: R1C19-1
Middle pair, bottom PDU: M2-1 Middle pair, right PDU: R1C19-1
U15 Middle pair, top PDU: M2-3 Middle pair, left PDU: B1C19-1
Middle pair, bottom PDU: M2-3 Middle pair, right PDU: B1C19-1
U11 Bottom pair, top PDU: M1-2 Bottom pair, left PDU: B1C19-1
Bottom pair, bottom PDU: M1-2 Bottom pair, right PDU: B1C19-1
U07 Bottom pair, top PDU: M2-1 Bottom pair, left PDU: R1C19-1
Bottom pair, bottom PDU: M2-1 Bottom pair, right PDU: R1C19-1
U03 Bottom pair, top PDU: M2-3 Bottom pair, left PDU: Y1C19-1
Bottom pair, bottom PDU: M2-3 Bottom pair, right PDU: Y1C19-1

Replacing a PDU
Replacing a PDU
If a PDU fails or is damaged, you can replace it. The table below shows the replacement
options.
PDU to be replaced Replacement PDU options
Hitachi Universal V2 PDU Hitachi Universal V2 PDU
Hitachi Vantara-supplied 1U horizontal PDU • Hitachi Vantara-supplied 1U horizontal

PDU, if available
• Hitachi Universal V2 PDU
Customer-supplied horizontal PDU • Customer-supplied horizontal PDU
• Customer-supplied vertical PDU (if the

rack is not a Hitachi Universal V2 rack)
• Hitachi Universal V2 PDU (if the rack is a

Hitachi Universal V2 rack)
Customer-supplied vertical PDU Customer-supplied vertical PDU
If you use a vertical PDU to replace one PDU in a pair of horizontal PDUs, the resulting pair
has one PDU of each type. This configuration is allowed.
What you need for replacing a PDU

For replacing a PDU, you need:
• The new PDU.

PDU part numbers:
¡ Hitachi Universal V2 PDU:
– Americas single phase: 1P30A-8C13-3C19UL.X
– Americas three phase: 3P30A-8C13-3C19UL.X
– EMEA/APAC single phase: 1P32A-9C13-3C19CE.X
– EMEA/APAC three phase: 3P16A-9C13-3C19CE.X
¡ Hitachi Vantara-supplied 1U horizontal PDU:
– Americas single phase: PDU-063112F10.X
– Americas three phase: PDU-063315F10.X
• A Sharpie and masking tape.
• If you're removing or installing a Hitachi Universal V2 PDU, a quarter-inch slotted

screwdriver.
• If you're removing or installing a Hitachi Vantara-supplied 1U horizontal PDU:

¡ A caged nut tool
¡ A #2 Phillips screwdriver

Replacing a PDU
• If you're installing a Hitachi Vantara-supplied 1U horizontal PDU:

¡ Four caged nuts
¡ Four large black screws
The assembly kit for the Hitachi Universal V2 rack includes caged nuts and large black
screws.
If the PDU you're replacing is a Hitachi Vantara-supplied 1U horizontal PDU, you can
reuse the caged nuts and large black screws that were used to install that PDU.
Replace the PDU

To replace the PDU:
1. For each power cable that's plugged into the old PDU:
a. Use the Sharpie and masking tape to label the PDU end of the cable with the outlet
identifier.
For the Hitachi Universal V2 PDU outlet identifiers, see "Hitachi Universal V2
PDUs" on page 190.
For the Hitachi Vantara-supplied horizontal PDU identifiers, see "Power-cable
connections with Hitachi Vantara-supplied horizontal PDUs" on page 193.
b. Disconnect the cable from the PDU.
2. Remove the old PDU from the rack.
This step is optional if you're replacing a horizontal PDU with a vertical PDU.
For instructions on removing a Hitachi Universal V2 PDU from a rack, see Hitachi
Universal V2 PDU Installation, Replacement, and Removal.
For instructions on removing a Hitachi Vantara-supplied horizontal PDU from a rack, see
"Removing a Hitachi Vantara-supplied horizontal PDU from a rack" on the next page.
3. Install the new PDU in the rack.
If you're replacing a horizontal PDU with a vertical PDU and:
¡ The old PDU is the top PDU in a pair, install the new PDU on the left side of the rack
(when viewed from the rear of the rack)
¡ The old PDU is the bottom PDU in a pair, install the new PDU on the right side of the
rack (when viewed from the rear of the rack)
For instructions on installing a Hitachi Universal V2 PDU in a rack, see Hitachi Universal
V2 PDU Installation, Replacement, and Removal.
For instructions on installing a Hitachi Vantara-supplied horizontal PDU in a rack, see
"Installing a Hitachi Vantara-supplied horizontal PDU in a rack" on the next page.
4. Connect the disconnected power cables to the new PDU.
If the new PDU is the same type as the old PDU, be sure to plug each cable into the
outlet that matches the label on the cable.

Removing a Hitachi Vantara-supplied horizontal PDU from a rack
If the old PDU is a Hitachi Vantara-supplied horizontal PDU and the new PDU is a
Hitachi Universal V2 PDU, be sure to plug each cable into the outlet that corresponds to
the outlet on the cable label. For the outlet correspondences, see "PDU outlet
correspondences" on page 195.
Removing a Hitachi Vantara-supplied horizontal PDU from a rack

To remove a Hitachi Vantara-supplied horizontal PDU from a rack:
1. While holding the PDU so that it doesn't fall, use the #2 Phillips screwdriver to unscrew
and remove the four large black screws that attach the PDU to the rear of the rack. Then
remove the PDU from the rack.
After removing the PDU, you have access to the caged nuts in the four holes from which
you removed the screws.
2. Use the caged nut tool to remove the four caged nuts from the rack.
3. On each side of the PDU, using the #2 Phillips screwdriver, unscrew and remove the
silver screws that attach the side bracket to the PDU.
Installing a Hitachi Vantara-supplied horizontal PDU in a rack

Hitachi Vantara-supplied 1U horizontal PDUs are installed in pairs at the rear of the rack. In
each pair, the bottom PDU is installed right side up, and the top PDU is installed upside
down.
The PDUs are installed with the outlet side facing the rear of the rack. The other side of each
PDU, where the power inlet cable is attached, faces the front.
Each PDU comes with two side brackets that you need to attach to the PDU before you can
install the PDU in the rack. The screws that attach the PDUs to the rack require caged nuts.

Installing a Hitachi Vantara-supplied horizontal PDU in a rack
To install a Hitachi Vantara-supplied horizontal PDU in a rack:

1. Attach the side brackets to the PDU. To attach a side bracket:
a. With the side of the bracket that has the round holes against one side of the PDU,
position the side of the bracket that has the oblong holes so that the side is flush with
the outlet side of the PDU. Align the round holes in the bracket with the holes in the
side of the PDU.
b. Using the #2 Phillips screwdriver and two of the silver screws that come with the
PDU, attach the bracket to the PDU.
2. At the rear of the rack, use the caged nut tool to attach the four caged nuts to the top and
bottom holes (two on the left and two on the right) in the vertical mounting rails in the rack
unit in which you're mounting the PDU. Orient the caged nuts so that the brackets on the
nut grip the left and right sides of the holes.
3. At the rear of the rack, position the PDU in the rack so that:
¡ The sides of the PDU brackets that have the oblong holes are in front of the vertical
mounting rails (when viewed from the rear of the rack)
¡ The oblong holes in the PDU brackets are aligned with the holes to which you
attached the caged nuts
4. Using the #2 Phillips screwdriver and the four large black screws, attach the PDU to the
rack.

Chapter 11: Using the system service tools
HCP S Series Nodes include tools that let you act on both server modules in an S Series
Node with a single command. These Python tools, called system service tools , use
SSH to log into each server module in the S Series Node at the same time and perform the
actions you request:
• cluster_ssh does any of these:

¡ Issues one or more Linux commands on each module
¡ Reboots or shuts down each module
¡ Retrieves internal log messages from each module
¡ Runs a user-supplied script on each module
• cluster_get retrieves files from the each module.
• cluster_put stores files on each module.
About the system service tools

To use a system service tool:
Note: Depending on the action you want to perform, you may also need the root SSH
key in your keychain.

4. Enter the command to run the tool you want.
Each system service tool writes all output both to the console and to files on the server
module on which you ran the tool. The output files, one for each server module, are located in
the /var/rhino/logs directory. The name of each file is username-server-module-
interconnect-ip-address.out (for example, service-10.1.1.1.out).
The system service tools all use the same set of output files. As each tool runs, it appends
its output to the text that already exists in the files.

cluster_ssh
cluster_ssh
The cluster_ssh tool does any of these:
• Issues one or more Linux commands to be executed on each server module
• Reboots or shuts down each server module
• Retrieves internal log messages from each server module

Syntax for the cluster_ssh tool is:
cluster_ssh.py
(-h|--help)
|--version
|([(-u|--user) username]
[(-t|--timeout_min) timeout-minutes]
[(-T|--max_threads) max-threads]
[-v|--verbose]
(((-l|--level) message-severity-level)
|(-r|--reboot)
|(-H|--halt)
|((-i|--inputScript) script-file)
|"command-string"))
cluster_ssh parameter descriptions

The table below describes the parameters for the cluster_ssh tool.
Parameter Description
-h|--help Displays and describes the syntax for the cluster_ssh tool; then exits.
--version Displays the version number of the currently installed cluster_ssh tool; then
exits.
(-u|--user) username Tells cluster_ssh to log into each server module with the specified username. If
you omit this parameter, cluster_ssh logs in with the username you used to log
into the server module on which you're running the tool.
(-t|--timeout_min) Specifies the number of minutes cluster_ssh should wait for any given
timeout-minutes command to finish before canceling the comand. The default is 2,880.
(-T|--max_threads) Specifies the maximum number of threads cluster_ssh can use to run any given
max-threads command on each server module. The default is 25.
-v|--verbose Reports cluster_ssh activity in greater detail. If an error occurs while cluster_
ssh is running, rerunning the same cluster_ssh command with this parameter
can help identify the problem.

cluster_ssh
(Continued)
(-l|--level) message- Retrieves all the log messages with the specified severity level or a more severe
severity-level level from the log files in the /var/rhino/logs directory on each server module.
Valid values for message-severity-level are:
FINEST
FINER
FINE
INFO
WARNING
SEVERE
These values are case sensitive.

This parameter is mutually exclusive with the -r, --reboot, -H, --halt, -i, --
inputScript, and command-string parameters.
-r|--reboot Tells cluster_ssh to shut down the HCP S Series software on each server
module and then reboot the module.
This parameter is mutually exclusive with the -l, --level, -H, --halt, -i, --
-H|--halt Tells cluster_ssh to shut down the HCP S Series software on each server
module and then power off the module.
This parameter is mutually exclusive with the -l, --level, -r, --reboot, -i, --
(-i|--inputScript) Specifies a user-supplied script for cluster_ssh to execute on each server

script-file module. script-file is the name of the script file with or without a directory
path. If included, the path can be absolute or relative to the current directory.
Before running the script, cluster_ssh puts it in a temporary location on each
server module. After running the script, cluster_ssh deletes it from that location.
This parameter is mutually exclusive with the -l, --level, -r, --reboot, -H, --
halt, and command-string parameters.

cluster_ssh
(Continued)
"command-string" Specifies one or more commands for cluster_ssh to execute on each server
module. cluster_ssh executes multiple commands on each module in the order
in which you specify them.
Use a semicolon (;) or a double ampersand (&&) to separate each command
from the next:
• The semicolon means proceed with the next command even if the current
command fails.
• The double ampersand means do not proceed if the current command fails.
The double quotation marks (") are required when you specify more than one
command or when you specify a single command with one or more options. You
can omit the quotation marks around a single command with no options.
This parameter is mutually exclusive with the -l, --level, -r, --reboot, -H, --
halt, -i, and --inputScript parameters.
Note: To reboot server modules, use the -r or --reboot parameter instead of a
reboot command. With a reboot command, the server module on which you ran
the tool may shut down before it can communicate the request to the other server
module. Similarly, use the -H or --halt parameter instead of a shutdown
command.
cluster_ssh examples
Here are three sample cluster_ssh commands:
• The cluster_ssh command below echoes the ping command on each server module.
You can use a command like this on one server module to check whether the other
server module is running.
cluster_ssh.py "echo ping"

cluster_ssh
The console output from this command looks like this:
• The cluster_ssh command below displays the current date and time followed by
information about the current run of the HCP S Series software on each server module.
cluster_ssh.py "date;uptime"

cluster_ssh
• The cluster_ssh command below retrieves all the messages with a severity level of
SEVERE from the log files in the /var/rhino/logs directory on each server module.
The messages appear in the cluster_ssh output.
cluster_ssh.py --level SEVERE

cluster_get
cluster_get
The cluster_get tool retrieves one or more files from each server module and stores them on
the server module on which you ran the tool. By default, the files are stored in subdirectories,
one per server module, of a particular directory, but you can choose to have them stored
directly in that directory. The name of each subdirectory is the server interconnect network
IP address of the applicable server module.
Syntax for the cluster_get tool is:
cluster_get.py
(-h|--help)
|--version
[-d|--disable-unique-ify]
[-v|--verbose]
((-l|--logs)
|((-i|--image) [--days number-of-days])
|((source-file|source-directory) destination-directory)))

cluster_get
cluster_get parameter descriptions

The table below describes the parameters for the cluster_get tool.
-h|--help Displays and describes the syntax for the cluster_get tool; then exits.
--version Displays the version number of the currently installed cluster_get tool; then
exits.
(-u|--user) username Tells cluster_get to log into each server module with the specified username. If
you omit this parameter, cluster_get logs in with the username you used to log
(-t|--timeout_min) Specifies the number of minutes cluster_get should wait for any given
timeout-minutes command to finish before canceling the command. The default is 2,880.
(-T|--max_threads) Specifies the maximum number of threads cluster_get can use to run any given
-d|--disable- Puts all the returned files directly in the directory identified by the destination-
unique-ify directory parameter. With the -d or --disable-unique-ify parameter, files
with the same name that come from different server modules overwrite each
other.
Without the -d or --disable-unique-ify parameter, cluster_get puts each
returned file in a directory named with the server interconnect network IP
address for the server module from which the files was retrieved. These
directories are located in the directory specified by the destination-directory
parameter.
The -d and --disable-unique-ifyparameters are not valid with the -l, --logs,
-i, and --image parameters.
-v|--verbose Reports cluster_get activity in greater detail. If an error occurs while cluster_get
is running, rerunning the same cluster_get command with this parameter can
help identify the problem.
-l|--logs Retrieves and compresses the S Series Node internal log files in the
/var/rhino/logs directory on each server module. The log files from each
server module are compressed into a single file named access-network-ip-
address_log.tar.bz2, which is then stored in a subdirectory of the current
directory. The name of each subdirectory is the server interconnect network IP
address for the server module from which the log files were retrieved.
The -l and --logs parameters are not valid with the -i, --image, source-file,
source-directory, and destination-directory parameters.
For information about the internal log files, see "Internal logs" on page 55.

cluster_get
(Continued)
-i|--image Retrieves and compresses the S Series Node internal log files in the
/var/rhino/logs directory on each server module, along with other files
containing server module information that’s useful for identifying problems. The
log files and other information from each server module are compressed into a
single file named fully-qualified-server-module-hostname-image.tar.bz2,
which is then stored in a subdirectory of the current directory. The name of each
subdirectory is the server interconnect network IP address for the server module
from which the log files were retrieved.
The -i and --image parameters are not valid with the -l, --logs, source-file,
source-directory, and destination-directory parameters.
For information about the internal log files, see "Internal logs" on page 55.
Important: This operation is CPU intensive. It also makes reviewing the logs in
real time more difficult for support personnel. Do not request this operation
unless explicitly told to do so by HCP support personnel.
--days number-of-days Specifies the number of days worth of logs to retrieve from the /var/rhino/logs
directory when the -i or --image parameter is specified in the cluster_get
command. Days are counted backward starting from the current day.
The --days parameter is valid only with the -i and --image parameters
source-file Specifies the file cluster_get should retrieve from each server module. The file
specification must include the absolute path to the file.
The source-file parameter is not valid with the -l, --logs, -i, --image, and
source-directory parameters.
source-directory Specifies a directory from which cluster_get should retrieve all files on each
server module, including the files in any subdirectories of that directory,
recursively. The directory specification must be an absolute path.
The source-directory parameter is not valid with the -l, --logs, -i, --image,
and source-file parameters.
destination-directory Specifies the directory in which cluster_get should put the returned files. The
directory specification can be an absolute path or a path relative to the current
directory. If the specified directory doesn’t exist, cluster_get creates it.
The destination-directory parameter is required with the source-file and

source-directory parameters. It is not valid with the -l, --logs, -i, and --
image parameters.
cluster_get examples
Here are three sample cluster_get commands:
• The cluster_get command below retrieves the build.version file from each server
module and stores it in a directory named with the server interconnect network IP
address of that server module. cluster_get creates these directories in the
/service/temp directory on the server module on which the command was run. You
can use this command to verify that the same version of the HCP S Series software is
installed on both server modules.
cluster_get.py /opt/rhino/build.version /service/temp

cluster_get
• The cluster_get command below retrieves a compressed copy of the contents of

/var/ris/logs from each server module. Each copy is stored in a subdirectory of the
current directory. The subdirectory is named with the server interconnect network IP
address of the applicable server module. The command tells cluster_get to log into each
server module with the username root in order to have the permissions required for the
requested action.
cluster_get.py -u root -l
• The cluster_get command below retrieves a copy of the S Series Node internal logs
from the current day and the previous day from each server module, along with other files

cluster_get
containing useful information. For each server module, the retrieved files are
compressed into a single file named using the fully qualified hostname of that module
and stored in a subdirectory of the current directory. The subdirectory is named with the
server interconnect network IP address of the applicable server module.
cluster_get.py -i --days 2

cluster_put
cluster_put
The cluster_put tool stores one or more files on each server module. Syntax for this tool is:
cluster_put.py
(-h|--help)
|--version
[-v|--verbose]
(source-file|source-directory)
[destination-directory])
cluster_put parameter descriptions

The table below describes the parameters for the cluster_put tool.
-h|--help Displays and describes the syntax for the cluster_put tool; then exits.
--version Displays the version number of the currently installed cluster_put tool; then
exits.
(-u|--user) username Tells cluster_put to log into each server module with the specified username. If
you omit this parameter, cluster_put logs in with the username you used to log
(-t|--timeout_min) Specifies the number of minutes cluster_put should wait for any given
timeout-minutes command to finish before canceling the command. The default is 2,880.
(-T|--max_threads) Specifies the maximum number of threads cluster_put can use to run any given
-v|--verbose Reports cluster_put activity in greater detail. If an error occurs while cluster_put
is running, rerunning the same cluster_put command with this parameter can
help identify the problem.
source-file Specifies the file cluster_put should store. cluster_put copies this file only from
the server module on which you're running the tool.
The file specification can include an absolute path or a path relative to the
current directory.
source-directory Specifies a directory containing the files cluster_put should store. cluster_put
copies all files in the specified directory, including the files in any subdirectories
of that directory, recursively. cluster_put copies the files only from the server
module on which you're running the tool.
The directory specification must be an absolute path.

cluster_put
(Continued)
destination-directory Specifies the directory in which cluster_put stores the files on each server
module. The specified directory must already exist.
The directory specification must be an absolute path.
If you don't specify a destination directory, cluster_put uses the soruce directory
as the destination directory. If the source directory is specified by a relative path,
cluster_put creates an absolute destination directory path by appending that
path to the path to the current directory.
cluster_put examples
Here are two sample cluster_put commands:
• The cluster_put command below copies the fix-3.sh file from the current directory on
the server module on which you're running the tool to the existing
/service/temp/fixes directory on each server module.
cluster_put.py fix-3.sh /service/temp/fixes
• The cluster_put command below copies the /service/temp/cluster.cfg file from

the server module on which you're running the tool to the to the /opt/rhino/config
directory on each server module, overwriting the cluster.cfg file that's already in that
directory. The command tells cluster_put to log into each server module with the
username root in order to have the permissions required for the requested action. This
command is useful for propagating configuration changes to both server modules at the
same time.
cluster_put.py -u root /service/temp/cluster.cfg /opt/rhino/config

cluster_put

Appendix: HCP S Series Node Configuration
Information form
This appendix contains a form on which you can record the information you need for the
configuration of an HCP S Series Node. So that the information you need is readily available,
keep the completed form with you when you perform a custom reinstallation of the HCP S
Series OS and software, configure the S Series Node for the customer environment, or
recover a server module.
Appendix: HCP S Series Node Configuration Information form

HCP S Series Node Configuration Information

Use this form to record the information you need for the configuration of an S Series Node.
Field Value
Identification
Domain name
Serial number
Initial user account
Password
Access network
IP mode o IPv4
o IPv6
Access network: IPv4 settings
IPv4 gateway address
IPv4 subnet mask
Server module 1 physical IPv4 address
Server module 2 physical IPv4 address
Server module 1 virtual IPv4 address
Server module 2 virtual IPv4 address
Access network: IPv6 settings
Primary IPv6 gateway address
Primary IPv6 prefix length
Server module 1 primary physical IPv6 address
Server module 2 primary physical IPv6 address
Server module 1 primary virtual IPv6 address
Server module 2 primary virtual IPv6 address
Secondary IPv6 gateway address
Secondary IPv6 prefix length
Server module 1 secondary physical IPv6 address

(Continued)
Field Value
Server module 2 secondary physical IPv6 address
Server module 1 secondary virtual IPv6 address
Server module 2 secondary virtual IPv6 address
Access network: Other settings
Duplex o Auto
o 10GbE Full
Bonding mode o active-backup
o 801.3ad
MTU o 1500
o 9000
VLAN ID (optional)
Management network
IP mode o IPv4
o IPv6
Management network: IPv4 settings
IPv4 gateway address

(do not use 10 as the fourth octet)
IPv4 subnet mask
Server module 1 IPv4 address

Server module 2 IPv4 address

Management network: IPv6 settings
Primary IPv6 gateway address

(do not use 10 as the last segment)
Primary IPv6 prefix length
Server module 1 primary IPv6 address

Server module 2 primary IPv6 address

Secondary IPv6 gateway address

Secondary IPv6 prefix length

(Continued)
Field Value
Server module 1 secondary IPv6 address

Server module 2 secondary IPv6 address

Management network: Other settings
Duplex o Auto
o 10MbE Half
o 10MbE Full
o 100MbE Half
o 100MbE Full
o 1GbE Full
MTU o 1500
o 9000
VLAN ID (optional)
Server interconnect network
Subnet
DNS servers and time servers
DNS server IP addresses
Time server IP addresses

Hitachi Vantara
Corporate Headquarters Contact Information
2535 Augustine Drive USA: 1-800-446-0744
Santa Clara, CA 95054 USA Global: 1-858-547-4526
HitachiVantara.com | community.HitachiVantara.com HitachiVantara.com/contact

HCP S10 Node v2 2 0 Maintenance FE-HCPS002-17

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCP S10 Node v2 2 0 Maintenance FE-HCPS002-17

Uploaded by

Copyright:

Available Formats

Hitachi Content Platform S Series Node

HCP S10 Node Maintenance

HCP S10 Node Maintenance 2

Chapter 2: HCP S10 Node physical requirements 19

HCP S10 Node Maintenance 3

Chapter 3: Preparing for HCP S10 Node maintenance 31

Chapter 4: Configuring an HCP S Series Node in DNS 44

Chapter 5: Monitoring an HCP S10 Node 49

Chapter 6: Maintaining the HCP S Series operating system and software 59

HCP S10 Node Maintenance 4

Chapter 7: Maintaining data and database drives 114

HCP S10 Node Maintenance 5

Chapter 8: Maintaining the enclosure 132

HCP S10 Node Maintenance 6

Chapter 9: Maintaining server modules 173

HCP S10 Node Maintenance 7

Chapter 10: Maintaining PDUs 190

Chapter 11: Using the system service tools 200

Appendix: HCP S Series Node Configuration Information form 214

HCP S10 Node Maintenance 8

Notation Meaning Example

boldface Type exactly as it appears in This book shows: cluster_ssh.py

italics Replace with a value of the This book shows: username

| Vertical bar — Choose one This book shows: -h|--help

[] Square brackets — Include This book shows: [-v|--verbose]

() Parentheses — Include This book shows: (-T|--max_threads)

• HCP S Series Node Refurbishment (FE-HCPS013) — This book contains complete

• HCP S Series Node Troubleshooting (FE-HCPS007) — This book contains information

Accessing product documentation

• Adds the option to put the HCP S Series OS and software

• Updates the format of HCP S Series OS and software

• Adds instructions for using Rufus to reformat bootable USB

• Updates the formats of software upgrade and hotfix file names

• Removes information about database conversion from

• Adds instructions for running update prechecks independently

• Adds the "free space for update of internal database," "repair

• Corrects the number of OS and software installation USB drives

• Adds the option to use a DVD instead of a USB flash drive to

• Changes the default for data in-flight encryption from disabled

• Changes the default for SSH access from enabled to disabled

• Adds instructions for using the first-time setup wizard to

• Adds an optional instruction to have the customer enable SSH

• Adds instructions for recovering a server module

• Adds instructions for checking firmware versions after replacing

• Updates the part number for the server interconnect cable

• Power distribution options

HCP S Series Nodes

Chapter 1: HCP S10 Node overview

For administrative purposes, S Series Nodes provide a web-based Management Console

S10 Node hardware components

Chapter 1: HCP S10 Node overview

S10 Node product offerings

S10 Node Number of Number of

Half populated 6 TB 28 4 192 TB

Fully populated 6 TB 56 4 360 TB

Half populated 10 TB 28 4 320 TB

Fully populated 10 TB 56 4 600 TB

S10 Node rack options

Chapter 1: HCP S10 Node overview

S10 Node power distribution options

1P30A-8C13-3C19UL.X Americas Single 208V, 30A, NEMA L6-30P 8 3

3P30A-8C13-3C19UL.X Americas Three 208V, 30A, NEMA L15-30 8 3

1P32A-9C13-3C19CE.X EMEA/APAC Single 230V, 32A, IEC309 2P+E 9 3

3P16A-9C13-3C19CE.X EMEA/APAC Three 400V, 16A, IEC309 3P+N+E 9 3