This document contains Cisco-specific product, feature, and release note information to supplement the NetScout Systems nGenius Real-Time Monitor (RTM) documentation you received.

Acknowledgements

nGenius Real-Time Monitor (RTM) is NetScout Systems' end-to-end performance management suite.

These products are offered to Cisco Systems customers in cooperation with NetScout Systems, Inc.

Documentation Roadmap

Read the documents shown in Table 1, in the order listed, to install and use the nGenius RTM modules effectively.

Note To view the PDF files, Adobe Acrobat Reader 4.0 (provided on the nGenius Real-Time Monitor Third party Applications CD) is required.

Table 1: Sequence to Read RTM Documentation

This Document...	Written By...	Is Provided to You As...	And Contains
Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.2 (this document)	Cisco Systems	Hardcopy	Cisco-specific product, feature, and release note information to supplement the NetScout documentation.
nGenius Real-Time Monitor 1.2 Release Notes	NetScout Systems	Hardcopy	Detailed information about changes and new functionality.
Real-Time Monitor Installation Guide	NetScout Systems	Hardcopy	Instructions for installing all RTM modules.
nGenius Instrumentation Overview¹	NetScout Systems	PDF on RTM CD-ROM	Background information about RMON and instructions for using NetScout probes.
Real-Time Monitor Configuration Guide	NetScout Systems	PDF on RTM CD-ROM	Tasks to establish user security, configure devices, and manage databases.
In any sequence: Getting Started with Traffic Monitor or Getting Started with NetScout Packet Analyzer	NetScout Systems	PDF on RTM CD-ROM	Instructions for using the RTM web-based network monitoring module. Instructions for using the RTM protocol and network analysis module.
Online help	NetScout Systems	Embedded information within each RTM module	More in-depth, context-sensitive, procedural information than what is provided in the hardcopy or PDF documentation.

¹This booklet describes only how to set up NetScout probes, not Cisco switches or Network Analysis Modules.

Special Note about Probes and Other Monitoring Devices

Although not explicitly stated in the NetScout nGenius documentation and online help, the word probe includes such devices as external NetScout and Cisco SwitchProbe devices, internal embedded Cisco Catalyst 5000 and Catalyst 6000 family Network Analysis Modules (NAMs), and mini-RMON switch ports.

For information about NetScout probes, see the NetScout document nGenius Instrumentation Overview and the NetScout hardware and agent documentation you received with your probe.
For information about Cisco SwitchProbe devices or NAMs, see the Cisco SwitchProbe, Catalyst 5000 NAM, or Catalyst 6000 NAM documentation you received with your hardware.

Performance Monitor Support

Although mentioned in several places in the NetScout documentation and online help, and visible in the user interface, Cisco Systems does not support the Performance Monitor module in this release.

Note Contact NetScout Systems directly for sales and support information about adding Performance Monitor to your RTM environment.

Important Installation Notes

The following sections contain important information that you should read before starting the installation.

Solaris Server and Client Support

Cisco Systems supports RTM only on Solaris 2.6 and 2.7 platforms in this release. Solaris 2.8 is not supported.

Creating Secured User Account with No Remote Login Privileges

Caution While every precaution has been taken to secure all nGenius directories, files, and the runtime execution environment, it is highly recommended that you limit unprivileged local login access to nGenius server systems to trusted users and disallow remote login access by privileged accounts.

Before installing the RTM Server, you must create a secured user account and user group that have no remote login privileges. During installation, all RTM files are fully accessible (with read, write, and execute permissions enabled) only to an administrator logged in as this secure user.

You can protect RTM by limiting access so that only systems with valid needs can access it over the network. To do so, place an access control list (ACL) on a router between the RTM Server and the remainder of the network.

If the RTM Server and client systems are separated by a firewall, you can configure your firewall to accept connections from specific clients outside the firewall and modify the startup script to recognize the domain name of the RTM system. See the troubleshooting section in Part II of Real-Time Monitor Installation Guide.
If the RTM Server and client systems are both inside a firewall, you must configure the client browser and set an exception for the RTM Server. See the troubleshooting section in Part II of Real-Time Monitor Installation Guide.

Updating Registry Files During Installation on Windows NT and Windows 2000 Servers

Near the end of the installation:

Step 1 You must click Yes when responding to this prompt:

Are you sure you want to add the information in install_directory 
to the registry?

Note If you click No, the RTM Server will not start automatically as a system service.

After you click Yes, the following message is displayed:

Information in the install_directory\nGeniusRTM.reg has been 
successfully entered into the registry.

Step 2 Click OK.

Step 3 A DOS command window is displayed with the following prompt; you must enter Y when responding to this prompt:

Are you sure (Y/N)?

Note If you enter N, file permissions are not set appropriately, leaving files open and vulnerable.

Step 4 At the following prompt, enter Y again:

Are you sure (Y/N)?

Installing and Starting RTM on Windows 2000 and Windows NT Systems

To install RTM on Windows 2000 and Windows NT systems, you must be logged in as a local Administrator.

When the installation is complete, start the Server by selecting Start>Programs>NetScout nGenius Server>Start nGenius Server.

Note You must remain logged in as the local Administrator during this process.

Installing and Starting RTM on UNIX Systems

To install RTM on UNIX systems, you must be logged in as root and you must create a secured user.

Using the following example, assume you want to use the name ngenius as the secured user and group. To do this:

Step 1 Add "ngenius:x:user_id:group_id::/tmp:" to the /etc/passwd file.

Step 2 Add "ngenius::group_id:" to the /etc/group file.

Step 3 Add "ngenius:*LK*:::::::" to the /etc/shadow file.

This procedure locks the account, thereby disabling remote logging to the server by the genius user and group.

Step 4 After performing the nGenius RTM installation using the instructions in Real-Time Monitor Installation Guide, start the nGenius Server by entering this command:

su ngenius -c ngenius_dir/bin/start

Note If you start the server as root, many RTM files will be owned by root instead of the secured user. If this occurs, change the ownership of all RTM files to the secured user and group (except for TrapServer, which must be owned by root).

Java Plug-In Support

It is critical that you use only the supported Java plug-in versions listed in NetScout's nGenius Real-Time Monitor 1.2 Release Notes and Real-Time Monitor Installation Guide. If you use any other version, system behavior is not guaranteed.

RTM Client Platforms Supported

The RTM client is supported on these platforms:

Microsoft Windows 2000 Server or Professional with Service Pack 1.
Windows NT 4.0 Server or Workstation with Service Pack 6a.
Sun Solaris Release 2.6 or 2.7.
IBM-AIX 4.3.3.

Note Future client support is planned for HP-UX.

Installing Required Third-Party Applications

The following applications are provided on the nGenius Real-Time Monitor Third party Applications CD-ROM.

Note These applications are provided to you as a convenience, but each is licensed and supported separately by Adobe Systems, Inc., Netscape Communications Corporation, Sun Microsystems, Inc., and Microsoft Corporation respectively.

Adobe Acrobat
Netscape Navigator
Java Virtual Machine (JVM)
Internet Explorer

Controlling Device Configuration When Using RTM with TrafficDirector

Note If you are not using the Cisco TrafficDirector application, skip this section.

Because only one network management system can control configuration of shared RMON devices, you must decide if you want RTM or TrafficDirector to control device configuration—before you log in and start configuring devices.

Note For optimum performance, it is recommended that you install RTM on a dedicated system on which TrafficDirector is not installed.

If you want RTM to control all device configuration, use the instructions in this document and the nGenius Server online help to add and configure devices in RTM.
If you want TrafficDirector to control device configuration for all monitoring devices, you must enable a flag in the RTM properties file before adding monitoring devices to RTM.

Using TrafficDirector to Configure All Devices

To use TrafficDirector to configure all devices, you must add the nGenius.nsminuse parameter to the server.properties file. This parameter tells RTM that TrafficDirector is configuring devices and prevents RTM from applying global settings and templates to those devices.

Using TrafficDirector to Configure Some Devices

To use TrafficDirector to configure only some devices, you must change the write community strings on the devices. If the write community strings do not match, the write community will fail, and the nGenius Server cannot write global settings and templates to the device.

Generating History Reports

The type of data generated in history reports depends on which application is configuring devices. Each application collects data only from those devices for which it controls configuration. Therefore, if you want RTM to control device configuration, you cannot use TrafficDirector to receive reports at the same time.

The nGenius Server collects and stores data for up to 31 days for each device that RTM configures. To view historical reports, use nGenius Traffic Monitor.
TrafficDirector collects and stores data for up to 31 days for historical reports and 366 days for summary reports. (The actual number of days included in a report depends on how you configure the report.)

Applying Global Settings and Templates

By default, RTM automatically configures all devices you add to the nGenius Server by applying global settings and templates to the devices. If you want TrafficDirector to control device configuration, you must modify the RTM settings.

It is strongly recommended that you make these changes before you add devices to RTM to eliminate the step of reconfiguring the device in TrafficDirector.

Step 1 On the system on which the nGenius Server is installed, go to the nGenius_directory\bin\admin directory.

Step 2 Use a text editor to open the server.properties file.

Step 3 Add this string to the file:

: nGenius.nsminuse=true

Step 4 Save your changes.

Step 5 Close the server.properties file.

Integrating RTM with the CiscoWorks2000 Desktop

The RTM installation dynamically creates Cisco Management Connection (CMC) files for each available application, and these files initially reside in the nGenius/bin folder.

nGeniusS.lf—For nGenius Server
nGeniusT.lf—For Traffic Monitor
nGeniusK.lf—For Packet Analyzer

Before starting the RTM installation, you must manually create the NMSROOT environment variable and reference the root directory where the CiscoWorks2000 software was installed.

If CiscoWorks2000 and RTM are installed on the same system, the files are copied automatically to the $NMSROOT/htdocs/xml/ public/maintree CiscoWorks2000 directory; CiscoWorks2000 uses these files to create menus to launch nGenius Server, Traffic Monitor, and Packet Analyzer.
If CiscoWorks2000 and RTM are installed on different systems, or if nGenius was installed before CiscoWorks2000, you must manually copy the CMC files to the location specified in the CiscoWorks2000 installation.

After the CMC files are in place, you must reboot the system for the changes to take effect. Then, when you select nGenius Server, Traffic Monitor, or Packet Analyzer, an nGenius graphic is displayed in the main CiscoWorks2000 window and the selected application starts. The nGenius system administrator might choose to create the same users and apply the same privileges from CiscoWorks2000 to the nGenius system.

Supported Cisco Devices

Although other vendors' devices are listed in the NetScout documentation, Cisco Systems supports only those devices listed in Table 2. For information about support for other devices, contact NetScout Systems.

Table 2: Cisco Catalyst Switches Supported by RTM

1200
1800
1900
1912
1924
2820

2900
2908XL
2916XL
2924XL
2926
2926G

2948G
2980G
3000
3100
3200
3500XL

3900
3920
4000
4003
4006
4908G

5000
5002
5505
5509
6000
6006

6009
6500
6506
6509
CPW2200
Generic

Configuring the Cisco Catalyst 6000 NAM

You configure the Cisco Catalyst 6000 NAM using the same procedures as for a switch. Traffic Monitor uses switch templates to establish default mini-RMON on the switch, and global settings to establish full RMON1 and RMON2 on the NAM.

Note Support is limited to a single NAM installed in each Catalyst 6000 switch.

To enable NetFlow in the Cisco Catalyst 6000 NAM:

Step 1 Enter this command from the switch CLI:

: set snmp extendedrmon netflow enable mod

Step 2 Add the switch to the nGenius Server.

Step 3 Launch Traffic Monitor.

An entry called Netflow (via NAM) is displayed in the switch port drop-down list.

Configuring the Cisco Catalyst 5000 NAM

Because of architectural differences, the global settings and templates you use for other monitored elements do not apply to the Cisco Catalyst 5000 NAM; you must configure the NAM manually.

Step 1 On the nGenius Server system, change directory to nGenius_dir\data.

Step 2 Make a copy of Nam_Protocol_Config.dat.

Step 3 Rename the copied file Nam_Protocol_Config_Copy.dat.

Caution You must use this exact filename; otherwise, the configuration
will fail.

Step 4 Use text editor to open Nam_Protocol_Config_Copy.dat.

The file is organized into columns with no headers. (Table 3 describes each column in the order they appear in the file.)

Step 5 Modify each field as necessary:

To enable a setting, enter 1.
To disable a setting, enter 0.

Step 6 Save and close the file.

Step 7 Change directory to nGenius_dir\bin.

Step 8 To reload the NAM configuration settings into the database, run the cfgNAM.bat script.

Table 3: Fields in NAM Protocol Configuration Data File

Column Heading	Description
NAM_Protocol_Config_ID	Identifier used internally by the database. Do not modify this information.
Protocol_Type_Code	Unique protocol identifier. Do not modify this information.
Enable_Flag	Indicates if logging is enabled. If protocol is active and Enable_Flag is inactive, the device continues to monitor the protocol, and you can view real-time data. However, no data is logged to the database.
Enable_Flag_Default	Default for Enable_Flag. Do not modify this setting.
Host_Flag	Enables and disables host monitoring.
Conv_Flag	Enables and disables conversation monitoring.
ART_Flag	Enables and disables Application Response Time (ART) monitoring.
Host_Flag_Default	Default for Host_Flag. Do not modify this setting.
Conv_Flag_Default	Default for Conv_Flag. Do not modify this setting.
ART_Flag_Default	Default for ART_Flag. Do not modify this setting.
Active_Flag	Indicates if the switch should be configured to monitor this protocol. If protocol is set as inactive, it is not monitored in the switch and all logging-related flag settings are ignored.

Feature Comparisons—Packet Analyzer, Traffic Monitor, and TrafficDirector

Note If you are not using the Cisco TrafficDirector application, skip this section.

Packet Analyzer is a superset of the TrafficDirector Data Capture and Protocol Decode features.

Table 4 compares nGenius Traffic Monitor and TrafficDirector features.

Table 4: Feature-by-Feature Product Comparison, Traffic Monitor and
TrafficDirector

RMON Group Name and Number	Traffic Monitor Feature	TrafficDirector Feature
Statistics(1)	Data Link Layer view None; achieved with different views None; achieved with different views Link Usage	TrafficMonitor Segment Zoom Segment Details Domain History
History(2)	Short-Term Usage Long-Term Usage	Short-Term History Long-Term History
Alarms(3) Events(9)	Alarm Viewer	Alert Monitor
Hosts(4)	All Hosts Host Zoom Host Usage	All Talkers Host Zoom Host History
Host TopN(5)	TopN Hosts	TopN Talkers
Matrix(6)	All Conversations Conversation Usage	All Conversations Conversation History
Filter(7)	nGenius Server	Filter Editor
Capture(8)	None (part of nGenius RTM Packet Analyzer module)	Data Capture
Token Ring(10)	Ring Monitor Source Routing	Ring Station Lis t Source Routing
ProtocolDir(11)	All Traffic	Domain Discovery
ProtocolDist(12)	Application Layer group view	Protocol Monitor
	Network Layer group view TopN Protocols All Protocols	Stored in EtherStats
	None (TopN Protocols and All Protocols provide similar functions)	Protocol Zoom
	Protocol Usage	Protocol Zoom (stored in EtherStats)
AddressMap(13)	All Hosts, TopN Hosts, All Conversations, TopN Conversations (database stores network-to-MAC mapping)	All Talkers , TopN Talkers, All Conversations (database mapping done in nettomac command-line application)
NLHost(14)	All Hosts	All Talkers
NLMatrix(15)	All Conversations TopN Conversations	All Conversations TopN Conversations
ALHost(16)	All Hosts	All Talkers
ALMatrix(17)	All Conversations TopN Conversations	All Conversations TopN Conversations
UsrHistory(18)	None	Custom History
ProbeConfig(19)	nGenius Server Admin	Configuration Manager
ATMRMON	ATM Traffic	ATM Monitor
SMON	SMON Monitor	SMON Monitor
HCRMON	Supported	Supported
ARTMIB	None None None nGenius Server Admin Element Info/Contact Element nGenius Server Admin None	ART Monitor ¹ Round Trip Delay Proxy SNMP Remote Login Agent Test Domain Editor Trend Reporter ²

¹Contact NetScout Systems for information about applications that provide Application Response Time (ART) monitoring functionality.
²Contact NetScout Systems for information about applications that provide trend reporting functionality.

Known Problems

Known problems are unexpected behaviors or defects in RTM software releases. They are graded according to severity level. These release notes contain information for severity levels 1 and 2.

You can search for known problems using Bug Navigator II, the Cisco bug tracking tool. To access Bug Navigator II, log into Cisco.com and select
Service & Support>Technical Assistance Center>Tools>Software Bug Toolkit>Bug Navigator II or enter http://www.cisco.com/support/bugtools in your web browser.

Table 5: nGenius RTM Known Problems

Bug ID	Summary	Explanation
CSCdu31670	Installation documentation error.	There is a typographical error in Step 2 on page 2-17 of the section, "Start the Real-Time Monitor Server," in the Real-Time Monitor Installation Guide. The step incorrectly reads: 2 Type su -<`secured username`> to log in as the secured user. The instructions should read: 2 Type su - <`secured username`> to log in as the secured user. You must type a space before the <secured username>, otherwise, the RTM server does not start as root; the next reboot of the server will not allow the secured user to start the RTM server, and therefore, RTM is unusable.
CSCdu60429	nGenius UNIX uninstallation guide documentation error.	The correct steps to perform the uninstallation are: Step 1 Log in as the root user. Step 2 Stop the nGenius Server. Step 3 Insert the RTM 1.2 product CD-ROM into the CD-ROM drive. Step 4 Enter these three commands: `cd <nGenius root installation directory>` (for example, /opt/nGenius) `/<cdrom>/solarisjre/bin/jre -cp .:/<cdrom>/solarisjre/lib/rt.jar uninstallpa /<cdrom>/solarisjre/bin/jre -cp .:/<cdrom>/solarisjre/lib/rt.jar uninstall` Step 5 Remove the nGenius root installation directory (for example, rm -fr /opt/nGenius).
CSCdr97781	RTM does not learn port name on 2900XL and 3500XL switches.	RTM looks at the ifAlias instead of the ifName on Catalyst 2900XL and 3500XL switches.
CSCds12017	RTM learns only ports that are up on 2924XL switches.	Ports with ifSpeed of zero are not learned.
CSCdt14818	Upgrading SwitchProbe software via Remote Login results in timeout error.	When you upgrade firmware in a SwitchProbe device using the Remote Login button from nGenius Server>Device Configuration, the upgrade times out. To work around this problem, upgrade the SwitchProbe device using the console port.
CSCdt28209	The cacls.exe file should not be displayed during installation on Windows.	See the "Updating Registry Files During Installation on Windows NT and Windows 2000 Servers" section.
CSCdt30078	RTM displays invalid login errors when server is restarted.	If the nGenius Server has been restarted, but the client browser has not, attempts to log in result in errors. To work around this problem, restart the client browser, then log in.
CSCdt34319	RTM displays an error message if Java plug-in is not installed on Solaris client.	Make sure you install the Java plug-in before trying to launch RTM.
CSCdt28443	RTM does not report errors when roving ports.	On some Catalyst 5000-family switches with an installed NAM, RTM reports that a port was roved successfully even if the rove failed. After you right-click on the roved port or VLAN, only the data link layer view is available; the network and application layer views are grayed-out. Switch firmware releases that exhibit this problem are 4.5(4) and 5.2(2). Switch firmware releases that do not exhibit this problem are 4.5(8), 4.5(10), 5.5(5), and 6.1(1b).
CSCdt30076	Error message displayed when performing a data capture with NetFlow on Catalyst 6000 NAM is not meaningful.	Performing a data capture against NetFlow is not supported. Therefore, the following error is not meaningful in this context: `Error creating datacapture session on device, Details: Couldn't create datacapture session; Unidentified Error, Severity:1, Code:8026, Severity 4, Code: 16116` Note This happens only on the NetFlow interface. If you span ports, VLANs, or FECs, the data capture works properly.
CSCdt30089	RTM becomes unstable after long periods of time.	If the RTM client runs for a long period of time, the Traffic Monitor module becomes out of sync with the Server. (For example, when you add a new device, it does not show in Traffic Monitor or Packet Analyzer.) To work around this problem, restart the browser.
CSCdt30090	RTM does not log users out after long periods of inactivity.	To avoid the potential for unauthorized access, make sure to log out after you finish using RTM.
CSCdt30891	RTM 1.2 does not support HP-UX clients.	Future client support is planned for HP-UX.
CSCd37011	nGenius installation prompts to install registry keys on Windows.	See the "Updating Registry Files During Installation on Windows NT and Windows 2000 Servers" section.
CSCdt22462	Long delay while downloading console on Windows 2000 clients.	On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances). After the applet has been loaded and cached locally, the problem no longer occurs. The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems. Because of this, downloading is significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.) To work around this problem, disable your virus scanner. Doing so will considerably improve Java applet download times. You can also disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension). Exact instructions vary depending on the virus scanner installed on your system. If you are using Norton AntiVirus 2000, disable the Auto-Protect feature. If you are using McAfee VirusScan: 1. Close and exit any programs that are actively downloading. 2. Launch the VirusScan console. 3. Click Configure.
CSCdt22462 (continued)		4. Select the Detection tab. 5. Verify that Enable Internet download scanning is not selected. 6. Select Program files only. 7. Click Apply. 8. Click OK. For more information, see the following article: http://support.microsoft.com/support/kb/articles/q240/3/09.asp
CSCdt36673	Uninstalling RTM does not stop nGenius services.	If the uninstallation program is run before the nGenius services shut down, RTM is only partially removed. To recover, you must shut down the nGenius services from the Services Control Panel, run the uninstallation program again, reboot the system, then remove the remaining ngenius directory manually. To work around this problem, make sure to shut down the nGenius services before starting the uninstallation.
CSCdt36936	Uninstalling RTM does not remove all files.	On Windows platforms, the uninstallation program does not remove all files; several directories under the ngenius install directory remain. To work around this problem, manually remove the ngenius installation directory after running the uninstallation program.
CSCdt73025	RTM does not support Catalyst 6000 NAM Multilayer Switch Module (MSM).	RTM 1.2 does not support the Catalyst 6000 family Multilayer Switch Module (MSM). When an MSM is installed in the switch with a gigabit EtherChannel (GEC) configured to channel to the MSM, the spanning ports to a Catalyst 6000 NAM fail. There is no workaround.
CSCdt30080	RTM does not learn roving information from switches.	When a switch is added to RTM, no roving information already on the switch is learned. RTM does not display the network and application layer views from the roved port or VLAN. To work around this problem: 1. Click the Spanning... button in the nGenius Server. 2. Select a port or VLAN other than the one currently being roved. 3. Apply your changes. 4. Reselect the port or VLAN to rove. You should now see network and application layer information for that port.
CSCdt53629	RTM installs custom protocols incorrectly in protocolDirTable.	An example is with the well-known Apache HTTP port 8080. The OID string for that port is 0.0.31.144. After installing the global settings on the SwitchProbe and Catalyst 6000 NAM and performing a walk on protocolTableDir, the OID string stored in protocolDirParameters is 0.0.1.136. This occurs when editing a previously defined custom protocol entry. (When creating the custom protocol for the first time, the OID is set correctly.) To work around this problem, delete the entry an recreate it as a new one.
CSCdt58814	Devices in Catalyst 6000 switch family with NAM are marked as Generic after importing from TrafficDirector Release 5.8.2 into RTM.	After importing devices from TrafficDirector Release 5.8.2 into RTM, you cannot see the NAM using Device Configuration>Details. To work around this problem, delete the device and add it again to the nGenius Server.
CSCdt54876	Secure user created by following Installation Guide instructions allows remote access.	Using the following example, assume you want to use the name ngenius as the secured user and group. To do this: 1. Add "ngenius:x:user_id:group_id::/tmp:" to the /etc/passwd file. 2. Add "ngenius::group_id:" to the /etc/group file. 3. Add "ngenius:LK:::::::" to the /etc/shadow file. 4. Start the nGenius Server by entering this command: `su ngenius -c ngenius_dir/bin/start` This procedure locks the account, thereby disabling remote logging to the server by the genius user and group.
CSCdp82231	Cannot add two Catalyst 6000 NAMs in the same switch using RTM.	The following example shows that a second NAM installed in a Catalyst 6000 NAM is not recognized by RTM: 1. Install two NAMs in the same Catalyst 6000 switch—one in slot 3 (3/01) and one in slot 5 (5/01). 2. Add the switch to RTM. 3. The analyzer port is displayed as 5/01. 4. Edit the switch definition and change the analyzer port to 3/01. 5. Everything appears to configure properly, but the analyzer port is still shows 5/01 instead of 3/01. There is no workaround to this problem. Support is currently limited to a single NAM installed in each Catalyst 6000 switch.
CSCdt37000	Launching default views for a NAM does not display all data.	Launching the Defaults Views for a NAM does not display data for the network and application layers if you select Show Utilization as the default. The views and legends are displayed but the bars are not drawn (although the bars for data link layer are drawn). There is no known workaround.
CSCdt39188	Launching a second nGenius module from CiscoWorks2000 results in the first module shutting down.	In the following example, the second nGenius module launched (Traffic Monitor) will unexpectedly shut down the first one (Server Admin): 1. Log into CiscoWorks2000. 2. Click Management Connection> Connections>nGenius. 3. Click an nGenius module (for example, Server Admin). 4. Log into nGenius. 5. Click another nGenius module (for example, Traffic Monitor). 6. Log into nGenius. The Server Admin process started in Step 3 unexpectedly shuts down. To work around this problem, access additional nGenius modules from any modules already running.
CSCdt51117	Packets counted twice when roving a VLAN to NAM or SwitchProbe device.	When used to rove a VLAN to a Catalyst 6000 NAM or SwitchProbe device, RTM configures the rove (span) session with the direction set to BOTH (Tx and Rx; transmit and receive). For most Catalyst supervisor modules (except sub-models F6020 and F6020A), the span feature sends two copies of each packet to the destination port, thereby resulting in double the actual statistics. To work around this problem, you must manually reconfigure the span direction to either transmit or receive. For example, if the rove is VLAN 10 to a SwitchProbe device or NAM on port 4/1, you must: 1. Telnet to the switch. 2. Enter one of these commands from the switch CLI to ensure that only one copy of the packet is sent: `set span 10 4/1 tx set span 10 4/1 rx`
CSCdt62297	RTM and another trap receiver application cannot coexist.	If you install RTM and another trap receiver application (such as TrafficDirector or Device Fault Manager) on the same server, you must configure each application to receive traps properly. By default, RTM listens on port 162. To change the setting so that RTM is not the primary listener application: 1. Stop the nGenius Server. 2. Open the file //nGenius_dir/bin/serverprivate.properties (where nGenius_dir is the complete path to the installed nGenius Server files). 3. Change the line that reads: devicelistener.portlist=162,395 to read: devicelistener.portlist=395 4. Save and close the serverprivate.properties file. 5. Restart the nGenius Server. 6. Follow the instructions in the documentation for the other trap receiver application to forward traps to port 395.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

NetScout is a registered trademark and the nGenius family of trademarks are trademarks of NetScout Systems, Inc.

AccessPath, AtmDirector, Browse with Me, CCDE, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0105R)

Table of Contents