deploying an hcp anywhere vm system - hitachi …hcp...

Hitachi Content Platform AnywhereDeploying an HCPAnywhere VM System

MK-HCPAW011-02

© 2014, 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.

Hitachi Data Systems Corporation reserves the right to make changes to this document at any timewithout notice and assumes no responsibility for its use. This document contains the most currentinformation available at the time of publication. When new or revised information becomes available, thisentire document will be updated 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 Corporation at https://portal.hds.com.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions ofthe applicable Hitachi Data Systems agreement. The use of Hitachi Data Systems products is governed bythe terms of your agreement 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, RS/6000, 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 website are properties oftheir respective owners.

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Notice Export Controls. The technical data and technology inherent in this Document may be subject toU.S. export control laws, including the U.S. Export Administration Act and its associated regulations, andmay be subject to export or import regulations in other countries. Reader agrees to comply strictly with allsuch regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, orimport the Document and any Compliant Products.

https://portal.hds.com/

Contents

Preface viiIntended audience viiProduct version viiWhat's new viiRelated documents ixGetting help ixComments x

Chapter 1: HCPAnywhere system overview 1About HCP Anywhere 2Management Console 2System components and architecture 2System availability and failover management 5Monitoring HCP Anywhere 5

Chapter 2: Site preparation 7ESXi host requirements 8VMware product requirements 8Virtual machine requirements 9Storage requirements 9Supported VMware features 11Unsupported VMware features 11Network requirements 11Network connection information 12User authentication requirements 20Time source requirements 21System availability recommendations 21

Deploying an HCP Anywhere VM System

iiiContents

Chapter 3: Creating and configuring the virtual machines 23Information you need 24Resources you need 25Step 1: Log into vSphere Web Client 25Step 2: Conditionally, add ESXi hosts 26Step 3: Specify time settings for the ESXi hosts 26Step 4: Create the datastores 28Step 5: Configure the networks 30

Step 5a: Conditionally, configure the front-end network 30Step 5b: Create the back-end network 32

Step 6: Create the virtual machines 34Step 6a: Unpack the virtual machine image file 34Step 6b: Deploy the OVF template 34

Step 7: Conditionally, reconfigure each virtual machine 37Step 7a: Reconfigure CPU and memory 38Step 7b: Conditionally, add hard disks 39Step 7c: Conditionally, reconfigure hard disks 41Step 7d: Configure the other virtual machine 42

Step 8: Start the virtual machines 43

Chapter 4: Installing and configuring the HCP Anywhere software 45Information you need 46Configuring network settings for each HCP Anywhere node 46

Step 1: Log in for the network configuration 47Step 2: Configure front-end network settings 49Step 3: Configure back-end network settings 51Step 4: Apply the changes 52Step 5: Configure network settings for the other node 52

Installing the HCP Anywhere software 52Performing the HCP Anywhere software installation 53Step 1: Log in for the installation 53Step 2: Configure the HCP Anywhere system 55Step 3: Verify the system configuration 62Step 4: Execute the installation 62

Verifying the HCP Anywhere installation 63Logging into the Management Console 66After installing the software 67

Appendix A: Adding ESXi hosts 69Information you need 70Adding the hosts 70

iv Contents


Appendix B: Forms 73Virtual Machine Creation Information 74HCP Anywhere Software Installation Information 75

Glossary 77

Index 83

vContents


vi Contents


Preface

This book is the setup guide for Hitachi Content Platform Anywhere (HCPAnywhere) VM systems. It provides all the information you need to deploya virtualized HCP Anywhere system in your VMware vSphere®environment.

Note: This book does not explain how to configure Hi-Track Monitor tomonitor the nodes in the HCP Anywhere system. For that information, seeInstalling an HCP Anywhere System — Final On-site Setup.

Intended audience

This book is intended for the people responsible for deploying an HCPAnywhere VM system at a customer site. It assumes you have experiencewith computer networking, creating virtual machines, familiarity withVMware products and concepts, and a basic understanding of HCPAnywhere systems.

Product version

This book applies to release 2.0 of HCP Anywhere.

Important: To be installed in virtual machines, the HCP Anywhere softwaremust be at release 1.2 or later. Earlier versions are not supported and notknown to work in virtual machines.

What's new

This section describes the new features, product enhancements, and otherchanges for this version of the document.


Preface vii

Support for accessing network shares from HCP AnywhereAdministrators can now use HCP Anywhere to grant users access to networkshares on CIFS servers in their organization's network. Users can work withthe contents of these shares from the User Portal and from their mobiledevices.

Administrators use the Management Console to make CIFS servers andshares known to the HCP Anywhere system. For information on doing this,see the HCP Anywhere Administrator Help.

For information on the network connections necessary to support thisfeature, see "Network connection information" on page 12.

VM system sizing recommendationsThis book has been updated to include infrastructure sizingrecommendations for creating HCP Anywhere VM systems that supportanywhere from 1 to 50,000 users. Previously, sizing recommendations wereprovided only for systems supporting 5,000 or 20,000 users.

For more information, see "Storage requirements" on page 9 and "Virtualmachine requirements" on page 9.

VM environment requirementsThe virtualization infrastructure requirements for HCP Anywhere have beenrevised. For information, see "Chapter 2: Site preparation" on page 7.

Support for VMware DRS and vMotionHCP Anywhere VM systems now support the VMware Distributed ResourceScheduler (DRS) and vMotion features.

Support for new HDI device typesIn release 2.0, HCP Anywhere can now configure and monitor HDI SingleNode and virtual machine devices. Administrators can also use theManagement Console to add support for new device types, as necessary.

For information on managing HDI devices, see the HCP AnywhereAdministrator Help.

What's new

Prefaceviii


Related documents

These documents contain 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.

• Installing an HCP Anywhere System – Final On-site Setup— Thisbook contains instructions for deploying an assembled and configuredphysical HCP Anywhere system at a customer site. It explains how tomake the necessary physical connections and reconfigure the system forthe customer computing environment. It also contains instructions forconfiguring Hi-Track® Monitor to monitor an HCP Anywhere system.

• 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.

Getting help

The Hitachi Data Systems customer support staff is available 24 hours aday, seven days a week. If you need technical support, log on to the HitachiData Systems Portal for contact information: https://portal.hds.com.

Related documents

Preface ix


https://portal.hds.com/

Comments

Please send us your comments on this document:

[email protected]

Include the document title, number, and product version number, and referto specific sections and paragraphs whenever possible. All commentsbecome the property of Hitachi Data Systems.

Thank you!

Comments

Prefacex


mailto:[email protected]

HCP Anywhere system overview

This chapter introduces HCP Anywhere and describes the architecture for anHCP Anywhere system installed in a VMware vSphere environment.


1

1

Chapter 1: HCP Anywhere system overview

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 to accessand share files from any location at which the user has Internet access.

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 that havebeen 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 the Management Console.The HCP Anywhere system administrator uses this Console to configure,monitor, and manage the system.

System components and architecture

This section describes the components and architecture of an HCPAnywhere VM system.

NodesAn HCP Anywhere VM system consists of two virtual machines, callednodes. Ideally, the nodes run on two separate ESXi hosts. The nodes runthe HCP Anywhere software and are the essential parts of the system.

About HCP Anywhere

Chapter 1: HCP Anywhere system overview2


NetworksAn HCP Anywhere system uses both back-end and front-end networks. Thefront-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, and remainseparate from the front-end network. Interfering with the operation of theback-end network can cause the HCP Anywhere system to become inoperableand can result in data loss.

StorageAn HCP Anywhere VM system relies on the VMware infrastructure to providestorage. Each virtual machine must be configured to use a datastore. Theunderlying storage for the datastore can be provisioned on the hoststhemselves or in a location external to the hosts.

Each node uses its datastore for storing the HCP Anywhere software,operating system, and database. The HCP Anywhere database contains thisdata:

• Information about file synchronization and sharing users and theirregistered devices

• Information about the files that users have stored in HCP Anywhere (butnot the contents of those files)

• Information about the HDI devices that HCP Anywhere manages

• Records of events that have occurred in the system

The contents of files added by users are stored in an HCP system.


Chapter 1: HCP Anywhere system overview 3


System architectureThe illustration below shows the architecture of an HCP Anywhere VMsystem.

In this diagram:

• The dashed lines represent the connections from the datastores to thelocations of the underlying storage.

• Internal Storage represents a storage location on the host itself.

• External Storage represents a storage location that has been provisionedoutside of the host using a method such as NFS or SAN.

• The solid lines represent the network connections from the hosts to theinfrastructure for the front-end and back-end networks.




System availability and failover management

Each node runs the complete HCP Anywhere software and also stores a copyof the HCP Anywhere database. The database, which contains essentialsystem data, is maintained by one node and copied to the other.

If a node becomes unavailable, HCP Anywhere detects the outage andinitiates a failover. During a failover, the available node automaticallybegins maintaining the database. This means that even when one of thenodes is unavailable, users can continue to access and use the system.

Important: The HCP Anywhere system initiates a failover if one of the virtualmachines is paused. After being resumed, the virtual machine may takeseveral minutes to begin performing HCP Anywhere operations again.

Note: VMware vSphere provides a number of features that provide highavailability and failover management. HCP Anywhere has not been fully testedwith all of these features. Some may work with HCP Anywhere but others willnot. For more information, see "Supported VMware features" on page 11.

Monitoring HCP Anywhere

The HCP Anywhere Management Console provides tools for monitoring thehealth and activity of the HCP Anywhere system. These tools include graphsthat display an overview of system activity, a system log that allows you tomonitor system activity on a more detailed level, and an internal log thatcan be used by HCP Anywhere support personnel for diagnosing andresolving problems.

For information on using these tools to monitor the HCP Anywhere software,see the HCP Anywhere Administrator Help, which is accessible from thedocumentation control ( ) in the top righthand corner of eachManagement Console page.

When running in a virtualized environment, HCP Anywhere does not provideany tools for monitoring the underlying ESXi hosts or other physicalhardware. The customer must provide the tools for monitoring thisequipment.

System availability and failover management

Chapter 1: HCP Anywhere system overview 5


Monitoring HCP Anywhere



Site preparation

Before an HCP Anywhere VM system can be deployed, you need to ensurethat your virtualization infrastructure meets certain requirements. If itdoesn't, you should wait to deploy the system until the necessary changeshave been made.

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 requirements and recommendations forsuccessful installation and operation of an HCP Anywhere VM system at yoursite.


7

2

Chapter 2: Site preparation

ESXi host requirements

The ESXi hosts you provide must have ESXi version 5.1 Update 2 or laterinstalled. HCP Anywhere virtual systems have been qualified for use withESXi version 5.1 Update 2 and ESXi version 5.5.

Other ESXi versions may work but have not been formally tested.

VMware product requirements

The following VMware products are supported for setup and management ofan HCP Anywhere VM system:

• VMware vCenter Server version 5.1 or 5.5

• VMware vSphere Web Client version 5.1 or 5.5

HCP Anywhere VM has not been tested with any other versions of VMwarevCenter or vSphere.

ESXi host requirements

Chapter 2: Site preparation8


Virtual machine requirements

Each virtual machine requires a certain number of CPUs and a certainamount of memory. These amounts are determined by the number of usersthe system can support:

Potential number of users CPUs Memory

1-100 4 4 GB

101–200 4 6 GB

201–500 4 8 GB

501–1000 4 10 GB

1001–2000 4 16 GB

2,001–5,000 6 32 GB

5,001–20,000 16 128 GB

20,001-50,000 16 256 GB

Important:

• Do not overprovision the CPUs or memory on the ESXi hosts on which youare installing HCP Anywhere.

• The numbers of users in the table above represent how many users thesystem is capable of supporting. The number of users that can actuallyregister with the system is limited by the license that you've purchased.

Storage requirements

When deploying an HCP Anywhere VM system, you create one or moredatastores in which the HCP Anywhere virtual machines will store data.Before deploying the system, you need to provision the underlying storagefor the datastores.

Note: HCP Anywhere uses the storage you provision for storing its internaldata. An HCP system is required for storing user files.

Storage locationsYou can provision storage on the ESXi hosts themselves or use a methodsuch as NFS or SAN to provision storage in a location external to the hosts.

Virtual machine requirements

Chapter 2: Site preparation 9


Space requirementsThe total amount of space you need to provide depends on the number ofusers your system supports:

Potential number of users Space

1-100 91 GB

101–200 91 GB

201–500 91 GB

501–1000 253 GB

1001–2000 415 GB

2,001–5,000 901 GB

5,001–20,000 2.61 TB

20,001-50,000 5.47 TB

Important:

• HCP Anywhere must have access to the required amounts of free space. Donot overprovision the underlying storage for the datastores.

• HCP Anywhere does not support reprovisioning space after the system isinstalled. Before installing the system, you need to provision enough spacefor the maximum number of users that you expect your system willsupport.

• The numbers of users in the table above represent how many users thesystem is capable of supporting. The number of users that can actuallyregister with the system is limited by the license that you've purchased.

Creating datastoresYou use the VMware vSphere Web Client to create datastores. Forinstructions on creating datastores, see "Step 4: Create the datastores"on page 28.

Storage requirements



Supported VMware features

These VMware vSphere features or tools have been qualified for use withHCP Anywhere VM systems:

• vMotion

• Storage vMotion

• Distributed Resource Scheduler (DRS)

Note: When using this feature, you should make sure that the virtualmachines are never migrated to the same host. See the applicable VMwaredocumentation for information on configuring vSphere DRS.

• Storage DRS

Unsupported VMware features

These VMware vSphere features or tools have not been tested and are notsupported with HCP Anywhere:

• VMware HA

• Fault Tolerance

• Snapshots. (Specifically, HCP Anywhere does not support rolling back toa snapshot of an HCP Anywhere virtual machine.)

Network requirements

Each HCP Anywhere virtual machine requires connectivity to two networks:

• A front-end network, which allows users, administrators, and theirdevices to connect to the system.

• A back-end network, which enables the nodes to communicate with eachother. This must be a private, non-routable network.

You need to set up these networks at your site before deploying the HCPAnywhere virtual machines.

Supported VMware features



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 process inwhich 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.

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

Tip: Even when you have enabled SSL termination support for the HCPAnywhere system, you should configure the HCP Anywhere system to use anSSL certificate that's been signed by a trusted vendor. This increases thelikelihood 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.




PurposeInboundor

OutboundSource

SourceNetwork

Target Port ProtocolOptionalor

requiredNotes

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 external SSLtermination for filesynchronization andsharing and HDI devicemanagement featurecommunication, HCPAnywhere uses port 80for HTTP access withoutSSL security. Allreturned URLs useHTTP with SSL security(HTTPS).

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

13Chapter 2: Site preparation



PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

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 HCPAnywhere ManagementConsole, HCP Anywhereuses only port 443 forfile synchronization 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)




PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

SNMP access formonitoring the HCPAnywhere system

Inbound NetworkMonitoringSystem (SNMP)


161 TCP, UDP Optional Support for SNMP canbe enabled and disabledin the ManagementConsole.

Hi-Track Monitor usesSNMP tomonitor theHCP Anywhere system.

HCP Anywhere supportsonly SNMP version 2c.

HCP Anywhere does notsend system logmessages to SNMPmanagers.

Active Directoryauthentication

Outbound HCP Anywheresystem

Corporate ActiveDirectoryserver

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

Support for ActiveDirectoryauthentication isconfigured in theHCP AnywhereManagement Console.

(continued)




PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

Access to ActiveDirectory LDAPservice



389 TCP, UDP Required HCP Anywhere uses theLightweight DirectoryAccess Protocol (LDAP)for user authenticationand for ensuring thatAW support forAD authenticationcontinues to function.

Maintaining thepassword for the HCPAnywhere computeraccount in ActiveDirectory



464 TCP, UDP Required HCP Anywhere uses theKerberos kpasswdservice to automaticallychange the passwordfor the HCP Anywherecomputer account inAD.

Access to MicrosoftGlobal Catalog



3268 TCP, UDP Required HCP Anywhere accessesthe Global Catalog forAD user authenticationand for ensuring thatAW support forAD authenticationcontinues to function.

DNS nameresolution


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

(continued)




PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

Access to externaltime server


Corporate NTP server 123 TCP, UDP Required HCP Anywhere requiresa time source that is anexternal NTP timeserver.

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 of HCPAnywhere events


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)




PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

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 uses theHCP Management APIto 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)




PurposeInboundor

OutboundSource

SourceNetwork


requiredNotes

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)




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 domain inthe forest. If your AD infrastructure does not allow HCP Anywhere to dothis, you can use the domain whitelist in the Management Console tospecify only the domains to which the system can connect. For information,see the HCP Anywhere Administrator Help, which is available from theManagement Console.

• 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 to communicatewith Active Directory Federation Services (AD FS). This allows HCP Anywhereto authenticate users from multiple AD forests. For more information, see theHCP Anywhere Administrator Help, which is accessible from the documentationicon ( ) in the top righthand corner of each Management Console page.

User authentication requirements



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.

System availability recommendations

To ensure system availability in the event of a hardware failure, each HCPAnywhere virtual machine should run on a separate host.

For additional information on maintaining the availability of virtualmachines, see the applicable VMware documentation.

Note: If you are using the vSphere Distributed Resource Scheduler (DRS)feature, you should configure the feature so that the HCP Anywhere virtualmachines are never migrated to the same host. See the applicable VMwaredocumentation for information on configuring vSphere DRS.

Time source requirements



System availability recommendations



Creating and configuring the virtualmachines

This chapter includes instructions for using the VMware vSphere Web Clientto connect to a vCenter Server and create the HCP Anywhere virtualmachines. This chapter also contains instructions for configuration activitiesyou need to perform in your VMware vSphere environment to support HCPAnywhere.

The instructions in this chapter explain how to set up HCP Anywhere in itsrecommended configuration. Depending on your vSphere environment,some of these steps may not apply. For more information on setting upvirtual machines, see the applicable VMware vSphere documentation.


23

3

Chapter 3: Creating and configuring the virtual machines

Information you need

In order to deploy an HCP Anywhere VM system, you need to know certaininformation about your vSphere environment and about the HCP Anywheresystem you are creating.

Tip: To make the deployment easier, use the Virtual Machine CreationInformation form on page 74 to record the information you need.

Number of usersYou need to know the number of users that the system will support. Thisdetermines how much storage, memory, and CPUs you need to allocate foreach virtual machine.

vSphere Web ClientIn order to access the vSphere Web Client, you need to know:

• The address for the vSphere Web Client on the vCenter server. Theaddress has this format:

http[s]://vcenter-ip-address-or-hostname:port/vsphere-client

By default, the port number is 9443.

• The username and password for an account with administrativepermissions for the vCenter server

Time serversFor each ESXi host, you need to know the hostnames or IP addresses of oneor more time servers for the host to use.

DatastoresYou need to create datastores for the virtual machines to use. You do this inthe vSphere Web Client by identifying storage locations that you havealready provisioned.

For more information about datastores, see the applicable VMware vSpheredocumentation.


Chapter 3: Creating and configuring the virtual machines24


Virtual networkingYou need to configure two virtual switches for each HCP Anywhere node. Todo this, you need to know which vmNICs on each host the virtual switchesshould use.

Virtual machinesTo deploy OVF template to create the HCP Anywhere virtual machines, youneed to know:

• The name to assign to each machine

• The name of the datastore in which to store data for the virtual machine

Resources you need

To create the virtual machines, you need the DVDs that contain the HCPAnywhere virtual machine images. You get these DVDs from the HCPAnywhere distributor.

Each DVD contains an image file. You choose one of these files dependingon how you want to configure the virtual disks for each virtual machine youcreate:

• AW012_VMDK-x.x.x.x.iso— This image automatically creates all the virtualdisks that the virtual machine requires. However, depending on thenumber of users your system will support, you may need to reconfigurethe sizes of the virtual disks.

• AW013_RDM-x.x.x.x.iso— This image creates only one of the requiredvirtual disks. For each virtual machine that you create using this file, youneed to manually create and configure two additional virtual disks.

Step 1: Log into vSphere Web Client

To log into the vSphere Web Client:

1. In a web browser, enter the address for the vCenter server.

The VMWare vSphere Web Client login page appears.

2. In the User name field, type the username for a user account that hasadministrator permissions for the vCenter server.

3. In the Password field, type the password for the user account.

Resources you need

Chapter 3: Creating and configuring the virtual machines 25


4. Click on the Login button.

Step 2: Conditionally, add ESXi hosts

If you're installing HCP Anywhere on ESXi hosts that the vCenter Serverdoes not know about, you need to add both hosts to a new or existingdatacenter. For instructions on doing this, see "Appendix A: Adding ESXihosts" on page 69.

Otherwise, continue to "Step 3: Specify time settings for the ESXi hosts"below.

Step 3: Specify time settings for the ESXi hosts

You need to configure both ESXi hosts to use one or more external timeservers as a time source. The recommended configuration is for both ESXihosts to use the same time source as your Active Directory environment.

To specify time settings for an ESXi host:

1. Right-click on the host and click on Settings.

Step 2: Conditionally, add ESXi hosts



2. Click on the Manage tab > Settings > Time Configuration > Edit button.

Step 3: Specify time settings for the ESXi hosts



The Edit Time Configuration window appears.

3. Ensure that Use Network Time Protocol (Enable NTP client) is enabled.

4. In the NTP Service Startup Policy section, select Start and stop with host.

5. In the NTP Servers section, enter the IP addresses or hostnames of oneor more time servers. Then click on the OK button.

6. Repeat this procedure for the other host. In step 5, use the same timeserver or time servers that you specified for first host.

Step 4: Create the datastores

You need to create a datastore for each HCP Anywhere virtual machine touse. You do this in the vSphere Web Client by identifying storage locationsthat you have already provisioned. The datastores you create can share thesame storage location or they can use different storage locations.




For information on:

• The storage requirements for each virtual machine, see "Storagerequirements" on page 9.

• Provisioning the underlying storage for a datastore, see the applicablevSphere documentation.

To create a datastore:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe ESXi hosts that you added and click on New Datastore.




The New Datastore window appears.

2. Follow the wizard to create the datastore for the storage that you haveprovisioned for HCP Anywhere to use. For more information, see theapplicable vSphere documentation.

3. Repeat this procedure to create a datastore for the other ESXi host.

Step 5: Configure the networks

Each HCP Anywhere virtual machine requires access to two networks. One,the front-end network, is used for user and administrator access and theother, the back-end network, is used for communication between the virtualnodes.

Step 5a: Conditionally, configure the front-end network

If the ESXi host does not have an existing network that provides front-endconnectivity, you need to create one.

To create the front-end network:

1. Click on the Go to vCenter icon ( ).

Step 5: Configure the networks



2. In the lefthand panel, in the Inventory Trees section, click on Hosts andClusters.

3. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe ESXi hosts that you added and click on Settings.

Step 5a: Conditionally, configure the front-end network



4. Click on the Manage tab > Networking > Virtual switches.

5. On the Virtual switches page, click on the Add host networking icon( ).

6. Use the Add networking wizard to create a front-end network forHCP Anywhere to use.

For information on adding networks, see the applicable VMware vSpheredocumentation.

Step 5b: Create the back-end network

To configure the back-end network:

1. On the Virtual switches page, click on the Add host networking icon( ).

The Add Networking window appears




2. On the Select connection type page, select Virtual Machine Port Group fora Standard Switch.

Note: For information on setting up other types of connections, see theapplicable VMware vSphere documentation.

3. Click on the Next button.

4. On the Select target device page, select New standard switch.


6. On the Create a Standard Switch page, select a physical adapter toassign to the new switch.


8. On the Connection Settings page, in the Network label field, type HCPAnywhere Back-End Network.


10.On the Ready to complete page, click on Finish.




Step 6: Create the virtual machines

You create the HCP Anywhere virtual machines by deploying the OVFtemplate twice.

Step 6a: Unpack the virtual machine image file

On your computer, access the DVD that contains the virtual machine imagefile and unpack the AW012_VMDK-x.x.x.x.iso or AW013_RDM-x.x.x.x.iso file into adirectory of your choice.

Step 6b: Deploy the OVF template

To create an HCP Anywhere virtual machine, you need to deploy the OVFtemplate contained in the AW012_VMDK-x.x.x.x.iso or AW013_RDM-x.x.x.x.iso file. You need to do this twice to create the two HCP Anywherevirtual machine nodes.

To deploy the OVF template:



Step 6: Create the virtual machines



3. On the Hosts and Clusters tab in the lefthand panel, right-click on a hostand click on Deploy OVF Template.




The Deploy OVF Template window appears.

4. On the Select source page:

a. Select Local file.

b. Click on the Browse button and navigate to the location where youunpacked the AW012_VMDK-x.x.x.x.iso or AW013_RDM-x.x.x.x.iso file.

c. Select the HCP-AW-VMDK.ovf or HCP-AW-RDM.ovf file.

d. Click on the Open button.

e. Click on the Next button.

5. On the Review details page, view the information about the template.Then click on the Next button.

6. On the Select name and folder page:

a. In the Name field, type a name for the HCP Anywhere virtualmachine.

b. In the Select a folder or datacenter section, select the datacenter towhich you added the hosts.

c. Click on the Next button.




7. On the Select storage page:

a. In the Select virtual disk format field, select either Thick ProvisionLazy Zeroed or Thick Provision Eager Zeroed.

For information on these disk formats, see the applicable VMwarevSphere documentation.

b. In the table at the bottom of the page, select one of the datastoresthat you created in "Step 4: Create the datastores" on page 28.


8. On the Setup networks page:

a. For Frontend, select HCP Anywhere Front-End Network.

b. For Backend, select HCP Anywhere Back-End Network.


9. On the Ready to complete page, ensure that Power on after deploymentis not selected.

10.Click on the Finish button.

The vSphere Web Client begins creating the virtual machine. This cantake several minutes to complete.

11.Repeat this procedure on the other host.

Step 7: Conditionally, reconfigure each virtual machine

If you used the AW012_VMDK-x.x.x.x.iso file and your system supports2,001–5,000 users, you do not need to edit the virtual machine settings.Continue to step "Step 8: Start the virtual machines" on page 43.

Otherwise, you need to reconfigure each virtual machine.

Step 7: Conditionally, reconfigure each virtual machine



Step 7a: Reconfigure CPU and memory

To reconfigure the CPU and memory for a virtual machine:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe virtual machines that you deployed and click on Edit Settings.

Step 7a: Reconfigure CPU andmemory



The Edit Settings window opens to the Virtual Hardware tab.

2. In the CPU and Memory fields, enter the applicable values for thenumber of users the system supports.

Potential number of users CPUs Memory

1-100 4 4 GB

101–200 4 6 GB

201–500 4 8 GB

501–1000 4 10 GB

1001–2000 4 16 GB

2,001–5,000 6 32 GB

5,001–20,000 16 128 GB

20,001-50,000 16 256 GB

Step 7b: Conditionally, add hard disks

If you used the AW013_RDM-x.x.x.x.iso file, you need to create two harddisks for each virtual machine. Otherwise, continue to "Step 7c:Conditionally, reconfigure hard disks" on page 41.

To create the hard disks:

1. From the New device menu at the bottom of the Virtual Hardware tab,select New Hard Disk. Then click on the Add button.

A New Hard disk row appears in the window.




2. In the New Hard disk row, specify the applicable disk size from the tablebelow.

Number of users Hard disk 2 size

1-100 20 GB

101–200 20 GB

201–500 20 GB

501–1000 70 GB

1001–2000 120 GB

2,001–5,000 270 GB

5,001–20,000 800 GB

20,001-50,000 800 GB

3. Click on the arrow to expand the New Hard disk row and configure anyother settings as necessary for your storage configuration. Forinformation on the settings you can configure, see the applicableVMware vSphere documentation.

Important: The Disk Provisioning type cannot be Thin Provision.

4. Repeat steps 1 through 3 to create a second hard disk. For this disk,specify the applicable disk size from the table below.


1-100 40 GB

101–200 40 GB

201–500 40 GB

501–1000 152 GB

1001–2000 264 GB

2,001–5,000 600 GB

5,001–20,000 1800 GB

20,001-50,000 4.64 TB




5. Continue to "Step 7d: Configure the other virtual machine" on thenext page.

Step 7c: Conditionally, reconfigure hard disks

If you used the AW012_VMDK-x.x.x.x.iso file and your system does notsupport 2,001–5,000 users, you need to change the sizes of two of thethree virtual disks.

Note: Hard disk 1 is used to store the HCP Anywhere OS. Do not changethe size of hard disk 1.

To reconfigure the hard disks:

1. On the Virtual Hardware tab, in the Hard disk 2 field, specify theapplicable value from the table below.


1-100 20 GB

101–200 20 GB

201–500 20 GB

501–1000 70 GB

1001–2000 120 GB

2,001–5,000 270 GB

5,001–20,000 800 GB

20,001-50,000 800 GB

Step 7c: Conditionally, reconfigure hard disks



2. In the Hard disk 3 field, specify the applicable value from the tablebelow.


1-100 40 GB

101–200 40 GB

201–500 40 GB

501–1000 152 GB

1001–2000 264 GB

2,001–5,000 600 GB

5,001–20,000 1800 GB

20,001-50,000 4.64 TB

3. Click on the OK button.

Step 7d: Configure the other virtual machine

Repeat steps "Step 7a: Reconfigure CPU and memory" on page 38through "Step 7c: Conditionally, reconfigure hard disks" on the previouspage for the other virtual machine.

Step 7d: Configure the other virtual machine



Step 8: Start the virtual machines

To start a virtual machine:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe virtual machines that you deployed and click on Power On.

2. Repeat step 1 for the other node.




Installing and configuring theHCP Anywhere software

After you create and configure the HCP Anywhere virtual machines, youneed to configure the network settings for each node and install the HCPAnywhere software.

This chapter includes instructions for using the HCP Anywhere Setupprogram to perform these tasks.


45

4

Chapter 4: Installing and configuring the HCP Anywhere software


To install the HCP Anywhere software and configure the network settings forthe HCP Anywhere nodes, you need to know certain information about thesystem that you are creating. You can use the HCP Anywhere SoftwareInstallation Information form on page 75 to record this information.

You need to know:

• The back-end IP addresses for both nodes

These IP addresses need to be on the same class C subnet.

• The front-end IP addresses for both nodes

• The front-end IP subnet mask

• The IP address for the front-end gateway

• The DNS name for the system

• The IP address of a DNS server for the system to use

• The IP address of a time server for the system to use

• The time zone for the location in which the system is installed

• The name of the distributor key for the installation. You get this namefrom the HCP Anywhere distributor.

• If the HCP Anywhere distributor is not HDS, the HCP Anywherecustomer support contact information.

Configuring network settings for each HCP Anywherenode

When initially created, the HCP Anywhere virtual nodes are assigned defaultfront-end and back-end IP addresses. You need to change these addressesto ones that work for your network environment.


Chapter 4: Installing and configuring the HCP Anywhere software46


Step 1: Log in for the network configuration

To begin the procedure for changing the network configuration, you need tolog in as the install user and then change the password for that user:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe virtual machines that you deployed and click on Open Console.

The console opens in a new browser window to the login prompt.

2. Click within the black area of the screen to type in the console.

3. Enter: install

A password prompt appears.


Chapter 4: Installing and configuring the HCP Anywhere software 47


4. Enter: Chang3Me!

As you type, the characters do not show.

Note: If you've previously changed the password for the install user, enterthat password instead. Then continue the installation procedure from whereyou ended the last session.

The system prompts for the current password again.

5. Enter: Chang3Me!

The system prompts for a new password for the install user.

6. Enter a new password for the install user.

Passwords must follow the standard rules for Unix passwords. To bevalid, a password must include at least one character from two of thesethree groups: alphabetic, numeric, and special characters. Also, apassword cannot be a word found in the dictionary.

Changing the install user password is a one-time event. Be sure toremember the new password. You will need it when checking the healthof the system after installing the HCP Anywhere software.

Tip: For the new password, use hcpawinsta11, where the last twocharacters are the number one.

7. When prompted, enter the new password again.

The system changes the password and prompts you to continue.




8. Press Enter.

TheWelcome to HCP-AW! menu appears.

9. Enter 2

10.In response to the confirming prompt, enter y to confirm your entry or nto try again.

The HCP-AW Network Configuration Menu appears.

Step 2: Configure front-end network settings

To configure the front-end network settings for the virtual machine:

1. On the HCP-AW Network Configuration Menu, enter 1




2. In response to the confirming prompt, enter y to confirm your entry or nto try again.

The HCP-AW Front-end Network Configuration Menu appears.

3. Enter 1


5. When prompted, enter the front-end IP address for the node.


7. Enter 2


9. When prompted, enter the subnet mask for the front-end IP address.


11.Enter 3





13.When prompted, enter the IP address for the front-end gateway.


15.Enter b

Step 3: Configure back-end network settings

To configure the back-end network settings for the virtual machine:

1. On the HCP-AW Network Configuration Menu, enter 2


The HCP-AW Back-end Network Configuration Menu appears.

3. Enter 1


5. When prompted, enter the back-end IP address for the node.

Note: Take note of the node to which you assign the highest back-endIP address. You need to perform the HCP Anywhere software installationfrom this node.


Step 3: Configure back-end network settings



7. Enter b

Step 4: Apply the changes

After reconfiguring the back-end and front-end network settings, you needto apply the changes you've made to the node. Doing this causes the nodeto reboot.

To apply the changes you've made to the network configuration:

1. On the HCP-AW Network Configuration Menu, review the Pending front-end IPv4 Configuration and Pending back-end IPv4 Configuration sectionsto ensure that the settings you entered are correct.

1. Enter x


3. In response to the prompt warning that the node will be rebooted, entery.

The node reboots and the login screen reappears.

Step 5: Configure network settings for the other node

Repeat "Step 1: Log in for the network configuration" on page 47 through"Step 4: Apply the changes" above for the other node.

If you've configured the network settings for both virtual machines,continue to "Installing the HCP Anywhere software" below.

Installing the HCP Anywhere software

After configuring the network settings for the virtual nodes, you need toinstall the HCP Anywhere software. The nodes contain the HCP Anywheresoftware installation files so you do not need to download or retrieve thosefiles.

Step 4: Apply the changes



Performing the HCP Anywhere software installation

To install the HCP Anywhere software:

1. Log into the highest-numbered node in the HCP Anywhere system (see"Step 1: Log in for the installation" below).

2. Configure the HCP Anywhere system (see "Step 2: Configure the HCPAnywhere system" on page 55).

3. Verify the configuration (see "Step 3: Verify the system configuration"on page 62)

4. Execute the installation (see "Step 4: Execute the installation" onpage 62).

Step 1: Log in for the installation

To begin the procedure for installing the HCP Anywhere software, you needto log into the highest-numbered node as the install user:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on thevirtual machine with the highest back-end IP address and click on OpenConsole.

Performing the HCP Anywhere software installation





3. Enter: install


4. Enter the password and press enter.


Step 1: Log in for the installation



Step 2: Configure the HCP Anywhere system

To configure the HCP Anywhere system, from theWelcome to HCP-AW!menu, enter 1

The HCP-AW Setup: New Install Menu appears.

From the New Installmenu, execute the additional options for configuringthe HCP Anywhere system. Each option either opens a lower-level menuwith configuration options or leads directly to a configuration option.

Step 2a: Identify the nodes in the systemTo identify the nodes in the system:

1. From the New Installmenu, enter 1.





The Back-end IP Addresses menu appears.

3. Enter e.


The wizard prompts for the back-end IP address of one of the nodes.

5. Enter the back-end IP address for one of the nodes.


The wizard prompts for the back-end IP address of another node.

7. Enter the back-end IP address for the other node.





9. In response to the confirming prompt, enter y to confirm that both theIP addresses you entered are correct or enter n to try again.

10.Enter b.


The New Installmenu reappears.

Step 2b: Configure network settingsTo configure the network settings for the HCP Anywhere system:



The HCP-AW Networking Options menu appears.

3. Enter 1.


The wizard prompts for the front-end IP gateway address.

5. Enter the front-end IP gateway address.


7. Enter b.






Step 2c: Configure DNS settingsTo configure the DNS settings for the HCP Anywhere system:



The HCP-AW DNS Options menu appears.

3. Enter 1.


The wizard prompts for a DNS name for the system.

5. Enter the DNS name for the system.


7. Enter 2


The wizard prompts for the IP address for a DNS server.




9. Enter the IP address for a DNS server for HCP Anywhere to use.


11.Enter b.



Step 2d: Configure time settingsTo configure time settings for the HCP Anywhere system:



The HCP-AW Time Options menu appears.

3. Enter 1.


The wizard prompts for the IP address or hostname of a time server.

5. Enter the IP address or hostname for a time server for HCP Anywhere touse.





7. Enter 2.


The wizard prompts for the region in which the system is located.

9. Enter the name of region from the list in the prompt. Do not type squarebrackets in your entry.


The wizard prompts for a location. The options differ depending on theregion you selected.

Tip: Press Shift+Page Up and Shift+Page Down to scroll through the list.

11.Enter the name of the applicable location from the list in the prompt. Donot type square brackets in your entry.





The HCP-AW Time Options menu reappears.

13.Enter b.



Step 2e: Configure service settingsTo configure the service settings for the HCP Anywhere system:



The HCP-AW Service Settings menu appears.

3. If the distributor key is not Acton, enter 1.


The wizard prompts for the name of a distributor key.

5. Enter the name of the distributor key for the system.





7. If the HCP distributor is not HDS, enter 2.

The wizard prompts for the customer support contact information.

8. Enter the customer support contact information.


10.Enter b.



Step 3: Verify the system configuration

To verify the system configuration before executing the installation:

1. From the New Installmenu, enter v.

The wizard displays the current configuration.

2. Review the configuration.

3. Enter b.

The wizard returns to the New Installmenu, from which you can correctthe configuration or execute the installation.

Step 4: Execute the installation

To execute the HCP Anywhere software installation:

1. From the New Installmenu, enter x.


Step 3: Verify the system configuration



HCP-AW Setup performs a set of configuration prechecks and, if they aresuccessful, installs the HCP Anywhere software on all nodes in thesystem.

When the installation is complete, HCP-AW Setup logs you out andreboots the nodes. The console then displays the login prompt.

If HCP-AW Setup exits at any time before the installation processing iscomplete, make a note of all error messages and then contact your HCPAnywhere service provider for help.

Verifying the HCP Anywhere installation

To verify that the HCP Anywhere software installed correctly:

1. On the Hosts and Clusters tab in the lefthand panel, right-click on one ofthe virtual machines and click on Open Console.






3. Enter: install


4. Enter the password and press enter.


5. On theWelcome to HCP-AW! page, enter 2.





When you enter y, the HCP-AW Node Status page appears.

7. Review the system status.

Ensure that the status for each system component is either OK or Online.

If any component displays a status of Broken, Unavailable, or Offline,please contact your authorized HCP Anywhere service provider for help.

8. Enter b.


TheWelcome to HCP-AW! menu reappears.




Logging into the Management Console

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

1. In a web browser, enter the URL for the Management Console. The URLhas this format:

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

For example:

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

Notes:

• If you inadvertently use http instead of https in the URL, thebrowser returns an error. Enter the URL again, this time usinghttps.

• For the Management Console to be accessible, TLS 1.0 needs tobe enabled for your web browser.

2. 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.

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

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

5. Click on the Log In button.

The Console displays the Change Password page.

Logging into the Management Console



6. 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.

7. Click on the Update Password button.

After installing the software

By default, the HCP Anywhere VM system supports only a limited number ofusers and HDI devices. In order to increase these limits, you need tocontact your authorized HCP Anywhere service provider to reset the systemserial number and apply the licenses that you purchased.

Additionally, you need to perform some configuration activities to grantaccess to users and to enable the file synchronization and sharing and HDIdevice 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.




Adding ESXi hosts

In order to install an HCP Anywhere VM system, you need to add both ESXihosts to the vCenter server.

This appendix contains instructions for adding ESXi hosts to the vCenterserver. For more information on doing this, see the applicable VMwaredocumentation.


69

A

Appendix A: Adding ESXi hosts


For each ESXi host that you are adding, you need to know:

• The hostname or IP address of the host.

• The name of the license key for the host to use.

• Whether to enable lockdown mode. For information, see the applicableVMware vSphere documentation.

Adding the hosts

To add ESXi hosts to the datacenter, in the VMware vSphere Web Client:




Appendix A: Adding ESXi hosts70


3. Optionally, to create a new datacenter in which to group the hosts:

a. On the Hosts and Clusters tab in the lefthand panel, right-click on thevCenter Server that you want and click on New Datacenter.

b. In the New Datacenter window, enter a name for the new datacenter.Then click on the OK button.

4. Right-click on the datacenter you want and click on Add Host.

Adding the hosts

Appendix A: Adding ESXi hosts 71


The Add Host window appears.

5. In the Add Host window, on the Name and location page, enter thehostname or IP address for one of the ESXi hosts. Then click on the Nextbutton.

The Host summary page appears and shows information about the hostyou specified.


7. On the Assign license page, select an existing license key to apply to thehost or specify a new license key. Then click on the Next button.

8. Optionally, on the Lockdown mode page, to prevent remote users fromaccessing the host, select Enable lockdown mode. Then click on the Nextbutton.

9. On the VM location page, click on the Next button.

10.On the Ready to complete page, click on the Finish button.

The host is added to the datacenter.

11.Repeat this procedure for the second ESXi host you are adding.

Adding the hosts

Appendix A: Adding ESXi hosts72


Forms

This appendix contains forms that you can use to facilitate the procedurespresented in this book:

• Virtual Machine Creation Information lets you record the informationyou need to set up your vSphere environment and create the HCPAnywhere virtual machines.

• HCP Anywhere Software Installation Information lets you record theinformation you need to install the HCP Anywhere software.


73

B

Appendix B: Forms

Virtual Machine Creation Information

Use this form to record the information for setting up your vSphereenvironment and creating the HCP Anywhere virtual machines.

vSphere environment setupESXi host IP addresses or hostnames:

Time server IP address:

Datastore name(s) and storage location(s):

vmNIC for Front-end Network:

vmNIC for Back-end Network:

Deploying the OVF templateMaximum expected number of HCP Anywhere users:

HCP Anywhere virtual machine names:

Disk Format (cannot be Thin Provisioned):

Virtual Machine Creation Information

Appendix B: Forms74


HCP Anywhere Software Installation Information

Use this form to record the information for an HCP Anywhere softwareinstallation and for configuring network settings for the nodes.

Network configurationFront-end IP addresses:

Front-end IP subnet mask:

Front-end gateway IP address:

Back-end IP addresses:

DNSDNS name of the HCP Anywhere system:

IP address of corporate DNS server:

TimeIP address of time server:

Time zone:

ServiceDistributor key:

Customer support contact information:


Appendix B: Forms 75



Appendix B: Forms76


Glossary

AActive Directory (AD)

A Microsoft product that, among other features, provides userauthentication services.

ADSee Active Directory (AD).

Ddata center

In VMware vSphere, a logical unit for grouping and managing hosts.

databaseSee HCP Anywhere database.

datastoreA representation of a location in which a virtual machine stores files. Adatastore can represent a location on a host or an external storagelocation such as a SAN LUN.

domainA group of computers and devices on a network that are administeredas a unit.

domain name system (DNS)A network service that resolves domain names into IP addresses forclient access.

Glossary 77


DRSSee VMware vSphere Distributed Resource Scheduler.

EESXi

See VMware ESXi.

FFault Tolerance

See VMware vSphere Fault Tolerance.

file synchronization and sharingA feature of HCP Anywhere that allows users to access and share filesfrom almost any location. HCP Anywhere provides file synchronizationapplications for computers and mobile devices and a web-basedapplication called the HCP Anywhere User Portal.

HHCP

See Hitachi Content Platform (HCP).

HCP AnywhereA system that provides file synchronization services and managesHitachi Data Ingestor (HDI) devices. An HCP Anywhere systemconsists of both hardware and software and, for file synchronizationservices, uses Hitachi Content Platform (HCP) to store data.

HCP Anywhere databaseIn internal component of an HCP Anywhere system that containsessential data about the system, users, and user's files. The databaseis maintained by one node and copied to the other.

HCP Anywhere User PortalThe system-specific web application used for managing filesynchronization activity.

DRS

Glossary78


HCP Anywhere VM systemAn HCP Anywhere system in which the nodes are virtual machinesrunning in a VMware vSphere environment.

HDISee Hitachi Data Ingestor (HDI) Remote Server.

HDI device managementA feature of HCP Anywhere that allows administrators to remotelyconfigure, manage, and monitor Hitachi Data Ingestor (HDI)appliances.

Hitachi Content Platform (HCP)A distributed object-based storage system designed to support large,growing repositories of fixed-content data.

Hitachi Data Ingestor (HDI) Remote ServerA storage device that allows users to access the contents of an HCPsystem as if it were part of the local file system.

hostA physical computer on which virtual machines are installed and run.

hypervisorA type of operating system that allows virtual machines to be run on aphysical host machine.

Nnode

A server or virtual machine running HCP Anywhere software. Twonodes are networked together to form an HCP Anywhere system.

Pphysical HCP Anywhere system

An HCP Anywhere system in which the nodes are physical hardware(not virtual machines).

physical HCP Anywhere system

Glossary 79


SSAML

See security assertion markup language (SAML).

Security assertion markup languageAn XML-based protocol used for exchanging authenticationinformation between HCP Anywhere and an identity provider.

SSL terminationA process in which SSL-encrypted traffic bound for one server isredirected to another server that decrypts the information and thensends it to the target server. In this way, the target server does notneed to use its resources to decrypt the information.

UUser Portal

See HCP Anywhere User Portal.

VvCenter

See VMware vCenter Server.

virtual machineA piece of software that emulates the functionality of a physicalcomputer. Virtual machines must be run in a special operating systemcalled a hypervisor.

vmNICA representation in VMware vSphere of one of the physical NICs on ahost.

vMotionSee VMware vSphere vMotion.

VMware ESXiThe underlying hypervisor for the VMware vSphere product.

SAML

Glossary80


VMware vCenter ServerA VMware product that allows you to manage multiple ESXi hosts andthe virtual machines that they run.

VMware vSphere Distributed Resource SchedulerA feature of VMware vSphere that balances computational loadsacross virtual machine resources.

VMware vSphere Fault ToleranceA feature of VMware vSphere in which a copy of a virtual machine iskept up-to-date and immediately brought into service when theoriginal virtual machine experiences a failure.

VMware vSphere vMotionA feature of VMware vSphere that allows an active virtual machine tobe migrated from one host to another.

vSphere Web ClientA browser application that allows you to manage virtual machinesacross multiple hosts.

vSphere Web Client

Glossary 81


VMware vCenter Server

Glossary82


AActive Directory 20architecture, system 2-4availability, about 5

Bback-end IP addresses

changing 51-52information needed 46

back-end network, about 2

Cchanging

back-end IP addresses 51-52front-end IP addresses 49-51

Ddatastores

creating 28-30underlying storage 3

Distributed Resource Scheduler (DRS)11

DRS 11

EESXi

about hosts 2adding hosts 69host requirements 8supported versions 8

Ffailover management, about 5

Fault Tolerance (vSphere feature) 11features not supported 11file synchronization and sharing,

about 2firewall, information for configuring 12-

19forms

HCP Anywhere Software InstallationInformation 75

Virtual Machine Creation Inform-ation 74

free space needed 10front-end IP addresses

changing 49-51information needed 46

front-end network, about 2

HHCP Anywhere

about 2availablity 5failover management 5file synchronization and sharing 2HDI device management 2monitoring 5network connection information 12-

19system architecture 2-4user authentication 20verifying installation 65

HCP Anywhere software installationform 75

Index

Index 83


HCP Anywhere Software Installation Information form

performing 53HCP Anywhere Software Installation

Information form 75HDI device management, about 2hosts

about 2monitoring 5requirements 8

Iimage files

obtaining 25types 25

information neededfor software installation 25, 46

installing, HCP Anywhere software 52

Lload balancer, information for con-

figuring 12-19logging in

for configuring network settings 47-49

for software installation 53-54vSphere Web Client 25-26

logging into Management Console 66-67

MManagement Console

logging in 66-67URL 66

monitoringHCP Anywhere 5hosts 5

NNAS servers, network connection inform-

ation 19network requirements 11nodes, about 2

OOVF template

deploying 34-37obtaining 25

Ppreparing site for installation 7

Rrequirements

for ESXi hosts 8for virtual machines 9network 11storage 9-10time source 21user authentication 20

Ssite preparation 7Snapshots 11software installation

logging in 53-54performing 53

space requirements 10storage

about 3locations 9requirements 9-10

supported versionsActive Directory 20ESXi 8vCenter Server 8vSphere Web Client 8

system architecture 2-4system health, checking 65

Ttime source requirements 21

Uuser authentication requirements 20

Index84


vSphere Web Client

VvCenter Server, supported versions 8verifying HCP Anywhere installation 65versions

supported for vCenter Server 8supported for vSphere Web Client 8

Virtual Machine Creation Informationform 74

virtual machinescreating 34requirements 9

vMotion 11VMware features, unsupported 11VMware vSphere Fault Tolerance 11VMware vSphere vMotion 11vSphere Web Client

logging in 25-26supported versions 8

Index 85


Index86


MK-HCPAW011-02

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]/



deploying an hcp anywhere vm system - hitachi …hcp...

Documents