Aruba Intelligent Management Center iHATool Installation guide

HPE Intelligent Management Center

iHATool Installation Guide

P

art number: 5998-6760R

Software

version: IMC PLAT 7.3 (E0705)

Document version: 5PW105-20201124

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard

Enterprise products and services are set forth in the express warranty statements accompanying such

products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett

Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or

copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software

Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s

standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard

Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise

website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the

United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

i

Contents

Overview ······································································································· 1

Preparing for installation ················································································ 2

Checking server requirements for IMC ·············································································································· 2

Installing iHATool ··············································································································································· 3

Configuring the shared storage ·························································································································· 4

Configuring firewall settings ······························································································································· 4

Deploying an IMC system and installing IMC HAC ········································ 6

Deploying IMC and installing IMC HAC on Windows ························································································· 6

Centralized deployment with a remote database ······················································································· 6

Centralized deployment on shared storage ····························································································· 13

Centralized deployment with DBMan for data synchronization ································································ 26

Deploying IMC and installing IMC HAC on Linux ····························································································· 33

Centralized deployment with a remote database ····················································································· 33

Centralized deployment on shared storage ····························································································· 39

Centralized deployment with DBMan for data synchronization ································································ 45

Installing IMC HAC and deploying standby servers for an IMC server ········· 54

Installing IMC HAC and deploying standby servers on Windows ···································································· 54

Centralized deployment with a remote database ····················································································· 54

Centralized deployment on shared storage ····························································································· 56

Centralized deployment with DBMan for data synchronization ································································ 57

Installing IMC HAC and deploying standby servers on Linux ·········································································· 58

Centralized deployment with a remote database ····················································································· 58

Centralized deployment on shared storage ····························································································· 60

Centralized deployment with DBMan for data synchronization ································································ 61

Synchronizing configuration files from the active server to standby servers in

real time ······································································································· 62

Synchronizing configuration files on Linux ······································································································· 62

Prerequisites ············································································································································ 62

Installing inotify-tools ································································································································ 62

Installing rsync ········································································································································· 65

Installing imcsyncs ··································································································································· 70

Synchronizing configuration files on Windows ································································································· 71

Prerequisites ············································································································································ 71

Installing cwRsyncServer ························································································································· 71

Installing imcsyncs ··································································································································· 76

Starting the RsyncServer service ············································································································· 78

Restrictions and guidelines ·········································································· 81

Using iHATool ·················································································································································· 81

Registering licenses ········································································································································· 83

Jserver startup failure on the subordinate server after IMC version upgrade ·················································· 83

Modifying iHA Server script after IMC service name is changed ····································································· 84

Upgrading iHATool ······················································································ 86

Uninstalling iHATool ···················································································· 87

About HPE IMC documents ········································································· 88

Document conventions ················································································ 90

Support and other resources ······································································· 91

Accessing Hewlett Packard Enterprise Support······························································································· 91

ii

Accessing updates ··········································································································································· 91

Websites ·················································································································································· 92

Customer self repair ································································································································· 92

Remote support ········································································································································ 92

Documentation feedback ························································································································· 92

1

Overview

IMC HAC provides high availability for the IMC system by allowing one or multiple standby servers to

provide IMC services for redundancy. Without IMC HAC, IMC services are interrupted when a server

is faulty and are available after the server is fixed. To prevent service interruption, when IMC HAC

detects hardware or software faults, it immediately starts IMC on a standby server.

Depending on whether DBMan is used to back up database files and configuration files for IMC

servers, IMC deployment modes can be classified into the following types:

•

In deployments where DBMan is not used, IMC deployment modes can be classified into the

following types:

 IMC is deployed on the local server with a single remote database.

 IMC is deployed on the shared storage.

•

In deployments where DBMan is used for data backup, IMC deployment modes can be

classified into the following types:

 IMC is deployed on the local server with different remote databases.

 IMC is deployed on the local server with local databases.

The iHATool client software runs on a remote machine for managing the IMC HAC system, including

servers running the iMC HAC Server (in Windows) or imchacs (in Linux) service. iHATool supports

only the IMC Platform, and does not support IMC service components. iHATool supports only the

SQL Server and Oracle databases to be used by IMC (the MySQL database is not supported

currently).

To implement IMC HAC, use the following configuration flow:

1. Install IMC HAC on the servers.

2. Add the servers to server groups by using iHATool.

3. Install and deploy IMC on the servers or the shared storage.

Each server group in iHATool must be configured with a virtual IP address through which the server

group provides services regardless of the IP address of the active server in the group. As a best

practice, set the virtual IP addresses of all server groups to be on the same network segment.

2

Preparing for installation

This chapter describes the tasks you must complete before performing the IMC HAC installation.

Checking server requirements for IMC

Check the server where IMC and IMC HAC services are to be installed. Make sure the server meets

all the hardware and software requirements for IMC installation. For more information, see HPE IMC

deployment guides.

Table 1 Hardware requirements for 64-bit Windows operating system

Management scale

System minimum requirements

Nodes Collection

units Online

operators CPU Server

memory

Java

heap

size

Disk space

for

installation

Disk space

for data

storage

0 to 200 0 to 5 K 20 2 cores 12 GB 4 GB 3 GB 100 GB

0 to 200 5 K to 50 K 10 2 cores 12 GB 4 GB 3 GB 200 GB

200 to 1

K 0 to 10 K 30 4 cores 16 GB 4 GB 3 GB 100 GB

200 to 1

K 10 K to 100 K 10 4 cores 16 GB 4 GB 3 GB 200 GB

1 K to 2

K 0 to 20 K 30 6 cores 24 GB 8 GB 4 GB 100 GB

1 K to 2

K 20 K to 200 K 10 6 cores 24 GB 8 GB 4 GB 200 GB

2 K to 5

K 0 to 30 K 40 8 cores 32 GB 12 GB 5 GB 120 GB

2 K to 5

K 30 K to 300 K 20 8 cores 32 GB 12 GB 5 GB 250 GB

5 K to 10

K 0 to 40 K 50 16

cores 48 GB 16 GB 7 GB 150 GB

5 K to 10

K 40 K to 400 K 20 16

cores 48 GB 16 GB 7 GB 300 GB

10 K to

15 K 0 to 40 K 50 24

cores 64 GB 24 GB 10 GB 200 GB

10 K to

15 K 40 K to 400 K 20 24

cores 64 GB 24 GB 10 GB 600 GB

Table 2 Hardware requirements for 64-bit Linux operating system

Management scale

System minimum requirements

Nodes Collection

units Online

operators CPU Server

memory

Java

heap

size

Disk space

for

installation

Disk

space for

data

storage

0 to 200 0 to 5 K 20 2 cores 12 GB 4 GB 3 GB 100 GB

3

Management scale

System minimum requirements

0 to 200 5 K to 50 K 10 2 cores 12 GB 4 GB 3 GB 200 GB

200 to 1

K 0 to 10 K 30 4 cores 16 GB 6 GB 3 GB 100 GB

200 to 1

K 10 K to 100 K 10 4 cores 16 GB 6 GB 3 GB 200 GB

1 K to 2

K 0 to 20 K 30 6 cores 24 GB 8 GB 4 GB 100 GB

1 K to 2

K 20 K to 200 K 10 6 cores 24 GB 8 GB 4 GB 200 GB

2 K to 5

K 0 to 30 K 40 8 cores 32 GB 12 GB 5 GB 120 GB

2 K to 5

K 30 K to 300 K 20 8 cores 32 GB 12 GB 5 GB 250 GB

5 K to 10

K 0 to 40 K 50 16 cores 64 GB 16 GB 7 GB 150 GB

5 K to 10

K 40 K to 400 K 20 16 cores 64 GB 16 GB 7 GB 300 GB

10 K to

15 K 0 to 40 K 50 24 cores 80 GB 24 GB 10 GB 200 GB

10 K to

15 K 40 K to 400 K 20 24 cores 80 GB 24 GB 10 GB 600 GB

Installing iHATool

iHATool can be installed only on a Windows machine.

To install iHATool, run the installer on Windows. Click Browse to set the installation directory, and

then click Install, as shown in Figure 1.

4

Figure 1 Installing iHATool

Configuring the shared storage

This configuration is required when both IMC and the database reside on the shared storage.

When IMC and the database use the ISCSI shared storage or FC shared storage, perform the

following tasks:

•

Specify two logical volumes of the same storage type on the shared storage.

•

Use one of the volumes to install IMC and store database files. Partition of the volume and

format the partition. Make sure the disk space meets the minimal disk space requirements for

running IMC.

•

Use the other volume as the arbiter drive during shared parameter setting in iHATool. Set the

size of the volume to 1 GB (recommended).

Configuring firewall settings

To enable communications among IMC HAC, iHATool, and IMC, you must perform the following

tasks:

•

Open ports 8801 and 8802.

•

Enable ping operation on the iHATool host and IMC HAC server.

5

For more information about the firewall setting requirements for IMC installation, see HPE IMC

deployment guides.

6

Deploying an IMC system and installing

IMC HAC

Deploying IMC and installing IMC HAC on

Windows

Centralized deployment with a remote database

Figure 2 shows a centralized deployment network with a remote database.

Figure 2 Network diagram

Installation considerations

•

Install the database on a remote server before you install IMC. For more information about the

installation procedure, see HPE IMC SQL server installation and configuration guides.

•

Install and deploy the same set of IMC components on all servers in the server group so that

they can provide redundancy for each other.

•

After the IMC HAC configuration is complete on the active and standby servers, install

cwRsyncServer and imcsync software on the servers.

These software products are required for realtime synchronization of configuration files from the

active server to standby servers. For installation procedures, see "Synchronizing configuration

files from the active server to standby servers in real time."

•

By default, IMC HAC sets the first server added to a server group as the active server and other

servers as standby servers.

7

The following sections describe how to add the first (active) and second (standby) servers to the

server group. To add more standby servers in the group, follow the same procedure.

Installing and configuring IMC HAC on Server 1

1. Register the iMC HAC Server service by running the installer, as shown in Figure 3.

Figure 3 Registering the iMC HAC Server service

2. On the client, run iHATool, and then select File > Add Server Group.

The Add Server Group dialog box opens.

3. Specify the following server group attributes and server attributes, as shown in Figure 4:

 Group Name—Enter the server group name.

 External Virtual IP Address—Enter the virtual IP address of the server group.

 External IP Address—Enter the external IP address of Server 1.

 Internal IP Address—Enter the internal IP address of Server 1.

 Password—Enter the password used to access the server group. When you create a

server group, you must configure the password as admin. After the server group is created,

you can modify the password.

 Priority—Select a priority for the server. A greater value represents a higher priority.

8

Figure 4 Adding a server group

4. Click OK.

5. Install and deploy IMC in centralized mode on Server 1 and specify the remote database. See

HPE IMC deployment guides.

To specify the remote database during IMC installation, perform the following tasks, as shown

in Figure 5:

a. In the Checking Database Connectivity dialog box, select other server for the Database

Location field.

b. In the Database Server Address field, specify the IP address of the database server.

9

Figure 5 Checking database connectivity during IMC installation

6. Register the HP-iMC-Start service on the server:

a. Verify whether the HP-iMC-Start service is running on the server. If the service is running,

delete the service, as shown in Figure 6.

Figure 6 Deleting the HP-iMC-Start service

b. Enter the IMC installation directory iMC\deploy and register the HP-iMC-Start service.

JavaService.exe -install "HP-iMC-Start" "C:\Program

Files\iMC\deploy\jdk\bin\server\jvm.dll" -Djava.class.path=deploy.jar -start

com.h3c.imc.deploy.ProcessLauncher -params -wait start -stop

com.h3c.imc.deploy.ProcessLauncher -params stop -current "C:\Program

Files\iMC\deploy" -path "C:\Program Files\iMC\deploy\jdk\bin" -auto -shutdown 300

-startup 30 -description "iMC Startup Controller for Cluster Usage"

NOTE:

The IMC installation path, C:\Program Files\, is subject to your actual environment.

The service is successfully registered, as shown in Figure 7.

10

Figure 7 Command output

7. After registering the HP-iMC-Start service, start IMC. Use a browser to access the IMC login

page, and then click the Activate link to activate the license. When the license is successfully

activated, stop IMC. Make sure the license contains the IMC platform authorization and iHA

authorization.

8. Change the startup type of the HP-iMC-Start and Intelligent Management Server services to

Manual, and then stop these services, as shown in Figure 8.

Figure 8 Changing the service startup type

Installing and configuring IMC HAC on Server 2

1. Register the iMC HAC Server service by running the installer.

11

2. Start the iMC HAC Server service.

3. Add Server 2 to the server group by using iHATool:

a. Run iHATool on the client.

b. Right-click the name of the server group for Server 1 and select Add Server from the

shortcut menu.

The Add Server dialog box opens.

c. Specify the following parameters, as shown in Figure 9:

− Server Group—This field displays the server group name.

− External IP Address—Enter the external IP address of Server 2.

− Internal IP Address—Enter the internal IP address of Server 2.

− Password—Enter the password used to access the server group.

− Priority—Select a priority for Server 2. A greater value represents a higher priority.

Figure 9 Adding Server 2 to the server group

4. Click OK.

5. Stop IMC, the HAC iMC Server service, and the HP-iMC-Start service on Server 1.

6. Install IMC on Server 2:

a. Copy the IMC installation directory iMC from Server 1 to the same directory on Server 2.

b. Enter the IMC installation directory iMC\deploy at the CLI on Server 2, and then execute

the following command:

svcinst.bat -install -instdir "C:\Program Files\iMC" -datadir "C:\Program

Files\imcdata" -servertype master -language en -country US -dbtype SQLServer

-dbadminusername sa -dbadminpasswd iMC123 -dbaddress 10.153.88.231 -dbport 1433

-dbinstance instancename

The command parameters are described in Table 5.

12

Table 3 Command parameter descriptions

Parameter

Value

Remarks

svcinst.bat -install Start the IMC installation operation.

-instdir "C:\Program Files\iMC" IMC installation directory.

-datadir "C:\Progra Files\imcdata" Database file directory.

-servertype master(slave) Server type:

• master—Management group.

• slave—Managed group.

-language en Language used for HAC installation:

• zh—Chinese.

• en—English.

-country US US—United States.

-dbtype SQLServer(Oracle) Database type.

-dbadminusername sa Database username.

-dbaddress 10.153.88.231(127.0.0.1) IP address of the local database:

127.0.0.1.

-dbport 1433 Port used by the database (1433 by

default).

-dbinstance instancename

Optional. Specifies the instance name of

the SQL server database. You do not

have to specify the option when the

default instance (MSSQLSERVER) is

used.

-dbservicename servicename

Optional. Specifies the service name of

the Oracle database. You do not have to

specify the option when the default

service name (orcl) is used.

All of the parameter values in this command, except svcinst.bat, are subject to the actual

environment. If you use the default instance of the database, you do not have to specify the

-dbinstance option and value.

If the system prompts you that the server is already installed with IMC, delete the

iMC-Reserved folder from C:\Windows, and then re-execute the command.

IMC is successfully installed on Server 2, as shown in Figure 10.

Figure 10 IMC successfully installed

7. Enter the IMC installation directory iMC\deploy and register the HP-iMC-Start service.

JavaService.exe -install "HP-iMC-Start" "C:\Program

Files\iMC\deploy\jdk\bin\server\jvm.dll" -Djava.class.path=deploy.jar -start

13

com.h3c.imc.deploy.ProcessLauncher -params -wait start -stop

com.h3c.imc.deploy.ProcessLauncher -params stop -current "C:\Program

Files\iMC\deploy" -path "C:\Program Files\iMC\deploy\jdk\bin" -auto -shutdown 300

-startup 30 -description "iMC Startup Controller for Cluster Usage"

The IMC installation directory, C:\Program Files\ in this command, is subject to your actual

environment.

8. Change the startup type of the HP-iMC-Start and Intelligent Management Server services to

Manual and stop these services.

Upgrading IMC HAC servers

To upgrade IMC when IMC HAC is implemented:

1. In iHATool, set the HA mode to Configuration.

2. On active and standby servers, stop the realtime synchronization service.

3. Upgrade IMC on the active server.

For operation procedures, see HPE IMC deployment guides.

4. Stop IMC.

5. Copy the IMC installation directory on the active server to the same directory on all standby

servers.

6. On active and standby servers, start the realtime synchronization service.

7. In iHATool, set the HA mode to Operating.

Centralized deployment on shared storage

Figure 11 shows a centralized deployment network on shared storage.

Figure 11 Network diagram

Installation considerations

•

IMC is installed on the shared storage and the database files are stored on the shared storage.

Each server in the server group is installed with a database server.

•

Make sure that the following requirements are met:

 The disk where IMC is installed has been partitioned and formatted.

14

 The other disk that is used for storing iHATool data has 1 GB or more of free space.

•

By default, IMC HAC sets the first server added to the server group as the active server and all

other servers as standby servers.

The following sections describe how to add the first (active) and second (standby) servers to the

server group. To add more standby servers to the group, follow the same procedure.

Installing and configuring IMC HAC on Server 1

1. Register the iMC HAC Server service.

2. On the client, run iHATool, and then select File > Add Server Group.

The Add Server Group dialog box opens.

3. Specify the following server group attributes and server attributes, as shown in Figure 12:

 Group Name—Enter the server group name.

 External Virtual IP Address—Enter the virtual IP address of the server group.

 External IP Address—Enter the external IP address of Server 1.

 Internal IP Address—Enter the internal IP address of Server 1.

 Password—Enter the password used to access the server group. When you create a

server group, you must configure the password as admin. After the server group is created,

you can modify the password.

 Priority—Select a priority for the server. A greater value represents a higher priority.

Figure 12 Adding a server group

4. Click OK.

5. Set disk and database sharing parameters for the server group.

a. Right-click the server group name.

b. From the shortcut menu, select Set Shared Parameters.

The Set Disk and Database Sharing Parameters window opens.

c. Configure the following parameters, as shown in Figure 13:

15

− Mount the Shared Database—Select whether to save the IMC data files to the shared

storage device.

− Mount the Shared Disk—Select whether to place the IMC installation directory at the

shared disk.

− Shared Disk Number—Enter the shared disk number.

− Arbiter Disk Number—Enter the arbiter disk number.

Figure 13 Setting disk and database sharing parameters

6. Click OK.

In the Server Manager on Server 1, you can view the shared disk number, as shown in Figure

14.

16

Figure 14 Viewing the shared disk number

7. Install the database on the local disk of Server 1.

8. Install and deploy IMC.

Make sure the following requirements are met:

 IMC must be installed on the shared disk. For example, if the shared disk is mounted to

Server 1 as disk E, IMC must be installed in the E:\ directory.

 In the Checking Database Connectivity dialog box, Localhost is selected in the

Database Location box during IMC installation.

 By default, the system saves IMC data in the same directory as the IMC installation folder,

which does not have to be modified. For example, if the IMC installation folder is saved in

E:\Program Files\iMC, the system stores IMC data in E:\Program Files\imcdata.

9. Back up the SQL Server master on Server 1 to the shared disk:

a. Open Microsoft SQL Server Management Studio.

b. Log in to SQL Server Management Studio by using a Windows account.

c. On the left navigation tree, select Databases > System Databases.

d. Right-click Master, and then select Tasks > Back Up, as shown in Figure 15.

Page is loading ...