Imc - Hpe.com

Transcript

IMC Intelligent Management Center PLAT 7.0 (E0102L03) Copyright (c) 2013 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.0 (E0102L03) can be upgraded from IMC PLAT 7.0 (E0102), IMC PLAT 7.0 (E0102L01), or IMC PLAT 7.0 (E0102L02). Features released in IMC PLAT 7.0 (E0102L03)    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. Features released in IMC PLAT 7.0 (E0102L02)       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 autodiscovered 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. Features released in IMC PLAT 7.0 (E0102L01)       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 realtime 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. Features released in IMC PLAT 7.0 (E0102)    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 o o o o        Supports customizing the icon for a single device in the custom topology. Supports displaying and saving GEO information for a device in the topology. Supports adding a room label to the data center topology. Supports displaying the abbreviated interface names for the links in the topology. 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 upperlevel/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 o  Report  Others o o o o o o o o Supports HyperV2012 and VMM2012. Supports ESX5.1. Adds aggregate link information to the topology reports. Redesigns the IMC web page look and all icons. Supports the Chrome browser. Provides the management UI for mobile phones. Supports the following new operating systems: Windows Server 2012, RHEL 5.9, and RHEL 6.4. Supports the new database MySQL 5.6. DBMAN generates an alarm to alert the user when it fails to transfer backup database files through FTP. 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. Features released in IMC PLAT 5.2 (E0401H07) 1. The stacking topology supports the save function. Features released in IMC PLAT 5.2 (E0401L06) 1. Supports the virtualization product CAS. 2. NQA link alarms can affect the colors of links in the topology. Features released in IMC PLAT 5.2 (E0401P05) 1. Supports H3C devices attached to the HP MIB tree. 2. Adds the predefined CLI scripts for F5 devices in the configuration template library. 3. Supports collecting performance statistics of the Load Balance index for F5 devices. Features released in IMC PLAT 5.2 (E0401H04) 1. None. Features released in IMC PLAT 5.2 (E0401H03) 1. None. Features released in IMC PLAT 5.2 (E0401H02) 1. None. Features released in IMC PLAT 5.2 (E0401H01) 1. None. Features released in IMC PLAT 5.2 (E0401)    Basic System Management o The typical installation mode installs and deploys all subcomponents of the IMC Platform through a one-touch operation. o Downloads IMC updates directly from HP's website. o Diagnoses data gathering for devices and IMC. o Encrypts sensitive data (such as passwords) for storage. o Connects to remote databases with "forced encryption". o Option to present a custom banner at the login page to require acceptance of terms for before logging in. o Forwards IMC operator logs in syslog format to other systems. Resource o Independent discovery schedules for different network domains. o Displays interface duplex mode. o Displays performance data in port groups by customizing columns. o Supports the following devices: Cisco 1000v, Juniper EX4200, and F5 Big-IP Virtual Edition. Topology o Supports the ProCurve 3800 Stack topology. o Supports LLDP-MED topologies. o Analyzes topology integrity. o Supports the Ping Topology that displays reachability only. o All links in the Traffic Topology are divided into three areas, of which the middle area displays link status. o    Terminal Access (Enterprise and Standard versions only) o Generates IP Address Allocation alerts. o Import of IP address segments to the IP Segment List. Performance o sFlow analysis in Basic version. o The instance name "[:.0]" is changed to a more understandable name of "[Device]". o Displays Performance data in a widget on the IMC home page. o Customs the polling time of Traffic Topology. o Some new Performance indexes join to Traffic Topology. o Supports temperature monitor for Comware devices. o Provide a modification function based on Performance View, such as threshold value. Configuration Center o The devices' properties can be modified in an existing configuration or software deployment task. o Some devices can be filtered from the all in one auto-backup plan. o      Configuration History can keep up to 50 startup configuration files and 50 running configuration files for every device. o Does not check Flash for available memory while deploying software. o The option to backup the configuration after deploying CLI scripts. o Supports software backup between primary and secondary while deploying software for ProCurve devices. ACL Management o Supports Layer 2 ACLs on Cisco devices. Report o Port Group can be selected in reports. Security Control Center (Enterprise and Standard versions only) o Execution of recovery actions after a specific time period in SCC. o Dynamic devices set. o Discovers ports of edge devices automatically. o Policy execution history. Compliance management (Enterprise and Standard versions only) o Predefined compliance policies. o Sends alarms about non-compliant devices. VNM (Enterprise and Standard versions only) o Supports dvPortGroup management, includes creation, modification, and deletion. [ Table of Contents ] Problems Fixed in this Release IMC PLAT 7.0 (E0102L03) fixes the following problems, including all bugs fixed after IMC PLAT 5.2 (E0401). Resolved Problems in IMC PLAT 7.0 (E0102L03) 1. Failed to import software from the HP Comware devices. 2. When an interface up alarm is received from a device, the interface status does not become up immediately. 3. When a large number of alarms exist, it takes a long time to open the Alarm Relation Report. 4. When you query the migration suggestions of VMs by time, an error page appears. 5. 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. 6. Configuring the interface UP/DOWN alarm filtering in batches failed. 7. The operation log list displays only the dates, but it does not display the accurate time. 8. The device group list page does support the filtering function. 9. 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. Resolved Problems in IMC PLAT 7.0 (E0102L02) 1. There is no Category-Based alarm information when put the mouse over the icon in Alarm Panel. Resolved Problems in IMC PLAT 7.0 (E0102L01) 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 catagory 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. Can¡¯t 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 Resolved Problems in IMC PLAT 7.0 (E0102) 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. 6. In a non-English operating system, no operation result appears after you use the DBMAN to back up or restore the database. Resolved Problems in IMC PLAT 5.2 (E0401H07) 1. The SR6602-X1 device panel does not include any cards. 2. When the system includes more than 100 custom scheduled reports, the page is loading very slowly after the operator clicks Add My Scheduled Report on the My Reports page. 3. 3Com VoIP Media Gateway series devices report alarms for duplicate devices. Resolved Problems in IMC PLAT 5.2 (E0401L06) 1. If you use IMC platform version 5.2 and add more than 30 categories of devices to the platform, the OutOfMemory error occurs to the jserver process after you log in to IMC. Resolved Problems in IMC PLAT 5.2 (E0401P05) 1. An error might appear if you click Add to add new trap definitions immediately after a delete operation. 2. When the current software of a Cisco device has folders, you might fail to specify the main next-startup software for the device. 3. The Save File for parameter in the Data Export Settings does not take effect. Files that that are saved longer than the specified days are not deleted. 4. If an IMC SSH username contains a backward slash (\), the backward slash will disappear during the process of logging into a device. 5. When you log in to a ProCurve device at the CLI, if the device does not require you to press Enter for displaying the username prompt, IMC will fail to back up the configuration of the device. Resolved Problems in IMC PLAT 5.2 (E0401H04) 1. ZDI-CAN-1645: IMC uses the DES algorithm in ECB mode and static key to store sensitive data. Resolved Problems in IMC PLAT 5.2 (E0401H03) 1. Stop and restart all service monitoring instances, and then view the service monitor view. The system displays that no monitor device exists. Resolved Problems in IMC PLAT 5.2 (E0401H02) 1. To bulk modify threshold settings for performance monitor instances, you must select the basic measurement unit. 2. In SCC, you cannot configure a security control policy that contains a UAM action (such as Kick Off) and uses the alarm source as the object. 3. IMC no longer generates unreachable alarms if the operator manually cleared the previous unreachable alarms for a device in IMC and the device becomes unreachable again. 4. In auto discovery, the resource backend might not respond if the number of devices is large. Resolved Problems in IMC PLAT 5.2 (E0401H01) 1. On the page displaying all alarms, after you recover or acknowledge alarms, the set alarm level conditions will be cleared, and alarms of all levels are displayed. 2. When you enable the real-time monitoring feature and enable real-time monitoring in the display tiling feature, memory leak will occur to real-time monitoring. 3. If you have add or delete hosts in the vSphere client, after a polling interval or after the vCenter is manually synchronized in IMC, the link between the DVS symbol in the virtual network topology and its mirroring DVS symbol in the host is lost. 4. When you use the IMC performance manager to monitor the virtual machine performance data in the KVM host, you will fail to get the performance data of the virtual machine. 5. On the virtual machine attribute editing dialog box of the vSphere client, select the network which the virtual machine will access. If the access network switches between the vSwitch and the dvSwitch multiple times, the virtual machine might fail to connect to the vSwitch in the virtual network topology. 6. When you use the IMC virtual network manager to migrate the virtual machines in the KVM host, the system sometimes prompts that the virtual machine migration fails for the reason "An error occurred, but the cause is unknown." 7. In the LLDP-MED topology of a switch, the icon of an IP phone is displayed as that of a workstation by mistake. 8. When you enable inter-routing interface link calculation for Layer 2 topology, the processing result is opposite to the value set on the interface. 9. If there are multiple child groups with the same name in user groups, when you import users, you cannot select child groups with the same name in different parent groups. 10. After a super password is set for the SSH login method of a Cisco device, IMC cannot access the Cisco device at the CLI. 11. Supports CPU and memory performance monitoring for HP MSM devices. Resolved Problems in IMC PLAT 5.2 (E0401) 1. When the user is logged out because the IMC page times out and then the user logs in again, error pages occasionally occur to the performance-related widgets. 2. When viewing the Monitoring Settings-Instance List page and saving the monitoring instances to the existing performance view, you can select the Service Monitoring view. 3. Open the Real-Time Monitoring window on the device details page or interface details page. The current device or interface is not selected by default. 4. If the port group list page has been modified by customizing columns, an error message is displayed when you expand or collapse a port group. 5. An error page appears when none of the syslog levels is selected for an advanced query. 6. The ICC general configuration comparison page cannot save the filtered contents. 7. The Visual Panel Designer is undocumented. 8. Interface Last Change time is not updating correctly. [ Table of Contents ] IMC Software Distribution Contents The IMC PLAT 7.0 (E0102L03) distribution list contains the following files and folders: 1. manual\readme_plat_7.0 (E0102L03).html - This file 2. windows\install - IMC patch installation program for Windows 3. linux\install - IMC patch installation program for Red Hat Enterprise Linux [ Table of Contents ] 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 2003 with Service Pack 2 o Windows Server 2003 X64 with Service Pack 2 and KB942288 o Windows Server 2003 R2 with Service Pack 2 o Windows Server 2003 R2 X64 with Service Pack 2 with KB942288 o Windows Server 2008 with Service Pack 2 o Windows Server 2008 X64 with Service Pack 2 o Windows Server 2008 R2 X64 with Service Pack 1 o Windows Server 2012 X64 with KB2836988 o Red Hat Enterprise Linux 5 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 5 X64 (Enterprise and Standard versions only) 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) o Red Hat Enterprise Linux 5.9 X64 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 6.1 X64 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 6.4 X64 (Enterprise and Standard 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 2005 Service Pack 4 (Windows only) 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 1 (Windows only) o Oracle 11g Release 1 (Linux only) o Oracle 11g Release 2 (Linux only) o MySQL Enterprise Server 5.1 (Linux and Windows) (Up to 1000 devices are supported) 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) [ Table of Contents ] Client Prerequisites PC Requirements  Minimum hardware requirements o 1.5 GHz processor o 2048 MB of RAM o 50 GB hard disk space  Operating system o Windows XP SP3 or later  Browser o IE 9.0 or 10.0 is recommended. o Firefox 20 or later is recommended. o Chrome 26 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_update10 or later is recommended. If a client has no JRE, IMC prompts the user to install JRE for the client. [ Table of Contents ] Installing and Upgrading IMC To install IMC on Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012, 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. Stop IMC in the Deployment Monitoring Agent. 3. Click Install on the Monitor tab of the Deployment Monitoring Agent 4. Select the windows/install/components directory in the upgrade package and click OK. 5. Click OK in the popup message dialog box. 6. Click Start in the Upgrade Common Components dialog box to upgrade common components. 7. After common components are upgraded, click Close. 8. 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. 9. The Deployment Monitoring Agent displays all components that need to be upgraded. Click OK to start upgrading. 10. In distributed deployment mode, upgrade all components deployed on every subordinate server. 11. 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 Installation Guide. Important: 1. Before you upgrade the IMC Platform, download upgrade packages for all deployed service components from HP's website. 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. Make sure the version of service components matches the IMC Platform version. 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. [ Table of Contents ] 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. [ Table of Contents ] 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. [ Table of Contents ] Starting IMC To start IMC, click Start IMC on the Monitor tab of the Deployment Monitoring Agent. [ Table of Contents ] 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. [ Table of Contents ] 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". [ Table of Contents ] 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 Installation Guide. [ Table of Contents ] 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 casesensitive 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. [ Table of Contents ] Port Usage IMC uses the following TCP/IP ports. Port Usage TCP 8025 Used to receive SHUTDOWN command for the jserver process. TCP 9091 The JMX monitoring port used by the jserver process. TCP 9044 Used to receive SHUTDOWN command to the "HP IMC Server" service process. TCP 9055 Used to receive SHUTDOWN command to the "Deployment Monitoring Agent" process. TCP 61616 Used for communication in a distributed deployment environment. TCP 61626 Used for communication to the HP IMC Server and Deployment Monitoring Agent. UDP 161 Used to access network elements through SNMP. UDP 162 Used to accept SNMP Traps from network elements. TCP 22 SSH/SFTP port, which the configuration center uses to back up and restore the device software and configuration file through SSH/SFTP. TCP 20/21 FTP port, which the configuration center uses to back up and restore the device software and configuration file through FTP. TCP 23 Telnet port, which the resource management module, ACL management module, and configuration center use to access the device through Telnet. TCP 25 SMTP port, which the resource management module uses to send alarms through email. ICMP ICMP port, which the resource management module uses to discover devices and check the reachability of the devices. UDP 69 IMC-specific tftp daemon. TCP 80 Used to launch the Web network management system of the device. TCP 443 HTTPS port, which the virtual network management module uses to obtain VMware virtual network data in SSL. UDP 514/515 IMC-specific syslog daemon. TCP/UDP 137 NetBIOS name resolution service port, used by the IMC resource management module and terminal access module. TCP 8080 IMC-specific Web server for HTTP protocol, which can be changed during installation. TCP 8443 IMC-specific Web server for HTTPS protocol, which can be changed during installation. TCP 8800 IMC messaging gateway listening port. TCP 1433 SQL Server database listening port (on Windows only). 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. [ Table of Contents ] 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 allocable memory Maximum allocable 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 [ Table of Contents ] 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. The device locations might change on the Google map topology in windows of different sizes or in full screen with different resolutions. Fail to add the Syslog filter rule when there are more than 20 devices in this filter rule. Discontinue monitoring the VM performance indices when the VM migrated to other hypervisor. 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. [ Table of Contents ] Issued: November 2013 Copyright (c) 2013 Hewlett-Packard Development Company, L.P. and its licensors.