IMC VAN Fabric Manager v7.0 (E0201) Copyright (c) 2013-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. VFM Software Distribution Contents 4. Installation Prerequisites 5. Client Prerequisites 6. Typical Installation 7. Upgrade 8. Removing VFM 9. Running the Deployment Monitoring Agent 10. Starting IMC 11. Logging in to IMC through a Web Browser 12. Monitoring the Server 13. Distributed Deployment 14. Platform Specific Issues 15. Port Usage 16. Memory Allocation 17. Known Problems What's New in this Release IMC VFM 7.0 (E0201) can be installed directly or upgraded from IMC VFM 7.0 (E0102) and IMC VFM 7.0 (E0103). IMC VFM provides the following features: Features released in IMC VFM 7.0 (E0201) FC Ping. FC Tracert. Set FC Ping Threshold. Configure Uplink-to-Downlink Interface Mapping of NPV switches. Disruptive Load Balancing of NPV switches. Add Fabric Comprehensive Report and Terminal Information Report.
Features released in IMC VFM 7.0 (E0103) None. Features released in IMC VFM 7.0 (E0102) At a Glance: This feature uses the pie charts and bar graphs to show the network device status, top 5 DCs by device quantity, SAN device view, fabric view, LAN topology, top 5 EVI services, top 5 migrations/24 hours, and top 5 EVI networks by VM migration delay for last week. VAN fabric topology: VAN fabric topologies include LAN topologies and SAN topologies. The LAN topology shows the network structure for all DCs in VFM, devices in each DC, links between devices, and links between DCs. Each DC provides a topology view for you to view the SPB network and the TRILL network. The SAN topology is organized by fabric, and it shows the network structure of each fabric. DC management: This feature manages the DCs and the ED devices, network devices, and servers in each DC. This function allows you to add, delete, and modify DCs. Also, this feature allows you to perform MAC location and auto discovery for DCs. SAN configuration: The SAN configuration function manages the fabric network, especially the Fiber Channel over Ethernet (FCoE) protocol, which carries FC over Ethernet. LAN configuration management: This feature manages the LAN configuration for the DC integration solution, including the TRILL configuration, SPB configuration, and EVI configuration. TRILL and SPB are tunneling techniques that connect devices in a DC at Layer 2. EVI is a tunneling technique that connects multiple DCs at Layer 2. Statistics: The statistics feature provides the ECT statistics chart and the VM migration information. Problems Fixed in This Release IMC VFM 7.0 (E0201) fixes the following problems. Resolved Problems in IMC VFM 7.0 (E0201) 1. When viewing the Terminal Information Report, the page prompts that you need to set parameters. In fact, you do not need to set parameters. 2. When adding EVI services, select a DC, select a server for the DC, and then delete the DC. An exception occurs on the page. 3. There is no data in the Fabric Comprehensive Report. 4. Delete a DC, and import devices into the DC on another browser. An exception occurs on the page.
Resolved Problems in IMC VFM 7.0 (E0103) 1. In Fabric details page, synchronizing the switch failed. 2. Modify the DCBX parameters, it shows success, but it failed in fact. Resolved Problems in IMC VFM 7.0 (E0102) 1. SPB services added through auto discovery cannot be automatically audited. 2. There is an exception of modifying fabric which contain switch. 3. Some of the SPB services can't audit by itself. IMC Software Distribution Contents The VFM software contains the following files and programs: 1. VFM\manual\readme_VFM_7.0 (E0201).html - This file 2. VFM\windows\install - the VFM installation program 3. VFM\linux\install - the VFM 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 server: Minimum hardware requirements o Pentium 4 3.0 GHz processor o 4 GB of RAM o 50 G 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 Oracle 11g Release 2 (64-bit) (Linux only) IMC Platform Compatibility o HP IMC Platform version: HP IMC PLAT 7.0 (E0202) or later 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. Client Prerequisites PC Requirements The following are the minimum hardware and software requirements for running IMC on a PC server: Minimum hardware requirements o 2.0 GHz Pentium 4 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. o Firefox 20 or later. o Chrome 26 or later. o Configure the browser to allow pop-up windows. o Add the VFM website to the trusted sites of the browser. o The minimum resolution is 1280x768. 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.
Typical Installation You can install IMC VFM 7.0 (E0201) directly. For more information about installation procedures, see IMC Deployment Guides. Upgrade The version can be upgraded from IMC VFM 7.0 (E0102) and IMC VFM 7.0 (E0103). Removing VFM You can remove VFM component through the Deployment Monitoring Agent. To do this, follow these steps: 1. In the Deployment Monitoring Agent window, click Stop IMC on the Monitor tab to stop all processes of IMC. 2. On the Deploy tab, right-click the VFM component, and select Uninstall the Component from the shortcut menu. 3. When an un-installation success dialog box appears, click OK. 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 IMC, the browser prompts "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 prompts you to install Adobe Flash Player Installer. Click Install to download the installer package and install the application. Without this application, the realtime performance view is not available. 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 content of the index.jsp file in directory \client\web\apps\root to <% response.sendredirect("/imc/index.jsp"); %>. 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 "Running the IMC Server." 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. 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. Port Usage IMC uses the following /IP ports. Port UDP 161 UDP Usage Used to access network elements through SNMP Used to accept SNMP Traps from network elements.
162 22 20/21 23 ICMP SSH/SFTP port, which the configuration center uses to back up and restore the device software and configuration file through SSH/SFTP. 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. ICMP port, which the resource management module uses to discover devices and check the reachability of the devices. UDP 69 IMC-specific TFTP daemon. 80 Used to launch the web network management system of the device. 443 8080 8443 8800 1433 UDP 6666 7668 HTTPS port, which the virtual network management module uses to obtain VMware virtual network data in SSL. IMC-specific Web server for HTTP protocol, which can be changed during installation. IMC-specific Web server for HTTPS protocol, which can be changed during installation. IMC listening port. SQL Server database listening port (on Windows only). inode location listening port. Used to manage HP Wireless device. Note: IMC cannot be bound to /IP ports 69, 162, and 514 if they are used by other SNMP, TFTP, or syslog applications. 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 setmem.sh 1024 (Windows OS) (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 Known Problems Installation/Upgrade/Patch The SPB auditing service feature determines the connectivity through querying the device link status database, and the auditing result does not represent the actual connectivity status. The links that are to be gradually deleted in the platform are still displayed in the VFM topology. Issued: Jan 2014 Copyright (c) 2013-2014 Hewlett-Packard Development Company, L.P. and its licensors.