HP IMC 7.1 Release Notes

IMC Intelligent Management Center PLAT 7.1 (E0302)

Copyright (c) 2010-2014 Hewlett-Packard Development Company, L.P. and its licensors.

Table of Contents

1. What's New in this Release 2. Problems Fixed in this Release 3. IMC Software Distribution Contents 4. Installation Prerequisites 5. Client Prerequisites 6. Installing and Upgrading IMC 7. Removing IMC 8. Running the Deployment Monitoring Agent 9. Starting IMC 10. Logging in to IMC through a Web Browser 11. Monitoring the Server 12. Distributed Deployment 13. Platform Specific Issues 14. TCP Port Usage 15. Memory Allocation 16. Known Problems

What's New in this Release

IMC PLAT 7.1 (E0302) can be installed directly, or you can upgrade from only IMC PLAT 7.0

(E0101) or later versions.

To upgrade from versions prior to v 7.0, upgrade both the IMC Platform and all the deployed

service components through each released version. The upgrade path is V3.3 >> V5.0 >> V5.1

>> V5.2 >> V7.0. Before you upgrade the IMC Platform, download upgrade packages for all

deployed service components from HP's website, and before you install them pay special

attention to the section "Platform Compatibility" in their readme. If an upgrade package is not

available for a service component, HP recommends not upgrading the IMC Platform, or you can

remove the service component before upgrading the IMC Platform. When the service component

is removed, its data is lost. It is not possible to import the database taken from a previous version

into V7.1. The following lists all features released after IMC PLAT 7.0 (E0102).

Features released in IMC PLAT 7.1 (E0302)

Baseline software audit supports ComwareV7 devices using the IPE software package.

Automatically deletes devices that are unreachable for a given period of time from iMC.

Supports centrally performing compliance check for devices across multiple RSMs.

Modifies the information display mode of the error information for report script

executions on the login page.

Cancels the limit on the number of exported alarms. Supports creating more tabs in the

exported excel file, with each tab containing up to 5000 rows.

Limits the URL length to 128 characters in Service Monitoring of Performance

Management.

Supports the backup and restore function for Juniper SRX650 devices in ICC.

Enhances the IP address management function by displaying IP address segment statistics

and displaying idle IPs in each IP address segment.

Supports sorting and searching capabilities for the lists on some network element

information pages, for example, the IP route pages.

Displays the custom view list in a tree, and sorts the custom views by name by default.

Reads the private MIB of an MSM device to get and show its sysuptime.

Supports using SCP to deploy configurations to Cisco 2960 /3750 switches.

Supports writing the operation logs to the imcforeground.log file. Users can

disable/enable this feature in IMC system settings. This feature is enabled by default.

Supports firmware upgrade for stacked Cisco 2960s devices.

Allows an operator to use the full name (which can contain characters other than ASCII

characters) to log in to IMC and shows the full name in the top right corner of IMC page

after the login succeeds.

Supports copying customized homepages and my favorites.

Supports importing a file to batch modify device labels on the Resource >

Import/Export Device page.

Supports showing power supply and fan status in device panel view for devices that can

provide related info in the MIBs.

Supports showing device label (alias name) and IP info in the device panel view for

10500 and 3800 devices.

Supports using SCP to back up configuration files for Cisco 7606 devices.

Improves the topology link labels as follows: sets different background colors for

different link labels; keeps the link label direction the same as the link direction; supports

displaying abbreviated interface names for interface names in link labels.

Adds the sysLocation as an optional parameter for customizing the alarm forwarding

format.

Displays the device type names on the Y-Axis of the Device View widget on the IMC

homepage.

Automatically sets the heap size for JServer according to the total physical memory size

of the IMC server during the IMC installation process.

Supports manually drawing curve links in the topology.

Supports disabling/enabling MSTP info gathering for L2 topologies.

Allows using hyphens (-), underscores (_), pluses (+) and spaces ( ) in VLAN

descriptions.

Shows links between Cisco switches correctly when the interfaces are configured as

channel trunk.

Supports HTML5 dashboards.

ICC uses only CLI rather than template to perform compliance checks. It will not be

affected by TFTP or SFTP.

Supports reading data in timeticket format from the MIBs.

Uses CLI to deploy Quickfix for compliance check, and supports Quickfix for HP

devices.

Shows the hard disk sizes of the virtual machines on the Web interfaces.

Shows the local storage information of the virtual machines on the Web interfaces.

Shows the link between the VM and the storage when the virtual host is open in the

virtual network topology.

Provides new dashboard widgets to show the VM performance.

Performs the privilege check for switches connected to VMs before VM migration.

Supports forwarding syslogs and traps to ArcSight by using the filter tools.

Optimizes ICC prompts.

Implements 3D datacenters by using WebGL 3D.

Adds a new theme named Sky Blue as the default theme.

Supports SQL Server 2014.

Combines HA with DBMAN to provide HA deployments for IMC and databases.

When a viewer with only the permission to the custom topology logs in to IMC and

views the topology, the topology does not provide the right-click shortcut menus, tool

bar, and tips.

Adds the function of collaborating with Microsoft SCOM and forwarding alarms in IMC

to SCOM.

Supports forwarding SMS through email.

Features released in IMC PLAT 7.0 (E0202H04)

None

Features released in IMC PLAT 7.0 (E0202P03)

Performance Management o Editing and copying custom indexes on the Resource > Performance

Management > Global Index Settings page.

o Modifying the real-time monitoring interval on the Resource > Performance

Management > Real-Time Monitoring page.

o The Alarm Statistics SMS Configuration feature is added to the System > System

Settings page.

Features released in IMC PLAT 7.0 (E0202L02)

Basic System Management o Provides unified SMSC settings in System > System Configuration > SMSC

Settings, which support the H3C SMSC platform and the third-party SMSC

platforms.

o Adds the dashboard feature in My Favorites menu.

Resource Management o Displays 3D device panels for HP devices.

Topology o Adds the converged topology feature in Resource > Topology.


None


Basic System Management o The IMC platform supports IPv6 devices, limited to only H3C devices and HP-A

series devices.

Resource Management o When you create a custom view, you can specify the device model, sysname,

sysContact, and syslocation fields as the auto grouping criteria on Resource >

Custom View > Add View page.

o When IMC detects that a link aggregation group member ports goes down, IMC

generates alarms and displays the status for the corresponding link in the

topology.

o Supports encrypting the exported files on Resource > Import/Export Device

page.

o Adds the LiveUpdate option to the device view, custom view, IP view, and auto-

discovered device list on Resource > Device View page, click More button.

o Implements the traceroute function, the entry of which is in the shortcut menu of

the topology, for devices and displays the traceroute path on IMC.

Topology o Supports importing custom views through a .txt file on Resource > Custom View

> Add View, where you can specify the names and IP address segments for

custom views.

o Provides the entry to the Real-Time Monitoring function on the custom topology,

the IP topology, and the device details page.

o Adds the Deploy Configuration menu item to the shortcut menu of the topology.

o The custom topology, IP topology, neighbor topology, stack topology, path

topology, and VLAN topology support the HTML5 topology.

Alarm Management o Supports configuring the filtering rules on Filtering Trap > Add Filtering Rule

page, upgrade rules on Trap to Alarm > Add Alarm Generation Settings page,

and forward rules on Alarm Notification > Add Mail Notification / Add

Message Notification / Add Alarm Forwarding page by custom device view in

the alarm module.

o Adds the link for modifying performance thresholds on the alarm details page.

o Adds the flashoff alarm filtering function on Alarm > Filtering Trap >

Intermittent Trap Analyze Configuration page.

Configuration Center

o Supports the Auto Deployment Plan (ADP) report on Report > Report Template

List page.

o Supports configuring an auto backup plan by custom view on Service > Auto

Backup Plan > Add Auto Backup Plan page.

o Displays the number of unqualified devices above the table on the Deploy Device

Configuration page.

o Adds the policy option for configuration deployment on the recovery wizard for

compliance check.

o Supports querying compliance check tasks on the Service > Check Task page.

o Deletes the function of restoring the device configuration to the running

configuration.

o iCC supports upgrading Cisco devices through tar files.

o iCC can storage readme files of the device software from LiveUpdate, displayed

on Service > Software Library page.

Terminal Access o The IP address management module supports detecting and batch releasing idle

IPs on Resource > IP Address Allocation page.

o The IP address management module supports exporting IP addresses into an excel

file on Resource > IP Address Allocation page.

VLAN Management o Supports obtaining VLAN names through standard MIBs.

o Supports automatically deploying VLANs to all devices on a path in HTML5

topologies.

Virtual Resource Management o VNM supports VMware and Hyper-V VM management, which allows you to

clone VMs, convert VMs into templates, clone VMs as templates, modify VM

configurations, and delete VMs.

o VNM supports VMware and Hyper-V VM power operations, including turning on

the power, turning off the power, resetting, suspending, resuming, shutting down

the operating system, and restarting the operating system.

o VNM supports VMware and Hyper-V VM template management, which allows

you to add, delete, delete, clone, and deploy VM templates.

o VRM supports Xen management to create virtual machines based on templates,

and provides the function of adding, deleting, starting, and stopping virtual

machines.

Device Panel o Adds the power management function for HP 640 devices in the network

management essential module.

Others o Supports checking the database connectivity before upgrading a component.

o Supports using SSL/TLS to encrypt the communication with the LDAP server on

System > Authentication Server page.

o Supports displaying the CPU, memory, disk, and database usage for the servers

on System > iMC Server Info page.

o DBMan generates alarm when errors occur during the database backup,

restoration, and transmission procedures.

o DBMan supports centralized management. To implement centralized

management, a user must configure the database backup/restoration policy after

upgrading DBMan.

o By default, server logs are kept for 30 days.

o Changes to the alarm sound settings take effect immediately and do not require a

jserver reboot.

o Remove the external tool settings for SSH/SFTP client.

o When you load MIB files in the MIB browser, you can select whether to save the

loaded MIB files.

o Removes the External tool setting option from System Settings.

Features released in IMC PLAT 7.0 (E0102P05)

ACL Management o ACL Management supports Cisco 3750 and Cisco 2950 device.

VLAN Management o VLAN Management supports configuring VLAN virtual interface for Cisco

devices.


None


Alarm Management o The name of the Device Not Accessible alarm is modified into The device does

not respond to poll packet.

Performance Management o When no performance data is collected, the performance monitoring charts can

have breaks or display the data in smooth lines. By default, the charts allow

breaks.

Virtual Network Management o VNM allows you to create VMs based on templates in VMware, and it also

allows you to delete, start, stop, and pause VMs.

Others o The number of digits allowed for the country code is expanded to 12 in the SMSC

configuration.


Resource o Supports exporting sensitive data in cipher text when exporting the device files.

o Adds the LiveUpdate option to the device view, custom view, IP view, and auto-

discovered device list.

Topology

o Adds the Deploy configuration item to the shortcut menu of the topology.

Terminal Access (Enterprise and Standard versions only) o Terminal access support IP recycle bin, IP address importing, and IP address

exporting.

o Adds the Host Name field to the IP addresses scanning function.

o Adds the idle IP detection function.

Alarm Management o After an interface down alarm is manually recovered, interface down alarms are

not generated until the next interface down event occurs.

Compliance Center o Adds the policy option for configuration deployment on the repair wizard for

compliance check.

Others o Supports HP 501 Wireless Client Bridge.

o Provides the Select All and Deselect All function when you set the operation

privileges for operator groups.


Resource o Supports using the device additional information as the query criterion for the

advanced device search.

Topology o Supports the VEPA topology, which displays the EVB vPort topology from the

virtual network topology.

Terminal Access (Enterprise and Standard versions only) o Supports searching IP addresses through exact match in IP Address Allocation.

Alarm Management o Supports querying alarms at the selected alarm level and higher levels for real-

time alarms and root alarms.

o Supports PSU and RPS traps of ProCurve devices.

Performance Management o Performance management support VLAN interface for QoS matching rate.

Network Asset Management o Adds the following property fields to Network Assets: Serial Number, Service

Time, Maintenance Expiration Date, Department, Location, and Maintainer

Contact Info, all of which can be manually modified.

o Supports customizing columns for the Network Asset List.

o Supports exporting the Network Asset List into a CSV file, which contains the

columns displayed and not displayed in the list.

ACL Management o Support 40GE interface for ACL package filter.

VNM (Enterprise and Standard versions only) o Supports HP distributed vSwitch management, which allows you to add, delete,

modify, and query HP distributed vSwitches.

o Supports performance monitoring for XenServer VM.

Others o Supports Aruba devices for basic monitor and ICC.

o Supports HP TippingPoint Next Generation Firewalls for basic monitor.

o Supports back slashes (\) and forward slashes (/) in SSH usernames.


Basic System Management o Provides four new Web page themes.

o Provides the general search feature, which can search various data files in the

IMC system, including help and navigation.

o MIB management tool, which can export the MIB walk query results into a text

file.

o Supports centrally configuring the data access privileges for operator groups.

o The data lists, such as device view, interface view, and operation log, support

generating real-time charts based on the data of the lists.

o Displays the iAR license information on the About HP Intelligent Management

Center box.

Resource o Supports the MDC feature, including identifying MDCs, creating MDCs, and

assigning resources for MDCs.

o Supports the VCF feature, including identifying VCF devices, displaying the PE

license information on the About box, VCF topology, and VCF assets.

o Supports the auto discovery (advanced) function, which can filter devices by

device model.

o Polls the service monitoring information when polling devices.

o Supports specifying the custom view name for each device in the .csv file when

importing devices. If the specified custom view name does not exist, it is

automatically created.

o Performance, alarm, syslog, and VLAN management modules do not poll

unmanaged devices.

o Supports creating a daily scheduled interface configuration plan for the batch

operation of configuring interfaces.

Topology o Supports customizing the icon for a single device in the custom topology.

o Supports displaying and saving GEO information for a device in the topology.

o Supports adding a room label to the data center topology.

o Supports displaying the abbreviated interface names for the links in the topology.

o Supports keeping the cloud colors consistent with the status colors of the specified

topology types (for example, IP topology and custom topology).

o The IP topology and custom topology do not need Java Applet when a browser

supporting HTML5 is used to access IMC.

Device Panel o Supports HP zl modules.

o Supports ONE Service modules.

Terminal Access (Enterprise and Standard versions only)

o Displays network segments of unassigned IP addresses.

Alarm Management o Allows you to delete, acknowledge, or recover all alarms on the System >

Process All Alarms page.

o Allows you to add interface descriptions or interface aliases to the trap

description. (Whether to use interface descriptions or interface aliases is

configured in the system parameters.)

o Allows you specify whether a trap parameter is an interface index. If the trap

parameter is configured as an interface index, the trap affects the topology link

status.

o Supports SNMP v2/v3 INFORM.

o In hierarchical IMC, recovering a trap also recovers the related trap in the upper-

level/lower-level IMC.

o Allows you to view all alarms of an interface on the interface details page.

o When an alarm is selected, its recovered alarm is automatically selected.

o The alarm panel does not need to use the Java Applet.

Performance o Supports collecting transmit/receive power statistics for transceiver modules.

o Supports modifying the name for a monitor instance.

o Provides a shortcut for configuring the threshold on the performance data page.

Configuration Center o OOBM supports backing up configurations for ProCurve devices.

o Supports upgrading software through ISSU for devices running Comware V7.

o Supports upgrading software through SCP for ProCurve devices.

o Allows you to copy system-defined compliance policies.

o Supports deleting compliance policies in batches during the process of creating a

compliance check task.

o Supports displaying only undeployed devices in the auto deployment plan.

VLAN Management o Identifies a VLAN by VLAN ID and VLAN name.

o Handles the VLAN names and interface aliases in the same way sysnames are

handled.

VNM (Enterprise and Standard versions only) o Supports XenServer.

o Supports HyperV2012 and VMM2012.

o Supports ESX5.1.

Report o Adds aggregate link information to the topology reports.

Others o Redesigns the IMC web page look and all icons.

o Supports the Chrome browser.

o Provides the management UI for mobile phones.

o Supports the following new operating systems: Windows Server 2012, RHEL 5.9,

and RHEL 6.4.

o Supports the new database MySQL 5.6.

o DBMAN generates an alarm to alert the user when it fails to transfer backup

database files through FTP.

o Adds the search platform (seplat) component, which can be deployed in

distributed mode to provide the indexing and searching capabilities for the general

search function of IMC.

[ Table of Contents ]

Problems Fixed in this Release

IMC PLAT 7.1 (E0302) fixes the following problems, including all bugs fixed after IMC PLAT

7.0 (E0102).

Resolved Problems in IMC PLAT 7.1 (E0302)

1. The "Server Errors" message might appear when you perform either of the following tasks: 1) Add custom indexes on the Resource > Global Index Settings page. 2) Query

indexes on the Resource > Global Index Settings page.

2. The Liveupdate feature failed.

Resolved Problems in IMC PLAT 7.0 (E0202H04)

1. The match mode fails to be modified and is still Greater than or equal after you perform the following tasks: on the Resource > Performance Management > Monitoring

Settings page, click Modify Index; enable Threshold 1, disable Threshold 2, and modify

the match mode from Greater than or equal to Less than or equal or Between; click

OK.

Resolved Problems in IMC PLAT 7.0 (E0202P03)

1. On the Copy Alarm Generation Settings page of a Trap to Alarm rule, traps are combined into one entry in the Trap Name list if they have the same Trap Name and Enterprise

Name.

2. On the IMC home page, the operator keeps clicking the Refresh buttons in the Lower-Level NMS Fault Statistic and Lower-Level NMS RealTime Fault areas.

3. The operation date/time of operation logs is incorrect when the logs are sent as Syslogs. 4. In IMC, pictures of 10500 device panels are incorrect. 5. When UAM or EAD is deployed, contents in DBMan configuration files are duplicated.

Database restoration fails.

6. You cannot open the converged topology as a viewer.

Resolved Problems in IMC PLAT 7.0 (E0202L02)

1. The security vulnerabilities ZDI-CAN-2312/1613/1661 are fixed.


1. The security vulnerabilities ZDI-CAN-2088/2089/2090 are fixed. 2. The RESTful API with the message content type application/json cannot be correctly

used.

3. On the 3800 device panel, the problem of failing to display the characters is fixed and the font size is modified.

4. In a report template with the End Time parameter, the default value of the End Time parameter is changed to End Time.

5. The link of a device is not calculated in the network topology when the other end of the link is a subinterface on a Juniper device or an aggregate interface on a Cisco device.

6. When you manually add new custom device models, these models are still displayed as Unknown SNMP Product after devices of these models are synchronized.

7. Some Windows Server 2003 servers fail to be added to IMC because the servers have not correctly implemented the IPv6 address MIB.

8. The alarms from some HP ProCurve devices are not defined in the MIB and the alarm OIDs are dynamically generated. As a result, IMC fails to recognize the alarms from

these devices.

9. When the interface performance index is monitored, the performance module might fail to be started if the devices return abnormal data.

10. When you install IMC that uses the Oracle database in the Linux operating system, the operation of using custom views to add backup configuration for auto backup plans does

not take effect.

11. The error data in the MIB tables of the HP MSM device configuration files is not immediately, automatically cleared. As a result, IMC might fail to back up the

configuration files for HP MSM devices.

12. HP devices fail to back up device configurations by transport type/login type. You must back up device configurations by login type.


1. IMC prompt that the license is invalid in the special linux server. 2. VLAN management isn't compatible with VLAN number 4095. 3. Traps starting with 1.3.6.1.4.1.11.2.14.11 cannot be configured to be sent through email. 4. A compliance task with the period being one day can be executed for only once. It is not

periodically executed as expected.

5. The IMC PLAT basic version cannot display sFlow traffic information. 6. Cannot back up the configuration files of Cisco AS5520 and AS5540 devices. 7. The plaintext password of the database user sa is displayed in the IMC logs. 8. The expiration of the license for SHM causes the IMC RESTful API to fail to start. 9. A non-English language environment variable might cause IMC licenses to become

invalid.

10. The system prompts that the server is busy when you create a custom view.

Resolved Problems in IMC PLAT 7.0 (E0102P05)

1. The information of the Recovery Status, Acknowledgment Status, Alarm at, Recovered At and Persisted Time columns is not completely displayed in the All

Alarms page by default.


1. After customize the columns for the all alarm list and select the Note column, the Note column is not displayed on the alarm list.

2. Click the Report button for a single performance instance in the summary data of the performance view, the report cannot be opened.

3. Log in to IMC as a viewer and access the performance threshold in alarm details page, privilege control is not enforced on the threshold modification function.


1. Failed to import software from the HP Comware devices. 2. Failed to backup configurations from Cisco AS5540 and AS5520, and redundant

configuration files were left in the device.

3. When an interface up alarm is received from a device, the interface status does not become up immediately.

4. When a large number of alarms exist, it takes a long time to open the Alarm Relation Report.

5. When you query the migration suggestions of VMs by time, an error page appears. 6. A prompt "Connection to the server disconnected. Check the connection and try again" is

displayed after the realtime performance monitoring runs for a while. Ignore the message

and click OK.

7. Configuring the interface UP/DOWN alarm filtering in batches failed. 8. The operation log list displays only the dates, but it does not display the accurate time. 9. The device group list page does support the filtering function. 10. When you customize the display columns for the custom view list and submit the

configuration, an error page occurs. The configuration takes effect after you log in again.


1. There is no Category-Based alarm information when put the mouse over the icon in Alarm Panel.


1. After a performance instance is obtained again, 1 is added to the original performance instance name.

2. When the software is upgraded for a Cisco device, the files in the same flash as the software image might be deleted.

3. When the software is upgraded for a Cisco device, the files in the same flash as the software image might be deleted.

4. Clicking the right menu in device details is invalid if going into the device details page from the faulty devices page.

5. Failed to configure trap level according to the device category in the trap definition page. 6. Failed to import software from Comware V7 devices when there is any software in the

IMC software library.

7. Cant start IMC after uninstall UAM/TAM. The log shows that there is no directory "conf/about".

8. Alarm daemon abnormally works when Access device is enabled and there are many interface UP/Down traps


1. In ICC, you may fail to restore a configuration file to running configuration. 2. When you add or delete an ESX server on a vCenter server, or an ESX server hardware

changes, the links between vSwitches and ESX servers in VNM Topology disappear. To

solve this problem, delete the vCenter server, add it to IMC again, and manually

synchronize ESX servers.

3. In VNM, if you click Refresh on the virtual machine performance monitoring page, the performance monitoring data for the virtual machine cannot be retrieved.

4. For Procurve 2520 and 4204vl, software upgrade via SFTP fails. 5. Fix root alarm calculation errors.


IMC Software Distribution Contents

The IMC PLAT 7.1 (E0302) distribution list contains the following files and folders:

1. manual\readme_plat_7.1 (E0302).html - This file 2. windows\install - IMC installation program 3. linux\install - IMC installation program for Red Hat Enterprise Linux


Installation Prerequisites

Server Requirements

The following are the minimum hardware and software requirements for running IMC on a PC

server:

Minimum hardware requirements

o Pentium 4 3.0 GHz processor

o 4 GB of RAM

o 50 GB hard disk space

Operating system (Versions marked X64 are recommended):

o Windows Server 2008 with Service Pack 2

o Windows Server 2008 X64 with Service Pack 2

o Windows Server 2008 R2 with Service Pack 1

o Windows Server 2012 with KB2836988

o Windows Server 2012 R2

o Red Hat Enterprise Linux 5.5 (Enterprise and Standard versions

only)

o Red Hat Enterprise Linux 5.5 X64 (Enterprise and Standard

versions only)

o Red Hat Enterprise Linux 5.9 (Enterprise and Standard versions

only)


versions only)


versions only)


versions only)

VMware:

o VMware Workstation 6.5.x

o VMware Workstation 9.0.x

o VMware ESX Server 4.x

o VMware ESX Server 5.x

Hyper-V:

o Windows Server 2008 R2 Hyper-V

o Windows Server 2012 Hyper-V

Database

o Microsoft SQL Server 2008 Service Pack 3 (Windows only)

o Microsoft SQL Server 2008 R2 Service Pack 2 (Windows only)

o Microsoft SQL Server 2012 Service Pack 2 (Windows only)

o Microsoft SQL Server 2014 (Windows only)

o Oracle 11g Release 1 (Linux only)

o Oracle 11g Release 2 (Linux only)

o MySQL Enterprise Server 5.5 (Linux and Windows) (Up to 1000

devices are supported)

o MySQL Enterprise Server 5.6 (Linux and Windows) (Up to 1000

devices are supported)

Note: 64-bit operating systems are recommended over 32-bit operating systems because of the

larger amount of available memory for applications.

Note: Optimal hardware requirements vary with scale, other management factors, and are

specific to each infrastructure. Please consult HP, or your local account teams and precise

requirements can be provided.

GSM modem (optional)

A GSM modem is required for forwarding alarm messages. The following models have been

tested to work with IMC. For more information about a specific GSM modem, see its product

manual.

WaveCom M2306B

WaveCom TS-WGC1 (Q2403A)

Wanxiang serial port GSM modem (DG-C1A)

Wanxiang USB GSM modem (DG-U1A)

Wanxiang USB min GSM modem (DG-MINI)

WaveCom M1206B GSM modem (chip: 24PL)

WaveCom USB M1206B GSM modem (chip: Q24PL, Q2403A)


Client Prerequisites

PC Requirements

Minimum hardware requirements

o 2.0 GHz processor

o 2048 MB of RAM

o 50 GB hard disk space

Operating system

o Windows XP SP3 or later

Browser

o IE 10 or 11 is recommended.

o Firefox 30 or later is recommended.

o Chrome 35 or later is recommended.

o Turn off the blocking settings in the browser.

o Add the IMC website to the trusted sites of the browser.

o The recommended resolution width is 1280.

o JRE 1.6.0_update27 or later is recommended. If a client has no

JRE, IMC prompts the user to install JRE for the client.


Installing and Upgrading IMC

To install IMC on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 or

Windows Server 2012 R2, first modify the user account control settings:

1. Open the Control Panel from the Start menu and click System and Security. 2. In the Action Center, click the Change User Account Control Settings link. 3. In the User Account Control Settings window, set the Choose when to be notified

about changes to your computer to Never notify.

To upgrade IMC:

1. Back up the IMC database on the Environment tab in the Deployment Monitoring Agent.

2. Manually copy the IMC installation directory to a backup path. 3. Stop IMC in the Deployment Monitoring Agent. 4. Click Install on the Monitor tab of the Deployment Monitoring Agent 5. Select the windows/install/components directory in the upgrade package and click OK. 6. Click OK in the popup message dialog box. 7. Click Start in the Upgrade Common Components dialog box to upgrade common

components.

8. After common components are upgraded, click Close.

9. In distributed deployment mode, stop the Deployment Monitoring Agent on the master server and restart the Deployment Monitoring Agent on every subordinate server. Click

Yes in the popup message dialog box to upgrade common components on every

subordinate server.

10. The Deployment Monitoring Agent displays all components that need to be upgraded. Click OK to start upgrading.

11. In distributed deployment mode, upgrade all components deployed on every subordinate server.

12. After all components are updated, start all processes in the Deployment Monitoring Agent.

For more information about installation and upgrade procedures, see IMC Getting Started Guide

and IMC deployment guides.

Important:

1. Before you upgrade the IMC Platform, download upgrade packages for all deployed service components from HP's website, and before you install them pay special attention

to the section "Platform Compatibility" in their readme. If an upgrade package is not

available for a service component, HP recommends not upgrading the IMC Platform, or

you can remove the service component before upgrading the IMC Platform. When the

service component is removed, its data is lost.

2. If the Deployment Monitoring Agent displays a list of components incompatible with the new version of the IMC Platform, you must download upgrade packages for these

components before you can continue the upgrade process.

3. All service components must use v7.0 or higher to work with IMC PLAT 7.0. After the IMC Platform is upgraded, upgrade the deployed service components, such as WSM,

UAM, EAD, NTA/UBA, APM, and SOM. Before installing or upgrading a service

component on this platform software, please verify the section "Platform Compatibility"

in the service components readme. Otherwise, IMC might not be started. For the

compatibility matrix, see readme files of the service components.

4. If you receive the message "Upgrade JVM failed..." during the upgrade process, delete the folder in the \common\jre directory of the IMC installation path and continue to

upgrade.

5. For data integrity, HP recommends backing up database on the Environment tab of the Deployment Monitoring Agent, and copying the IMC installation directory to a secure

location after the upgrade.


Removing IMC

To remove IMC on Windows, run the uninstallation wizard by selecting All Programs >

Intelligent Management Center > Uninstall IMC from the Start menu, or you can remove the

Intelligent Management Center in the Add or Remove Programs window of the Control Panel.

To remove IMC on Linux, enter the deploy directory of the IMC installation path by using the

cd command, and then execute uninstall.sh. IMC is typically installed in the /opt/iMC

directory.

Follow the directions in the uninstallation wizard, and manually delete all files in the IMC

directory when the process is complete.


Running the Deployment Monitoring Agent

The Deployment Monitoring Agent is a GUI program to manage the deployment of the IMC

modules and monitor the performance and the state of processes of the IMC server. After the

installation finished, the Deployment Monitoring Agent is automatically started to guide the user

through deployment.

On Windows, run the Deployment Monitoring Agent by selecting All Programs > Intelligent

Management Center > Deployment Monitoring Agent from the Start menu. On Linux, run the

Deployment Monitoring Agent by executing dma.sh in the deploy directory of the IMC

installation path.

If Deployment Monitoring Agent cannot start, make sure the HP IMC Server service is running.

This service is automatically started along with the OS and runs as a daemon/background

process. On Windows, you can start the service in Windows Services. On Linux, you can start

the service with the service imcdmsd start command.

IMC must be started from the Deployment Monitoring Agent.


Starting IMC

To start IMC, click Start IMC on the Monitor tab of the Deployment Monitoring Agent.


Logging in to IMC through a Web Browser

Once the server is running, you can access the IMC user interface using a Web browser. Enter

the following address in the Address Bar of a browser:

http://hostname:port/imc

Where hostname is the host name or IP address of the IMC server (the default is localhost if you

launch the Web browser on the IMC server machine), and port is the Web server port (the

default is 8080) used by IMC.

You can also access the IMC user interface with Web browser through HTTPS. Enter the

following address in the address bar of a browser:

https://hostname:port/imc

Where hostname is the host name or IP address of the IMC server (the default is localhost if you

launch the Web browser on the IMC server machine), and port is the Web server port for HTTPS

(the default is 8443) used by IMC.

When the IMC login page appears, use the username "admin" and password "admin" to log into

IMC.

Refer to the IMC Online Help for details on how to add operators, and add your devices to IMC.

The default security level in the IE properties is High. If you try to log in to IMC with this

default, the system will prompt "Content from the Web site listed below is being blocked by the

Internet Explorer Enhanced Security Configuration." Click Add to add the IMC website to the

trusted sites. If you do not add the IMC website to the trusted sites and determine not to display

the prompt any more, you may fail to log in to IMC. To solve the problem, use either of the

following methods:

1. Set the security level to Medium. o Start IE and select Tools > Internet Options.

o Select the Security tab, and then click Custom Level.

o In the popup dialog box, set the security level to Medium.

2. Add the website of the IMC server to the trusted sites. o Start IE and select Tools > Internet Options.

o Select the Security tab, Select Trusted sites, and the click Sites.

o Add the website of the IMC server in the popup dialog box.

On your first access to Resource > Network Topology, the browser prompts "The application's

digital signature cannot be verified. Do you want to run the application?" Below the prompt are

the name "topo", and the publisher "IMC Development Team". Select the "Always trust content

from this publisher" checkbox, and click Run.

Note: In centralized deployment, when the "User Access Manager - User SelfService"

component is deployed, you will enter the Self-Service login page rather than the IMC login page

if you enter http://hostname:port/ in the address bar. To enter the IMC login page, change the

string following window.location.href= into '/imc/login.jsf'; in the index.html file in directory

\client\web\apps\ROOT.


Monitoring the Server

On the Monitor tab of the Deployment Monitoring Agent, you can see the Disk Usage, CPU

Usage, and Physical Memory Usage of the IMC server. On the Process tab of the Deployment

Monitoring Agent, you can see all IMC processes and their running status. On the Environment

tab of the Deployment Monitoring Agent, you can see the OS information and database usage.

You can see the monitoring data of the IMC server only when IMC is started. For information

about starting IMC, see "Starting IMC".


Distributed Deployment

The IMC components can be installed on more than one server to meet specific performance

requirements. A distributed IMC system typically has one master server with IMC Platform

deployed and multiple subordinate servers with service components deployed.

To install IMC on a subordinate server, execute the installslave.bat file on Windows (or

installslave.sh on Linux) by either double-clicking the file or running the command in the folder

where installslave.bat (or installslave.sh) is located.

For information about deploying IMC in distributed mode, see IMC deployment guides.


Platform Specific Issues

Windows - General Issues

Please be especially careful about how filenames are capitalized and used. This is

essential in order to ensure consistent behavior across platforms that might use case-

sensitive file systems.

Linux - General Issues

The IMC server must be run from a root user account in order to receive SNMP traps,

accept syslog messages, and facilitate ftp file transfers.

UNIX filenames are case sensitive. Care must be taken when references are made to

python scripts and xml files.


Port Usage

IMC uses the following TCP/IP ports.

Component Subcomponent Protocol Port Configurable Use Server Client Notes

IMC

Platform - TCP 8025 No

Used by the

jserver process to

receive the

SHUTDOWN

command.

IMC

master

server.

IMC

master

server.

Internal

use.

IMC


JMX

monitoring

port used by

the jserver

process.

IMC

master

server.

IMC

master

server.

Internal

use.

IMC


Used by the

HP iMC

Server service

to receive the

SHUTDOWN

command.

IMC

master and

subordinate

servers.

IMC

master and

subordinate

servers.

Internal

use.

IMC


Used by the

Deployment

Monitoring

Agent process

to receive the

SHUTDOWN

command.

IMC

master and

subordinate

servers.

IMC

master and

subordinate

servers.

Internal

use.

IMC


Used for

communication

in a distributed

deployment

environment.

IMC

master

server.

IMC

master and

subordinate

servers.

Internal

use.

IMC


Used for

communication

between the

HP iMC

Server and

Deployment

Monitoring

Agent processes.

IMC

master and

subordinate

servers.

IMC

master and

subordinate

servers.

Internal

use.

IMC

Platform

Resource

Management UDP 161 No

Used to access

network

devices

through

SNMP.

Network

devices.

IMC

master and

subordinate

servers.

IMC

Platform

Resource

Management UDP 162 No

Used to receive

SNMP Traps

from network

devices.

IMC

master and

subordinate

servers.

Network

devices.

IMC

Platform

Resource

Management TCP 22 No

SSH/SFTP

port, which the

configuration

center uses to

back up and

restore the

device

software and

configuration

file through

SSH/SFTP.

Network

devices.

IMC

master and

subordinate

servers.

IMC

Platform ICC TCP 20/21 No

FTP port,

which the

configuration

center uses to

back up and

restore the

device

software and

configuration

file through

FTP.

Network

devices.

IMC

master and

subordinate

servers.

IMC

Platform

ACL


Telnet port,

which the

resource

management

module, ACL

management

module, and

configuration

center use to

access the

device through

Telnet.

Network

devices.

iMC

IMC

Platform

Alarm


SMTP port,

which the

resource

management

module uses to

send alarms

through email.

SMTP

Server

IMC

master and

subordinate

servers.

IMC

Platform

Resource

Management ICMP No

ICMP port,

which the

resource

management

module uses to

discover

devices and

check the

reachability of

the devices.

Network

devices.

IMC

master and

subordinate

servers.

IMC

Platform

Resource

Management UDP 69 Yes

IMC-specific

tftp daemon.

IMC

master and

subordinate

servers.

IMC

Platform

Resource

Management TCP 80 Yes

Used to launch

the Web

network

management

system of the

device.

Network

devices.

IMC

master and

subordinate

servers.

IMC

Platform

Virtual

Resource

Management

TCP 443 Yes

HTTPS port,

which the

virtual network

management

module uses to

obtain

VMware

virtual network

data in SSL.

IMC

master and

subordinate

servers.

IMC

Platform

Syslog

Management UDP 514/515 Yes

IMC-specific

syslog

daemon.

IMC

master and

subordinate

servers.

Network

devices.

IMC

Platform

Resource

Management TCP/UDP 137 No

NetBIOS name

resolution

service port,

used by the

IMC resource

management

module and

terminal access

module.

IMC

master and

subordinate

servers.

IMC

Platform - TCP 8080 Yes

IMC-specific

Web server for

HTTP

protocol,

which can be

changed during

installation.

IMC

master

server.

IMC


IMC-specific

Web server for

HTTPS

protocol,

which can be

changed during

installation.

IMC

master

server

IMC


IMC

messaging

gateway

listening port.

IMC

master and

subordinate

servers.

IMC

master and

subordinate

servers.

Internal

use.

IMC

Platform - TCP

21190-

21199 No

Java RMI

communication

port.

IMC

master and

subordinate

servers.

IMC

master and

subordinate

servers.

Internal

use.

IMC


SQL Server

database

listening port

(on Windows

only).

SQL

Server.

IMC

master and

subordinate

servers.

IMC


MySQL

database

listening port.

MySQL

Server.

IMC

master and

subordinate

servers.

IMC


Oracle

database

listening port

(on Linux

only).

Oracle

Server.

IMC

master and

subordinate

servers.

Note: On Linux, you must run IMC with root privileges to bind TCP/IP ports 69, 162, and 514.

Note: IMC cannot be bound to TCP/IP ports 69, 162, and 514 if they are used by other SNMP,

TFTP, or syslog applications.

Note: Make sure the firewall on each IMC server does not block programs javaw.exe and

java.exe. The programs are located in directory \common\jre\bin (/common/jre/bin/java for

Linux) of the IMC installation path.


Memory Allocation

The amount of memory allocated to the IMC jserver can be adjusted by a script. The memory

size should be tuned to make use of as much memory as required by your particular IMC server.

Move to the "client\bin" (or "client/bin" on Linux OS) sub-directory of the original IMC

installation directory (using the "cd" command), and use the setmem.bat (or setmem.sh on

Linux OS) script.

For example, to allocate 1024 MB RAM, move to the "installation directory\client\bin" (or

"installation directory/client/bin" on Linux OS) directory, and run the script:

setmem.bat 1024 (Windows OS)

setmem.sh 1024 (Linux OS)

The default and maximum memory that can be allocated to the IMC jserver is listed below:

OS Type Default allocatable memory Maximum allocatable memory

Windows 32-bit 512 MB 1024 MB

Windows 64-bit 2048 MB Depending on the physical memory

Linux 32-bit 512 MB 1280 MB

Linux 64-bit 2048 MB Depending on the physical memory


Known Problems

Installation/Upgrade/Patch

For a correct installation, the installation path can contain letters, digits, underlines, and

spaces, but cannot contain other special characters.

If the system installed with IMC has insufficient memory, java overflow might occur. To

prevent this issue, install IMC in a 64-bit OS with sufficient memory.

Other Problems

If the system is busy, the progress bar may be shown for a long time when you perform

an operation.

IMC does not support the PoE features of Comware V3 devices.

Configuration Center does not support the software upgrade of IRF devices through

SSH/SFTP.

Configuration Center does not support the software upgrade of old IRF2 devices or a

device with dual main boards.

If you configure a link aggregation across different units of IRF/IRF2 devices, the layer 2

topology cannot display the links because the master device cannot collect complete

information about links of the subordinate members. Ensure you configure link

aggregations only on the master device.

When you view the check result of a compliance check task, the system might display

"Do you want to abort the script?" if the check result contains too many devices and

policies. Click No to continue the operation.

A prompt "Connection to the server disconnected. Check the connection and try again" is

displayed after the realtime performance monitoring runs for a while. Ignore the message

and click OK.

If the device model is not correct for a third-party device, select System > Device Model

to edit the setting.

In an SNMP packet, the SNMP variables of the visible string type, the encoding mode

must be GBK or ASCII.

If you upgrade your IMC to IMC PLAT 7.0 (E0102), make sure you upgrade all

components after the upgrade package is installed. Otherwise, IMC cannot start.

The device locations might change on the Google map topology in windows of different

sizes or in full screen with different resolutions.

Discontinue monitoring the VM performance indices when the VM migrated to other

hypervisor.

If you cannot open the Applet topology after upgrading Java to the latest version for the

client, select Control Panel > Java > Security, and set the Security Level to Middle.

When you execute the backup.bat(.sh) script to back up IMC before upgrading IMC, only

files are backed up, but the database is not backed up.

In the dashboard, the realtime performance monitoring data for memory utilization is

displayed for CPU utilization.

In the converged topology, the status of a subview is always displayed as grey, which is

displayed based on alarms of the highest level on the devices in the subview.

The following problems occur to the 3D chassis in the data center: the added virtual

devices and trays cannot be displayed; the device locations in the 3D chassis are

incorrect; after you configure the chassis, the newly added devices can be displayed only

after the 3D chassis is reloaded.

In the Linux system, import device software fails when both IPv4 and IPv6 exist.

If IP addresses on two different network segments are configured on the IMC server, the

non-default initial configuration file fails to be downloaded when a device with zero

configurations is automatically deployed.

The SNMP test fails when the device location information is null.


Issued: September 2014

Copyright (c) 2010-2014 Hewlett-Packard Development Company, L.P. and its licensors.

HP IMC 7.1 Release Notes

Documents

Transcript of HP IMC 7.1 Release Notes