IMC. Table of Contents. What's New in this Release

Transcription

1 IMC Intelligent Management Center PLAT 5.0 SP1 (E0101P05) Copyright (c) 2011 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. IMC Upgrade Installation 7. Un-Installation 8. Running the Deployment Monitoring Agent 9. Running the IMC Server 10. Using IMC with a Web Browser 11. How to configure your network before deploying IMC 12. Monitoring the Server 13. Distributed Deployment 14. Platform Specific Issues 15. TCP Port Usage 16. Memory Allocation 17. Known Problems What's New in this Release IMC PLAT 5.0 SP1 (E0101P05) provides the following features: 1. Adds RSS feeds on the IMC homepage. 2. Adds port group under Resource > Port Group. 3. Adds traffic topology. To open such topology map, select Traffic Topology Index from the right-click menu of the custom topology. 4. Supports scheduled plans for automatic deployment. The feature is configurable under Service > Auto Deployment Plan. 5. Displays connections between hosts/virtual hosts and storage devices on the VNM topology. 6. Supports importing devices from HP NNMi The feature is configurable under Resource > Import/Export Device. 7. Supports building data center topology maps in batches. 8. Provides RMON statistics information in graphic charts. The feature is available under Device Details > RMON. 9. Adds parameter settings for alarm notification. The feature is configurable under Alarm > Alarm Notification. 10. Adds an up/down alarm filter on the interface list page. 11. Adds software baseline setting for device models. If different baselines are set for a device model and a particular device of that model, the baseline for the device model has a priority. The feature is configurable under Service > Software Library. 12. Supports setting the maximum number of backup configuration files. This field is configurable under Service > Configuration Center > Options. 13. Supports setting topology icons for different device models. This feature is configurable under System > Device Model.

2 14. Supports encrypting configuration files in icc. To encrypt configuration files, open the file under IMC installation path/server/conf/qvdm.conf, and delete the pound sign (#) before the parameter EncryptConfigFileFlag. 15. Supports importing IP addresses in batches in IP address allocation for terminal access control. The feature is configurable under Resource > IP Address Allocation. 16. Moves the Enable DismanPing setting from the topology setting to the system configuration. The item is available under System > System Settings. 17. Supports setting multiple labels for topology nodes and links. 18. Supports IRF topology management, and displays IRF member devices and their connections. 19. Allows modification of asset numbers. The feature is configurable under Resource > Network Asset Details. 20. Supports obtaining the terminal host names from DNS and DHCP servers for terminal access control. 21. Adds the configuration item Add VLAN to all Trunk/Hybrid/802.1q ports for adding a device to a VLAN topology. 22. Displays the managed ESX in a specific vcenter view in the VNM topology. Problems Fixed in this Release IMC PLAT 5.0 (E0101P05) fixed the following problems found in IMC PLAT 5.0 (E0101), IMC PLAT 5.0 (E0101L01), IMC PLAT 5.0 (E0101L02), IMC PLAT 5.0 (E0101H03) or IMC PLAT 5.0 (E0101H04): 1. Error occurred when you displayed the backup configuration file contents of VCX devices on the Device Details page. 2. Manually restore the database on the slave imc server while imc is running, it is possible that imc restarted while the database is being restored. 3. If parameter settings are configured in trap to alarm rule, the corresponding traps can t upgrade to alarm. 4. The help information for the trap definition parameters of $n, $+n, $# is not correct. 5. If no device interface was specified in a MAC-to-interface binding, this new binding would not appear on the terminal access binding list. 6. If the user password of the database SA contained ampersands (&), the DBMAN could not back up or restore the database. 7. If you executed a batch operation for more than 100 devices in a general task (such as Deploy Configuration, Restore Device Configuration, or Check Task), and most of these devices were not reachable, the jmcjobmgrdm process would occupy excessive memory, for example, more than 2 G, and finally the process would restart. 8. If you changed the SNMP template to SNMPv1/v2c for a device that was added by using the SNMPv3 template, the modification did not take effect, and IMC service modules continued using the SNMPv3 template to access the device. 9. After you modified the SNMP parameters for a device in IMC, the IMC configuration file management module continued using the original SNMP settings to access the device. 10. If an HP A-series device was running the Comware V5 B99 or a later version, IMC modules that mange devices through CLI (such as ACLM and MVM) could not work with the device. 11. Buffer overflow vulnerabilities occurred to the tftpserver, img, dbman and imcsyslogdm processes: ZDI-CAN-1010: IMC Remote Code Execution Vulnerability. ZDI-CAN-1011: IMC tftpserver WRQ Remote Code Execution Vulnerability. ZDI-CAN-1012: dbman sprintf Remote Code Execution Vulnerability. ZDI-CAN-1013: IMC tftpserver mode Remote Code Execution Vulnerability. ZDI-CAN-1014: IMC tftpserver DATA/ERROR Remote Code Execution Vulnerability. ZDI-CAN-1015: tftpserver opcode_table Remote Code Execution Vulnerability. ZDI-CAN-1028: IMC imcsyslogdm Remote Code Execution Vulnerability. 12. When you modified a user group, the system displayed that user groups could not be modified. 13. Incorrect available space was displayed during an IRF device upgrade with SFTP.

3 14. Modified the default SNMP template to SNMPv3, and then added devices that used the default template. If you changed the default SNMP template again, the system displayed that the user name already existed. 15. When you displayed information about an aggregate link on the IMC topologies, the member interfaces on the left were displayed as the right member interfaces and vice versa. 16. The home page was blank when you used a domain name that contained the string imc to access IMC. 17. Sometimes oversize database log files were created in SQL Server. 18. If the upgrade version had a different patch version number than the old version, the system would ask you to confirm whether to continue with the upgrade. IMC Software Distribution Contents The IMC CD/DVD ROM contains the following files and folders: 1. manual\readme_plat_5.0 SP1 (E0101P05).html this file 2. manual\hp IMC Getting Started Guide(IMC PLAT 5.0 SP1 (E0101P05)).pdf a PDF of the HP IMC Getting Started Guide 3. manual\hp IMC Installation Guide(IMC PLAT 5.0 SP1 (E0101P05)).pdf a PDF of the HP IMC Installation Guide 4. manual\hp IMC Base Platform Administrator Guide(IMC PLAT 5.0 SP1 (E0101P05)).pdf a PDF of the HP IMC Base Platform Administrator Guide 5. manual\sql Server 2005 Installation and Configuration Guide.pdf a PDF of the SQL Server 2005 Installation and Configuration Guide 6. manual\sql Server 2008 Installation and Configuration Guide.pdf a PDF of the SQL Server 2008 Installation and Configuration Guide 7. manual\sql Server 2008 R2 Installation and Configuration Guide.pdf a PDF of the SQL Server 2008 R2 Installation and Configuration Guide 8. manual\oracle 11g Installation and Configuration Guide.pdf a PDF of the Oracle 11g Installation and Configuration Guide for Linux 9. manual\oracle 11g R2 Installation and Configuration Guide.pdf a PDF of the Oracle 11g R2 Installation and Configuration Guide for Linux 10. manual\mysql 5.1 Installation and Configuration Guide(for Windows).pdf a PDF of the MySQL 5.1 Installation and Configuration Guide for Windows 11. manual\mysql 5.1 Installation and Configuration Guide(for Linux).pdf a PDF of the MySQL 5.1 Installation and Configuration Guide for Linux 12. windows\install the IMC patch installation program 13. linux\install the IMC patch installation program for Red Hat Enterprise Linux Installation Prerequisites PC Requirements The following are the minimum hardware and software requirements for running IMC on a PC server: Minimum hardware requirements Pentium GHz processor 4 GB of RAM

4 50 GB hard disk space Operating system (Versions marked X64 are recommended): Windows XP Service Pack 3 Windows Server 2003 with Service Pack 2 Windows Server 2003 X64 with Service Pack 2 and KB Windows Server 2003 R2 with Service Pack 2 Windows Server 2003 R2 X64 with Service Pack 2 with KB Windows Server 2008 with Service Pack 2 Windows Server 2008 X64 with Service Pack 2 Windows Server 2008 R2 X64 Windows 7 Windows 7 X64 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 5 X64 Red Hat Enterprise Linux 5.5 Red Hat Enterprise Linux 5.5 X64 VMware: VMware Workstation 6.5.x VMware ESX Server 4.x Hyper-V: Windows Server 2008 R2 Hyper-V Database Microsoft SQL Server 2005 Service Pack 3 (Windows only) Microsoft SQL Server 2008 Service Pack 2 (Windows only) Microsoft SQL Server 2008 Service Pack 2 (64-bit) (Windows 64-bit only) Microsoft SQL Server 2008 R2 (Windows only) Microsoft SQL Server 2008 R2 (64-bit) (Windows 64-bit only) Oracle 11g Release 1 (Linux only) Oracle 11g Release 2 (Linux only) Oracle 11g Release 2 (64-bit) (Linux only) MySQL Enterprise Server 5.1 (Linux and Windows) (Up to 1000 devices are supported) Note: 64-bit operating systems are recommended because the larger amount of memory is available for applications. Note: Optimal hardware requirements vary with scale, management factors, and networking infrastructure. For specific requirements, consult HP, or your local account teams. Client Prerequisites PC Requirements The following are the minimum hardware and software requirements for running IMC on a PC server: Minimum hardware requirements Pentium GHz processor 2 GB of RAM

5 50 GB hard disk space Operating system Windows Browser IE 8.0 or later is recommended Firefox 3.6 or later is recommended Turn off the blocking settings in the browser Add the IMC website to the trusted sites of the browser The client resolution is 1024*768 at least. JRE 1.6.0_update10 or later is recommended. If a client has no JRE, IMC provides the JRE installation program and asks users to install it. IMC Upgrade Installation This patch is available for IMC PLAT 5.0 (E0101), IMC PLAT 5.0 (E0101L01), IMC PLAT 5.0 (E0101L02), IMC PLAT 5.0 (E0101H03) and IMC PLAT 5.0 (E0101H04). If you are using the Enterprise edition and want to upgrade the NTA component, download the patch for NTA separately. To install IMC in Windows 7, Windows Server 2008 or Windows Server 2008 R2, you must first modify the User Account Control Settings. After installing IMC, you can restore the settings as needed. To modify the User Account Control Settings: click Start > Control Panel > System and Security, click the Change User Account Control Settings link in the Action Center to bring up the User Account Control Settings window. In the window, set the Choose when to be notified about changes to your computer to Never notify. Follow these instructions to upgrade IMC: 1. Back up the IMC database on the Environment tab in Intelligent Deployment Monitoring Agent. 2. Stop the IMC system in the Intelligent Deployment Monitoring Agent. 3. Click Install on the Monitor tab of the Intelligent Deployment Monitoring Agent. 4. Select the windows/install/components or linux/install/components subdirectory of the upgrade package, and click OK. 5. The installation wizard appears. Click Next. 6. Read the license agreement, select Accept, and click Next. 7. The installation wizard lists the common components that need to be upgraded. Click OK. 8. After the common components are upgraded, the Choose Target Folder window appears. Select the components that need to be upgraded as needed, and click Next. 9. Select a deployment and upgrade option as prompted by the Deployment and Upgrade Options window, and click Next. 10. Check the installation summary, and click Install. 11. After the installation is finished, select the components you want to upgrade in the Batch upgrade window, and then click OK. 12. After the selected components are upgraded, and click OK. 13. After the update is complete, start all processes in the Intelligent Deployment Monitoring Agent. 14. In a distributed deployment, upgrade components that are deployed on the slave servers separately. For more information about upgrading operations, see the IMC Getting Started Guide and IMC Installation Guide.

6 Note 1: If the message "Upgrade JVM failed..." appears during the upgrade process, take the following steps: 1. Delete the folder under "INSTALL_DIR\IMC\common\jre." 2. Install the service package again. Note 2: Patches cannot be undeployed. Un-Installation To un-install IMC, follow these steps: 1. Run the un-installation wizard. The method to run the un-installation wizard varies with operating systems. In Windows You can either click Start > All Programs > Intelligent Management Center > Uninstall IMC, or select to remove the Intelligent Management Center in Add or Remove Programs in Control Panel. In Linux Use the cd command to enter the deploy subdirectory of the IMC installation directory, and execute the uninstall.sh script. The default IMC installation directory is /opt/imc. 2. Follow the steps in the un-installation wizard to un-install IMC. The IMC un-installation procedure will not delete all files in the IMC directory. You can manually delete remaining files after the un-installation process is complete. Running the Intelligent Deployment Monitoring Agent The Intelligent Deployment Monitoring Agent is a GUI program to manage the IMC component deployment and monitor the IMC server performance and IMC processes status. After the installation is complete, the Intelligent Deployment Monitoring Agent automatically starts to guide users through component deployment. In Windows, log on to the system as an administrator, and click Start > All Programs > Intelligent Management Center > Deployment Monitoring Agent to run the Intelligent Deployment Monitoring Agent. In Linux, execute the dma.sh script in the deploy subdirectory of the IMC installation directory to run the Intelligent Deployment Monitoring Agent. If Intelligent Deployment Monitoring Agent fails to start, check the running status of the "HP IMC Server" service in the operating system. This service automatically starts when the operating system starts up and runs as a daemon. Make sure this service starts. In Linux, use the service imcdmsd start command to start the service. The IMC server will run only after you start IMC in the Intelligent Deployment Monitoring Agent (see the next section). Running the IMC Server To run the IMC server, click Start IMC in the Monitor tab of the Intelligent Deployment Monitoring Agent.

7 Using IMC with a Web Browser Once the IMC server is running, you can use a web browser to access the IMC configuration page. In the address bar enter the address in the following format: Where hostname is the host name or IP address of the IMC server (localhost by default if you launch the web browser on the host where IMC server resides), and port is the web server port (8080 by default) used by IMC. You can also access the IMC configuration page with web browser through HTTPS. In the address bar enter the address in the following format: Where hostname is the host name or IP address of the IMC server (localhost by default if you launch the web browser on the host where IMC server resides), and port is the web server port for HTTPS protocol (8443 by default) used by IMC. When the IMC login page appears, use the username admin and password admin to log in to IMC. See the IMC Online Help for more information about how to add operators and devices to IMC. The default security level in the IE properties is High. If you try to log in to IMC with this level, the system shows the message "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 set the IMC website as a trusted site and determine not to display the message 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. Launch IE and select Tools > Internet Options. Select the Security tab, and then click Custom Level. In the popup dialog box, set the security level to Medium. 2. Add the website of the IMC system to the trusted sites. Launch IE and select Tools > Internet Options. Select the Security tab, click Trusted sites, and the click Sites. Add the website of the IMC system in the dialog box. On your first access to IMC, the browser shows the message "The application's digital signature cannot be verified. Do you want to run the application?" Below are the name topo and the publisher IMC Development Team. Select the Always trust content from this publisher checkbox, and click Run. On your first access to the realtime performance view, the system asks you to install Adobe Flash Player Installer. Click Install to download the installation package and install the application. Without this application, the realtime performance view is not available. Note: When the "User Access Manager - User SelfService" component is deployed in centralized mode, entering in the address bar brings up the Self-Service login page. To enter the IMC platform login page with this address, go to the directory "\client\web\apps\root", and change the content of the index.jsp file to <% response.sendredirect("/imc/index.jsp"); %>.

8 How to Configure Your Network Before Deploying IMC Before deploying IMC, check all devices as follows: All devices can respond to ping requests (ICMP echo requests). SNMP read and write access is correctly configured. If not, the auto-discovery will add devices as PCs to IMC. Enable LLDP, CDP, and NDP for best results in topology. Avoid transparent STP BPDU transmission in a network. More specifically, if you enable STP in the network, do not connect two STP-enabled devices with one that does not support STP but can forward STP BPDUs. All devices allow ICMP packets sourced from non-existing IP addresses. All devices must be discovered via SNMP for IMC to build the correct topology. If ACLs are configured on a device, make sure that the ACLs permit packets from and to IMC. Installing the latest device software is recommended. IMC must be configured with the following settings: SNMP read and write access matching the device. Telnet and SSH for device configuration backup and other operations. Auto-discovery for devices to use IMC address for notifications. Auto-discovery to run daily or weekly, if dynamic updates are required. Install a telnet client on the host if IMC is running the Windows 2008 or Windows XP. These Windows editions do not come with a native telnet client. Enable the telnet service if IMC is running on a Linux operation system. If a device is discovered as an Unknown SNMP device, the device classification can be modified by changing the device vendor, model and type in IMC's System tab. Monitoring the Server The Monitor tab of the Intelligent Deployment Monitoring Agent displays the disk usage, CPU usage and physical memory usage of the IMC server. The Process tab displays all IMC processes and their running states. The Environment tab displays the operating system information and database usage. The monitoring data is available only after the IMC server starts. For more information about how to start the IMC server, see the section "Running the IMC Server." Distributed Deployment The IMC modules can be installed on more than one server to meet specific performance requirements. A typical scenario is that the system has one master server with the IMC platform deployed and multiple slave servers with other modules deployed. To install IMC on a slave server, double-click the installslave.bat file in Windows or run the installslave.sh script in Linux in the folder where the file or script is located.

9 For more information about distributed deployment, see the IMC Installation Guide. 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 which may have case sensitive file systems. LINUX General Issues The IMC server must be run by a root account so that the server can receive SNMP traps, accept syslog messages, and facilitate FTP file transfer. UNIX file names are case sensitive. Care must be taken when references are made to python scripts and xml files. TCP Port Usage The IMC server will bind to and use 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 Used for communication in a Master-Slave deployment environment TCP 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. SSH/SFTP port, which the configuration center uses to back up and restore the device software and TCP 22 configuration file through SSH/SFTP. TCP 20/21 TCP 23 TCP 25 ICMP UDP 69 FTP port, which the configuration center uses to back up and restore the device software and configuration file through FTP. Telnet port, which the resource management module, ACL management module, and configuration center use to access the device through Telnet. SMTP port, which the resource management module uses to send alarms through . ICMP port, which the resource management module uses to discover devices and check the reachability of the devices. IMC-specific tftp daemon.

10 TCP 80 TCP 443 UDP 514/515 TCP/UDP 137 Used to launch the web network management system of the device. HTTPS port, which the virtual network management module uses to obtain VMware virtual network data in SSL. IMC-specific syslog daemon. 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 (can be changed when installation). TCP 8443 IMC-specific web server for HTTPS protocol (can be changed when installation). TCP 8800 imf listening port. TCP 1433 SQL Server database listening port (Windows only). Note: In Linux, the IMC server must be run with root privileges to be bound to the TCP/IP ports (69, 162, 514). Note: The IMC server might not be able to bind to the TCP/IP ports (69, 162, 514) if other SNMP, TFTP or syslog applications are running and accessing them. 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 full use of memory as required by your particular IMC server. In Windows, enter the client\bin subdirectory and execute the setmen.bat file; or in Linux, use the cd command to enter the client/bin subdirectory of the IMC installation directory and execute the setmen.sh script. For example, to allocate 1024 MB RAM, enter the installation directory\client\bin (or installation directory/client/bin in Linux) directory, and run the script: setmem.bat 1024 setmem.sh 1024 (in Windows) (in Linux) 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 Up to the physical memory Linux 32-bit 512 MB 1280 MB Linux 64-bit 2048 MB Up to the physical memory Known Problems Installation/Upgrade/Patch

11 The installation path can contain letters, digits, underlines, and spaces. In Linux, the Oracle SIDs must be consistent if you adopt a distributed deployment for IMC or install IMC and database separately. If the host where IMC is installed has insufficient memory, java overflow may occur. It is a good practice to install the IMC in a 64-bit operating system and add more memory. Other Problems A device has non-continuous performance monitoring line graph when it is offline or the device monitoring is suspended for a while. The exported report, however, displays a continuous line graph. No index unit is available in the performance gather data. If you trigger an operation when system is busy, you may wait for a long time. IMC does not support the PoE features of Comware V3 devices. Configuration Center does not support the software upgrade of IRF/IRF2 devices through SSH/SFTP. Configuration Center does not support the software upgrade of 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 slave members. Make sure you configure link aggregations only on the master device. After upgrading your IMC to IMC PLAT 5.0 (E0101), if the alarm panel at the lower left of the interface shows an exclamation mark, select Start > Control Panel in Windows. Double-click Java, clear temporary Internet files, and log in to IMC again. When you upgrade your IMC to IMC PLAT 5.0 (E0101), make sure you upgrade all components after the upgrade package is installed, or IMC will no start. When you adjust the browser's window size, the page refreshes after 1 second, and restores to its initial state. For example, if you adjust the browser's window size before submitting any entered data, the window refreshes without saving the data. A message "Connection to the server disconnected. Check the connection and try again" appears after the realtime performance monitoring runs for a while. Click OK, and the page is closed. After you upgrade your IMC to IMC PLAT 5.0 (E0101), the room topology is changed from two dimensions to three dimensions, the rack positions might change, and the objects in the room topology might be lost. If you use the Topology Location function in the rack topology to locate the device in the IP Topology or My Network View, the location always points to the Data Center Topology. If you deploy IMC by using the non-default instance of the SQL Server database, and deploy the GAM component on the secondary server, the webserver process on the secondary server fails to start after you upgrade the GAM component to L01. If the device model is not correct for a third-party device, Select System > Device Model to edit the setting. When using Firefox 4.0 to operate in IMC, note the following guidelines: 1) Before importing or exporting devices, complete the NNMi configuration in System > System Settings. The values for the NNMi can be anything, and do not necessarily reflect the real networking parameters. 2) When multiple components are installed, the Device Details page cannot display all expanded menus on the right. To view those not displayed, collapse some menus on the upper part. Except Up and Down, other states on the interface list, like Block, are classified as unknown for the link status of the topology link information. In a non-english operating system, no operation result appears after you use the DBMAN to back up or restore the database. Restart IMC after IMC finishes calculating the topology of the IRF virtual device. If an IRF member device disappears unexpectedly from the topology and get discovered again, the links to this device are blue. Issued: May 2011 Copyright 2011 Hewlett-Packard Development Company, L.P.