installing an hcp anywhere system final on-site setup anywhere managementconsole. accesstoactive...

Hitachi Content Platform AnywhereInstalling an HCP Anywhere System - Final On-site Setup

MK-HCPAW005-07

©© 2013, 2015 Hitachi Data Systems Corporation. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic ormechanical, including photocopying and recording, or stored in a database or retrieval system for anypurpose without the express written permission of Hitachi Data Systems Corporation (hereinafter referredto as “Hitachi Data Systems”).

Hitachi Data Systems reserves the right to make changes to this document at any time without notice andassumes no responsibility for its use. This document contains the most current information available at thetime of publication. When new or revised information becomes available, this entire document will beupdated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the most recentproduct announcement for information about feature and product availability, or contact Hitachi DataSystems at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions ofthe applicable Hitachi Data Systems agreements. The use of Hitachi Data Systems products is governed bythe terms of your agreements with Hitachi Data Systems.

By using this software, you agree that you are responsible for:

a) Acquiring the relevant consents as may be required under local privacy laws or otherwise fromemployees and other individuals to access relevant data; and

b) Ensuring that data continues to be held, retrieved, deleted, or otherwise processed in accordance withrelevant laws.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi DataSystems is a registered trademark and service mark of Hitachi, Ltd., in the United States and othercountries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM,Lotus, MVS, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries,z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.

All other trademarks, service marks, and company names in this document or web site are properties oftheir respective owners.

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, andmay be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility to obtainlicenses to export, re-export, or import the Document and any Compliant Products.

https://support.hds.com/en_us/contact-us.html

Contents

Preface viiIntended audience viiProduct version viiWhat's new viiRelated documents viiiAccessing product documentation ixGetting help ixComments ix

Chapter 1: HCPAnywhere system overview 1About HCP Anywhere 2Management Console 2Nodes 2Physical system types 3System architecture and networking 4Final on-site setup activities 6

Chapter 2: Site preparation 7Environmental requirements 8Domain name system requirements 9User authentication requirements 9Time source requirements 10Network connection information 10Components that you supply 20

Chapter 3: Assembling rackless components 21Before assembling rackless components 22

Contents iii

Installing an HCP Anywhere System - Final On-site Setup

Components that come with a rackless system 22Servers 23Server mounting hardware 24Ethernet switches 24Power cords 26Perforated blanking plates 26

Components that you supply for a rackless system 26Server and switch placement 27Tools and accessories you need 27

What you do 28Step 1: Prepare the rack 29Step 2: Install the PDUs 29Step 3: Mount the back-end Ethernet switches 29What you need 30What you do 30

Step 4: Install the Rails 31Step 4a: Separate the inner and outer server rails 31Step 4b: Attach the inner rails to the server 34Step 4c: Install the outer server rails in the rack 35

Step 4d: Mount the server in the rack 37Step 5: Connect the servers to the PDUs 38What you need 39What you do 39

Step 6: Connect the switches to the PDUs 39What you need 39What you do 40

Step 7: Install the perforated blanking plates 40What you need 40What you do 41

Step 8: Connect the back-end Ethernet cables to the back-end switches 41Step 9: Connect the back-end Ethernet cables to the servers 42What you need 42What you do 42

Step 10: Reassemble the rack 42

Chapter 4: Connecting and configuring HCPAnywhere at your site 43Connecting to the power sources 44Reconfiguring the HCP Anywhere system for your site 44

What you need to know 45

iv Contents


Preparing to reconfigure the system 46Step 1: Connect to the HCP Anywhere default back-end network 47Step 2: Log in with the initial user account 47Step 3: Check the health of the HCP Anywhere system 48

Reconfiguring the system 49Connecting to your corporate network 50Verifying the serial number 52Installing license files 52Performing additional configuration activities 54

Chapter 5: Configuringmonitoring with Hi-TrackMonitor 55Enabling SNMP in HCP Anywhere 56Configuring Hi-Track Monitor 57

Index 59

Contents v


vi Contents


Preface

This book is the final on-site setup guide for physical Hitachi ContentPlatform Anywhere (HCP Anywhere) systems. It provides all theinformation you need to deploy an assembled and configured HCPAnywhere system at your site. It also contains instructions for assemblingthe components of an HCP Anywhere system that was ordered without arack. Additionally, it explains how to configure Hi-Track Monitor to monitorthe nodes in the HCP Anywhere system.

Note: This book does not contain information about deploying HCPAnywhere in virtual machines. For information on doing that, seeDeploying an HCP Anywhere VM System.

Intended audience

This book is intended for the people at a customer site who are responsiblefor the on-site setup of an HCP Anywhere system. It assumes you haveexperience with computer networking, installing computer hardware, and abasic understanding of HCP Anywhere systems.

Product version

This book applies to release 2.0.4 of HCP Anywhere.

What's new

Support for VMWare HA for single node VM systems

Support for ESXI 6.0

Preface vii


Support for Quanta D51B-2U ServersAs of release 2.0.4 of HCP Anywhere, new Standard and Entry pods are nowQuanta D51B-2U servers.

Note: This book is about HCP Anywhere systems installed on QuantaD51B-2U servers. For information on systems running on CR210H servers,see Installing an HCP Anywhere System - Final On-site Setup for version2.0 of HCP Anywhere.

Related documents

These documents contain additional information about HCP Anywhere:

• HCP Anywhere Administrator Help— This set of help topics containsthe instructions you need to use the HCP Anywhere ManagementConsole to configure and monitor an HCP Anywhere system and itshardware. This set of help topics also includes instructions onadministering the file synchronization and sharing and HDI devicemanagement features.

This set of help topics is accessible from the HCP Anywhere ManagementConsole.

• HCP Anywhere User Help— This set of help topics explains how to useHCP Anywhere for file storage and synchronization. These topics discussthe file synchronization interfaces that HCP Anywhere provides, whichinclude desktop and mobile applications and a web application called theUser Portal.

This set of help topics is accessible from the HCP Anywhere User Portal.

• Deploying an HCP Anywhere VM System— This book provides theinformation you need to install HCP Anywhere in virtual machines. Itexplains what you need to know to successfully configure your VMenvironment and contains step-by-step instructions for the installationprocedure.

• Assembling and Configuring an HCP Anywhere System— This bookcontains complete instructions for building an HCP Anywhere system,from assembling and configuring the hardware to installing the HCPAnywhere software.

Related documents

viii Preface


• Third-party Copyrights and Licenses — This book contains copyrightand license information for third-party software distributed with orembedded in the HCP Anywhere operating system, core software, andfile synchronization and sharing applications.

Accessing product documentation

Product documentation is available on Hitachi Data Systems SupportConnect: https://support.hds.com/en_us/documents.html. Check thissite for the most current documentation, including important updates thatmay have been made after the release of the product.

Getting help

Hitachi Data Systems Support Portal is the destination for technicalsupport of products and solutions sold by Hitachi Data Systems. To contacttechnical support, log on to Hitachi Data Systems Support Connect forcontact information: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is the destination to get answers, discover insights, and makeconnections. Join the conversation today! Go to community.hds.com,register, and complete your profile.

Note: If you purchased your HCP Anywhere from a third party, pleasecontact your authorized service provider.

Comments

Please send us your comments on this document:

[email protected]

Include the document title and part number, including the revision (forexample, -01), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data Systems.

Thank you!

Accessing product documentation

Preface ix


https://support.hds.com/en_us/documents.html



https://community.hds.com/

http://community.hds.com/

mailto:[email protected]

x Preface


HCP Anywhere system overview

An HCP Anywhere system is delivered to a customer site as either unrackedcomponents or as a racked appliance installed in the same rack as anHCP system. In either case, all the components are preconfigured and theHCP Anywhere software is already installed. However, once the system isdelivered, it needs some final on-site setup.

This chapter introduces HCP Anywhere and describes the hardware andsoftware used in an HCP Anywhere system. It also contains an overview ofthe final setup activities required to make your HCP Anywhere systemoperational at your site.

Notes:

• In this book, a system that is delivered in a rack with an HCP system isreferred to as a preassembled system. A system that is deliveredwithout a rack is referred to as a rackless system. For a racklesssystem, you provide the rack in which the system is installed.

• This book does not contain information about deploying HCP Anywherein virtual machines. For information on doing that, see Deploying anHCP Anywhere VM System.

Note: This book is about HCP Anywhere systems installed on QuantaD51B-2U servers. For information on systems running on CR210H servers,see Installing an HCP Anywhere System - Final On-site Setup for version2.0 of HCP Anywhere.

Chapter 1: HCP Anywhere system overview 1


1

About HCP Anywhere

HCP Anywhere is the system from Hitachi Data Systems (HDS) thatprovides these two major features:

• File synchronization and sharing — This feature allows a user toaccess and share files from any location at which the user has Internetaccess.

When a user adds files to HCP Anywhere, HCP Anywhere stores the filesin a Hitachi Content Platform (HCP) system. The files are then madeavailable through a web browser application called the HCP AnywhereUser Portal and through each computer, smartphone, and tablet thatthe user has registered with HCP Anywhere.

• HDI device management— This feature allows an administrator toconfigure and monitor Hitachi Data Ingestor (HDI) systems thathave been deployed at multiple remote sites throughout an enterprise.

For information on purchasing HDI devices, please contact your HCPAnywhere sales representative.

Management Console

HCP Anywhere includes a web application called theManagementConsole. The HCP Anywhere system administrator uses this Console toconfigure, monitor, and manage the system. The Console reports certainhardware problems as they occur, so the system administrator can takeappropriate action to initiate repairs.

Nodes

A physical HCP Anywhere system includes two servers, called nodes, thatare networked together. Nodes are the essential part of an HCP Anywheresystem.

Both nodes run the complete HCP Anywhere software. Additionally, thesystem keeps copies of essential system data on both nodes. These featuresensure that if a node fails, the system remains accessible to users.

2 Chapter 1: HCP Anywhere system overview


About HCP Anywhere

Physical system types

Depending on the internal hardware of the nodes, a physical HCP Anywheresystem can be one of two types:

• Entry Pod — This type consists of two nodes that can support up to5,000 file synchronization and sharing users.

• Standard Pod — This type consists of two nodes with more memory,storage space, and processing power than the nodes in an Entry Pod.Standard Pod systems shipped after release 2.0 can support up to50,000 file synchronization and sharing users. Older Standard Podsystems support up to 20,000 users.

Note: For information on converting an Entry Pod to a Standard Pod or onupgrading a pre-2.0 Standard Pod system to support up to 50,000, contactyour HCP Anywhere sales representative.

The final on-site setup activities you need to perform are identical for bothhardware configurations.



Physical system types

System architecture and networking

HCP Anywhere system hardware consists of:

• Two nodes, which are Quanta D51B-2U servers. These nodes arenetworked together.

• Ethernet cables and Brocade ICX 6430 Ethernet switches fornetworking.

Two-node HCP Anywhere systems, both physical and VM, use back-end andfront-end networks. Single-node VM systems use only a front-end network.

The front-end network is used for:

• Access by HCP Anywhere applications on user's computers and mobiledevices

• Browser access to the User Portal and Management Console

• Storing and accessing files in the HCP system that HCP Anywhere uses

• Sending configuration information to and receiving health reports fromHDI devices

The back-end network is used for inter-node communication.

Caution: The back-end network must be isolated, non-routable, andremain separate from the front-end network. Interfering with the operationof the back-end network can cause the HCP Anywhere system to becomeinoperable and can result in data loss.

To connect the nodes to the front-end network (that is, your corporatenetwork), the recommended setup includes two independent Ethernetswitches that connect these ports to the front-end network.

As delivered, an HCP Anywhere system includes the Ethernet switches thatestablish the back-end network. You need to supply two front-end switchesand all the cables needed to connect each server to the front-end switches.

For information on the switches and cables that you need to supply, see"Components that you supply" on page 20.




The figure below shows the architecture of a physical HCP Anywheresystem.

The table below describes the cables in this illustration.

Cable color Cable type Connects from Connects to

Red Ethernet Ethernet port 4 ineach node

Back-end switches

Blue Ethernet Ethernet port 2 ineach node

Back-end switches

Green* Ethernet Ethernet port 3 ineach node

Front-end switches

Orange* Ethernet Ethernet port 1 ineach node

Front-end switches

Purple Ethernet Back-end switches Each other

Black Power Each node Two PDUs

Each back-endswitch

One PDU

* The orange and green cables in this illustration represent the front-end Ethernetcables that you provide. These cables do not need to be orange and green, though it isrecommended that you use cables that are colors other then red and blue.




Final on-site setup activities

An HCP Anywhere system arrives with the HCP Anywhere software alreadyinstalled and configured with various default settings.

To get the system up and running, you need to perform the activitiesoutlined in the table below.

Step Activity More information

1 Verify that your site is ready for the HCP Anywhere system to beinstalled.

"Chapter 2: Sitepreparation" on page 7

2 For a preassembled system, remove the rack containing the HCP andHCP Anywhere systems from the packing crate and position it in yourdata center.

N/A

For a rackless system, assemble the HCP Anywhere systemcomponents in a rack that you supply.

"Chapter 3:Assembling racklesscomponents" onpage 21

3 Connect the HCP Anywhere PDUs to your power sources. "Connecting to thepower sources" onpage 44

4 Connect the HCP Anywhere system to your corporate network.

If the preconfigured front-end IP addresses don't work for yourenvironment, perform step 6 below before performing this step.

"Connecting to yourcorporate network" onpage 50

5 Configure the HCP Anywhere hostname in the corporate DNS setup. Besure to use your site-specific node IP addresses and HCP Anywheresystem name and not the default settings that the system arrives with.

N/A

6 Reconfigure the HCP Anywhere system for your environment. "Reconfiguring theHCP Anywhere systemfor your site" onpage 44

7 Optionally, configure Hi-Track Monitor to monitor the HCP Anywherenodes.

"Chapter 5:Configuringmonitoring with Hi-Track Monitor" onpage 55



Final on-site setup activities

Site preparation

Before an HCP Anywhere system can be deployed, you need to ensure thatthe intended location for the system meets certain environmentalrequirements. If it doesn't, you should wait to deploy the system until thenecessary changes have been made.

You also need to have on hand the additional components that enable youto complete the connections between the HCP Anywhere system and yourenvironment.

HCP Anywhere requires Windows Active Directory (AD) for userauthentication. For HCP Anywhere to support AD, you need to provideaccess to one or more servers running Windows Active Directory.

You need to configure various network components such as firewalls andload balancers to manage traffic for the HCP Anywhere system. To configurethese components, you need to know certain network connectioninformation for the HCP Anywhere system.

This chapter describes the conditions, components, network connectioninformation, and Active Directory system requirements for successfulinstallation and operation of an HCP Anywhere system at your site.

Chapter 2: Site preparation 7


2

Environmental requirements

This section contains information on the environmental requirements of theservers and switches that make up an HCP Anywhere system.

The table below shows the approximate weights of the servers and switchesin an HCP Anywhere system.

Weight Value

Each Quanta D51B-2U server Approximately 55 lbs (25 kg)

This value varies depending on the type of HCPAnywhere system to which the node belongs.Nodes in an HCP Anywhere Standard Pod systemare heavier than nodes in an HCP Anywhere EntryPod system.

Two back-end Ethernet switches Approximately 15.16 lbs (6.88 kg)

Your data center must be able to compensate for the componentcharacteristics shown in the table below. All measurements in this table areat 200V.

Component

Max. powerdraw inwatts

Max. total currentdraw in amps

Max. coolingin BTUs/hour

Each Quanta D51B-2Userver

314.08 1.51 1,071.0

Each Brocade ICX 6430Ethernet switch

24.16 0.9 70.08

For information on the environmental requirements of the servers,switches, and infrastructure components of the HCP system thataccompanies a preassembled HCP Anywhere system, see the applicableHCP documentation:

• For HCP SAIN systems, see Installing an HCP SAIN System— FinalOn-site Setup

• For HCP RAIN systems, see Installing an HCP RAIN System— FinalOn-site Setup

8 Chapter 2: Site preparation


Environmental requirements

Domain name system requirements

Before installing the HCP Anywhere system at your site, you need toconfigure the HCP Anywhere hostname in your corporate DNS setup. Besure to use your site-specific node IP addresses and HCP Anywhere systemname and not the default settings that the system arrives with.

User authentication requirements

HCP Anywhere requires Windows Active Directory for userauthentication. For HCP Anywhere to be able to use AD:

• All Active Directory domain controllers must run one of these:

¡ Windows Server 2012 R2

¡ Windows Server 2012

¡ Windows Server 2008 R2

• HCP Anywhere must have network connectivity to one or more domainsin the AD forest.

Note: By default, HCP Anywhere attempts to connect to every domainin the forest. If your AD infrastructure does not allow HCP Anywhere todo this, you can use the domain whitelist in the Management Console tospecify only the domains to which the system can connect. Forinformation, see the HCP Anywhere Administrator Help, which isavailable from the Management Console.



Domain name system requirements

• HCP Anywhere must be able to contact at least one DNS server that canresolve the AD domain name. Additionally, HCP Anywhere must be ableto do reverse DNS lookups of the IP addresses of all AD domaincontrollers that HCP Anywhere is configured to use (that is, the DNSconfiguration must include PTR records for the IP addresses that identifyhostnames for AD domain controllers).

• The AD time must be in sync with the HCP Anywhere system time. Therecommended configuration is for HCP Anywhere and AD to use thesame time server.

Additionally, to ensure that AD users have continuous access to HCPAnywhere, the AD infrastructure should have a robust and fault tolerantconfiguration.

Note: HCP Anywhere also supports using the SAML protocol tocommunicate with Active Directory Federation Services (AD FS). This allowsHCP Anywhere to authenticate users from multiple AD forests. For moreinformation, see the HCP Anywhere Administrator Help, which isaccessible from the documentation icon ( ) in the top righthand corner ofeach Management Console page.

Time source requirements

The HCP Anywhere system requires at least one external time server as atime source. Ideally, HCP Anywhere and Active Directory should use thesame time source.

Network connection information

The table in this section contains network connection information aboutinbound and outbound traffic for an HCP Anywhere system. You need thisinformation when configuring networking components such as loadbalancers and firewalls to manage network traffic for an HCP Anywheresystem.

You also need the information in the table for configuring your network tosupport SSL termination for HCP Anywhere. SSL termination is a processin which SSL-encrypted traffic bound for one server is redirected to anotherserver that decrypts the information and then sends it to the target server.In this way, the target server does not need to use its resources to decryptthe information.



Time source requirements

Note: To support SSL termination, you also need to enable support for it inthe HCP Anywhere Management Console. For information on doing this, seethe HCP Anywhere Administrator Help.

Tip: Even when you have enabled SSL termination support for the HCPAnywhere system, you should configure the HCP Anywhere system to usean SSL certificate that's been signed by a trusted vendor. This increasesthe likelihood that user's computers, browsers, and mobile devices willautomatically trust the HCP Anywhere system.

In the table, each row represents a type of network traffic. The Optional orrequired column indicates whether the applicable type of traffic is requiredfor the HCP Anywhere system to function properly. Each node in the HCPAnywhere system can handle all types of network traffic listed in the table.




Purpose

Inboundor

Outbound SourceSourceNetwork Target Port Protocol

Optionalor

required Notes

Insecure (HTTP)access to the UserPortal and forcommunicationrelated to filesynchronization andsharing and HDIdevice management

Inbound Proxies forSSL termination(load balancers,RP caches)

DMZ orCorporate

HCPAnywheresystem

80 TCP Optional To support externalSSL termination for filesynchronization andsharing and HDI devicemanagement featurecommunication, HCPAnywhere uses port 80for HTTP accesswithout SSL security.All returned URLs useHTTP with SSL security(HTTPS).

Support for externalSSL termination can beenabled and disabled inthe HCP AnywhereManagement Console.




Purpose

Inboundor


Optionalor

required Notes

Secure (HTTPS)access to the UserPortal and forcommunicationrelated to filesynchronization andsharing and HDIdevice management

Inbound Any of these:

• A registeredcomputer

• A registeredmobile device

• A webbrowser usedto access theHCPAnywhereUser Portal

• An HDIdevice

InternetorCorporate

HCPAnywheresystem

443 TCP Required If support for externalSSL termination isdisabled in the HCPAnywhereManagement Console,HCP Anywhere usesonly port 443 for filesynchronization andsharing and HDI devicemanagement featurecommunication.

Access to the HCPAnywhereManagementConsole throughHTTPS

Inbound Administratorclient computeraccessing theManagementConsole througha web browser

Corporate HCPAnywheresystem

8000 TCP Required HCP Anywhere usesonly port 8000 foraccess to theManagement Console.

SSH access to theHCP Anywheresystem by HDSservice personnel

Inbound Support clientcomputer


22 TCP, UDP Optional Support for SSH accessto the HCP Anywheresystem can be enabledand disabled in theManagement Console.

(Continued)



Purpose

Inboundor


Optionalor

required Notes

SNMP access formonitoring the HCPAnywhere system

Inbound NetworkMonitoringSystem (SNMP)


161 TCP, UDP Optional Support for SNMP canbe enabled anddisabled in theManagement Console.

Hi-Track Monitor usesSNMP tomonitor theHCP Anywhere system.

HCP Anywheresupports only SNMPversion 2c.

HCP Anywhere doesnot send system logmessages to SNMPmanagers.

(Continued)




Purpose

Inboundor


Optionalor

required Notes

Active Directoryauthentication

Outbound HCP Anywheresystem

Corporate ActiveDirectoryserver

88 TCP, UDP Required For access to theManagement Consoleand the filesynchronization andsharing feature, HCPAnywhere requiresActive Directory foruser authentication.

Support for ActiveDirectoryauthentication isconfigured in theHCP AnywhereManagement Console.

Access to ActiveDirectory LDAPservice



389 TCP, UDP Required HCP Anywhere usesthe LightweightDirectory AccessProtocol (LDAP) foruser authenticationand for ensuring thatAW support forAD authenticationcontinues to function.

(Continued)



Purpose

Inboundor


Optionalor

required Notes

Maintaining thepassword for theHCP Anywherecomputer account inActive Directory



464 TCP, UDP Required HCP Anywhere usesthe Kerberos kpasswdservice toautomatically changethe password for theHCP Anywherecomputer account inAD.

Access to MicrosoftGlobal Catalog



3268 TCP, UDP Required HCP Anywhereaccesses the GlobalCatalog for AD userauthentication and forensuring that AWsupport forAD authenticationcontinues to function.

DNS nameresolution


Corporate DNS server 53 TCP, UDP Required The HCP Anywheresystem requires accessto DNS servers forperformingDNS lookups.

(Continued)




Purpose

Inboundor


Optionalor

required Notes

Access to externaltime server


Corporate NTP server 123 TCP, UDP Required HCP Anywhererequires a time sourcethat is an externalNTP time server.

The recommendedconfiguration is for HCPAnywhere and theActive Directory serverto use the same timeserver.

Email notification ofHCP Anywhereevents


Corporate InternalSMTP server

25 TCP, UDP Optional HCP Anywhere can beconfigured to sendemail notificationswhen certain eventsoccur.

Syslog logging ofHCP Anywhereevents


Corporate Internalsyslogserver

Configurable(default is514)

UDP Optional HCP Anywhere can beconfigured to sendevent logs to anexternal syslog server.

The port can beconfigured in theManagement Console.By default, HCPAnywhere uses 514.

(Continued)



Purpose

Inboundor


Optionalor

required Notes

Virus scanning offiles added by filesynchronization andsharing users


Corporate InternalICAPservers

Configurable(default is1344)

TCP Optional HCP Anywhere can beconfigured to send filesto one or more ICAPservers for virusscanning.

The port can beconfigured in theManagement Console.By default, HCPAnywhere uses 1344.

Managing HCPtenants


Corporate HCP system 9090 TCP Required HCP Anywhere usesthe HCP ManagementAPI to manage HCPtenants.

For filesynchronization andsharing, reading andwriting user files toan HCP system


Corporate HCP system 443 TCP Required By default, HCPAnywhere reads andwrites files to HCPthrough HTTPS.

For filesynchronization andsharing, reading andwriting user files toan HCP system


Corporate HCP system 80 TCP Optional HCP Anywhere can beconfigured to read andwrite files to HCPthrough HTTP withoutSSL security (HTTP).

(Continued)




Purpose

Inboundor


Optionalor

required Notes

For filesynchronization andsharing, access tothe contents of NASservers.


Corporate NAS servers 445 TCP Optional HCP Anywhere can beconfigured to grantusers access to NASshares through themobile applications andthe User Portal.

HCP Anywhere usesCIFS to communicatewith NAS servers.

(Continued)



Components that you supply

To establish the front-end network for both rackless and preassembled HCPAnywhere systems, you need to provide:

• Two Ethernet switches in your corporate network. Each switch:

¡ Must support full-duplex communication.

¡ Must have a port speed of one GB/s or less. The recommended portspeed is one GB/s.

¡ Must support autonegotiation.

¡ Must have two open ports, one for each node in the HCP Anywheresystem.

¡ Must have the Spanning Tree Protocol (STP) disabled.

• To establish the front-end network, for each node, two Cat 6 Ethernetcables. If possible, half of these cables should be one color and halfanother color. Also, if possible, the colors of these cables should not bered and blue because these are the colors of the cables used to establishthe back-end network.

To assemble a rackless system, you need to provide some components inaddition to the ones described above. For information on these components,see "Components that you supply for a rackless system" on page 26.



Components that you supply

Assembling rackless components

The components of a rackless HCP Anywhere system are deliveredconfigured but unassembled. You need to provide some additionalcomponents and assemble the system at your site. This chapter providesinstructions for doing this.

Chapter 3: Assembling rackless components 21


3

Before assembling rackless components

This section lists the tools and accessories you need and containsinformation you need to know to assemble an HCP Anywhere system thatwas shipped as separate components.

Components that come with a rackless system

For a rackless HCP Anywhere system, these components are shipped to yoursite:

• Two servers with the HCP Anywhere software already installed. For moreinformation on the servers that make up an HCP Anywhere system, see"Servers" on the facing page.

Each server comes with the necessary hardware for installing it in a rack.For more information on this hardware, see "Server mountinghardware" on page 24.

• Two back-end Ethernet switches. For more information on the switches,see "Ethernet switches" on page 24.

• Power cords for the servers and back-end switches — two per server andone per switch. These power cords are separate from the power cordsincluded in the original packaging for each server and switch.

If the PDUs you supply aren't compatible with the power cords includedwith the system, you also need to supply two power cords for each serverand one power cord for each switch. For more information on the powercords that are shipped with a rackless system, see "Power cords" onpage 26.

• Two red and two blue Ethernet cables for connecting the servers to theback-end switches.

• A purple Ethernet cable for connecting the back-end switches to eachother.

• Two perforated blanking plates for covering the rack units that containthe back-end switches.

• One serial number label. This label is taped to the top of the first nodeyou mount when you assemble the system.

22 Chapter 3: Assembling rackless components



• A CD that contains any license files for the system. These license filesincrease the number of file synchronization and sharing users and HDIdevices that the HCP Anywhere system can have.

After setting up the HCP Anywhere system for your site, you use theManagement Console to install these license files. For instructions ondoing this, see "Installing license files" on page 52.

Servers

HCP Anywhere nodes are Quanta D51B-2U servers. Each server occupiestwo rack units.

The internal components of a Quanta D51B-2U server differ depending onwhether the server is part of a Standard Pod system or Entry Pod system. Aserver in a Standard Pod system has more memory, processing power, anddisk space than a server in an Entry Pod system.

The front of each server has two buttons on the left side. The top button isthe power button. The button below it is the reset button.

The figure below shows the front of a Quanta D51B-2U server.

Each server has six Ethernet ports on the back. Going from left to right onthe back of the server, these Ethernet ports are labeled 2, 1, andMaintenance (represented by a wrench icon). In the HCP AnywhereManagement Console and operating system, ports 1 and 2 are identified aseth0 and eth1, respectively. Port M is reserved for server maintenance andis not represented in the Console or OS.




The table below contains information on how these Ethernet ports are usedin an HCP Anywhere system.

Port Use

1 (eth0) Front-end communication

2 (eth1) Back-end communication

3 (eth2) Front-end communication

4 (eth3) Back-end communication

M Reserved for server maintenance

The back of each server also has two sockets for power cords, one on theright and one on the left.

The picture below shows the back of a Quanta D51B-2U server.

Server mounting hardware

For rack mounting, each Quanta D51B-2U server comes with two rail kits,one for each side. It doesn’t matter which kit you use for each side.

Each rail kit consists of one part that you attach to the server, one part thatyou install in the rack, and an extra part that you remove and set aside. Thepart that attaches to the server comes nested inside the part that youinstall in the rack.

Ethernet switches

A physical HCP Anywhere system uses two 1U Brocade ICX 6430 Ethernetswitches for the back-end network.




The front of each switch has 24 ports in two rows of 12. The ports arenumbered starting from the top left. The odd-numbered ports are the onesin the top row. The even-numbered ports are the ones in the bottom row.

The back of each switch has a socket for a power cord.

The figures below show the front and back of a Brocade ICX 6430 Ethernetswitch.

Each switch comes with:

• Two mounting brackets.

• Six small black screws.

• Eight larger silver screws with bushings and washers.

• Four cage nuts.

You use the purple Ethernet cable to connect the two switches.




Power cords

Several separately-packaged power cords are shipped with a racklessHCP Anywhere system. These cords require PDUs with C14 IEC receptacles.

Each Ethernet switch comes with an additional power cord and each servercomes with two additional power cords. These power cords require PDUswith NEMA 5-15-P receptacles.

If the PDUs that you supply are not compatible with either type of powercord, you need to provide alternative power cords as applicable. To connectto a server or switch, each power cord you provide must have a C13 IECplug at one end.

Perforated blanking plates

An HCP Anywhere system uses two 1U perforated blanking plates to coverthe units where the Ethernet switches are mounted.

Components that you supply for a rackless system

To assemble the system, you need to supply these additional components:

• A rack that meets these requirements:

¡ It must be a 19-inch (482.6 mm) EIA-310-E-compliant four-postrack with square or unthreaded round holes.

¡ It must support a rail depth between 660.4 and 1,430.4 mm.

¡ If it has square holes, it must have a square-hole adjustment rangeof 692 to 756 mm.

¡ It must have clearance of at least 45 inches (1,143 mm) at the front.

¡ It must have six contiguous empty rack units to accommodate thetwo servers and the two back-end Ethernet switches. Each serveroccupies two rack units, and each switch occupies one rack unit.

• Two PDUs.

If the PDUs you supply aren't compatible with the power cords includedwith the system, you also need to supply two power cords for each serverand one power cord for each switch. For more information on the powercords, see "Power cords" above.




• Velcro straps and/or cable ties for bundling and securing cables.

• Screws and cage nuts for installing the perforated blanking plates.

Additionally, you need to provide Ethernet switches and cables forconnecting the HCP Anywhere system to your corporate network. Forinformation on the switches and cables you need to provide, see"Components that you supply" on page 20. For information on connectingthe HCP Anywhere system to your corporate network after you assemble thesystem hardware, see "Connecting to your corporate network" onpage 50.

Server and switch placement

When assembling the system, you need to arrange the servers and switchesin the rack in a specific order.

The top of each server has a label that indicates the relative order of theserver in the rack. The order is given as an integer (for example, 1).

Within the empty rack units:

• Mount the switches for the back-end network. Do not skip any rackunits. The front of each switch, where the Ethernet ports are located,faces the rear of the rack

• Mount the two servers directly above those switches. Mount the serverlabeled 1 (one) in the rack unit above the topmost back-end switch.Mount the server labeled 2 in the rack unit above that one. Do not skipany rack units.

Tools and accessories you need

To assemble the hardware for an HCP Anywhere system, you need thesetools and accessories:

• Four spare Ethernet cables.

These cables are used to simulate the front-end network during the HCPAnywhere software installation. These cables are not shipped to thecustomer site.

• #1 Phillips screwdriver.

• #2 Phillips screwdriver.




• Cage-nut tool.

• Wire cutters.

• Velcro straps.

• Cable ties.

Tip: The hardware assembly is easiest with a magnetic screwdriver.

What you do

To assemble the hardware for an HCP Anywhere system:

1. Prepare the rack for the installation of the HCP Anywhere systemcomponents (see Step 1: "Prepare the rack" on the facing page)

2. Install the PDUs in the rack (see Step 2: "Install the PDUs" on thefacing page)

3. Mount the back-end Ethernet switches in the rack (see Step 3: "Mountthe back-end Ethernet switches" on the facing page)

4. Install the server rails in the rack (see Step 4: "Install the Rails" onpage 31)

5. Mount the servers in the rack (see Step 4d: "Mount the server in therack" on page 37)

6. Connect the servers to the PDUs (see Step 5: "Connect the servers tothe PDUs" on page 38)

7. Connect the switches to the PDUs (see Step 6: "Connect the switchesto the PDUs" on page 39)

8. Install the perforated blanking plates in front of the Ethernet switches(see Step 7: "Install the perforated blanking plates" on page 40)

9. Connect the back-end Ethernet cables to the back-end Ethernetswitches (see Step 8: "Connect the back-end Ethernet cables to theback-end switches" on page 41)



What you do

10.Connect the back-end Ethernet cables to the servers (see Step 9:"Connect the back-end Ethernet cables to the servers" on page 42)

11.Reassemble the rack (see Step 10: "Reassemble the rack" onpage 42)

Note: The steps above are listed in the recommended order ofperformance. If some components are available before others, you can varythis order as needed. However, the fully assembled system should matchthe arrangement specified in the instructions in the remainder of thischapter.

Step 1: Prepare the rack

Optionally, to facilitate the system assembly, remove the doors and sidesfrom the rack.

Step 2: Install the PDUs

If the PDUs are not already installed in the rack, install them now. Attachthem to the vertical rails at the back of the rack, one on each side.

Step 3: Mount the back-end Ethernet switches

An HCP Anywhere system uses two Ethernet switches for the back-endnetwork. The front of each switch, where the Ethernet ports are located,faces the rear of the rack. The two back-end switches are connected to eachother by a purple Ethernet cable.

The picture below shows the two back-end switches mounted in a rack.

The following sections tell you what you need and what steps to take tomount the Ethernet switches in the rack.



What you do

For information about the Ethernet switches, see "Ethernet switches" onpage 24. For information on where in the rack to put the switches, see"Server and switch placement" on page 27.

What you need

To mount the Ethernet switches in the rack, you need:

• The mounting hardware that comes with each switch.

• The purple Ethernet cable.

• A #2 Phillips screwdriver.

• A cage-nut tool.

What you do

To mount an Ethernet switch in the rack:

1. Attach one mounting bracket to each side of the switch. To attach amounting bracket:

a. Position the bracket so that the side with the four holes lines up withthe three holes on the side of the switch and the side with the twoholes is flush with the front of the switch.

b. Use three of the small black screws to attach the bracket to theswitch.



What you do

2. On the cage rails, clip the four cage nuts to the top and bottom holes inthe rack unit in which you’re mounting the switch (two on the left andtwo on the right).

2. Position the switch in the rack so that the two holes in the bracket oneach side of the switch align with the holes with the cage nuts.

3. Using two of the silver screws on each side, attach the switch to the cagerails.

4. Use the purple Ethernet cable to connect the two switches to each other.Use port number 24 in each switch.

Step 4: Install the Rails

Continue the assembly by installing the server mounting rails.

Step 4a: Separate the inner and outer server rails

A server rail kit consists of two sets of inner and outer rails. The rails areuniversal; that is, each set of rails can be used for either the left or rightside of the server.



What you do

In a new server module rail kit, the inner rails are nested inside the outerrails. You need to separate them before you can attach the inner rails to theserver and the outer rails in the rack.

The figure below shows an inner rail nested inside an outer rail.

The figure below shows the inner and outer rails separated from each other.The outer rail is on top.



What you do

The word FRONT is stamped on the top and bottom lips of each outer rail atthe front of the rail. The word REAR is stamped on the top and bottom ofeach rail at the rear of the rail.

At the rear of each outer rail, the letter L is stamped on one lip and theletter R is stamped on the other lip. With the letter L facing up, the rail goeson the left side of the rack, when viewed from the front of the rack. With theletter R facing up, the rail goes on the right side of the rack.

To separate the inner and outer server rails:

1. Slide the inner rail out of the outer rail toward the front until it locks intoplace.

The inner part of the outer rail slides also slides out.



What you do

2. While pulling forward the white tab on the side of the inner rail thatfaces the outer rail, slide the inner rail forward to release it from theouter rail. Then slide the inner rail all the way out of the outer rail.

3. Slide the inner part of the outer rail back into the outer rail. To do this,while pressing down the metal tab on the inner part of the outer rail,slide the inner part toward the back to release it. Then slide the innerpart all the way back into the outer rail.

Step 4b: Attach the inner rails to the server

The two inner rails in the server rail kit attach to the sides of the server.Each rail can attach to either side of the server .



What you do

To attach an inner rail to a server:

1. Position the rail on the side of the server so that the white tab on the railfaces out and the studs on the server fit into the holes in the rail.

2. While pushing the rail against the server, slide the rail toward the backof the server until the rail locks into place.

Step 4c: Install the outer server rails in the rack

The two outer rails in the server rail kit attach to the sides of the rack. Eachrail can attach to either side of the rack.

The outer rails are installed in the lower of the two rack units the server willoccupy. For example, if the server will occupy rack units 15 and 16, theouter rails are installed in rack unit 15.



What you do

To install an outer rail in the rack:

1. At the rear of the rack, with the inside of the outer rail facing into therack, align the two square studs at the rear of the rail with the back ofthe top and bottom square holes for the applicable rack unit in cage rail.

2. Fit the studs into the holes in the cage rail and pull the outer rail towardthe rear of the rack until the back of the outer rail locks into place.



What you do

3. At the front of the rack, align the two square studs at the front of theouter rail with the back of the top and bottom square holes for theapplicable rack unit in cage rail.

4. Fit the studs into the holes in the cage rail and pull the outer rail towardthe front of the rack until the front of the outer rail locks into place.

Step 4d: Mount the server in the rack

To mount a server in a rack:

1. Ensure that the inner part of each outer rail for the server is pushed allthe way back into the rack.



What you do

2. At the front of the rack, align the rear of the inner rails on the serverwith the front of the outer rails on the rack.

3. Fit each inner rail into the inside of the inner part of the correspondingouter rail. Then push the server back into the rack as far as it goes.

4. While pushing back or pulling forward the purple tabs on the outsides ofboth inner rails on the server, push back on the server to release it. Thenslide the server all the way back into the rack.

5. Using the #1 Phillips screwdriver, screw in the black locking screw belowthe handle on each side of the front of the server.

Step 5: Connect the servers to the PDUs

Each server connects to two PDUs — one on the left side of the rack and oneon the right.



What you do

When connecting the servers to the PDUs, start with the bottom server.Connect the first server to the bottommost of the receptacles you plan touse. Connect the second server to a receptacle above the one you used forthe first server. The receptacles you use do not need to be contiguous. Ifpossible, connect the servers to different circuit breakers on each PDU.

Reserve one receptacle in each PDU for connecting the back-end switches.

What you need

To connect the servers to the PDUs, you need two power cords for eachserver. For information on the type of power cords you need, see "Powercords" on page 26.

What you do

To connect the servers to the PDUs, for each server:

1. Connect a power cord from the left socket in the server to a receptacle inthe PDU on the left side of the rack.

2. Use the cable clamp on the server to secure the cable to the server.

3. Connect a power cord from the right socket in the server to a receptaclein the PDU on the right side of the rack.

4. Use the cable clamp on the server to secure the cable to the server.

Step 6: Connect the switches to the PDUs

Each Ethernet switch connects to one PDU. In the PDUs, you use thereceptacles you reserved in Step 5: "Connect the servers to the PDUs" onthe previous page.

What you need

To connect the switches to the PDUs, you need one power cord for eachswitch. For information on the type of power cords you need, see"Components that you supply for a rackless system" on page 26.



What you do

What you do

To connect the switches to the PDUs:

1. Connect a power cord from the bottom back-end switch to the PDU onthe right side of the rack.

2. Connect a power cord from the top back-end switch to the PDU on theleft side of the rack.

Step 7: Install the perforated blanking plates

Two perforated blanking plates cover the front of the rack units where theEthernet switches are installed.

The following sections tell you what you need and what steps to take toinstall the perforated blanking plates in the rack.

What you need

To install the perforated blanking plates in the rack, you need:

• For each blanking plate, two screws and two cage nuts from the rackaccessory kit

• A #2 Phillips screwdriver

• A cage-nut tool



What you do

What you do

To install a perforated blanking plate in the rack:

1. On each of the front vertical cage rails, clip one of the cage nuts into themiddle hole for the applicable rack unit.

2. Using two of the screws, secure the blanking plate to the rack.

Step 8: Connect the back-end Ethernet cables to the back-endswitches

The red Ethernet cables connect to the top back-end switch. The blue back-end Ethernet cables connect to the bottom back-end switch.

This picture shows the back-end cables connected to the back-end switches.

To connect the back-end Ethernet cables to the back-end switches:

1. Connect the two red cables to ports 1 (one) and 2 in the top back-endswitch.

2. Connect the two blue cables to ports 1 (one) and 2 in the bottom back-end switch.



What you do

Step 9: Connect the back-end Ethernet cables to the servers

One red back-end Ethernet cable and one blue back-end Ethernet cableconnect to each server. The red cables connect to port number 4 on eachserver. The blue cables connect to Ethernet port number 2 on each server.

The following sections tell you what you need and what steps to take toconnect the back-end Ethernet cables to the servers.

What you need

To connect the back-end Ethernet cables to the servers, you need Velcrostraps and/or cable ties for bundling and securing cables.

What you do

To connect the back-end Ethernet cables to the servers:

1. Connect the red cable in Ethernet port number 1 in the top back-endswitch to Ethernet port number 4 on the bottom server.

2. Connect the red cable in Ethernet port number 2 in the top back-endswitch to Ethernet port number 4 on the top server.

3. Connect the blue cable in Ethernet port number 1 in the bottom back-end switch to Ethernet port number 2 on the bottom server.

4. Connect the blue cable in Ethernet port number 2 in the bottom back-end switch to Ethernet port number 2 on the top server.

Step 10: Reassemble the rack

Using Velcro straps and/or cable ties, bundle any excess length of theEthernet cables and power cords and secure them to the rack. Then replacethe doors and sides on the rack if you had previously removed them.



What you do

Connecting and configuring HCPAnywhere at your site

To get the HCP Anywhere system up and running in your environment, youneed to make the external physical connections and reconfigure the systemfor your computing environment. For both preassembled and rackless HCPAnywhere systems, you need to:

• Connect the PDUs to the power sources

• Change the DNS, time, and network settings from the default settingsto settings that work for your environment

• Connect the system to your corporate network

• Verify that the serial number displayed in the Management Consolematches the serial number on the label shipped with the system

• Install the license files from the license CD that was shipped with thesystem components

This chapter provides instructions for these activities.

Chapter 4: Connecting and configuring HCP Anywhere at your site 43


4

Connecting to the power sources

Each node in an HCP Anywhere system is connected to two PDUs. Theswitches are each connected to one PDU.

You need to connect each PDU to a different power source at your site. Ifpossible, these should be uninterruptible power sources (UPSs).

Important: Before connecting the PDUs in a preassembled system to thepower sources, ensure that all the power cables connecting the systemcomponents to the PDUs are firmly seated at both ends. These cansometimes come loose during shipping.

Once you’ve connected the PDUs to the power sources, you can power onthe nodes. The switches power on automatically when the PDUs areconnected to the power sources.

Reconfiguring the HCP Anywhere system for your site

The HCP Anywhere system comes delivered with default network, DNS, andtime settings. You need to change these settings to match your computingenvironment.

To change these settings, you use the HCP Anywhere Management Console.You can change them in any order.

Important: This section describes activities to be performed when youfirst set up the HCP Anywhere system at your site. Before performing theseactivities at any other time, consult your authorized HCP Anywhere serviceprovider.

44 Chapter 4: Connecting and configuring HCP Anywhere at your site


Connecting to the power sources

What you need to know

Before you can reconfigure the system, you need to know:

• The DNS settings to use. Specifically:

¡ The DNS name you specified for the HCP Anywhere system in thecorporate DNS setup.

If you have not yet configured HCP Anywhere as a hostname in thecorporate DNS setup, do so now. Be sure to use your site-specificnode IP addresses and HCP Anywhere system name, not the defaultsettings that the system arrives with.

¡ The IP addresses of all your corporate DNS servers. Specifying allservers ensures that the HCP system can perform DNS lookups aslong as at least one of those servers is available.

Important: For AD authentication to work, HCP Anywhere must beable to contact at least one DNS server that can resolve the ADdomain name.

• The time settings to use. Specifically:

¡ The IP addresses or hostnames of the external time servers you wantto use.

Important: For AD authentication to work, the AD time must be insync with the HCP Anywhere system time. The recommendedconfiguration is for HCP Anywhere and AD to use the same timeserver.

¡ The time zone you want HCP Anywhere to use. HCP Anywhere storesall times in Coordinated Universal Time (UTC) and uses its time zonesetting only for presentation purposes.




• The network settings to use. Specifically:

¡ The front-end IP address to use for each HCP Anywhere node and thesubnet mask for those IP addresses.

The default front-end IP addresses for the HCP Anywhere nodes are192.168.100.101 and 192.168.100.102. If these IP addresses don’twork for your computing environment, you need to change thembefore you connect the HCP Anywhere nodes to your corporatenetwork.

¡ The IP address to use for the front-end gateway router. Typically, thefirst three octets in this address are the same as the first three octetsin the IP address of the front-end network.

¡ If the default back-end subnet for the HCP Anywhere nodes conflictswith an existing IP subnet at your site, the private back-endIP subnet for HCP Anywhere to use.

Important: This subnet is used only for internode communication.It must not be connected to the corporate network, which is used forother types of data communication at your site.

The default back-end IP subnet for the HCP Anywhere nodes is10.238.1.0.

¡ The maximum packet size, in bytes, to use for the front-endnetwork. The options are 1500 and 9000.

Preparing to reconfigure the system

To reconfigure an HCP Anywhere system for your computing environment,you need to first:

1. Connect a client computer to the HCP Anywhere default back-endnetwork (see Step 1: "Connect to the HCP Anywhere default back-endnetwork" on the facing page)

2. Log into the Management Console with the initial user account (see Step2: "Log in with the initial user account" on the facing page)

3. Check the health of the HCP Anywhere system (see Step 3: "Check thehealth of the HCP Anywhere system" on page 48)




Step 1: Connect to the HCP Anywhere default back-end network

For you to use the HCP Anywhere Management Console, you need a clientcomputer with connectivity to the default back-end subnet to which theHCP Anywhere nodes belong. To connect a client computer to this subnet:

1. Ensure that the client computer has a physical connection to one of theback-end switches used by the HCP Anywhere system.

2. If the client computer is not in the HCP Anywhere default back-endsubnet:

a. Make a note of the current IP address and subnet mask for the clientcomputer so you can reset them after you change the networksettings for the HCP Anywhere system.

b. On the client computer, set the IP address for the local area networkto 10.238.1.100.

c. On the client computer, set the subnet mask to 255.255.255.0.

Step 2: Log in with the initial user account

To log into the HCP Anywhere Management Console for the first time:

1. On a computer connected to the HCP Anywhere back-end network, opena browser window.

2. In the address field, enter:

https://10.238.1.1:8000

The IP address in this URL is the preconfigured back-end IP address ofone of the nodes in the HCP Anywhere system.

3. When prompted, accept the HCP SSL server certificate temporarily forthe current session.

The HCP Anywhere Management Console login page appears.

If the browser cannot find the Management Console login page, wait afew minutes; then try again.

If the login page still doesn’t open after a few minutes, please contactyour authorized HCP Anywhere service provider for help.




4. In the Username field, type this case-sensitive username: admin

5. In the Password field, type this case-sensitive password: Chang3Me!

6. Click on the Log In button.

The Console displays the Change Password page.

7. On the Change Password page:

¡ In the Existing Password field, type: Chang3Me!

¡ In the New Password field, type a new password for the adminaccount.

Passwords can be up to 64 characters long, are case sensitive, andcan contain any valid UTF-8 characters, including white space. Theminimum password length is six characters.

To be valid, a password must include at least one character from twoof these three groups: alphabetic, numeric, and other.

¡ In the Confirm New Password field, type the new password again.

Important: Remember this password. In case of an AD failure, theManagement Console is accessible only by the admin user account.

8. Click on the Update Password button.

Step 3: Check the health of the HCP Anywhere system

To ensure that the HCP system is running properly:

1. In the top-level menu in the HCP Anywhere Management Console,mouse over System to display a secondary menu.

2. In the secondary menu, click on Hardware.

3. On the Hardware page, for each node, check that the node status isAvailable.

If both nodes are available, you can safely continue with the HCPAnywhere system reconfiguration.




If either node has a status other than Available, please contact yourauthorized HCP Anywhere service provider for help.

Reconfiguring the system

To reconfigure the system, you use the Configuration page in theManagement Console. You cannot make changes on this page if one of theHCP Anywhere nodes is unavailable.

To change network, DNS, and time settings for an HCP Anywhere system:


2. In the secondary menu, click on Configuration.

3. On the Configuration page, click on Network and Time.

4. On the Network and Time panel, in the DNS section:

¡ In the System Name field, type the fully qualified DNS name for thesystem. This name can contain only lowercase letters, numbers, andhyphens (-). Additionally, it must consist of at least three segments,separated by periods (.). This name cannot exceed 253 characters.

¡ In the DNS Servers field, type a comma-separated list of the IPaddresses of all the current corporate DNS servers. Spaces areallowed.

Important: When you change the DNS name of the HCP Anywheresystem, the system will need a new SSL certificate. For informationon changing the SSL certificate for the system, see the HCPAnywhere Administrator Help.

5. In the Time Settings section:

¡ In the Time Servers field, type the IP addresses or hostnames of oneor more time servers. Use commas to separate multiple IP addressesand hostnames.

¡ In the Time Zone field, select a new time zone.




6. In the Network Settings section:

¡ In the Default Gateway field, type the new gateway router IP addressfor the front-end network.

¡ In the Front-end Netmask field, type the new front-end subnet maskfor each node.

¡ In the Front-end MTU field, select the maximum packet size, inbytes, for the front-end network. The options are 1500 and 9000.

¡ In the Back-end Subnet field, type the new back-end IP subnet. Youneed to change this only if the default back-end subnet conflicts withan existing subnet at your site.

¡ In the IP Addresses section, in the Front-end IP field for each node,type the new front-end IP address for the node. Specify the lower IPaddress for node aw-01 and the higher IP address for node aw-02.

7. Click on the Update Settings button.

A warning message appears asking you to confirm the changes you’vemade.

8. In the field in the message window, type YES. This is case sensitive.


The Management Console checks to ensure that the settings youspecified are valid and that both nodes are available. If so, the HCPAnywhere system restarts with the new settings. This takes a fewminutes, during which the system is inaccessible to users andapplications.

Connecting to your corporate network

An HCP Anywhere system should be connected to your corporate networkthrough two front-end switches.

Important: The default front-end IP addresses for the HCP Anywherenodes are 192.168.100.101 and 192.168.100.102. If these IP addressesdon’t work for your computing environment, you need to change thembefore you connect the HCP Anywhere nodes to your corporate network. Forinformation on doing this, see "Reconfiguring the system" on theprevious page.




You need to supply two Ethernet switches and the Ethernet cables toconnect those switches to the system nodes. Each node in the systemshould be connected to both switches. Use cables of one color to connect thenodes to one of the switches and cables of another color to connect thenodes to the other switch. If possible, these cables should be colors otherthan red and blue. For more information on the switches and cables youneed to supply, see "Components that you supply" on page 20.

Note: Do not mount the switches you provide in the rack holding apreassembled HCP Anywhere system.

To connect the HCP Anywhere system to your corporate network:

1. Label each cable at both ends. Then connect the cables to the nodes andfront-end switches:

¡ Connect all the cables for one switch to port 1 (one) on each node.

¡ Connect all the cables for the other switch to port 3 (three) on eachnode.

¡ Connect the cables to the switches in sequential order by nodenumber. That is, connect node 1 to one port in each switch, thenconnect node 2 to another port.

The figure below shows these connections.

2. Bundle the cables separately for each switch and use cable ties to securethem to the rack. The cables should be secure but not strained orpinched.




After making the physical connections and reconfiguring network settingsfor the HCP Anywhere system, you can disconnect the client computer fromthe back-end switch and access the Management Console through yourcorporate network. To do this, enter the URL for the HCP AnywhereManagement Console in a browser window. The URL has this format:

https://hcp-anywhere-system-name.domain-name:8000/admin

For example, to access the Management Console for the HCP Anywheresystem named anywhere-ma, you would use this URL:

https://anywhere-ma.example.com:8000/admin

Verifying the serial number

Each HCP Anywhere system is assigned a unique five-digit serial number.For a preassembled HCP Anywhere system, this number is on a label that’sattached to the bottom of the system rack, just inside the rear doors. For arackless HCP Anywhere system, this number is on a label that's taped to thetop of one of the servers.

When the HCP Anywhere system software is installed, the serial number isentered as part of the system configuration. You need to verify that theserial number in the system configuration matches the serial number on thelabel delivered with the system.

You use the Management Console to view the serial number configured forthe system. The serial number is displayed in the top and bottom righthandcorners of each Console page.

If the serial number displayed in the Console doesn't match the one fromthe label, contact your authorized HCP Anywhere service provider.

Installing license files

By default, the HCP Anywhere system supports only a few filesynchronization and sharing users and HDI devices. To increase one or bothof these limits, you need to install the license files from the license CD thatwas delivered with the system.



Verifying the serial number

The filenames for HCP Anywhere license files have this format:

HCPAWLic_SNserial-number_Qquote-number-for-license-purchase_[FSS|HDI]_Nquantity.[bin|plk]

For example, this license file was purchased as part of quote number123456 and increases the limit of registered file synchronization andsharing users to 500 for the HCP Anywhere system with the serial number00001:

HCPAWLic_SN00001 _Q123456_FSS_N500.plk

Important: Before installing license files, you need to verify the serialnumber for the system. For information on doing this, see "Verifying theserial number" on the previous page.

To install a license file:

1. Insert the license CD into the CD drive on the client computer.


3. In the secondary menu, click on Upgrades/Licenses.

4. On the Upgrades and Licenses page, on the Upload tab, click on theBrowse button.

5. Navigate to the license file on the CD and select the file.

6. Click on the Upload button.

The Management Console uploads the file. The progress bar displays theprogress of the upload.



Installing license files

7. Click on the Next button.

The Review details and apply tab opens and displays this informationabout the file you uploaded:

¡ A description of the file.

¡ In the Details section:

– The type of file you uploaded. That is, License.

– The number of file synchronization and sharing users or in-service HDI devices that the license allows.

At this point, the file has been stored in the system but not applied.That is, the file synchronization and sharing user or HDI device limitshave not been increased. The system can store only one license file at atime. If you upload a new license file before applying the current one,the current license file is replaced.

8. Click on the Apply License button.

A warning message appears asking you to confirm that you want toapply the license to the HCP Anywhere system.

9. In the field in the message window type YES. This is case sensitive.

10.Click on the Apply button.

The system begins installing the license. The progress bar displays theprogress of the installation.

Performing additional configuration activities

After installing the license files and configuring the system for yourcomputing environment, you need to perform some additional configurationactivities to grant access to users and to enable the file synchronization andsharing and HDI device management features.

For information on performing these activities, see the HCP AnywhereAdministrator Help, which is accessible from the documentation control ( )in the top righthand corner of each Management Console page.



Performing additional configuration activities

Configuring monitoring with Hi-TrackMonitor

Hi-Track Monitor is an HDS product that allows you to remotely monitor thenodes in an HCP Anywhere system. With Hi-Track Monitor, you can view thestatus of these components in a web browser. You can also configure Hi-Track Monitor to notify you by email of error conditions as they occur.Additionally, you can configure Hi-Track Monitor to report error conditionsto HDS support personnel.

Hi-Track Monitor is for monitoring and error notification purposes only. Itdoes not allow any changes to be made to the system. Hi-Track Monitor isinstalled on a server that is separate from the HCP Anywhere system. Theprogram uses SNMP to retrieve information, so SNMP must be enabled inHCP Anywhere.

This chapter explains what you need to know to set up monitoring of HCPAnywhere nodes with Hi-Track Monitor. The chapter assumes that Hi-TrackMonitor is already installed and running according to the documentationthat comes with the product.

Note: For you to monitor HCP Anywhere with Hi-Track Monitor, the Hi-Track Monitor system must be at release 6.1 or later.

Chapter 5: Configuringmonitoring with Hi-Track Monitor 55


5

Enabling SNMP in HCP Anywhere

For Hi-Track Monitor to work with HCP Anywhere, you need to enable SNMPin the HCP Anywhere Management Console. HCP Anywhere supports SNMPversion 2c.

By default, Hi-Track Monitor is configured to support SNMP version 2c withthe community name public. If you change the community name inHCP Anywhere, you need to configure a new SNMP user in Hi-Track Monitorto match what you specify in HCP Anywhere. For more information on this,see the Hi-Track Monitor documentation.

For instructions on logging into the Management Console with the adminuser account, see Step 2: "Log in with the initial user account" onpage 47.

To enable SNMP in HCP Anywhere for use with Hi-Track Monitor:

1. In the top-level menu in the Management Console, mouse over Systemto display a secondary menu.

2. In the secondary menu, click on Monitoring.

3. On the Monitoring page, click on SNMP.

4. In the SNMP Settings section:

¡ Select the Enable SNMP at snmp.hcp-anywhere-name.domain-nameoption.

¡ Optionally, in the Community field, type a different communityname.


Tip: By default, the HCP Anywhere system allows SNMP monitoringthrough any IP address. However, you can explicitly specify that Hi-Track Monitor is allowed access to HCP Anywhere through SNMP. To dothis:

1. In the entry field in the Allow section, type the IP address of theserver on which Hi-Track Monitor is installed.

2. Click on the Add button.

56 Chapter 5: Configuringmonitoring with Hi-Track Monitor


Enabling SNMP in HCP Anywhere

3. Log out of the Management Console and close the browser window.

Configuring Hi-Track Monitor

To configure Hi-Track Monitor to monitor the nodes in the HCP Anywheresystem, log into the Hi-Track Monitor and add HCP Anywhere as a newdevice. You need this information:

• Your HDS customer ID. If you don’t know it, contact your authorizedHCP Anywhere service provider for help.

• The front-end IP addresses of the nodes in the HCP Anywhere system.

• The SNMP user that corresponds to the SNMP configuration in HCPAnywhere. Typically, this is public.

For information on configuring SNMP in HCP Anywhere, see "EnablingSNMP in HCP Anywhere" on the previous page.

For information on adding devices to Hi-Track Monitor, see the Hi-TrackMonitor documentation.

Chapter 5: Configuringmonitoring with Hi-Track Monitor 57


Configuring Hi-Track Monitor

58 Chapter 5: Configuringmonitoring with Hi-Track Monitor


AActive Directory 9activities, final on-site setup 6architecture, system 5

Bback-end cables

connecting 41-42rackless system components 22

back-end Ethernet ports 23-24back-end network

about 4accessing 47

back-end subnet, changing 50back-end switches

about 24-25connecting Ethernet cables 41mounting in rack 29-31

blanking platesabout perforated 26installing perforated 40-41

Cchecking health of HCP Anywhere system 48-

49components

customer-supplied for racklesssystems 26-27

customer supplied for front-endnetwork 20

shippedwith rackless systems 22-23configuring

DNS settings 49-50network settings 49-50time settings 49-50

cooling 8current draw 8

Ddefault back-end IP subnet 46, 50default IP addresses for nodes 50DNS

configuring settings 49-50HCP Anywhere in corporate 9

DNS settingsabout reconfiguring 45reconfiguring 49-50

Eenabling SNMP 56Entry Pod 3environmental requirements

HCP 8HCP Anywhere 8

Ethernet ports 23-24

Ffile synchronization and sharing, about 2firewall, information for configuring 10-19front-end Ethernet ports 23-24front-end gateway, changing 50front-end IP addresses, default 50front-end network

about 4components you supply 20

front-end switches, about 4

Hhardware

networking 5nodes 2overview 4-5

hardware assemblycomponents you supply 26-27tools needed 27-28

Index

Index 59


HCP Anywhere

HCP Anywhere 56about 2checking system health 48-49DNS requirements 9enabling SNMP 56file synchronization and sharing 2hardware 4-5HDI device management 2in corporate DNS 9in virtual machine 1Management Console 2network connection information 10-19physical system types 3server and switch placement 27system architecture 5user authentication 9verifying serial number 52

HDI device management, about 2Hi-Track Monitor

about 55enabling SNMP for HCP Anywhere 56

Lload balancer, information for configuring 10-

19logging into Management Console 47-48

MManagement Console

about 2logging in 47-48

mounting switches 29-31

NNAS servers, network connection

information 19network settings

about reconfiguring 46reconfiguring 49-50

networking, about 5nodes

about 2front-end network connections 4

Pperforated blanking plates

about 26installing 40-41

physical system types 3placement, servers and switches 27

pod 2ports, Ethernet 23-24power cords

about 26connecting to servers 38-39connecting to switches 39-40

power draw 8preassembled systems, about 1preparing site for installation 7

QQuanta D51B-2U server

about 23-24cooling 8current draw 8Ethernet ports 23power draw 8weight 8

Rrack

preparing for HCP Anywhere installation 29reassembling after HCP Anywhere

installation 42requirements for customer supplied 26

rackless systemsabout 1components 22-23customer-supplied components 26-27server and switch placement 27

rails, serverabout 24

requirementsenvironmental 8reconfiguring network and time

settings 45-46time source 10

Sserial number label

location 22serial number, verifying 52server rails

about 24servers

about mounting hardware 24connecting to PDUs 38-39

site preparation 7SNMP, enabling 56Standard Pod 3

60 Index


weight

switchesabout 25about back-end 24-25about front-end 4connecting back-end cables 41connecting to PDUs 39-40mounting hardware 25mounting in rack 29-31

system, architecture 5

Ttime settings

about reconfiguring 45reconfiguring 49-50

time source requirements 10tools for hardware assembly 27-28types of physical systems 3

Uuser authentication requirements 9

VVM systems 1

Wweight

servers 8switches 8

Index 61


62 Index


MK-HCPAW005-07

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2627U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0) 1753 [email protected]

Asia Pacific+852 3189 [email protected]

http://www.hds.com/

http://[email protected]/



installing an hcp anywhere system final on-site setup anywhere managementconsole. accesstoactive...

Documents