Release Notes for the Cisco NetFlow Generation Appliance

This release note includes important information about Cisco NetFlow Generation Appliance (Cisco NGA) Software Release 1.1 (1) and contains the following sections:

New and Changed Information

Cisco NGA Enhancements

Cisco NGA Bugs

Documentation Updates

Product Documentation

Obtaining Documentation and Submitting a Service Request

page on Cisco.com.

New and Changed Information

The following sections describe release information that is pertinent to Cisco NetFlow Generation Appliance Software Release 1.1 (1).

June 01, 2015

Hardware release of Cisco NetFlow Generation Appliance 3340 and software version 1.1 (1), with enhancements and bug fixes, NGA 3240 software version 1.0(2) and 1.0(3) upgrade support.

February 11, 2015

Software releases of version 1.0 (3) for Cisco NetFlow Generation Appliance 3240 with enhancements and bug fixes and software version 1.0 (2) upgrade support.

November 21, 2012

Hardware release of Cisco NetFlow Generation Appliance 3240 and software version 1.0 (2), with enhancements and bug fixes and Cisco NGA 3140 software version 1.0 (1) upgrade support.

May 18, 2012

Initial hardware release of Cisco NGA 3140 with software version 1.0 (1).

Cisco NGA Enhancements

Cisco NetFlow Generation Appliance (NGA) provides network visibility and establishes a new standard for cross-device flow visibility. It empowers network operations, engineering, and security teams with actionable insight into network traffic for the purpose of resource optimization, application performance improvement, traffic accounting, and security needs.

.

Enhancement Features

Description

Enhancements in Cisco NGA 1.1 (1)

Allowing Customization of SNMP Strings of Data Ports

Cisco NGA 1.1 allows setting new values for IF-MIB strings ifName, ifAlias, and/or ifDescr on the data ports. This enhancement allows identifying what the data ports are actually connected to. The NetFlow collector can then provide more meaningful information in reports.

Adding Exporter IP Address (NGA Management IP Address) to Flow

NGA management IP address can be included as a flow data record field to enable reporting flow record data based on management IP address.

Adding Support for NGA 3340

Cisco NGA 1.1 supports Cisco NGA 3340.

Enhancements in Cisco NGA 1.0 (3)

Adding CLI Idle/Inactivity Timeout

Cisco NGA supports CLI idle/inactivity timeout command to set the idle timeout.

Upgrading to CiscoSSL

Cisco NGA is upgraded to the latest version of CiscoSSL

Allowing User to Remap ifDescr, ifName, and ifAlias strings

SNMP IF-MIB has three different objects such as ifDescr, ifName, and ifAlias, that contain user meaningful interface string values. Of the 3 SNMP objects, different NetFlow collector uses different object for GUI presentations. Cisco NGA 1.1 allows you to select using which of the three for collector GUI presentations.

Shutting Down Unused Data Port

The unused NGA data port is shutdown to reduce NGA's energy consumption and heat dissipation. It also helps external load balancers to detect the port status correctly.

Adding Support for Secure File Transfers

Cisco NGA supports secure image upgrade procedure by using protocols such as FTP, HTTP, SCP, and SFTP.

Support for TACACS+ server

Added support to the TACACS+ server.

Enhancements in Cisco NGA 1.0 (2) Patch 1

Adding SVI Interfaces

Cisco NGA flow data records are enhanced to support SVI interface if-index values.

Enhancements in Cisco NGA 1.0 (2) Patch 2

Reducing Frequency of Logins to Remote Device(s)

To get interface information for flow record data, Cisco NGA periodically launches SSH connection to its managed devices and issues some show commands. Instead of one SSH connection per show command per interval, Cisco NGA is enhanced to use one SSH connection for all commands in the interval.

Device Support

Common Deployment Scenarios

This release note includes the following examples to help illustrate several configuration scenarios for your Cisco NGA.

Single Source of Flow Visibility for Multiple Management Applications

Fabric Path Domain Flow Visibility in the Data Center

Collect Data Using Various Export Formats to Support Multiple Management Applications

Single Source of Flow Visibility for Multiple Management Applications

Figure 1 shows a configuration example of the Cisco NGA flow components that use the same traffic flows but allow you to filter flow data about specific applications; for example, if you want to verify application specific flows that enable you to charge a customer for usage, use this type of configuration. The numbered list below the figure corresponds to the callouts in Figure 1 and describes each component in this configuration example.

.

Figure 1 Deployment for Single or Multiple Device Traffic Flows for Multiple Application Data

1

Configure traffic from one or more network devices to Cisco NGA using SPAN or a passive network tap. For details on how to configure SPAN or a tap device, see your device documentation.

2

Configure a flow monitor with all four interfaces from your switch (which could be an access or aggregation switch).

3

Configure a single v5 flow exporter to receive traffic on all four data ports. The flow exporter manages the flows with the same filters to support one format; in Figure 1 the exporter supports v5 format.

4

Configure multi-destination policies to replicate the flows across multiple collectors. This enables you to use the same traffic flows across all collectors for the purpose of separate management tasks.

5

Configure a filter for billing purposes by selecting the source IP address and source port number in the Advanced Setup Filter configuration window. Alternately, if you have a v9 flow exporter use the application ID defined in the record, you may filter on the application instead of the port number.

6

Use your NetFlow collectors to produce reports, graphs, and analysis of the data.

Fabric Path Domain Flow Visibility in the Data Center

Figure 2 shows a configuration example of the Cisco NGA flow components that help you to analyze Layer 2 traffic flows from two or more switches within the data center using load balancing policies; for example, to filter specific flows across all collectors, use this type of configuration. The numbered list below the figure corresponds to the callouts in Figure 2 and describes each component in this configuration example.

Figure 2 Deployment for Fabric Path Domain Flow Visibility in the Data Center

1

Configure traffic from two (or more) network devices in the Fabric Path domain to Cisco NGA using SPAN or a passive network tap. This enables you to analyze Layer 2 traffic flows within the data center. For details on how to configure SPAN or a tap device, see your device documentation.

2

3

Configure multiple flow exporters to receive traffic from different devices on all four data ports. The flow exporter manages the flows with the same filters to support one format; in Figure 2 the exporter supports v9 format.

In this mode, only one level of filters are allowed; the filters that are associated with the flow exporter. Having only a single set of filters applied at the exporter level allows the appliance to accurately honor the round-robin weight assignments.

4

Configure load balancing policies to spread the flows across multiple collectors. This enables you to avoid high traffic flows on any one collector and improve scalability.

5

When collectors are configured in load-balancing mode you can apply filters at the exporter level only.

6

Use your NetFlow collectors to produce reports, graphs, and analysis of the data.

Collect Data Using Various Export Formats to Support Multiple Management Applications

Figure 3 shows a configuration example of the Cisco NGA flow components that help to gather flow data using different export formats. This scenario supports flow visibility into multiple management applications such as billing (using NetFlow v5 format) and security (using IPFIX format). The numbered list below the figure corresponds to the callouts in Figure 3 and describes each component in this configuration example.

Figure 3 Deployment with Different Export Formats Collecting Multi-Application Data

1

Configure traffic to Cisco NGA using SPAN or a passive network tap. A flow monitor can be configured to listen to up to four data ports. For details on how to configure SPAN or a tap device, see your device documentation.

2

Configure one or more flow monitors to export multiple export formats. Figure 3 depicts v5 and IPFIX exporters. Each exporter can work independently using different traffic input based on the requirements of your management application.

3

4

Given that filtering has been configured at the flow exporter, no extra filtering is required at the flow collector.

5

Use your NetFlow collectors to produce reports, graphs, and analysis of the data.

Cisco NGA Bugs

This section provides the following information:

Resolved Bugs

Using the Bug Tool Kit

Resolved Bugs

provides a list of resolved bugs in Cisco NGA Software Release 1.1 (1).

Table 1 Resolved Bugs in Cisco NGA 1.1 (1)

Identifier

Description

CSCut19060

In Cisco NGA 1.1, if any flow received at the NGA data ports include IP fragments, the NetFlow records exported by the NGA contain an incorrect value of 255 in the IP Protocol field.

CSCut45937

Cisco NGA evaluates OpenSSL vulnerabilities.

CSCut77454

Cisco NGA evaluates NTPd vulnerabilities.

CSCut80974

Cisco NGA reports incorrect IP Protocol field while exporting flow records for Encapsulating Security Payload (ESP) packets.

CSCuu47537

In Cisco NGA 1.1, CLI must not timeout in non-interactive mode.

provides a list of resolved bugs in Cisco NGA Software Release 1.0 (3).

Table 2 Resolved Bugs in Cisco NGA 1.0 (3)

Identifier

Description

CSCum63633

In Cisco NGA, if a flow consists of a single packet, the exported value of the last timestamp may be one tick less than the value of the first timestamp. To avoid this incorrect timestamp, the configuration must be done in such a way that the first timestamp is updated before the last timestamp.

CSCuq10201

Cisco NGA XWT version is upgraded from 1.6 to 1.7.3.39. This upgrade allows the web user interface to change to newer from the dark Kubrick color scheme to lighter color scheme.

CSCur61498

Cisco NGA evaluates the SSLv3 POODLE vulnerability in CBC mode.

CSCus14910

Cisco NGA reduces the maximum value of cache size from 80M to 72M on NGA 3140 and 3240. This cache size reduction avoids low memory issue. NGA 3340 has 80M cache size.

provides a list of resolved bugs in Cisco NGA Software Release 1.0 (2) Patch 2.

Table 3 Resolved Bugs in Cisco NGA 1.0 (2) Patch 2

Identifier

Description

CSCup32818

If traffic is directed to the NGA data ports which have Fabricpath encapsulation, the traffic may not be accounted correctly. The Cisco NGA exports incorrect flow values for MAC addresses, ethertype, and other fields.

CSCup45836

The show lookup statistics command shows only the number of successful lookups and the number of failures.

CSCup32912

Cisco NGA returns incorrect values for some SNMP MIB objects.

CSCup90918

In HSRP deployments, traffic that is switched through "Gateway" MAC address must be associated with the VLAN SVI interface instead of the port-channel connecting the peer switches.

CSCur64313

Cisco NGA logs incorrect error messages in nam_debug_log.txt file for debugging purpose.

provides a list of resolved bugs in Cisco NGA Software Release 1.0 (2) Patch 1.

Table 4 Resolved Bugs in Cisco NGA 1.0 (2) Patch 1

Identifier

Description

CSCug32537

Cisco NGA uses IPFIX flow record ID values in v9 flow record template flowset.

CSCug32496

Cisco NGA CLI "show cache" command does not correctly show NGA internal flow count when TCP connections with same address and port pair are closed and restarted back to back.

CSCug32554

Fixed NGA exports flow record timestamp value unit issue.

Using the Bug Tool Kit

This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release.

.

. The Bug Toolkit page opens.

Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.

.

Step 4 To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:

Select Product Category—Network Management and Automation.

Select Products—[Product Name].

Software Version—[Product Version].

Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information:

– Severity—Choose the severity level.

– Status—Choose Terminated, Open, or Fixed.

Choose Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required.

Choose Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box. For example, if you want to view only new bugs in NGA 9.5, choose only New.

Choose Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box.

– Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.

– Modified Date—Choose this option to filter bugs based on the date when the bugs were last modified.

– Results Displayed Per Page—Specify the number of bugs to display per page.

. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Step 6 To export the results to a spreadsheet:

.

b. Specify the filename and location at which to save the spreadsheet.

. All bugs retrieved by the search are exported.

or contact the Cisco Technical Assistance Center (TAC).

Documentation Updates

.

The following information is more recent than the existing Cisco.com documentation and online help:

Updates for Quick Start Guide

User Guide Content

Updates for Quick Start Guide

are updated below for release 1.1 (1) as follows:

Rear Panel for Cisco NGA 3340

Front Panel for Cisco NGA 3340

Supported Upgrade Path

Configure Your Traffic Sources

Field Replaceable Units (FRU) Components

Cisco NGA 3340 Technical Specifications

and refer back to the release notes for recently updated details.

Rear Panel for Cisco NGA 3340

The rear panel for the Cisco NGA 3340 is described in Figure 4.

Figure 4 Cisco NGA 3340 Rear Panel

Table 5 Rear Panel Location Numbers

1

PCIe riser 1/slot 1

7

Serial port (RJ-45 connector)

2

PCIe riser 2/slot 2

8

Dual 1-Gb Ethernet ports (LAN1 and LAN2)

3

Modular LAN-on-motherboard (mLOM) card slot

9

VGA video port (DB-15)

4

Grounding-lug hole (for DC power supplies)

10

Rear unit identification button/LED

5

USB 3.0 ports (two)

11

Power supplies (up to two, redundant as 1+1)

6

1-Gb Ethernet dedicated management port

Front Panel for Cisco NGA 3340

The front panel for the Cisco NGA 3340 is described in Figure 5.

Figure 5 Cisco NGA 3340 Front Panel

Table 6 Cisco NGA 3240 Front Panel

1

Drives (up to eight 2.5-inch drives)

7

Fan status LED

2

Pull-out asset tag

8

Temperature status LED

3

Operations panel buttons and LEDs

9

Power supply status LED

4

Power button/Power status LED

10

Network link activity LED

5

Unit identification button/LED

11

KVM connector (used with KVM cable that provides two USB 2.0, one VGA, and one serial connector)

6

System status LED

Supported Upgrade Path

provides details on the commands to use for Cisco NGA backup, upgrade, and restore tasks.

Table 7 Backup, Upgrade, and Restore Information

Task

Preferred Method

Command

Back up Cisco NGA version 1.0 (2), 1.0 (3) or 1.1 (1)

CLI

Upgrade Cisco NGA 3240, v 1.0 (3) to 1.1 (1)

CLI

Restore configuration v 1.0 (2), 1.0 (3) or 1.1 (1)

CLI

Recovery (only when catastrophic event occurs)

CIMC

power cycle server or use helper utility

Configure Your Traffic Sources

This section includes updates to the existing product documentation which now includes the Cisco Nexus 3000 Series switch as a managed device.

.

There are two tasks to configuring your traffic sources. The traffic source in Cisco NetFlow Generation Appliance can be either a switch or router. The first task is required; the second task is optional.

.

1. (Required) Create a Switched Port Analyzer (SPAN) session (also known as port mirroring) on your switch or router using the command line interface, or use a tap device to forward traffic to your Cisco NGA. Port mirroring selects network traffic for analysis by a network analyzer.

Ensure that your traffic sources are connected to the data ports on the appliance with the appropriate 10-Gb Ethernet cable. This document does not provide details on how to create SPAN sessions or to use a network tap device. For details on how to set up these configurations, see your device documentation.

2. (Optional) Configure the IP address of your traffic source in Cisco NGA as a managed device.

If your traffic source is one of the supported Cisco switches or routers and you want the appliance to export flow records with the input and output interface of the device rather than data port interface index on the appliance, you need to configure the IP address and login credentials of your traffic source as a managed device. For details, see Configure the IP Address of Your Traffic Source.

One of the benefits of configuring a managed device on the Cisco NGA allows the appliance to gather the interface index from the device. Cisco NGA populates exported NetFlow records with the interface (ifIndex) values from the device that is being monitored, rather than the interface values from the appliance itself.

Note SSH must be enabled on the remote Nexus device in order for Cisco NGA to access interface information. For details on how to enable SSH on the Nexus OS, see the device documentation.

Configure the IP Address of Your Traffic Source

One of the benefits of configuring the IP address of your supported Nexus Series switches is that when your switch is configured as a managed device, Cisco NetFlow Generation Appliance uses the switch's interface index values when exporting records. This allows you more visibility into the collected data. This is an optional task.

Ensure that your traffic sources are connected to the data ports on the Cisco NGA with the appropriate 10Gb Ethernet cable.

To add, edit, or delete managed devices:

.

Step 2 Choose one of the following tasks:

To add managed devices, click Create and enter the required information in the Create Managed Device window. See Table 1-8 for field descriptions.

To edit an existing managed device, select the row, click Edit then enter the device information.

To delete a managed device, select the row and click Delete .

Table 1-8 Managed Devices Table Field Descriptions

Field

Field Description

Address

Device IP address. Use the IP address and not the domain name.

Verify Password

Enter the managed device (switch or router) access credentials.

Data Ports

Enter the appliance data ports that are connected to the managed device (for example, the Nexus 3000, Nexus 5000, or Nexus 7000 Series device) as SPAN destinations. These ports will receive replicated packets for monitoring.

Any combination of data ports may be connected to the same managed device. If you connect the appliance to multiple Nexus Series switches, ensure you define a separate managed device for each switch that specifies the correct data ports that the switch connects to on the appliance.

You can configure up to four managed devices. For each managed device, you can specify which set of data ports are attached to it. Once a data port is assigned to one managed device, you cannot assign it to another managed device.

.

. A NetFlow monitor instance consists of a flow monitor, collector, and exporter for v5 and a flow monitor, collector, exporter, and record name for v9. Then use Advanced Setup if you require additional flow components or filters.

Cisco NGA 3340 Technical Specifications

The following table contains links to the technical specifications for the Cisco NetFlow Generation Appliance 3340. Cisco NGA is an integrated hardware platform that is preinstalled with the Cisco NetFlow Generation Appliance Software Release 1.1 (1) on the UCS C220 M4 server.

Specification

See...

Physical

.

Environmental

.

Power

. Cisco NGA ships with a 770W power supply.

.

User Guide Content

The following sections are available in the user guide:

Overview of Cisco NGA Flow Components

Examples of Deployment Scenarios

Miscellaneous Updates

Using Virtual Media to Install or Recover Cisco NGA

Overview of Cisco NGA Flow Components

Cisco NGA uses flow components, or standard NetFlow configurations, to customize the traffic analysis parameters for your specific requirements. You can quickly set up a single NetFlow monitoring instance which is the minimum set of flow components required using the Quick Start workflow.

For advanced configurations where multiple NetFlow monitoring instances are desired or advanced features such as filters and customizing v9 and IPFIX record parameters are needed, you can use the Advanced Setup workflow.

.

Figure 6 Quick Setup Diagram of Cisco NGA Flow Components

.

defines each flow component and provides examples of how to configure them. Flow components can be combined to create various monitoring instances to address specific deployment needs. For details on the deployment methods you can choose for device support, see Examples of Deployment Scenarios.

Table 9 Cisco NGA Flow Components and Terms

Component 1

Description

Uses/Importance

Flow monitor

A flow monitor is required to export flow cache data. You must create and activate at least one flow monitor for the system to begin exporting flows.

You can create more than one flow monitor to monitor different sets of data ports and use different cache parameters.

One data port can be used by one active monitor at any given time.

The flow monitor designates which data ports are monitored by the the appliance and specifies parameters for the flow cache operation. You can custom the following parameters:

The size of the cache

Timeout values and behavior

Which flow records are to be associated with the flow monitor

When you use multiple flow monitors you can associate different data ports with each monitor. You can also associate different exporters with each monitor, and by doing so associate different collectors with each monitor.

For example, you can attach four different switches to the appliance, so that you send the data from each switch to a different collector. In this case, you must create four distinct flow monitors, each one configured with the data port that is connected to the corresponding switch. Each flow monitor has its own flow exporter (so you can vary them to use either v5 or v9), and each of those exporters can be associated with a different collector.

Flow collector

Each flow collector within the Cisco NGA represents a construct (which may have associated filters). That internal construct, represented in the figure as a flow collector socket, is what you must explicitly configure.

The NetFlow collector is an external device, separate from the Cisco NGA, to which the appliance can export flow records. Most collectors will store the flow data in a database and then produce reports, graphs, and analysis of the data. Use the Cisco NGA’s flow collector configuration to specify the IP address and UDP port of your collectors.

A collector may specialize in traffic accounting, billing, monitoring traffic patterns on your network, or detecting potential security threats. Flow records exported by the Cisco NGA provide the necessary data to produce these reports.

You may configure multiple collectors and the Cisco NGA exports data to each of them, either alternating between them in a round robin fashion, or replicating the same flow data to each collector. In this way you can deploy multiple collectors for different purposes. You can also spread the load across multiple collectors if one collector cannot keep up with the data rate exported by the Cisco NGA.

Flow exporter

The flow exporter specifies which version of NetFlow Data Export format should be exported by the Cisco NGA.

The flow exporter is also used to designate other parameters such as how often the Cisco NGA sends out NetFlow template updates, and which policy should be used if there are multiple collectors (replicate the same to data to each, or load balance among them).

You may define filters in the flow exporter to specify exactly which flows are to be sent to each collector.

Ensure you choose a NetFlow Data Export format that is supported by your collectors.

Note Cisco NGA is capable of generating a large amount of data. If necessary, use filters to reduce the load on your collector, or use multiple collectors in round robin load balancing mode.

Flow Filters (optional)

There are two configurable filter levels in Cisco NGA: one filter that defines which device record data to collect (collector) and one that defines what data to export to the NetFlow collectors (exporter).

You can use filters to match specific fields within each flow record before it is exported.

You can also reduce the demand on your collector by applying filters to reduce the number of flows that are actually exported by the appliance.

You may apply specific filters to individual collectors, or you may apply filters globally in the flow exporter definition and they will apply to all collectors in that exporter.

The primary use of filters is to lighten the load on collectors that may not be able to keep up with a high export rate.

Alternately, you may only be interested in flow data for a particular host, or set of hosts, or a particular application, and so on. In these cases, you can use filters to limit the data to only those flows that are of interest.

Filters are not applicable for round robin export policy.

Flow Record (configurable in v9 and IPFIX)

A flow record is a basic unit of information exported by the Cisco NGA to collectors.

Use the record configuration to specify which fields are used to uniquely identify a flow, and to specify which counters and information elements are to be exported for each flow.

fields are treated as keys and are used to uniquely identify each flow. For example, you may want a particular flow to be identified by five parameters such as source IP address, destination IP address, source port number, destination port number, and IP protocol value.

fields. For example by selecting only the source and destination IP address. In that case, several connections which use different port numbers are aggregated into a single flow record for export.

fields collect additional data in the flow that you can specify; such as packet count, byte count, TCP flags, and so on.

Managed Device

A supported Cisco switch or router that is configured so that the Cisco NGA can gather NetFlow data such as interface details.

One of the benefits of configuring a managed device on the Cisco NGA is that it allows the appliance to gather the interface index from the device as well as the interface name. Cisco NGA populates exported NetFlow records with the interface (ifIndex) values (ifName, ifDescr, ifAlias, ifType, ifMtu, ifSpeed, and ifHighSpeed) from the device that is being monitored, rather than the interface values from the appliance itself.

1.For details on how to configure these components, see the Quick Start Guide for Cisco NetFlow Generation Appliance or the User Guide for Cisco NetFlow Generation Appliance.

1.For details on how to configure these components, see the Quick Start Guide for Cisco NetFlow Generation Appliance or the User Guide for Cisco NetFlow Generation Appliance.

Examples of Deployment Scenarios

The following content clarifies the deployment methods, or scenarios, that Cisco NGAsupports.

You can direct packets to the Cisco NGA using either or both of the following deployment scenarios:

A Switched Port Analyzer (SPAN) session (also known as port mirroring) from the network device that supports this method. Port mirroring selects network traffic for analysis by a network analyzer. This is a low-cost alternative to network taps.

You can choose to use SPAN, remote SPAN (RSPAN), or SPAN with port channels to monitor your traffic. To configure one of these SPAN methods on your Cisco Nexus or Catalyst devices to send traffic to the Cisco NGA, use the Nexus supervisor or the Catalyst IOS CLI. Using local SPAN uses four data ports, thus four routers or switches.

A network tap. A network tap is a hardware device which provides a copy of the data that flows across a network link. By setting up a network tap using remote SPAN or Remote (RSPAN), you are able to monitor more than the four routers or switches you are limited to using local SPAN.

To understand how SPAN, RSPAN, and port channelling work on Cisco routers and switches and how to configure your network devices using standard SPAN, see your router and switch software configuration documentation.

Field Replaceable Units (FRU) Components

This section details links to manage the Cisco NGA Field Replaceable Units (FRUs):

Removing and Replacing a Hard Disk Drive

section in the Cisco UCS C220 Server Installation and Service Guide.

Installing or Replacing a Power Supply

section in the Cisco UCS C220 Server Installation and Service Guide.

Miscellaneous Updates

The following details will be added to the user guide during the next release update:

You must define a NetFlow v9 record counter field (such as packets or bytes) or no NetFlow data generates (since there is no data to collect).

The v9 record name of an existing flow monitor may still be displayed after the particular flow monitor being edited and changed to exported NetFlow v5 type. The workaround is, while in flow monitor editing mode, use the backspace key to delete the Exporter name then un-select the v9 Record Name when this field becomes editable. Reselect the Exporter then save.

When you use the CLI, if you have multiple existing filters and attempt to add another filter you must reenter all the filter names in order to add any new filters. We recommend you use commas with no spaces to separate the filters.

Cisco NGA is now recovered using virtual media if necessary. The CD/DVD is no longer shipped. See Using Virtual Media to Install or Recover Cisco NGA for instructions.

Table 10 lists the ports used by the Cisco NGA for network communication.

Table 10 Ports Used by Cisco NGA in Network Deployments

Port

Description

TCP (22)

SSH—The port that Cisco NGA uses to collect configuration information from managed devices.

Note SSH must be enabled on the remote Nexus device in order for Cisco NGA to access interface information. For details on how to enable SSH on the Nexus OS, see the device documentation.

TCP (23)

Telnet—Port used for Telnet.

TCP (80)

HTTP—Default port if Cisco NGA is configured for access using HTTP.

UDP (161)

SNMP—The port used to communicate with the Cisco NGA’s SNMP Agent.

TCP (443)

HTTPS—Default port if Cisco NGA is configured for access using HTTPS.

Using the CIMC

The CIMC is a built-in management service provided with the Cisco NGA. CIMC provides a web-based GUI that enables you to perform tasks including:

Manage remote presence with KVM console. The console is an interface accessible from CIMC and emulates a direct keyboard, video, and mouse (KVM) connection to the appliance. The KVM console allows you to connect to the appliance from a remote location. It also provides the “Virtual Media” feature used for recovery/ISO install. (See Using the KVM Console.)

Power on, power off, power cycle, reset and shut down the appliance

Toggle the locator LED to locate the appliance with blinking blue LED

For instructions on how to use the Cisco NGA built-in management tool to perform various tasks, see Using Virtual Media to Install or Recover Cisco NGA.

Using the KVM Console

The KVM console is an interface accessible from the Cisco NGA that emulates a direct KVM connection. The KVM console allows you to view the serial console remotely without any connection to a terminal server. It also provides the Virtual Media feature used for recovery/ISO install.

If you want to use the KVM console to access the appliance, you must ensure that either the appliance or the service profile associated with the appliance is configured with a CIMC IP address. The KVM console uses the CIMC IP address assigned to an appliance or a service profile to identify and connect with the correct appliance.

If the management subnet you are connected to has a DHCP server deployed, the CIMC will automatically receive an IP address. This address will be displayed during initial bootup and can be seen from a serial console connection or a VGA screen.

If the management subnet you are connected to does not have a DHCP server, you must enter a static IP address by entering the CIMC configuration setup during bootup. To do this, press <F8> during initial bootup. After the address is set, the CIMC GUI and ssh connections will be available.

.

Using Virtual Media to Install or Recover Cisco NGA

To upgrade or recover Cisco NGA you can use the Cisco Image Management Controller to map the Cisco NGA ISO file to the virtual media CD. No CD/DVD is shipped with the product. You must log in with user or admin privileges to perform this task.

Step 1 Download the ISO file from Cisco.com (where the Cisco NGA images are located).

Step 2 Log into web interface (default: admin/password) using your web browser.

.

Step 3 Click Launch KVM Console (requires Java).

Step 4 In the Java applet, click the Virtual Media tab.

and select the ISO file.

Step 6 Check Mapped in Client View for the newly created drive.

.

The appliance will boot up from the mapped ISO image and will stop at the Helper Utility menu.

Step 8 Click the KVM tab in the Java applet.

Step 9 Choose one of these options:

a. Option 3 to install the image bundled in the ISO.

You must use Option 3 when upgrading from Cisco NGA 3140, software release 1.0.1 to 1.0.2. This option ensures the helper image is updated.

b. Option 2 to install a new image from the network and reformat the disk.

c. Option 1 to upgrade NGA to a new image from the network.

.

Reference Appendix Updates

, Configure Records Window Fields, the following routing features are not supported in Cisco NGA:

– SRC_AS, DST_AS

– BGP_NEXT_HOP

– SRC_MASK, DST_MASK

Product Documentation

The Cisco NetFlow Generation Appliance product documentation supports Hardware Releases 3340.

Note We sometimes update the documentation after original publication. Therefore, you should review the documentation on Cisco.com for any updates.

Related Documentation

This section provides information about other documentation related to the Cisco NetFlow Generation Appliance.

Cisco Nexus 7000 Series Switch

Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x

SPAN Configuration on a Nexus 7000 Series Switches

Cisco Nexus 5000 Series Switch

Cisco Nexus 5000 Series NX-OS Software Configuration Guide

Cisco Nexus 3000 Series Switch

Cisco Nexus 3000 Series NX-OS Fundamentals Configuration Guide (for SPAN configuration details)

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at the following URL:

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)