IMC Network Traffic Analyzer 7.1 (E0301P04) Copyright (c) 2015 Hewlett-Packard Development Company, L.P. All Rights Reserved.

Transcription

1 Network Traffic Analyzer 7.1 (E0301P04) Copyright (c) 2015 Hewlett-Packard Development Company, L.P. All Rights Reserved. Table of Contents 1. What's New in this Release 2. Problems Fixed in this Release 3. Software Distribution Contents 4. Installation Prerequisites 5. Installing and Upgrading 6. Removing 7. Port Usage 8. Known Problems What's New in this Release 7.1 (E0301P04) can be upgraded from 7.1 (E0301), 7.1 (E0301H01), 7.1 (E0301H02) and 7.1 (E0301P03). The following lists all features released after 7.0 (E0101). Features released in 7.1 (E0301P04) 1. None. Features released in 7.1 (E0301P03) 1. Traffic distribution can be displayed for links on the custom topology map. 2. Lower-Level Traffic Analysis Server. Features released in 7.1 (E0301H02) 1. None. Features released in 7.1 (E0301H01) 1. None. Features released in 7.1 (E0301) 1. Supported the Web desktop. 2. Supported Cisco ASA 5510 firewalls.

2 3. Supported sflow packets with Layer 3 headers following the MPLS labels. 4. inter-business traffic analysis tasks support selecting interfaces or probes for collecting statistics. 5. Probes support RHEL 6.4 (64-bit). Features released in 7.0 (E0201P02) 1. Max. Link Utilization added for interface traffic analysis tasks. 2. Opens the report data sources o The data sources of traffic baseline data. Features released in 7.0 (E0201H01) 1. None. Features released in 7.0 (E0201) 1. Added the Interface flux report for an Interface Traffic Analysis Task. 2. Added the Single Interface Traffic Summary Report. 3. Added the feature of querying domain names through IP addresses. Features released in 7.0 (E0101P01) 1. The Statistics Direction option was added for configuring an inter-business traffic analysis task. 2. The business based on continuous address segments can be added for configuring an inter-business traffic analysis task. Features released in 7.0 (E0101) 1. The perspective graph feature is added to the source, destination, and session pages. 2. Automatically discovers the interfaces sending traffic. 3. The sequence arrangement feature is added to the task list on the task summary page. 4. Opens the report data sources o o The data sources of VPN traffic analysis tasks. The data sources of the 10-minute peak values and valley values of traffic analysis tasks. Problems Fixed in this Release 7.1 (E0301P04) fixes the following problems, including all bugs fixed after 7.0 (E0101).

3 Problems fixed in 7.1 (E0301P04) 1. An error page appears after one or more tasks are selected for the Application Traffic for Host Task (Last 1 Hour) widget on the imc home page. 2. Two operators concurrently edit the same custom topology in two browsers and both add links for interfaces that are monitored by an interface traffic task. After one operator finishes editing the links, the other operator clicks the pie chart and encounters an error page. 3. After is upgraded to E0301, all legacy scheduled reports become unavailable and HTTP 404 errors occur. 4. Although a host traffic analysis task has excluded an IP address range, excluded IP addresses might still appear as the source or destination hosts in traffic analysis. 5. Problems fixed in 7.1 (E0301P03) 1. The check box for selecting all tasks is ineffective on the host task setting page. 2. The system fails to load the single business report for an inter-business traffic analysis task when you switch back to this report from a single business details report. 3. The navigation bar disappears if you choose to display the Top 10 traffic report for unknown applications by source or destination port. 4. On the database space usage page, an operator selects Custom from the Time list, leaves the Start Time or End Time field empty, and clicks Query. Then a query error occurs. Problems fixed in 7.1 (E0301H02) 1. Interfaces of different devices cannot be added to an interface traffic analysis task when they use the same interface description and the same interface index. 2. A filter strategy includes a filter condition based on source and destination hosts, but cannot filter packets by both source and destination hosts. 3. interface threshold alarms display incomplete description information. Problems fixed in 7.1 (E0301H01) 1. When automatically discovers a large number of interfaces, the receiver messages are frequently updated. However, when you view the interface traffic analysis tasks, these tasks do not have traffic data. 2. If you do not input the query time for a traffic analysis task, an error page appears when you switch between tabs. Problems fixed in 7.1 (E0301)

4 1. This version does not support collaboration with Platform HTML 5 topology. 2. cannot obtain the IP address of an interface automatically discovered based on traffic, and the IP address of the interface sending traffic is recognized as the device IP address. 3. On the inter-business traffic analysis task traffic details page, the displayed information might be inaccurate and disordered. 4. On the host session summary page, if you select a secondary server, information about the primary server is displayed. Problems fixed in 7.0 (E0201P02) 1. A probe cannot be started if it is installed on an RHEL 5.X operating system. 2. When monitors interfaces of a large number of devices, data might be unable to be collected after the configuration is deployed. 3. No pivot chart can be added on the Source, Destination, and Session tabs of Traffic Analysis Task. 4. In distributed deployment where is deployed on multiple subordinate servers, the Sessions floating menu displays blank. 5. Baseline analysis and threshold alarming information is displayed incorrectly. Problems fixed in 7.0 (E0201H01) 1. The number of devices added cannot reach the number specified by the license. Problems fixed in 7.0 (E0201) 1. None. Problems fixed in 7.0 (E0101P01) 1. The probe is installed in the Linux RedHat 6.1 operating system, and the probe process is started. After the device mirrors traffic to the probe, the probe server restarts. 2. On the traffic analysis task summary page, you can select tasks that you do not have privilege to. 3. When the device sends NetStream V9 logs, cannot automatically discover the interfaces sending traffic. 4. When is deployed in distributed mode, the interfaces sending traffic which are automatically discovered on the primary server are incorrect. 5. On the host session number summary page, you cannot select a single host to view its trend graph. 6. On the traffic analysis task management page, the total number of tasks displayed is incorrect. 7. When the data size is large, the task of automatically deleting the expired logs fails, and the SQLSERVER log quickly grows to a maximum value. 8. The listening port deployed to sflow devices is always 9021.

5 9. On the session tab of an interface traffic analysis task page, click the pie chart. The system prompts a server error. 10. When you add a VLAN, probe, or host traffic analysis task, the devices or probes on secondary servers cannot be selected. 11. When you set the probe traffic analysis task parameters on the home page, the system prompts a server error. 12. If is upgraded to V7 when a device not configured in sends traffic to the server, traffic analysis tasks might fail to display data. Problems fixed in 7.0 (E0101) 1. Deploy in distributed mode with a separate database. The master server uses the database on the subordinate server, and the subordinate server uses the database on the master In this case, the database on the master server will be mistaken as the shared database. 2. When is deployed in distributed mode or deployed with a separate database, if you view the device interface traffic summary report or device application summary report in the reporting module, prompts that errors occur to searching the JNDI names. Software Distribution Contents The 7.1 (E0301P04) distribution list contains the following files and folders: 1. \manual\readme_nta_7.1 (E0301P04).html - this file 2. \probe - the probe installation program 3. \windows\install - the installation program for Windows OS 4. \linux\install - the installation program for Linux OS Installation Prerequisites Server Requirements The following are the minimum hardware and software requirements for running on a server: Platform Compatibility o Platform version: PLAT 7.1 (E0303) or later

6 Hardware o 3.0Ghz dual core CPU 2 or more o 6GB RAM or higher o 720GB of free hard disk space or higher Operating system 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 KB o Windows Server 2012 R2 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 2008 Service Pack 3 (Windows only)

7 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 Enterprise versions Release 1 (Linux only) o Oracle 11g Enterprise versions 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) Installing and Upgrading To install : 1. Before installing, make sure that the platform is installed correctly and the platform version is PLAT 7.1 (E0301) or later. 2. To install, click Install button on the Monitor tab of the Intelligent Deployment Monitoring Agent, then select the components sub-directory of the upgrade package, and click OK button to launch the installation wizard. To upgrade : 1. Back up the database on the Environment tab in Deployment Monitoring Agent. 2. Stop the system in the Deployment Monitoring Agent. 3. Click Install on the Monitor tab of the Deployment Monitoring Agent. 4. Select the install/components subdirectory of the upgrade package, and click OK. 5. After the installation is complete, the Intelligent Deployment Monitoring Agent lists the components that need to be upgraded. Click OK to start upgrading the components. 6. If this is a distributed deployment, upgrade the components deployed on the slave servers separately. 7. After the upgrade is complete, start all processes in the Intelligent Deployment Monitoring Agent window. For more information about installation and upgrade procedures, see Getting Started Guide and deployment guides.

8 Removing You can remove the component through the intelligent deployment monitoring agent. To do this, follow these steps: 1. In the Intelligent Deployment Monitoring Agent window, click Stop on the Monitor tab to stop all processes of. 2. On the Deploy tab, right-click the component, and select Uninstall the Component from the shortcut menu. 3. When an un-installation success dialog box appears, click OK. Port Usage uses the following TCP/IP ports. Component Subcomponent Protocol Port Configurable Use Server Client Notes - TCP 8051 No - TCP 9099 No - UDP No - UDP No Used by the unbaserver process to receive the SHUTDOWN command. JMX monitoring port used by the unbaserver process. Used by the jserver process and receiver process to communicate. Used by the jserver process and processor process to communicate. master master master master Internal use. Internal use. Internal use. Internal use. - UDP No Used by the Internal

9 Component Subcomponent Protocol Port Configurable Use Server Client Notes - UDP 9020 No - UDP 9021 No - UDP 6343 No jserver process and unbaserver process to communicate. Used to receive network packet. Used to receive network packet. Used to receive network packet. master Network devices. - Network devices. - Network devices. - use. Known Problems For a correct installation, the installation path can contain letters, digits, underlines, and spaces, but cannot other special characters. When you trigger the configuration deployment through adding or modifying a traffic analysis task or configuring parameters, the configurations on the receiver might fail to be updated. When you use browsers not recommended by, script errors might occur on the pages. Please use the recommended browsers. The VPN traffic analysis task cannot export the traffic report. When you click the bar graph on the traffic analysis overview page, the page might be navigated to other traffic analysis tasks. To solve this problem, click the link for a task on the traffic analysis overview page. Database connection error occurs when you analyze an interface traffic application task report by application or protocol. The Sub Traffic Analysis Server window has no data when the current imc system accesses lower-level imc through HTTPS. On the imc home page, a host task is selected for the Traffic Trend for Host Task (Last 1 Hour) widget, but the widget does not have data. If a device includes an apostrophe (') in the name or description, the interface traffic analysis task that contains interfaces of the device does not have data. An imc viewer cannot display the host session monitoring information on the traffic analysis page.

10 Issued: March 2015 Copyright 2015 Hewlett-Packard Development Company, L.P. and its licensors.