Guest

Cisco Prime Network Analysis Module Software

Release Notes for Cisco Prime Network Analysis Module Software 5.1(2)

  • Viewing Options

  • PDF (723.5 KB)
  • Feedback
Cisco Prime Network Analysis Module Software 5.1(2) Release Notes

Table Of Contents

Cisco Prime Network Analysis Module Software 5.1(2) Release Notes

New and Changed Information

New Features and Enhancements in Cisco Prime Network Analysis Module 5.1(2)

NAM Platforms

System Requirements

Platform Hardware Requirements

Using NME-NAMs with Cisco Integrated Services Routers

Platform Software Requirements

NAM and IOS Software Requirements for Virtual Switch System

WAAS Appliance Requirements

NAM SRE Requirements

Catalyst 6500 NAM-1 and NAM-2 Memory Recommendation

Data Storage Recommendation

Browser Requirements

Connecting to NAM Using the HTTP Secure Server

Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image and BIOS Requirements

NAM Licensing Requirements

Upgrading to NAM 5.1(2)

Supported Upgrades

Upgrading from NAM 5.0(1T) to NAM 5.1(2)

Upgrading from NAM 5.1(1) to NAM 5.1(2)

Installing NAM Software

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image Software

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 BIOS Image Software

Upgrading ROMMON for Catalyst 6500 Series Switches

Upgrading the NAM FPD Image for NAM-3/SUP2T

Determining if an FPD Upgrade is Required

Upgrading the Cisco IOS and FPD Image

Upgrading the FPD Image Only

Limitations and Restrictions

NAM Creates Capture File on Cancel

NAM Support With Non-Cisco H.323 Voice Devices and Call Managers

ACS Version Supported

Direct Flow Packets to NAM Data Port

No Default CLI Password

Response Time and Voice Quality Analytics

Intelligent Application Performance (IAP)

Checking the NAM Maintenance Image and BIOS Versions

NAM Appliance Support for Cisco Nexus 7000

Restrictions for NME-NAMs

Most Recent NAM 5.1(2) Information

IOS Issues That Might Affect NAM 5.1(2)

IOS Image Incompatibility Prevents Creating SPAN Data Sources Using NAM GUI

Cisco 7600 With Redundant Supervisor Cards Running IOS Image 12.2(33)SRC2

Running IOS Image Newer Than 12.2(18)SXF5

RSPAN and ERSPAN Unsupported in IOS Image 12.2(33)SRD

Caveats

Known Anomalies in NAM 5.1(2)

Resolved Anomalies in NAM 5.1(2)

Documentation Updates

Updates for NAM 5.1(2) Installation and Configuration Guides/Notes

Preparing External iSCSI Storage

Connecting the Storage Array

Updates for NAM 5.1(2) User Guide

Capture Source Field

Documentation

Cisco Prime Network Analysis Module Software 5.1(2)

Cisco Prime Network Analysis Module Release Notes

Cisco Prime Network Analysis Module User Guide

Cisco Prime Network Analysis Module Command Reference

Cisco Prime Network Analysis Module Software API Programmer Guide 5.1

Cisco Prime Network Analysis Module Software 5.1(2) Third Party and Open Source Copyright Notices

Cisco Prime NAM for ISR G2 SRE Documentation

Cisco 2200 Series NAM Appliance Documentation

Quick Start and Documentation Guide for the Cisco 2200 Series NAM Appliance

Installation and Configuration Guide for the Cisco NAM 2204 Appliance

Installation and Configuration Guide for the Cisco NAM 2220 Appliance

Regulatory Compliance and Safety Information for the Cisco NAM 2200 Series Appliances

Cisco Prime Network Analysis Module for Virtual Services Blades Documentation

Cisco Prime Network Analysis Module for WAAS VB Installation and Configuration Guide, 5.1

Cisco Prime Network Analysis Module (NAM) for Nexus 1010 Installation and Configuration Guide, 5.1

Related Documentation

Obtaining Documentation and Submitting a Service Request


Cisco Prime Network Analysis Module Software 5.1(2) Release Notes


May 18, 2012, OL-25929-03

These release notes provide general information about Cisco Prime Network Analysis Module Software 5.1(2).

This document includes the following sections:

New and Changed Information

New Features and Enhancements in Cisco Prime Network Analysis Module 5.1(2)

NAM Platforms

System Requirements

Upgrading to NAM 5.1(2)

Limitations and Restrictions

Caveats

Documentation Updates

Documentation

Obtaining Documentation and Submitting a Service Request

New and Changed Information

May 18, 2012

Included instructions on NAM FPD image for NAM-3/SUP2T customers

April 6, 2012

Updated SM-SRE 710 and 910 support

October 6, 2011

Initial release


New Features and Enhancements in Cisco Prime Network Analysis Module 5.1(2)

Cisco Prime Network Analysis Module 5.1(2) now supports the high performance Cisco Catalyst 6500 Series Network Analysis Module (WS-SVC-NAM3-6G-K9). This release offers integrated, high performance application visibility and troubleshooting in high speed, high density Catalyst 6500 Campus Backbone and Data Center environments.

NAM 5.1(2) increases visibility into both physical and virtual switch environments, and enhances Catalyst 6500 operational manageability in physical and VSS switching environments.

Other features include:

Supports ERSPAN data for voice and RTP monitoring

Supports up to 60k RTP streams and 30k calls monitoring

Consolidates WebEx-relevant sessions into one call

Supports 1588 time synchronization

Supports external storage using a Mini SAS connector or 10 GbE FCoE port

This release is supported on all platforms (as a blind revision).

NAM Platforms

The following models differ in memory, performance, disk size, and other capabilities. Therefore, some allow for more features and capabilities (for example, the amount of memory allocated for capture).

NAM 5.1(2) software supports the following NAM models (SKU):

Cisco NAM 2204 Appliances

NAM2204-RJ45

NAM2204-SFP

Cisco NAM 2220 Appliance

NAM2220

Cisco 6500 Series Switches and Cisco 7600 Series Routers

WS-SVC-NAM-1

WS-SVC-NAM-1-250S

WS-SVC-NAM-2

WS-SVC-NAM-2-250S

WS-SVC-NAM3-6G-K9

Cisco Branch Routers

NME-NAM-120S

Cisco SRE NAM

SM-SRE-700 and 710

SM-SRE-900 and 910

Cisco WAAS NAM Virtual Services Blade

WAVE-574

WAE-674

Cisco Nexus 1010 Virtual Services Blade

N1K-C1010

Table 1 lists the software product numbers for NAM 5.1(2). All other part numbers from NAM 5.1 can be used to receive the updated NAM 5.1(2) software since this is a blind revision.

Table 1 Software Product Numbers

Part Number
Description
SC-SVC-NAM3-5.1-K9

Cisco NAM 5.1(2) for Catalyst 6500 and Cisco 7600 NAM

NAM-APPL-SW-5.1-K9

Cisco NAM 5.1(2) for Appliances with Recovery CD

NME-NAM-SW-5.1-K9

Cisco NAM 5.1(2) for Branch Routers NAM

WAAS-VB-NAM5.1-K9

Cisco NAM Software 5.1(2) for WAAS 574/674

WAAS-VB-NAM5.1-K9=

Cisco NAM Software 5.1(2) for WAAS 574/674 Spare

L-WAAS-VBNAM-5.1-K9

Cisco NAM Software 5.1(2) for WAAS 574/674 (eDelivery)

N1K-C1010NAM5.1-K9

Cisco NAM Virtual Service Blade Software 5.1(2) for Nexus 1010

N1K-C1010NAM5.1-K9=

Cisco NAM Virtual Service Blade Software 5.1(2) for Nexus 1010 Spare

L-N1KC10NAM5.1-K9=

Cisco NAM Virtual Service Blade Software 5.1(2) for Nexus 1010 (eDelivery)

SM-NAM-SW-5.1-K9

Cisco NAM 5.1(2) for ISR G2 SRE SM

L-SM-NAM-SW-5.1-K9=

Cisco NAM 5.1(2) for ISR G2 SRE SM (eDelivery)


The NAM 5.1(2) software does not support any upgrade paths from NAM 3.x or NAM 4.x releases.

System Requirements

This section describes the platform hardware, platform software, NAM hardware, and NAM software requirements for NAM 5.1(2) software:

Platform Hardware Requirements

Platform Software Requirements

WAAS Appliance Requirements

NAM SRE Requirements

Catalyst 6500 NAM-1 and NAM-2 Memory Recommendation

Data Storage Recommendation

Browser Requirements

Connecting to NAM Using the HTTP Secure Server

Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image and BIOS Requirements

NAM Licensing Requirements

Platform Hardware Requirements

Table 2 identifies the hardware modules and platforms required to use NAM 5.1(2).

At least 1 GB of memory is required to run the NAM 5.1(2) software on any of the supported platforms.

Table 2 NAM Hardware Compatibility

Module
Supervisor Card
Platform or Devices

WS-SVC-NAM-1
WS-SVC-NAM-1-250S
WS-SVC-NAM-2
WS-SVC-NAM-2-250S

SUP720
SUP32
RSP720-1G
SUP720-10G
RSP720-10G

Catalyst 6500 Series Switches

Cisco 7600 Series Routers

WS-SVC-NAM3-6G-K9

SUP720-10G

Catalyst 6500E Series Switches

NME-NAM-120S

NA

Cisco 2800 Series Integrated Services Routers (except Cisco 2801)

Cisco 2900 Series Integrated Services Routers (except Cisco 2901)

Cisco 3700 Series Multiservice Access Routers

Cisco 3800 Series Integrated Services Routers

Cisco 3900 Series Integrated Services Routers

SM-SRE-700 and SM-SRE-710

NA

Cisco 2900 Series Integrated Services Routers

SM-SRE-900 and SM-SRE-910

NA

Cisco 3900 Series Integrated Services Routers


Using NME-NAMs with Cisco Integrated Services Routers

This section describes the requirements to use NME-NAM with Cisco Integrated Services Router (ISR) and ISR Generation Two (G2) Platforms.

You can deploy the NME-NAM-120S in any network module slot in the Cisco router platforms indicated in Table 3. A Network Module (NM) Adapter Card, SM-NM-ADPTR, is required to successfully integrate the NME-NAM into supported ISR G2 platforms. The NME-NAM supports the router platforms using NAM 3.6 or later. See Table 5, Minimum Cisco ISR and ISR G2 IOS Versions Required for NAM 5.1(2), for the minimum IOS software requirements to support NME-NAM. Only one Cisco NAM can be installed in a Cisco branch router.

Table 3 Supported Routers

Router Platform
Network Module Adapter
Card Required?

Cisco 3945 ISR

Yes

Cisco 3925 ISR

Yes

Cisco 2951 ISR

Yes

Cisco 2921 ISR

Yes

Cisco 2911 ISR

Yes

Cisco 3845 ISR

No

Cisco 3825 ISR

No

Cisco 2851 ISR

No

Cisco 2821 ISR

No

Cisco 2811 ISR

No

Cisco 3745 MSR

No

Cisco 3725 MSR

No


To install an NME-NAM-120S network module in supported ISR G2 platforms using the NM Adapter Card, see Installing Cisco Network Modules and Service Modules, section "Using Network Modules in Service Module Slots on Cisco 2900 Series and Cisco 3900 Series Routers":

http://www.cisco.com/en/US/docs/routers/access/interfaces/nm/hardware/installation/guide/InstNetM.html

Platform Software Requirements

Table 4 lists the Minimum Cisco Catalyst 6500 and Cisco 7600 Series IOS Versions Required for NAM 5.1(2).

Table 4 Minimum Cisco Catalyst 6500 and Cisco 7600 Series IOS Versions Required for NAM 5.1(2)

Chassis
Supervisor Card
SXF
SXH
SXI
SXJ
SRA
SRB
SRC
Other

Catalyst 6500 Switches

SUP32

12.2(18) SXF

12.2(33) SXH(1)

12.2(33) SXI

         

SUP 32 PISA

             

12.2(18)
ZY(1)

SUP720

12.2(18)
SXF

12.2(33) SXH(1)

12.2(33) SXI

         

SUP720-10GE

 

12.2(33) SXH(1)

12.2(33) SXI

12.2(33)
SXJ(1)1

       

7600 Series Routers

SUP32

12.2(18)
SXF

     

12.2(33) SRA(1)

12.2(33) SRB(1)

12.2(33) SRC

 

SUP720

12.2(18)
SXF

     

12.2(33) SRA(1)

12.2(33) SRB(1)

12.2(33) SRC

 

RSP720-1G

           

12.2(33) SRC

 

RSP720-10GE

             

12.2(33)
SRD

1 NAM-3 requires this specific version.


Table 5 lists the Minimum Cisco ISR and ISR G2 IOS Versions Required for NAM 5.1(2) on the NME-NAM-120S.

Table 5 Minimum Cisco ISR and ISR G2 IOS Versions Required for NAM 5.1(2)

Router Platform
IOS Version

Cisco 2800 Series Integrated Services Routers

12.4(9)T

Cisco 2900 Series Integrated Services Routers

15.0(1)M

Cisco 3700 Series Multiservice Access Routers

12.4(9)T

Cisco 3800 Series Integrated Services Routers

Cisco 3900 Series Integrated Services Routers

15.0(1)M


NAM and IOS Software Requirements for Virtual Switch System

Table 6 lists the NAM and IOS software requirements for NAM blades used in a Cisco Virtual Switch System (VSS) environment.

Table 6 NAM and IOS Software Requirements for VSS

NAM
NAM Software
IOS Software

WS-SVC-NAM-1

NAM 3.6.1a or later

IOS 12.2(33) SXH(1) or later5.1-K9

WS-SVC-NAM-2

WS-SVC-NAM-1-250S

NAM 3.6.1b or later

WS-SVC-NAM-2-250S

WS-SVC-NAM3-6G-K9

NAM 3.6.1b or later

12.2(33)SXJ1


WAAS Appliance Requirements

NAM 5.1(2) supports the WAVE-574 and WAE-674 WAAS appliances. Table 7 provides a description of the Cisco WAAS appliances, their components, and deployment scenarios. WAAS appliances require the following software:

Central Manager: WAAS 4.2.3 (build 55 or later).

Managed WAAS: WAAS 4.2.3 (or later).

Table 7 Cisco WAAS Appliances

Platform
Component
Deployment Scenarios

Cisco WAVE-574

3 or 6 GB DRAM

500 GB hard disk drive

RAID-1 (optional)

2- and 4-port inline card options

WAAS-VB-NAM-5.0

Edge deployments at enterprise branch offices

Core deployments at small data centers

Cisco WAE-674

4 or 8 GB DRAM

600 GB HDD

RAID-5 (optional)

4-port inline card optional

WAAS-VB-NAM-5.0

Edge deployments at large enterprise branch offices

Core deployments at medium-sized data centers


NAM SRE Requirements

NAM 5.1(2) supports the Cisco SRE (Service Ready Engine), the SM-SRE-700 and 710 and SM-SRE-900 and 910. The Cisco® Services Ready Engine (SRE) modules are router blades for the Cisco Integrated Services Routers Generation 2 (ISR G2) that provide the capability to host Cisco, third-party, and custom applications.

For hardware requirements for the Cisco SRE modules, see the Cisco Services-Ready Engine Data Sheets on Cisco.com.

Catalyst 6500 NAM-1 and NAM-2 Memory Recommendation

To optimize the performance of NAM software, particularly of NAM 5.x releases given new features that can have large table sizes, Cisco offers a field-installable memory upgrade kit that can be purchased for WS-SVC-NAM-1 and WS-SVC-NAM-2 devices. The memory upgrade kit comes with 2GB of DRAM. Its part number is MEM-C6KNAM-2GB=.

Cisco has characterized that the memory upgrade can increase the number of hosts and conversations that can be monitored by up to a factor of two (the improvement can vary depending on packet sizes monitored, burstiness of traffic, NAM features enabled, switch/router features enabled, and so on). The memory upgrade not only can improve the number of hosts and conversations monitored, but also, as a result of the foregoing, can increase the number of concurrent flows that can be monitored. This can result in improved NAM performance when the NAM is deployed in places in the network where it can see a large number of concurrent flows.

You can find information about how to upgrade your memory in the document NAM Memory Upgrade Install Note at the following URL:

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/hardware/Config_Notes/
78_18630.html

No memory upgrade kit is offered for the WS-SVC-NAM-1-250S and WS-SVC-NAM-2-250S, which already ship from factory with 2 GB DRAM.

Data Storage Recommendation

The Cisco Catalyst 6500 Series Network Analysis Module (WS-SVC-NAM3-6G-K9) offers external storage connectivity for extended capture durations and higher capture bandwidths. This connectivity is provided through two front-panel ports, one Mini Serial Attached SCSI (SAS, SFF-8088), and one Fibre Channel Over Ethernet (FCoE, SFP+). The external SAS storage array can be directly attached, while most FCoE arrays require an FCoE-capable switch (such as the Nexus 5000 Series Switch) to connect to a NAM-3. A Nexus 5000 Series Switch can connect to multiple FC and FCoE storage arrays.

If you are using FCoE storage, Cisco recommends that your Nexus 5000 Series Switch is running NX-OS 5.0(3)N1(1) or higher.

iSCSI is also supported over the switch backplane.

Table 8 FCoE Data Storage

Module
Switch Used in FCoE Array
NX-OS Software Version

WS-SVC-NAM3-6G-K9

Nexus 5000 Series Switch

Other FCoE-capable switch

5.0(3)N1(1)


Browser Requirements

Table 9 describes the browser requirements for all platforms.

Table 9 Minimum Browser Requirements 

Browser
Versions
Client Platform 1
JVM Support 2
Adobe Flash

Internet Explorer

8.0

(7.0 not supported)

Windows 7

Windows XP Professional

Java Plug-In 1.5.0_11

Version 10.1 or greater

English Firefox

3.6

(4.0 not supported)

Windows 7

Windows XP Professional

Linux (RHEL)

Macintosh OSX 10.6+

1 At least 4 GB of memory is recommended for optimal NAM GUI performance.

2 A Java plug-in might be required to use the Java Virtual Machine (JVM).



Note Although NAM does not require a Java plug-in, you might be required to use the Java Virtual Machine (JVM). The Java plug-in versions listed have been tested for browsers that require a plug-in for the JVM. Cisco recommends JRE Version 5.0 Update 6.


Connecting to NAM Using the HTTP Secure Server

You can connect to the NAM using HTTPS when you enable the secure server using the NAM CLI. For all platforms, except NAM on SM-SRE and WS-SVC-NAM-3 (which already include the crypto patch), you must download a strong crypto patch from Cisco.com to enable this functionality. For details, see your NAM installation guide.

The NAM ships with a self-signed certificate that enables secure connections over port 443. Once you set up the NAM to use HTTPS, a client browser can connect to the NAM using HTTPS. All browsers generate an exception for the self-certificate on the first connection, and you must select OK to accept the exception to proceed.

If you use a Firefox browser to access the HTTPS page or the CLI using SSH and a certificate was generated for the NAM site before, then a sec_error_reused_issuer_and_serial error might display after applying the new crypto patch.

To workaround this error, perform the following steps:


Step 1 Select Tools > Options > Advanced and select View Certificates.

Step 2 Remove the certificates in the Servers tab.

Step 3 In the Authorities tab, locate the certificate authority (CA) on the device on which you are having trouble and delete it.

Step 4 Cisco recommends you do the following to fix the issue (these steps are optional, but recommended):

a. On the NAM CLI enter ip http secure generate to generate a certificate.

b. Enter ip http secure install to install a signed certificate.

Once you complete these steps, the exception message reappears on the connection again andyou must confirm the exception one last time.


Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image and BIOS Requirements

Table 10 lists the minimum versions of the NAM maintenance image, the maintenance image filename, and the BIOS image required for NAM-1 and NAM-2 when using NAM application image 5.1(2).

Table 10 NAM Maintenance Images

Module
Version
(minimum)
Maintenance Image
BIOS
Version

WS-SVC-NAM-1

2.1(5)

c6svc-nam-maint.2-1-5.bin.gz

4.0-Rel 6.0.9 or later

WS-SVC-NAM-2


The BIOS image is bundled with the NAM's maintenance image.

The Upgrading to NAM 5.1(2) section of these Release Notes provides information on:

How to identify the version of the Catalyst 6500 and Cisco 7600 NAM's BIOS image

How to upgrade the Catalyst 6500 and Cisco 7600 NAM's Maintenance image

How to upgrade the Catalyst 6500 and Cisco 7600 NAM's BIOS image

How to upgrade the NAM's Application Image

NAM Licensing Requirements

NAM software (for the WAAS, Nexus 1010, and SRE) requires you to install a product license in the form of a text file. An evaluation license allows you to use the software for up to 60 days, but you will be unable to log in to the NAM GUI after the evaluation license expires. When using an evaluation license, the NAM login window indicates how many days remain before the evaluation license expires.

You can provide licensing information, also known as node-locking information, during software installation or after software installation using the NAM CLI. During the NAM software installation, you will be prompted to enter a product identifier (PID) and serial number (SN). To obtain PID and SN for licensing purposes, use the NAM show inventory command from the CLI.

To obtain a NAM license, go to the following URL:

http://www.cisco.com/go/license

Follow the instructions on this page to obtain a NAM license file. You will need the appliance PID and SN to obtain the license file. After you enter the PID and SN or the Product Authorization Key, a license file will be sent to you by e-mail. Store this license file on an available FTP server. Use the license install command to install the license after the NAM software installation completes.

Upgrading to NAM 5.1(2)

This section provides the following topics:

Supported Upgrades

Installing NAM Software

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image Software

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 BIOS Image Software

Upgrading ROMMON for Catalyst 6500 Series Switches

Upgrading the NAM FPD Image for NAM-3/SUP2T

Supported Upgrades

NAM 5.1(2) does not support any upgrades from the NAM 3.x or NAM 4.x software releases on NAM devices. If you are running a NAM 3.x or NAM 4.x release, you will need to do a fresh install of NAM 5.1(2) (see the next section, Installing NAM Software). Also, since NAM 5.1(2) has a new architecture, if you are upgrading from NAM 3.x or NAM 4.x, you will lose the configuration you have currently set in your NAM. Cisco highly recommends that you back up your current configuration in case you want to go back to a previous version of NAM, where you can restore the saved configuration.

To back up your current configuration, from the NAM command line enter a config upload command like the following:

config upload ftp://server/path
 
   
 
   

The config upload command sends a copy of the NAM running configuration to the destination you specify. The information is stored in a back-up configuration file with an ending suffix of .confg as in NAM_host-c6svc-nam-3.6.1b.confg. The destination address should be a valid server name and directory path.


Note The Cisco Nexus 1010 Virtual Services Appliance is not supported with NAM 5.0. Therefore, because an upgrade from NAM 4.x to NAM 5.0 is not supported, you will need to do a fresh install of NAM 5.1(2) if you are using the Nexus 1010.


Upgrading from NAM 5.0(1T) to NAM 5.1(2)

The NAM software can be upgraded from NAM 5.0(1T) to NAM 5.1(2) using either the CLI or Helper image.

Upgrading from NAM 5.1(1) to NAM 5.1(2)

The NAM software can be upgraded from NAM 5.1(1) to NAM 5.1(2) with some platforms. Table 11 shows the method that you can follow depending on the platform on which you are running the NAM.

Table 11 Upgrade Method Per Platform

NAM Platforms
Upgrade Method (from NAM 5.1(1) to NAM 5.1(2)
NAM blades (NAM-1, NAM-1x, NAM-2, NAM-2x)

Upgrade from the maintenance image

NME NAM

Upgrade from the Helper image

NAM 2220 and 2204 Series Appliances

Upgrade from the CLI or Helper image

NAM on WAAS VB

Upgrade from the Helper image

NAM on Nexus 1010 1

Upgrade from the CLI or Helper image

NAM SRE

Upgrade from the CLI or Helper image

1 We recommend that nexus-1010.4.2.1.SP1.3 software version be used with NAM 5.1(2) for optimal performance.


Installing NAM Software

If you need to do a fresh install of NAM, see the Installation and Configuration Guide specific to your platform.


Note Be sure to review the installation updates in Updates for NAM 5.1(2) Installation and Configuration Guides/Notes. This information is not included in the guides listed below.


For Cisco Catalyst 6500 Series Switch, the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps5401/tsd_products_support_series_home.html

For Cisco 2200 Series Appliances, see the following URL:

http://www.cisco.com/en/US/products/ps10113/prod_installation_guides_list.html

For the WAAS NAM Virtual Blade, see the following URL:

http://www.cisco.com/en/US/products/ps10506/prod_installation_guides_list.html

For NAM on Nexus 1010, see the following URL:

http://www.cisco.com/en/US/products/ps10846/prod_installation_guides_list.html

For the NAM SRE, see the following URL:

http://www.cisco.com/en/US/products/ps10598/prod_module_series_home.html

For all other platforms, see the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps5401/tsd_products_support_series_home.html

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image Software

To upgrade the NAM maintenance image software, follow these steps.


Note This section applies only to the WS-SVC-NAM-1 and WS-SVC-NAM-2 blades running a maintenance image before version 2.1(5).



Step 1 Copy the NAM maintenance software image to a directory accessible to FTP.

You can download the latest version of the NAM maintenance image from the following URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/ws-svc-nam

The most recent NAM maintenance image software available to download is 2.1(5), and its filename is c6svc-nam-maint.2-1-5.bin.gz.

Step 2 Log in to the switch through the console port or through a Telnet session.

Step 3 If the NAM is running in the application image, go to Step 5. If the NAM is not running in the application image, enter this command in the privileged mode:

Router# hw-module module 9 reset hdd:1
Device BOOT variable for reset = hdd:1
Warning:Device list is not verified.
 
   
Proceed with reload of module? [confirm]
% reset issued for module 9
Router# 
00:31:11:%SNMP-5-MODULETRAP:Module 9 [Down] Trap
00:31:11:SP:The PC in slot 9 is shutting down. Please wait ...
00:31:25:SP:PC shutdown completed for module 9
00:31:25:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (admin
request)
00:31:28:SP:Resetting module 9 ...
00:31:28:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on
00:33:26:%SNMP-5-MODULETRAP:Module 9 [Up] Trap
00:33:26:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed
00:33:26:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are now
online
 
   

Step 4 After the NAM is back online, establish a console session with the NAM and log in to the root account.

Step 5 Upgrade the NAM maintenance image software as follows:

root@localhost# upgrade ftp-url 
 
   

where ftp-url is the FTP location and name of the NAM software image file.


Note If the FTP server does not allow anonymous users, use the following syntax for the ftp-url value: ftp://user@host//absolute-path/filename. Enter your password when prompted.


Step 6 Follow the screen prompts during the upgrade.

Step 7 After completing the upgrade, log out of the NAM.

Step 8 Boot into the maintenance image to reset the NAM maintenance image software with a command like the following:

Router# hw-module module 9 reset cf:1
Device BOOT variable for reset = cf:1
Warning:Device list is not verified.
 
   
Proceed with reload of module? [confirm]
% reset issued for module 9
 
   
Router# 
00:16:06:%SNMP-5-MODULETRAP:Module 9 [Down] Trap
00:16:06:SP:The PC in slot 9 is shutting down. Please wait ...
00:16:21:SP:PC shutdown completed for module 9
00:16:21:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (admin request)
00:16:24:SP:Resetting module 9 ...
00:16:24:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on
00:18:21:%SNMP-5-MODULETRAP:Module 9 [Up] Trap
00:18:21:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed
00:18:21:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are now online
Router# 
 
   

Step 9 (Optional) Verify the initial configuration after the NAM comes back online by logging into the NAM root account as follows:

root@localhost# show ip
 
   

Step 10 (Optional) Reboot into the application image as follows:

Router# hw-module module 9 reset
 
   

This example shows how to upgrade the NAM maintenance image software:

Router# 
Router# hw-module module 9 reset hdd:1
Device BOOT variable for reset = hdd:1
Warning:Device list is not verified.
 
   
Proceed with reload of module? [confirm]
% reset issued for module 9
Router# 
00:31:11:%SNMP-5-MODULETRAP:Module 9 [Down] Trap
00:31:11:SP:The PC in slot 9 is shutting down. Please wait ...
00:31:25:SP:PC shutdown completed for module 9
00:31:25:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (admin
request)
00:31:28:SP:Resetting module 9 ...
00:31:28:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on
00:33:26:%SNMP-5-MODULETRAP:Module 9 [Up] Trap
00:33:26:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed
00:33:26:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are now
online
Router# 
 
   
Router# session slot 9 proc 1
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 127.0.0.91 ... Open
 
   
Cisco Network Analysis Module (WS-SVC-NAM-2)
 
   
login:root
Password:
 
   
Cisco Network Analysis Module (WS-SVC-NAM-2) Console, 5.0
Copyright (c) 2010 by cisco Systems, Inc.
 
   
WARNING! Default password has not been changed!
root@localhost.cisco.com#
 
   
root@localhost.cisco.com# upgrade ftp://host/pub/c6svc-nam-maint.2-1-5.bin.gz
 
   
Downloading image...
ftp://host/pub/c6svc-nam-maint.2-1-5.bin.gz (11065K)
-                         [########################]   11065K |  837.65K/s
11331153 bytes transferred in 13.21 sec (837.64k/sec)
 
   
Uncompressing the image...
 
   
Verifying the image...
 
   
Applying the Maintenance image.
This may take several minutes...
 
   
Upgrade of Maintenance image completed successfully.
root@hostname.cisco.com# exit
 
   
Router# hw-module module 9 reset cf:1
Device BOOT variable for reset = cf:1
Warning:Device list is not verified.
 
   
Proceed with reload of module? [confirm]
% reset issued for module 9
Router# 
02:27:19:%SNMP-5-MODULETRAP:Module 9 [Down] Trap
02:27:19:SP:The PC in slot 9 is shutting down. Please wait ...
02:27:36:SP:PC shutdown completed for module 9
02:27:36:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (admin
request)
02:27:39:SP:Resetting module 9 ...
02:27:39:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on
02:29:37:%SNMP-5-MODULETRAP:Module 9 [Up] Trap
02:29:37:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed
02:29:37:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are now
online
Router# 

Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 BIOS Image Software


Note This section applies only to the WS-SVC-NAM-1 and WS-SVC-NAM-2 blades running a BIOS image prior to version 6.0.9.



Note The BIOS image is bundled with the NAM's maintenance image.


The NAM maintenance image software also provides upgrade software for your BIOS. If the show version command indicates a BIOS version below 4.0-Rel 6.0.9, see the following procedure for performing a BIOS upgrade:


Step 1 Boot the NAM to the maintenance image. Enter the following command from the Supervisor CLI:

hw-module module <module-number> reset cf:1

Step 2 After the NAM has booted the new maintenance image, session into the NAM module with the following Supervisor CLI command:

session slot <module-number> processor 1

Step 3 Log in as user root with the default password cisco.

Step 4 Enable the guest account (disabled by default) for the maintenance image. Enter the following command at the NAM maintenance CLI:

enable-guest


Note You can only perform the BIOS upgrade procedure from the guest account.


Step 5 Log out of the NAM CLI.

Step 6 Log in again as the user guest.

The default password for the guest account is cisco.


Warning While the new BIOS is being programmed, the procedure should not be interrupted in any way. Do not turn power off or shut down the NAM until the programming is complete.

A message such as BIOS programming complete displays when the procedure is finished, usually in less than two minutes.

Step 7 While logged into the guest account, enter the following command to begin the BIOS upgrade procedure:

upgrade-bios

Step 8 When prompted for the filename of the BIOS file to be programmed. Enter the following filename:

B01MQ009.ROM
 
   

Note In the above filename, use the digit 0, not the letter O, except for the .ROM extension which does use the letter O.


The following output shows an example of this procedure:

---------------------------------------------------------
guest@nam-test.cisco.com#upgrade-bios
Enter filename of BIOS file to be programmed: B01MQ009.ROM
Write BIOS File B01MQ009.ROM to Flash
 
   
WARNING: Removing or powering down this module during BIOS programming may resul t in the 
module unable to come online!
 
   
Erasing old BIOS...
Programming new BIOS...DONE
Verifying new BIOS...DONE
 
   
BIOS programming complete
guest@nam-test.cisco.com#
---------------------------------------------------------
 
   

Step 9 Log out of the NAM CLI (returning to the Supervisor CLI), and enter a command like the following to boot the NAM Application image:

hw-module module <module-number> reset hdd:1

Step 10 Enter the show version command to verify the BIOS was successfully installed.

show version

The output of the show version command should look something like the following:

BIOS Version: 4.0-Rel 6.0.9
 
   

This show version command output indicates that the most recent BIOS version (4.0-Rel 6.0.9) is installed.

You can now reboot the NAM Application image and resume normal NAM operation.


Upgrading ROMMON for Catalyst 6500 Series Switches

Cisco router ROM monitor (also known as ROMMON) runs when the router is powered up or reset. The firmware helps to initialize the processor hardware and boot the operating system software. You can perform certain configuration tasks, such as recovering a lost password or downloading software over the console port, by using the ROM monitor. If there is no Cisco IOS software image loaded on the router, the ROM monitor runs the router.

The BIOS and ROMMON images for the NAM-3 blade are bundled together, and are always installed in one process. To update the TriX86 Boot Firmware using the BIOS disk TFTP utility:


Step 1 Copy biosdisk_tri_x_y_z.bin to your TFTP server.

Step 2 Connect to the local TriX86 console.

Step 3 Break into TriX86 ROMMON if you are in an autoboot mode.

Step 4 Select the external ethernet interface port that is on your TFTP network (if not already the default port in ROMMON). This is done from the ROMMON CLI using the interface command.

Step 5 Set the ROMMON TFTP parameters:

local port IP address: addr w.x.y.z

server IP address: serv w.x.y.z

gateway IP address if applicable: gate w.x.y.z

file path on TFTP server: file userid/biosdisk_tri_x_y_z.bin

NAM management VLAN: vlan x

Step 6 Verify the connection to the server with a ping, using either ping server or ping w.x.y.z.

Step 7 TFTP boot the BIOS disk utility using the command tftpdnld.

Step 8 The BIOS disk will automatically reprogram the boot SPI flash, and then stop at the BIOS disk CLI prompt. Enter reboot after the installation is complete to reset the NAM.


Upgrading the NAM FPD Image for NAM-3/SUP2T

For NAM-3/SUP2T users, when installing a new NAM-3 with SUP2T and Cat6K-E chassis, a FPD error may display in the logs. A show mod shows the NAM-3 as powered down state. Follow the detailed steps below to resolve the issue.

The NAM 5.1(2) includes a separate FPD image that you can upgrade using Cisco IOS software on the switch.

Determining if an FPD Upgrade is Required

Upgrading the FPD Image Only

Determining if an FPD Upgrade is Required

Determine if an FPD upgrade is required using the show hw-module all fpd IOS command on the switch.

If the NAM has the minimum required version (NAM 1.10), no further action is necessary. If an FPD image package needs an upgrade, proceed to the next step.

The following non-VSS environment sample output indicates that the NAM does not meet the minimum version requirements.

Router# show hw-module all fpd
==== ====================== ====== =============================================
                             H/W   Field Programmable   Current   Min. Required
Slot Card Type               Ver.  Device: "ID-Name"    Version      Version
==== ====================== ====== ================== =========== ==============
   1 WS-SVC-NAM-3-K9 			 				1.0   1-TRISUL FPGA          1.8        1.10
==== ====================== ====== =============================================
 
   

In VSS environments, use the show hw-module switch <#> all fpd command.

Upgrading the Cisco IOS and FPD Image

If you need to upgrade the Cisco IOS image, you can also load a new FPD image on local flash memory (disk0: or bootdisk:) to automatically install the FPD on the NAM when you reload the switch.

Detailed Steps


Step 1 Verify that the FPD automatic upgrade feature is enabled by examining the output of the show running-config IOS command on the switch.

Look for the "upgrade fpd auto" line in the output. If there are no upgrade commands in the output, upgrade fpd auto is enabled because it is the default setting. If automatic upgrades are disabled, use the upgrade fpd auto command to enable automatic FPD upgrades.

Step 2 If you have a Cisco.com login, you can obtain the FPD image from the following website:

http://www.cisco.com/cisco/software/release.html?mdfid=283933147&flowid=29364&softwareid=280805682&release=15.0.1-SY1&relind=AVAILABLE&rellifecycle=ED&reltype=latest

Step 3 Download the FPD image package to local flash memory on the switch.

See the switch documentation for more information about downloading files to flash memory.


Note Do not change any FPD-related settings on your system. If the default settings for the upgrade fpd path command have been changed, change the settings back to their default settings using the no form of this command.


Step 4 Obtain the Cisco IOS image from the following website:

http://www.cisco.com/cisco/software/release.html?mdfid=283933147&flowid=29364&dvdid=282804709&softwareid=280805685&release=15.0.1-SY1&relind=AVAILABLE&rellifecycle=ED&reltype=latest

See the switch documentation for information about loading the new IOS image.

Step 5 Reload the switch using the new IOS image.

When Cisco IOS boots, it searches for the FPD image package in flash. The switch updates the FPD images automatically as part of the Cisco IOS boot process.


Upgrading the FPD Image Only

If you do not need to upgrade the Cisco IOS image, you can upgrade the FPD image separately.

Restrictions

The FPD image must be in local flash memory. Remote upgrading from FTP or TFTP is not supported.

Detailed Steps


Step 1 If you have a Cisco.com login, you can obtain the FPD image from the following website:

http://www.cisco.com/cisco/software/release.html?mdfid=283933147&flowid=29364&softwareid=280805682&release=15.0.1-SY1&relind=AVAILABLE&rellifecycle=ED&reltype=latest

Step 2 Download the FPD image package to the switch flash memory. We recommend the local flash disk (disk0: or bootdisk:).

See the switch documentation for more information about downloading files to flash memory.

Step 3 Verify the contents of the FPD image package using the following command:

Router# show upgrade fpd file file-url
 
   

The file-url argument is the location and name of the FPD image package file. For example, the following command successfully verifies the image (see the TRIFECTA card type for the NAM):

Router# show upgrade fpd file disk0:<c6500-fpd-pkg.1.10.pkg>
 
   
Cisco Field Programmable Device Image Package for IOS
C6500 Family FPD Image Package (c6500-fpd-pkg.1.10.pkg), Version 15.0(0)SY99.41
Copyright (c) 2004-2012 by cisco Systems, Inc.
Built Thu 19-Apr-2012 14:46 by integ
 
   
 
   
=============================== ================================================
                                        Bundled FPD Image Version Matrix
                                ================================================
                                                                       Min. Req.
Supported Card Types            ID  Image Name                Version  H/W Ver.
=============================== == ========================= ========= =========
2-port T3/E3 Serial SPA          1 T3E3 SPA ROMMON              2.12      0.0
                                 2 T3E3 SPA I/O FPGA            0.24      0.0
                                 3 T3E3 SPA E3 FPGA             1.4       0.0
                                 4 T3E3 SPA T3 FPGA             1.4       0.0
------------------------------- -- ------------------------- --------- ---------
4-port T3/E3 Serial SPA          1 T3E3 SPA ROMMON              2.12      0.0
                                 2 T3E3 SPA I/O FPGA            0.24      0.0
                                 3 T3E3 SPA E3 FPGA             1.4       0.0
                                 4 T3E3 SPA T3 FPGA             1.4       0.0
...
------------------------------- -- ------------------------- --------- ---------
TRIFECTA                         1 Trifecta  DPFPGA             1.10      0.0
=============================== ================================================
 
   

Step 4 Upgrade the FPD using the following command:

Router# upgrade hw-module slot slot-number fpd file file-url
 
   

The slot-number argument indicates the chassis slot location of the NAM. The file-url argument is the location and name of the FPD image package file. For example, to upgrade the NAM in slot 2, enter the following command:

Router# upgrade hw-module slot 4 fpd file disk0:<c6500-fpd-pkg.1.10.pkg>
% The following FPD will be upgraded for WS-SVC-NAM-3-K9 (H/W ver = 1.1) in slot 4:
 
   
 ================== =========== =========== ============ 
 Field Programmable   Current     Upgrade   Estimated 
 Device: "ID-Name"    Version     Version   Upgrade Time 
 ================== =========== =========== ============ 
 1-TRISUL FPGA          1.8         1.10      00:06:30
 ================== =========== =========== ============ 
 
   
% NOTES:
  - Use 'show upgrade fpd progress' command to view the progress of the FPD
    upgrade.
   - Since the target card is currently in disabled state, it will be 
     automatically reloaded after the upgrade operation for the changes to 
     take effect.
 
   
WARNING: The target card will be reloaded in order to start FPD image 
         upgrade. This action will interrupt normal operation of the card.
         If necessary, ensure that appropriate actions have been taken to 
         redirect card traffic before starting the upgrade operation.
 
   
% Are you sure that you want to perform this operation? [no]: yes
% Reloading the target card for FPD image upgrade ... Done!
% Upgrade operation will start in the background once the target card gets 
  initialized after the reload operation. Please wait ...
  (Use "show upgrade fpd progress" command to see upgrade progress)
 
   

Step 5 Verify that the FPD upgrade is complete using the following command:

Router# show upgrade fpd progress
 
   

The following example shows that the FPD upgrade is updating:

Router# show upgrade fpd progress
 
   
FPD Image Upgrade Progress Table:
 
   
 ==== =================== ====================================================
                                               Approx.
                          Field Programmable    Time     Elapsed
 Slot Card Type           Device : "ID-Name"   Needed      Time    State
 ==== =================== ================== ========== ========== ===========
    2 WS-SVC-NAM-3-K9 						1-TRISUL FPGA       00:06:30   00:00:24  Updating...
 ==== =================== ====================================================
 
   

The following example shows that the FPD upgrade is complete, because the upgrade is no longer in progress:

Router# show upgrade fpd progress
 
   
% There is no FPD image upgrade in progress.
 
   

Step 6 Verify that the FPD upgrade was successful using one of the following commands:

Router# show module
 
   

or

Router# show module switch <#>
 
   
 
   
Mod Ports Card Type                              Model              Serial No.
 
   
--- ----- -------------------------------------- ------------------ -----------
 
   
 1   24  CEF720 24 port 1000mb SFP              WS-X6824-SFP       SAL1533MAUM
 2   24  CEF720 24 port 1000mb SFP              WS-X6824-SFP       SAL1533MAU0
 3   16  CEF720 16 port 10GE                    WS-X6816-10GE      SAL1549XGLV
 4    4  Trifecta NAM Module                    WS-SVC-NAM-3-K9    SAL1552ZJAH
 6    5  Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G       SAL160855QC
 
   
 
   
Mod MAC addresses                       Hw    Fw           Sw           Status
 
   
--- ---------------------------------- ------ ------------ ------------ -------
 
   
 1  0007.7d90.55a8 to 0007.7d90.55bf   1.0   12.2(18r)S1  15.0(1)SY1   Ok
 2  0007.7d90.53f8 to 0007.7d90.540f   1.0   12.2(18r)S1  15.0(1)SY1   Ok
 3  70ca.9bc5.75c0 to 70ca.9bc5.75cf   1.1   12.2(18r)S1  15.0(1)SY1   Ok
 4  e8b7.4829.3140 to e8b7.4829.314f   1.1   12.2(50r)SYL 15.0(1)SY1   Ok
 6  588d.098a.d6e6 to 588d.098a.d6ed   1.2   12.2(50r)SYS 15.0(1)SY1   Ok
 
   
Mod  Sub-Module                  Model              Serial       Hw     Status
 
   
---- --------------------------- ------------------ ----------- ------- -------
 
   
 1  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1538QPEG  1.1    Ok
 2  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1538QPET  1.1    Ok
 3  Distributed Forwarding Card WS-F6K-DFC4-E      SAL1552ZEWA  1.1    Ok
4/0 NAM Application Processor   SVC-APP-PROC-1     SAL1540RPLV  1.0    Ok
 6  Policy Feature Card 4       VS-F6K-PFC4        SAL16084WD3  1.1    Ok
 6  CPU Daughterboard           VS-F6K-MSFC5       SAL160859J3  1.3    Ok
 
   
Base PID:
 
   
Mod  Model         Serial No.
 
   
---- -----------   ----------
 
   
4 WS-SVC-APP-HW-1    SAL1552ZJAH
 
   
Mod  Online Diag Status
 
   
---- -------------------
 
   
 1  Pass
 2  Pass
 3  Pass
 4  Pass
4/0 Pass
 6  Pass
 
   
Router#
 
   

If you are using a VSS environment, see Determining if an FPD Upgrade is Required for details on the IOS command to use.


Limitations and Restrictions

The following limitations and restrictions currently apply to the NAM 5.1(2) software release:

NAM Creates Capture File on Cancel

NAM Support With Non-Cisco H.323 Voice Devices and Call Managers

ACS Version Supported

Direct Flow Packets to NAM Data Port

No Default CLI Password

Response Time and Voice Quality Analytics

Intelligent Application Performance (IAP)

Checking the NAM Maintenance Image and BIOS Versions

NAM Appliance Support for Cisco Nexus 7000

Restrictions for NME-NAMs

IOS Issues That Might Affect NAM 5.1(2)

Most Recent NAM 5.1(2) Information

NAM Creates Capture File on Cancel

If you are using a Cisco 2200 Series appliance, and during Capture > Packet Capture/Decode > Files you click on the Download button, a xxx.pcap file is created regardless of whether you accept the download action or cancel it. This is why one capture done from a Cisco 2200 Series appliance may have an extra file, while another from a different platform may not.

NAM Support With Non-Cisco H.323 Voice Devices and Call Managers

NAM voice call monitoring may not function properly with some of the non-Cisco voice devices and Call Managers such as Avaya. This is only for non-Cisco voice devices. Cisco IP Phone and Call Managers do not have any problems.

ACS Version Supported

ACS server versions supported are ACS versions 5.2, 5.1, and 4.2.

Direct Flow Packets to NAM Data Port

If you use a NAM-2 device, either WS-SVC-NAM-2 or WS-SVC-NAM-2-250S, we recommend that you direct all packets for the same flow to the same data port.


Note This issue applies only to the WS-SVC-NAM-2 and WS-SVC-NAM-2-250S NAM models.


NAM-2 devices have two data ports (DATA_PORT1 and DATA_PORT2), but the packets received on these two ports are not well merged in respect to the order in which the packets are received. When packets for a given flow are split into two data ports, it might impact the calculation of application response time (ART) metrics and voice quality metrics.

No Default CLI Password

For security purposes, beginning with NAM 4.1, we no longer provide a default root password. After you install NAM 5.1(2), you must specify a password for the root account. Store this password in accordance with your site's security policies. You will need the root account password for additional software upgrades.

Response Time and Voice Quality Analytics

The calculation of Application Performance Response Time and voice quality metrics in NAM 5.0 depends on the actual packet arrival time and packet sequences. In events such as packet drops, duplicated packets, or asymmetric routing, the NAM might not be able to calculate accurate quality metrics for the associated polling interval.

You should pay attention to the NAM syslog messages and system alerts to remain aware of any packet drops or duplicated packets occurrences.

Intelligent Application Performance (IAP)

For IAP, also referred to as Application Response Time (ART), due to the way NAM 5.1(2) processes packets in a TCP connection, response time monitoring on WAAS data sources probably will not include the first response of the TCP connection. This occurs because the WAAS optimization engine might not be able to determine to which optimized or non-optimized segment the first few packets belong.

This issue will be noticed when you monitor a TCP connection that has only a single response. No response time will be reported for this connection. The NAM determines response time by taking the average response time over multiple TCP connections. Because most TCP connections have multiple responses, this issue is generally unnoticed over a longer period of monitoring.

Checking the NAM Maintenance Image and BIOS Versions

NAM 5.1(2) software requires that you use the correct NAM maintenance image and BIOS versions. The recommended BIOS version for NAM 5.1(2) software is BIOS 6.0.9.

The recommended maintenance partition (MP) version depends on the NAM model. See Table 10 for the recommended maintenance image for each NAM platform. If you need to upgrade your NAM-1/-2 maintenance image, see Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image Software.

NAM Appliance Support for Cisco Nexus 7000

With the deployment flexibility the Cisco NAM 2200 Series appliances offer, you now have a NAM solution to gain visibility into network and application performance for the Cisco Nexus 7000 Series switches. The Cisco NAM 2200 Series appliances provide core NAM functionality to support the Cisco Nexus 7000 Series including monitoring, reporting, capturing data and alarms. The NAM appliances support features such as traffic analysis, Intelligent Application Performance (IAP) monitoring, differentiated services analysis, and voice quality monitoring. The same NAM software image supports all tested infrastructure devices.

The Cisco NAM 2200 Series appliances do not yet offer the same level of management interface support they offer other tested devices, such as the Catalyst 6500 Series switches. This affects the following NAM functions:

Configuring a SPAN session on the Nexus 7000 Series using the NAM GUI. Instead, use the switch CLI to configure such a session.

Configuring and displaying alarms about the managed device.

Support for both NBAR-PD and MPLS functionality is not available for the Nexus 7000.

Restrictions for NME-NAMs


Note This restriction applies only to traffic that is monitored through the internal NAM interface on the NME-NAM-120S.


The NAM provides Layer 3 and higher layer information about the original packets. The Layer 2 header is modified by the router when it forwards the packets to the NAM, so the Layer 2 information that the NAM records is not applicable to the original packets.

Most Recent NAM 5.1(2) Information

To see the most recent version of the NAM 5.1(2) User Guide, see the technical documentation for the Network Analysis Module on www.cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps5401/tsd_products
_support_series_home.html

IOS Issues That Might Affect NAM 5.1(2)

The following IOS issues might affect your use of NAM 5.1(2) depending on other software versions.

IOS Image Incompatibility Prevents Creating SPAN Data Sources Using NAM GUI

Cisco 7600 With Redundant Supervisor Cards Running IOS Image 12.2(33)SRC2

Running IOS Image Newer Than 12.2(18)SXF5

RSPAN and ERSPAN Unsupported in IOS Image 12.2(33)SRD

IOS Image Incompatibility Prevents Creating SPAN Data Sources Using NAM GUI

An issue with the supervisor card and IOS images 12.2(18)SXF9 and 12.2(33)SRB1 prevents you from creating SPAN data sources (SPAN sessions) using the NAM GUI. (This issue is described in CSCse98807.)


Note This issue has been resolved with IOS image 12.2(18)SXF10.


You can also use switch command-line interface (CLI) commands to create SPAN sessions, or you can use other IOS releases on the supervisor card, such as 12.2(18)SXF10 or 12.2(33)SRB2, that fix this IOS issue.

On affected systems, when you attempt to use the NAM GUI to create a SPAN session by choosing
Setup > Data Source and clicking Create, the NAM GUI displays no information for the Destination Port. This prevents you from creating the SPAN session.

Cisco 7600 With Redundant Supervisor Cards Running IOS Image 12.2(33)SRC2

You might experience an error condition with a Cisco 7600 chassis that has redundant supervisor cards running the 12.2(33)SRC2 IOS image and a NAM service blade. The error occurs when you perform a sequential boot of the two supervisor cards because the secondary (standby) supervisor does not go into proper standby mode.

You can find more information about this issue in Field Notice #63179.


Note This issue has been resolved in 12.2(33)SRC3.


This problem does not occur:

When you boot the two supervisor cards in parallel

When you boot the standby supervisor card after the primary supervisor is up

When the Cisco 7600 router runs the 12.2SRC1 image

When only one supervisor card is installed in the Cisco 7600 chassis

Problem Symptom

When the primary supervisor functions as a standalone with the secondary supervisor card in RPR mode, the Cisco 7600 chassis functions normally (as if it has a standalone supervisor card). A switchover causes the system to be unavailable for up to three minutes because the secondary supervisor card is not in proper standby mode.


Note When both supervisors are booted simultaneously, the system will go to Hot Standby status. The primary supervisor will reboot when you issue the redun force-switchover command which causes the redundant supervisor to boot up to be the primary and the primary to be the redundant.


Solution

This problem requires you to downgrade the IOS image from 12.2SRC2 to 12.2SRC1. Account teams will help you do this if needed.

Running IOS Image Newer Than 12.2(18)SXF5

If you upgrade your IOS to an image newer than 12.2(18)SXF5, you remain vulnerable to a security issue where IOS switches the SNMP communication between the NAM and the SUP from inband to EOBC.

Due to this issue, you should not apply the NAM CLI command supervisor address <sup-address>. To remove this configuration from the NAM, use the negating form of the command,
no supervisor address.


Note This issue has not yet been resolved.


RSPAN and ERSPAN Unsupported in IOS Image 12.2(33)SRD

The ERSPAN command is not working properly in NAM 5.1(2) when using IOS image 12.2(33)SRD. The problem is noticed when you attempt to configure a destination on the NAM in ERSPAN or RSPAN sub-mode.

After issuing the command:

destination analysis-module 3 data-port 1

Where module 3 is the NAM you have set up to monitor (using the command monitor session 1 type erspan-destination), the configured destination cannot be found.

This problem also affects the local SPAN (with sub-mode configuration).


Note This issue has been resolved with IOS image 12.2(33)SRD1 or later.


Caveats

This section provides information about active anomalies in the NAM 5.1(2) software.

Known Anomalies in NAM 5.1(2)

Resolved Anomalies in NAM 5.1(2)

To obtain more information about known problems, access the Cisco Software Bug Toolkit at the following URL:

http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl

Known Anomalies in NAM 5.1(2)

Table 12 provides a list of known anomalies in NAM 5.1(2) software. Each anomaly includes a description of the symptom, conditions in which the anomaly occurs, and any workaround.

Table 12 Known Anomalies in NAM 5.1(2) 

Bug ID
Description
CSCtt02897

Intervals displayed using a show counter command are counted twice.

Workaround: Manually calculate the correct counter interval by dividing the number by two.

CSCts99960

Alarm trigger time is not adjusted for client time. Alarm clear time displays correctly.

Workaround: Synchronize client time with NAM system time.

CSCts99943

Schedule export doesn't show the same data for NDE interface stat.

In the NAM Analyze > Traffic > NDE Interface, there are several inconsistencies. The Schedule Export should comply with NDE interface stat page. When it shows % Utilization, the report should be the same.

CSCts99874

NAM does not receive any DCSP type alarms.

NAM alarms work properly when the DSCP group contains only one DSCP number. Currently, each DSCP group includes more than one DSCP number. To fix this problem, create a user-defined DSCP group instead of using system-predefined DSCP group, as follows:

1. Create a new DSCP group which contains only one DSCP number. This DSCP number will be associated with the alarm.

2. Create a DSCP alarm associated to the new DSCP group.

CSCts99743

On the Analyze > Voice Call Statistics page, the packet loss percentage could be over 100 percent in the Top N End Points by Packet Loss (%)and Top N Calls by Packet Loss (%) charts. This data comes directly from the Call Manager (or should it be Communications Manager?) to NAM. You should check the CM configuration to address the packet loss issue.

CSCts97278

Interface Stat shows no interface name for some entries (1 day, 1 week). There is no workaround.

CSCts96724

Install ing SM-SRE from an IOS router fails. Use the helper application to install NAM.

CSCts96711

Unnecessary error message about network not being set after using the SM-SRE helper to install. It is safe to ignore this message.

CSCts95931

NDE Data source of Nexus 1K device cannot be auto-created. There is no workaround.

CSCts87308

iSCSI storage becomes unformatted after NAM blade reboot from SUP.

Workaround: From NAM CLI, run fsck command and reboot the NAM blade to pick up the mounted filesystems.

CSCts86952

NAM datasource advance filter display problems.

CSCts86302

No error displays when you set syslog alarm action without syslog server set up.

CSCts81057

Inconsistent message displays when disabling HTTPS server.

CSCts80603

File rotation option support per platforms issue.

CSCtr92947

Select All function should not active if there is no data to select.

CSCts80133

V9 Export filter issues.

CSCts76767

nbd error messages for NME-NAM-120S after installing NAM image

CSCts73141

VSB should remove data port as a source for capture session.

CSCts65530

Identical labels should not be allowed in the same NAM.

CSCts65528

iSCSI external storage limitations exist on the 32-bit platform. These include:

Each IQN can only have one LUN (disk).

32-bit platform NAM (NAM-1/-2) cannot read external storage which was previously formatted by a 64-bit platform NAM device. As a result, interchanging external storage between 64-bit platform and 32-bit platform is not supported.

CSCts56389

MP 2.1(5) is required to install NAM 5.1(2) on a NAM-1 or NAM-2. You cannot install with MP 2.1(3). To upgrade, see Upgrading Catalyst 6500 and Cisco 7600 NAM-1 and NAM-2 Maintenance Image Software.

CSCts47270

Application Groups Details table shows one more app group.

CSCts36146

DATA COLLECTOR error messages are seen in NAM-3.

CSCts28945

SA export causes main process (mond) to reboot.

Workaround: Use the standard NBI API for SA.

CSCtr26475

Extra step to bring up RTP Conversation Details screen. You must click RTP Conversation Details in a pop-up window to bring up the detailed information.

CSCts24979

5.1(2) NAM-1/-2 non-reformat upgrade has read-only error messages. You can ignore these messages.

CSCtr13732

No display of Managed Device Health and IF info with SNMPv3 enabled.

Cisco 22xx appliances and NME-NAM have issues when Managed Device feature is configured with SNMPv3 support.

On 22xx appliances:

The Analyze > Managed Device > Health > Managed Device Information page does not display.

The Analyze > Managed Device > Interface page does not display.

On NME-NAM:

Fan status is missing on Analyze > Managed Device > Health > Router Health page.

The Analyze > Managed Device > Health > Router Information page does not display.

The Analyze > Managed Device > Interface page does not display.

CSCtq30121

When the VPN-SPA (shared port adapter) module is present, the NAM-3 doesn't recognize its interfaces as configurable SPAN sources. However, once the configuration is done via CLI, the status is reported in the GUI.

There is no workaround.

CSCtq27947

Changing the System Time may cause the NAM-3 to restart.

There is no workaround.

CSCtq22111

Buffer I/O errors are seen in a reverse telnet session on the NAM-3.

Reverse telnet is a new feature added for Cisco IOS that supports the NAM 5.0(1T) release. It is similar to a console to the NAM.

There is no workaround.

CSCtq15493

The nslookup may not function when using hostname. Some hostnames cannot be resolved by the DNS and some SQL errors are seen in some pages. The problem has been seen in the following pages.

Analyze > Response Time > Client-Server

Analyze > Response Time > Client

Analyze > Response Time > Server

Analyze > WAN Optimization > Conversation Multi-segments (the GUI shows "No data available" but the SQL error is seen in the log file)

CSCto72361

After you delete a site, an interactive report cannot be saved.

If you create two sites on the NAM (Site A and Site B), create and save an interactive report with Site A as the source, create and save an interactive report with Site B as the source, and then delete Site A and try to save another interactive report, after clicking the Submit button, nothing happens.

There is no workaround.

CSCto59473

The NAM-3 fails to send the alarm trap to the server.

If you set up a trap server on the NAM, set an Alarm action to send the trap out, and check the server when alarm happens, the trap is not found on the server. When you set up a syslog to send to the same server for an Alarm, it functions properly.

There is no workaround.

CSCto59439

The incorrect clear time is shown in the Alarm Table.

On the Alarm Summary page (Monitor > Overview > Alarm Summary), scroll down to the Last 50 Alarms table, and click the All Alarms button to launch the "All Alarms" table. If a new alarm is triggered but not cleared, the clear time will show "-". If the time range is less than or equal to the last hour, the table shows "-" correctly. If the time range is set to greater than or equal to the last four hours, the NAM shows the incorrect clear time, which is even earlier then the trigger time.

There is no workaround.

CSCto54858

The NAM information in the IOS show module output is missing some information. The "Mod Online Diag Status" shows "Bypass" for Modules 1-4, and Module 2 is missing from the Sub-Module.

CSCto46833

In the Response Time Details table, the preference is set to Bits, but it shows "Client/Server Bytes" with bits information.

CSCto46831

When you use the Internet Explorer 8 browser to view the NAM GUI, and go to Analyze > Managed Device > NBAR, you do not see any data.

The workaround it to use the Mozilla Firefox browser for this function (it works using Firefox 3.6.x).

CSCto40292

The Capture Session action NBI is not working. The actions are changed from the NAM 4.x to NAM 5.x.

The workaround is to use the NAM web GUI for Capture actions.

CSCto23030

VSB/VB NAM can only handle the NDE/ERSPAN traffic. NAM does not support voice/video for NDE/ERSPAN source traffic. Any setting related to voice/video on VB/VSB should be ignored.

CSCtn79004

In the NAM, on the Monitor > Traffic Summary page, when the Interactive Report time range is less than 24 hours, starting from NOW going backward to the past, all the top N charts data are fine. However, sometimes when the time range is not starting from NOW, for example Custom to view 3 days ago data, the Host Top N chart may display no data but others are OK.

This occurs when viewing data with long term (more than 24 hours) window.

There is not workaround.


Resolved Anomalies in NAM 5.1(2)

Table 13 provides a list of resolved anomalies in NAM 5.1(2) software.

Table 13 Resolved Anomalies in NAM 5.1(2) 

Bug ID
Description
CSCts90039

Alarm entries clear time display is fixed.

CSCts80603

Correct file rotation option support per platforms.

CSCts80528

Remote Storage Volume feature is now removed.

CSCts77400

iSCSI storage mounts successfully after reboot.

CSCts73283

iSCSI drive mounts successfully on SM-SRE NAM.

CSCts72997

Last 50 alarms now filters by severity.

CSCts70492

NetFlow interval is now the same as the short term aggregation interval.

CSCts70470

Sending NetFlow template every 10 short term interval has been fixed.

CSCts67974

Module igb displays in /proc/modules on NAM-3.

CSCts65499

After NAM is rebooted the In Use status of external storage displays properly.

CSCts64536

Show vsb name of a NAM VSB no longer displays domain ID field

CSCts59168

Auto-mount iSCSI works properly after NAM reboot.

CSCts59034

Monitoring Rate data calculation works properly.

CSCts54358

5.1(2): Storage button/dialog/CLI name changes

CSCts51205

Unwanted external storage checking messages fixed.

CSCts51039

Show debug counters for SM-SRE NAM now show NIC counters.

CSCts45240

External storage volume has been removed from the release.

CSCts45031

WAAS VB can install AP image from helper successfully.

CSCts44687

SM-SRE displays helper info from show version command.

CSCts44627

SM-SRE: ip interface command works correctly.

CSCts44336

NTP is synchronized after a boot occurs.

CSCts38823

New message displays for option #2 from helper regarding Hard Disk requirements.

CSCts36058

Converted file status displays correctly.

CSCts33481

5.1(2) - /nbi/nbi-capture/swfilter/id/4 update filter works properly.

CSCts33194

Traffic rates in time charts display properly.

CSCts33123

napatech: NAM main process stops processes correctly.

CSCts32090

Improved CLI message for sync ptp on unsupported platform implemented.

CSCtr29513

Re-enable iSCSI works correctly.

CSCts28945

SA export NAM main process works properly.

CSCts27520

Unrecognizable server name has been fixed.

CSCts21061

Delete capture file NBI API returns works properly.

CSCts19431

UCS-related CLI commands disabled in 5.1(2).

CSCts19159

Total Disk Size displays correctly.

CSCts14368

You can now disable monitor voice & ART from the CLI.

CSCts13645

Improved CLI messages in monitor voice.

CSCts09744

iSCSI captures work properly.

CSCts07155

Unique storage label enforcement works properly.

CSCtr92816

5.1(2)CLI.csv-export should be removed from preference setting.

CSCtr92627

Duplicate hardware filter entries can no longer be created.

CSCtr68554

All captured packets are displayed in capture wrap-around mode.

CSCtr65354

Interface View page displays correct information in Analyze > Traffic > NDE Interfaces.

CSCtr29549

Enhanced CLI show debug counter.

CSCtr21313

SSL key generation has been changed to 2048 bits.

CSCtr18947

Disabled Capture for WAAS VB.

CSCtr13769

NAM main process works properly on appliances.

CSCtr11513

Cross launching from Operations Manager no longer causes an error code to display.

CSCtr08386

Fixed CLI.Preference. incorrect number of graph bars.

CSCtq98631

Napatech driver updated for NAM appliances.

CSCto92535

Fixed NAM ntp service vulnerability to CVE-2009-3563.

CSCtq87174

SM-SRE full installation is no longer an issue.

CSCtq81929

Upgrade no longer fails for platforms with 2 GB or less memory.

CSCtq78774

show version shows correct local disk & memory size.

CSCtq76567

WCM/NAM 5.1 application synchronization now works properly.

CSCtq70471

Telnet session works properly with show tech.

CSCtq28034

Fixed a memory leak caused by NetFlow Data Export.

CSCtq22021

Host Conversation screen title correctly shows Cumulative units for Rate.

CSCtq14085

Added iSCSI as part of storage subsystem.

CSCtq06446

Fixed the issues with NAM 5.0 and 5.1 scheduled reports.

CSCto78831

Fixed NAM-3:/usr/local/nam/bin/httpd: line 47: kill: (6373) - No such process.

CSCtn93651

Fixed Linux kernel panic on 5.0(1T) NAM console when browsing NAM GUI.


Documentation Updates

Review the Caveats and Limitations and Restrictions section for required critical information. This information is not available in the documentation that was included with the product image. The following information was added to the release notes after the documentation was released.

Updates for NAM 5.1(2) Installation and Configuration Guides/Notes

Updates for NAM 5.1(2) User Guide

Updates for NAM 5.1(2) Installation and Configuration Guides/Notes

These updates will be included in all platform Installation and Configuration Guides in the next release.

The platform-specific installation and configuration documentation changes for NAM 5.1(2) appear below. You can use the existing NAM 5.1 guides/notes for this release, but they do not include the following changes:

The "Installing and Configuring External Storage" section in the Cisco installation and configuration guides do not include the iSCSI support for all platforms that were added in this release. See the "Capture Data Storage Setup" in the Cisco Prime Network Analysis Module User Guide 5.1(2).

The NAM now supports up to 32 LUNs between all protocols.

The update-inventory command has been removed. Storage additions and removals are detected automatically for SAS and FCoE. iSCSI requires a Login/Logout step; see Preparing External iSCSI Storage for step-by-step details.

Preparing External iSCSI Storage

This section provides an overview of how to manually prepare your external iSCSI storage information to work with NAM. Use your vendor's user guide to ensure you have properly configured the iSCSI array. The NAM is independent of most array settings, but some are important for accessibility and performance.

1. To configure the Logical Unit Numbers (LUNs) on the array, there is often a Segment Size setting. Larger segment sizes can improve write speeds. We recommend you configure the Segment Size setting to the largest segment size possible (up to 512KB).

Multiple LUNs can be configured on a single array.

2. Map the LUNs to iSCSI Qualified Names (IQNs) on the array. Each IQN represents a different list of LUNs for hosts (such as the NAM) to access.

3. The NAM supports up to 32 LUNs between all protocols. For 32-bit NAM platforms map only one LUN per IQN. The 64-bit platforms support multiple LUNs mapped to one IQN.

4. The NAM also has an IQN, which represents the host side of an iSCSI session. Ensure you map each NAM's IQN to the LUNs for host read-write access. Most storage arrays require this for security reasons, to ensure that only certain hosts can access the LUNs. Each NAM has a unique IQN, so perform this step for each NAM that requires access and for each target LUN that is to be accessed. See Locating the NAM IQN for more details on what CLI command to use.

5. Set the IP path to the NAM management port. See Connecting the Storage Array for details.


Locating the NAM IQN

To find the NAM IQN use the remote-storage iscsi local-iqn CLI command:

root@nam.domain# remote-storage iscsi local-iqn
Local iSCSI Qualified Name: iqn.1987-05.com.cisco:WS-SVC-NAM3-6G-K9.00:19:55:07:15:9A
 
   

Connecting the Storage Array

After you configure the iSCSI storage arrays, ensure it has an IP path to the NAM management port. Use the correct host-connect port on the array as indicated in your vendor's user guide. The array can be connected while the NAM is running.

Some arrays come with multiple storage controller modules. As a security feature, module ownership must often be mapped to each LUN.

The NAM logs into the storage to start an iSCSI session using the IP address and IQN(s) of the storage array. To connect the storage array using the user interface, follow these steps:

1. Log into the NAM web interface. To access the Data Storage page, select Capture > Packet Capture/Decode > Data Storage.

2. Click the iSCSI Login button and enter the target IP and IQN.

The storage table refreshes with the newly discovered LUNs.

If the LUNs do not appear, do the following:

Check remote-storage iscsi list to verify the iSCSI session was properly started.

If so, check the storage array configuration to verify that the LUNs are mapped to the target IQN and the NAM IQN has been given Read/Write access to the LUNs.

If you make any configuration changes, logout of the iSCSI session and login again. To logout, use the CLI remote-storage iscsi logout. If the LUNs appear on the user interface, you can select one of them and click iSCSI Logout. All LUNs mapped to that target IQN will be disconnected.

The follow examples shows how to verify the iSCSI session.

root@nam.domain# remote-storage iscsi list
Storage ID: 16
     Label:
    Status: Ready
 Protocol: ISCSI
 Target IP: 172.20.122.81
Target IQN: iqn.2011-09:celeros.target11
      Type: LUN
     Model: IET VIRTUAL-DISK
       LUN: 4
 Capacity: 24.98GB
 Available: 24.98GB
 
   
Active iSCSI Sessions:
tcp: [8] 172.20.122.81:3260,1 iqn.2011-09:celeros.target11
 
   

The LUN number (in the above example, LUN 4) can help you identify one LUN from others of the same IQN. This number is unique to each IQN, meaning two LUNs from different IQNs can have the same number.

You can now use the iSCSI external storage from within the NAM. See the Cisco Prime Network Analysis Module User Guide for more information.

Updates for NAM 5.1(2) User Guide

Several updates were made to the User Guide. To view the latest information, see the latest documentation on Cisco.com.

Capture Source Field

In Table 4-3, "Capture Settings Fields," the Capture Source usage notes are missing support for SM-SRE. The correct information appears below:

Catpure Source

Data-Port of ERSPAN

Choose the capture source (check one or more check boxes):

Data-port: This accepts SPAN, RSPAN, and VACL capture. For NME-NAM and SM-SRE, internal, external, or both.

ERSPAN: Locally terminated is recommended.


Documentation

Cisco Prime Network Analysis Module Software 5.1(2)

This section provides a list of the Cisco Prime Network Analysis Module Software 5.1(2) software documentation. You can find links to all NAM software documentation at the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps5401/tsd_products
_support_series_home.html

The following is a list of the documentation, in the order in which you should address it.

Cisco Prime Network Analysis Module Release Notes 5.1(2)

Cisco Prime Network Analysis Module User Guide 5.1(2)

Cisco Prime Network Analysis Module Command Reference 5.1(2)

Cisco Prime Network Analysis Module Software API Programmer Guide 5.1

Cisco Prime Network Analysis Module Software 5.1(2) Third Party and Open Source Copyright Notices


Note Only a sub-set of the documentation was revised for 5.1(2). For installation and configuration updates for all platforms, see Updates for NAM 5.1(2) Installation and Configuration Guides/Notes.


Cisco Prime Network Analysis Module Release Notes

OL-25929-03

The Cisco Prime Network Analysis Module Release Notes (this document) provides a collection of information including software and hardware compatibility and information about new features, requirements, and anomalies that might exist.

http://cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.1_2/release/notes/
nam512note.html

Cisco Prime Network Analysis Module User Guide

OL-25961-01

The Cisco Prime Network Analysis Module User Guide describes how to use the Cisco Prime Network Analysis Module and NAM 5.1(2) user software.

http://cisco.com/en/US/docs/net_mgmt/network_analysis_module
_software/5.1_2/user/guide/nam512_ug.html

Cisco Prime Network Analysis Module Command Reference

OL-24400-01

The Cisco Prime Network Analysis Module Command Reference provides information about how to use the NAM command-line interface to manage the NAM devices supported by NAM 5.1(2) software.http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.1_2/
command/reference/guide/cmdref.html

Cisco Prime Network Analysis Module Software API Programmer Guide 5.1

OL-24408-01

The Cisco Prime Network Analysis Module API Programmer Guide describes APIs that are available to connect to the NAM system. The NAM API provides a mechanism for provisioning and retrieving data from the NAM servers using an eXtensible Markup Language (XML) interface. The API utilizes REpresentational State Transfer (REST) methodology to execute requests (web services) over HTTP or HTTPS by sending the XML data to the API server.

The developers who use the APIs should have an understanding of a high-level programming language such as Java or an equivalent.

The Cisco Prime Network Analysis Module API Programmer Guide is available on the Cisco NAM Technology Center. The Cisco NAM Technology Center is an online resource for additional downloadable Cisco NAM support content, including help for developers who use Cisco NAM application programming interfaces (APIs). The website provides information, guidance, and examples to help you integrate your applications with Cisco NAM. It also provides a platform for you to interact with subject matter experts. To view the information on the Cisco NAM Technology Center website, you must have a Cisco.com account with partner level access, or you must be a Cisco NAM licensee. You can access the Cisco NAM Technology Center at http://developer.cisco.com/web/nam/home.

Cisco Prime Network Analysis Module Software 5.1(2) Third Party and Open Source Copyright Notices

OL-25965-01

The Cisco Prime Network Analysis Module 5.1(2) Third Party and Open Source Copyright Notices provides a listing of all copyright notices for the open source third-party software used in NAM 5.1(2).

http://cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.1_2/
copyright/notice/NAM_Open_Source_Documentation5.1_2.pdf

Cisco Prime NAM for ISR G2 SRE Documentation

OL-24407-01

The Cisco Prime Network Analysis Module (NAM) for ISR G2 SRE Installation and Configuration Note provides detailed steps to install the NAM on an ISR G2 SRE and configure the NAM. For 5.1(2) updates, see Updates for NAM 5.1(2) Installation and Configuration Guides/Notes.

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.1/
sm_sre/SM_SRE_incfg_5_1.html

Cisco 2200 Series NAM Appliance Documentation

This section describes the Cisco 2200 Series NAM Appliance documentation.

Quick Start and Documentation Guide for the Cisco 2200 Series NAM Appliance

Installation and Configuration Guide for the Cisco NAM 2204 Appliance

Installation and Configuration Guide for the Cisco NAM 2220 Appliance

Regulatory Compliance and Safety Information for the Cisco NAM 2200 Series Appliances

Quick Start and Documentation Guide for the Cisco 2200 Series NAM Appliance

78-18440-01

The Quick Start and Documentation Guide for the Cisco 2200 Series NAM Appliance is available online at the following URL:

http://www.cisco.com/en/US/products/ps10113/products_documentation_roadmaps_list.html

This document contains a description of the documentation for the NAM appliance and NAM software and information about how to get started with the NAM appliance.

Installation and Configuration Guide for the Cisco NAM 2204 Appliance

OL-24404-01

The Installation and Configuration Guide for the Cisco NAM 2204 Appliance provides information to help you install and configure the NAM 2204 appliance. This guide includes overview information and details about how to install the appliance, connect the appliance to power and the device it monitors, configure the appliance, log in, and get started setting up the appliance to monitor the device.

The Installation and Configuration Guide for the Cisco NAM 2204 Appliance is an online only document you can find at the following URL:

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_appliance/5.1/
2204/instcfg2204.html

Installation and Configuration Guide for the Cisco NAM 2220 Appliance

OL-24403-01

The Installation and Configuration Guide for the Cisco NAM 2220 Appliance provides information to help you install and configure the NAM 2220 appliance. This guide includes overview information and details about how to install the appliance, connect the appliance to power and the device it monitors, configure the appliance, log in, and get started setting up the appliance to monitor the device.

The Installation and Configuration Guide for the Cisco NAM 2220 Appliance is an online only document you can find at the following URL:

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_appliance/5.1/
2220/installation/guide/instcfg2220.html

Regulatory Compliance and Safety Information for the Cisco NAM 2200 Series Appliances

78-18308-01

The Regulatory Compliance and Safety Information for the Cisco NAM 2200 Series Appliances is a printed document that ships with the NAM appliance and is also available online at the following URL:

http://cisco.com/en/US/docs/net_mgmt/network_analysis_module_appliance/
regulatory/compliance/nam2200rcsi.html

The Regulatory Compliance and Safety Information for the Cisco 2200 Series NAM Appliances contains regulatory compliance and safety information for the Cisco 2200 Series NAM appliances.

Cisco Prime Network Analysis Module for Virtual Services Blades Documentation

The following URL provides links to product support, additional product literature, software, and other helpful information for the Cisco WAAS NAM Virtual Blade:

http://www.cisco.com/en/US/products/ps10506/index.html

The following URL provides links to product support, additional product literature, software, and other helpful information for the Nexus 1010 NAM Virtual Blade:

http://www.cisco.com/en/US/products/ps10846/tsd_products_support_series_home.html

Cisco Prime Network Analysis Module for WAAS VB Installation and Configuration Guide, 5.1

OL-24405-01

The Cisco Prime Network Analysis Module (NAM) for WAAS VB Installation and Configuration Guide, 5.1 provides detailed steps to install the NAM VSB on a WAAS appliance and configure the NAM VSB.

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_virtual
_blade/5.1/install/guide/waas/waas51install.html

Cisco Prime Network Analysis Module (NAM) for Nexus 1010 Installation and Configuration Guide, 5.1

OL-24406-01

The Cisco Prime Network Analysis Module (NAM) for Nexus 1010 Installation and Configuration Guide, 5.1 provides detailed steps to install the NAM VSB on a Nexus 1010 switch and configure the NAM VSB.

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_virtual_blade/5.1/
install/guide/nexus/nx51_instcfg.html

Related Documentation

This section provides information about other documentation related to the Network Analysis Module software.

NAM-1 and NAM-2

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 5.1

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/
5.1/switch/configuration/guide/switchcfg.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 5.0

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/
5.0/switch/configuration/guide/switchcfg.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 4.2

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module
_software/4.2/switch/configuration/guide/65_76cfg42.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 4.1

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module
_software/4.1/switch/configuration/guide/swconfig.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 4.0

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module
_software/4.0/switch/configuration/guide/swinstcfg.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note, 3.6

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module
_software/3.6/switch/configuration/guide/swconfig.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module
Installation Note. 3.5

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/
nam/nam_3_5/hw_install/78_17286.html

NME-NAM

Cisco Branch Routers Series Network Analysis Module (NME-NAM-120S) Installation and Configuration Note, 5.1

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.1/
branch_router/configuration/guide/BRincfg_51.html

Cisco Branch Routers Series Network Analysis Module (NME-NAM-120S) Installation and Configuration Note, 5.0

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/5.0/
branch_router/configuration/guide/BRincfg_50.html

Cisco Branch Routers Series Network Analysis Module (NME-NAM-120S) Installation and Configuration Note, 4.2

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/
4.2/branch_router/configuration/guide/BRincfg_42.html

Cisco Branch Routers Series Network Analysis Module (NME-NAM-120S) Installation and Configuration Note, 4.1

http://www.cisco.com/en/US/docs/net_mgmt/network_analysis_module_software/
4.1/branch_router/configuration/guide/BRincfg_120S.html

Cisco NAM Enhanced Network Modules

http://www.cisco.com/en/US/docs/routers/access/interfaces/nm/hardware/
installation/guide/namnme.html

Installing Cisco Network Modules and Service Modules

http://www.cisco.com/en/US/docs/routers/access/interfaces/nm/hardware/installation/guide/
InstNetM.html

Cisco 3800 Series Hardware Installation

http://cisco.com/en/US/docs/routers/access/3800/hardware/installation/
guide/hw.html

Cisco 3700 Series Routers Hardware Installation Guide

http://www.cisco.com/en/US/docs/routers/access/3700/hardware/
installation/guide/3700hig.html

Installing Network Modules in Cisco 2800 Series Routers

http://www.cisco.com/en/US/docs/routers/access/2800/hardware/
installation/guide/08_hw.html

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.