HPE Intelligent Management Center

iHATool Installation Guide

Part number: 5998-6760R

Software version: IMC PLAT 7.3 (E0705)
Document version: 5PW105-20201124
© Copyright 2014, 2020 Hewlett Packard Enterprise Development LP
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.
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

i
Accessing updates ··········································································································································· 91
Websites ·················································································································································· 92
Customer self repair ································································································································· 92
Remote support········································································································································ 92
Documentation feedback ························································································································· 92

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

1
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

Java Disk space Disk space
Collection Online Server
Nodes CPU heap for for data
units operators memory
size installation 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
0 to 10 K 30 4 cores 16 GB 4 GB 3 GB 100 GB
K

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

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

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

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

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

5 K to 10 16
0 to 40 K 50 48 GB 16 GB 7 GB 150 GB
K cores

5 K to 10 16
40 K to 400 K 20 48 GB 16 GB 7 GB 300 GB
K cores

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

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

Table 2 Hardware requirements for 64-bit Linux operating system

Management scale System minimum requirements

Disk
Java Disk space
Collection Online Server space for
Nodes CPU heap for
units operators memory data
size installation
storage
0 to 200 0 to 5 K 20 2 cores 12 GB 4 GB 3 GB 100 GB

2
 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
0 to 10 K 30 4 cores 16 GB 6 GB 3 GB 100 GB
K

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

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

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

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

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

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

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

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

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

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.

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

4
For more information about the firewall setting requirements for IMC installation, see HPE IMC
deployment guides.

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

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

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

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

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

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

11
 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.
Server type:
-servertype master(slave) • master—Management group.
• slave—Managed group.

Language used for HAC installation:

-language en • zh—Chinese.
• en—English.

-country US US—United States.

-dbtype SQLServer(Oracle) Database type.
-dbadminusername sa Database username.
IP address of the local database:
-dbaddress 10.153.88.231(127.0.0.1)
127.0.0.1.

Port used by the database (1433 by

-dbport 1433
default).

Optional. Specifies the instance name of

the SQL server database. You do not
-dbinstance instancename have to specify the option when the
default instance (MSSQLSERVER) is
used.
Optional. Specifies the service name of
the Oracle database. You do not have to
-dbservicename servicename
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

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

13
  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:

14
 − 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.

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

16
 Figure 15 Backing up the master database

CAUTION!
Make sure the shared disk is correctly mounted. Otherwise, the operation fails.

e. Back up the master to the root directory of the shared disk as E:\master.bak, as shown in
Figure 16.

17
 Figure 16 Setting the backup path for master

f. If the system prompts that you do not have rights to save files to the root directory of the
shared disk, create a new folder under the root disk. For example, create the folder tmp,
and then save the master to that folder as E:\tmp\master.bak.
g. Click OK.
10. After backing up the IMC data, 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.
11. In the Windows Task Manager, stop the Intelligent Management Server service and the
MSSQLSERVER service, as shown in Figure 17.

18
 Figure 17 Stopping services

12. Register the HP-iMC-Start service at the IMC installation directory iMC\deploy\.
JavaService.exe -install "HP-iMC-Start" "E:\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 "E:\Program
Files\iMC\deploy" -path "E:\Program Files\iMC\deploy\jdk\bin" -auto -shutdown 300
-startup 30 -description "iMC Startup Controller for Cluster Usage"

NOTE:
The IMC installation directory, E:\Program Files\ in this command, is subject to your actual
environment.

13. Change the startup type of the HP-iMC-Start, Intelligent Management Server, SQL Server,
and SQL Server Agent services to Manual and stop these services.
Installing and configuring IMC HAC on Server 2
1. Register the iMC HAC Server service by running the installer.
2. Add Server 2 to the same group as Server 1 by using iHATool.
a. Run iHATool on the client.
b. Right-click the name of the server group for Server 1, and then select Add Server from the
shortcut menu.
The Add Server dialog box opens.
c. Configure the following parameters, as shown in Figure 18:
− Server Group—Select the server group to which you want to add Server 2.
− External IP Address—Enter the external IP address of Server 2.
− Internal IP Address—Enter the internal IP address of Server 2.

19
 − Password—Enter the password used to access the server group.
− Priority—Select a priority value for Server 2. A greater value represents a higher
priority.
Figure 18 Adding Server 2 to the server group through iHATool

3. Click OK.
4. Open the Sql Server Configuration Manager and delete any existing database files.
5. Stop the database services, as shown in Figure 19.
Figure 19 Stopping the database service

6. Mount the shared disk to the server by executing the sqlservr –m command.
If you use a named instance in SQL Server, execute the sqlservr –m -s instancename
command. Replace instancename with the actual instance name.
The system might prompt that sqlservr is not recognized as an internal or external
command, operable program or batch file, as shown in Figure 20.

20
 Figure 20 Invalid sqlservr -m command

Use either of the following methods to fix this problem:

 Add the path for sqlservr.exe to the system environment variables.
 Enter the C:\Program Files\Microsoft SQL Server\MSSQL \Binn directory, and then
execute the sqlservr –m command.
You can locate the directory for the sqlservr commands by searching for the sqlservr.exe
file.
The default directory is C:\Program Files\Microsoft SQL Server\MSSQL \Binn.
The command is successfully executed, as shown in Figure 21.
Figure 21 sqlservr -m command output

7. Open a new CLI window, and then restore the master database.
osql –E
restore database master from disk='E:\master.bak’ with replace
go
Replace the database backup path E:\ in the command according to your actual environment.
Figure 22 shows the CLI when the master database is successfully restored.

21
 Figure 22 Restoring database master

8. Run SQL Server Management Studio. Log in to the database by using the sa account, and
then delete the administrator account that contains the computer name, as shown in Figure 23.

22
 Figure 23 Deleting the administrator account

9. In the confirmation dialog box, click OK.

10. Create a new administrator account, as shown in Figure 24:
a. Right-click Login and select New Login from the shortcut menu.
b. Click Search.
The Select User or Group dialog box opens.
c. Enter administrator as the object name to select.
d. Click OK.

23
 Figure 24 Creating an administrator account

e. Click Server Roles.

The right pane displays a list of server roles.
f. Select sysadmin and click OK, as shown in Figure 25.
On the left navigation tree, the new administrator account is displayed under the Logins
node.

24
 Figure 25 Creating an administrator account

11. Exit SQL Server Management Studio.

12. In the Windows Task Manager, stop the MSSQLSERVER service.
13. On Server 2, install IMC at the \iMC\deploy directory.
svcinst.bat -install -instdir "E:\Program Files\iMC" -datadir "E:\Program
Files\imcdata" -servertype master -language zh -country CN -dbtype SQLServer
-dbadminusername sa -dbadminpasswd iMC123 -dbaddress 127.0.0.1 -dbport 1433
-dbinstance instancename
For this command, the parameter values are subject to the actual environment. If you use the
default instance of the database, you do not have to enter the -dbinstance option and value.
For the command parameter descriptions, see Table 5.
If the system prompts you that IMC is already installed on the server, delete the iMC-Reserved
directory folder at C:\Windows\, and then re-execute the command.
IMC is successfully installed on Server 2, as shown in Figure 26.
Figure 26 IMC successfully installed

25
 14. At the IMC installation directory \iMC\deploy, register the HP-iMC-Start service.
JavaService.exe -install "HP-iMC-Start" "E:\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 "E:\Program
Files\iMC\deploy" -path "E:\Program Files\iMC\deploy\jdk\bin" -auto -shutdown 300
-startup 30 -description "iMC Startup Controller for Cluster Usage"
The IMC installation directory, E:\Program Files\ in this command, is subject to your actual
environment.
15. Change the startup type of the HP-iMC-Start, Intelligent Management Server, SQL Server,
and SQL Server Agent 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. Upgrade IMC on the active server.
3. Perform the following tasks on each standby server:
a. Back up master.bak to the standby server, as shown in Figure 15.
b. Start the MSSQLSERVER service on the server, clear the database, and then stop the
MSSQLSERVER service.
c. Restore master.bak on the standby server. See "Installing and configuring IMC HAC on
Server 2."
4. In iHATool, set the HA mode to Operating.

Centralized deployment with DBMan for data synchronization

Figure 27 shows a centralized deployment network with local databases. DBMan is used to
synchronize database files and configuration files from the active server to the standby server.
Figure 27 Network diagram

Installation considerations
• To use DBMan to synchronize IMC data between the active the standby servers, add
usedbman = true to the iHATool configuration file, server\imf\server\conf\hac\hac.conf,

26
 before you install iHATool on each server. If iHATool is already installed, restart the iMC HAC
Server service and then edit the iHATool configuration file on each server.
• To use DBMan to synchronize data between IMC servers that use remote databases, you must
install DBMan on the remote databases.
In this example, the IMC servers use local databases.
• Because the communication between HAC and IMC DBMan requires encryption, you must
copy the IMC files iMC\common\conf\ks.dat and iMC\server\conf\imchw.conf to the
server\imf\server\bin directory of iHATool.
Installing and configuring IMC HAC on Server 1
1. Perform steps 1 through 5 as described in "Installing and configuring IMC HAC on Server 1."
Follow these guidelines:
 If the IMC server uses a local database, in the Checking Database Connectivity dialog
box, specify the local database for the server.
 If the IMC server uses a remote database, you must perform the following tasks:
− Before IMC installation, install a database client that is the same version as the remote
database on the server.
− In the Checking Database Connectivity dialog box, specify the remote database used
by Server 1.
In this example, IMC uses a local database.
2. After registering the HP-iMC-Start service, start IMC. Use a browser to access the IMC login
page, and then click the Activate link on the page to activate the license. Make sure the license
contains the IMC platform authorization and iHA authorization.
3. In the Intelligent Deployment Monitoring Agent dialog box, click the Environment tab, as
shown in Figure 28.
Figure 28 Environment tab

4. Click Configure.

27
 The Auto Backup and Recovery Settings page opens.
5. Select Auto Backup Model and configure the following parameters, as shown in Figure 29:
a. Set Daily Backup Time (HH:mm) to 04:00 am.
b. In the Master Server IP of Backup System field, enter the IP address of the Server 2.
c. Set the Storage Path of Other Files to C:\dbmanbak.
d. In the Databases to Back Up list, select all databases in the Upload To Backup System
column.
Figure 29 Configuring Auto Backup settings

6. Click OK.
7. Click Auto Restore Model and configure the following parameters, as shown in Figure 30:
a. Set the Backup files location to C:\dbmanrestore.
b. In the Databases to Restore list, select all databases in the Restore column.

28
 Figure 30 Configuring Auto Restore settings

8. Click OK.
9. 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.
Installing and configuring IMC HAC on Server 2
1. Register the iMC HAC Server service by running the installer.
2. Add Server 2 to the same group as Server 1 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. Configure the following parameters, as shown in Figure 31:
− Server Group—Select the server group for Server 2.
− External IP Address—Enter the external IP address of Server 2.

29
 − 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 value for Server 2. A greater value represents a higher
priority.
Figure 31 Adding Server 2 to the server group

3. Click OK.
4. On Server 2, install and deploy IMC in centralized mode. Specify a local or remote database
other than the database used by Server 1. For more information, see HPE IMC deployment
guides.
5. In the Intelligent Deployment Monitoring Agent dialog box, click the Environment tab, as
shown in Figure 28.

30
 Figure 32 Environment tab

6. Click Configure.
The Auto Backup and Recovery Settings page opens.
7. Select Auto Backup Model and configure the following parameters, as shown in Figure 29:
a. Set Daily Backup Time (HH:mm) to 04:00 am.
b. In the Master Server IP of Backup System field, enter the IP address of the Server 1.
c. Set the Storage Path of Other Files to C:\dbmanbak.
d. In the Databases to Back Up list, select all databases in the Upload To Backup System
column.

31
 Figure 33 Configuring Auto Backup settings

8. Click OK.
9. Click Auto Restore Model and configure the following parameters, as shown in Figure 30:
a. Set the Backup files location to C:\dbmanrestore.
b. In the Databases to Restore list, select all databases in the Restore column.

32
 Figure 34 Configuring Auto Restore settings

10. Click OK.

11. 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.
12. Change the startup type of the HP-iMC-Start and Intelligent Management Server services to
Manual and stop these services.

Deploying IMC and installing IMC HAC on Linux

Centralized deployment with a remote database
Figure 35 shows a centralized deployment network with a remote database.

33
 Figure 35 Network diagram

Installation considerations
• Deploy each server in the server group with the same set of IMC components so that they can
provide redundancy for each other.
• Install the database on a remote server. For installation procedures, see Oracle 11g R2
Installation and Configuration Guide.
• After the IMC HAC configuration is complete on the active and standby servers, install
inotify-tools, rsync, 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."
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 imchacs service as shown in Figure 36, and then start the service.
Figure 36 Registering the imchacs service

34
2. Add Server 1 to the server group by using iHATool.
a. Run iHATool on the client.
b. Select File > Add Server Group.
The Add Server Group dialog box opens.
c. Configure the following parameters, as shown in Figure 37:
− 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 Server 1. A greater value represents a higher priority.
d. Click OK.
Figure 37 Adding a server group

3. Install and deploy IMC in centralized mode on the server and specify the remote database. See
HPE IMC deployment guides.
Before the IMC installation, install a database client that is the same version as the remote
database on the server.
After IMC is installed, the imcdmsd service starts to run on the server.
4. Change the startup type of the imcdmsd service to Manual by executing the chkconfig --level
2345 imcdmsd off command, as shown in Figure 38.

35
 Figure 38 Changing the startup type of the service to Manual

5. After changing the startup type of the imcdmsd 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.
6. Stop the imcdmsd service by executing the service imcdmsd stop command.
Installing and configuring IMC HAC on Server 2
1. Register the imchacs service.
2. 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 39:
− Server Group—Select the server group to which you want to add Server 2.
− 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.

36
 Figure 39 Adding Server 2 to the server group

d. Click OK.
3. Perform the database installation preparations as described in Oracle 11g R2 Installation and
Configuration Guide, and then install a database client on the server.
Make sure the environment variables and the database user account are correct. For more
information, see Oracle 11g R2 Installation and Configuration Guide.
4. In the $ORACLE_HOME/network/admin directory on Server 2, modify the tnsnames.ora file
to match the tnsnames.ora file on Server 1.
5. Copy the /opt/iMC folder generated on Server 1 during IMC installation to the same directory on
Server 2 by executing the scp –r 10.153.147.70:/opt/iMC /opt command, as shown in Figure
40.

37
 Figure 40 Copying the IMC folder

After the IMC installation is complete, the imcdmsd service starts to run on the server.
6. On Server 2, install IMC to the /opt/iMC/deploy directory, as shown in Figure 41.
./svcinst.sh -install -instdir "/opt/iMC" -datadir "/opt/iMC" -servertype master
-language zh -country CN -dbtype Oracle -dbadminusername sys -dbadminpasswd oracle
-dbaddress 10.153.147.86 -dbport 1521 -dbservicename servicename
The values for -dbaddress and -dbport (in this example, 10.153.147.86 and 1521) are subject
to the actual environment. If you use the default service name of the database, you do not have
to enter the -dbservicename option and value.
For the command parameter description, see Table 5.
Figure 41 Installing IMC on Server 2

After the IMC installation is complete, the mcdmsd service starts to run on the server.
7. Change the startup type for the imcdmsd service to Manual by executing the chkconfig
--level 2345 imcdmsd off command.
8. Stop IMC.
9. Stop the imcdmsd service by executing the service imcdmsd stop command.

38
Upgrading IMC HAC servers
To upgrade IMC when IMC HAC is implemented:
1. In iHATool, set the HA mode to Configuration.
2. On the active and all 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 for the active server to the same directory on all standby
servers.
6. On the active and all standby servers, start the realtime synchronization service.
7. In iHATool, set the HA mode to Operating.

Centralized deployment on shared storage

Figure 42 shows a centralized deployment network on shared storage.
Figure 42 Network diagram

Installation considerations
• IMC is installed on the shared storage and the database files are also 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.
 The 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 active and 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 imchacs service and start the service.

39
2. On the client, run iHATool, and select File > Add Server Group.
The Add Server Group dialog box opens.
3. Add Server 1 to the server group by using iHATool, as shown in Figure 43.
a. Configure the following server group attributes and server attributes:
− 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 43 Adding a server group

b. Click OK.
4. Set the disk and database shared parameters for the server group by using through iHATool.
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, as shown in Figure 44.

40
 Figure 44 Setting disk and database sharing parameters

c. Configure the following parameters:

− 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 on the
shared disk.
− Storage Device—Enter the location of the shared storage device. To view the path of
the shared disk, execute the fdisk –l command on Server 1, as shown in Figure 45.
− Mounting Directory—Enter the directory for mounting the shared disk.
− Arbiter Device—Enter the location of the arbiter device.
d. Click OK.

41
 Figure 45 Viewing the disk path

5. Mount the shared disk to the server, and then start the database listener and the database.
6. On Server 1, install and deploy IMC.
Save the IMC installation files, the IMC installation directory, and the database files to the
shared disk.
7. After the deployment of IMC components on Server 1, 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. Stop the database.
9. Stop the database listener by executing the command lsnrctl stop, as shown in Figure 46.

42
 Figure 46 Stopping the database listener and the database

10. Change the startup type of the imcdmsd service to manual startup by executing the chkconfig
--level 2345 imcdmsd off command.
11. Stop the imcdmsd service.
Installing and configuring IMC HAC on Server 2
1. Register the imchacs service.
2. Add Server 2 to the same group as Server 1 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. Configure the following parameters, as shown in Figure 47:
− Server Group—Select the server group to which you want to add Server 2.
− 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 value for Server 2. A greater value represents a higher
priority.

43
 Figure 47 Adding Server 2 to the server group

d. Click OK.
3. Perform the preparations for installing the database.
Make sure the environment variables and the database user account are correct. For more
information, see Oracle 11g R2 Installation and Configuration Guide.
4. In the $ORACLE_HOME/network/admin directory on Server 2, modify the tnsnames.ora file
to match the tnsnames.ora file on Server 1.
5. Mount the shared disk to the server.
6. Install IMC to the /iMC/deploy directory on the shared storage where Server 2 is mounted.
./svcinst.sh -install -instdir "/opt/iMC" -datadir "/opt/iMC" -servertype master
-language zh -country CN -dbtype Oracle -dbadminusername sys -dbadminpasswd oracle
-dbaddress 127.0.0.1 -dbport 1521 -dbservicename _servicename
The parameter values of this command are subject to the actual environment. If you use the
default service name of the database, you do not have to enter the -dbservicename option and
value.
For the command parameter description, see Table 5.
The system might prompt that IMC is already installed, as shown in Figure 48.
Figure 48 IMC installed on the server

Enter the /etc directory to delete the iMC-Reserved folder, and then re-execute the command,
as shown in Figure 49.

44
 Figure 49 Deleting the iMC-Reserved folder

After IMC is successfully installed, the imcdmsd service starts to run on the server.
7. Change the startup type for the imcdmsd service to Manual by executing the chkconfig
--level 2345 imcdmsd off command.
8. Stop the imcdmsd service.
Upgrading IMC HAC servers
To upgrade IMC when IMC HAC is implemented:
1. In iHATool, set the HA mode to Configuration.
2. Upgrade IMC on the active server.
3. In iHATool, set the HA mode to Operating.

Centralized deployment with DBMan for data synchronization

Figure 50 shows a centralized deployment network with local databases. DBMan is used to
synchronize database files and configuration files from the active server to the standby server.
Figure 50 Network diagram

Installation considerations
• To use DBMan to synchronize data between the active the standby servers, add usedbman =
true to the iHATool configuration file server\imf\server\conf\hac\hac.conf before you install
iHATool on each server. If iHATool is already installed, restart the iMC HAC Server service and
then edit the iHATool configuration file on each server.
• To use DBMan to synchronize data between IMC servers that use remote databases, you must
install DBMan on the remote databases.
In this example, the IMC servers use local databases.
Installing and configuring IMC HAC on Server 1
1. Register the imchacs service, as shown in Figure 51.

45
 Figure 51 Registering the imchacs service

2. Add Server 1 to the server group by using iHATool.

IMC HAC sets the first server added to a server group as the active server and other servers as
standby servers.
a. Run iHATool on the client.
b. Select File > Add Server Group.
The Add Server Group dialog box opens.
c. Configure the following parameters, as shown in Figure 52:
− 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 Server 1. A greater value represents a higher priority.
IMC HAC automatically sets the first server (Server 1) added to a server group as the active
server and other servers as standby servers.

46
 Figure 52 Adding Server 1 to a server group

d. Click OK.
3. Install and deploy IMC in centralized mode on the server:
If the IMC server uses a remote database, install a database client that is same version as the
remote database before you install IMC on the server.
In this example, the IMC server uses a local database.
After IMC is installed, the imcdmsd service starts to run on the server.
4. Change the startup type of the imcdmsd service to manual startup by executing the chkconfig
--level 2345 imcdmsd off command, as shown in Figure 53.
Figure 53 Changing the startup type of the imcdmsd service

5. Start IMC. Use a browser to access the IMC login page, and then click the Activate link to
activate the license. Make sure the license contains the IMC platform authorization and iHA
authorization.
6. Start the Intelligent Monitoring Agent, and then click the Environment tab.
7. Click Configure.

47
8. In the Auto Backup and Recovery Settings window, click Auto Backup Model and configure
the following parameters on the Basic Configuration tab, as shown in Figure 54:
a. Set Daily backup time (HH:mm) to 04:00.
b. In the Master Server IP of Backup System field, enter the IP address of the Server 2..
c. Set the Storage path of Other Files to /opt/dbmanbak.
d. In the Databases to Back Up list, select all databases in the Upload To Backup System
column.
9. Click OK.
Figure 54 Configuring auto backup settings

10. Click Configure.

11. In the Auto Backup and Recovery Settings window, click Auto Restore Model and configure
the following parameters, as shown in Figure 55:
a. Set the Backup files location to /opt/dbmanrestore.
b. Select all databases in the Restore column.

48
 12. Click OK.
Figure 55 Configuring auto restore settings

13. Stop IMC on Server 1.

14. Execute the service imcdmsd stop command to stop the imcdmsd service.
Installing and configuring IMC HAC on Server 2
1. Register the imchacs service, and then start the service.
2. Add Server 2 to the server group for Server 1 by using iHATool:
a. Run iHATool on the client.
b. On the navigation tree, right-click the server group name and select Add Server from the
menu.
The Add Server dialog box opens.
c. Configure the following parameters, as shown in Figure 56:
− Server Name—Select the server group to which you want to add server 2.

49
 − 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 the Server 2. A greater value represents a higher priority.
Figure 56 Adding Server 2 to the server group

3. Click OK.
4. Prepare for installing the database.
Make sure the environment variables and the database user account are correct. For more
information, see Oracle 11g R2 Installation and Configuration Guide.
5. In the $ORACLE_HOME/network/admin directory on Server 2, modify the tnsnames.ora file
to match the tnsnames.ora file on Server 1.
6. Copy the /opt/iMC folder generated on Server 1 during IMC installation to the same directory on
Server 2 by executing the scp –r 10.153.147.70:/opt/iMC /opt command, as shown in Figure
57.

50
 Figure 57 Copying the IMC folder

7. Install IMC to the /opt/iMC/deploy directory on Server 2.

./svcinst.sh -install -instdir "/opt/iMC" -datadir "/opt/iMC" -servertype master
-language zh -country CN -dbtype Oracle -dbadminusername sys -dbadminpasswd oracle
-dbaddress 127.0.0.1 -dbport 1521 -dbservicename servicename
The parameter values of this command are subject to the actual environment.
If you use the default service name of the database, you do not have to enter the
-dbservicename option and value.
For the command parameter descriptions, see Table 5.
Figure 58 shows the CLI when IMC is successfully installed on Server 2. After the IMC
installation is complete, the imcdmsd service starts to run on the server.
Figure 58 Installing IMC on Server 2

8. Change the startup type of the imcdmsd service to manual startup by executing the chkconfig
--level 2345 imcdmsd off command.
9. Start the Intelligent Monitoring Agent, and then click the Environment tab.
10. Click Configure.

51
11. In the Auto Backup and Recovery Settings window, click Auto Backup Model and configure
the following parameters on the Basic Configuration tab, as shown in Figure 54:
a. Set Daily backup time (HH:mm) to 04:00.
b. In the Master Server IP of Backup System field, enter the IP address of the Server 1.
c. Set the Storage path of Other Files to /opt/dbmanbak.
d. In the Databases to Back Up list, select all databases in the Upload To Backup System
column.
12. Click OK.
Figure 59 Configuring auto backup settings

13. Click Configure.

14. In the Auto Backup and Recovery Settings window, click Auto Restore Model and configure
the following parameters, as shown in Figure 55:
a. Set the Backup files location to /opt/dbmanrestore.
b. Select all databases in the Restore column.

52
15. Click OK.
Figure 60 Configuring auto restore settings

16. Stop IMC.

17. Execute the service imcdmsd stop command to stop the imcdmsd service.

53
Installing IMC HAC and deploying standby
servers for an IMC server
This chapter describes how to install IMC HAC and deploy standby servers for a running IMC server.
This task uses the same procedures as "Deploying an IMC system and installing IMC HAC", except
that you do not need to install the database and deploy IMC on the active server.
Before proceeding with these steps, make sure IMC has been activated by using a correct license.
Make sure the license contains the IMC platform authorization and iHA authorization.

Installing IMC HAC and deploying standby

servers on Windows
Centralized deployment with a remote database
Figure 61 shows a centralized deployment network with a remote database.
Figure 61 Network diagram

Installation considerations
• Before you install IMC, install the database on a remote server. 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.

54
 • Before you register the HP-iMC-Start service, identify whether the service is already running on
the server. If it is, execute the sc delete "HP-iMC-Start" command at the CLI to delete the
service.
• After the IMC HAC configuration is complete on the active and standby servers, install software
cwRsyncServer and imcsync 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."
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. On Server 1, stop the iMC and Intelligent Management Server services.
2. Register the iMC HAC Server service by running the installer, as shown in Figure 62.
Figure 62 Registering the iMC HAC Server service

3. On the client, run iHATool to add Server 1 to the server group (see step 3 in "Installing and
configuring IMC HAC on Server 1").
4. Register the HP-iMC-Start service on the IMC installation directory iMC\deploy.
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"
The IMC installation path (C:\Program Files\ in this example) is subject to your actual
environment.
Figure 63 shows the command output when the service is successfully registered.

55
 Figure 63 Registering the HP-iMC-Start service

5. 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 64.
Figure 64 Changing the service startup type

Installing and configuring IMC HAC on Server 2

For installation procedures, see "Installing and configuring IMC HAC on Server 2."

Centralized deployment on shared storage

Figure 65 shows a centralized deployment network on shared storage.

56
 Figure 65 Network diagram

Installation considerations
• IMC is installed on the shared storage and the database files are also 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.
 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 in the group, follow the same procedure.
Installing and configuring IMC HAC on Server 1
1. On Server 1, stop the iMC and Intelligent Management Server services.
2. Register the iMC HAC Server service by running the installer, and then start the service.
3. On the client, run iHATool to add Server 1 to the server group, and then configure server group
and shared storage settings (see steps 3 and 4 in "Installing and configuring IMC HAC on
Server 1").
4. On Server 1, run SQL Server Management Studio to back up the master database.
5. Follow steps 7 through 12 in "Installing and configuring IMC HAC on Server 1" to finish the
configuration on Server 1.
Installing and configuring IMC HAC on Server 2
For installation procedures, see "Installing and configuring IMC HAC on Server 2."

Centralized deployment with DBMan for data synchronization

For installation procedures, see "Centralized deployment with DBMan for data synchronization."
Skip the steps for installing the database and deploying IMC on the active server.

57
Installing IMC HAC and deploying standby
servers on Linux
Centralized deployment with a remote database
Figure 66 shows a centralized deployment network with a remote database.
Figure 66 Network diagram

Installation considerations
• Deploy each server in the server group with the same set of IMC components so that they can
provide redundancy for each other.
• Install the database on a remote server. For installation procedures, see Oracle 11g R2
Installation and Configuration Guide.
• After the IMC HAC configuration is complete on the active and standby servers, install software
inotify-tools, rsync, and imcsync 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."
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. On Server 1, stop iMC and stop the imcdmsd service by executing the service imcdmsd stop
command.
2. Register the imchacs service as shown in Figure 67, and then start the service.

58
 Figure 67 Registering the imchacs service

3. On the client, run iHATool and select File > Add Server Group.
The Add Server Group dialog box opens.
4. Specify the server group attributes and server attributes, as shown in Figure 68. For more
information, see step 2 in "Installing and configuring IMC HAC on Server 1."
Figure 68 Adding a server group through iHATool

5. Change the startup type of the imcdmsd service to manual startup by executing the chkconfig
--level 2345 imcdmsd off command, as shown in Figure 69.

59
 Figure 69 Changing the startup type of the service to Manual

Installing and configuring IMC HAC on Server 2

For installation procedures, see "Installing and configuring IMC HAC on Server 2."

Centralized deployment on shared storage

Figure 70 shows a of centralized deployment network on shared storage.
Figure 70 Network diagram

Installation considerations
• IMC is installed on the shared storage and the database files are also 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.
 The other disk that is used for storing iHATool data has 1 GB or more of free space.
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.

60
Installing and configuring IMC HAC on Server 1
1. On Server 1, stop iMC and stop the imcdmsd service by executing the service imcdmsd stop
command.
2. Register the imchacs service, and then start the service.
3. On the client, run iHATool to add Server 1 to the server group and configure server group and
shared storage settings (see steps 3 and 4 in "Installing and configuring IMC HAC on Server
1").
4. Stop the database listener and the database by executing the lsnrctl stop command, as shown
in Figure 71.
Figure 71 Stopping the database listener and the database

5. Change the startup type of the imcdmsd service to manual startup by executing the chkconfig
--level 2345 imcdmsd off command.
6. Stop the imcdmsd service.
7. Dismount the shared disk from the server.
Installing and configuring IMC HAC on Server 2
For installation procedures, see "Installing and configuring IMC HAC on Server 2."

Centralized deployment with DBMan for data synchronization

For installation procedures, see "Centralized deployment with DBMan for data synchronization."
Skip the steps for installing the database and deploying IMC on the active server.

61
Synchronizing configuration files from the
active server to standby servers in real
time
When both IMC and database files reside on the shared storage, the standby server automatically
takes over the failed active server by using the stored configuration files and database files.
When IMC is installed and deployed locally on each IMC server, the configuration files of the active
server must be synchronized to standby servers in real time. Otherwise, configurations made to the
active sever are lost when a standby server takes over.
You can use third-party software to synchronize configuration files from the active server to standby
servers in real time.
The third-party software used varies with the operating system on which IMC runs:
• On Linux, use inotify-tools and rsync.
• On Windows, use cwRsyncServer.

Synchronizing configuration files on Linux

Prerequisites
Before you configure realtime synchronization of configuration files from the active server to standby
servers, complete the following tasks:
• Install iHATool and IMC.
The IMC installation information is required when you install inotify-tools and rsync.
• Verify whether your kernel version supports inotify by executing the uname –r command.
inotify is supported on Linux kernel 2.6.13 or later. If an early version is used, you must
recompile the Linux kernel to support inotify.
• Open rsync port 873 in the Linux firewall or disable the firewall.

Installing inotify-tools
Install inotify-tools on the active server and all standby servers in the same server group.
To install inotify-tools on a server:
1. Download and store the source code file for inotify-tools on the Linux server.
This example uses the inotify-tools-3.14.tar.gz source code file.
2. Log in as root. In the Linux terminal window, enter the directory where the inotify-tools source
code file is stored.
3. Decompress the source code file, as shown in Figure 72.
tar zxvf inotify-tools-3.14.tar.gz

62
 Figure 72 Decompressing the tar.gz file

4. Enter the inotify-tools-3.14 directory, as shown in Figure 73.

cd inotify-tools-3.14

Figure 73 Entering the inotify-tools-3.14 directory

5. Configure the installation directory for inotify-tools.

./configure --prefix=/directory
The --prefix=/directory string specifies the installation directory. If the command is executed
without the --prefix=/directory string, the default installation directory is used.
This example uses the default installation directory, as shown in Figure 74.

63
 Figure 74 Configuring the installation directory for inotify-tools

6. Compile inotify-tools, as shown in Figure 75.

make

Figure 75 Compiling inotify-tools

7. Install inotify-tools, as shown in Figure 76.

64
 make install

Figure 76 Installing inotify-tools

Installing rsync
Install rsync on the active server and all standby servers in the same server group.
To install rsync on a server:
1. Download and store the rsync source code file of rsync on the IMC server.
This example uses the rsync-3.10.tar.gz source code file.
2. Log in as root. In the Linux terminal window, enter the directory where the rsync source code
file is stored.
3. Decompress the file, as shown in Figure 77.
tar zxvf rsync-3.1.0.tar.gz

65
 Figure 77 Decompressing the tar.gz file

4. Enter the rsync-3.1.0 directory, as shown in Figure 78.

cd rsync-3.1.0

Figure 78 Entering the rsync directory

5. Configure the rsync installation directory.

66
 ./configure --prefix=/directory
The --prefix=/directory string specifies the installation directory. If the command is executed
without the --prefix=/directory string, the default installation directory is used.
This example uses the default installation directory, as shown in Figure 79.
Figure 79 Configuring the rsync installation directory

6. Compile rsync, as shown in Figure 80.

make

67
 Figure 80 Compiling rsync

7. Install rsync, as shown in Figure 81.

make install

Figure 81 Installing rsync

8. Create the rsync configuration file in the /etc directory, as shown in Figure 82.

68
 cd /etc
touch rsyncd.conf

Figure 82 Creating the rsync configuration file

9. Edit the rsync configuration file according to the IMC installation directory and the active and
standby server settings. In this example, IMC is installed in the /opt/iMC directory and the file
rsyncd.conf is as follows:

10. Configure rsync to run as a daemon process, as shown in Figure 83.

/usr/local/bin/rsync --daemon

Figure 83 Configuring rsync to run as a daemon

69
 11. Add rsync to the automatic boot file, as shown in Figure 84.
echo "/usr/local/bin/rsync --daemon" >>/etc/rc/local
The rsync service will automatically start up as a daemon process on Linux startup.
Figure 84 Starting rsync with Linux

Installing imcsyncs
1. Copy the imcsyncs installation package (the sync folder) from the \server\linux\tool\ directory
in the iHATool.zip file to the IMC server.
2. Set the executable permissions for the install.sh and uninstall.sh scripts, and then install
imcsyncs on the server, as shown in Figure 85.
Figure 85 Installing the imcsyncs service

70
Synchronizing configuration files on Windows
Prerequisites
Before you configure realtime synchronization of configuration files from the active server to standby
servers, complete the following tasks:
• Install iHATool and IMC.
The IMC installation information is required when you install cwRsyncServer.
• Obtain the cwRsyncServer installation package from website:
http://www.backupassist.com/rsync/
This example uses cwRsyncServer_4.2.0_Installer.exe.

Installing cwRsyncServer
On the active server and all standby servers, install cwRsyncServer in the same server group.
To install cwRsyncServer on a server:
1. Log in to Windows with administrator privileges.
2. Store the cwRsyncServer_4.2.0_Installer.exe file on the IMC server and double-click the file.
The cwRsyncServer_4.2.0 Setup Wizard opens, as shown in Figure 86.
Figure 86 Installing cwRsyncServer

3. Click Next.
The License Agreement window opens, as shown in Figure 87.

71
 Figure 87 License Agreement

4. Click I Agree.
The Choose Install Location window opens.
5. Specify the destination folder, as shown in Figure 88.
Figure 88 Choose Install Location

72
6. Click Next.
The Service Account window opens, as shown in Figure 89.
Figure 89 Service Account

7. Set the service account to administrator and specify a password.

8. Click Install.
The Installation Complete window opens, as shown in Figure 90.

73
 Figure 90 Installation Complete

9. Click Close.
10. Open the Run dialog box and enter services.msc.
The Service window opens.
11. Right-click the RsyncServer service and select Properties from the shortcut menu, as shown
in Figure 91.

74
 Figure 91 RsyncServer service

12. On the General tab of the Properties dialog box, set the service startup up type to automatic,
as shown in Figure 92.
Figure 92 Setting the startup type for RsyncServer

75
 13. Click the Login tab, select Local System Account, and click OK, as shown in Figure 93.
Figure 93 Modifying the service account

14. Start the RsyncServer service after installing imcsyncs.

Installing imcsyncs
1. Copy the imcsyncs installation package (the sync folder) from the \server\windows\tool\
directory in the iHATool.zip file to the IMC server and enter the directory.
This example uses E:\share\rsync\windows.
2. Install imcsyncs on the server.
install.bat "C:\Program Files (x86)\ICW\bin"
The C:\Program Files (x86)\ICW\bin string represents the bin directory under the installation
directory for cwRsyncServer, as shown in Figure 94.

76
 Figure 94 Realtime synchronization service

3. Press any key to continue after iMC RsyncServer is automatically installed.

4. Modify the service account:
a. Right-click the iMC RsyncServer service and select Properties from the shortcut menu, as
shown in Figure 95.
b. On the Log On tab of the iMC RsyncServer Properties window, enter administrator in
the This account field, enter a password, and click OK, as shown in Figure 96.
Figure 95 iMC RsynServer service
无法显示链接的图像。该文件可能已被移动、重命名或删除。请验证该链接是否指向正确的文件和位置。

77
 Figure 96 Modifying the logon account
无法显示链接的图像。该文件可能已被移动、重命名或删除。请验证该链接是否指向正确的文件和位置。

Starting the RsyncServer service

1. Replace the rsyncd.conf file with the following file in directory C:\Program Files (x86)\ICW.

2. In the rsyncd.conf file, edit the path value according to the IMC installation path.
In this example, IMC is installed in the E:\Program Files\iMC directory. You must set the path
value to path = /cygdrive/E/Program Files/iMC/… , as shown in Figure 97.

78
 Figure 97 Editing the rsyncd configuration file

3. In the run.bat file in the in directory C:\Program Files (x86)\ICW, edit the iMCRoot value
according to the IMC installation path.
In this example, IMC is installed in the E:\Program Files\iMC directory. You must set the
iMCRoot value to iMCRoot="E:\Program Files\iMC\", as shown in Figure 98.
Figure 98 Editing the run.bat file

79
4. Start the RsyncServer service.

80
Restrictions and guidelines
Using iHATool
To ensure a smooth switchover from the active server to a standby server with a higher priority at the
specified time, perform the following steps:
1. Run iHATool, right-click the name of the target server group, and select Configure
Alarm-Triggered Actions from the shortcut menu, as shown in Figure 99.
Figure 99 Configuring alarm-triggered actions

2. Click Add. The Add Alarm-Triggered Action dialog box opens, as shown in Figure 100.
Select A member device with a higher priority is detected from the Action(*) list, select
HAC Server Role Changing from the Action(*) list, and click OK.
Figure 100 Adding alarm-triggered action

81
3. Configure the following parameters in the Configure Global Parameters window, as shown in
Figure 96.
Make sure a standby server has higher priority than the active server.
 Alarm Lifecycle—Enter the lifecycle for alarms, in the range of 1 to 30 days. By default, the
alarm lifecycle is 7 days. Alarms are cleared automatically when the alarm lifecycle expires.
 Internal Network Connection Type—Select a connection type for the active server and
standby servers. You must enter an internal arbitrator IP address if you select Indirectly
Connected.
 Internal Arbitrator IP Address—Enter an internal arbitrator IP address. As a best practice,
use the internal network gateway IP address as the internal arbitrator IP address.
 Time of Switchover—Enter the time for the system to perform an active and standby
switchover, in the hh:mm format in 24-hour notation. For example, if you set the time to
06:10, the switchover starts at 06:10 in the morning.
 Check Retries—Enter the number of check attempts, in the range of 3 to 10. The default
value is 3. An alarm will be triggered if the system does not detect connectivity between the
active server and standby servers until the maximum check attempt is reached.
 Check Interval—Enter the check interval, in the range of 30 to 600 seconds. By default, the
check interval is 60 seconds.
 Check Timeout—Enter the check timeout, in the range of 1 to 7200 seconds. The default
value is 3600 seconds.
 Action Timeout—Enter the rebuild action timeout, in the range of 1 to 7200 seconds. The
default value is 3600 seconds.
 Rebuild Interval—Enter the interval for server role checks, in the range of 5 to 20 seconds.
By default, the rebuild interval is 5 seconds.
 Reachability Retires—Enter the number of reachability retries, in the range of 3 to 10. The
default value is 3.
 Reachability Check Interval—Enter the interval for reachability checks, in the range of 1 to
3 seconds. The default value is 1 second.
 Heartbeat Retries—Enter the number of heartbeat retries, in the range of 3 to 10. The
default value is 3.
 Heartbeat Check Interval—Enter the interval for heartbeat checks, in the range of 10 to 60
seconds. The default value is 60 seconds.
In running mode, you can view but cannot configure global parameters.

82
 Figure 101 Configuring global parameters

Registering licenses
Follow these restrictions and guidelines during license registration:
• Before authorizing the IMC Platform and iHA, make sure IMC HAC is installed and the HAC
Server service is started. If you install IMC HAC and start the HAC Server service after
authorization, the page gets stuck when you run iHATool on the client to add a server group.
• If no authorization is performed for the IMC Platform or iHA, or the authorization has expired,
the dual-device HA system cannot provide high availability services correctly. To ensure correct
operation of the dual-device HA system, authorize the IMC Platform and iHA at the same time.
• After a node switchover, the master node checks the local license files upon IMC startup. It
sends a message to the iHA cluster service upon detecting mismatching information (IP/MAC).
The iHA service verifies the relationship between license files and nodes in the cluster. If the
master node and license files belong to the same cluster, the verification succeeds, and IMC
login will be successful after startup. (To avoid IMC login failure due to inconsistent license files,
make sure the HAC service and file synchronization service are enabled on the master node.)

Jserver startup failure on the subordinate server

after IMC version upgrade
If IMC is upgraded to iMC PLAT 7.3 (E0703) or a later version and the Jserver process cannot be
started on the subordinate server, use the following methods to resolve this issue:
• In Windows environment, execute the following command under the iMC/client/bin directory of
the subordinate server, as shown in Figure 102.
cacls jmx.password /P administrators:F

83
 Figure 102 Executing the command

• In Linux environment, execute the following command under the iMC/client/bin directory of all
nodes.
Chmod 400 jmx.password

Modifying iHA Server script after IMC service

name is changed
If the name of the IMC service (as shown in Figure 103) is changed after IMC version upgrade, you
must modify the iHA Server script. If you do not modify the iHA Server script, IMC service might fail to
be started upon a node switchover.
Figure 103 IMC service

To modify the iHA Server script:

1. Locate the make_config_file script file as shown in Figure 104, and open it using the text
editor.
Figure 104 make_config_file script file

84
2. Locate the H3C iMC Server and HP iMC Server, as shown in Figure 102.
Figure 105 Locating H3C iMC Server and HP iMC Server

3. Add the configuration as shown in Figure 103.

Figure 106 Adding configuration

85
Upgrading iHATool
1. In iHATool, set the HA mode to Configuration.
2. Stop the iMC HAC Server service on the HAC server, and stop the iMC Sync Server service on
the active server.
3. Decompress the file iHATool.zip in the iHATool installation directory. After the decompression
is complete, copy all files in the \iHATool\server\windows\server\imf\server\bin directory
and the file folder imc-integration to replace files in the
\iHATool\server\windows\server\imf\server\bin directory on the HAC server.
4. Copy all decompressed files in the \iHATool\server\windows\tool\sync\bin directory to the
ICW\bin directory under the cwRsyncServer installation directory on the HAC server. For
example, if the cwRsyncServer is installed on Disk C, the target file directory is C:\Program
Files (x86)\ICW\bin.
5. Start the iMC HAC Server service on the HAC server.
6. Repeat steps 2 to 5 on other HAC servers.
7. In iHATool, set the HA mode to Operating.

86
Uninstalling iHATool
1. On the HAC server, execute the uninstall.bat script in the \iHATool\server\windows directory
of the iHATool installation directory to delete the iMC HAC Server service.
2. Execute the uninstall.bat script in the \iHATool\server\windows\tool\sync directory to delete
the iMC Sync Server service.

87
About HPE IMC documents
The following are the documents available for HPE IMC:

Documents Purpose
Hardware specifications and installation

Quickly guides you through the IMC main features and

HPE IMC Getting Started Guide
troubleshooting common problems.
Provides a complete guide to IMC platform and components
HPE IMC Centralized Deployment Guide
installation and centralized deployment using embedded
with Embedded Database
database.
Provides a complete guide to IMC platform and components
HPE IMC Centralized Deployment Guide
installation and centralized deployment using local
with Local Database
database.
Provides a complete guide to IMC platform and components
HPE IMC Centralized Deployment Guide
installation and centralized deployment using remote
with Remote Database
database.

Provides a complete guide to IMC Probe installation and

HPE IMC Probe Installation Guide
deployment.

Provides a complete guide to IMC RSM installation and

HPE IMC RSM Installation Guide
deployment.
HPE IMC iHATool Installation Guide Provides a complete guide to IMC iHATool installation.
SQL Server 2008 Installation and
Guides you through installing SQL Server 2008 for IMC.
Configuration Guide
SQL Server 2008 R2 Installation and
Guides you through installing SQL Server 2008 R2 for IMC.
Configuration Guide
SQL Server 2012 Installation and
Guides you through installing SQL Server 2012 for IMC.
Configuration Guide
SQL Server 2014 Installation and
Guides you through installing SQL Server 2014 for IMC.
Configuration Guide
Oracle 11g Installation and Configuration
Guides you through installing Oracle 11g on Linux for IMC.
Guide (for Linux)
Oracle 11g R2 Installation and Configuration Guides you through installing Oracle 11g R2 on Linux for
Guide (for Linux) IMC.
Oracle 12c Installation and Configuration
Guides you through installing Oracle 12c on Linux for IMC.
Guide (for Linux)
MySQL 5.5 Installation and Configuration
Guides you through installing MySQL 5.5 on Linux for IMC.
Guide (for Linux)
MySQL 5.5 Installation and Configuration Guides you through installing MySQL 5.5 on Windows for
Guide (for Windows) IMC.
MySQL 5.6 Installation and Configuration
Guides you through installing MySQL 5.6 on Linux for IMC.
Guide (for Linux)
MySQL 5.6 Installation and Configuration Guides you through installing MySQL 5.6 on Windows for
Guide (for Windows) IMC.
Red Hat Enterprise Linux 6.4 Installation Guides you through installing Red Hat Enterprise Linux 6.4
Guide for IMC.
Red Hat Enterprise Linux 7.0 Installation Guides you through installing Red Hat Enterprise Linux 7.0

88
Documents Purpose
Guide for IMC.
Software configuration
HPE IMC Enterprise and Standard Platform
Describes operation procedures on the IMC platform.
Administrator Guide
HPE IMC Quality of Service Manager Describes operation procedures on the IMC Quality of
Administrator Guide Service Manager.
HPE IMC Resource Automation Manager Describes operation procedures on the Resource
Administrator Guide Automation Manager.
HPE IMC Service Health Manager Describes operation procedures on the Service Health
Administrator Guide Manager.
HPE IMC VAN Connection Manager Describes operation procedures on the IMC VAN
Administrator Guide Connection Manager.
HPE IMC VAN Software Defined Network Describes operation procedures on the IMC VAN Software
Manager Administrator Guide Defined Network Manager.
HPE IMC VAN Fabric Manager Administrator Describes operation procedures on the IMC VAN Fabric
Guide Manager.
HPE IMC Application Manager Administrator Describes operation procedures on the IMC Application
Guide Manager.
HPE IMC Branch Intelligent Management Describes operation procedures on the IMC Branch
System Administrator Guide Intelligent Management System.
HPE IMC Business Service Performance Describes operation procedures on the IMC Business
Administrator Guide Service Performance.
HPE IMC IPsec VPN Manager Administrator Describes operation procedures on the IMC IPsec VPN
Guide Manager.
HPE IMC MPLS VPN Manager Administrator Describes operation procedures on the IMC MPLS VPN
Guide Manager.
HPE IMC Network Traffic Analyzer Describes operation procedures on the IMC Network Traffic
Administrator Guide Analyzer.
HPE IMC Service Operation Manager Describes operation procedures on the IMC Service
Administrator Guide Operation Manager.
HPE IMC User Behavior Auditor Describes operation procedures on the IMC User Behavior
Administrator Guide Auditor.
Describes operation procedures on the IMC UC Health
HPE IMC UC Health Manager Admin Guide
Manager.
HPE IMC Wireless Service Manager Describes operation procedures on the IMC Wireless
Administrator Guide Service Manager.
HPE IMC User Access Manager Describes operation procedures on the IMC User Access
Administrator Guide Manager.
HPE IMC TACACS+ Authentication Manager Describes operation procedures on the IMC TACACS+
Administrator Guide Authentication Manager.
HPE IMC EAD Security Policy Administrator Describes operation procedures on the IMC EAD Security
Guide Policy Manager.
Online Help Helps you properly use IMC.
Operations and maintenance

Readme Provides most recent IMC release information.

89
Document conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
Command conventions

Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.
# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Description
Window names, button names, field names, and menu items are in Boldface. For
Boldface
example, the New User window opens; click OK.
Multi-level menus are separated by angle brackets. For example, File > Create >
>
Folder.

Symbols

Convention Description
An alert that calls attention to important information that if not understood or followed
WARNING! can result in personal injury.
An alert that calls attention to important information that if not understood or followed
CAUTION: can result in data loss, data corruption, or damage to hardware or software.

IMPORTANT: An alert that calls attention to essential information.

NOTE: An alert that contains additional or supplementary information.

TIP: An alert that provides helpful information.

90
Support and other resources
Accessing Hewlett Packard Enterprise Support
• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
• To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc
Information to collect
• Technical support registration number (if applicable)
• Product name, model or version, and serial number
• Operating system name and version
• Firmware version
• Error messages
• Product-specific reports and logs
• Add-on products or components
• Third-party products or components

Accessing updates
• Some software products provide a mechanism for accessing software updates through the
product interface. Review your product documentation to identify the recommended software
update method.
• To download product updates, go to either of the following:
 Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates
 Software Depot website:
www.hpe.com/support/softwaredepot
• To view and update your entitlements, and to link your contracts, Care Packs, and warranties
with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials

IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HP Passport set up with relevant
entitlements.

91
Websites
Website Link
Networking websites

Hewlett Packard Enterprise Information Library for

www.hpe.com/networking/resourcefinder
Networking
Hewlett Packard Enterprise Networking website www.hpe.com/info/networking
Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support
Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking
Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty
General websites

Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs

Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Services Central ssc.hpe.com/portal/site/ssc/
Contact Hewlett Packard Enterprise Worldwide www.hpe.com/assistance
Subscription Service/Support Alerts www.hpe.com/support/e-updates
Software Depot www.hpe.com/support/softwaredepot
Customer Self Repair (not applicable to all devices) www.hpe.com/support/selfrepair
Insight Remote Support (not applicable to all devices) www.hpe.com/info/insightremotesupport/docs

Customer self repair

Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If
a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your
convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized
service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair

Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or
contractual support agreement. It provides intelligent event diagnosis, and automatic, secure
submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast
and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly
recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs

Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help
us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,

92
part number, edition, and publication date located on the front cover of the document. For online help
content, include the product name, product version, help edition, and publication date located on the
legal notices page.

93