Guest

Cisco Prime Network Analysis Module Software

Release Notes for Cisco Network Analysis Module Software, 3.5

  • Viewing Options

  • PDF (649.7 KB)
  • Feedback
Release Notes for the Network Analysis Module Software Release 3.5

Table Of Contents

Release Notes for the Network Analysis Module Software Release 3.5

Contents

New Features in NAM 3.5

System Requirements

Hardware Requirements

Software Requirements

NAM-1/NAM-2 Software Requirements

NM-NAM Software Requirements

Browser Requirements

Upgrading NAM Software

NAM Disk Partitioning

Product Documentation

Related Product Documentation

Limitations and Restrictions

Caveats

NAM 3.5.1b

Known Anomalies in NAM 3.5(1b)

Anomalies Resolved in NAM 3.5(1b)

NAM 3.5.1a

Known Anomalies in NAM 3.5.1a

Anomalies Resolved in NAM 3.5.1a

NAM 3.5

Known Anomalies in NAM 3.5

Anomalies Resolved in NAM 3.5

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for the Network Analysis Module Software Release 3.5


Revised: April 3, 2008, OL-8399-06

This document includes information about the NAM 3.5.1b release. NAM 3.5.1b replaces the NAM 3.5.1a release.

These release notes provide general information about Cisco Network Analysis Module (NAM) software release 3.5 including system requirements, limitations and restrictions, new features, product documentation, and known and resolved anomalies.

Product Numbers:

SC-SVC-NAM-3.5
(Cisco Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module Software 3.5)

NM-NAM-SW-3.5
(Cisco Branch Routers Series Network Analysis Module Software 3.5)

CCO Date: Release 3.5.1b, February 2007

NAM 3.5.1b is a complete software release, not a patch. To upgrade NAM 3.5.1 to version 3.5.1b, enter the NAM CLI command upgrade while in maintenance mode. For information about the upgrade command see the Network Analysis Module 3.5 Command Reference Release at the following URL:

http://www.cisco.com/en/US/products/hw/switches/ps708/products_command_reference_chapter09186a00805e34f0.html#wp1048351

You can apply the NAM3.5.1 Crypto K9 patch, nam-app.3-5.cryptoK9.patch.1-0.bin, on top of NAM3.5.1a using NAM CLI command patch.


Note For detailed installation and configuration procedures for the NAM, see the Quick Start Guide for the Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module, Release 3.5 or the Quick Start Guide for the Cisco Branch Routers Series Network Analysis Module, Release 3.5, Installation and Configuration Note for the Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module Release 3.5 and User Guide for the Network Analysis Module Traffic Analyzer Release 3.5. See Product Documentation for more information.


Contents

This document includes the following sections:

New Features in NAM 3.5

System Requirements

Hardware Requirements

Software Requirements

Browser Requirements

Upgrading NAM Software

Product Documentation

Related Product Documentation

Limitations and Restrictions

Caveats

Known Anomalies in NAM 3.5(1b)

Anomalies Resolved in NAM 3.5(1b)

Known Anomalies in NAM 3.5.1a

Anomalies Resolved in NAM 3.5.1a

Known Anomalies in NAM 3.5

Anomalies Resolved in NAM 3.5

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

New Features in NAM 3.5

This section lists the new features added to the NAM 3.5 release.


Note All features apply to NAM-1, NAM-2, and NM-NAM unless otherwise indicated.


Monitoring IP/MPLS labels (for NAM-1 and NAM-2)

Enables you to monitor L2 EoMPLS and L3 MPLS VPN traffic.

Support for Voice Quality in SIP protocol

Enables you to view Voice Quality information for the SIP protocol

Permits the set-up of the SIP protocol to be the same as for the other voice protocols currently supported in this function

Includes statistics associated with the Voice Overview, Known Phones, and Active Call screens

Uses the SIP protocol (RFC 3261 and RFC 2327) with some Cisco extensions

NAM-1 and NAM-2 support for ERSPAN

Enables you to receive ERSPAN traffic on the NAM monitoring port. This scenario requires you to send ERSPAN traffic from one switch with Sup720 to the switch where the NAM resides. That switch requires a Sup720 as well. Once received, you can SPAN the traffic to the NAM monitor port for analysis.

Enables you to receive ERSPAN traffic on the NAM management port (ERSPAN traffic as a data source). This scenario requires you to send ERSPAN from one switch with Sup720 directly to the NAM in another switch with or without Sup720.

Protocol updates including SigTran and mobile wireless protocols

NAM-1 and NAM -2 support for Virtual SPAN

Permits you to leverage the VSPAN feature within the switch

Set-up includes an option to specify the destination port or ports to which the spanned traffic can be sent to the NAM

NM-NAM support for interface-based traffic analysis

Using NetFlow as a data source, allows you view topN applications, hosts, and conversations by interface and subinterface

Enables you to configure NetFlow (activate NetFlow flows by way of the interface and sub-interface on the routers) using the NAM GUI.

Capability to save capture files to a network disk

Permits you to send captured packets to an external disk using NFS or iSCSI

Permits you to specify which dedicated directory in the external disk to store the capture files so that the RMON capture can write packet data to the specified directory as if it were the local disk

Permits you to decode capture files stored remotely in external storage

On demand and scheduled report export

Allows you to perform an export of report data in XML format

Provides an option for you publish a report using the web interface

Allows you to configure NAM reports for periodic export

Provides a GUI scheduler to enable you to configure export time, frequency, report types, and destinations

Supports e-mail and FTP for report export

Supports the following report formats:

XML
HTML
CSV
PDF

Capture analysis tool enables you to analyze captured packets

Permits you to analyze captured packets to identify hosts and applications

Permits you to view a graph of the traffic rate during the capture period so you can pin-point the time a utilization anomaly occurred

Once the exact time period of the anomaly is known, permits you to drill down to more closely examine:

Top applications during the period

Top hosts

Monitoring video quality for RTP streams

Supports up to 100 RTP streams (NAM-2)

Detects and displays packet loss rate down to 10-6 on all RTP streams

Logs packet drop events with timestamps and associated RTP stream information

Decoding support to allow sorting of headers in the decode screen

Decoding support to allow you to follow the TCP stream in the decode screen

Export of voice quality data in CSV format

Allows NAM alarms to be sent by e-mail

Enhancements to the reporting function enabling you to configure TopN reports for applications, hosts, and conversations

Enhancements to the historical reporting function for switch and router health monitoring

Usability enhancement to simplify saving newly-learned protocols in the protocol directory

Support to view local disk usage statistics

Enhancements to enable an administrator to track user's critical browser-based and CLI activities in an audit trail log

Enhancement to URL monitoring functions to allow you to filter content type in addition to the host and path fields in the URL string

System Requirements

This section describes the hardware, software, and browser requirements for NAM 3.5

Hardware Requirements

Table 1 identifies the Catalyst 6500 Series and Cisco 7600 supervisors and platforms that are compatible with NAM-1 and NAM-2.

Table 1 Catalyst 6500 Series and Cisco 7600 Series NAM Hardware Compatibility

Module
Running Catalyst
OS Software
Running Cisco
IOS Software
Platform or Devices

WS-SVC-NAM-1
WS-SVC-NAM-2

SUP2 with MSFC2

SUP720

SUP32

Catalyst 6000 Series

Catalyst 6500 Series

Cisco 7600 Series


Table 2 shows the specific router models that support NM-NAM.

Table 2 Supported Cisco Branch Routers

Module
Supported Routers

NM-NAM

Cisco 262xXM

Cisco 265xXM

Cisco 2691 Multiservice Platform

Cisco 2811 Integrated Services Router

Cisco 2821 Integrated Services Router

Cisco 2851 Integrated Services Router

Cisco 3660 Multiservice Platform

Cisco 3725 Multiservice Access Router

Cisco 3745 Multiservice Access Router

Cisco 3825 Integrated Services Router

Cisco 3845 Integrated Services Router


Software Requirements

This section describes software required to use NAM 3.5 software.

NAM-1/NAM-2 Software Requirements

Table 3 lists the minimum software versions required to use NAM-1 and NAM-2 modules with NAM 3.5.

Table 3 Software Requirements for Minimum OS Versions

Module
Software
Release
Orderable Product Number
Minimum IOS Software Versions Supported
Minimum CatOS Software Versions Supported

WS-SVC-NAM-1
WS-SVC-NAM-2

3.5

SC-SVC-NAM-3.5

Release 12.1(13)E1 or later with a Supervisor Engine 2 with an MSFC2.

Release 12.2(14)SX1 or later with a WS-SUP720.

Release 12.2(18)SXF with SUP32

Release 7.3(1) or later with Supervisor Engine 2.

Release 8.2(1) or later with a WS-SUP720.

1 If you are running a 12.1(13)E-based release, Cisco recommends a later 13E release such as 12.1(13)E11 over 12.1(13)E3.


Table 4 lists the Cisco IOS and CatOS versions used on the Catalyst 6500 Series and Cisco 7600 Series (except as noted) when testing and developing NAM 3.5.

Table 4 Latest Supported IOS and Cat OS Versions

Modules
Cisco IOS
Versions
Catalyst OS
Versions

WS-SVC-NAM-1

WS-SVC-NAM-2

12.2(18)SXD4

12.2(18)SXD7

12.2(18)SXE4

12.2(18)SXF3

12.2(18)SXF4 (Modular IOS)

12.2(18)SXF5

12.2(33)SRA for Cisco 7600

CatOS 8.5


The software versions in Table 4 are the specific versions used in testing NAM 3.5. All system software releases from the minimum to the latest version tested are officially supported. Note the following conditions and exceptions:

Cisco IP Phone firmware 6.0 and above is required for SIP voice packet quality monitoring

IOS 12.2(18)SXE4, at minimum, is required to support the ERSPAN feature. Dependencies and limitations for ERSPAN can be found in Configuring Local SPAN, RSPAN, and ERSPAN, Guidelines and Restrictions, at:

http://www.cisco.com/ef/cc/td/doc/product/lan/cat6000/122sx/swcg/span.htm

IOS 12.2(18)SXD or CatOS 8.5, at minimum, are required to support the Virtual SPAN feature.

NM-NAM Software Requirements

The minimum software version required to use NM-NAM modules with NAM 3.5 is Cisco IOS Version 12.3(7)T or later or 12.4(1) or later.


Note The NAM 3.5.1a version has been tested with IOS 12.4(10).


Browser Requirements

Table 5 describes the browser requirements for all platforms.

Table 5 Browser Requirements 

Browser
Version
Platform
Java Plug-In Support 1

Internet Explorer (recommended)

6.0

Windows
Windows XP Professional

JRE Version 5.0 Update 6

Mozilla

1.7

Windows
Windows XP Professional Solaris

Firefox

1.5

Windows
Windows XP Professional
Solaris
Linux (Redhat, SuSe)

1 Although Traffic Analyzer does not require a Java plug-in, one 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.


Upgrading NAM Software

NAM 3.5.1b is a complete software release, not a patch. To upgrade NAM 3.5.1 or 3.5.1a to version 3.5.1b, enter the NAM CLI command upgrade while in maintenance mode. For information about the upgrade command see the Network Analysis Module 3.5 Command Reference Release at the following URL:

http://www.cisco.com/en/US/products/hw/switches/ps708/products_command_reference_chapter09186a00805e34f0.html#wp1048351


Note If a switch is running a non-compliant image for the new 2007 Daylight Savings Time (DST) rule, the NAM's synched-to-the-switch time will be one hour ahead of the home switch time after the NAM is upgraded to NAM 3.5(1b). This issue occurs when you cannot upgrade all switches at the same time, or when you do not adopt the new DST rule.


You can apply the NAM 3.5.1 Crypto K9 patch, nam-app.3-5.cryptoK9.patch.1-0.bin, on top of
NAM 3.5.1b using NAM CLI command patch.


Note If you had previously installed the NAM 3.5.1 Crypto K9 patch, you will need to re-install it after installing NAM 3.5(1b).


NAM Disk Partitioning

NAMs that shipped prior to NAM 3.3 might still be using an older and less efficient disk partitioning system. The NAM 3.3 release increased the size of the /storage partition to 12 gigabytes to handle the NAM's increased data capture capabilities.


Note This condition affects the NAM-1 and NAM-2 but not the NM-NAM.


If your NAM's /storage partition is only 3.4 GB, you can increase its size to 12 GB by reloading the NAM software with the 3.5(1) image using the --install option.

You can check your disk's partitioning using the GUI by clicking Admin > Diagnostics > Tech Support and checking the df heading. The following shows an example of the old partitioning with only 3.4GB of space /storage:

Filesystem           1K-blocks       Used  Available   Use% Mounted on
LABEL=/                4128320     243476    3675108     7% /
/dev/hdc2              1032056      33460     946156     4% /nvram
/dev/hdc3              3451192     183208    3092668     6% /storage
/dev/hda1                15860      10089       4947    68% /mnt/mp

The following shows an example of the newer partitioning with only 12 GB of space /storage:

Filesystem          1K-blocks       Used  Available   Use% Mounted on
LABEL=/               4128320     243912    3674672     7% /
/dev/hdc2             1032056      34284     945332     4% /nvram
/dev/hdc3            12385072     197792   11558112     2% /storage
/dev/hda1               15860      10102      4934     68% /mnt/mp

To increase your disk partitioning to the correct size, you can reload the 3.5(1) image using a command like the following:

upgrade ftp://ftpusername@ftp-server-ip/path/nam-image-filename --install

Where;

ftpusername is the username of the individual performing the FTP access.

ftp-server-ip is the IP or hostname of the FTP server.

path is the path to the image on the FTP server.

nam-image-filename is the filename of the NAM image to install.

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates. You can find product documentation for all releases at the following location:
http://www.cisco.com/en/US/products/sw/cscowork/ps5401/tsd_products_support_series_home.html


Your product shipped with a Documentation CD-ROM. The Documentation CD-ROM contains product documentation that you can access and print.

The following is a list of the documentation for Cisco Network Analysis Module, Release 3.5. You can access the URLs listed for each document on the Documentation CD-ROM and at www.cisco.com on the World Wide Web at the following URL:

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

We recommend you refer to the documentation in the following order:

Release Notes for the Cisco Network Analysis Module, Release 3.5 (OL-8399-03), this document

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

Quick Start Guide for the Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module, Release 3.5 (OL-8401-01)

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

Quick Start Guide for the Cisco Branch Routers Series Network Analysis Module, Release 3.5 (OL-8404-01)

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

User Guide for the Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module, Release 3.5 (OL-8405-01)

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

Copyright Notices for the Cisco Network Analysis Module, Release 3.5 (78-17273-01)

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

Related Product Documentation

The following is a list of related documentation for your product. Most of these documents were not shipped with your product, but you can access them by using the URLs listed below and order printed copies by following the instructions in the following section:

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module Installation Note, Release 3.5 (78-17286-01)

http://www.cisco.com/en/US/products/hw/switches/ps708/prod_installation
_guide09186a00805e3549.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module Command Reference, Release 3.5 (OL-8349-01)

http://www.cisco.com/en/US/products/hw/switches/ps708/products_command_reference
_book09186a00805e081d.html

Catalyst 6500 Series Switch and Cisco 7600 Series Router Network Analysis Module Configuration Note, Release 3.5 (OL-9179-01)

http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide
_book09186a00805e081e.html

Cisco Branch Routers Series Network Analysis Module (OL-10702-01)

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

Limitations and Restrictions

Before using the NAM, read the Quick Start Guide for the Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module and Installation and Configuration Note for the Catalyst 6500 Series and Cisco 7600 Series Network Analysis Module Release 3.5.

The following are limitations and restrictions for NAM software release 3.5 users:

You must now configure the local time zone for the NAM regardless of the time synchronization source (switch or NTP). For more information on configuring the local time zone using Traffic Analyzer, see the User Guide for the Network Analysis Module Traffic Analyzer Release 3.5.

If you change the NAM IP address, the default gateway resets to 0.0.0.0. Enter the new default gateway for the new IP address to an address other than one on the current subnet.

If your NAM release is 3.1 or earlier, please use install option when upgrading to NAM 3.5 to enable a larger disk partition for the capture and reports. The NAM upgrade procedures are described in the Installation and Configuration Note.

Before using the NM-NAM, please read the Cisco Network Modules Quick Start Guide, NM-NAM Feature Module, and the Quick Start Guide for the Cisco Branch Router Series Network Analysis Module.

The following are limitations and restrictions for NM-NAM software release 3.5 users:

If you change the NAM IP address, the default gateway resets to 0.0.0.0. Enter the new default gateway for the new IP address.

The NBAR-PD feature is supported in the NM-NAM only and requires the IOS version 12.3(7)T or later.

Caveats

This section provides information about active and resolved anomalies in the NAM 3.5 software.


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log in to Cisco.com.)


NAM 3.5.1b

This section provides the following information:

Known Anomalies in NAM 3.5(1b)

Anomalies Resolved in NAM 3.5(1b)

Known Anomalies in NAM 3.5(1b)

Table 6 describes anomalies known to exist in NAM 3.5(1b) software. Each anomaly listed includes symptoms, conditions, and any workaround available.

Table 6 Known Anomalies in NAM 3.5.1b 

Bug ID
Description

CSCsm69310

A known IOS issue might cause you to lose connectivity to the NAM.

Typical symptoms are:

CLI login attempts to the NAM fail.

You cannot launch the NAM GUI.

Pings to the NAM IP address fail.

You are able to create a NAM session from the supervisor CLI

Packet forwarding from Sup720-10GE uplink ports to Fabric-enabled (65xx) linecards card can fail when all of the following conditions are met:

Conditions for 12.2(33)SXH:

1. Sup720-10GE is running 12.2(33)SXH release.

2. There is at least one Legacy-based linecard (61xx/62xx/63xx), and the number of fabric enabled (65xx) linecards in the system is less than the truncated mode threshold (default threshold is 2).

3. There is no dCEF720 (DFC-based) linecard in the system.

Conditions for 12.2(33)SXH1:

1. Sup720-10GE is running 12.2(33)SXH1 release.

2. There is at least one Legacy-based linecard (61xx/62xx/63xx), and the number of fabric enabled (65xx) linecards in the system is less than the truncated mode threshold (default threshold is 2).

3. There is no dCEF720 (DFC-based) linecard in the system.

4. With 12.2(33)SXH1 release, if you have changed the default threshold configuration using a value of ">2" with a global command like the following:

fabric switching-mode allow truncated threshold <value>

and the number of fabric enabled (65xx) linecards in the system is less than the configured threshold, you will experience the packet forwarding problems described above.

With 12.2(33)SXH1, if the default threshold configuration has not been changed (remains set to 2), you will not experience the packet forwarding problems.

Workaround for 12.2(33)SXH:

Use the following configuration CLI:

Router(config)# fabric switching-mode allow truncated threshold 1


Workaround for 12.2(33)SXH1

No workaround is needed if you use the default configuration (threshold set to 2).

If you do change the default configuration is issued, set the threshold to 1.

CSCsh49604

Error occurs when connecting to RMON daemon while creating a datasource for MPLS VRF

Symptom: When trying to create an MPLS datasource from an imported VRF or VC, an error message displays:

Error connecting to RMON daemon while creating Datasource. 

When this occurs, the GUI will be unresponsive for up to a few minutes and all existing MPLS and VLAN datasources will be lost.

Conditions: It is not clear what triggers this anomaly and it is occurs very rarely.

Workaround: You must wait for the GUI to become responsive again, re-import the MPLS information from the router (or a file), then re-create the datasources you want to monitor.

CSCsg91293

NETFLOW as a data source does not receive netflow data

Symptom: The switch is exporting netflow packets to the NAM management interfaces. However, no data shows up in monitoring pages for NAM data source NETFLOW.

Conditions: Using IOS 12.2(18)SXF5 or later, go to Setup > Monitor > Core Monitoring. Select data source NETFLOW, then check to enable the collections.

Workaround: In releases older than 12.2(18)SXF5, the NAM SNMP to supervisor uses the switch inband address. Per NAM design, this supervisor address is the key for NAM to populate netflow data to the NAM data source NETFLOW. Beginning with 12.2(18)SXF5, the supervisor SNMP address told to NAM is 127.0.0.x address. However, netflow packets from the switch to the NAM still have the switch inband address, and the NAM is unable to find the data source NETFLOW for to collect data.

To workaround this issue, use Setup > Data Sources > NetFlow Listening Mode to see the address that the switch is using to send netflow packets to the NAM. Create a remote netflow device with this address, and use the NDE-x.x.x.x data source instead of the NETFLOW data source in collecting netflow data.

Use the NetFlow Listening Mode to view the additional IP addresses of the devices able to send the NDE packets to NAM. When such interface is learned, add that interface to the NetFlow Listening Mode table. Use the learned device as a Data Source for the netflow data.

CSCsf32729

Cannot create a second NAM monitor session (monitor session 2) using the GUI

Symptom: The NAM works well, but you cannot create a second monitor session using the GUI. The error message is something like the following:

Create SPAN session failed for SPAN source(s): int1, int2, ....

Conditions: This problem has been seen on NAM versions 3.4(1a) and 3.5(1). Other versions may also be affected.

Workaround: Use the switch CLI to configure monitor session 2. Another workaround is to use NAM GUI to created the second monitoring session but use session number 5 instead of 2.

CSCse40730

Negative values in default NM-NAM top interface reports

Symptom: Negative numbers might appear in the first report interval for NM-NAM top interface report.

Conditions: This occurs on NM-NAMs with top interface reports configured.

Workaround: None

CSCse41809

NAM-1 cannot ping the switch IP address

Symptom: NAM-1 management port is not reachable externally, nor can the NAM ping the switch.

The NAM-1 boots up successfully with its management port correctly configured to access the VLAN. However, the supervisor does not bring up the management port. The port remains in shut down mode which is the root cause of this anomaly.

Conditions: This occurs on Catalyst 6500 switches with Sup2 running IOS 12.1(26)E5.

Workaround: Upgrade the IOS image to 12.2 or later.

CSCsf18805

Capture Analysis shows incorrect host statistics if packets are sliced

Symptom: Capture Analysis shows incorrect host statistics (byte and packet counts are low).

Conditions: This occurs when packet slicing is used during a capture.

Workaround: In the Capture Setting window, set the Packet Slice Size to the maximum value (1984 bytes).

CSCsf18545

NM-NAM loses IP connectivity after reload with 12.4(10)

Symptom: After reloading the 3745 router running IOS version 12.4(10), an installed NM-NAM has no IP connectivity outside the router.

Conditions: This defect occurs after system re-initialization of the 3745 router running 12.4(10).

Workaround: After waiting for several hours, the system will recover and the NM-NAM will regain normal IP connectivity.

CSCsf02903

Enhancement request to add support for StationCallInfoV2Message for SCCP

Symptom: When using Cisco Unified CallManager 5.0.2 to manager SCCP phones, NAM cannot detect SCCP calls because StationCallInfoMessage (0x8F) is replaced by StationCallInfoV2Message (0x14A). NAM does not currently support StationCallInfoV2Message.

Conditions: This occurs if StationCallInfoV2Message is used by CallManager.

Workaround: None

CSCse90874

Several PHP errors occur when monitor collection is not configured

Symptom: The Show Tech screen displays PHP errors for several monitor screens when the particular monitor table is not enabled or there is no data for that table.

Conditions: This only happens when there is no monitor data for a particular window.

Workaround: A workaround is not necessary. These errors do not affect data being displayed properly when it is available. It is a matter of the code trying to read the array of data when there is no array of data. Therefore, a PHP error is generated.

CSCse90896

Setup > Preferences window has PHP errors if values in file are 0

Symptom: PHP errors occur if you modify the Setup > Preferences information.

Conditions: This only happens when the database is being updated with a false value, and the value is already false.

Workaround: No workaround is necessary. A minor change in the file calls will correct the error messages. But the correct values of false are still being saved in the database file.

CSCse97810

NAM 3.5(1) remote-storage CLI throws errors on exit when nothing is done

Symptom: If you use the CLI command remote-storage then exit without doing anything, the following errors occur:

root@myname(sub-rs-nfs)# exit
ERROR: NFS description is not set.
To provide NFS description, use 'descr' subcommand.
Invalid parameter!

Conditions: This is only an issue for NAM 3.5(1). Older versions do not support remote-storage functions and hence are not affected.

Workaround: Ignore the errors.

CSCse97829

NAM 3.5(1) GUI throws errors when adding an NFS drive directory with a dash character (-) in its name

Symptom: A directory name is allowed to have a dash character (-) in it. NAM remote-storage CLI allows this at least.

However, if one tries to use the NAM GUI interface and create an NFS drive using a directory name of something like nam-dir, you will see the errors. This can easily be reproducible in Admin > System > Capture Data Storage

Conditions: This is only an issue for the NAM 3.5(1). Older versions are not affected.Workaround: Ignore the errors. Or use CLI command remote-storage instead of the GUI interface.

Workaround: None


Anomalies Resolved in NAM 3.5(1b)

Table 7 describes anomalies found in earlier releases of NAM that were resolved in NAM 3.5(1b).

Table 7 Anomalies Resolved in NAM 3.5(1b)  

Bug ID
Description

CSCsh31426

SSH disabled after reboot

Symptom: It is not possible to SSH the NAM card after a reboot.

Conditions: This problem affects all NAM platforms (WS-SVC-NAM-1, WS-SVC-NAM-2 and NM-NAM) using software version: 3.5.1a (nam-app.3-5.cryptoK9.patch.1-0.bin applied) with SSH enabled using the following command:

exsession on ssh

Workaround: Enable SSH on the card after rebooting using session from supervisor.

CSCsh18288

UDP port 139 misclassified for NDE

Symptom: NAM does not show statistics for UDP ports 139 and TCP port 445 in the monitor application screens for NDE (NetFlow export) data sources.

Conditions: This only affects the NAM GUI. SNMP will report the counters.

The NAM classifies these applications as nbt-session instead as nb-unknown. nbt-session is not a leaf protocol in the protocolDir. Only leaf protocols are shown in the NAM GUI.

Workaround: none

CSCsg99886

HTTP header parsing is looping

Symptom: The message "HTTP header parsing is looping!" is seen in the output of show tech-support command.

Conditions: Certain malformed HTTP request packets.

Workaround: none

CSCsg99868

Packet counters wrong for aged and relearned entries

Symptom: Counters in the NAM GUI Monitor Current Rate screens are too high.

Conditions: Returning to the current rate screens after a while (longer than one hour) and the collections are full (entries are being aged out).

The rate calculated (in polld) is wrong for entries that are aged-out and then relearned later. That can happen with a lot of entries when coming back to the monitor screens after some time.

Workaround: Wait a few refresh intervals for data to settle.

CSCsg97421

Adopt new default daylight savings time (DST) rules from Energy Policy Act of 2005

Symptom: The impact of these changes is that the default values, which have been set for US Standards, will be incorrect until the default values are changed in later versions of code. Furthermore, those systems that reside within time zones that are currently congruent with the United States definitions may no longer be so. This means that later versions of code may require the use of the summertime command in order to properly reflect current local time.

Conditions: For operating systems that have not been updated with the new DST policy changes, products timestamps will exhibit a one hour time clock delay lasting three weeks beginning at 2 a.m. on the second Sunday of March of 2007 and a one hour time clock delay lasting one week beginning at 2 a.m. on the first Sunday in November.

Workaround: none

CSCsg64270

NAM does not respond to Keep Alive polling

Symptom: A NAM-1 or NAM-2 is powered down and the supervisor log reports that NAM was shutdown due to missed keep-alive responses:

%OIR-SP-3-PWRCYCLE: Card in module 7, is being power-cycled off (Module not responding to 
Keep Alive polling) 

Conditions: This occurs in WS-SVC-NAM-1 and WS-SVC-NAM-2 in Catalyst 6500 or 7600 family chassis with Supervisor 720 running IOS. This is seen most often when the NAM or switch is reloading (starting up) or when using session from supervisor to NAM and running commands with a lot of output (like show tech-support), but might happen any time there is a lot of traffic on the EOBC.

The problem is caused by the EOBC MAC transmit queue getting stuck due to missing configuration. The timeout of the MAC to detect the problem is about the same time (5 seconds) as the keep-alive polling timeout. The Transmit queue seems to get stuck when there is a lot of traffic on the EOBC.

The NAM-2 module is power cycled due to not responding to Keep Alive polling after switch reload or when using output intensive commands via session from supervisor. This problem is more frequent with ION images than the IOS images. The module may power-cycle several times prior to becoming operational.

Workaround: Keep reloading or powering up the NAM, or enter the following command from the switch processor CLI (remote login switch):

debug oir no-reset-on-crash <NAM module #>

Another possibility is to use Telnet or SSH to the NAM CLI for output intensive commands.

CSCsg54624

channelStatus does not work with createRequest

Symptom: Creating a new channel entry with initial channelStatus of createRequest(2) fails.

Conditions: This affects all NAM platforms.

Workaround: Create a new channel entry with channelStatus of valid(1).

CSCsg54607

A newly created etherStatsStatus set to valid fails

Symptom: Creating a new etherStats entry with initial etherStatsStatus equal to valid(1) fails.

Conditions: This affects all NAM platforms.

Workaround: Create a new entry with etherStatsStatus = createRequest(2), then change it to valid.

CSCsg62683

NAM-2 TopN reports are all the same

Symptom: The TopN data duplication is caused by old data are not properly removed.

Conditions: This occurs for TopN data reports on NAM-2.

Workaround: There is no workaround other than to restart the NAM to temporarily fix the problem (by flushing out old data). (The problem might eventually return).

CSCsg52033

Incorrect packet length for captures of jumbo packets on NAM-1

Symptom: Packet length for captured packets on WS-SVC-NAM-1 is wrong for packets larger than 2048 bytes.

Conditions: This occurs only on WS-SVC-NAM-1 for captures of packets larger than 2048 bytes. The statistics in monitor and reports are not affected by this, only captures by both SNMP and in the web GUI. Capture to file is not affected.

Workaround: Capture to file.

CSCsf03723

SNMP can loop in etherStatsHighCapacityTable

Symptom: SNMP walk on etherStatsHighCapacityTable loops (get-next returns smaller or equal index).

Conditions: This occurs when etherStatsIndex is larger than 65535.

The valid values for etherStatsIndex according to the RMON-MIB are 1 through 65535. The NAM fails to check for indices larger than 65535 and fails to handle them well when walking the etherStatsHighCapacityTable.

Workaround: Remove etherStatsEntry rows with etherStatsIndex larger than 65535.

CSCsf25077

NAM-1 power-cycled off due to missing Keep Alive polling

Symptom: NAM-1 is reset by the supervisor.

Conditions: NAM-1 might be reset by the supervisor due to missed keep-alive response. This condition occurs intermittently and only on NAM-1 with a WS-SUP720 running native IOS.

Workaround: The following workaround disables keep-alive messages from the supervisor to the NAM-1:

1. telnet to the switch and enter enable mode

2. Log in to SP. (remote login switch)

3. Enter a command like the following:

debug oir no-reset-on-crash NAM_module#


NAM 3.5.1a

This section provides the following information:

Known Anomalies in NAM 3.5.1a

Anomalies Resolved in NAM 3.5.1a

Known Anomalies in NAM 3.5.1a

Table 8 describes anomalies known to exist in NAM 3.5.1a software. Each anomaly listed includes symptoms, conditions, and any workaround available.

Table 8 Known Anomalies in NAM 3.5.1a 

Bug ID
Description

CSCsf25077

NAM-1 power-cycled off due to missing Keep Alive polling

Symptom: NAM-1 is reset by the supervisor.

Conditions: NAM-1 might be reset by the supervisor due to missed keep-alive response. This condition occurs intermittently and only on NAM-1 with a WS-SUP720 running native IOS.

Workaround: The following workaround disables keep-alive messages from the supervisor to the NAM-1:

1. telnet to the switch and enter enable mode

2. Log in to SP. (remote login switch)

3. Enter a command like the following:

debug oir no-reset-on-crash NAM_module#

CSCsf18805

Capture Analysis shows incorrect host statistics if packets are sliced

Symptom: Capture Analysis shows incorrect host statistics (byte and packet counts are low).

Conditions: This occurs when packet slicing is used during a capture.

Workaround: In the Capture Setting window, set the Packet Slice Size to the maximum value (1984 bytes).

CSCsf18545

NM-NAM loses IP connectivity after reload with 12.4(10)

Symptom: After reloading the 3745 router running IOS version 12.4(10), an installed NM-NAM has no IP connectivity outside the router.

Conditions: This defect occurs after system re-initialization of the 3745 router running 12.4(10).

Workaround: After waiting for several hours, the system will recover and the NM-NAM will regain normal IP connectivity.

CSCsf02903

Enhancement request to add support for StationCallInfoV2Message for SCCP

Symptom: When using Cisco Unified CallManager 5.0.2 to manager SCCP phones, NAM cannot detect SCCP calls because StationCallInfoMessage (0x8F) is replaced by StationCallInfoV2Message (0x14A). NAM does not currently support StationCallInfoV2Message.

Conditions: This occurs if StationCallInfoV2Message is used by CallManager.

Workaround: None

CSCsf03723

SNMP can loop in etherStatsHighCapacityTable

Symptom: SNMP walk on etherStatsHighCapacityTable loops (get-next returns smaller or equal index).

Conditions: This occurs when etherStatsIndex is larger than 65535.

Workaround: Remove etherStatsEntry rows with etherStatsIndex larger than 65535.

CSCse90874

Several PHP errors occur when monitor collection is not configured

Symptom: The Show Tech screen displays PHP errors for several monitor screens when the particular monitor table is not enabled or there is no data for that table.

Conditions: This only happens when there is no monitor data for a particular window.

Workaround: A workaround is not necessary. These errors do not affect data being displayed properly when it is available. It is a matter of the code trying to read the array of data when there is no array of data. Therefore, a PHP error is generated.

CSCse90896

Setup > Preferences window has PHP errors if values in file are 0

Symptom: PHP errors occur if you modify the Setup > Preferences information.

Conditions: This only happens when the database is being updated with a false value, and the value is already false.

Workaround: No workaround is necessary. A minor change in the file calls will correct the error messages. But the correct values of false are still being saved in the database file.

CSCse97810

NAM 3.5(1) remote-storage CLI throws errors on exit when nothing is done

Symptom: If you use the CLI command remote-storage then exit without doing anything, the following errors occur:

root@myname(sub-rs-nfs)# exit
ERROR: NFS description is not set.
To provide NFS description, use 'descr' subcommand.
Invalid parameter!

Conditions: This is only an issue for NAM 3.5(1). Older versions do not support remote-storage functions and hence are not affected.

Workaround: Ignore the errors.

CSCse97829

NAM 3.5(1) GUI throws errors when adding an NFS drive directory with a dash character (-) in its name

Symptom: A directory name is allowed to have a dash character (-) in it. NAM remote-storage CLI allows this at least.

However, if one tries to use the NAM GUI interface and create an NFS drive using a directory name of something like nam-dir, you will see the errors. This can easily be reproducible in Admin > System > Capture Data Storage

Conditions: This is only an issue for the NAM 3.5(1). Older versions are not affected.Workaround: Ignore the errors. Or use CLI command remote-storage instead of the GUI interface.

Workaround: None


Anomalies Resolved in NAM 3.5.1a

Table 9 describes anomalies found in earlier releases of NAM that were resolved in NAM 3.5.1a.

Table 9 Anomalies Resolved in NAM 3.5.1a  

Bug ID
Description

CSCse97844

NAM Remote Storage functions needs some more config documentation.

Symptom: An administrator is likely to have difficulty configuring remote NFS storage for the NAM due to a lack of on-window instruction.

Conditions: This is only an issue for NAM 3.5(1). Other versions are not affected.

Workaround: None

CSCse90861

Setup > Router parameters screen Test button is broken when Preferences has DNS resolution turned on.

Symptom: Setup > Router parameters screen Test button is broken.

Conditions: This only happens when DNS resolution is turned on.

Workaround: Disable DNS resolution.

CSCse90909

Audit trail is missing for the following Monitor windows: Voice, RTP Stream, Response Time, Diffserv, and URL

Symptom: Several Setup > Monitor windows are missing the audit trail.

Conditions: After setting up monitor collections on all screens except the ore screens, the audit trail is not shown in the audit table.

Workaround: None

CSCse91260

MPLS data-source label failed to create an mpls specifically data source for a label

Symptom: MPLS label custom data sources can not be created using either the CLI or the GUI.

Conditions: This occurs under normal use.

Workaround: None

CSCse85757

Trying to create report with spaces in the hostname breaks Basic Report window

Symptom: The Basic Report window does not show any report after creating a new Host report.

Conditions: This occurs when the new host report contains leading spaces in the host name/IP address.

Workaround: Use CLI command config clear-all to delete the reports, then re-create them without space in the host names.

CSCse84717

NAM report daemon has memory leak with TopN report configured

Symptom: After NAM has been running for an extended period of time, the capture function might stop working due to insufficient memory.

Conditions: This occurs when TopN reports such as top application and top host are configured.

Workaround:

Disable the topN reports and reboot the NAM

Upgrade to the NAM 3.5 (1a) release

CSCse82775

NAM 3.5(1) Scheduled FTP report export has an invalid character (:) in the filename

Symptom: The NAM 3.5(1) version software includes a new FTP export feature. The scheduled FTP report exports use the colon character (:) in the file names. This is all right for UNIX FTP servers, but is invalid for file names in Windows-based FTP servers.

The report file names are something like:

Web-16:26:02-27067.pdf

Web-17:01:01-28176.csv

Conditions: This is only a problem for NAM 3.5(1). Older versions of NAM images do not support this FTP report export feature.

Workaround: None for scheduled FTP report exports.

CSCse78954

Support host name resolution in TopN host report

Symptom: TopN host reports only show the IP addresses of the hosts, not the DNS hostnames, even when the DNS option is enabled in Setup > Preferences.

Conditions: This happens to TopN hosts and conversations reports.

Workaround: None.

CSCse76696

SysUpTime - IOS 12.1

Symptom: The Setup > Switch Parameters window occasionally shows the system uptime as time ticks instead of the days.

Conditions: This occurs intermittently under normal operating conditions.

Workaround: Refresh the screen.

CSCse76241

Need Instruction Boxes for Remote Audit Trail Syslog

Symptom: It is not clear how to setup Audit Trail remotely. Instruction boxes should be added to Setup > Preferences and Setup > Alarms > Syslog to describe how to turn on the Audit Trail remotely.

Conditions: Normal operating conditions

Workaround: None

CSCse70358

Switch Health Cross Bar Channel speed has wrong header

Symptom: Monitor > Switch > Health Cross Bar Channel speed shows an incorrect wrong header, displaying MB instead of MBits/s.

Conditions: This occurs when you view the Switch Health window.

Workaround: None

CSCse68557

The Port Names do not correspond to the row of data (counts) shown.

Symptom: After navigating to Monitor > Switch > Port Stats, the Port Name shows rows of data (counts) which do not correspond with the names displayed.

Conditions: Normal operating conditions

Workaround: None

CSCse64003

The NAM CLI command no audit-trail enable has an invalid command message

Symptom: The NAM CLI command no audit-trail enable gives invalid command message.

root@NAM# no audit-trail enable
Invalid command 'enable'. Following are the only valid commands:
audit-trail               - disable logging Web GUI and CLI accesses
root@NAM# no audit-trail

Conditions: This might occur when you attempt to use the NAM CLI to disable logging of the NAM web GUI and CLI accesses.

Workaround: Instead of using the no audit-trail enable command, use the no audit-trail audit-trail command. You might instead navigate the NAM GUI to Setup > Preferences and uncheck the Audit Trail checkbox.

CSCse52208

show rxcounters on NAM-1 is not correct

Symptom: On WS-SVC-NAM-1 the port number displayed when executing the NAM CLI command show rxcounter is wrong. Instead of the data port number (1), a random umber is displayed.

Conditions: This occurs on WS-SVC-NAM-1. This anomaly does not affect WS-SVC-NAM-2.

Workaround: Ignore the port number of the CLI command output. It is safe to assume the port umber is always one (1) for WS-SVC-NAM-1.

CSCse47531

Audit Trail did not log GUI activities if using --install option

Symptom: When using --install option, the audit trail from the GUI does not work.

Conditions: This only happens after trying to upgrade with the --install option.

Workaround: Navigate to the Setup > Preferences screen and the audit trail should work properly.

CSCse47353

Cannot pause wrap-mode capture from decode screen

Symptom: When you try to decode a capture running in wrap-when-full mode, a popup window will show an error message:

Cannot decode capture in wrap-when-full mode.  Do you want to pause the capture?

If you click Pause on that the popup window, the capture is not be paused. The popup window is blank.

Conditions: This occurs when you try to decode a wrapping capture.

Workaround: Navigate to Capture > Buffer > Setting to pause a capture.

CSCse41761

Need to monitor a MPLS VRF having multiple local labels.

Symptom: NAM MPLS traffic monitoring shows only partial incoming traffic for VRF

Conditions: When importing VRF information from a router, all the local labels for a VRF have to be imported.

Workaround: None

CSCse24395

Need support importing router VRF/VC configuration for Catalyst 7600 running IOS version 12.2 SRA

Symptom: No MPLS VRF and VC information displays on the NAM MPLS data source window

Conditions: This occurs when trying to import MPLS VRF/VC label information from Catalyst 7600 running IOS version 12.2 SRA

Workaround: Import MPLS VRF/VC label information from external configuration file option from the MPLS datasource window.

CSCsd88998

Custom named protocols do not show up in application response time report

Symptom: When a custom named created protocol is added to the protocol directory, the associated named protocol does not show up in the pull-down menu of the create application response time report window.

Conditions: This happens only when you remove the w-ether2.ip.tcp prefix from the protocol name.

Workaround: Rename protocol from custom name to w-ether2.ip.tcp.custom name.

Alternatively (for NAM 3.5), in the Create Application Response Time Report window, deselect the encapsulation selection box then re-select it. The missing protocol will display.


NAM 3.5

This section provides the following:

Known Anomalies in NAM 3.5

Anomalies Resolved in NAM 3.5

Known Anomalies in NAM 3.5

Table 10 describes anomalies known to exist in NAM 3.5 software. Each anomaly listed includes symptoms, conditions, and any workaround available.

Table 10 Known Anomalies in NAM 3.5  

Bug ID
Description

CSCeh33543

Should not allow deletion of a protocol when the protocol is used by Applications Group

Symptom: If you delete a protocol that exists in a protocol group, the protocol group will no longer report traffic on the deleted protocol. No warning message is given.

Conditions: This problem applies to NAM1, NAM2, and NM-NAM software.

Workaround: Ensure that a protocol being deleted is not part of a protocol group.

CSCsd60305

A Scheduled Report name with hyphen would break FTP

Symptom: Download scheduled report file might fail if the filename contains a dash or hyphen character (-).

Conditions: This might occur when using FTP program in DOS to transfer a NAM report file.

Workaround: Change the report filename or use mget in FTP.

CSCsd88998

Newly added custom-named protocol does not display in the Create Application Response Time Report window

Symptom: When a custom named protocol you have created is added to the protocol directory, the associated named protocol does not show up in the pull down of the Create Application Response Time Report window.

Conditions: This occurs when you remove the w-ether2.ip.tcp prefix from the protocol name.

Workaround: Rename protocol from custom_name to w-ether2.ip.tcp.custom_name.

Alternatively, in the Create Application Response Time Report window, deselect the encapsulation selection box then re-select it. The missing protocol will display.

CSCsd89355

A show tech command does not always work well

Symptom: Entering the NAM CLI command show config or show tech-support sometimes ends the NAM session.

Conditions: This might occur under the following conditions:

NAM CLI commands are applied from a session that was initiated from the NAM local switch or router as in the following:

session slot 5 processor 1 in IOS

session 5 in CatOS

service-module analysis-module 2/0 session in Branch Router

NAM CLI command has a lot of output messages.

Workaround: Use NAM CLI from a telnet or ssh session. To configure the NAM to accept telnet, enter exsession on from the NAM CLI.

CSCsd94402

The monitor mpls command is not supported in 3.5

Symptom: The following two NAM CLI commands are missing from the NAM 3.5 release:

monitor mpls

no monitor mpls

Conditions: In the NAM 3.4 release, you could enable NAM to parse the MPLS payload using the monitor mpls command or disable the parse using the no monitor mpls command. In NAM 3.5, these two commands are no longer required.

Workaround: A new feature in NAM 3.5 supports MPLS and displays a summary of packet and byte count per MPLS label. You can also define a specific MPLS label, VC, or VRF data source and use the data source in RMON stats collections. As a result of this feature, NAM always parses the MPLS payload, so these two commands are no longer needed and have been removed from the NAM CLI.

CSCsd95687

NAM: Cannot create SPAN with the data source as Etherchannel

Symptom: Etherchannels configured at the switch are not displayed at the NAM SPAN configuration GUI

Conditions: Etherchannels configured with LACP protocol

Workaround: Use the switch CLI to configure a SPAN session to NAM data port.

CSCse24395

NAM might not be able to import VRF/VC configuration from a Catalyst 7600 running IOS version 12.2 SRA.

Symptom: No MPLS VRF and VC information is displayed on NAM MPLS datasource window

Conditions: MPLS VRF and VC label information was not imported from a Catalyst 7600 running IOS version 12.2 SRA

Workaround: Use the Import from File option to import the VRF/VC configuration file to the MPLS Data Source window.

CSCse34409

When Editing reports, some fields jump to default value

Symptom: When editing a topN custom report, the Style drop-down list does not show the topN number (10, 20...). Instead it incorrectly shows Bar graph, Line graph, or other style.

Conditions: This occurs when editing reports only. Creating a new custom report works OK.

Workaround: Uncheck, then check the topN report in the tree selector to force the Style list to display correctly.

CSCse38526

Missing reports after changing from http to https

Symptom: e-mail or FTP scheduled report with PDF type does not work

Conditions: After the scheduled reports are configured, you change the NAM to either use a different type of HTTP server (from HTTP to HTTPS or from HTTPS to HTTP) or you change the HTTP or HTTPS port.

Workaround: Use the NAM GUI choose to do the following:

1. Choose Report > Scheduled Report.

2. Select an existing scheduled report.

3. Click Edit, then click Apply.

CSCse41934

Saving running config to startup config gives failure indication

Symptom: If the NAM is in a switch, click Save in SPAN screen. A message window might pop up indicating the saving the running config to startup config failed. This message is misleading because the actual startup configuration is saved successfully at the supervisor.

Conditions: Occurs on Catalyst 6000 series NAM with supervisor running native IOS

Workaround: None

CSCse40730

Negative values in default NM-NAM top interface report

Symptom: Negative number might appear in the first report interval for NM-NAM top interface report

Conditions: This might occur in NM-NAM with a top interface report configured.

Workaround: None

CSCse40735

TopN application reports unknown protocol OIDs

Symptom: TopN application reports occasionally show numeric protocol ID (OIDs) instead of decoded protocol name, as in 4 1000001 800 6 29b 0 1 0 0.

Conditions: This is a very rare occurrence.

Workaround: None

CSCse41809

A NAM-1 cannot ping the switch IP address

Symptom: NAM-1 management port is not reachable externally neither NAM can ping the switch.

Further Problem Description: NAM-1 was booted up successfully with its management port correctly in the configured access VLAN. However, the supervisor did not bring up the management port. The port remains in shut down mode and that the root cause of this bug. The same problem was not observed with another NAM-2 in the same chassis running identical NAM software image

Conditions: Cat6500 with sup2 running IOS 12.1(26)E5

Workaround: Upgrade the IOS image to 12.2 or later

CSCse41761

Need to monitor a MPLS VRF having multiple local labels

Symptom: NAM MPLS traffic monitoring shows only partial incoming traffic for VRF.

Conditions: When importing VRF information from router, all the local labels for a VRF have to be imported

Workaround: None


Anomalies Resolved in NAM 3.5

Table 9 describes anomalies found in earlier releases of NAM that have been resolved in NAM 3.5.

Table 11 Anomalies Fixed in NAM 3.5  

Bug ID
Description

CSCeh48590

Symptoms: On the Monitor > Switch > Port Stats screen, if you do a Real-Time graph on a port that has a description name associated with it, the graph does not work.

Conditions: This only applies to ports with a description name.

Workaround: Delete the port description from the switch CLI.

CSCeh47638

Symptoms: SPAN delete/edit function does not work in NAM SPAN GUI if the supervisor is running CATOS 8.4(x).

Conditions: This behavior will occur if the SPAN session number for the SPAN session is other than 1.

Workaround: Use the supervisor CLI to delete or edit an existing SPAN session.

Note This anomaly was fixed in Cat OS 8.5.

CSCeh40618

NBAR Interface Details filter is not working properly.

Symptom: Interface Type filtering does not work on the Setup > Router Parameters > NBAR Protocol Discovery window. However, filtering on the Interface Name does work correctly.

Conditions: This occurs on Setup > Router Parameters > NBAR Protocol Discovery Interface Details window.

Workaround: None

CSCeh34341

Unable to change the owner string for a Diffserv Aggregate from the command-line interface (CLI)

Symptom: This problem occurs when you do the following:

1. Session or telnet to the NAM.

2. Log in as root.

3. Create a diffserv aggregation as follows:

a. Issue the command diffserv aggregate to get into the subcommand mode.

b. Issue the command descr <description-string>.

c. Issue the command exit to create a diffserv entry.

4. The diffserv entry will be created in NAM with the default owner equal to monitor.

5. Modify the diffserv entry as follows:

a. Issue the command diffserv aggregate to enter subcommand mode.

b. Issue the command control-index <index-#> and set index-# to the control index value of the entry created in step 3c.

c. Issue the command owner <owner-string> to modify the owner string.

d. Issue the command exit to apply the modification.

After completing the steps above, the CLI indicates that the modification was successful. However, the command show diffserv aggregate indicates that the owner string is still monitor.

Conditions: This problem applies to NAM1, NAM2, and NM-NAM software.

Workaround: From the NAM CLI, delete the entry to be modified as follows:

1. Delete any diffserv profile associated with the aggregation entry with the CLI command
no diffserv profile <index>

2. Delete the diffserv aggregation to be modified with the CLI command
no diffserv aggregate <control-index>

3. Recreate the diffserv aggregation entry with the CLI command
diffserv aggregate

Apply the subcommand owner <owner-string> to set the owner string to desired value.

4. Recreate the diffserv profile with the CLI command diffserv profile (if applicable).

CSCeh16637

Decode screen does not highlight the ETH Header hexadecimal field

Symptom: When you click the ETH line on the Decode screen, occasionally the corresponding Ethernet header hexadecimal field is not highlighted.

Conditions: This problem applies to NAM1, NAM2, and NM-NAM software.

Workaround: Click another field, then click the ETH line. The ETH hex header should then be highlighted.

CSCeh36630

The show monitor ifstats CLI command incorrectly indicates router interface statistics are enabled or disabled.

Symptom: From NM-NAM GUI, when you click Setup > Monitor > Core Monitoring > Data Source Router, both Interface Statistics and NBAR Statistics check boxes are checked.

However, the NAM CLI command show monitor ifstats returns a message that does not indicate Interface Statistics are enabled.

Conditions: This problem applies only to NM-NAM software.

Workaround: Do the following:

Log in to NAM GUI.

Click Setup > Monitor > Core Monitoring > Data Source Router.

Click on Apply button.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

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

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

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

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

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

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

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

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html