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

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

You must 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	Provided As	Contains
Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.3 (this document)	Cisco Systems	Hardcopy	Cisco-specific product, feature, and release note information to supplement the NetScout documentation.
NetScout nGenius Real-Time Monitor 1.3 Release Notes	NetScout Systems	Hardcopy	Detailed information about changes and new functionality since RTM Release 1.2.
NetScout nGenius Real-Time Monitor 1.3 Installation Guide	NetScout Systems	Hardcopy and PDF on RTM CD-ROM	Instructions for installing all RTM components.
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.

Special Note about Probes and Other Monitoring Devices

Although not always explicitly stated in the NetScout nGenius hardcopy and online documentation, 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 more information about NetScout probes, see the hardware and agent documentation you received with your NetScout probe.
For more information about Cisco SwitchProbe devices or NAMs, see the Cisco SwitchProbe, Catalyst 5000 NAM, or Catalyst 6000 NAM documentation you received with your hardware.

Special Note about Physical Interface Limits

Page 26 of NetScout nGenius Real-Time Monitor 1.3 Release Notes describes the limits for physical interfaces as 50 active probe physical interfaces and up to 10,000 active switch ports.

RTM Release 1.3, as provided by Cisco systems, does not impose hard limits on the number of physical interfaces you can add to the nGenius Server. However, with a minimum system configuration, it is recommended that you follow these guidelines.

Important Installation Notes

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

Obtaining a License Activation Key Not Required

RTM Release 1.3, as provided by Cisco Systems, does not require a license activation key. Therefore, you can disregard the license activation instructions
in the NetScout nGenius Real-Time Monitor 1.3 Release Notes and the
NetScout nGenius Real-Time Monitor 1.3 Installation Guide.

Upgrading from RTM Release 1.2 to Release 1.3

After upgrading from RTM Release 1.2 to Release 1.3, but before you start the nGenius Server, make sure you upgrade your database.

Tip It takes approximately 1 hour per GB to upgrade the database. The size of the new database increases by approximately 15 percent. Be sure you have sufficient disk space before you begin the upgrade.

Windows Systems

Step 1 Go to the new RTM installation directory.

Step 2 Change directory to bin.

Step 3 From a DOS command window, run dbupgrade.bat.

UNIX Systems

Step 1 Go to the new RTM installation directory.

Step 2 Change directory to bin.

Step 3 From a UNIX shell, run dbupgrade.sh.

Creating Secured User Account with No Remote Login Privileges

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

During installation, RTM automatically creates the secured user ngenius. All RTM files are fully accessible (with read, write, and execute permissions enabled) only to an administrator logged in as the secured 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 system 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 the Installation" section in Chapter 2 of NetScout nGenius Real-Time Monitor 1.3 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 the Installation" section in Chapter 2 of NetScout nGenius Real-Time Monitor 1.3 Installation Guide.

Installing and Starting RTM on Windows 2000 and
Windows NT Systems

Note To install RTM on Windows 2000 and Windows NT systems, you must log in as a local administrator (not a domain administrator).

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

Caution about Java Plug-In Support

It is critical that you use only the supported Java plug-in versions listed in NetScout nGenius Real-Time Monitor 1.3 Release Notes and NetScout nGenius Real-Time Monitor 1.3 Installation Guide.

Caution 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
(English and Japanese)
Windows NT 4.0 Server or Workstation with Service Pack 6a (English and Japanese)
Sun Solaris Release 2.6, 2.7, or 2.8
IBM-AIX 4.3.3
HP-UX 11.0

Installing Required Third-Party Applications

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

Note Each of these applications is provided to you as a convenience, but 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

TimeSaver If you are not using Cisco TrafficDirector, you can 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, you should 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 parameter nGenius.nsminuse 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 Only 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 fails, 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 generate 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 historical reports for up to 31 days and summary reports for 366 days. (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.

TimeSaver You should 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 $RTMHOME\bin folder (on Windows systems) or $RTMHOME/bin (on UNIX systems).

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

Step 3 Add this string to the file:

: stealth.nsminuse=true

Step 4 Save your changes.

Step 5 Close the serverprivate.properties file.

Integrating RTM with the CiscoWorks2000 Desktop

The RTM installation dynamically creates Cisco Management Connection (CMC) files for each available application; these files initially reside in the nGenius\bin folder (on Windows systems) or nGenius/bin (on UNIX systems).

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 is installed.

If CiscoWorks2000 and RTM are installed on the same system, the files are copied automatically to this CiscoWorks2000 folder:

On Windows systems—$NMSROOT\htdocs\xml\public\maintree
On UNIX systems—$NMSROOT/htdocs/XML/Public/maintree

: 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 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.

Note 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
3550XL
3900
3920
4000
4003
4006

4908G
5000
5002
5500
5505
5509
6000
6006

6009
6500
6506
6509
6513
CPW2200
Generic

Configuring the Cisco Catalyst 6000 Network Analysis Module

To configure the Cisco Catalyst 6000 Network Analysis Module (NAM), you use 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. (Support is limited to a single NAM installed in each Catalyst 6000 switch.)

Note For more information, see the Catalyst 6000 Family Network Analysis Module Installation and Configuration Note on Cisco.com.

To use NetFlow Data Export (NDE) as a traffic source for the NAM, enable the NetFlow Monitor option so the NAM receives the NDE stream. The statistics are presented on reserved ifIndex.3000.

Note For more information, see the Catalyst 6000 Family Software Configuration Guide on Cisco.com.

To enable the NetFlow Monitor option on the NAM:

Step 1 Enter this command at the switch command line:

set snmp extendedrmon netflow enable mod

Step 2 Add the switch to the nGenius Server.

Step 3 Start Traffic Monitor.

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

Configuring the Cisco Catalyst 5000 Network Analysis Module

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
(on Windows systems) or nGenius_dir/data (on UNIX systems).

Step 2 Make a copy of Nam_Protocol_Config.dat.

Step 3 Rename the copied file Nam_Protocol_Config_Copy.dat.

Caution If you do not use this exact filename, the configuration will fail.

Step 4 Use a 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 it appears 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 (on Windows systems) or nGenius_dir/bin (on UNIX systems).

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 change this information.
Protocol_Type_Code	Unique protocol identifier. Do not change this information.
Enable_Flag	Indicates whether 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 change 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 change this setting.
Conv_Flag_Default	Default for Conv_Flag. Do not change this setting.
ART_Flag_Default	Default for ART_Flag. Do not change 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

TimeSaver If you are not using Cisco TrafficDirector, you can skip this section.

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

Table 4 compares nGenius Traffic Monitor and Cisco TrafficDirector features.

Table 4: Feature-by-Feature Product Comparison, nGenius Traffic Monitor and
Cisco 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 List 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 and Resolved Problems

Known problems are unexpected behaviors or defects in Real-Time Monitor software releases. They are graded according to severity level.

These release notes contain descriptions of:

All severity level 1 or 2 bugs.
Significant severity level 3 bugs.
All customer-found bugs (regardless of severity level).

You can search for problems using the Cisco bug tracking tool, Bug Navigator II. To access Bug Navigator:

Step 1 Log into Cisco.com.

Step 2 Select Service & Support>Technical Support Help—Cisco TAC>Tool Index.

Step 3 In the Jump to: links at the top of the page, click the letter S.

Step 4 Select Software Bug Toolkit/Bug Watcher>Bug Navigator II.

You can also access Bug Navigator by entering the following URL in your web browser: http://www.cisco.com/support/bugtools .

Table 5 describes the problems known to exist in this release; Table 6 describes the problems resolved since the last release of RTM.

Table 5: nGenius RTM Known Problems

Bug ID (Severity)	Summary	Explanation
CSCdt30078 (3)	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 (3)	RTM displays an error message if Java plug-in is not installed when using Netscape browser.	To work around this problem, you must install the Java plug-in before launching RTM.
CSCdv17614 (3)	Server Message log filter does not recognize Japanese date.	In the nGenius Server, when you select Administration>Message Log, then select View>Filter Messages, the customized date in the Filter Message dialog box is displayed in the local Japanese yy/mm/dd format. However, RTM does not recognize this format. To work around this problem, change the client operating system locale to the US date format mm/dd/yy.
CSCdv35177 (3)	(UNIX systems only.) RTM installation fails if there is not enough space in /tmp.	The following messages are displayed. `java.io.IOException: Not enough space at java.lang.UNIXProcess.init(UNIXProcess. java) at java.lang.Runtime.exec(Runtime.java) at java.lang.Runtime.exec(Runtime.java) at com.netscout.installation.extensions. launch.LaunchItems.executeAction(LaunchItems. java:87) at merlin.wizard.core.WizardActionLeaf$ ExecuteContext.run(WizardActionLeaf.java:500) setup class not found.` To work around this problem, clean up the /tmp directory or allocate more disk space for /tmp on your system.
CSCdt30090 (3)	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.
CSCdt36936 (3)	Uninstalling RTM does not remove all files.	After you uninstall RTM, several directories remain under the ngenius installation directory. To work around this problem, manually remove the ngenius installation directory after running the uninstallation program.
CSCdt36673 (3)	Uninstalling RTM does not stop nGenius services.	If you run the uninstallation program before the nGenius services shut down, RTM is only partially removed. To work around this problem, shut down the nGenius services (from the Services Control Panel) before starting the uninstallation.
CSCdt53629 (3)	RTM installs edited custom protocols incorrectly.	If you edit the port number of an existing custom protocol and apply the change, RTM uses the old OID string. To work around this problem, delete the custom protocol, then recreate it.
CSCdv23530 (3)	nGenius Alarm Viewer does not show DLCI or PVC info for DLCI trap.	When enterprise-specific DLCI traps are sent to the nGenius Server, there is DLCI or PVC information in the trap data. However, the RTM Alarm Viewer does not show any of the DLCI/PVC information, making the displayed trap information unusable because there is no way to determine which DLCI or PVC has changed.
CSCdv24809 (3)	RTM cannot clean up collected data.	There is no utility to reduce the size of collected data in the RTM database. By default, nGenius turns on logging for all protocols; as a result, stealth.db can grow quickly when there are many PVCs or DLCIs.
CSCdv11244 (3)	RTM cannot configure any VLAN threshold traps.	RTM can configure normal switch port RMON threshold traps as expected. However, there is no way to configure VLAN threshold traps without roving to a NAM or SwitchProbe device, even when the VLAN has an ifIndex number.
CSCdv24821 (3)	RTM cannot recover a user-defined configuration.	It is recommended that you use traditional, frequent database backup procedures to preserve and protect your environment.
CSCdt39188 (3)	A second RTM module launched from CiscoWorks2000 shuts down the first module.	In the following procedure, the second RTM module unexpectedly shuts down the first one: 1. Log into CiscoWorks2000. 2. Click Management Connection> Connections>nGenius. 3. Click an RTM module (for example, Server Admin). 4. Log into nGenius. 5. Click another RTM module (for example, Traffic Monitor). 6. Log into nGenius. The Server Admin process you started in Step 3 shuts down. To work around this problem, access additional RTM modules from any modules already running.
CSCdv44677 (3)	RTM does not allow short- and long-term usage on VLANs and FECs.	The options in the user interface for Short-Term Usage and Long-Term Usage for FECs and VLANs should not be disabled. There is no known workaround.
CSCdv31663 (3)	Installation fails on Windows systems with server (netBIOS computer) name ngenius.	On Windows NT systems, the server name and user names are assigned unique Security Identifiers (SIDs). RTM does not recognize when the server name and user names are both ngenius. To work around this problem, change the Windows system name.
CSCdv44438 (3)	Adding a Catalyst 1900 switch to RTM fails on Fast Ethernet ports.	When a Catalyst 1900 switch is added to RTM, the operation fails on Fast Ethernet ports 26 and 27. There is no known workaround.
CSCdp82231 (3)	Cannot add two Catalyst 6000 NAMs in the same switch if the switch uses RTM.	RTM does not recognize two NAMs installed in the same switch, as in the following example: 1. You install two NAMs in the same Catalyst 6000 switch—one in slot 3 (3/01) and one in slot 5 (5/01). 2. You add the switch to RTM. 3. The analyzer port is displayed as 5/01. 4. You 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 for this problem. Support is currently limited to a single NAM installed in each Catalyst 6000 switch.
CSCdv44830 (3)	In enterprise environments, RTM requires high-end PCs with excessive amounts of resources.	RTM must increase logging performance and memory to allow reasonably configured high-end PCs to function correctly in an enterprise environment. RTM experiences low memory conditions in some high-end PCs (for example, on a system with two 1 GB CPUs, 1 GB of physical memory, and 26 GB of disk space and an Ultra 160 disk controller) if the server is configured with 100 physical and 1000 virtual interfaces, and the MAX_JVM_MEMORY setting on the nsstart.bat file is 900 MB. To work around this problem, add more memory to your system.
CSCdt62297 (3)	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 this line: `devicelistener.portlist=162,395` to: `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.
CSCdv24838 (3)	nGenius Packet Analyzer does not decode RTP protocols.	nGenius Packet Analyzer does not decode the RTP protocol correctly. It might show all RTP packets as VIA-FTP.
CSCdt51117 (3)	Packets are counted twice when a VLAN is roved to a 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 engine modules (except submodels F6020 and F6020A), the span feature sends two copies of each packet to the destination port which results in doubling the actual statistics. To work around this problem, manually reconfigure the span direction to either transmit or receive. For example, if the rove is VLAN 10 to a NAM or SwitchProbe device 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`
CSCdv28150 (3)	Traffic Monitor does not save Scene/Show customization.	After you select several views for a SwitchProbe device or a switch with customized settings for show by bytes, show by utilization, and so on, the views are not saved correctly. For example: 1. Launch Traffic Monitor. 2. Select a SwitchProbe device. 3. Launch several views. 4. Select Show>Packet Size. 5. Select File>Scene Save As.
CSCdv28150 (continued)		6. Enter a scene name. 7. Exit Traffic Monitor. 8. Restart Traffic Monitor. 9. Select File>Load Scene. 10. Select the scene you saved in Step 5. The customized Show and View layouts are not the same as those you saved (for example, Packet Size might become Utilization).
CSCdt77889 (3)	nGenius Server does not start if another application uses port 1099.	If you install RTM on a system where no other applications are using port 1099, RTM uses port 1099. If another application tries to bind to port 1099 while nGenius is using this port, that application will fail. However, if the nGenius Server is not running when another application binds to port 1099, that application continues working successfully while the nGenius Server cannot start. To work around this problem, change the RMI port used by RTM by manually editing the $RTMHOME/bin/serverprivate.properties and $RTMHOME/html/client.properties files. In those files, change the RMIRegistryPort=1099 to RMIRegistryPort=1100 (or the next available TCP port).

Table 6: nGenius RTM Resolved Problems

Bug ID (Severity)	Summary	Additional Information
CSCdr97781 (2)	RTM does not learn port name on 2900XL and 3500XL switches.	None.
CSCds12017 (2)	RTM learns only those ports that are up on 2924XL switches.	None.
CSCdt14818 (3)	Upgrading SwitchProbe software via Remote Login results in timeout error.	None.
CSCdt30089 (2)	RTM becomes unstable after long periods of time.	None.
CSCdt28443 (3)	RTM does not report errors when roving ports.	None.
CSCdu31670 (2)	Installation documentation error.	The error in the instructions for logging in as a secured user has been fixed.
CSCdu60429 (2)	nGenius UNIX uninstallation documentation error.	The error in the instructions for uninstalling nGenius on UNIX systems has been fixed.
CSCdt73025 (2)	RTM does not support Catalyst 6000 NAM Multilayer Switch Module (MSM).	None.
CSCdt30891 (2)	RTM 1.2 does not support HP-UX clients.	Client support has been added for HP-UX in RTM 1.3.
CSCdt28209 (3)	The cacls.exe file should not be displayed during installation on Windows.	This file is no longer displayed during the installation.
CSCdt30076 (3)	Error message displayed when performing a data capture with NetFlow on Catalyst 6000 NAM is not meaningful.	This error message is no longer displayed.
CSCdt54876 (2)	Secure user created by following Installation Guide instructions allows remote access.	Remote access is no longer permitted.
CSCdu10043 (3)	SwitchProbes do not always display immediately in the Admin server.	None.
CSCdt37011 (2)	nGenius installation prompts to install registry keys on Windows.	These prompts are no longer displayed.
CSCdt37000 (2)	Launching default views for a NAM does not display all data.	Data for the network and application layers is now displayed.
CSCdu30173 (1)	nGenius RTM uninstall causes large core dumps.	None.
CSCdu38000 (2)	Error adding Catalyst 6509 switch with NAM.	None.
CSCdu28993 (1)	RTM server does not start; generates Not Enough Memory errors.	These errors are no longer displayed.
CSCdt30080 (2)	RTM does not learn roving information from switches.	None.
CSCdt82740 (1)	nGeniusSQL.sh does not work in RTM.	None.
CSCdu34434 (2)	nGenius does not handle NULL passwords correctly.	NULL passwords are now handled correctly.
CSCdu54282 (2)	Packet Analyzer indicates "Frame too short" with ATM probe.	This message is no longer displayed.
CSCdu47217 (2)	nGenius Packet Analyzer could not start dengine; core dump result.	None.
CSCdu43448 (2)	Packet Analyzer loads no packets with wrap-when-full option is selected.	None.
CSCdu36658 (2)	RTM does not decode Frame Relay captures above Layer 2.	None.
CSCdt58814 (3)	Devices in Catalyst 6000 switch family with NAM are marked as Generic after importing from TrafficDirector Release 5.8.2 into RTM.	These devices are no longer marked as Generic.
CSCdu31718 (3)	nGenius RTM server start script hard codes ulimit as -n 512.	The ulimit is now 768.
CSCdu47217 (2)	nGenius Packet Analyzer could not start dengine with core dumps.	None.
CSCdv05538 (2)	Unable to edit DLCI CIR in RTM.	None.
CSCdv13755 (3)	Packet Analyzer does not decode Frame Relay LMI packets properly.	None.
CSCdv07646 (3)	nGenius shows 2948G ports incorrectly.	None.
CSCds30966 (1)	Network and Application layers unavailable for NAM ports.	None.
CSCdt90215 (2)	(Windows systems only.) Main java.exe stops when a user logs out of the system.	None.
CSCds30966 (1)	Network and Application layers unavailable for NAM ports.	None.
CSCdt90215 (2)	(Windows systems only.) Main java.exe stops when a user logs out of the system.	None.
CSCdt18389 (1)	Unable to add a 6K NAM to nGenius.	Errors are no longer displayed when adding a Catalyst 6506 switch with an installed NAM to the nGenius Server.
CSCdt22462 (2)	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 6 minutes in some instances). After the applet has been loaded and cached locally, the problem no longer occurs. The delay is caused by filtering mechanisms such as virus scanning on the client. Because some virus scanners automatically scan content downloaded by browsers, a delay might occur. To work around this problem, disable your virus scanner to considerably improve Java applet download times. You can also disable automatic scanning of downloaded files and enable scanning of program files only. Exact instructions to disable scanning vary with the virus scanner installed on your system; refer to the appropriate vendors' documentation. For more information, see the article How to Fully Disable Antivirus Software from Filtering Files at: http://support.microsoft.com/support/kb/articles/q 240/3/09.asp

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

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

Ordering Documentation

Note To order printed copies of the NetScout documentation, contact NetScout Systems directly.

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

: http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

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 by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity
Resolve technical issues with online support
Download and test software packages
Order Cisco learning materials and merchandise
Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

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

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

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

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

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

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.

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

AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, 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 Press, 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. (0108R)

Table of Contents

Windows Systems

UNIX Systems

Installing and Starting RTM on Windows 2000 and Windows NT Systems

Installing and Starting RTM on Windows 2000 and
Windows NT Systems