HP Intelligent Management Center Installation Guide (IMC PLAT 5.1 (E0202))

HP Intelligent Management Center Installation Guide

Part number: 5998-1345 Software version: iMC PLAT 5.1 (E0202) Document version: 5PW104-20111222

Legal and notice information © Copyright 2010-2011 Hewlett-Packard Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FITNESS FOR FOR A PARTICULAR PARTICULAR PURPOSE. PURPOSE. Hewlett-Packard shall not be liable for errors errors contained contained herein or for incidental or consequential damages in connection with the furnishing, furnishing, performance, or use of this material. 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.

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 (if 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 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, 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 http://www.hp.com/suppor .com/support/downloads t/downloads HP software depot http://www.software.hp.com

1

Conventions This section 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 .

Convention

Description

Symbols

CAUTION NOTE

An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that contains additional or supplementary information.

Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device.

2

Contents Overview ······································································································································································ 1 Introduction to iMC components ····································································································································· 1 Introduction to iMC editions ····························· ····························· ······························ ······························ ······················· 1

Installation preparations ·············································································································································· 3 Server requirements ·························································································································································· 3 Hardware requirements ··························· ······························ ····························· ······························ ······················· 3 Software requirements ····························· ····························· ······························ ······························ ······················· 5 Client requirements ··························································································································································· 7 Guidelines for installing on a virtual machine ············································· ······························ ····························· ······· 7 Preparation for installation and deployment ···························· ······························ ····························· ··························· 7 System time setting ···························· ······························ ······························ ······························ ··································· ··· 8 Checking the system time ········································································································································ 8 Setting the time zone ·························· ······························ ······························ ······························ ···························· 8

Installation and deployment requirements ·················································································································· 9 Prerequisites for deploying iMC in distributed mode ····························· ······························ ······························ ··········· 9 Prerequisites for upgrading iMC ·································································································································· 10 Obtaining iMC installation and deployment methods ···························· ····························· ······························ ········ 11

Installation and deployment of the iMC Platform····································································································· 12 Installing the iMC Platform ············································································································································ 13 Typical installation ················································································································································· 13 Custom installation ················································································································································ 16 Deploying the iMC Platform ····························· ····························· ······························ ······························ ···················· 21 Deploying iMC in centralized mode (user-supplied database) ·························· ····························· ················· 21 Deploying iMC in centralized mode (embedded database) ····························· ······························ ················· 25 Deploying a single iMC component ··················································································································· 26 Plug-in installation ·························································································································································· 26 Installing DHCP plug-ins········································································································································ 26 Installing VNM agent plug-ins ··························· ······························ ······························ ······························ ········· 28 Installing Android clients ··············································································································································· 29

Installation and deployment of iMC service components························································································ 31 Installing iMC NTA ························································································································································ 33 Deploying iMC NTA ······················································································································································ 38 Centralized deployment ······································································································································· 38 Distributed deployment ········································································································································· 39

Upgrading iMC ··························································································································································46 Backing up iMC ····························································································································································· 46 Upgrading iMC ······························································································································································ 47 Restoring iMC (optional) ··············································································································································· 52

Logging in to iMC ······················································································································································54 Removing iMC····························································································································································55 Removing an iMC component ······································································································································ 55 Removing all iMC components at one time ················································································································ 56 Removing iMC deployed in centralized mode ······················································· ······························ ············· 56 Removing iMC deployed in distributed mode ··························· ······························ ······························ ············· 56

i

Registering iMC and incremental node licenses······································································································58 Registering iMC ······························································································································································ 58 Registering first license·········································································································································· 58 Registering incremental node licenses ················································································································ 63 Activating iMC ····························· ······························ ····························· ······························ ···································· ····· 64 iMC V5.0 license upgrade process ·························· ······························ ······························ ······························ ········· 65 iMC V5.1 license upgrade process ·························· ······························ ······························ ······························ ········· 66

Security settings ··························································································································································67 Anti-virus software ····························· ······························ ······························ ····························· ···································· 67 Port settings ····································································································································································· 67

Database backup and restoration ····························································································································69 Database backup and restoration on the local server cluster ·························· ······························ ··························· 70 Database backup and restoration in centralized mode ··························· ······························ ··························· 70 Database backup and restoration in distributed mode ···························· ······························ ··························· 72 Database backup and restoration to the backup server cluster ····························· ····························· ······················ 73 Database backup and restoration to the backup server cluster (centralized mode) ···························· ·········· 73 Database backup and restoration to the backup server cluster (distributed mode) ····························· ·········· 75 Database backup and restoration when a separate database server is used ······························ ·························· 77 Configuration guidelines ··············································································································································· 79

FAQ·············································································································································································80

ii

Overview HP Intelligent Management Center (iMC) runs on Windows or Linux. When running on Windows, iMC stores and manages data through SQL Server. When running on Linux, iMC stores and manages data through Oracle or MySQL. To ensure normal operation of iMC, you need to properly install the operating system, database and iMC software. HP recommends you to access the iMC system through IE 6.0 SP1 or higher, or through Firefox 3.6 or higher without installing the client software.

Introduction to iMC components iMC comprises the iMC Platform and service components. The iMC Platform, which is the required configuration, involves such common components as Resource Manager, NE Management, Alarm Management, Performance Management, VLAN Management, ACL Management, and Intelligent Configuration Center. Service components involve Network Traffic Analyzer (NTA), User Behavior Auditor (UBA), QoS Manager, Service Operation Manager, Applications Manager, User Access Manager (UAM), EAD Security Policy, CAMS Accounting Manager, IPsec VPN Manager, and MPLS VPN Manager. You can select service components as needed. The iMC Platform is the basis for implementing various services. Therefore, before installing service components, you need to install the iMC Platform.

Introduction to iMC editions Two editions of iMC are available: iMC Enterprise and Standard. Table 1 shows the differences between the editions. Table 1 Differences between the two iMC editions Item

Enterprise

Standard

Number of nodes

Extensible

Extensible

Hierarchical NM

Supported

Partially supported (Used as lower-level NMS only)

Operating system

Windows and Linux

Windows and Linux

Distributed deployment

Supported

Supported Supported.

Embedded database

Not supported.

For the installation description, see SQL Server 2008 R2 Installation and Configuration Guide.

1

NOTE: •

•

•

For the embedded database installation description, see SQL Server 2005 R2 Installation and Configuration Guide . For the database installation description on Windows, see SQL Server 2005 Installation and Configuration Guide , SQL Server 2008 Installation and Configuration Guide , and SQL Server 2008 R2 Installation and Configuration Guide , and MySQL 5.1 Installation and Configuration Guide (for windows) . For the database installation description on Linux, see Oracle 11g Installation and Configuration Guide and Oracle 11g R2 Installation and Configuration Guide, and MySQL 5.1 Installation and Configuration Guide (for Linux) .

2

Installation preparations Server requirements Hardware requirements Table 2 Server requirements in a 32-bit Windows operating system Management scale Nodes 0 to 200 200 to 500

System minimum requirements

Collected Online unit operators 0 to 5K

20

5K to 50K

10

0 to 10K

30

10K to 100K

10

CPU

Memory size

Java heap size

Storage required for installation

2 CPU or 1 CPU dual-core)

4G

512 MB

3 GB

1

4 CPU or 2 CPU (dual-core)

Storage required for operation 30 GB 60 GB 50 GB

6G

1G

3 GB

100 GB

Table 3 Server requirements in a 64-bit Windows operating system Management scale Nodes 0 to 200 200 to 1K

1K to 2K

2K to 5K

5K to 10K



20

5K to 50K

10

0 to 10K

30

10K to 100K

10

0 to 20K

30

20K to 200K

10

0 to 30K

40

30K to 300K

20

0 to 40K

50

40K to 400K

20

CPU

Memory size


4G

1

4 CPU or 2 CPU (dual-core) 8 CPU or 4 CPU (dual-core)

Java heap size


Storage required for operation 30 GB

1G

3 GB

60 GB 50 GB

8G

2G

3 GB

100 GB 60 GB

16 G

4G

4 GB

200 GB 80 GB


32 G

8G

5 GB

250 GB 100 GB


64 G

3

16 G

7 GB

300 GB

Table 4 Server requirements in a 32-bit Linux operating system Management scale Nodes 0 to 200 200 to 500



20

5K to 50K

10

0 to 10K

30

10K to 100K

10

1

CPU

2 CPU or 1 CPU (dual-core) 4 CPU or 2 CPU (dual-core)

Memory size

Java heap size

6G

512 MB


Storage required for operation 30 GB

3 GB

60 GB 50 GB

8G

1G

3 GB

100 GB

Table 5 Server requirements in a 64-bit Linux operating system Management scale Nodes 0 to 200 200 to 1K

1K to 2K

2K to 5K

5K to 10K



20

5K to 50K

10

0 to 10K

30

10K to 100K

10

0 to 20K

30

20K to 200K

10

0 to 30K

40

30K to 300K

20

0 to 40K

50

40K to 400K

20

Memory size

1

CPU

2 CPU or 1 CPU (dual-core) 4 CPU or 2 CPU (dual-core) 8 CPU or 4 CPU (dual-core) 16 CPU or 8 CPU (dual-core) 32 CPU or 16 CPU (dual-core)

4

Java heap size

Storage Storage required for required for installation operation 30 GB

8G

1G

3 GB

60 GB 50 GB

16 G

2G

3 GB

100 GB 60 GB

24 G

4G

3 GB

200 GB 80 GB

32 G

8G

5 GB

250 GB 100 GB

64 G

16 G

7 GB

300 GB

NOTE: •

•

•

CPU1: No less than 2.5 GHz in Table 2, Table 3, Table 4, and Table 5. Java heap size: Refers to the maximum memory size to be used by Java processes on the iMC Web Server. To improve the input/output (I/O) performance, follow these guidelines: {

{

{

{

If the number of collection units is from 100 K to 200 K, install two or more disks and a RAID card with a cache of 256 MB or more. If the number of collection units is from 200 K to 300 K, install two or more disks and a RAID card with a cache of 512 MB or more. If the number of collection units is from 300 K to 400 K, install four or more disks and a RAID card with a cache of 1 GB or more. HP recommends that you set the RAID level to 0. If you want to set RAID level 5 or 10, install proper number of parity disks.

The hardware requirements of iMC vary with the components and networking circumstances. For more information, see the release notes of each component.

Software requirements Table 6 lists the recommended software configuration to run iMC. Table 6 Software requirements Item

Requirement

Remarks

Windows Server 2003 (32bit)

Service Pack 2 is required.


Service Pack 2 (64 bit) and KB942288 are required.

Windows Server 2003 R2 (32bit)



Service Pack 2 (64 bit) and KB942288 are required.




Service Pack 2 (64 bit) is required. This operating system does not support the embedded database shipped with iMC.





Windows

Operating system

Service Pack 3 is required for SQL Server 20 05. Service Pack 3 is required for SQL Server 20 08.

SQL Server 2005

Service Pack 1 is required for SQL Server 20 08 R2.

SQL Server 2008 Database

For both Standard and Professional editions.

SQL Server 2008 R2

Make sure the latest database service packs are installed.

SQL Server 2008 R2 Express

Only for Standard edition.

MySQL 5.1

None

Linux

5

Item

Operating system

Database

Requirement

Remarks

Red Hat Enterprise Linux Server 5 (32bit)

None

Red Hat Enterprise Linux Server 5 (64bit)

None

Red Hat Enterprise Linux Server 5.5 (32bit)

None


None


None

Oracle 11g

None

Oracle 11g Release 2

None

MySQL 5.1

None

HP recommends that you use a 64-bit operating system for the server when deploying iMC Platform and service components simultaneously. If the server runs a 32-bit operating system, you must manually modify the assignable memory size of the Java after deployment, with the following method: 1.

Use the editor (such as WordPad in Windows or vi in Linux) to run the \client\bin\startup.bat script or the startup.sh script on Linux, 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 ....

2.

Save the file and restart the jserver process. If the jserver process cannot start up, decrease the above values until it can start up. If the OutofMemory Error occurs after the jserver process starts up, use a 64-bit operating system.

NOTE: You can install the database on a separate database server and save the iMC data on t he database server. To install the database on a separate database server, follow these guidelines: For SQL Server: •

•

On the iMC server, install an SQL Server client with the same version as the database. Create a data file folder on the database server, and input the local path when deploying the iMC components.

For Oracle: •

•

On the iMC server, install an Oracle client with the same version as the database. On the iMC server, create a name for network service where the host name is the database server IP address.

6

Client requirements Table 7 Client requirements OS

Hardware

Web browser

•

CPU: Speed ≥ 2.0G Hz Memory: Size ≥ 1G Hard Disk: Size ≥ 20G Windows

CD-ROM: Speed ≥ 48X Network Adapter: Speed ≥ 100M

Web browser requirements

IE 6.0 SP1 or higher

•

Firefox 3.6 or higher

•

•

•

Audio Card is needed

•

Turn off the Pop-up Blocker in Internet Explorer; Enable the Cookies in Internet Explorer; Add the iMC site to the trusted sites; Make sure the Screen Resolution is 1024x768 or higher; IE 8.0 or higher is recommended. Firefox 3.6.3 or higher is recommended.

Guidelines for installing on a virtual machine iMC can be installed on a VMware virtual machine. Before the installation, you must set the path where the virtual machine is located and hardware information including the types and number of CPUs, the number, models, and MAC addresses of network adapters, and the number and space of disk drives. After you install iMC, do not change the previous configuration. Otherwise, iMC cannot work normally.

Preparation for installation and deployment For instructions of database installation, see related database documents. Before installation, make sure that all the requirements listed in Table 8 are met. Table 8 Installation environment Item

Requirements

Hardware

Meets the specifications of CPU, memory, and hard disk in the contract.

Software

Make sure that the type and version of the operating system, database version, and iMC version meet the installation requirements. The server is restarted after database installation.

Database installation check

SQL Server patch check

Before installing iMC, install the database first. During t he iMC installation procedure, the corresponding database connections are checked. On Linux, a 32-bit operating system must use the 32-bit Oracle database and a 64-bit operating system must use the 64-bit Oracle database. Service Pack 3 is required for SQL Server 2005. Service Pack 1 is required for SQL Server 2008.

Auto startup of SQL Server service

Select Control Panel > Administrative Tools > Services and make sure the Startup Type item of the MSSQLSERVER is set to Automatic.

Auto startup of SQL Server Agent

Select Control Panel > Administrative Tools > Services and make sure the Startup Type item of the SQL SERVERAGENT is set to Automatic.

7

Item

Requirements

Uninstallation of iMC software

A thorough uninstallation is required if the iMC software has been installed in the system previously. For how to remove the iMC, see Removing iMC. Reboot the system after the iMC is uninstalled. To thoroughly remove the iMC: For Windows, after you remove the iMC, locate and delete the iMC-Reserved folder in the WINDOWS folder of the system disk. For Linux, locate and delete the iMC-Reserved folder in the /etc/ directory. •

•

Firewall settings check

To deploy iMC in distributed mode, you must open the listening port on the server installed with the database. The default listening port number of the SQL server database is 1433, the default listening port number of the Oracle database is 1521, and the default listening port number of the MySQL database is 3306.

Hardware

Meets the specifications of CPU, memory, and hard disk in the contract.

CAUTION: •

•

To ensure proper installation and operation of iMC, do not install iMC with other network management products on the same server. Use the same operating system bit count on the master and slave servers when you deploy iMC in distributed mode.

System time setting Checking the system time Before installing iMC, check that the system time, date and time zone settings on the server are correct. If not, you need to adjust the settings. After iMC is started, do not modify the system time of the server; otherwise, the following or other unpredictable problems may occur. If you modify the system time to a future time that differs greatly from the current time, the system takes a long time to process a large amount of data exceeding the maximum time that the data can be saved in the database, which affects the current data sampling speed and results in delay. After the processing of such data is complete, the delay is gradually recovered. If you modify the system time to a past time, data with overlapping time may occur, and data processing may become abnormal. After the overlapping time is past, data processing becomes normal again. If you encounter other problems caused by system time modification, for a master server, HP recommends that you restart all master and slave servers; for a slave server, you need to restart only the server. When deploying iMC in distributed mode, make sure that the time zone settings of all servers are the same. In addition, HP recommends using the Network Time Protocol (NTP) to synchronize the time on all servers.

Setting the time zone Before installing iMC in the Windows Server 2003 operating system, deselect automatically adjust clock daylight saving changes when you set the time zone in the Date & Time window.

8

Installation and deployment requirements To improve the server performance, iMC uses the Install and Deploy model. iMC installation is to copy the iMC installation file to the master server. iMC deployment is to decompress the installation package and create a database script on the master server or slave servers as needed. The components of iMC are operational only after they are deployed. You can deploy iMC in two ways: Centralized deployment: All iMC components are deployed to the same server. Distributed deployment: The basic iMC components are deployed to the master server, and other iMC components are deployed to the master server or slave servers. NOTE: •

•

The master server is the management center of iMC. It interacts with slave servers to implement network management. A slave server is responsible for specific management tasks, for example, tasks performed by Performance Management and by Intelligent Configuration Center (iCC).

In distributed deployment, the master server provides centralized web services. You can simply access the master server for performing all management functions. iMC supports typical installation and custom installation: Typical installation allows you to quickly install and deploy all platform components on the current server. Before performing the typical installation, you must first configure installation parameters, such as database connectivity, installation location, and web service port numbers. The typical installation is available only for local database deployment. Custom installation allows you to select certain platform components to install and deploy on the master iMC server and specify a separate database server. This installation method is available for both local and separate database deployment.

Prerequisites for deploying iMC in distributed mode Operating system and database of the master and slave servers Make sure that all slave servers and the master server use the same operating system. On Windows, the SQL Server and MySQL database can be used. While on Linux, the Oracle and MySQL database can be used. Components that need to be deployed on the master server The Resource Manager, Data Analysis Manager, NE Manager, Report Manager, and Security Control Center components of iMC must be deployed on the master server. For more information about the deployment of service components, see “Installation and deployment of iMC service components.” The components that you want to deploy to the slave servers must have been installed on the master server. On the master server, the resource management component is deployed and the processes of the deployed components are started. 9

If the iMC intelligent deployment monitoring agent has been installed on the slave servers, uninstall it before deploying iMC components in distributed mode. To install iMC on Linux by using the Oracle database, you must configure the network service name. Take the following application scenario for example: If Server A (master iMC server), and Servers B and C (subordinate iMC servers) use local databases and have been configured with network service names TNSNAME_A for connecting to Server A, TNSNAME_B for connecting to Server B, and TNSNAME_C for connecting to Server C, respectively, you must configure the other two unavailable network service names for each server, for example, TNSNAME_B and TNSNAME_C for Server A. For more information about network service name configuration, see Oracle 11g Installation and Configuration Guide or Oracle 11g R2 Installation and Configuration Guide . Java Runtime Environment 6.0 has been installed on the slave servers. Use either of the following approaches to install JRE 6.0: Approach 1: Download the program from http://www.oracle.com/technetwork/java/index.htmland install it. Approach 2: Run the JRE 6.0 setup in the iMC package. To install JRE 6.0, perform the following steps: a. On the slave server, launch the web browser and enter http://192.168.4.44:8080/imc

(192.168.4.44 is the IP address of the master server, and 8080 is the HTTP port number) in the address bar. b. On the login page, type the username and password. c. Click Login to enter the Home tab. d. Select the System tab and click Deploy Components. e. Click the If fail to start Remote Installation Wizard, download and install JRE. link. f.

In the popup jre.exe file download window, click Save before running the file or directly click Run.

CAUTION: During the distributed deployment process, do not i nstall, deploy, undeploy, or update the iMC software on the master and slave iMC servers simultaneously. Otherwise, faults may occur. NOTE: •

•

The username and password of the super user for the system are both admin by default. To use Firefox for accessing iMC on Linux, install JRE 6.0 or JDK first. For the detailed operation procedure, see “FAQ.”

Prerequisites for upgrading iMC After you install the iMC Platform and components, if you want to upgrade the iMC Platform, first make the following preparations: The components require iMC V5.0 or a higher version. For the compatibility matrix, see the readme file. For data safety, HP recommends that you back up the database by using the Intelligent Monitoring Agent Environment tab, and copy the entire iMC installation path, it is not done during upgrade. For how to back up the iMC database, see “ Database backup and restoration.” 10

Download the upgrade packages for all listed components before you upgrade the iMC Platform. CAUTION: •

•

To upgrade the iMC Platform without preparing upgrade packages for some components, you must remove these components and then upgrade the iMC Platform. Otherwise, the upgraded iMC Platform is not available. Removing a component will cause loss of the corresponding data. To upgrade iMC from version 3.x to version 5.x, re-log in to the registration website and obtain a new activation file.

Obtaining iMC installation and deployment methods You can obtain the iMC installation and deployment methods through reading this document. Installing iMC on Windows and Linux is similar. The following illustrates installing the iMC Platform and service components on Windows Server 2003. The iMC software is available on the HP website.

11

Installation and deployment of the iMC Platform This chapter describes the installation and recommended deployment schemes of the iMC Platform. When you use only the iMC Platform to manage your network, HP recommends that you deploy the iMC components to the same server, which means you use the centralized deployment mode. To manage a large number of devices and use iMC Enterprise edition, HP recommends you to use a user-supplied database. For more information, see “ Software requirements.” To manage a small number of devices and use iMC Standard edition, use either the embedded iMC database or a user-supplied database. NOTE: •

•

The iMC Standard edition supports both embedded database and user-supplied database. HP recommends that you use a user-supplied database. When using the iMC-embedded database, make sure that no SQL Server database is installed on the master or slave servers.

To deploy the iMC components to the slave servers, see Table 9. Table 9 iMC subcomponents and their deployment requirements Component

iMC Platform

Subcomponents

Optional server

Resource Manager

Master server

Alarm Manager

Master and slave servers

Data Analysis Manager

Master server

Data Analyzer


Guest Access Manager


Performance Manager


Network Asset Management


ACL Manager


Intelligent Configuration Center


NE Manager

Master server

Report Manager

Master server

Security Control Center

Master server

Syslog Manager


VLAN Manager

Master server

User Selfservice Manager


Virtual Network Manager

Master server

12

Installing the iMC Platform Log in to Windows Server 2003 with the administrator account, decompress the installation file, and then run the install\install.bat script in the downloaded installation package to install iMC. Then, a window as shown in Figure 1 appears, asking you to select a proper country/region, language, and installation type. CAUTION: •

•

To properly install iMC in Windows Server 2003 or Windows Server 2003 R2, you must log in as an administrator and then install iMC. To properly install iMC in Windows Server 2008 or Windows Server 2008 R2, you must first right-click the install.bat script and select Run as Administrator from the shortcut menu, or modify the User Account Control Settings and then restart the server. After installing iMC, you can restore the related settings as needed. Modify the User Account Control Settings as follows: click Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center , and the User Account Control Settings window appears. In the window, set the Choose when to be notified about changes to your computer to Never notify.

NOTE: To install iMC on Linux, you must start the iMC installation wizard by running theinstall.sh script in the downloaded installation package as a root user. Figure 1 Select Locale

Select the country or region where you are located, language, and typical or custom installation type according to the iMC deployment. The following sections describe typical installation and custom installation, respectively.

Typical installation On the page shown in Figure 1, select Typical and click OK . The window for checking installation parameters appears.

13

Figure 2 Checking installation parameters

Configure the installation parameters to check before you can install and deploy iMC components: 1.

Select the database type and instance name, enter the SQL server super user name ( sa by default) and password, and enter the listening port (1433 by default).

NOTE: When you install iMC on Linux, select a network service name or click the icon to add a network service name. If a local database is used, you must configure a network service name for connecting to the local database address. If a separate database is used, you must configure a network service name for connecting to the database server address. For more information about the network service name configuration, see Oracle 11g Installation and Configuration Guide or Oracle 11g R2 Installation and Configuration Guide . 2.

Use the default installation location and database file location, or custom the installation location and database file location as needed.

3.

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

4.

Click OK .

The system starts to check the installation environment. If the installation environment fails the check, modify parameters according to the check results. Click Continue if you see a message reminding you of less than 2 GB free space for the installation environment. When the check is passed, the system directly installs and deploys all platform components. After the installation and deployment is complete, the Batch deploy succeeded window appears.

14

Figure 3 Batch deploy succeeded

To start iMC immediately, select Start iMC Server now and click OK . The intelligent deployment monitoring agent window appears, as shown in Figure 4. To start iMC later, click OK . Then you can click Start iMC on the Monitor tab of the intelligent deployment monitoring agent any time you want to start iMC. Figure 4 Intelligent deployment monitoring agent

Click the Deploy tab to view the deployed components. Click the Process tab to view the running process information. NOTE: The Deploy tab shown in Figure 4 contains two data analyzer components, one in Deployed state and the other in Undeployed state, because the component can be deployed on multiple servers (one for each server). Click the Monitor tab to view the iMC startup information, as shown in Figure 5. If 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 startsif you want iMC to automatically start at the system startup.

15

Figure 5 Intelligent deployment monitoring agent

To install new components, click Install in Figure 5, or right-click the Intelligent Deployment Monitoring Agent icon on the Windows system tray and select Install from the shortcut menu. For more information, see “Installation and deployment of iMC service components.”

Custom installation In Figure 1, Select Custom and click OK to enter the page for checking database connectivity. Figure 6 Checking Database Connectivity

You must pass the database authentication before performing the installation and deployment. Therefore, you must select the database type, and the instance name created in the SQL Server installation, and then enter the superuser name (sa by default), password, and listening port number (1433 by default).

16

NOTE: When you install iMC on Linux that uses Oracle database, select a network service name or click the icon to add a network service name. If a local database is used, you must configure a network service name for connecting to the local database address. If a separate database is used, you must configure a network service name for connecting to the database server address. For more information about the network service name configuration, see Oracle 11g Installation and Configuration Guide or Oracle 11 R2 Installation and Configuration Guide . If you select local host for the database location, you must enter the superuser name and password. If you select other server , specify the server IP address and enter the superuser name and password for the specified database server. After the configuration, click OK . Then the system starts to check the database connectivity. After the installation environment check, the HP iMC Installation Wizard appears. If the free hard disk space is less than 1 GB, you can still click Continue to install iMC. If the installation environment cannot meet the requirements, you cannot install iMC. You can adjust the installation environment according to the check results. After passing the installation environments check, the Welcome to HP iMC Installation Wizard window appears, as shown in Figure 7. NOTE: When you use an embedded database, after you select the Country/Region and Language, the system directly checks the installation environments. When you pass the installation environments check, you directly enter the HP iMC Installation Wizard, as shown in Figure 7. Figure 7 Welcome to HP iMC Installation Wizard

Click Next. The Agreement window appears, as shown in Figure 8.

17

Figure 8 Agreement

Read the license agreement and third party license, select Accept, and then click Next. The Choose Target Folder window appears, as shown in Figure 9. Figure 9 Choose Target Folder

The Choose Target Folder window displays the components. Select the components you want to install. By default, iMC is installed in C:\Program Files\iMC (or in /opt/iMC on Linux). You can either type a path or click Browse to select a path to install it in another folder. CAUTION: •

In the partition where you want to install the iMC software, at least 5 GB free space must be available.

•

You must choose a local installation path.

•

Linux does not support the iMC installation in a symlink path.

In the Choose Target Folder window, you can also view information about the components that you want to install. These components include Resource Manager, NE Manager, Alarm Manager, Performance Manager, and so on. 18

After selecting an iMC installation path, click Next. The Deployment and Upgrade Options window appears, as shown in Figure 10. Figure 10 Deployment and Upgrade Options

You can select an option according to the option descriptions in the window. In this example, select Deploy or upgrade later , and click Next. The Installation Summary window appears, as shown in Figure 11. Figure 11 Installation Summary

The Installation Summary window provides the following information: The name, description, version, and disk space required of each component The installation location of each component The total disk space The free disk space of the partition where iMC is to be installed Click Install. The Installing window appears, as shown in Figure 12.

19

Figure 12 Installing common components

The wizard shows the process of component installation. The installation will take a while. After the installation is finished, the Installation Completed window appears, as shown in Figure 13. Figure 13 Installation Completed

In the Installation Completed window, you have the following options: If you install only the iMC Platform without any service component, select the Open deployment monitoring agent box and then click Finish to start deployment. If you continue to install other service components, decompress the installation file, select the Install other iMC Components box and then click Finish to enter the Choose folder dialog box, as shown in Figure 22 in “Installation and Deployment of iMC Service Components.” You can directly click Finish to close the window without selecting any of the two boxes. Then on your PC, select 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 deployment monitoring agent and perform relevant operations.

20

NOTE: To open the Intelligent Deployment Monitoring Agent on Linux, you must run the dma.sh script in /deploy of the iMC installation path.

Deploying the iMC Platform Deploying iMC in centralized mode (user-supplied database) After installation, in the window as shown in Figure 13, select Open deployment monitoring agent and then click Finish. Then the system automatically starts the intelligent deployment monitoring agent. For the first deployment, a Batch deploy window appears at the same time, as shown in Figure 14. Figure 14 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 theDeploy tab, select Batch Deploy from the right-click menu of the target components to start batch deployment. In the Batch deploy window, the components to be deployed by default include Resource Manager, Data Analysis Manager, Data Analyzer, Alarm Manager, Intelligent Configuration Center, NE Manager, Performance Manager, Report Manager, and Security Control Center. The rest are the optional components, which include User Selfservice Manager, Guest Access Manager, Network Asset Management, ACL Manager, Syslog Manager, VLAN Manager and Virtual Network Manager. You can also select the components to be deployed as needed (Resource Manager is required). Then click OK to enter the Database Configuration Info window, as shown in Figure 15.

21

Figure 15 Database Configuration Info

Enter the password for the superuser, which was used for installing iMC database, and then select the location for saving database files. By default, database files are stored in C:\Program Files\imcdata. If you do not want to use the default location, click Browse and select one. CAUTION: Save data files to a writable hard drive. Select a path to save the data files and click Next. The Configure Web Service Port window appears, as shown in Figure 16. Figure 16 Configure Web Service Port

The default port for HTTP access is 8080, and that for HTTPS access is 8443. You can change these port numbers. NOTE: Make sure that the Web service ports that you set here are not being used by another service. 22

After configuring the Web service port, click Deploy. The Deploying window appears, as shown in Figure 17. Figure 17 Deploying iMC components

After the deployment, the Batch deploy succeeded window appears, as shown in Figure 18. Figure 18 Batch deploy succeeded

In the Batch deploy succeeded window, you can select View readme file, Start iMC Server now, or both. In this example, select Start iMC Server now and click OK . The system will immediately start the iMC service and pop up the Intelligent Deployment Monitoring Agent window, as shown in Figure 19. On this window, select the Deploy tab, and you can view information about the component deployment.

23

Figure 19 Information about component deployment

NOTE: The Data Analyzer can be deployed to multiple servers (once for each server). Therefore, after this component is deployed, another Data Analyzer with status Undeployed appears in the component list. Some iMC components depend on others. When deploying such components, be sure to consider the dependencies between components. In the Deploy tab, select Show Dependencies from the right-click menu of a component to view the components that the selected component depends on. If the component does not depend on any components, Show Dependencies is grayed out. After the deployment is finished, follow these steps to start the processes of iMC: 1.

In the Intelligent Deployment Monitoring Agent window, select the Monitor tab, as shown in Figure 20.

2.

Click Start iMC.

You can also select the Automatically start the services when the OS starts box to start iMC with the operating system.

24

Figure 20 Intelligent Deployment Monitoring Agent

To view the running information of each process, select the Process tab to enter the process management window.

Deploying iMC in centralized mode (embedded database) Deploying iMC with an embedded database in centralized mode is applicable to small-sized networks because it can only manage a small number of devices. NOTE: The SQL Server 2008 R2 Express database is embedded in iMC Standard edition. For how to install the SQL Server 2008 R2 Express database, see the SQL Server 2008 R2 Installation and Configuration Guide . Deploying the iMC Platform with an embedded database in centralized mode is similar to that with a user-supplied database. However, when you deploy the iMC Platform with an embedded database in centralized mode: You can select the components to be deployed from the Batch deploy window, and click OK to enter the Database Configuration Info window, as shown in Figure 21.

25

Figure 21 Database Configuration Info

Select Install embedded database. Otherwise, you cannot deploy the components. Select the location for saving database files. By default, database files are stored in C:\Program Files\imcdata. If you do not want to use the default location, click Browse and select one. Select a path to save the data files and click Next. The Configure Web Service Port window appears, as shown in Figure 16. The subsequent deployment procedure is the same as “ Deploying iMC in centralized mode (user-supplied database).”

Deploying a single iMC component To deploy a single iMC component, use either of the following methods in the window as shown in Figure 19. Select Deploy the Component from the right-click menu of the target component. Select the target components, and select Batch deploy from the right-click menu. The Batch deploy dialog box appears. Select the components, and click OK . The detailed deployment procedure for a single component is similar to the batch deployment.

Plug-in installation To support some iMC functions, you must install proper plug-ins.

Installing DHCP plug-ins A DHCP server installed with a DHCP plug-in allows iMC to obtain the names of terminals, such as servers, PCs, and printers, from the DHCP server. To accomplish this, make sure that: 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. 26

This section describes how to install DHCP plug-ins on MS DHCP and Linux DHCP servers respectively.

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.

Enter the \server\conf\ directory in the iMC installation path, use the wordpad to open the file qvdm.conf, and add the following line to the file: l 2t opoPCN opoPCNameDhcpSw eDhcpSwi t ch=1

Save and exit the file, and restart the iMC. 2.

Install the iMC DHCP plug-in on the MS DHCP Server.

The DHCP plug-in installer dhcp-plug-windows.zipis dhcp-plug-windows.zip is saved in the \windows\tools\directory \windows\tools\ directory of the iMC installer. Copy the plug-in installer to the MS DHCP Server. Decompress the installer, and use the wordpad to open the imf.cfg file in the dhcp-plug-windows folder \server\imf\server\conf\ directory. Modify the IMGAddress into the iMC server IP address and IMGPort (which is 8800 by default) to the IMG port number. Save and exit the file. 3.

Run the install.bat script in the dhcp-plug-windows folder. After the installation, a new server iMC DHCP Plug is added to the system services.

4.

Start the iMC DHCP plug service. Start, and select Administrative select Administrative Tools > Component Services to open the Component a. Click Start, Services window. b. Select Services (Local) from the navigation tree, right-click the iMC DHCP Plug service on the

Services (Local) list, and select Start to start the iMC DHCP plug service. 5.

Complete the DHCP plug-in installation.

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

Linux DHCP server 1.

Modify the file qvdm.conf, so that the iMC supports getting the terminal DNS name or terminal name through the Linux DHCP server.

Use the VI editor to open the qvdm.conf file in the /server/conf/ directory, vi qvdm qvdm. conf

Add the follow following ing line to the file: l 2t opoPCN opoPCNameDhcpSw eDhcpSwi t ch=1

Save and exit the file, and restart the iMC. 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. Copy the plug-in installer to the Linux DHCP Server, decompress the installer, and use the VI editor to open the imf.cfg file in the dhcp-plug-linux folder /server/imf/server/conf/ directory: 27

vi i mf . c f g

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 the iMC. Save and exit the file. 3.

Check whether the path of the DHCP server IP allocation information file dhcpd.leases is correct.

Enter the /var/lib/dhcp directory of the Linux operating operati ng system, and check whether the dhcpd.leases file exists. If the file does not exit, enter the /server/conf directory of the dhcp-plug-linux dhcp-plug -linux file, 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. DhcpPl hcpPl ugI ugI pAl pAl l ocPat ocPat h=/ dhcpd dhcpd.. l eases eases

Save and exit the file. 4.

Execute the install.sh script.

Execute the install.sh script of the dhcp-plug-linux file. After the installation is complete, the dhcp-plug service is added to the system services, and has been automatically started. 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. The DHCP plug-in installation is complete. NOTE: To uninstall a DHCP plug-in, run the uninstall.sh script in the dhcp-plug-linux 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 VNM agent plug-ins If Microsoft Hyper-V servers exist in the network, you must install VNM agent plug-ins plu g-ins for iMC to manage the Hyper-V servers. If the Microsoft Hyper-V servers are managed by Microsoft Virtual Machine Monitor (VMM) servers, install VNM agent plug-ins on all of the Microsoft VMM servers. If not, you can install instal l a VNM agent plug-in pl ug-in on one Windows server. server. A VNM agent plug-in pl ug-in can work for up to 50 Hyper-V servers. If more than 50 Hyper-V servers exist in the network, install more than one VNM Agent plug-ins. CAUTION: VNM agent plug-ins plug-ins can only be installed installed on Windows servers that can can access all Hyper-V Hyper-V servers. A Windows server can can be installed with only one VNM Agent plug-in. A VNM agent agent plug-in is dependent on NET Framew Framework ork 2.0, 2.0, NET NET Frame Framework work 2. 2.1, NET Frame Framewor workk 3.0, 3.0, and PowerShell 2.0. Before you install VNM agent plug-in, 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 Windows operating operating system systems, s, go to the Micros Microsoft oft official official website website to down download load and install them. 1.

The installation file vnm-plug-windows.zip vnm-plug-windows.zip of VNM agent plug-in is stored in tools folder of the iMC installation package. Decompress Decompress the file and copy the file to a directory of the server where the VNM agent plug-in is to be installed. installed. 28

NOTE: Do not delete the vnm-plug-window folder after the installation is complete because the folder is the service registration directory. 2.

Run Register.bat in the vnm-plug-windows folder. If 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 then start the installation process again.

3.

Use the wordpad program to open the imf.cfg file in the vnm-plug-windows\server\imf\server\conf vnm-plug-windows\server\imf\server \conf directory. Modify IMGAddress as the IP address of the master iMC server and IMGPort as the MBP port number (8800 by default). Save your settings and quit.

4.

Start the iMC VNM plug service. a. Click Start, Start, and select Administrative select Administrative Tools > Component Services to open the Component

Services window. b. Select Services (Local) from the navigation tree, right-click iMC VNM Agent on the Services

(Local) list, and select Start to start the VNM agent service. The VNM agent plug-in installation is complete. NOTE: To uninstall a VNM agent plug-in, run the file UnRegister.bat in the vnm-plug-windows the vnm-plug-windows directory.

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 device must meet meet the followin following g requiremen requirements ts before before it can can access access iMC: The device is installed with the operating system of Android 2.1 update1 or a later version. The screen resolution is i s HVGA(480*320) HVGA(480*320) or WVGA(800*480). The mobile device can communicate with the iMC server (through wireless connection, for example). Follow these steps to install an Android client: 1.

Access the website http://imc-addr:port/imc/noAuth/imc.apk http://imc-addr:port/imc/noAuth/imc.apkby by using the embedded browser of the mobile device to automatically download the client installation program. imc-addr is 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. If the message Programs from unknown sources are not allowed to install appears during installation, locate to Settings > Applications and select Unknown source. source.

Follow these steps to log in to iMC: 1.

Open the client program.

2.

Enter the iMC server address, login name, and password.

29

http://imc-addr:port, where imc-addr is imc-addr is the IP address The iMC server address is in the format of http://imc-addr:port, 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). If HTTPS does not use the default port number when iMC was deployed for the first time, enter the specified port number. The login name must be an existing login name, which has the privilege to access iMC Platform > Resource Manager > Mobile Client Access in the iMC. 3.

Select Save password or Auto or Auto Login as needed. If you select Save password, password, you do not need to enter the password for the next logins. If you select Auto Login, 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 information about about faulty device devicess and interfaces interfaces,, and query specific specific device devices. s. View device device alarms. alarms. Inform real-time alarms. Test device reachability by using ping or traceroute. View View custom custom views views and device device views. views. Use an Android browser to access iMC to perform configuration and management operations. Play iMC videos. NOTE: If RADIUS authentication or LDAP authentication is used or if 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 the iMC.

30

Installation and deployment of iMC service components This chapter describes the recommended iMC Platform plus service ser vice components deployment mode, and how to install and deploy the service components. iMC common service components include Network Traffic Analyzer, User Behavior Auditor, QoS Manager, Service Operation Manager, Applications Manager, User Access Manager (UAM), EAD Security Policy, Policy, CAMS Accounting Manager, IPsec VPN Manager, Manager, and MPLS VPN Manager. Table 10 iMC subcomponents and their deployment requirements Component

Subcomponents

Optional server

Remarks

Network Traffic Analyzer

Master server

—

Network Traffic Analyzer Server


—

Network Behavior Analyzer

Master server

—

Network Behavior Analyzer Server


—

User Behavior Auditor

Master server

—

User Behavior Auditor Server


—

Network Behavior Analyzer

Master server

—

Network Behavior Analyzer Server


—

QoS Management

Master server

—

Service Health Management


—

NQA Collector Management


—

CMDB Management


—

Service Desk


—

Applications Manager

Applications Manager Manager


—

CAMS Accounting Manager

CAMS Accounting Manager


Deployed on the same server as the UAM component.

EoC Manager

EoC Manager


—

EPON Manager

EPON Manager

Master server

—

Network Traffic Analyzer

User Behavior Auditor

QoS Manager Service Health Manager

Service Operation Manager

31

Component

Subcomponents

Optional server

Remarks

Wireless Service Manager

Wireless Service Manager


—

Voice Service Manager

Voice Service Manager


—

IPsec VPN Manager

IPsec VPN Manager


—

MPLS VPN Management


—

MPLS TE management


—

L2VPN Management


—

MPLS VPN Manager

You must first deploy the data analyzer component. Set the database password (defaults to iMC5_uamead) and UAM Server’s IP Address, which is the IP address of the network adapter providing services externally of the server where UAM is deployed.

User Access Management


Portal Web Server and Portal Proxy


—


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.


Set Policy Server’s IP Address, which is the IP address of the network adapter providing services externally of the server where the policy server component is deployed.


Set Policy Proxy Server’s IP Address, which is the IP address of the network adapter providing services externally of the server where the policy proxy server component is deployed.

Portal Server User Access Manager

Policy Server

Policy Proxy Server

32

Component

Subcomponents

Optional server

User SelfService


Set User SelfService’s IP Address, which is the IP address of the network adapter providing services externally of the server where the user selfservice component is deployed.

Security Policy Configuration


—


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.

iNode Dissolvable Client


—

Desktop Asset Manager

EAD Security Policy

iNode Dissolvable Client

Remarks

The installation and deployment processes for the common service components are similar. This chapter takes the installation of NTA as an example.

Installing iMC NTA NOTE: Before installing service components, you need to install t he iMC Platform. For the installation steps, see “Installing the iMC Platform.” In the Installation Completed window as shown in Figure 13 in "Installation and Deployment of the iMC Platform", select the Install other iMC Components box and then click Finish to enter the Choose folder dialog box, as shown in Figure 22. Figure 22 Choose folder

33

NOTE: You can also install a new component with either of the following approaches: •

•

Select Start > All Programs > HP Intelligent Management Center > HP Deployment Monitoring Agent and click Install in the Monitor tab to begin installation. In the system tray, right-click the Intelligent Deployment Monitoring Agent icon and select Install from the popup menu to install a new component.

Then, in the Choose folder window, click Browse and select the install\components folder in the iMC NTA downloaded installation package. Then, click OK . A window as shown in Figure 23 appears to guide you through the iMC installation. Figure 23 Welcome to HP iMC Installation Wizard

Click Next. The Agreement window appears, as shown in Figure 24. Figure 24 Agreement

Read the license agreement and third party license, select Accept, and then click Next. The Choose Target Folder window appears, as shown in Figure 25. 34

Figure 25 Choose Target Folder

Some iMC components depend on other components to function. If the latter are not installed, the Description of a dependent component to be installed in the Choose Target Folder window may be Do Not Install (The dependence has not been installed. Right-click to view dependency information). In this case, you can view which components that this component depends on by selecting Show Dependent Influence from the right-click menu in the component list. The Choose Target Folder window displays information about the NTA. The system specifies the installation location of the NTA as the installation location of the iMC Platform by default. After confirmation, click Next. The Deployment and Upgrade Options window appears, as shown in Figure 26. Figure 26 Deployment and Upgrade Options

You can select an option as needed. In this example, Deploy or upgrade later is selected. Click Next. The Installation Summary window appears, as shown in Figure 27.

35

Figure 27 Installation Summary

After confirming the related installation information, click Install. The Installing window appears, as shown in Figure 28. Figure 28 Installing

The wizard is installing the component. The installation will take a while. After the installation is finished, the Installation Completed window appears, as shown in Figure 29.

36

Figure 29 Installation Completed

This chapter describes the installation of the NTA only. Select Open deployment monitoring agent in the Installation Completed window and click Finish. NOTE: To install other iMC common components, select Install other iMC Components in the Installation Completed window and click Finish to begin the installation. The installation procedure is similar to that of NTA. Besides the previous installation methods, you can also start a new component installation wizard with either of the following approaches: Approach 1: After installing and deploying iMC, select 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 intelligent deployment monitoring agent, and click Install in the Monitor tab to begin installation. CAUTION: •

•

To normally install iMC in Windows Server 2008 or Windows Server 200 8 R2, you must first modify the User Account Control Settings. After installing iMC, you can restore the related settings as needed. To modify the User Account Control Settings, select Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center, and the User Account Control Settings window appears. In the window, set the Choose when to be notified about changes to your computer to Never notify.

Modify the User Account Control Settings as follows: click Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center , and the User Account Control Settings window appears. In the window, set the Choose when to be notified about changes to your computer to Never notify. Approach 2: In the system tray, right-click the Intelligent Deployment Monitoring Agent icon and select Install from the popup menu to install a new component. 37

The detailed installation procedure is the same as the previously described.

Deploying iMC NTA HP recommends you to deploy NTA as follows: deploy the Network Traffic Analyzer component and the Network Behavior Analyzer component to the master server; deploy the Network Traffic Analyzer Server component and the Network Behavior Analyzer Server component to the slave server. To deploy the iMC database, use either of the following two ways: Database not separated: Each component uses its own database on the server where the component is deployed. Separate database. Use either of the following ways: 1) All components use the database on a separate database server. 2) A deployed component uses the database on another server. NOTE: •

•

•

•

Before deploying service components, deploy the basic iMC components and the co mponents on which the service components depend. For more information about the deployment procedure, see “Deploying iMC in centralized mode (user-supplied database).” See “Prerequisites for deploying iMC in distributed mode” before deploying service components in distributed mode. Before installing the SQL Server/Oracle database separately, you must install the SQL Server/Oracle database client on the server where iMC is deployed. The MySQL database only supports using a user-supplied database server when it is deployed as a separate database.

Centralized deployment This section describes how to deploy the iMC Network Traffic Analyzer and Network Behavior Analyzer to the master server. After installation, in the window as shown in Figure 29, select Open deployment monitoring agent and then click Finish. Then the system automatically starts the intelligent deployment monitoring agent. A Batch deploy window appears at the same time, as shown in Figure 30.

38

Figure 30 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 theDeploy tab, select Batch Deploy from the right-click menu of the target components to start batch deployment. In the Batch deploy window, you can select the components to deploy. In this example, select Network Traffic Analyzer and Network Behavior Analyzer. Then click OK to start deploying the components. After the deployment is complete, the Batch deploy result dialog box prompting Batch deploy succeeded appears. Click OK . On the intelligent deployment monitoring agent that appears, select the Monitor tab, and click Start iMC to start iMC. After iMC is normally started, you can perform deployments on the slave servers.

Distributed deployment The following sections describe the deployment of iMC NTA to separate slave server. Before deploying iMC NTA, install the Intelligent Deployment Monitoring Agent on the slave servers.

Starting the remote installation wizard iMC provides two approaches to starting the remote installation wizard: through the web browser and through the iMC downloaded installation package. Start the remote installation wizard through the web browser CAUTION: On Linux, the Firefox browser does not support starting the remote installation wizard of the intelligent deployment monitoring agent. First, on the slave servers, open the web browser and enter http://192.168.4.44:8080/imc in the address bar. 192.168.4.44 is the IP address of the master server and 8080 is the HTTP port number. The 39

iMC login page appears. Type the username and password, and then click Login. The Home tab appears. NOTE: •

192.168.4.44 is the IP address of the master server, and 8080 is the HTTP port for Web services.

•

The username and password of the super user for the system are both admin.

Select the System tab to enter the System Management page. On this page, click Component Deploy. On the Installed Components page, click Start deploy. A dialog box appears, as shown in Figure 31. Figure 31 Whether to launch the intelligent deployment monitoring agent

Click OK . The Downloading application dialog box appears, as shown in Figure 32, indicating that Java file (jre.exe) is being downloaded. NOTE: If JRE6.0 has been installed on the slave servers, the system starts the remote installation wizard when you click OK . Figure 32 Downloading application

After the Java file is downloaded and installed, the Choose Target Folder for Deployment dialog box appears, as shown in Figure 36. Start the remote installation wizard through the iMC downloaded installation package On the slave servers, run the installslave.bat script in the install directory of the iMC downloaded installation package. The Address of Master window appears, as shown in Figure 33. NOTE: To start the remote installation wizard of the intelligent deployment monitoring agent on Linux, run the installslave.sh script in the install directory in the iMC downloaded installation package.

40

Figure 33 Address of Master

Type the IP address of the master server, and click OK . The Checking Database Connectivity window appears, as shown in Figure 34. Figure 34 Checking Database Connectivity

You must pass the database authentication before perform the installation and deployment. Therefore, you must select the database type, and the instance name created in the SQL Server installation, and then enter the superuser name (sa by default), password, and listening port number (1433 by default). NOTE: When you install iMC on Linux that uses Oracle database, select a network service name or click the icon to add a network service name. If a local database is used, you must configure a network service name for connecting to the local database address. If a separate database is used, you must configure a network service name for connecting to the database server address. For more information about the network service name configuration, see Oracle 11g Installation and Configuration Guide or Oracle 11 R2 Installation and Configuration Guide . When you use the database on the slave server, select local host for the database location, and enter the superuser name (sa by default) and password, as shown in Figure 34. When you use a separate database server, select other server for the database location, specify the server IP address, and enter the superuser name (sa by default) and password of the corresponding database, as shown in Figure 35.

41

Figure 35 Checking Database Connectivity

Click OK to start checking the database connectivity. After the installation environment check succeeds, the iMC Installation Wizard appears. Input the correct master server IP address, and click OK . Then, the Choose Target Folder for Deployment window of the HP iMC Remote Installation Wizard appears, as shown in Figure 36, which means that you have successfully started the remote installation wizard. NOTE: If you have deployed other components before deploying the current component, the Database Configuration Info window as shown in Figure 40 does not appear if the password for the user sa is not modified and the available space of the disk saving the data file exceeds 1 GB when you deploy the current component.

Installing the intelligent deployment monitoring agent After successfully starting the remote installation wizard, you can start to install the deployment monitoring agent. Figure 36 Choose Target Folder for Deployment

42

As shown in Figure 36, the default deployment location is C:\Program Files\iMC (or in /opt/iMC on Linux). If you want to deploy iMC in another location, you can either type a path or click Browse to select one path. After selecting a deployment location, click Install to start file downloading. After the files are downloaded, the Installation Completed dialog box appears, as shown in Figure 37. Figure 37 Installation Completed

Then, click Finish.

Deploying the iMC NTA On the slave servers, select 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). In the displayed window, select the Deploy tab, as shown in Figure 38. Figure 38 Information about component deployment

Select the Network Behavior Analyzer Server component that has not been deployed, right-click it, and select Batch Deploy from the shortcut menu. Then, the Batch deploy window as shown in Figure 39 appears. 43

Figure 39 Batch deploy

In the Batch deploy window, select Network Behavior Analyzer Server and Network Traffic Analyzer Server , and click OK . Then, the system starts downloading the files. After downloading is complete, the Database Configuration Info window as shown in Figure 40 appears. Figure 40 Database Configuration Info

Enter the password for the user sa for the current database, which is the superuser name for installing iMC, and select a data file location. By default, iMC saves the data file in C:\Program Files\imcdata. To modify the data file location, click Browse to select one. After selecting the data file location, click Deploy to start the deployment. After the deployment is finished, the Batch deploy result dialog box prompting Batch deploy succeeded appears. Click OK . After successfully finishing the deployment, select the Deploy tab in the intelligent deployment monitoring agent, as shown in Figure 41.

44

Figure 41 Information about component deployment

On the master server, select 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). In the displayed window, select the Monitor tab and click Start iMC. A dialog box appears asking you if you want to start all the processes of iMC. Click OK . After all processes start, iMC is ready for use.

45

Upgrading iMC This chapter describes how to upgrade iMC components, using upgrading iMC Platform patches as an example. After you install the iMC Platform and components, if you want to upgrade the iMC Platform, first make the following preparations: The components require iMC V5.0 or a higher version. For the compatibility matrix, see the readme file. For data safety, HP recommends that you back up the database by using the Intelligent Monitoring Agent Environment tab, and copy the entire iMC installation path, it is not done during upgrade. For how to back up the iMC database, see “ Database backup and restoration.“ Download the upgrade packages for all listed components before you upgrade the iMC Platform. CAUTION: •

•

•

To upgrade the iMC Platform without upgrade packages for a component, you must remove the component and then upgrade the iMC Platform. Otherwise, the upgraded iMC Platform is not available. Removing a component will cause loss of the corresponding data. To upgrade iMC from version 3.x to version 5.x, re-log in 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.

Backing up iMC Before upgrading iMC, you must back up iMC in case of upgrade failure. According to the iMC deployment, use one of the following methods to back up iMC: For iMC deployed in distributed mode, back up iMC on the master and all slave servers. For iMC using separate databases, use the manual backup feature to immediately back up the database of each component. For more information, see “ Database backup and restoration.” For iMC deployed in stateful failover mode, only back up iMC on the servers that are online. Follow the steps to back up iMC: 1.

Log in to the operating system as an Administrator .

2.

Run the install\backup.bat script in the downloaded installation package. The Backup iMC window appears, as shown in Figure 42.

46

CAUTION: •

•

To normally back up iMC in Windows Server 2003 or Windows Server 2003 R2, you must log in as an administrator and then back up iMC. To normally back up iMC in Windows Server 2008 or Windows Server 2008 R2, you must first right-click the backup.bat script and select Run as Administrator from the shortcut menu, or modify the User Account Control Settings and then restart the server. After backing up iMC, you can restore the related settings as needed. Modify the User Account Control Settings as follows: Select Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center , and the User Account Control Settings window appears. In the window, set the Choose when to be notified about changes to you computer to Never notify.

NOTE: To back up iMC on Linux, you must start the iMC installation wizard by running thebackup.sh script in the install directory of the iMC installation package as a root user. Figure 42 Back up iMC

3.

Click Browse to choose the location for saving the backup files. Before doing that, check the size of the backup files and make sure the disk for saving the files has enough memory. Insufficient memory may cause backup failure.

Figure 43 Choose the backup file location

4.

Click Start to start backing up iMC.

After the backup is complete, the backup file directory generates a package iMC.zip, which contains the complete backup files under the iMC installation path. In the backup directory also is a folder db\, which contains the database backup data of all components.

Upgrading iMC To upgrade an iMC component, make sure that the iMC Platform has been installed, and the components on which the component you want to upgrade depends have been installed and upgraded. NOTE: To view the dependency between components, select Show Dependencies from the right-click menu of a component in the Deploy tab in the HP Deployment Monitoring Agent. Use one of the following ways to start upgrading iMC components: 47

On the Installation Completed window as shown in Figure 13, 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 intelligent deployment monitoring agent and then click Install new components on the Monitor tab. CAUTION: •

•

To normally upgrade iMC in Windows Server 2003 or Windows Server 2003 R2, you must log in as an administrator and then upgrade iMC. To normally upgrade iMC in Windows Server 2008 o r Windows Server 2008 R2, you must first select Start > All Programs > H3C Intelligent Management Center , right-click Deployment Monitoring Agent, and select Run as Administrator from the shortcut menu to open the deployment monitoring agent, or modify the User Account Control Settings and then restart the server. After upgrading iMC, you can restore the related settings as needed. Modify the User Account Control Settings as follows: Select Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center , and the User Account Control Settings window appears. In the window, set the Choose when to be notified about changes to you computer to Never notify. On the system tray of Windows, right-click the Deployment Monitoring Agent icon, and select Install from the menu.

Then, the Choose folder window as shown in Figure 44 appears. Figure 44 Choose folder

Click Browse, and select folder install\components in the upgrade files. Then, click OK . The Welcome to HP iMC Installation Wizard window as shown in Figure 45 appears. Figure 45 Welcome to HP iMC Installation Wizard

48

Click Next, and the Agreement window as shown in Figure 46 appears. Figure 46 Agreement

Read the license agreement carefully, select Accept, and click Next. Then, the Upgrade Common Components window as shown in Figure 47 appears. Figure 47 Upgrade Common Components

Click OK . The system starts upgrading common components, as indicated by the Upgrade Common Components window in Figure 48. Figure 48 Upgrade Common Components

After the common components are upgraded, the Choose Target Folder window as shown in Figure 49 appears. 49

Figure 49 Choose Target Folder

The Choose Target Folder window displays the components to be upgraded. The system will install the upgrade files in the location where the iMC Platform is installed. Check the information, click Next, and the Deployment and Upgrade Options window as shown in Figure 50 appears. Figure 50 Deployment and Upgrade Options

You can select a deployment and upgrade option as prompted by the window. In this example, select Deploy or upgrade at once, click Next, and the Installation Summary window as shown in Figure 51 appears.

50

Figure 51 Installation Summary

Check the installation summary, click Install, and the Installing window as shown in Figure 52 appears. Figure 52 Installing

The installation wizard is installing the components. The installation will take a while. After the installation is finished, the Batch upgrade window as shown in Figure 53 appears.

51

Figure 53 Batch upgrade

Select the components you want to upgrade, and then click OK . After the selected components are upgraded, the Batch upgrade result window as shown in Figure 54 appears. Figure 54 Batch upgrade result

Click OK . On the Monitor tab of the deployment monitoring agent, click Start iMC. After the processes of all components are started normally, iMC is ready for use. NOTE: •

•

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 normally. If this is a distributed deployment, upgrade all components deployed on slave servers separately.

CAUTION: When iMC is deployed in distributed mode on Linux that uses Oracle database, you must install related tools on the master iMC server after upgrading iMC from version 5.1 to 5.5, so that the master and subordinate servers can communicate with each other. If you changed the IP address of the iMC server or database server before upgrading iMC, you must configure a network service name on the subordinate iMC server for connecting to the modified IP address after upgrading iMC and installing tools. For more information about the network service name configuration, see Oracle 11g Installation and Configuration Guide or Oracle 11g R2 Installation and Configuration Guide .

Restoring iMC (optional) If errors occur in iMC upgrading, you must restore iMC. According to the iMC deployment, use one of the following methods to restore iMC: 52

For iMC deployed in distributed mode, restore iMC on the master and all slave servers. For iMC deployed using separate databases, manually restore the iMC installation path, and then immediately restore the database of each component. For more information, see “ Manually restoring databases.” For iMC deployed in stateful failover mode, only restore iMC on the servers that are online. Follow these steps to restore iMC: 1. 2.

Restore iMC database. See “Manually restoring databases.” When the restoration is complete, stop all iMC processes, including the monitoring agent and HP iMC server.

3.

Manually delete all the files in the iMC installation path.

4.

Decompress the iMC.zip package to the iMC installation path.

CAUTION: In the Windows operating system, use WinRAR or 7-Zip to decompress the package, other than the decompression tool that comes with the Windows system. 5.

Restart iMC processes, such as the monitoring agent and HP iMC server.

53

Logging in to iMC On a PC running Windows, you can log in to iMC through IE 6.0 SP1 or higher, or through Firefox 3.6 or higher; on a PC running Linux, you can log in to iMC through Firefox 3.6 or higher. Use the browser to access http://192.168.4.44:8080/imc, and the iMC login page appears. Input the correct username and password, and then click Login to enter the home page of iMC. NOTE: •

192.168.4.44 is the IP address of the master server, and 8080 is the HTTP port for Web services.

•

The username and password of the super user for the system are both admin.

After installing and deploying the UAM user self-service, you can access the iMC self-service center in one of the following two ways: http://192.168.4.66:8080 http://192.168.4.66:8080/selfservice NOTE: 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 for Web services. After installing and deploying the SOM service desk, you can access the service desk by accessing http://192.168.4.22:8080/servicedesk. NOTE: 192.168.4.22 is the IP address of the server where the SOM service desk is deployed, and 8080 is the HTTP port.

54

Removing iMC The iMC uninstallation on Windows and Linux systems are similar. The following describes how to remove iMC from a Windows Server 2003-based machine.

Removing an iMC component You can remove a deployed component through the intelligent deployment monitoring agent. Perform the following steps: 1.

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

2.

In the window displayed, select Stop iMC from the Monitor tab to stop all processes of iMC.

3.

In 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. Then click OK .

4.

In 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. Then, click OK .

NOTE: When you remove an iMC component deployed in distributed mode, undeploy the component on the server where it was deployed, and then remove the component on the master server. Before removing a component, remove the components that depend on it, if any. In the following two cases, the deployment information of a removed component cannot be cleared automatically: The component was removed from the slave servers by force, which is an incorrect operation. The slave server crashed when the component was being removed from it. To solve the problem, perform the following steps: 1.

Select the component on the Deploy tab of the intelligent deployment monitoring agent on the master server.

2.

Right-click Uninstall the Component for the master server only.

To re-install a component removed from a monitoring agent, you must restart the deployment monitoring agent and HP iMC server, with the following steps: 1.

Quit the deployment monitoring agent window.

2.

Stop the HP iMC server process.

3.

Start the HP iMC server process.

4.

Start the intelligent deployment monitoring agent.

5.

Click Install in the Monitor tab to begin installation

55

Removing all iMC components at one time The following sections describe how to remove the iMC software deployed in centralized and distributed modes respectively. NOTE: •

•

When reinstalling iMC, you must manually delete the folder named imcdata, which is created on the master server upon installation of iMC if you have re-installed an SQL server database after you uninstalled iMC. If you fail to install or uninstall iMC, manually delete the iMC installation folder and the iMC-Reserved folder in the Windows installation directory (or delete this folder in the/etc directory on Linux operating systems); otherwise, iMC cannot be reinstalled.

Removing iMC deployed in centralized mode 1.


2.

In the popup window, select Stop iMC in the Monitor tab to stop all processes of iMC.

3.

Select Start > All Programs > HP Intelligent Management Center > Uninstall HP Intelligent Management Center (or run the uninstall.sh script in /deploy of the iMC installation path on Linux). A window appears to guide you through the rest of the process.

4.

Click Uninstall.

5.

Click Finish when the Uninstallation Completed dialog box appears.

6.

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

7.

Reboot the system.

Removing iMC deployed in distributed mode To remove the iMC software deployed in distributed mode, you must remove the components deployed on the slave server before removing the iMC software deployed on the master server.

Removing components deployed on the slave server 1.


2.

In the popup window, select Stop iMC in the Monitor tab to stop all processes of iMC.

3.

Select Start > All Programs > HP Intelligent Management Center > Uninstall HP Intelligent Management Center (or run the uninstall.sh script in /deploy of the iMC installation path on Linux). A window appears to guide you through the rest of the process.

4.

Click Uninstall.

5.

Click Finish when the Uninstallation Complete dialog box appears.

6.


7.

Reboot the system.

56

Removing components deployed on the master server Before removing the components deployed on the master server, ensure that all components deployed on the slave server and the intelligent deployment monitoring agent are removed. To remove the components deployed on the master server, perform the following steps: 1.

Click Stop on the Monitor tab in the Intelligent Deployment Monitoring Agent window to stop all the processes of iMC.

2.

Select Start > All Programs > HP Intelligent Management Center > Uninstall HP Intelligent Management Center (or run the uninstall.sh script in /deploy of the iMC installation path on Linux). Then, a window appears to guide you through the rest of the process.

3.

Click Uninstall.

4.

Click Finish when the Uninstallation Completed window appears.

5.


6.

Reboot the system.

57

Registering iMC and incremental node licenses An unregistered iMC version delivers the same functions as that of a registered iMC, but can be used for 60 days only. 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 2003-based machine. NOTE: Please ensure you Register and Activate iMC before Registering and Activating any additional node licenses. CAUTION: To transfer an existing license to a different Serial Number, contact your local HP Support office.

Registering iMC From the iMC login page click on the Activate link to enter the License Information page as shown in Figure 55. Figure 55 License Information

Select and copy or make a note of the Serial Number (this is unique to your installation of iMC).

Registering first license Go to the HP My Networking system web site (http://hp.com/networking/mynetworking/ ), log in to My Networking portal, and the HP Passport sign-in page will appear, as shown in Figure 56.

58

Figure 56 HP Passport sign-in

Input the User ID and Password, and then click Sign in. The Welcome Robin Sharp page will appear, as shown in Figure 57. Figure 57 Welcome Robin Sharp page

Click on the My Licenses tab from the tabular navigation system on the top. The Enter Order number or Registration ID page will appear, as shown in Figure 58.

59

Figure 58 Enter Order number or Registration ID page

Input the Order number or Registration ID, and then click Next. The Enter the email associated with Order number page will appear, as shown in Figure 59. Figure 59 Enter the email associated with Order number page

Input an email address associated with Order number, and then click Next. The Select the Product License page will appear, as shown in Figure 60.

60

Figure 60 Select the Product License page

Select the product for which you want to register or activate a license. Input the quanti ty to be redeemed and click Next. The Enter details page will appear, as shown in Figure 61. Figure 61 Enter details page

Input the Base software serial number, and then click Next. The License agreement page will appear, as shown in Figure 62.

61

Figure 62 License agreement page

Read the license agreement, select I accept all of the above terms, and then click Finish. The Confirmation page will appear, as shown in Figure 63. Figure 63 Confirmation page

Click Save as, 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. If you need to email the confirmation, enter the Send license confirmation to and Comments, and then click Send email in this page. Also, you can view the details of the license you have registered.

62

Registering incremental node licenses Registering an Incremental Node License is similar to registering the first license. This section describes only the differences between them. To register an Incremental Node license, select the Incremental Node License you want to register on the Select the Product License page, as shown in Figure 64. Figure 64 Select the Product License page

Then, click Next. The Enter details page will appear, as shown in Figure 65.

63

Figure 65 Enter details page

Select you base product and enter the Base software serial number, and then click Next. The Confirmation page will appear, as shown in Figure 63. Click Save as, 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.

Activating iMC Return to the License Information page, as shown in Figure 55. Select Activate now, the Activate Your Product page appears as shown in Figure 66. Figure 66 Activate Your Product

After selecting the license file in the format of .txt, select the license type, which can be Register/Activate host license or Register/Activate back-up license, as needed, and click OK . The Activations Succeeded dialog will appear as shown in Figure 67. Figure 67 Activation Succeeded

64

Reboot the system. Your iMC system has now been successfully Registered and Activated.

iMC V5.0 license upgrade process 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 V5.0. You need to download your updated iMC license file from My Networking and reactivate your iMC V5.0. The following example describes how to update iMC license file from My Networking and reactivate your iMC V5.0. 1.

Find your iMC Serial Number

Follow the Activate link from the iMC login page to enter the License Information page. Your iMC serial number is clearly displayed. When you need to enter your iMC serial number into My Networking, it is simplest to just select and copy & paste the serial number from your iMC License information page. 2.

Reset your new HP Passport password so you can login to My Networking using your new HP Passport account

Go to the HP My Networking system web site (http://hp.com/networking/mynetworking/ ), log in to My Networking portal, and the HP Passport sign-in page will appear. Your eSupport user account has been transferred to My Networking and a HP Passport accou nt has been created using your eSupport user name. You need to reset your HP Passport password before you can login. Follow the Forgot Password link. Provide the email address of your eSupport account user. An email is sent to you containing instructions for resetting you password. Follow the email instructions to click on the Choose a new password link. Enter your new HP Passport password. Then select your security questions and answers. You have now successfully reset your HP Passport password. In future you can login to My Network using this new HP Passport account with your original eSupport user name and this new password. 3.

Login to My Networking

Click on Continue in the Change HP Passport password page, and you will be logged into My Networking. The Welcome Robin Sharp page will appear. 4.

Locate your iMC licenses

Click on the My Licenses tab from the tabular navigation system on the top. The Enter Order number or Registration ID page will appear. Click on View Licenses from the My Licenses navigation. Find your iMC Platform license in the list of your licenses. If necessary copy & paste your iMC serial number into the search field and click the Search button. 5.

Download the updated iMC license file

Click on the appear.

link corresponding to the iMC Platform license. The license information page will

65

Click on the Download License link. Choose to save the license file, and choose where to save the license file. You will need to locate it later. 6.

Updating your iMC V5.0 license file

Follow the Activate link on the iMC login page to enter the License Information page. Click on Activate now button, the Activate Your Product page appears. Browse to the location where you saved the license file and select it, and click OK . The Activations Succeeded dialog will appear. After selecting the license file in the format of .txt, select the license type, which can be Register/Activate host license or Register/Activate back-up license, as needed, and click OK . The Activations Succeeded dialog will appear Your iMC V5.0 should now be fully licensed with the equivalent licenses you had before.

iMC V5.1 license upgrade process To upgrade iMC V5.0 to iMC V5.1, you only need to upgrade the license of QoSM components. The QoSM license upgrade process is the same as the V5.0 license upgrade process. For more information, see “iMC V5.0 license upgrade process.”

66

Security settings Anti-virus software To ensure the secure running of the iMC server, HP recommends that you install anti-virus software, and update the virus library in time.

Port settings To ensure the steady running of the iMC server, HP recommends that you use a firewall to control the data sent to the iMC server cluster, that is, filter the non-service data sent to the iMC server. In this way, abnormal attacks can be effectively prevented. CAUTION: •

•

HP recommends that you use ACL configurations on a firewall rather than on a switch to control data packets; otherwise, packet fragmentations will be filtered. If you have installed firewall software on the iMC server, besides setting the ports listed in Table 10, set an IP address for the master server and all the slave and database servers to ensure normal communication between them.

The following table lists the port numbers used by the components of the iMC. Table 11 Port numbers used by the iMC PLAT Default port number

Usage

Location

UDP 161

Port to add a device to the iMC

Device end

UDP 22

Port for SSH-related operations

Device end

TCP 23

Port for Telnet-related operations

Device end

UDP 514, 515

Port for Syslog-related operations

iMC server

UDP 162

Port for Trap-related operations

iMC server

TCP 8080, configurable

Port for the access to the iMC through HTTP

iMC server

TCP 8443, configurable

Port for the access to the iMC through HTTPS

iMC server

UDP 69

Port for the iCC to perform configuration management through TFTP

iMC server

TCP 20, 21

Port for the iCC to perform configuration management through FTP

iMC server

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

TCP 8051

Listening port used to monitor the command for stopping the NTA/UBA service

iMC server

67

Default port number

Usage

Location

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

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

68

Database backup and restoration Dbman, the automatic backup and restoration tool for iMC databases, provides a full-range system disaster backup solution. Through Dbman, the iMC Platform database and the component databases can be automatically backed up and restored. Dbman uses a standard SQL backup and restoration mechanism, and processes the complete dat abases. You can perform corresponding configurations and operations based on different application scenarios to implement manual and automatic data backup and restoration. Dbman is integrated in the Intelligent Deployment Monitoring Agent, as shown in Figure 68. Figure 68 Environment tab

On the left of the Environment tab displays the software and hardware information of the server(s), on the right displays the usage of the user database file and log file, and at the bottom is the Dbman database backup and restoration configuration area. You can back up iMC databases in either of the following two ways: Back up the databases to the local server cluster (one or a group of servers depending on different scenarios): To restore the databases in this case, you can only do it manually. Back up the databases to the backup server cluster (one or a group of servers depending on different scenarios): When the primary server in the master server cluster fails, iMC automatically switches to the backup server cluster, and uses the database files saved on the backup server cluster. CAUTION: Before configuring Dbman to back up databases, make sure: •

•

The servers in the master server cluster and backup server cluster use the same operating system, the same iMC versions and patches, and the same database types and versions. FTP server is installed on all backup servers.

69

Database backup and restoration on the local server cluster This section describes how to back up and restore iMC databases in different deployment scenarios.

Database backup and restoration in centralized mode Application scenario: The whole iMC system is deployed on one server.

Backing up databases Database backup for iMC deployed in centralized mode allows you to back up the iMC databases to the local server by using Dbman in either of the following two ways: Manual backup: Allows you to manually back up the iMC databases immediately. Automatic backup: Allows you to configure automatic database backup to periodically back up the iMC databases to the specified server. 1.

Manual backup

Start the Intelligent Deployment Monitoring Agent on the local server, and click Backup in the Environment tab, as shown in Figure 68. The Select database backup path dialog box appears, prompting you to specify the backup file save path. Select the backup file save path, click OK , and the system begins to back up all databases used by the iMC system on the server to the specified path. 2.

Automatic backup

Start the Intelligent Deployment Monitoring Agent on the master server whose databases are to be backed up, and click Configure in the Environment tab, as shown in Figure 68. The Auto Backup and Restore Configuration dialog box appears, on which you can configure automatic backup parameters, as shown in Figure 69.

70

Figure 69 Auto Backup and Restore Configuration

You can configure the following parameters as needed: Enable auto backup and restoration: Enables or disables Dbman. Max Size of Log File: Specifies the maximum size of the log file for database backup and restoration. The default path of the log file is iMC_install\dbman\log. If the log file exceeds the maximum size, the system automatically generates a new log file. File Lifetime: Specifies the duration for storing automatic backup files. The expired files will be removed. Operation Type: Specifies automatic backup or automatic restoration. Select Auto Backup in this configuration. Backup Time in a Day: Specifies the time at which automatic backup operation starts every day. Backup File Location: Specifies the path to which backup files are saved. Set the path to a d isk that has enough space because backup files are typically large. Do not set the path to the operating system drive because the operating system cannot start normally when this drive is fully occupied. Upload backup files to FTP Server: Specifies an FTP server to which backup files are uploaded. FTP Host: IP address of the FTP server. FTP User: FTP username. You can leave this field blank to log in as an anonymous user. FTP Password: FTP user password. Upload backup files to FTP Server: Allows you to set whether to delete locally saved files after uploading these files to the FTP server. After the configuration, click OK , and the system automatically backs up the iMC databases at the specified time. 71

Manually restoring databases To manually restore databases, start the Intelligent Deployment Monitoring Agent on the server, and click Restore in the Environment tab, as shown in Figure 68. A confirmation dialog box as shown in Figure 70 appears. Figure 70 Confirmation dialog box

To restore databases of the iMC system that has been started, click Yes. A dialog box appears for you to select a database file to be restored. Select all database files. Click OK . A confirmation dialog box appears saying “Do you want to start iMC immediately after the restoration is complete?” If you click Yes, the system begins to restore the databases. The system prompts restoration success after the restoration is complete. Then click OK , and iMC will be automatically started. If the iMC system has just been installed (not started yet), click No, start iMC, and then repeat the step above. CAUTION: When restoring databases of the iMC system, also restore databases of all components that have been deployed. If you restore only some of them, data will be lost. NOTE: During the restoration process, the system stops and then restarts iMC and the database server.

Database backup and restoration in distributed mode Application scenario: An iMC system is deployed to multiple servers.

Backing up databases to the local server cluster (databases not deployed on a separate server) When iMC is deployed in distributed mode and the database of each component is deployed on the same server as the component, Dbman backs up the database of each component to the specified server. You can back up the databases in either of the following two ways: Manual backup: Allows you to manually back up the iMC databases on the current server cluster immediately. For more information, see “Manual backup.” Automatic backup: Enables you to configure automatic backup to periodically back up the iMC databases on the current server cluster. You can also back up the databases to the specified server cluster through FTP. For more information, see “ Automatic backup.” CAUTION: To ensure the databases can be used normally after they are backed up, set the same automatic backup time on each server. 72

Manual restoration enables you to use Dbman to restore the database of each iMC component on the server where the component is deployed. For more information, see “ Manually restoring databases.”

Backing up databases to the local server cluster (databases deployed on a separate database server) A typical application scenario of this database backup and restoration method is deploying iMC in distributed mode and deploying the databases of all iMC components to a separate database server. For more information about database backup and restoration in this scenario, see “ Configuration guidelines.”

Database backup and restoration to the backup server cluster This section describes how to back up and restore iMC databases to the backup server cluster in different deployment scenarios.

Database backup and restoration to the backup server cluster (centralized mode) Application scenario: Deploy an iMC system in centralized mode on the master server and backup server respectively. Select the license type as master server license on the master server, and select the license type as backup server license on the backup server. NOTE: To implement database backup to the backup server for iMC deployed in centralized mode, the iMC components of the master server and the backup server must be deployed in the same way.

Backing up databases to the backup server You can use Dbman to periodically back up the iMC databases to the backup server so that when the master server fails, you can log in to the iMC system of the backup server. You can back up the databases to the backup server in either of the following two ways: Manual backup: Enables you to manually back up the iMC databases on the master server immediately to the backup server. For more information, see “ Manual backup.” Automatic backup: Allows you to configure automatic backup to periodically back up iMC databases to the specified backup server cluster. For more information, see “ Automatic backup.”

Manually restoring databases You can use Dbman on the backup server to immediately restore the database backup files on the master server so that the data on the backup server is the same as the backup data on the master server. To manually restore the databases, start the Intelligent Deployment Monitoring Agent on the backup server, and click Restore in the Environment tab, as shown in Figure 68. A confirmation dialog box as shown in Figure 71 appears.

73

Figure 71 Confirmation dialog box

To restore databases of the iMC system that has been started, click Yes. A dialog box appears for you to select a database file to be restored. Select all database files. Click OK . A confirmation dialog box appears saying “Do you want to start iMC immediately after the restoration is complete?” If you click Yes, the system begins to restore the databases. The system prompts restoration success after the restoration is complete. Then click OK , and iMC will be automatically started. If the iMC system that has just been installed (not started yet), click No, start iMC, and then repeat the step above. CAUTION: When restoring databases of the iMC system, also restore databases of all components that have been deployed. If you restore only some of them, data will be lost.

Automatically restoring databases You can configure Dbman to periodically restore the database backup files on the master server so that the data on the backup server is the same as the backup data on the master server. To automatically restore the databases, start the Intelligent Deployment Monitoring Agent on the backup server, and click Configure in the Environment tab, as shown in Figure 68. A confirmation dialog box as shown in Figure 72 appears.

74

Figure 72 Automatic Restoration Configuration

You can configure the following parameters as needed: Operation Type: Specifies automatic backup or automatic restoration. Select Auto Backup in this configuration. Location to archive restored files: Specifies the path (typically the root directory on the FTP server) to store files to be restored. iMC periodically restores the databases according to the backup files saved in the path. Backup files location: Specifies the backup path for database backup files. iMC saves the database backup files to the specified path after restoring the database backup files. After the configuration, click OK . After the master server backs up the databases and sends the backup files to the backup server, the backup sever automatically restores the databases as long as it finds the database backup files have been sent to it.

Database backup and restoration to the backup server cluster (distributed mode) Backing up databases to the backup server cluster (databases not deployed on a separate database server) You can back up iMC databases to the backup server cluster (distributed mode) in these two scenarios: Application scenario 1: Deploy an iMC system in distributed mode on the master server cluster and backup server cluster respectively. The number of servers and the way the iMC components are deployed in the master and backup server clusters must be consistent. Select the license type as master server license on the master server cluster, and select the license type as backup server license on the backup 75

server cluster. In this scenario, Dbman periodically backs up the iMC databases on each server in the master server cluster to the corresponding server in the backup server cluster so that when the primary server in the master server cluster fails, you can log in to the iMC system of the primary server in the backup server cluster to perform operations. Application scenario 2: Deploy an iMC system in distributed mode on the master server cluster and an iMC system in centralized mode on the backup server. Select the license type as master server license on the master server cluster, and select the license type as backup server license on the backup server. In this scenario, Dbman periodically backs up the iMC databases on each server in the master server cluster to the backup server so that when the primary server in the master server cluster fails, you can log in to the iMC system of the backup server to perform operations. You can back up the databases to the backup server cluster in either of the following two ways: Manual backup: Enables you to manually immediately back up the iMC databases on the master server cluster to the backup server cluster. For more information, see “ Manual backup.” Automatic backup: Allows you to configure automatic backup to periodically backup iMC databases to the specified backup server cluster. For more information, see “ Automatic backup.” CAUTION: To ensure the databases can be used normally after they are backed up, set the same automatic backup time on each server. You can use Dbman on the backup server cluster to immediately restore the database backup files on the master server cluster so that the data on the backup server cluster is the same as the backup data on the master server cluster. For more information, see “ Manually restoring databases.” You can configure Dbman on the backup server cluster to periodically restore the dat abase backup files on the master server cluster so that the data on the backup server cluster is the same as the backup data on the master server cluster. For more information, see “ Automatically restoring databases.”

Backing up databases to the backup server cluster (databases deployed to a separate database server) You can back up iMC databases to the backup server cluster (distributed mode) in these two scenarios: Application scenario 1: Deploy an iMC system in distributed mode on the master server cluster and backup server cluster respectively, and each of them uses a separate database server. Select the license type as master server license on the master server cluster, and select the license type as backup server license on the backup server cluster. Application scenario 2: Deploy an iMC system in distributed mode on the master server cluster and an iMC system in centralized mode on the backup server, and each of them uses a separate database server. Select the license type as master server license on the master server cluster, and select the license type as backup server license on the backup server. In these two scenarios, Dbman periodically backs up the iMC database on each server in the master server cluster to the backup server so that when the primary server in the master server cluster fails, you can log in to the iMC system of the backup server to perform operations. In both of these two scenarios, a separate database server is used. For more information, see “Configuration guidelines.”

76

Database backup and restoration when a separate database server is used In the scenario where a separate database server is configured, there are no database files on the servers where iMC components are deployed, so you cannot backup and restore databases on the iMC servers. Therefore, to backup databases, you must copy the backup configuration files generated and other related files on the iMC servers to the database server, and install and run Dbman on the database server. Perform these steps: Start the Intelligent Deployment Monitoring Agent on the server where the iMC Platform is deployed, and click Configure in the Environment tab, as shown Figure 68. The Auto Backup and Restore Configuration dialog box appears, as shown in Figure 69. After the configuration, click OK . A message dialog box appears, as shown in Figure 73. Figure 73 Database backup prompt message

If you perform the database backup and restoration for the first time, install Dbman as prompted in Figure 73 with the following steps: 1.

Copy the dbman folder under the iMC installation path to the database server (to the folder INSTDIR, for example).

CAUTION: The folder INSTDIR is for example only. You can set a folder name as needed and must use the same folder name in the following operations and commands. 2.

On Windows, install Microsoft Visual C++ 2008 Redistributable, whose installation program is saved in iMC installation CD\components\common\server\vcredist.exe on the database server. On Linux, set the environment variables: expor t LD_L I BRARY_PATH= $LD_LI BRARY_PATH: / I NSTALL_ DI R/ dbman/ bi n: / $ORACLE_HOME/ l i b.

3.

Run Dbman on the database server. On Windows, open the Command Prompt window, and use the cd command to enter the INSTDIR\dbman\bin\ folder. X:

X is the drive number of the logical disk that saves the INSTDIR folder. cd \ I NSTDI R\ dbman\ bi n\

On Linux, open the Terminal window, and use the cd command to enter the INSTDIR/dbman/bin/ folder: cd / I NSTDI R/ dbman/ bi n/

77

Perform the following operations as prompted: Start automatic backup and restoration: dbman. Stop automatic backup and restoration: dbman -k. Manually back up: dbman –backup “path where the backup file is saved” Manually restore: dbman -restore “specifies the path and name of the file to be restored” To restore multiple databases simultaneously, use the colons (;) to separate the database files. See the following sentence: dbman –r est or e “C: \ moni t or _db_i mc_moni t or _db_20090626_095700_f ul l . db; conf i g_db_i mc_conf i g_db_20090626_09 5714_f ul l . db”

Check whether Dbman runs normally: dbman –c CAUTION: •

•

Do not close the Command Prompt window or Terminal window for running the automatic database backup command dbman. Otherwise, the backup process terminates. Before performing manual restoration, stop running the intelligent deployment monitoring agent on the iMC server. Otherwise, you cannot manually restore the database.

After you install Dbman on the database server, and upgrade iMC PLAT components, you must perform the following operations: 1.

Terminate the automatic backup process on the database server: dbman - k

2.

Copy the dbman folder under the iMC installation path to the database server (to the folder INSTDIR, for example).

3.

Start the automatic backup process on the database server: dbman

After you install Dbman on the database server, and modify backup and restoration parameters for the intelligent monitoring agent without upgrading iMC PLAT components, you must perform the following operations: 1.

Terminate the automatic backup process on the database server: dbman - k

2.

Copy the dbman.conf file under the iMC installation path \dbman\etc\ (/dbman/etc/ on Linux) to the INSTDIR\dbman\etc\ directory on the database server (INSTDIR is for example only).

3.

Start the automatic backup process on the database server: dbman

NOTE: •

•

Automatic database restoration is not supported when a separate database server is configured. If you perform manual database restoration on the database server, the system restarts the SQL Server database. Make sure that the SQL Server database on the database server is not occupied by other programs.

78

Configuration guidelines If a component of the iMC system, such as NTA, has a large amount of data, do not configure backup and restoration for such data when configuring Dbman. To disable Dbman from backing up the database, perform the following: In the dbman\etc folder of the database server of the component, create a file with extension .skip (for example, nta.skip), and write the following to the file: dbName=nt a_db ( f or SQL Ser ver / MySQL) dbUser Name=i mc_ nt a ( f or Or acl e)

After you save the .skip file, Dbman automatically reads the file and does not back up the database in the file. 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 INSTALL_DIR\dbman\etc\dbman_addons.conf. After you save the file, iMC automatically executes the configurations you added. For example, write the following before or after database restoration: Bef or eSQLScr i pt _moni t or _db_i mc_moni t or = D: \ 1. bat Af t erSQLScr i pt_ moni t or_ db_i mc_moni t or = D: \ 2. bat

To use the report/table customization function of iAR on the master and backup iMC systems, perform following operations. A backup license provides only the reading right. 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. Dbman does not support backup and restoration of the data saved in the configuration file of iMC and other locations. For iMC maintenance, some configuration data of iMC is not saved in the databases, but saved in the configuration file. If you have modified the configuration data, you must manually copy the configuration file from the master server cluster to the backup server cluster when you back up and restore databases. The configuration includes operator authentication sever configuration information (saved in iMC\client\conf\authserver.conf) and device append definition configuration (saved in iMC\client\conf\deviceAppendDef.xml).

79

FAQ When I uninstall iMC in distributed mode from the master server, the component data in the Oracle database cannot be deleted. Why? This is because the data is used by other users that the iMC cannot drop. Restart the operating system or the Oracle database.

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 .

How to install the Java running environment on Linux so that I can access iMC properly through Firefox? To install the Java running environment, install JDK or JRE and then configure JDK or JRE for Firefox. JDK is taken for example in the following part. 1.

Download JDK

Address: http://www.oracle.com/technetwork/java/javase/downloads/index.html Make sure the correct version is downloaded. jdk-6u12-linux-i586-rpm.bin for x86-based Linux. 2.

For

example:

you

must

download

Install JDK

Upload the installation file jdk-6u12-linux-i586-rpm.bin to the server. Suppose the installation file is saved in directory /tmp, execute the following commands: cd / t mp sh j dk- 6u12- l i nux- i 586- r pm. bi n

After executing the commands above, press the Space bar to view the copyright information, and then enter yes to finish the JDK installation. Thus, JDK is installed in directory /usr/java/jdk1.6.0_12. At the same time, a link /usr/java/default pointing the directory /usr/java/jdk1.6.0_12 is generated automatically, equivalent to JDK is installed in directory /usr/java/default. 3.

Configure JDK for Firefox

On the Linux operating system, execute the following commands: c d / var / l ocal / f i r ef ox/ pl ugi ns / l n - s / us r / j ava/ def aul t / j r e / pl ugi n/ i 386/ ns 7/ l i bj avapl ugi n_ oj i . s o

After executing the commands above, you can run /var/local/firefox/firefox to access iMC.

80

In Linux, the current system time in iMC (such as the login time and operation log record time) is different from that on the server, and the difference may be several hours. How to solve the problem? This is because the current time zone setting on the ser ver is different from that when iMC was installed. You can use the tzselect command to modify the time zone of the server.

After iMC is installed in the Windows Server 2003 64-bit edition, the iMC background processes cannot be started. How to solve the 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. If this problem has occurred, fix the problem as follows: stop iMC, install t he patch mentioned above, and then manually execute "iMC installation path\deploy\components\server\vcredist.exe."

When iMC database is installed on a separate database server (Windows Server 2008 or Windows Server 2008 R2), how to solve the abnormality occurred during the deployment process? This is because the user that enabled the SQL Server on the separate database server is not assigned the write access to the imcdata folder in the iMC installation path. To solve the problem, manually change the access right of the imcdata folder on the separate database server.

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. Then check the specified log file according to the prompt information, and only the error information that the object dbo.qv.id already exists is displayed. How to solve the problem? Log in to the Query Analyzer of SQL Server as a sa user, and then execute the following commands: use model EXEC sp_dr opt ype ' qv_i d'

Then, deploy the component again.

When installing iMC on a PC running Windows Server 2008 R2, the system prompts that Windows Installer cannot be installed, as shown in the following figure. How to 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.

In Linux, how can I solve the problem that the JavaService is closed when Xwindows is closed? Use service imcdmsd start to start the JavaService.

81

The report cannot work properly when iMC adopts distributed deployment in Linux with the service components deployed on slave servers, and the master server uses Oracle database on a separate database server. What to do to solve the problem? 1.

Check the configuration files in \common\conf\server-addr.xml of the iMC installation path, and the database names of the components on the slave servers.

Take the following environment for example: The master server is at 192.168.0.1, and the database server is at 192.168.0.100. Deploy UAM component on server A at 192.168.0.2, and deploy WSM components on server B at address 192.168.0.3. Run the server-addr.xml file to view the following information:

or acl e- si d=“or cl ” t ype=“Or acl e”

......

or acl e- si d=“or cl ” t ype=“Or acl e”

......

The configuration information shows that the database names of the components deployed on server A and server B are 192_168_0_2 and 192_168_0_3. 2.

Check the $ORACLE_HOME/network/admin/tnsnames.orafile on the master server, and the configuration of the databases 192_168_0_2 and 192_168_0_3.

192_168_0_2 = ( DESCRI PTI ON = ( ADDRESS = ( PROTOCOL = TCP) ( HOST = 192. 168. 0. 2) ( PORT = 1521) ) ( CONNECT_ DATA = ( SERVER = DEDI CATED) ( SERVI CE_NAME = or cl ) ) ) ...... 192_168_0_3 = ( DESCRI PTI ON = ( ADDRESS_LI ST = ( ADDRESS = ( PROTOCOL = TCP) ( HOST = 192. 168. 0. 3) ( PORT = 1521) ) ) ( CONNECT_ DATA = ( SERVI CE_NAME = or cl )

82

) )

3.

Use vi to run the $ORACLE_HOME/network/admin/tnsnames.orafile on the database server 192.168.0.100 to check whether the above configuration exists. If not, add the above configuration to the file.

On Windows, iMC service processes cannot be started or stopped after iMC runs for a certain period of time. How to solve the problem? This problem is caused by insufficient virtual memory. Set the virtual memory to the system managed size on the server. Follow these steps 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 as shown in Figure 74 appears.

Figure 74 System properties

2.

Select the Advanced tab, and click Settings in the Performance area. Then the Performance Options dialog box as shown in Figure 75 appears.

83

HP Intelligent Management Center Installation Guide (IMC PLAT 5.1 (E0202))

Recommend Documents