Cisco Services Modules

Release Notes for Cisco Nexus 7000 Series Network Analysis Module (NAM-NX1) 6.0(1)

  • Viewing Options

  • PDF (105.4 KB)
  • Feedback

Table of Contents

Release Notes for Cisco Nexus 7000 Series Network Analysis Module (NAM-NX1) 6.0(1)


Enhancements or New Features in this Release

System Requirements

Package Details


Compatibility Testing of Supported NX-OS

Known Issues

Related Documentation

Cisco Bug Search

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Nexus 7000 Series Network Analysis Module (NAM-NX1) 6.0(1)

Published: September 23, 2013, OL-30665-01
Revised: April 14, 2014


These release notes provide general information about Cisco Prime Network Analysis Module Software release 6.0(1) on the Cisco Nexus 7000 Series Network Analysis Module (NAM-NX1).

This document includes the following sections:


Network Analysis Module release 6.0(1) is for NAM-NX1 platform only. NAM-NX1 is the first Nexus 7000 service module.

To take advantage of the Cisco Nexus 7000 Series Release 6.2(8) performance improvements for Data Center protocols (VxLAN, FabricPath,  OTV, LISP, Segment ID, VNTag, and FCoE), you can upgrade the FPGA image in your Cisco Nexus 7000 Series NAM-NX1. For details on how to upgrade your FPGA image, see FPGA/EPLD Upgrade Note for Cisco Prime NAM-NX1, 6.0 .

Enhancements or New Features in this Release

Network Analysis Module release 6.0(1) is the first software release on the NAM-NX1 platform.

System Requirements

NX-OS Release 6.2(2) or later on Sup 1 and Sup 2 and Nexus 7004, 7009, 7010, and 7018 chassis.

It works with F2, F2e, M1 and M2 series line cards. It does not work with F1 series line cards. It also does not work in FCoE storage VDC.

Package Details

Table 1 provides details on the NAM images available for this release on

Table 1 Package Details



NAM application image. Runs in normal operations


Boot image. Only runs when NAM is booting up


Boot helper image. Only runs during application image upgrade or recovery


1. NAM packet decode does not provide the option to enter decode preferences and protocol forcing such as the Decode As feature seen in other products.

2. The decode filter syntax is not documented in the online help.

3. VACL capture support for NAM is not available on the Nexus 7K switch at this time.

4. When NAM monitors and captures FabricPath packets, the FabricPath header will be unconditionally removed due to a known hardware issue with F2 line cards. Although the packet data will be correctly processed and presented by NAM, the FabricPath information carried inside the header will be lost. To identify traffic that is FabricPath encapsulated, use another means such as specific VLANs or interfaces on the switch.

5. NAM correctly monitors and captures OTV, LISP, FCoE, VxLAN, VNTag, and Segment ID packets. However the performance is not optimal. An upgrade to improve the performance will be available in the near future.

6. To monitor traffic on the NAM management VLAN, you must SPAN it to data port 2.

7. The default NAM account (“guest”) for CLI login has been removed due to security requirements.

8. Not all user-defined applications can be used in capture filters. This limitation applies if the application cannot be correctly identified in a single data packet.

9. Some long URLs may be truncated in the URL hit monitoring feature.

10. When performing a capture decode, you may not be able to scroll down to see all decoded packets until the entire decode is complete.

11. Configuring an unreliable or unreachable DNS server may cause some operational issues or delays on the NAM.

12. The two NAM-NX1 data ports can be combined for monitoring data but cannot be combined for packet captures. Use separate filters and capture sessions for each data port.

13. Please select the correct data port, site, and other qualifiers for your drill-down operations. In some cases, if you leave them blank, the implied/default selection may be different from your expectations.

14. Capturing packets from data port 2 to local disk works for traffic rates within the specified limit and completed sessions. Repeated start and stop of the same file-wrap session may cause data corruptions. Constant data rate higher than the disk write I/O throughput in file-wrap capture mode may also cause delay in NAM responding to Nexus 7000 supervisor, which in turn may cause the NAM to be rebooted by switch supervisor. Capture from data port 1 works fine in all cases.

15. Capturing packets to iSCSI disk and external SAS storage are not fully tested.

16. PTP/1588 time synchronization is not fully working yet.

Compatibility Testing of Supported NX-OS

Only NX-OS 6.2(2) or later is supported. There is no IOS support.

Known Issues

Table 2 contains the known issues for this release.

Table 2 Known Issues

Bug ID


A more precise formula should be used for Avg Concurrent Connections

The current formula is not optimal.


Browser script error (Firefox) with Decode function

Some version(s) of the Firefox browser may experience a script error in decode function. We are still trying to diagnose under what conditions this will occur.


Real Time Graph loses sort column on data refresh

User selected column sorting does not persist over screen refresh. It goes back to the default sorting.


ART metric values exported through the NBI changed from milliseconds to microseconds

NAM 6.0 improved Application Response Time (ART) units from milliseconds to microseconds. This causes a compatibility issue with the existing Prime Infrastructure (PI) application which still expects the data in units of millisecond.


Changing all values on 'network parameters' page has no effect using IE9

This is IE9 only issue. Works fine with other browsers.


Viewing old data with deleted app/site/datasource may cause an error

Custom defined application / site / data source already present in NAM data base may be shown differently or incorrectly if the definition is later deleted by the user.


UI may become unresponsive if decode session is repeatedly removed while processing

If incomplete decode sessions that are working in the background are repeatedly removed several times in succession, the GUI may become unresponsive and require an http restart. This does not occur while actually viewing decoded packets, only when canceling existing decode sessions that are not yet completed.


Unable to perform 'Analyze' operation on certain pcap files

Some lab-generated traffic saved to PCAP files may cause this issue.


Not able to dissect VxLAN encapsulation capture

Need to add VxLAN port number to decode preference.


Real Time Graph shows spikes and valleys with constant source traffic

Due to the accuracy of interval timing, data port receive counters may not be exactly equal for each interval when the input rate is kept constant.


NAM: CLI and GUI show different time zone

System time on GUI shows UTC, but CLI shows the local time zone.


NAM-NX1: application restart may occur when sending trap messages

Deliver trap message may cause an internal process to crash and restart.


CLI shut command on N1K VSB NAM works as restart instead

This is due to a Nexus 1K platform limitation.


[Report] analyze response time reports excludes 'other metrics' data

“Other metrics” information which is displayed in the GUI are missing from reports.


LineChart: x-axis time values only display date when querying > 24 hours

Due to a limitation with a GUI widget, too many time points may be displayed in the same area of the x-axis. Under certain conditions the x-axis may become unreadable.


NAM-NX1 does not support Ejector-based graceful application shutdown

This is a hardware design limitation.


Cannot send encrypted e-mail

Encrypted e-mail is not yet supported


Error may occur when configuring Conversation Bytes (Dst/Src) threshold

Specifying “Bytes (Dst/Src)” in the “Conversation Metrics (per second)” input field may generate an error dialog.


Using 'custom' time may show different result than 'Last Hour'

When using the ‘custom’ time range selector and selecting the last one hour of data, the result shown may be different than what is shown by selecting ‘Last 1 Hour,’ even though they represent the same interval of time. This occurs infrequently.


Timeouts may occur when viewing the Monitor > Alarm Summary screen

If there are many alarms configured and many have been triggered, viewing a large number of them on the Monitor > Alarm Summary screen (e.g. last 1 week) may time out.

Cisco Bug Search

Bug Search Tool (BST), the online successor to Bug Toolkit, is designed to improve our customers’ effectiveness in network risk management and device troubleshooting. Use Network Analysis Module to search.

BST allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The service has provision to filter bugs based on credentials to provide external and internal bug views for the search input.

Please check out Bug Search Tools & Resources on For more details on the tool overview and functionalities, check out the help page, located at

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.