HP Intelligent Management Center v7.1 Centralized Deployment

HP Intelligent Management Center v7.1
Centralized Deployment Guide
with Embedded Database
Abstract
This document describes the processes for deploying the HP Intelligent Management Center. It also includes information on
upgrading, removing, registering, backing up, and restoring IMC. This document is intended for use by network engineers
and system administrators responsible for installing network management software.
Part number: 5998-6768
Published: September 2014
Software Version: IMC PLAT 7.1 (E0302)
Edition: 1.0
Legal and notice information
© Copyright 2014 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP 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.
The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Acknowledgements
Citrix® and XenDesktop® are registered trademarks of Citrix Systems, Inc. and/or one more of its
subsidiaries, and may be registered in the United States Patent and Trademark Office and in other
countries.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft® and Windows® are trademarks of the Microsoft Group of companies.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
VMware®, VMware® vCenter™, VMware vSphere®, and VMware® Enterprise Plus Edition™ are
registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.
ii
Contents
Legal and notice information ·········································································································································· ii
Acknowledgements ·························································································································································· ii
1 Introduction to Intelligent Management Center ········································································································· 1
IMC components ······························································································································································· 1
IMC Platform ····························································································································································· 1
Service components ················································································································································· 1
IMC editions ······································································································································································ 3
2 Preparing for installation ············································································································································· 5
Hardware requirements ···················································································································································· 5
Software requirements ······················································································································································ 6
Setting the Java memory size on 32-bit OS ··················································································································· 7
Installing IMC on a virtual machine ································································································································ 7
Preparing the installation environments ·························································································································· 8
Setting the system time······················································································································································ 8
3 Installation and deployment requirements ···············································································································10
Terms and concepts ······················································································································································· 10
Installation and deployment ································································································································· 10
Checking the installation environment ························································································································· 10
Embedded database restrictions and guidelines ········································································································ 11
4 Installing and deploying the IMC Platform ··············································································································12
Installing the IMC Platform ············································································································································ 12
Typical installation ················································································································································· 13
Custom installation ················································································································································ 17
Deploying the IMC Platform ·········································································································································· 23
Deploying a single IMC component···················································································································· 28
IMC service logon accounts ·········································································································································· 28
5 Installing and deploying IMC service components ·································································································30
Installing IMC NTA ························································································································································ 33
Installing IMC NTA ················································································································································ 33
Deploying IMC NTA ············································································································································· 37
Installing and deploying IMC UAM ····························································································································· 39
Installing and deploying IMC EAD······························································································································· 46
Installing and deploying IMC MVM····························································································································· 49
6 Installing plug-ins ························································································································································52
Installing DHCP plug-ins ················································································································································ 52
Installing DHCP plug-ins on the MS DHCP server ······························································································ 52
Installing DHCP plug-ins on the Linux DHCP server ··························································································· 53
Installing VRM agent plug-ins········································································································································ 54
Installing a VRM Windows agent ························································································································ 54
Installing a VRM Linux agent ································································································································ 55
Installing Android clients ··············································································································································· 56
Installing LLDP agent plug-ins ········································································································································ 57
Installing an LLDP Linux agent ······························································································································ 57
Installing an LLDP Windows agent ······················································································································ 58
iii
7 Logging in to IMC ······················································································································································59
Accessing IMC ······························································································································································· 59
Securing IMC ·································································································································································· 59
Accessing UAM ······························································································································································ 60
Displaying a user agreement ········································································································································ 60
8 Upgrading, backing up, or removing IMC ·············································································································62
Backing up IMC ····························································································································································· 62
Upgrading IMC ······························································································································································ 62
Restoring IMC ································································································································································· 69
Removing IMC ································································································································································ 69
Removing an IMC component ····························································································································· 69
Removing all IMC components at one time ········································································································ 69
9 Registering IMC and incremental node licenses ·····································································································71
Registering IMC ······························································································································································ 71
Registering the first license ··································································································································· 71
Registering incremental node licenses ················································································································ 75
Activating IMC ······························································································································································· 77
Registering the IMC license for stateful/stateless failover·························································································· 77
Registering the IMC license for stateful failover ································································································· 77
Registering the IMC license for stateless failover ······························································································· 79
Upgrading to an IMC V7.1 license ····························································································································· 80
Updating your IMC V7.1 license file ·················································································································· 81
10 Security settings ························································································································································82
Anti-virus software ·························································································································································· 82
Port settings ····································································································································································· 82
11 Database backup and restoration ·························································································································84
Manual backup ······························································································································································ 85
Manual restore ······························································································································································· 85
Automatic backup ·························································································································································· 86
Automatic restore ··························································································································································· 88
Database backup and restore by using DBMan········································································································· 91
Database backup and restore for a single IMC system ···················································································· 91
Database backup and restore in IMC stateless failover···················································································· 91
Configuration guidelines ··············································································································································· 92
12 FAQ ···········································································································································································93
Support and other resources·········································································································································97
Contacting HP ································································································································································ 97
Subscription service ·············································································································································· 97
Related information ························································································································································ 97
Documents ······························································································································································ 97
Websites································································································································································· 97
Conventions ···································································································································································· 98
iv
1 Introduction to Intelligent Management
Center
To facilitate Intelligent Management Center (IMC) installation and deployment, you can deploy IMC in
centralized mode and use the embedded database.
This scales to small networks of less than 40 users and 1000 devices.
IMC components
IMC includes the IMC Platform and service components.
IMC Platform
The IMC Platform is the base component for providing IMC services and includes the following
subcomponents:

ACL Management

Alarm Management

General Search Service Management

Guest Access Management

Intelligent Configuration Center

Network Asset Management

Network Element (NE) Management

Performance Management

Report Management

Resource Management

Security Control Center

Syslog Management

User Self-service Management

Virtual Resource Management

VLAN Management
Service components
Service components are optional and purchased separately from the IMC Platform. Their installation and
deployment are based on the IMC Platform.
Service components are as follows:
1

User Access Manager (UAM)—Provides policy based AAA (Authentication, Authorization and
Accounting) services. UAM software extends management to wired, wireless and remote network
users and enables the integration of network device, user, guest and terminal management on a
single unified platform.

Endpoint Admission Defense (EAD) Security Policy—Endpoint Admission Defense integrates
security policy management and endpoint posture assessment to identify and isolate risks at the
network edge. The security policy component allows administrators to control endpoint admission
based on an endpoint's identity and posture.

MPLS VPN Manager (MVM)—Provides functions such as VPN autodiscovery, topology, monitoring,
fault location, auditing, and performance evaluation, as well as VPN and service deployment.
MVM also contains a traffic engineering component that helps operators monitor an entire network
and deliver service quality by distributing suitable network resources as needed.

IPsec VPN Manager (IVM)—Provides features for all aspects of IPSec VPN management, which
allows administrators to construct an IPSec VPN network, effectively monitor the operation and
performance of the VPN network, and quickly locate device faults for full IPSec VPN lifecycle
management.

Voice Service Manager (VSM)—Provides a solution for reducing the voice network maintenance
cost and improving maintenance efficiency. VSM is designed for enterprise-level voice networks.

Wireless Service Manager (WSM)—Provides unified management of wired and wireless networks,
adding network management functions into existing wired network management systems. WSM
software offers wireless LAN (WLAN) device configuration, topology, performance monitoring, RF
heat mapping, and WLAN service reports.

Network Traffic Analyzer (NTA)—Is a graphical network-monitoring tool with real-time information
about users and applications consuming network bandwidth. A reliable solution for enterprise and
campus network traffic analysis, it defends the network against virus attacks and applies varying
levels of bandwidth traffic to different services and applications.

User Behavior Auditor (UBA)—Provides comprehensive log collection and audit functions
supporting log formats such as NAT, flow, NetStreamV5, and DIG. UBA provides DIG logs to audit
security-sensitive operations and digest information from HTTP, FTP, and SMTP packets.

Service Operation Manager (SOM)—Allows IT organizations to adhere to ITIL v3.0, including IT
services such as policy design, operation, and improvement. Based on a unified configuration
management database (CMDB), SOM provides configurable flows and options for self-service, as
well as management of asset configuration, change, fault events, problem recognition, and
auto-generation of a knowledge base.

Application Manager (APM)—Allows administrators to visualize and measure the health of critical
business applications and their impact on network performance. With the available data,
administrators can easily determine which business process is affected and which application
issues to prioritize—all leading to quick and effective troubleshooting.

QoS Manager (QoSM)—Enhances visibility and control over QoS configurations and helps
administrators focus on QoS service planning by providing a rich set of QoS device and
configuration management functions. It allows administrators to organize traffic into different
classes based on the configured matching criteria to provide differentiated services, committed
access rate (CAR), generic traffic shaping (GTS), priority marking, queue scheduling, and
congestion avoidance.

Service Health Manager (SHM)—Provides visual service quality management functions. It
integrates the alarm, performance, NTA, and NQA data. It uses key quality indexes and service
level agreements to monitor and measure service health.
2

TACACS+ Authentication Manager (TAM)—Provides basic AAA functions for network device or IT
users for network device management security. TAM can assign users with different privileges,
monitor login and command execution operations, and simplify user management.

VAN Connection Manager (VCM)—Provides a solution for physical network configuration
migration. It tracks the startup, stopping, and migration of virtual machines (VMs), and according
to the latest VM location, it deploys a physical network configuration. The VCM allows
collaboration for physical and virtual networks. It also provides compatibility between physical and
virtual networks of different vendors.

Branch Intelligent Management System (BIMS)— Provides support for service operations,
delivering high reliability, scalability, flexibility, and IP investment returns. Based on the TR-069
protocol, IMC BIMS offers resource, configuration, service, alarm, group, and privilege
management. It allows the remote management of customer premise equipment (CPE) in WANs.

Remote Site Manager (RSM)—Securely extends the IMC core platform capability to remote sites by
deploying remote agents. These agents manage and monitor the remote network, and apply
policies and configurations to the remote network devices on behalf of the central IMC server.

Resource Automation Manager (RAM)—Provides a solution for customizing network services for
users and automatically deploying network services.

VAN SDN Manager (SDNM)—Manages OpenFlow-based SDN. SDNM allows you to manage an
OpenFlow network through RESTful APIs provided by HP SDN controllers. Combined with the
device management, reports, and homepage widgets functions in the IMC Base Platform, SDNM
also allows you to perform visual management and monitoring on the OpenFlow network.

VAN Fabric Manager (VFM)—Provides an integrated solution for managing both the LANs and
SANs in data centers by working with HP devices. VFM depends on VRM to obtain virtual machine
(VM) migration information.

Unified Communications Health Manager (UCHM)—Provides a solution for monitoring the health
status of networks deployed with Microsoft Lync Server. It allows you to manage network resources
including the Lync Servers, PSTN gateways, and Lync client endpoints.

Intelligent Analysis Reporter (IAR)—Extends the reporting capabilities within IMC to include
customized reporting. IAR includes a report designer, which can save designs into report templates.
Report outputs include a variety of formats, including charts. Reports can be automatically
generated at specified intervals and distributed to key stakeholders.
For information about all service components, see v7.1 HP Intelligent Management Center Getting
Started Guide.
The IMC Platform is the basis for implementing various services and must be installed before service
component deployment.
IMC editions
The following editions of IMC are available:

Enterprise

Standard

Basic
To deploy IMC in centralized mode and to use the embedded database, you must use the IMC Basic or
Standard edition.
3
Table 1 Differences between IMC editions
Item
Basic
Standard
Enterprise
Number of nodes
1000
Extensible
Extensible
Not supported
Lower-level NMS only
Supported
Operating system
Windows
Windows and Linux
Windows and Linux
Distributed deployment
Not supported
Supported
Supported
Embedded database
Supported
Supported only on
windows
Not supported
Remote database server
Not supported
Supported
Supported
Hierarchical Network
Management
4
2 Preparing for installation
The following information describes IMC installation requirements for both hardware and software.
Hardware requirements
Table 2 and Table 3 use the following terms:

Node—IMC servers, database servers, and devices managed by IMC are called nodes.

Collection unit—Represents a performance instance that is collected every 5 minutes. When a
performance instance uses another collection interval, it corresponds to a number of collection units
calculated with the formula: 5 minutes/instance collection interval in minutes.
For example, the collection interval is set to 10 minutes for all performance instances. A monitored
device contains 1 CPU, 1 memory bar, and 10 interfaces. To collect performance data for CPU,
memory, response time, reachability rate, and interface send and receive rates, the total collection
units of the device are: (1+1+1+1+(10×2))×5/10=12.

CPU1—The CPU must be no less than a Pentium 4 3.0 GHz processor.

Java heap size—Maximum memory size to be used by Java processes on the IMC Web Server.
The hardware requirements of IMC vary with the components and networking circumstances. For more
information, see the release notes of each component.
Table 2 Server requirements for 32-bit operating systems
Management scale
Nodes
0 to 200
200 to 500
System minimum requirements
Collection
units
Online
operator
s
0 to 5 K
20
5 K to 50 K
10
0 to 10 K
30
10 K to 100 K
10
CPU1
Server
memory
Max.
Java
heap
Storage
required
for
installation
2 cores
4 GB
512
MB
3 GB
 Win
4 cores
5
dows
:6
GB
 Linux
:8
GB
Storage
required
for
operation
50 GB
60 GB
50 GB
1 GB
3 GB
100 GB
Table 3 Server requirements for 64-bit operating systems
Management scale
Nodes
0 to 200
System minimum requirements
Collection
units
Online
operator
s
0 to 5 K
20
5 K to 50 K
10
CPU1
Server
memory
Max.
Java
heap
Storage
required for
installation
 Windo
2 cores
ws: 4
GB
Storage
required for
operation
50 GB
2 GB
3 GB
 Linux: 6
60 GB
GB
0 to 10 K
200 to 1
K
10 K to 100 K
 Windo
30
10
4 cores
ws: 8
GB
 Win: 2
2 GB
 Linux:
0 to 20 K
1 K to 2
K
20 K to 200 K
 Windo
30
10
6 cores
ws: 12
GB
5 K to 10
K
10 K to
15 K
0 to 30 K
40
4 GB
 Linux:
30 K to 300 K
20
0 to 40 K
50
4 K to 400 K
20
0 to 40 K
50
40 K to 400 K
20
8 cores
24 GB
8 GB
5 GB
32 GB
12 GB
7 GB
64 GB
16 GB
10 GB
x:
12
core
s
24
cores
Requirement
Remarks
Windows Server 2003 (32-bit)
Service Pack 2
Windows
6
60 GB
200 GB
80 GB
250 GB
100 GB
: 16
core
s
Table 4 Software requirements
Operating
system
 Linux: 6
 Win
 Linu
100 GB
GB
GB
Software requirements
Item
 Linux: 4
 Win: 4
16 GB
2 K to 5
K
GB
GB
12 GB
50 GB
300 GB
200 GB
600 GB
Item
Database
Requirement
Remarks
Windows Server 2003 (64-bit)
Service Pack 2 (64-bit) and KB942288
Windows Server 2003 R2 (32-bit)
Service Pack 2
Windows Server 2003 R2 (64-bit)
Service Pack 2 (64-bit) and KB942288
Windows Server 2008 (32-bit)
Service Pack 2
Windows Server 2008 (64-bit)
Service Pack 2 (64-bit)
Windows Server 2008 R2 (64-bit)
Service Pack 1
Windows Server 2012 (64bit)
KB2836988
SQL Server 2008 R2 SP2 Express
The database is the embedded database of the
Standard edition.
To ensure correct installation and operation of IMC, do not install IMC with other network management
products on the same server.
Setting the Java memory size on 32-bit OS
HP recommends using a 64-bit operating system when simultaneously deploying the IMC Platform and
service components.
When IMC runs on a 32-bit operating system, manually modify the assignable memory size of Java after
deployment using the following method:
1.
Use a text editor (such as WordPad in Windows or vi in Linux) to edit the \client\bin\startup.bat
script or the startup.sh script on Linux.
2.
Replace set JAVA_OPTS=-server –Xmx512m -Xrs -XX:PermSize=64m -XX:MaxPermSize=386m
... with set JAVA_OPTS=-server -Xmx1024m -Xrs -XX:PermSize=64m -XX:MaxPermSize=576m
....
3.
Save the file and restart the jserver process.

If the jserver process cannot start, decrease the above values until it can start.

If an out of memory error occurs after the jserver process starts, use a 64-bit operating system.
Installing IMC on a virtual machine
HP recommends installing IMC on a Physical server.
If IMC is installed on a virtual machine, do not change the following virtual machine configuration
settings:

Number of CPUs

Number, model, and MAC addresses of network adapters

Number of disk drives, storage paths

Assignments of storage
Although changing the settings does not affect VM migration, IMC will not operate correctly.
7
Table 5 Hypervisor platform requirements
Vendor
Hypervisor
Remarks
VMware Workstation 6.5.x
VMware
VMware Workstation 9.0.x
VMware ESX Server 4.x
VMware ESX Server 5.x
Hyper-V
Windows Server 2008 R2 Hyper-V
Windows Server 2012 Hyper-V
Preparing the installation environments
Uninstalling previous versions of IMC
If IMC was previously installed on the system, thoroughly remove it first. For instructions on removing IMC,
see "8 Upgrading, backing up, or removing IMC."
After you remove IMC:

In Windows, locate and delete the IMC-Reserved folder in the WINDOWS folder of the system disk.

In Linux, locate and delete the IMC-Reserved folder in the /etc directory.
Ports and firewalls
Table 6 IMC port requirements
Component
Server
IMC Webserver
Platform
Usage: protocol/default port
HTTP: TCP/8080
HTTPS: TCP/8443
Direction
Browser to IMC
SQL server database: TCP/1433
Database
Oracle database: TCP/1521
IMC and components to
Database
MySQL database: TCP/3306
Use tools such as ‘netstat -a’ and ‘telnet hostname port’ to verify access between systems.
Other IMC components may have additional port requirements.
Setting the system time
HP recommends the following settings:

Set the time zone to GMT or Coordinated Universal Time.

Do not enable seasonal time adjustments such as daylight savings time.
8

Before installing IMC, check that the system time, date, and time zone settings on the server are
correct.
After IMC is started, do not modify the system time of the server. Otherwise, intermittent problems can
occur, such as:

When jumping to a future time, the system can take a long time to process a large amount of data.
It can exceed the maximum time that the data can be saved in the database.
This affects the current data sampling speed and results in delay. After the processing of such data
is complete, the delay is gradually recovered.

When you modify the system time to a past time, data with overlapping time can occur, and data
processing might become abnormal. After the overlapping time is past, data processing becomes
normal again.
9
3 Installation and deployment requirements
The following information describes important concepts and requirements for IMC installation and
deployment. Read the information carefully before you install and deploy IMC.
Terms and concepts
Installation and deployment
To improve server performance, IMC uses the "Install + Deploy" model. Install puts copies of the IMC
installation packages on the server. Deploy decompresses the installation packages and runs
deployment scripts on the server.
Before IMC deployment, you must install the target components on the server. The components of IMC
are operational only after they are deployed.
IMC automatically creates a database user when a service component is deployed. HP recommends not
modifying the database user configuration, including the user's password and password security policy.
If the deployment or upgrade process is interrupted, IMC automatically stores logs as a compressed file
in the \tmp directory of the IMC installation path. With the logs, you can quickly locate the problem or
error that occurred in IMC deployment or upgrade.
In IMC centralized deployment, all the components are deployed on the same server.
Checking the installation environment
The IMC installation package provides a tool (envcheck) to check the system environment and database
connectivity.
1.
Copy the tool (envcheck.bat for Windows, envcheck.sh for Linux) from the tools folder to the install
folder of the IMC installation package.
2.
Run the tool. You do not have to run it as administrator.
If not all check items are passed, resolve the issue and run the tool again.
The system environment check includes:

Whether or not the service port to be used by IMC is idle. If it is used by another program, you must
remove that program or modify the service port of that program.

At least 2 GB of physical memory.

Whether or not the database client and server software is installed.

Required operating system version and patches.

Net Framework 2.0 SP2 is installed.

At least 512 MB of free space on the system disk.

Whether or not the database files can be written on the database server.
10
The following information is needed by the envcheck tool:

Database Type—Select the database type, Microsoft SQL Server, MySQL, or Oracle.

Instance Name—Use the default instance or select Other Instance to specify a user-defined
instance.

Superuser—Enter the database superuser name.

Password—Enter the password of the superuser.

Database Location—Select the location of the database server from the list, local host or other
server.

Database Server Address—Enter the IP address of the database server. This field is editable only
when other server is selected as the database location.

Listening Port—Enter the listening port of the database server. The default is 1433.

Installation Location—Enter or browse to the local directory where the IMC installation package is
stored.

Data File Location—Enter or browse to the local or remote directory where the database files are
stored. If a remote database server is used, make sure the directory exists on the database server.
Envcheck verifies read and write access to this directory.

HTTP Port—Enter the HTTP port number for IMC’s webserver.

HTTPS Port—Enter the HTTPS port number for IMC’s webserver.
Embedded database restrictions and guidelines
The embedded database software, SQL Server 2008 SP2 Express, is shipped with the installation
packages of IMC Standard and SNS editions. To use the embedded database on these IMC editions,
follow these restrictions and guidelines:

The IMC server must use a Windows operating system on which no SQL server database has been
installed.

The number of nodes to be managed by IMC does not exceed 1000. Otherwise, install a separate
database.
11
4 Installing and deploying the IMC Platform
You can use the Microsoft SQL Server 2008 R2 SP2 Express database embedded in IMC of Standard
edition on Windows without installing any database or database client prior to the IMC installation.
The following information describes the installation and recommended deployment schemes of the IMC
Platform.
Installing the IMC Platform
To install the IMC Platform:
1.
Log in to the operating system as a user with administrator privileges.


2.
To install IMC in Windows Server 2008, 2008 R2, 2012 or 2012 R2 right-click install.bat (see
below) and select Run as Administrator from the shortcut menu.

To install IMC on Linux, start the IMC installation wizard by running install.sh as a root user.

To install IMC on Linux, all of the installation files must be on the local server.
Uncompress the installation file.


3.
To install IMC in Windows Server 2003 or Windows Server 2003 R2, you must log in as an
administrator.
If installing from DVD on Red Hat Linux 6, copy all installation files to the local server.
If installing on Linux, make sure the installer can run the chmod –R 775 .\linux\install\install.sh
command.
Run .\windows\install\install.bat (or .\linux\install\install.sh). A window appears, as shown in
Figure 1.
When you are using other Windows server operating systems or Linux, follow these guidelines:


To install IMC in Windows Server 2003 or Windows Server 2003 R2, you must log in as an
administrator.
To install IMC in Windows Server 2008 or Windows Server 2008 R2, right-click the install.bat
script and select Run as Administrator from the shortcut menu.
12
Figure 1 Selecting Locale (on Windows Server 2008 R2)
4.
Select a country/region, language used during and after installation, and installation type.
IMC supports typical and custom installation:


Typical—Install and deploy all platform subcomponents on the current server. A typical
installation is a good place to start a centralized deployment, although service components
could be installed on subordinate servers.
Custom—Allows you to select IMC Platform subcomponents to install and deploy on the current
server.
To deploy all the IMC Platform subcomponents, select Typical. To deploy only the desired IMC Platform
subcomponents, select Custom.
Typical installation
If you select typical installation, the installation program automatically installs and deploys all
subcomponents for the IMC Platform on the server:
1.
Select the country or region and language, click Typical, and click OK, as shown in Figure 1.
The window for checking installation parameters appears, as shown in Figure 2.
13
Figure 2 Checking installation parameters
2.
Configure the installation parameters:
a. Use the default installation location and database file location, or customize the installation
location and database file location as needed.
Make sure the disk for IMC installation has at least 5 GB of free space, and the disk for storing
data files has at least 30 GB of free space. Otherwise, IMC installation or deployment fails.
b. Configure the Web service port numbers (8080 for HTTP and 8443 for HTTPS by default).
You can also use other service port numbers that are not used by other services. If UAM is to
be installed for the IMC system, set HTTP Port to 80. You cannot change the HTTP port number
after IMC installation is completed. To change the HTTP port number, you must reinstall IMC.
3.
Click OK.
The window for checking installation environments appears and displays the check results, as
shown in Figure 3.
14
Figure 3 Checking installation environments
The system environment check includes:

Whether or not the database listening port is used by another service.

At least 2 GB of physical memory is available.

Required operating system version and patches are installed.

.Net Framework 2.0 SP2 is installed.

At least 512 MB of free space is available on the system disk.
4.
Adjust the installation environments according to the check results.
5.
If the installation environments check is passed, click Continue.
The system starts to install IMC Platform subcomponents, install the embedded database to the
same partition where the Windows folder is located, and then deploy all IMC Platform
subcomponents. When the installation is complete, you can log in to the database by using
username sa and password iMC-Install2008.
After IMC installation and deployment is complete, the Batch deploy succeeded window appears,
as shown in Figure 4.
Figure 4 Batch deploy succeeded
To start IMC immediately, select Start iMC Server now, and then click OK. The Intelligent
Deployment Monitoring Agent window appears, as shown in Figure 5.
15
To start IMC later, click OK. When you want to start IMC, click Start iMC on the Monitor tab of the
Intelligent Deployment Monitoring Agent.
Figure 5 Intelligent Deployment Monitoring Agent
The Intelligent Deployment Monitoring Agent window allows you to perform the following tasks:

Click the Deploy tab to view the deployed components.

Click the Process tab to view the running process information.

Click the Monitor tab to view the IMC startup information, as shown in Figure 6. When the startup
is complete, the Start iMC button is grayed out.

To disable IMC, click Stop iMC.

You can select Automatically start the services when the OS starts when you want IMC to
automatically start at the system startup.

To install new components, click Install, as shown in Figure 6, or right-click the Intelligent
Deployment Monitoring Agent icon on the Windows system tray, and then select Install from the
shortcut menu. For more information, see "5 Installing and deploying IMC service components."
16
Figure 6 Intelligent Deployment Monitoring Agent
Custom installation
If you select custom installation, you must manually deploy the desired subcomponents for the IMC
Platform after installation.
1.
In Figure 1, select the country or region and language, click Custom, and then click OK.
The window for checking installation environments appears and displays the check results, as
shown in Figure 7.
Figure 7 Checking installation environments
The check items include:
17
2.

Whether or not the database listening port is used by another service.

At least 2 GB of physical memory is available.

Required operating system version and patches are installed.

.Net Framework 2.0 SP2 is installed.

At least 512 MB of free disk space is available.
Click Continue.
The Welcome to HP iMC Installation Wizard window appears, as shown in Figure 8.
Figure 8 Welcome to HP iMC Installation Wizard
3.
Click Next.
The Agreement window appears, as shown in Figure 9.
18
Figure 9 Agreement
4.
Read the license agreement and third party license and select Accept.
5.
Click Next.
The Choose Target Folder window appears, as shown in Figure 10.
Figure 10 Choose Target Folder
19
The Choose Target Folder window displays the components.
6.
Select the components you want to install and specify the installation location.
By default, IMC is installed in the \Program Files\IMC directory of the disk with the maximum free
space on Windows or in /opt/IMC on Linux. In this example, IMC is installed in E:\Program
Files\IMC.
You can enter a path or click Browse to select another path.
NOTE:
 At least 5 GB free space must be available.
 The installation path must be local.
 Linux does not support the IMC installation in a path with a symlink path.
 If the specified installation location includes files, a confirmation dialog box appears. Click OK to
delete the files.
7.
Click Next.
The Deployment and Upgrade Options window appears, as shown in Figure 11.
Figure 11 Deployment and Upgrade Options
8.
Select Deploy or upgrade at once or Deploy or upgrade later. In this example, select Deploy or
upgrade later.
9.
Click Next.
The Installation Summary window appears, as shown in Figure 12.
20
Figure 12 Installation Summary
The Installation Summary window shows the following information:

Name, description, version, and disk space required by each component to be installed.

IMC installation location.

Total disk space required by the installation.

Free disk space of the partition where IMC is to be installed.
10. Click Install.
The Installing common components window appears, as shown in Figure 13.
21
Figure 13 Installing common components
The wizard shows the process of component installation.
After the installation is complete, the Installation Completed window appears, as shown in Figure
14.
Figure 14 Installation Completed
11. Perform either of the following tasks:

To start to deploy the IMC Platform, select Open deployment monitoring agent.
22

To continue to install other IMC components, select Install other iMC Components.
In this example, select Open deployment monitoring agent.
12. Click Finish.
Deploying the IMC Platform
This section describes the IMC deployment procedures.
1.
In the Installation Completed window (see Figure 14), select Open deployment monitoring agent
and then click Finish.
The system automatically starts the Intelligent Deployment Monitoring Agent. For the first
deployment, a Batch deploy window appears, as shown in Figure 15.
Figure 15 Batch deploy
NOTE:
You can also start the Intelligent Deployment Monitoring Agent by selecting Start > All Programs >
HP Intelligent Management Center > HP Deployment Monitoring Agent (or running the dma.sh
script in /deploy of the IMC installation path on Linux). Then select the Deploy tab, select Batch
Deploy from the right-click menu of the target components to start batch deployment.
In the Batch deploy window, the subcomponents to be deployed by default include:

Alarm Management

Intelligent Configuration Center

NE Management

Performance Management

Report Management

Resource Management
23

Network Asset Management

Security Control Center

User Self-service Management
Optional subcomponents include:

ACL Management

General Search Service Management

Guest Access Manager

Syslog Management

Virtual Resource Management

VLAN Management
You can also select the subcomponents to be deployed as needed, except that the Resource
Management component is required. This example deploys all the subcomponents.
2.
Select all subcomponents and click OK.
The Database Configuration Info window appears, as shown in Figure 16.
Figure 16 Database Configuration Info
3.
Select Install embedded database. Otherwise, you cannot deploy the subcomponents.
4.
Select the location for saving database files.
By default, the data files are stored in the Program Files\imcdata directory of the disk with the
maximum free space on windows or /opt/imcdata on Linux. In this example, data files are stored
in C:\Program Files\imcdata.
When you do not want to use the default location, click Browse and select another local location.
5.
Select a path to save the data files and click Next.
24
The Configure Web Service Port window appears, as shown in Figure 17.
Figure 17 Configure Web Service Port
6.
Set the HTTP port and HTTPS port.
The default is 8080 and 8443. Make sure the specified ports are open in the firewall settings and
are not being used by other services. If UAM is to be installed for the IMC system, set HTTP Port to
80. You cannot change the HTTP port number after IMC installation is completed. To change the
HTTP port number, you must reinstall IMC.
7.
Click Deploy.
The Deploying window appears, as shown in Figure 18.
The system starts to install the embedded database and deploy subcomponents. Automatic
database installation takes time. Please wait with caution.
25
Figure 18 Deploying IMC subcomponents
After the deployment, the Batch deploy succeeded window appears, as shown in Figure 19.
Figure 19 Batch deploy succeeded
8.
In the Batch deploy succeeded window, select Open readme file directory, Start iMC Server now,
or both.
In this example, select Start iMC Server now and click OK.
The system immediately starts the IMC service and opens the Intelligent Deployment Monitoring
Agent window, as shown in Figure 20.
In this window, select the Deploy tab to view information about the component deployment, as
shown in Figure 20.
26
Figure 20 Information about component deployment
9.
After the deployment is finished, follow these steps to start the IMC service:
a. In the Intelligent Deployment Monitoring Agent window, select the Monitor tab, as shown in
Figure 21.
b. Click Start iMC.
c. You can also select the Automatically start the services when the OS starts box to start IMC
with the operating system.
Figure 21 Intelligent Deployment Monitoring Agent
27
d. To view the enabling and running status of each process, click the Process tab to enter the
process management window.
Deploying a single IMC component
To deploy a single IMC component, use either of the following methods in the window, as shown in
Figure 20.

Method 1:
Right-click the target component and select Deploy the Component from the shortcut menu.

Method 2:
a. Select any target component and select Batch deploy from the shortcut menu.
The Batch deploy dialog box appears.
b. Select the component and click OK.
Some IMC components depend on others. When deploying such components, consider the
dependencies between components. On the Deploy tab, select Show Dependencies from the right-click
menu of a component to view the components in which the selected component depends. When the
component does not depend on any components, Show Dependencies is grayed out.
The detailed deployment procedure for a single component is similar to the batch deployment.
Figure 22 Batch deployment
IMC service logon accounts
By default, the IMC system service HP iMC Server is logged on and started using the LocalSystem
account. To use another account for IMC service logon, you must grant the account read and write
28
access to the IMC installation folder, and then start IMC by using the Intelligent Deployment Monitoring
Agent.
29
5 Installing and deploying IMC service
components
This following information describes the recommended IMC Platform plus service components
deployment mode, how to install, and deploy the service components.
IMC common service components include:

Application Performance Manager (APM)

Branch Intelligent Management System (BIMS)

Endpoint Admission Defense (EAD)

Intelligent Analysis Reporter (IAR)

MPLS VPN Manager (MVM)

Network Traffic Analyzer (NTA)

QoS Manager (QoSM)

Remote Site Manager (RSM)

Service Health Manager (SHM)

Service Operation Manager (SOM)

TACACS+ Authentication Manager (TAM)

User Access Manager (UAM)

User Behavior Auditor (UBA)

Virtual Application Networking Fabric Manager (VAN SAN)

Virtual Application Networking Software Defined Network (VAN SDN)

Wireless Service Manager (WSM)

iNode Dissolvable Client

IPsec VPN Manager

VAN Connection Manager

Voice Service Manager
Table 7 IMC subcomponents and deployment requirements
Component
Network Traffic Analyzer
User Behavior Auditor
Subcomponent
Remarks
Network Traffic Analyzer
N/A
Network Traffic Analyzer Server
N/A
Network Behavior Analyzer
N/A
Network Behavior Analyzer Server
N/A
User Behavior Auditor
N/A
User Behavior Auditor Server
You must configure the NTAS server.
Network Behavior Analyzer
N/A
30
Component
Subcomponent
Remarks
Network Behavior Analyzer Server
N/A
QoS Management
N/A
Service Health Management
N/A
NQA Collector Management
N/A
CMDB Management
N/A
Service Desk
N/A
Applications Manager
N/A
BIMS - Branch Intelligent
Management System
N/A
BIMS - Auto-Configuration Server
N/A
Mobile Branch Manager
N/A
Wireless Service Manager
Wireless Service Manager
N/A
Voice Service Manager
Voice Service Manager
N/A
IPsec VPN Manager
IPsec VPN Manager
N/A
MPLS VPN Management
N/A
MPLS TE management
N/A
L2VPN Management
N/A
QoS Manager
Service Health Manager
Service Operation Manager
Applications Manager
BIMS
MPLS VPN Manager
Resource Management
Report Management
User Access Management
Set the database password (defaults to
iMC5_uamead) and UAM Server's IP
Address, which is UAM’s RADIUS
server.
Portal Web Server and Portal Proxy
N/A
Portal Server
Set Portal Server's IP Address, which
is the IP address of the network
adapter providing services externally
of the server where the Portal server
component is deployed.
Third Party Page Publish Server
Set the Portal Server’s Port.
End User Intelligent Profiling Server
N/A
End User Intelligent Profiling Sub
Server
N/A
Policy Server
Set Policy Server's IP Address.
Policy Proxy Server
Set Policy Proxy Server's IP Address.
User SelfService
Set User SelfService's IP Address.
User Access Management Sub
Server
Provides RADIUS authentication for
access users.
Security Policy Configuration
N/A
User Access Manager
EAD Security Policy
31
Component
Subcomponent
Remarks
Desktop Asset Manager
Set the database password (defaults to
iMC5_uamead), and DAM Server's IP
Address, which is the IP address of the
network adapter providing services
externally of the server where DAM is
deployed.
Desktop Asset Manager Proxy
Server
Set DAM Proxy Server's IP Address,
which is the IP address of the network
adapter providing services externally
of the server where the DAM proxy
server component is deployed.
End User Intelligent Profiling
End User Intelligent Profiling Server
and Subserver
Set the EIP Server IP Address.
TACACS+ Authentication
Manager
TACACS+ Authentication Manager
N/A
iNode DC
iNode Dissolvable Client
N/A
VAN Connection Manager
VAN Connection Management
N/A
VAN Fabric Manager
VAN Fabric Manager
N/A
VAN SDN Manager
VAN SDN Manager
N/A
Resource Automation
Manager
Resource Automation Manager
N/A
UC Health Manager
UC Health Manager
N/A
The installation and deployment procedures for the common service components the same. The following
information describes how to install and deploy NTA, UAM, EAD, and MVM.
Table 8 lists the service components that use the same installation and deployment procedures as the
example components.
Table 8 Service components classified by deployment procedures
Example component
Component with the same
procedure
Remarks
NTA
APM, BIMS, IVM, QoSM, RAM,
SDNM, SHM, SOM, UBA,
UCHM, VCM, VFM, VSM, WSM,
iNode DC
No parameter is required to
complete the installation and
deployment.
UAM
N/A
Additional parameters are required
to complete the installation and
deployment.
EAD
TAM
Additional parameters are required
to complete the installation and
deployment.
MVM
N/A
Additional parameters are required
to complete the installation and
deployment.
32
Before you deploy a service component, deploy the base IMC components and the components on
which the service component depend.
Installing IMC NTA
IMC NTA includes the following subcomponents:

Network Traffic Analyzer

Network Behavior Analyzer

Network Traffic Analyzer Server

Network Behavior Analyzer Server
Installing IMC NTA
1.
Select Install other iMC components in the Installation Completed window (see Figure 14) and
click Finish, or perform one of the following operations as needed:


On Windows:

Select Start > All Programs > HP Intelligent Management Center > HP Deployment
Monitoring Agent. On the Monitor tab, click Install.

Right-click the Intelligent Deployment Monitoring Agent icon in the system tray and select
Install from the shortcut menu.
On Linux, run the dma.sh script in the /deploy directory of the IMC installation path. On the
Monitor tab, click Install.
The Choose folder dialog box appears, as shown in Figure 23.
Figure 23 Choose folder
2.
Insert the IMC NTA installation CD into the DVD-ROM drive. Then, in the Choose folder window,
click Browse and select the install\components folder on the CD.
3.
Click OK.
The HP IMC Installation Wizard appears, as shown in Figure 24.
33
Figure 24 Welcome to HP IMC Installation Wizard
4.
Click Next.
The Agreement window appears, as shown in Figure 25.
Figure 25 Agreement
5.
Read the license agreement and third party license and select Accept.
34
6.
Click Next.
The Choose Target Folder window appears, as shown in Figure 26.
Figure 26 Choose Target Folder
The Choose Target Folder window displays information about the NTA components to be installed
and the installation location.
In centralized deployment, the system specifies the installation location of the NTA as the
installation location of the IMC Platform by default.
7.
Verify the information and click Next.
The Deployment and Upgrade Options window appears, as shown in Figure 27.
35
Figure 27 Deployment and Upgrade Options
8.
Select Deploy or upgrade at once or Deploy or upgrade later. In this example, select Deploy or
upgrade later.
9.
Click Next.
The Installation Summary window appears, as shown in Figure 28.
Figure 28 Installation Summary
36
10. Verify installation information and click Install.
After the installation is complete, the Installation Completed window appears, as shown in Figure
29.
Figure 29 Installation Completed
11. Perform either of the following tasks:

To start to deploy IMC NTA, select Open deployment monitoring agent.

To continue to install other IMC components, select Install other iMC Components.
In this example, select Open deployment monitoring agent.
12. Click Finish.
Deploying IMC NTA
1.
In the Installation Completed window (see Figure 29), select Open deployment monitoring agent
and click Finish.
The system automatically starts the Intelligent Deployment Monitoring Agent. A Batch deploy
window appears at the same time, as shown in Figure 30.
37
Figure 30 Batch deploy
2.
Select the components you want to deploy. In this example, select all the NTA subcomponents.
3.
Click OK to start deploying the components.
After the deployment is complete, the Batch deploy succeeded window appears, as shown in
Figure 31.
Figure 31 Batch deploy succeeded
4.
Perform either of the following tasks:


To start IMC immediately, select Start iMC Server now and click OK.
To start IMC later, clear the Start iMC Server now option and click OK. Then, when you are
ready to start IMC, click Start iMC on the Monitor tab of the Intelligent Deployment Monitoring
Agent.
38
Installing and deploying IMC UAM
IMC UAM includes the following subcomponents:

Intelligent Strategy Proxy

User Access Management

Portal Server

EIP Server

EIP Sub Server

Policy Server

Policy Proxy Server

User SelfService

User Access Management Sub Server

Third-Party Page Publish Server
To install and deploy IMC UAM:
1.
Install IMC UAM in the same way IMC NTA is installed. (Details not shown.)
For information about the installation procedures, see "Installing IMC NTA."
2.
In the Installation Completed window (see Figure 32), select Open deployment monitoring agent.
Figure 32 Installation Completed
3.
Click Finish.
The system automatically starts the Intelligent Deployment Monitoring Agent and displays the
Batch deploy window, as shown in Figure 33.
39
Figure 33 Batch deploy
4.
Select the subcomponents you want to deploy. In this example, select all the subcomponents
except EIP Sub Server and User Access Management Sub Server and click OK.
5.
In the Strategy Proxy Server Configuration window (see Figure 34), configure the following
parameters:
a. Enter the IP address of the host on which Strategy Proxy Server is to be deployed in the IPv4
Address(Client) field. In this example, use the default value of the parameter.
b. Enter the IP address of the host on which User Access Management Sub Server is to be
deployed in the IPv4 Address(Server) field. In this example, use the default value of the
parameter.
40
Figure 34 Strategy Proxy Server Configuration
If Strategy Proxy Server and User Access Management are deployed on the same host but
associated with different NICs, enter the IP addresses of the NICs in the two fields.
6.
Click Deploy.
7.
In the Configure User Access Management window (see Figure 35), configure the following
parameters:


Database Password/Confirm Password—These fields are automatically populated with the
database password configured when the IMC Platform is installed. Do not change the values of
these fields unless the database password of the IMC Platform is changed after installation.
UAM Server's IPv4 Address—This field displays the IP address of the host on which UAM is to
be deployed. By default, the IP address of the current host is displayed. Use the default value in
this example.
41
Figure 35 Configure User Access Management
8.
Click Deploy.
9.
In the Configure Portal Component window (see Figure 36), configure the following parameters:
a. Enter the IP address of the host where the portal server is to be deployed in the Portal Server's
IPv4 Address field. In this example, use the default value of the parameter.
b. Enter the HTTP port number of the Apache server in the Apache Server's Http Port field. In this
example, use the default value (8888) of the parameter.
42
Figure 36 Configure Portal Component
10. Click Deploy.
11. In the Configure EIP Server window (see Figure 37), enter the IP address of the host where the EIP
server is to be deployed in the EIP Server's IPv4 Address field. In this example, use the default
value of the parameter.
Figure 37 Configure EIP Server
12. Click Deploy.
43
13. In the Configure Policy Server window (see Figure 38), enter the IP address of the host where
Policy Server is to be deployed in the Policy Server's IPv4 Address field. In this example, use the
default value of the parameter.
Figure 38 Configure Policy Server
14. Click Deploy.
15. In the Configure User SelfService window (see Figure 39), enter the IP address of the host where
User SelfServer is to be deployed in the User SelfServer's IPv4 Address field. In this example, use
the default value of the parameter.
44
Figure 39 Configure User SelfService
16. Click Deploy.
17. In the Third-Party Page Publish Server Configuration window (see Figure 40), enter the port
number in the HTTP Port field. In this example, use the default value (8899) of the parameter.
Figure 40 Third-Party Page Publish Server Configuration
45
18. Click Deploy.
After the deployment is complete, the Batch deploy succeeded window appears, as shown in
Figure 41.
Figure 41 Batch deploy succeeded
19. Perform either of the following operations:


To start IMC immediately, select Start iMC Server now and click OK.
To start IMC later, clear the Start iMC Server now option and click OK. Then, when you are
ready to start IMC, click Start iMC on the Monitor tab of the Intelligent Deployment Monitoring
Agent.
Installing and deploying IMC EAD
EAD includes the following subcomponents:

Security Policy Configuration

Desktop Asset Manager

Desktop Asset Manager Proxy Server
To install and deploy IMC EAD:
1.
Install IMC EAD in the same way IMC NTA is installed. (Details not shown.)
For information about the installation procedures, see "Installing IMC NTA."
2.
In the Installation Completed window (see Figure 42), select Open deployment monitoring agent.
46
Figure 42 Installation Completed
3.
Click Finish.
The system automatically starts the Intelligent Deployment Monitoring Agent and displays the
Batch deploy window, as shown in Figure 43.
Figure 43 Batch deploy
47
4.
Select the subcomponents you want to deploy. In this example, select all EAD subcomponents and
click OK.
5.
In the Configure Desktop Asset Manager Component window (see Figure 44), configure the
following parameters:


Database Password/Confirm Password—These fields are automatically populated with the
database password configured when the IMC Platform is installed. Do not change the values of
these fields unless the database password of the IMC Platform is changed after installation.
DAM Server's IP Address—This field displays the IP address of the host on which DAM is to be
deployed. By default, the IP address of the current host is displayed. Use the default value in this
example.
Figure 44 Configure Desktop Asset Manager Component
6.
Click Deploy.
After the deployment is complete, the Batch deploy succeeded window appears, as shown in
Figure 45.
Figure 45 Batch deploy succeeded
48
7.
Perform either of the following operations:


To start IMC immediately, select Start iMC Server now and click OK.
To start IMC later, clear the Start iMC Server now option and click OK. Then, when you are
ready to start IMC, click Start iMC on the Monitor tab of the Intelligent Deployment Monitoring
Agent.
Installing and deploying IMC MVM
IMC MVM includes the following subcomponents:

MPLS VPN Management

MPLS Management

MPLS TE Management

L2VPN Management
To install and deploy IMC MVM:
1.
Install IMC MVM in the same way IMC NTA is installed. (Details not shown.)
For information about the installation procedures, see "Installing IMC NTA."
2.
In the Installation Completed window (see Figure 46), select Open deployment monitoring agent.
Figure 46 Installation Completed
3.
Click Finish.
The system automatically starts the Intelligent Deployment Monitoring Agent and displays the
Batch deploy window, as shown in Figure 47.
49
Figure 47 Batch deploy
4.
Select the subcomponents you want to deploy. In this example, select all the subcomponents and
click OK.
5.
In the Please Choose L2VPN Global Parameter Operate window (see Figure 48), configure the
L2VPN parameters as needed. This example uses the default values of the parameters.
If BGP(Boarder Gateway Protocol) is selected for VPLS(Virtual private LAN service), VLL(virtual
leased line) and PBB(provider backbone bridge) options are automatically cleared.
50
Figure 48 Please Choose L2VPN Global Parameter Operate
6.
Click Deploy.
After the deployment is complete, the Batch deploy succeeded window appears, as shown in
Figure 49.
Figure 49 Batch deploy succeeded
7.
Perform either of the following operations:


To start IMC immediately, select Start iMC Server now and click OK.
To start IMC later, clear the Start iMC Server now option and click OK. Then, when you are
ready to start IMC, click Start iMC on the Monitor tab of the Intelligent Deployment Monitoring
Agent.
51
6 Installing plug-ins
To support some IMC functions, you must install necessary plug-ins.
Installing DHCP plug-ins
A DHCP server installed with a DHCP plug-in lets IMC obtain the names of terminals, such as servers,
PCs, and printers, from the DHCP server. To accomplish this task, make sure the following conditions
exist:

At least one DHCP server exists in the network.

All DHCP servers in the network have DHCP plug-ins installed.
To view the names obtained from the DHCP server, select Terminal Access > Unauthorized Access List or
History Access Log List from the navigation tree.
The following information describes how to install DHCP plug-ins on MS DHCP and Linux DHCP servers,
respectively.
Installing DHCP plug-ins on the MS DHCP server
1.
Modify the file qvdm.conf, so that the IMC supports getting the terminal name or terminal domain
name through the MS DHCP server.
a. Enter the\server\conf\ directory in the IMC installation path, open the file qvdm.conf in
Wordpad, and add the following line to the file:
l2topoPCNameDhcpSwitch=1
b. Save and exit the file.
c. Restart IMC in the Intelligent Deployment Monitoring Agent.
2.
Install the IMC DHCP plug-in on the MS DHCP server.
The DHCP plug-in installer dhcp-plug-windows.zip is saved in the \windows\tools\ directory of
the IMC installer.
a. Copy the plug-in installer to the MS DHCP server.
b. Decompress the installer.
c. Use Wordpad to open the imf.cfg file in the \server\imf\server\conf directory of the
dhcp-plug-windows folder.
d. Modify the IMGAddress into the master server IP address and IMGPort (which is 8800 by
default) to the IMG port number.
e. Save and exit the file.
3.
Run the install.bat script in the dhcp-plug-windows folder.
After the installation, a new service IMC DHCP Plug is added to the system services.
4.
Start the IMC DHCP plug service.
52
a. Click Start, and select Administrative Tools > Component Services to open the Component
Services window.
b. Select Services (Local) from the navigation tree.
c. Right-click the IMC DHCP Plug service on the Services (Local) list and select Start to start the IMC
DHCP plug service.
To uninstall a DHCP plug-in, run the file uninstall.bat in the dhcp-plug-windows directory.
CAUTION:
Do not remove the directory which the plug-in installer dhcp-plug-windows.zip is extracted to. Otherwise,
the DHCP plug-in cannot be uninstalled completely.
Installing DHCP plug-ins on the Linux DHCP server
1.
Modify the file qvdm.conf, so that IMC supports getting the terminal DNS name or terminal name
through the Linux DHCP server.
a. Use the Notepad to open the qvdm.conf file in the \server\conf directory of the IMC
installation path on the Windows server running IMC.
b. Add the following line to the file:
l2topoPCNameDhcpSwitch=1
c. Save and exit the file, and restart IMC in the Intelligent Deployment Monitoring Agent.
2.
Install the IMC DHCP plug-in on the Linux DHCP server.
The DHCP plug-in installer dhcp-plug-linux.zip is saved in the tools directory of the IMC Linux
installer.
a. Copy the plug-in installer to the Linux DHCP server.
b. Decompress the installer.
c. Use the VI editor to open the imf.cfg file in the /server/imf/server/conf/ directory of the
dhcp-plug-linux folder.
vi imf.cfg
d. Modify the IMGAddress into the IMC server IP address, and modify the IMGPort (which is
8800 by default) to the IMG port number that you set when installing IMC.
e. Save and exit the file.
3.
Check whether the path of the DHCP server IP allocation information file, dhcpd.leases, is correct.
a. Enter the /var/lib/dhcp directory of the Linux operating system, and check whether the
dhcpd.leases file exists.
b. When the file does not exit, enter the server/conf/ directory of the dhcp-plug-linux folder, use
the VI editor to open the qvdm.conf file, and add the following line to the file to specify the path
of the dhcpd.leases file:
DhcpPlugIpAllocPath=<Current path>/dhcpd.leases
c. Save and exit the file.
4.
Execute the install.sh script in the dhcp-plug-linux folder.
After the installation is complete, the dhcp-plug service is added to the system services, and has been
automatically started.
53
You can use the server dhcp-plug stop command to stop the service or use the server dhcp-plug start
command to start the service.
To uninstall a DHCP plug-in, run the uninstall.sh script in the dhcp-plug-linux directory.
CAUTION:
Do not remove the directory to which the plug-in installer dhcp-plug-windows.zip is extracted. Otherwise,
the DHCP plug-in cannot be uninstalled completely.
Installing VRM agent plug-ins
Virtual Resource Management (VRM) is a module on the IMC Platform to manage virtual networks. It
must work with a VRM Windows or Linux agent for virtual network management.
Installing a VRM Windows agent
When Microsoft Hyper-V servers exist in the network, install VRM Windows agents for IMC to manage
the Hyper-V servers.
A VRM Windows agent must be installed on one Windows server. When the Microsoft Hyper-V servers
are managed by Microsoft VMM servers, HP recommends installing VRM Windows agents on the
Microsoft VMM server. A VRM Windows agent can work for up to 50 Hyper-V servers. When more than
50 Hyper-V servers exist in the network, install more VRM Windows agents.
CAUTION:
VRM Windows agents can only be installed on Windows server 2008 R2 SP1/2012 that can access all
Hyper-V servers. A Windows server can be installed with only one VRM Windows agent.
A VRM Windows agent is dependent on .NET Framework 4.5, and PowerShell 3.0. Before you install a
VRM Windows agent, make sure that all the software applications are installed. For the Windows Server
2008 R2 system, they are installed in by default; for other Windows operating systems, go to the
Microsoft official website to download and install them.
1.
The installation file vrm-plug-windows.zip of a VRM Windows agent is stored in tools folder of the
IMC installation package. Decompress the file and copy the file to any directory of the server
where the VRM Windows agent is to be installed.
2.
Run Register.bat in the vrm-plug-windows folder. When all the related software applications are
installed, the installation process is complete. Otherwise, the system prompts you to install the
required software and quit the installation process. In this case, install the required software and
restart the installation process.
Do not delete the vrm-plug-windows folder or the files in the folder after installation. It becomes the
service registration path.
3.
Use Wordpad to open the imf.cfg file in the vrm-plug-windows/serverimf/server/conf directory.
Modify IMGAddress as the IP address of the master IMC server and IMGPort as the MBP port
number (8800 by default).
4.
Save your settings and quit.
5.
Start the IMC VRM plug service.
54
a. Click Start and select Administrative Tools > Component Services to open the Component
Services window.
b. Select Services (Local) from the navigation tree, right-click iMC VRM Agent on the Services
(Local) list, and select Start to start the VRM agent service.
To uninstall a VRM agent plug-in, run the file UnRegister.bat in the vrm-plug-windows directory.
Installing a VRM Linux agent
VRM uses a Linux agent to manage KVM virtual networks for Red Hat, Ubuntu, and Fedora and Citrix
XenServer virtual environment. With the agent, VRM can obtain virtual network data of KVM and Xen,
and set the virtual network parameters for KVM and Xen. Each VRM Linux agent can manage up to 200
physical KVM and Xen servers. You can install multiple VRM Linux agents as needed.
VRM Linux agents can run on 32-bit or 64-bit Red Hat 6.0 or later versions.
Installation prerequisites
The VRM Linux agent is a 32-bit program and applies only to Red Hat.
To install VRM Linux agent on 32-bit Red Hat Enterprise Linux 5.0 and 5.5, select a network server. No
other software package is required.
To install VRM Linux agent on 64-bit Red Hat Enterprise Linux 6.X, first install the following 32-bit
program packages:

compat-libcap1-1.10-1.i686.rpm

glibc-2.12-1.107.el6.i686.rpm

keyutils-libs-1.4-4.el6.i686.rpm

krb5-libs-1.10.3-10.el6.i686.rpm

libaio-0.3.107-10.el6.i686.rpm

libcom_err-1.41.12-14.el6.i686.rpm

libgcc-4.4.7-3.el6.i686.rpm

libidn-1.18-2.el6.i686.rpm

libssh2-1.4.2-1.el6.i686.rpm

libstdc++-4.4.7-3.el6.i686.rpm

nspr-4.9.2-1.el6.i686.rpm

nss-3.14.0.0-12.el6.i686.rpm

nss-softokn-freebl-3.12.9-11.el6.i686.rpm

nss-util-3.14.0.0-2.el6.i686.rpm

openldap-2.4.23-31.el6.i686.rpm

sshpass-1.05-1.el6.rf.i686.rpm

openssl-1.0.0-27.el6.i686.rpm
This example uses Red Hat Enterprise Linux 6.4. For other Red Hat Enterprise Linux 6.X, make sure the
package names are the same.
To install the packages, perform the following tasks:
1.
Log in to Red Hat Enterprise Linux as a root user.
55
2.
Place the Linux installation disk to the CD-ROM drive and enter the directory where packages are
saved.
3.
Copy the packages to the local directory and download sshpass-1.05-1.el6.rf.i686.rpm from the
network.
4.
Launch the Terminal window and enter the directory where packages are saved.
5.
Execute the command to install packages, where xxx indicates the package name.
rpm -i --nodeps xxx
Installation and configuration procedure
1.
Enter the tools directory on the IMC installation disk, copy file vrm-plug-linux.zip to a local disk
drive, and decompress the file.
2.
Run the install.sh script in the decompressed file folder.
3.
Enter the IP address of the IMC server.
4.
Run ps –ef | grep imcvrmagent to verify the installation is successful.
When the agent is successfully installed, you can see the imcvrmagent process is running.
Installing Android clients
Mobile clients (such as smart phones) can access IMC resources to manage and monitor IMC. This
edition of IMC supports the access of mobile devices running an Android operating system.
A mobile device must meet the following requirements before it can access IMC:

The device is installed with the operating system of Android 2.1 update1 or a later version.

The screen resolution is HVGA(480*320) or WVGA(800*480).

The mobile device can communicate with the IMC server (for example, through a wireless
connection).
To install an Android client:
1.
Access the website http://imc-addr:port/imc/noAuth/imc.apk by using the embedded browser
of the mobile device to automatically download the client installation program.
imc-addr is the IP address of the IMC server, and port is the HTTP port number (8080 by default)
set when IMC was deployed for the first time.
2.
Install the program as prompted.
When the message Programs from unknown sources are not allowed to install appears during
installation, go to Settings > Applications and select Unknown source.
To log in to IMC:
1.
Open the client program.
2.
Enter the IMC server address, login name, and password.
The IMC server address is in the format of http://imc-addr:port, where imc-addr is the IP address
of the IMC server and port is the HTTP port number (8080 by default). Do not add /imc to the end
of the address. To use a secure connection, enter the address in the format of
https://imc-addr:port (the port number defaults to 8443). When HTTPS does not use the default
port number when IMC was deployed for the first time, enter the specified port number.
56
The login name must be an existing login name, which has the privilege to access iMC Platform >
Resource Manager > Mobile Client Access in IMC.
3.
Select Save password or Auto Login as needed.
When you select Save password, you do not need to enter the password for the next logins. When
you select Auto Login, you do no need to enter the login name and password for the next logins.
4.
Click Login to log in to the IMC server.
You can use the Android client to implement the following functions:

View information about faulty devices and interfaces, and query specific devices.

View device alarms.

Inform real-time alarms.

Test device reachability by using ping or traceroute.

View custom views and device views.

Use an Android browser to access IMC to perform configuration and management operations.

Play IMC videos.
NOTE:
When RADIUS authentication or LDAP authentication is used or when you change the login password,
you must first log in to the IMC from a PC successfully before you can use a mobile client to log in to IMC.
Installing LLDP agent plug-ins
When the VRM component is deployed, you must install an LLDP agent for topology calculation.
An LLDP agent contains the following packages: lldp-agent-redhat.zip, lldp-agent-ubuntu.zip, and
lldp-agent-windows.zip. The first two packages are installed on a KVM server and the last package is
installed on a Microsoft Hyper-V server. The installation procedure for lldp-agent-redhat is similar to that
for llap-agent-ubuntu, and the following sections describe the installation procedure for
lldp-agent-redhat.
Before the LLDP agent installation, copy the three packages to the target server and decompress the
packages. If you are using a Windows server, copy the lldp-agent-windows.zip file to a non-system disk.
IMPORTANT:
Do not delete the folder where the decompressed installation packages reside after completing the LLDP
agent installation.
Installing an LLDP Linux agent
LLDP Linux agent plug-ins apply only to 64-bit Linux, including Redhat 5.5, Ubuntu 11.0, and their later
versions.
To install and configure an LLDP Linux agent:
1.
Set executable permission to the install.sh script and run the script in the LLDP Linux agent
installation file folder.
57
The LLDP Linux agent is installed.
2.
Configure the LLDP Linux agent.
The configuration file lldpagent.conf is located in the conf directory of the LLDP Linux agent
installation file folder.
LLDP agent plug-ins support either LLDP or CDP, but not both at the same time. By default, the
plug-ins support LLDP. To enable an LLDP agent to support CDP:
a. Open the lldpagent.conf file in the conf directory.
vi lldpagent.conf
b. Delete the pound sign (#) from the string #Agent=CDP.
You can set the interval at which LLDP or CDP packets are sent. The default setting is 300 seconds.
To change the setting, delete the pound sign (#) from the string #INTERVAL=300 and change the
value.
3.
Restart the lldp-agent service.
service lldp-agent restart
Installing an LLDP Windows agent
LLDP Windows agent plug-ins support 32-bit and 64-bit Windows operating systems.
To install and configure an LLDP Windows agent:
1.
Run the install.bat script in the LLDP Windows agent installation file folder.
The LLDP Windows agent is installed.
2.
Configure the LLDP Windows agent.
The configuration file lldpagent.conf is located in the conf directory of the LLDP Windows agent
installation file folder.
LLDP agent plug-ins support either LLDP or CDP, but not both at the same time. By default, the
plug-ins support LLDP.
To enable an LLDP agent to support CDP:
a. Open the lldpagent.conf file in the \Program Files\lldpAgent\ directory on the Windows
system disk.
b. Delete the pound sign (#) from the string #Agent=CDP.
You can set the interval at which LLDP or CDP packets are sent. The default setting is 300 seconds.
To change the setting, delete the pound sign (#) from the string #INTERVAL=300 and change the
value.
c. Restart the lldp-agent service
58
7 Logging in to IMC
IMC is a browser-based management tool. HP recommends accessing IMC with the following Web
browsers:

Internet Explorer 10 or 11

Firefox 30 or later

Chrome 35 or later
Accessing IMC
The default Web service ports of IMC are 8080 (HTTP) and 8443 (HTTPS).
1.
Enter the IMC login page using one of the following methods:

Through HTTP:
Enter http://192.168.4.44:8080/imc in the address bar of your browser and press Enter. The
portion 192.168.4.44 is the IP address of the server where IMC is deployed, and 8080 is the
HTTP port set during the IMC Platform deployment. A security certificate message appears. For
more information, see HP IMC Getting Started Guide.

Through HTTPS
Enter https://192.168.4.44:8443/imc in the address bar of your browser and press Enter.
The portion 192.168.4.44 is the IP address of the server where IMC is deployed, and 8443 is
the HTTPS port set during the IMC Platform deployment. A security certificate message
appears. For more information, see HP IMC Getting Started Guide.
2.
Enter the username and password, and then click Login.
By default, the IMC superuser name and password are admin and admin.
IMPORTANT:
Change the admin password immediately after the initial login.
Securing IMC
HP recommends performing the following tasks to secure IMC:

Create individual administrative user accounts and disable the default admin account.

Tie the administrative accounts to a central AAA server via LDAP or RADIUS.

Retain one administrative account (not named admin) with a local password to recover from loss of
access to the AAA server.

Enable the verification code feature on the IMC login page. For more information, see IMC Getting
Started Guide.
See v7.1 HP Intelligent Management Center Base Platform Administrator Guide.
59
Accessing UAM
There are several web-based features in UAM that have different URLs than IMC.
When the UAM user self-service component is deployed, access the IMC self-service center by
entering either of the following addresses in the address bar of the browser:


http://192.168.4.66:8080

http://192.168.4.66:8080/selfservice
192.168.4.66 is the IP address of the server where the UAM user self-service is deployed and
8080 is the HTTP port number set the first time the IMC platform subcomponents were deployed.
When the SOM service desk is deployed, access the service desk by entering
http://192.168.4.22:8080/servicedesk in the address bar of the browser.

192.168.4.22 is the IP address of the server where the SOM service desk is deployed and 8080
is the HTTP port number set the first time the IMC platform subcomponents were deployed.
If you cannot access IMC using the Web browsers, check your hardware and browser configuration
described in Table 9.
Table 9 Hardware and browser requirements
OS
Hardware
 CPU: 2.0 GHz or higher
 Memory: 2 GB or higher
 Hard Disk: 20 GB or
higher
Windows
 CD-ROM: 48 X or higher
 Network Adapter: 100
Mbps or higher
Browser version
Browser setting requirements
 IE 10 or 11
 Firefox 30 or
 Turn off the pop-up blocker in
later
 Chrome 35 or
later
 Sound card: Required.
 Display: Recommended
Internet Explorer.
 Enable Cookies in Internet Explorer.
 Add IMC as a trusted site.
width 1280
JRE 1.6.0_update10 or later is recommended. If a client has no JRE, IMC prompts the user to install JRE
for the client.
Displaying a user agreement
You can display a user agreement on the IMC login page to inform operators of the rights and
obligations for IMC login. To log in to IMC, operators must accept terms of the user agreement.
To display a user agreement on the IMC login page:
1.
On the IMC server, access the \client\conf directory in the IMC installation path.
2.
Open the commonCfg.properties file in Notepad (as administrator) or vi.
3.
Change the value of the enableTerms parameter to true.
4.
Save and close the commonCfg.properties file.
5.
Prepare a user agreement in HTML format named terms.html.
60
6.
Save the terms.html file to the \client\web\apps\imc directory in the IMC installation path.
Re-login to IMC. A User agreement link appears under the username and password area. Operators
can click the link to view terms of the user agreement. The Login button is grayed out unless I accept the
terms in the user agreement is selected.
Figure 50 User agreement on login page
61
8 Upgrading, backing up, or removing IMC
The following information describes how to upgrade IMC components, using upgrading IMC Platform
patches as an example.
After installing the IMC Platform and components, when you want to upgrade the IMC Platform, first
make the following preparations:

For data safety, HP recommends that you back up the database and the entire IMC installation path
because it is not done during upgrade. For how to back up the IMC database, see "11 Database
backup and restoration"

Download the upgrade packages for all listed components before you upgrade the IMC Platform.
Backing up IMC
To back up the IMC installation directory and database files:

Use DBMan in the Intelligent Deployment Monitoring Agent to back up database files.

Manually copy the IMC installation directory to a specific path.
Upgrading IMC
CAUTION:
 Make sure you have compatible upgrade packages for all deployed IMC components. Otherwise, the
components that are not upgraded become invalid after the IMC Platform upgrade.
 To upgrade IMC from version 3.x to version 5.x, re-login to the registration website and obtain a new
activation file.
 Do not upgrade IMC by running the install\install.bat script in the IMC installation path.
To upgrade an IMC component, make sure that the IMC Platform has been installed and any dependent
components have been upgraded. Before you upgrade a service component that is related to the Report
Management subcomponent, upgrade the Report Management subcomponent to a version compatible
with the service component. Otherwise, the report function might be abnormal.
To upgrade the IMC Platform:
1.
Use one of the following methods to start upgrade:


On the Installation Completed window, as shown in Figure 14, select Install Other Components,
and click Finish.
After you have installed and deployed the IMC Platform, click Start > All Programs > HP
Intelligent Management Center > HP Deployment Monitoring Agent (or run the dma.sh script in
/deploy of the IMC installation path on Linux), to start the Intelligent Deployment Monitoring
Agent and click Install new components on the Monitor tab.
62
CAUTION:
 To upgrade IMC in Windows Server 2003 or Windows Server 2003 R2, log in as an administrator and
upgrade IMC.
 To upgrade IMC in Windows Server 2008 or Windows Server 2008 R2, you must first select Start > All
Programs > HP Intelligent Management Center, right-click Deployment Monitoring Agent, and select
Run as Administrator from the shortcut menu to open the deployment monitoring agent.
2.
On the system tray of Windows, right-click the Deployment Monitoring Agent icon, and select
Install from the menu.
The Choose folder window appears, as shown in Figure 51.
Figure 51 Choose folder
3.
Click Browse, and select folder install\components in the upgrade files.
4.
Click OK.
The Welcome to HP IMC Installation Wizard window appears, as shown in Figure 52.
Figure 52 Welcome to HP IMC Installation Wizard
5.
Click Next.
63
The Agreement window appears, as shown in Figure 53.
Figure 53 Agreement
6.
Read the license agreement carefully and select Accept.
7.
Click Next.
The Upgrade Common Components window appears, as shown in Figure 54.
Figure 54 Upgrade Common Components
The system automatically starts upgrading common components, as indicated by the Upgrade
Common Components window, as shown in Figure 55.
Figure 55 Upgrade Common Components
64
After the common components are upgraded, the Choose Target Folder window appears, as
shown in Figure 56.
Figure 56 Choose Target Folder
The Choose Target Folder window displays the components to be upgraded. The system installs the
upgrade files in the location where the IMC Platform is installed.
8.
Check the information and click Next.
The Deployment and Upgrade Options window appears, as shown in Figure 57.
65
Figure 57 Deployment and Upgrade Options
9.
Select Deploy or upgrade at once or Deploy or upgrade later. In this example, select Deploy or
upgrade at once.
10. Click Next.
The Installation Summary window appears, as shown in Figure 58.
Figure 58 Installation Summary
66
11. Check the installation summary and click Install.
The Installing window appears, as shown in Figure 59.
Figure 59 Installing
The installation wizard installs the components.
After the installation is finished, the Batch upgrade window appears, as shown in Figure 60.
67
Figure 60 Batch upgrade
12. Select the components you want to upgrade and click OK.
After the selected components are upgraded, the Batch upgrade result window appears, as
shown in Figure 61.
Figure 61 Batch upgrade result
13. Click OK.
If you have used DBMan for IMC auto backup or restoration before upgrade, the Auto Backup and
Recovery Settings window appears after you click OK. Click OK in the Auto Backup and Recovery
Settings window to upgrade automatic backup and restoration configuration.
14. Click Start iMC on the Monitor tab.
When upgrading service components related to the Report Management module, you must also
upgrade the Report Management module to the version compatible with these related service
components, so that you can use the report function correctly.
68
Restoring IMC
When an error occurs during the IMC upgrade, check the environment (for example, check whether the
database is available) and upgrade IMC again. If the IMC upgrade still fails, follow these steps to restore
IMC to the version before the upgrade:
1.
Restore the IMC database. See "Manual restore."
2.
When the restoration is complete, stop the Intelligent Deployment Monitoring Agent and IMC
service.
3.
Manually delete all the files in the IMC installation path.
4.
Copy the backed up IMC installation directory to the IMC installation path.
5.
Restart the Intelligent Deployment Monitoring Agent and IMC service.
For IMC running in stateful failover mode, only restore IMC on the active server in the failover system.
Removing IMC
The following describes how to remove IMC from a Windows Server 2008 R2-based machine.
Removing an IMC component
Before removing an IMC component, remove any components that depend on it.
1.
Launch the Intelligent Deployment Monitoring Agent on the IMC server.
2.
On the Monitor tab, click Stop IMC to stop the IMC service.
3.
On the Deploy tab, select Undeploy the Component from the right-click menu of the component
that you want to undeploy.
A dialog box appears, indicating that the component was successfully undeployed.
4.
Click OK.
5.
On the Deploy tab, select Remove this Component from the right-click menu of the component that
you have undeployed.
A dialog box appears, indicating that the component was successfully removed.
6.
Click OK.
Removing all IMC components at one time
The following sections describe how to remove the IMC software deployed in centralized mode.
When reinstalling IMC, you must manually delete the folder named IMCdata, which is created on the
IMC server upon installation of IMC when you have re-installed an SQL Server database after you
uninstalled IMC.
When you fail to install or uninstall IMC, manually delete the IMC installation folder and the
IMC-Reserved folder in the Windows installation directory. Otherwise, IMC cannot be reinstalled.
1.
Launch the Intelligent Deployment Monitoring Agent.
2.
On the Monitor tab, click Stop IMC to stop the IMC service.
69
3.
Launch the IMC uninstaller.


On windows, select Start > All Programs > HP Intelligent Management Center > Uninstall HP
Intelligent Management Center.
On Linux, run the uninstall.sh script in /deploy of the IMC installation path.
A window appears to guide you through the rest of the process.
4.
Click Uninstall.
A confirmation dialog box appears.
5.
Click OK.
6.
In the Uninstallation Completed dialog box, clear the OS reboot option and click OK.
7.
Delete the IMC-Reserved folder in the WINDOWS folder of the system disk (or delete the
IMC-Reserved folder in the /etc/ directory on Linux).
8.
Reboot the system.
70
9 Registering IMC and incremental node
licenses
An unregistered IMC version delivers the same functions as that of a registered IMC, but can be used
only for 60 days since the date on which the IMC service was first started. To unlock the time limitation
or add extra nodes to IMC, the IMC licenses you have purchased must be registered and then activated
in the IMC Platform.
The IMC registrations on Windows and Linux systems are similar. The following describes how to register
IMC on a Windows Server 2008 R2-based machine. Ensure you Register and Activate IMC before any
additional node licenses.
NOTE:
To transfer an existing license to a different Serial Number, contact HP Support.
Registering IMC
From the IMC login page click on the Activate link to enter the License Information page appears.
Figure 62 License Information
Select and copy or make a note of the Serial Number (this is unique to your installation of IMC).
Registering the first license
1.
Go to the HP My Networking system website (http://hp.com/networking/mynetworking/), log in
to My Networking portal, and the HP Passport sign-in page appears.
71
Figure 63 HP Passport sign-in
2.
Enter the User ID and Password and click Sign in.
The Home page appears.
Figure 64 Home page
3.
Click Register license under the Licenses section of the home page.
The Enter Order number or Registration ID page appears.
72
Figure 65 Enter Order number or Registration ID page
4.
Enter the Order number or Registration ID and click Next.
The Enter the email associated with Order number page appears.
Figure 66 Enter the email associated with Order number page
5.
Enter an email address associated with the Order number and click Next.
The Select the Product License page appears.
Figure 67 Select the Product License page
73
6.
Select the product you want to register by activating the radio button to the left of the license
Product #.
7.
Enter the quantity to be redeemed and click Next.
The Enter details page appears.
Figure 68 Enter details page
8.
Enter the IMC software serial number and click Next.
The License agreement page appears.
Figure 69 License agreement page
9.
Read the license agreement, select I accept all of the above terms, and click Finish.
The Confirmation page appears.
74
Figure 70 Confirmation page
10. Click Save as to download and save the license key file.
Remember the location and file name for the next step of Activating the License in IMC.
11. If you want to email the confirmation information and license key file, enter the recipient’s email
address in the Send license confirmation to field, add any Comments and click Send email. Also,
you can view the details of the license you have registered.
Registering incremental node licenses
Registering an Incremental Node License is similar to registering the first license. The following
information describes only the differences between them.
To register an Incremental Node license:
1.
Select the Incremental Node License you want to register on the Select the Product License page.
75
Figure 71 Select the Product License page
2.
Click Next.
The Enter details page appears.
Figure 72 Enter details page
3.
Select you base product, enter the base software serial number, and click Next.
The Confirmation page appears.
4.
Click Save as to download and save the license key file.
You need to remember the location and file name for the next step of Activating the License in IMC.
76
Activating IMC
To activate IMC:
1.
Return to the License Information page (see Figure 62).
2.
Select Activate now.
The Activate Your Product page appears.
Figure 73 Activate Your Product
3.
Select the license file in the format of .txt.
4.
Select the license type, which can be Register/Activate host license or Register/Activate back-up
license, as needed.
5.
Click OK.
The Activations Succeeded dialog appears.
Figure 74 Activation Succeeded
6.
Reboot the system.
Your IMC system has now been successfully Registered and Activated.
Registering the IMC license for stateful/stateless
failover
Registering the IMC license for stateful failover
1.
Run IMC on the primary server.
2.
After the IMC starts up, access the IMC login page.
3.
Click Activate.
The License Information page appears.
77
Figure 75 License information
4.
Record the serial number of the primary server that is displayed in the Serial Number area.
5.
Switch the IMC services to the backup server and access the IMC login page again.
6.
Click Activate.
The License Information page appears.
7.
Record the serial number of the backup server in the Serial Number area.
8.
Log in to the HP My Networking system website (http://hp.com/networking/mynetworking/),
enter required information, and enter the serial numbers of the host and the IMC stateful server.
9.
Download and save the IMC license file locally.
For more information, see "Registering the first license."
10. Switch the IMC services back to the primary server and access the IMC login page again.
11. On the IMC login page, click Activate.
The License Information page appears.
12. Click Activate Now.
The registration page appears.
Figure 76 Registering your product
13. Click Browse to select the locally saved IMC license file.
14. Select Register/Activate host license from the Please select the license's type list.
15. Click OK.
16. Reboot the IMC.
The IMC has been successfully activated.
78
Registering the IMC license for stateless failover
When registering the IMC license for stateless failover, only the serial number of the primary server is
required to get the license file. Use this file on both the IMC primary server and the IMC backup server
to activate the license.
1.
Run IMC on the primary server.
2.
After the IMC starts up, access the IMC login page of the primary server.
3.
Click Activate.
The License Information page appears.
Figure 77 License information
4.
Record the serial number of the primary server that is displayed in the Serial Number area.
5.
Log in to the HP My Networking system website (http://hp.com/networking/mynetworking/),
enter required information, and enter the serial number of the host.
6.
Download and save the IMC license file locally.
For more information, see "Registering the first license."
7.
Access the IMC login page of the primary server again.
8.
Click Activate.
The License Information page appears.
9.
Click Activate Now.
The registration page appears.
Figure 78 Registering your product
10. Click Browse to select the locally saved IMC license file.
11. Select Register/Activate host license from the Please select the license's type list.
79
12. Click OK.
13. Reboot the IMC.
The IMC has been successfully activated on the primary server.
14. Access the IMC login page of the backup server.
15. Click Activate.
The License Information page appears.
16. Click Activate Now.
The registration page appears.
17. Click Browse to select the locally saved IMC license file. (This license file is the same as the file
used for the IMC registration on the host.)
18. Select Register/Activate back-up license from the Please select the license's type list.
Figure 79 Registering your product
19. Click OK.
20. Reboot the IMC.
The IMC has been successfully activated on the backup server.
Upgrading to an IMC V7.1 license
Your existing eSupport account including your IMC licenses have been transferred to My Networking
and a HP Passport account has been created with your eSupport user name.
The HP My Networking system address: http://hp.com/networking/mynetworking.
Your IMC license file has been updated in My Networking to support IMC V7.1.
You need to download your updated IMC license file from My Networking and reactivate your IMC V7.1.
To update your IMC license file from My Networking and reactivate your IMC V7.1:
1.
Locate your IMC Serial Number:
a. Follow the Activate link from the IMC login page to enter the License Information page and
your IMC serial number appears.
b. Select your IMC serial number, and copy and paste the serial from the IMC License information
page to My Networking.
2.
Reset your new HP Passport password so you can login to My Networking using your new HP
Passport account:
a. Go to the HP My Networking system website: http://hp.com/networking/mynetworking.
b. Log in to My Networking portal, and the HP Passport sign-in page appears.
80
Your eSupport user account has been transferred to My Networking and a HP Passport account
has been created using your eSupport user name.
c. Reset your HP Passport password before you can log in by following the Forgot Password link.
d. Provide the email address of your eSupport account user to receive instructions on resetting
your password.
e. Follow the email instructions to click on the Choose a new password link.
f.
Enter your new HP Passport password and select your security questions and answers.
Your HP Passport password is now reset, allowing you to log in to My Network using the HP
Passport account with your eSupport user name and password.
3.
Log in to My Networking
4.
Click Continue in the Change HP Passport password page to log into My Networking.
The Welcome <username> page appears.
5.
Locate your IMC licenses
6.
Click the My Licenses tab from the tabular navigation system on the top.
The Enter Order number or Registration ID page appears.
7.
Click on View Licenses from the My Licenses navigation.
8.
Locate your IMC Platform license in the list of your licenses.
When necessary copy and paste your IMC serial number into the search field and click Search.
9.
Download the updated IMC license file
10. Click
corresponding to the IMC Platform license.
The license information page appears.
11. Click the Download License link.
12. Choose to save the license file, and choose where to save the license file.
Save the license file so that you can locate it again when you need it.
Updating your IMC V7.1 license file
1.
Follow the Activate link on the IMC login page to enter the License Information page.
2.
Click Activate now.
The Activate Your Product page appears.
3.
Browse to the location where you saved the license file and select it, and click OK.
The Activations Succeeded dialog appears.
4.
Select the license file, which should be in .txt format.
5.
Select the license type, which can be Register/Activate host license or Register/Activate back-up
license, as needed.
6.
Click OK.
The Activations Succeeded dialog appears.
Your IMC V7.1 is now fully licensed with the equivalent licenses you had previously.
81
10 Security settings
Anti-virus software
To ensure secure operation, HP recommends installing anti-virus software on IMC servers and keeping
the virus definitions up to date.
Port settings
HP recommends using a firewall to protect the IMC server cluster, that is, filter the non-service data sent
to the IMC server. In this way, you can prevent abnormal attacks.
CAUTION:
 HP recommends that you use ACL configurations on a firewall rather than on a switch to control data
packets. Otherwise, packet fragmentations are filtered.
 When you have installed firewall software on the IMC server, besides setting the ports listed in Table 10,
set an IP address for the IMC servers to ensure normal communication between them.
Table 10 and Table 11 list the port numbers used by IMC components.
Table 10 Ports used by the IMC Platform
Default port number
Usage
Location
TCP 8080, configurable
HTTP access to IMC
Device
TCP 8443, configurable
HTTPS access to IMC
Device
TCP 61616
Java Message Broker
Device
UDP 161
Port to add a device to the IMC
Device
UDP 22
Port for SSH operations
Device
TCP 23
Port for Telnet operations
Device
UDP 514, 515
Port for syslog operations
IMC server
UDP 162
Port for trap operations
IMC server
UDP 69
Port for Intelligent Configuration Center to perform
configuration management through TFTP
IMC server
TCP 20, 21
Port for Intelligent Configuration Center to perform
configuration management through FTP
IMC server
Table 11 Port numbers used by the IMC NTA/UBA
Default port number
Usage
Location
UDP 9020, 9021, 6343
Port for the IMC server to receive logs
IMC server
82
Default port number
Usage
Location
TCP 8051
Listening port used to monitor the command for stopping
the NTA/UBA service
IMC server
TCP 9099
JMX listening port for the NTA/UBA service
IMC server
UDP 18801, 18802, 18803
Communication ports between the NTA and UBA
IMC server
When a firewall resides between the probe and the IMC server, you need to configure an ACL on the
firewall so that all the IP packets from the probe can be sent to the IMC server.
A sample of the Windows Firewall configuration after IMC platform installation is:
netsh advfirewall firewall add rule name="HP IMC HTTP" protocol=TCP localport=8080
action=allow dir=IN
netsh advfirewall firewall add rule name="HP IMC" protocol=TCP localport=61616
action=allow dir=IN
83
11 Database backup and restoration
DBMan is the automatic backup and restoration tool for the IMC Platform and service component
databases, and provides a full-range system disaster backup solution. DBMan uses a standard SQL
backup and restoration mechanism to process the complete databases.
DBMan supports both manual and automatic database backup and restoration. It is integrated in the
Intelligent Deployment Monitoring Agent, as shown in Figure 80.
Figure 80 Environment tab
The screen is broken into the following sections.

The software and hardware information of the servers displays on the left of the Environment tab.

The usage of the user database file and log file displays on the right.

The DBMan database backup and restoration configuration displays at the bottom.
The DBMan database backup and restoration configuration includes the following options:

Configure—Provides automatic backup and restoration function, which can back up and restore
database files on a regular basis. You can also upload backup database files to an FTP server for
storage. The automatic backup and restoration function is used mainly in stateless failover
scenarios.

Backup—Immediately backs up all data files (including running configuration files and database
files) of the current IMC server.
84

Restore—Replace the current database files with the backup database files to restore the database
to the specified time point.

View Log—View the database backup and restoration log.
NOTE:
To ensure correct operation of IMC, do not back up and restore database between different OSs.
Manual backup
Manual backup allows you to manually back up all data files of the server running IMC immediately.
To perform a manual backup:
1.
Start the Intelligent Deployment Monitoring Agent on the server.
2.
Click the Environment tab.
3.
Click Backup.
A confirmation dialog box appears.
4.
Click OK.
The Select database backup path dialog box appears.
5.
Select the backup file save path.
6.
Click OK.
DBMan starts to back up all database files used by the IMC system on the server to the specified
path.
Manual restore
CAUTION:
HP recommends restoring database files for the IMC Platform and deployed components together. If you
restore only some of them, data loss or inconsistency might occur.
Manual restoration allows you to restore the IMC database files to the files of the specified backup time
point. Make sure IMC is started at least once after installation and the backup database files exist.
To perform a manual restoration:
1.
Start the Intelligent Deployment Monitoring Agent on the server.
2.
Click the Environment tab.
3.
Click Restore.
The Restoration Type dialog box appears.
85
Figure 81 Restoration Type dialog box
4.
Click Locally Restore.
A confirmation dialog box appears.
Figure 82 Confirmation dialog box
5.
Click Yes.
6.
Select database files to be restored and click OK in the popup dialog box.
7.
Click OK in the popup dialog box.
DBMan starts to restore the databases and displays a restoration success message after the
restoration is complete.
8.
Click OK. IMC will be automatically started.
NOTE:
During the restoration process, DBMan shuts down and restarts IMC and the database service.
Automatic backup
You can configure automatic database backup to periodically back up the IMC database files to the
local database, and to upload the backup database files to the FTP server or the master server of the
backup system.
To configure automatic backup:
1.
Start the Intelligent Deployment Monitoring Agent on the server where IMC is deployed.
2.
Click the Environment tab.
3.
Click Configure.
The Auto Backup and Recovery Settings dialog box appears, as shown in Figure 83.
86
Figure 83 Auto Backup and Recovery Settings
4.
Read the prompt on the Auto Backup and Recovery Settings dialog box carefully, select Auto
Backup Model, and click OK, as shown in Figure 83.
The Auto Backup and Recovery Settings window appears, as shown in Figure 84.
Figure 84 Auto backup mode
87
5.
Click the Basic Configuration tab and configure the following parameters:





6.
Daily backup time (HH:mm)—Enter the time at which the automatic backup operation starts
every day. By default, the daily backup time is 04:00.
Master Server IP of Backup System—Enter the IP address of the master server in the backup
system. This option is applicable to database backup in stateless failover scenarios. Make sure
automatic restoration is enabled for the backup system.
Storage Path of Other Files—Enter or browse to the path where the backup data files are stored.
Local Back Up—Select the boxes in the Local Back Up column for the databases you want to
back up. By default, the boxes in the Local Back Up column are selected for all databases. You
can select or clear the boxes for all databases.
Upload To Backup System—Select the box in the Upload To Backup System column for a
database to upload the database file to the specified FTP server or the master server of the
backup system. By default, the boxes in the Upload To Backup System column are cleared for all
databases. You can select or clear the boxes for all databases. After you select this box, you
must configure the FTP server, the master server IP of the backup system, or both.
Click the Extension Configuration tab and configure the following parameters:


Backup file lifetime (days)—Enter the number of days a backup database file can be kept.
Expired files are automatically deleted.
Delete local files after upload even if upload fails—Specify whether to delete local backup files
after uploading the backup files to the FTP server or the backup server. To configure the FTP
server, manually create or configure the dbman_ftp.conf file in the \dbman\etc directory of the
IMC installation directory. The configuration file includes the configuration items ftp_ip,
ftp_user, and ftp_password in the following format:
ftp_ip=1.1.1.1
ftp_user=admin
ftp_password=1234
7.
Click OK.
Automatic restore
Automatic restoration applies to the backup server in stateless failover scenarios. Automatic restoration
must work together with automatic backup on the primary server. To synchronize data on the primary
server to the backup server, make sure the following requirements are met:

The master server IP address of the backup system is configured in DBMan of the primary server.

The boxes in the Upload to Backup System column in the Databases to Back Up area are selected
in DBMan of the primary server.

Restoration settings are configured in DBMan of the backup server.
After automatically backing up data, the primary server performs the following operations:
1.
Immediately uploads backup data to the restoration path (Backup files location) on the backup
server.
2.
Instructs the backup server to automatically restore the data.
To configure automatic restoration on the backup server:
3.
Start the Intelligent Deployment Monitoring Agent on the backup server.
88
4.
Click the Environment tab.
5.
Click Configure.
The Auto Backup and Recovery Settings dialog box appears, as shown in Figure 85.
Figure 85 Auto Backup and Restore Settings
6.
Read the prompt on the Auto Backup and Recovery Settings dialog box carefully, select Auto
Restore Model, and click OK, as shown in Figure 85.
The Auto Backup and Recovery Settings page appears, as shown in Figure 86.
89
Figure 86 Auto Backup and Recovery Settings
7.
In the Backup files location field, enter or browse to a path where the uploaded backup database
files are stored.
8.
In the Databases to Restore area, select the boxes in the Restore column for the databases you
want to restore. By default, the boxes are selected for all databases.
9.
Click OK.
NOTE:
Automatic restoration settings in this example apply only to the failover system that is deployed in
centralized mode and uses an embedded database.
90
Database backup and restore by using DBMan
Database backup and restoration includes the following types:

Database backup and restoration for a single IMC system—You can configure DBMan to
automatically or manually back up the database files to the local server. However, you can only
manually restore the backed up database files.

Database backup and restoration in IMC stateless failover—The primary server automatically
backs up and uploads database files to the backup server. The backup server performs automatic
restoration. When the primary server fails, IMC automatically switches to the backup server.
Database backup and restore for a single IMC system
To back up the local database of a single IMC system, perform manual backup or configure automatic
backup by using DBMan. For more information, see "Manual backup" or "Automatic backup."
To restore the local database for a single IMC system, perform manual restoration. For more information,
see "Manual restore."
Database backup and restore in IMC stateless failover
CAUTION:
Before you configure DBMan, make sure the primary and backup servers use the same operating system,
IMC version and patches, and database type and version.
Commonly used stateless failover scenarios are configured as follows:

The primary IMC system is deployed in centralized mode and uses an embedded database.

The failover system is deployed in centralized or distributed mode.
The license type is selected as primary server license on the primary server, and as backup server license
on the master of the failover system.
Automatic backup and automatic restoration are configured on the primary server and backup server
respectively.
In a stateless failover scenario, the primary server performs the following operations:
1.
Uses DBMan to periodically back up database files.
2.
Uploads the backup database files to the backup server.
3.
Instructs the backup server to perform automatic restoration to synchronize data from the primary
server.
Then the backup server automatically restores database files.
91
NOTE:
In a stateless failover scenario, you can perform any of the operations in the Auto Backup and Recovery
Settings dialog box to back up data:
 Clear the option Delete local files after upload even if upload fails in the automatic backup
configuration on the primary server.
 Set a path in Backup files location fields in the automatic restoration configuration on the backup server.
For more information about automatic backup, see "Automatic backup."
For more information about automatic restoration, see "Automatic restore."
Configuration guidelines

To add more configurations in the backup and restoration configuration file besides the properties
configured with DBMan in the Automatic Backup and Restoration window, write the configurations
to be added to file dbman_addons.conf at the \dbman\etc directory in the installation path. After
you save the file, IMC automatically executes the configurations you added.
For example, write the following before or after database restoration:
BeforeSQLScript_monitor_db_IMC_monitor = D:\1.bat
AfterSQLScript_monitor_db_IMC_monitor = D:\2.bat

In an IMC stateless failover system, a backup license for the iAR report/table customization function
provides read-only access. To synchronize the report/table template of the master system to the
backup system, you must advertise that template on the backup system by using the trial version and
then register the backup system.
92
12 FAQ
When I was deploying IMC components by using SQL Server 2008 R2 Express, I failed to create my
database. How can I solve this problem?
Modify the security attribute of the IMC data folder after deploying IMC components by following these
steps:
1.
Right-click the IMC data folder (the default folder is IMCdata).
2.
Click Properties on the shortcut menu. The Properties dialog box appears.
3.
Select the Security tab and allow Users to have full control of the folder.
4.
Click OK.
After IMC is installed in the Windows Server 2003 64-bit edition, the IMC background processes cannot
be started. How can I solve this problem?
Before installing IMC in Windows Server 2003 64-bit OS, you must first install the
WindowsServer2003-KB942288-v4-x64.exe patch. Otherwise, part of IMC processes cannot start after
installation and deployment.
To solve this problem, stop IMC, install the WindowsServer2003-KB942288-v4-x64.exe patch, and
manually execute IMC installation path\deploy\components\server\vcredist.exe.
During the component deployment process, an error message “Deployment is stopped with error. For
details, see the log.” appears, and “Execute database script error!” is displayed in the system log.
When I check the specified log file according to the prompt information, only the error information that
the object dbo.qv.id already exists is displayed. How do I solve the problem?
Log in to the Query Analyzer of SQL Server as an sa user and execute the following commands:
use model
EXEC sp_droptype 'qv_id'
Deploy the component again.
When installing IMC on a PC running Windows Server 2008 R2, the system indicates the Windows
Installer cannot be installed, as shown in the following figure. How do I solve this problem?
On the Windows Installer dialog box, click Browse. On the dialog box for selecting a file, search any
folder whose name contains digits and letters abcdef in the root directory, select file vc_red.msi in the
folder, and click OK. Then, you can continue the installation.
93
Figure 87 Windows Installer
On Windows, IMC service processes cannot be started or stopped after IMC runs for a certain period of
time. How do I solve the problem?
This problem is caused by insufficient virtual memory. Set the virtual memory to the system managed size
on the server.
To set the virtual memory to the system managed size:
1.
On the server, open the Control Panel window, and click the System icon. The System Properties
dialog box appears.
Figure 88 System properties
2.
Select the Advanced tab, and click Settings in the Performance area. Then the Performance
Options dialog box appears.
94
Figure 89 Performance options
3.
On the Performance Options dialog box, select the Advanced tab, and click Change in the Virtual
memory area. The Virtual Memory dialog box appears.
Figure 90 Virtual memory
4.
Select the System managed size option, click Set, and click OK.
95
96
Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:

Product model names and numbers

Technical support registration number (when applicable)

Product serial numbers

Error messages

Operating system type and revision level

Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals

For related documentation, navigate to the Networking section, and select a networking category.

For a complete list of acronyms and their definitions, see HP A-Series Acronyms.
Websites

HP.com http://www.hp.com

HP Networking http://www.hp.com/go/networking

HP manuals http://www.hp.com/support/manuals

HP download drivers and software http://www.hp.com/support/downloads

HP software depot http://www.software.hp.com
97
Conventions
The following information describes the conventions used in this documentation set.
GUI conventions
Convention
Description
Boldface
Window names, button names, field names, and menu items are in bold text. For
example, the New User window appears; click OK.
>
Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention
Description
WARNING!
Indicates that the failure to follow directions could result in bodily harm or death.
CAUTION
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT
Provides clarifying information or specific instructions.
NOTE
TIP
Provides additional information.
Provides helpful hints and shortcuts.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
98
Download PDF