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

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

Document	Written By	Provided As	Contains
Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 (this document)	Cisco Systems	Hardcopy	Cisco-specific product, feature, and release note information to supplement the NetScout documentation.
NetScout nGenius Real-Time Monitor 1.4 Release Notes	NetScout Systems	Hardcopy	Detailed information about changes and new functionality since RTM Release 1.3.
NetScout nGenius Real-Time Monitor 1.4 Installation Guide	NetScout Systems	Hardcopy	Instructions for installing all RTM components.
NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide	NetScout Systems	PDF on RTM CD-ROM	Instructions for using the RTM web- based network monitoring and protocol and network analysis modules.
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 and 6500 series 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 and 6500 Series NAM documentation you received with your hardware.

Special Note about Physical Interface Limits

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

RTM Release 1.4, 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:

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 Appendix A of NetScout nGenius Real-Time Monitor 1.4 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 Appendix A of NetScout nGenius Real-Time Monitor 1.4 Installation Guide.

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.4 Release Notes and NetScout nGenius Real-Time Monitor 1.4 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 2
(English and Japanese)
Windows NT 4.0 Server or Workstation with Service Pack 6a
(English and Japanese)
Sun Solaris Release 2.7 or 2.8

Note OS patch 107153-01 is required for Chinese OS running on Solaris 7.

IBM-AIX 4.3.3
HP-UX 11.0

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.

Supported Cisco Devices

Although other vendors' devices are listed in the NetScout documentation, Cisco Systems supports only those devices listed in Table 2.

Table 2 lists the devices supported by Cisco Systems.

Note For information about support for other devices, contact NetScout Systems.

Table 2: Cisco Catalyst Switches Supported by RTM

1200
1800
1900
1912
1924
2908XL
2912XL
2912MFXL
2916M-XL
2924XL
2924CXL

2924MXL
2924XLV
2924CXLV
2926
2926G
2948G
2948G-L3
2950-12
2950-24
2950C-24
2950G-12

2950G-24-DC
2950G-24-EI
2950G-48
2950T-24
2980G
3000
3100
3200
3508GXL
3512XL
3524XL

3550-24
3550-24DC
3550-24MMF
3550-48
3900
3920
4003
4006 (Sup II)
4908G-L3DC
4912G
5002

3548XL
3550-12G
5500
5505
6006
6009
6506
6509
6513
8510
8540
ONS 15327
ONS 15454

Enabling DSMON on a Catalyst 6000 and 6500
Series NAM

The DSMON MIB is disabled by default. To collect DSMON data from your network, you must enable the DSMON MIB on the NAM. After it is enabled, you can view DSMON data with Traffic Monitor.

Note To view DSMON statistics with a Catalyst 6000 and 6500 series NAM, you must be running NAM software release 2.1(x).

Step 1 On the system on which the nGenius Server is installed, go to the $RTMHOME\rtm\bin\admin folder.

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

Step 3 Set the dsmon.enbabled parameter to true.

dsmon.enabled=true

Step 4 Save your changes and close the file.

Step 5 Stop the nGenius server.

Wait until all RTM-related processes are complete.

Step 6 Start the nGenius server.

Modifying the DSMON Aggregation Profile

Using a text editor, you can modify the parameter dsmon.aggregation.profile
as necessary. You must restart the nGenius server for the changes to take effect.

Table 3 shows the options for each aggregation profile.

Table 3: DSMON Aggregation Profiles

Profile #	Aggregation Profile	Description
1	Voice Profile (default)	There are four code point groups: Code point 0—DSCP0 group Code point 26—Voice Control group Code point 46—Voice RTP group Code points 1-25, 27-45, 47-63—Other DSCP group
2	One group profile	Code points 0-63 are in one group—Group 0.
3	Four group profile	There are four code point groups: Code points 1-15—Group 0 Code points 16-31—Group 1 Code points 32-47—Group 2 Code points 48-63—Group 3
4	Eight group profile	There are eight code point groups: Code points 0-7—Group 0 Code points 8-15—Group 1 Code points 16-23—Group 2 Code points 24-31—Group3 Code points 32-39—Group 4 Code points 40-47—Group 5 Code points 48-55—Group 6 Code points 56-63—Group 7
5	Sixty-four group profile	Each code point has a group. For example: Code point 0—Group 0 Code point 1—Group 1

nGenius VoIP Monitor

The VoIP software component allows legacy SwitchProbe users to monitor voice and video traffic traveling on your network. Only those devices that support VoIP are displayed in the VoIP Navigation tree.

To use the VoIP Monitor, you must have a minimum of 32MB of RAM in your SwitchProbe device and be running NSP 5.2 firmware. This firmware version is only available from NetScout Systems.

Note For NSP 5.2 firmware, you must contact NetScout Systems.

The VoIP Monitor software component is not supported on the Catalyst 6000 and 6500 series NAMs and Catalyst 5000 series NAMs. However, you can use the Catalyst 6000 NAM Traffic Analyzer to monitor voice data. For more information on using Traffic Analyzer, see the User Guide for the Catalyst 6000 NAM Traffic Analyzer.

Enabling SMON Monitoring with Catalyst 6000 and 6500 Series NAMs

You must be running Catalyst 6000 and 6500 series NAM software release 2.1(1a) or later to use the SMON Monitor feature.

Note To view DSMON statistics with a Catalyst 6000 and 6500 series NAM, you must be running NAM software release 2.1(x) with patch 2.0. This patch can be downloaded from the following url:

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

Step 1 Log into the switch.

Step 2 Session to the NAM.

Step 3 Run the following commands from the NAM CLI:

autostart vlanstats enable
autostart priostats enable

Step 4 Reboot the NAM.

Configuring the Cisco Catalyst 6000 and 6500
Series NAM

To configure the Catalyst 6000 and 6500 series 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.

This section describes how to use RTM to install basic functionality and configure the NAM so it is recognized and can be managed by the nGenius Server and clients.

The instructions in this document assume that you have already installed and configured the NAM with an IP address, subnet mask, broadcast address, and default gateway, and that ping requests from the system on which RTM is running are successful.

Note If you have not already configured the NAM, and you are running Cisco IOS software, follow the instructions in the Catalyst 6000 Network Analysis Module Installation and Configuration Note. The configuration information in this document is for Catalyst 6000 and 6500 family switches running Catalyst OS software.

The primary function of RTM is to manage the RMON and RMON2 agents embedded in certain devices. To manage the Catalyst 6000 and 6500 series NAM with RTM, you must add the switch to the nGenius Server.

These sections provide more information:

Configuring the Catalyst 6000 and 6500 Series NAM

Before you can use the NAM for network analysis, you must log into the NAM root account and configure the following:

IP address
Subnet mask
IP broadcast address
IP host name
Default gateway
Domain name
DNS name server
SNMP MIB variables
Access control for the SNMP agent
System group settings on the NAM

To configure these parameters for the NAM, perform these steps in privileged mode:

Step 1 Enter this command to verify that the NAM is installed and that the power is on.

Console> show module mod_num

Step 2 Establish a console session with the NAM by entering:

Console> (enable) session mod_num

Step 3 At the login prompt, type root to log into the root account.

Step 4 At the password prompt, type root as the root password.

Note If you have not changed the password from the factory-set default, a warning message displays.

Step 5 Configure the IP address and subnet mask by entering:

root@localhost# ip address ip-address subnet-mask

Step 6 Configure the IP broadcast address by entering:

root@localhost# ip broadcast broadcast-address

Step 7 Configure the IP host name used in the CLI prompt, show commands, and log messages by entering:

root@localhost# ip host name

Step 8 Configure the default gateway by entering:

root@localhost# ip gateway default-gateway

Step 9 Configure the domain name for the NAM by entering:

root@localhost# ip domain domain-name

Step 10 Configure one or more IP addresses as DNS name servers by entering:

root@localhost# ip nameserver ip-address [ip-address]

Step 11 Verify the NAM configuration by entering:

root@localhost# show ip

Step 12 Configure the SNMP syslocation MIB variable by entering:

root@localhost# snmp location location-string

Note The MIB variables in Step 13 and Step 14 must be valid DisplayString texts, each with a maximum length of 64 characters.

Step 13 Set the SNMP sysContact MIB variable by entering:

root@localhost# snmp contact contact-string

Step 14 Set the SNMP sysName MIB variable by entering:

root@localhost# snmp name name-string

Note You can delete the SNMP location, SNMP contact, or SNMP name by entering the respective command without any parameters.

Step 15 Set the SNMP agent community string parameter password for read-write access by entering:

root@localhost# snmp community community-string rw

Step 16 Set the SNMP agent community string parameter password for read-only access by entering:

root@localhost# snmp community community-string ro

Note Clear the SNMP community string with the snmp delete community community-string command.

Step 17 Verify the SNMP access controls and settings by entering:

root@localhost# show snmp

Adding a Catalyst 6000 or 6500 Switch to the nGenius Server

Before the nGenius Server can communicate with a switch in which a NAM is installed, you must configure the switch and NAM in a specific way, using these guidelines:

The switch and NAM must reside in the same subnet.
SPAN sessions in the switch must be disabled.
You must make sure that the read and write community strings for both the switch and NAM match.

For example, using the switch CLI command show snmp, you will see:

Community-Access   Community-String
----------------   ----------------
read-only          public
read-write         private

Using the NAM CLI command show snmp, you will see:

community   private  write
community   public   read

Using the RTM Device Configuration feature, enter the switch name, switch IP address, switch type, and the read and write community strings established on the switch.

After doing this, the nGenius Server automatically learns and displays the ports, VLANs, FECs, and NetFlow interfaces configured on the switch.

To add a new switch to nGenius Server:

Step 1 Start RTM from http:// rtm-server:port/.

Step 2 Click Login (in the lower-right corner of the NetScout Products window).

The login dialog box is displayed.

Step 3 Enter the login name and password.

Step 4 Click Login.

Step 5 To start the nGenius Server, click the Server icon in the NetScout Products window.

Step 6 In the Device Configuration window, select the Switch tab.

Step 7 Click Add.

The Add Switch dialog box is displayed.

Step 8 In the Switch Name field, enter a name for the switch you are defining.

The name is case-sensitive and can be a maximum of 40 alphanumeric characters. You can use hyphens and underscores but no spaces in the name. The name must be unique; that is, you cannot assign this name to another switch.

Step 9 In the IP Address field, enter a valid switch IP address.

This is the IP address of the switch in which the NAM is installed and consists of numbers separated by decimal points (nnn.nnn.nnn.nnn).

Step 10 In the Switch Type field, select the type of switch you are adding.

For example:

If the NAM is installed in a Catalyst 6006 switch, select CAT6006.
If the NAM is installed in a Catalyst 6509 switch, select CAT6509.

Step 11 In the community names fields, do the following:

a. Read Community—Enter the read community name established on the switch.

b. Write Community—Enter the write community name established on the switch.

Note The read and write community strings installed on the switch must match the read and write community strings on the NAM. For more information, see the "Identifying Community Strings on the NAM" section.

Step 12 In the Retries and Timeout fields, do the following:

a. Retries—Enter the number of times (between 1 and 32767) the nGenius Server should try to reach the switch if there is no response.

b. Timeout—Enter the length of time in seconds (between 1 and 32767) the nGenius Server should wait between each retry.

Step 13 Click OK.

This process might take approximately 1 to 3 minutes, depending on the number of ports in the switch and speed of the system on which the Server resides.

You can check the Task Progress Report for details.

Note The nGenius Server identifies the detailed configuration on a switch (in the Details window) after you add the switch to the nGenius Server.

Step 14 Create a SPAN session:

a. Select the switch.

b. Click Spanning.

The Switch Spanning dialog box is displayed.

c. Select the SPAN source.

You can select ports, VLANs, or FECs as the SPAN source.

Note You may only select ports, VLANs, or FECs for one span session.

d. Click Add.

e. Click OK.

You can now use Traffic Monitor and Packet Analyzer with the NAM.

Identifying Community Strings on the NAM

The read and write community strings in the switch must match the read and write community strings in the NAM.

Use the show snmp command to display basic information about the SNMP agent configuration. The output from this command can help you debug communication problems.

The following is an example of the information displayed for the NAM:

root@localhost# show snmp

SNMP Agent: nam1.cisco.com 172.20.52.99
SNMPv1: Enabled
SNMPv2C: Enabled
SNMPv3: Disabled
community public write
community private read
sysDescr "Catalyst 6000 Network Management Module (WS-X6380-NAM)"
sysObjectID 1.3.6.1.4.1.9.5.1.3.1.1.2.223
sysContact "Jane Doe, Cisco Systems, (408) 111-1111"
sysName "6k-NAM - Slot 2"
sysLocation "Cisco Lab, Building X, Floor 1"

The following is an example of the information displayed for the switch:

Cat6ksup1> (enable) show snmp

RMON:                      Enabled
Extended RMON Netflow Enabled :None.
Memory usage limit for new RMON entries:85 percent
Traps Enabled: None
Port Traps Enabled:None
 
Community-Access     Community-String
----------------     -----------------
read-only            public
read-write           private
read-write-all       secret
 
Trap-Rec-Address Trap-Rec-Community Trap-Rec-Port Trap-Rec-Owner
---------------- ------------------ ------------- --------------
Trap-Rec-Index host.domain.com public 162 root@host.domain.com 1

Note The switch read-only community string matches the NAM read community string (public); the switch read-write community string (private) matches the NAM write community string.

Enabling the NetFlow Monitor Option

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.

Spanning Switch Interfaces

Spanning is a mechanism used by the nGenius Server for monitoring individual interfaces supported by a switch. These interfaces can include physical switch ports (including access ports and trunks), VLANs, and FECs.

Step 1 Start Device Configuration if you have not already done so.

Step 2 Select the switch.

Step 3 Click Spanning.

A list of ports associated with the switch is displayed in the left pane.

To use the NAM, you must span a port, VLAN, or FEC to it. During spanning, data is sent to the NAM for analysis.

Step 4 In the left pane, select the port, VLAN, or FEC to SPAN.

Note A port list is displayed by default. However, you can view VLANs or FECs by selecting the appropriate tab.

Step 5 Click Add.

Step 6 Click OK.

Usage Tips

For each port, VLAN, or FEC that you spanned in the nGenius Server, you can now bring up the Data Link Layer, Network Layer, and Application Layer Views. Use the Show menu to see packet rate, byte rate, bit rate, utilization, and so on.
By right- clicking the Data Link Layer View, you can see Link Usage, Short- and Long-Term Usage, TopN RMON Hosts, TopN RMON Conversations, All RMON Hosts, All RMON Conversations, and so on.
By right-clicking the Network Layer View, you can see Protocol Usage, TopN NL Hosts, TopN NL Conversations, TopN NL Protocols, All NL Hosts, All NL Conversations, All NL Protocols, and so on.
By right-clicking the Application Layer View, you can see Application Usage, TopN AL Hosts, TopN AL Conversations, TopN AL Applications, All AL Hosts, All AL Conversations, All AL Applications, and so on.
You can use Packet Analyzer to perform data captures and decodes for each port, VLAN, or FEC that you spanned in the nGenius Server.

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 of 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)	nGenius RTM Packet Analyzer	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 (bugs) in Real-Time Monitor 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 Software Bug Toolkit. To access the Software Bug Toolkit:

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, then select Software Bug Toolkit.

You can also access the Software Bug Toolkit by entering the following URL in your web browser:

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

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
CSCdx40532 (2)	RTM Task Progress Report does not always work.	When adding or deleting a device in RTM, the Task Progress Report occasionally does not appear. To work around this problem, restart the client browser.
CSCdx56721 (2)	RMI cannot be tunneled across HTTP.	RTM supports a feature known as RMI-over-HTTP tunneling so that clients can access servers behind firewalls. This feature does not work in RTM 1.4 To work around this problem, open all TCP ports greater than 1024 so that the client can communicate directly with the server using RMI.
CSCdx56228 (3)	RTM should change to a default RMI port other than 1099.	RTM currently uses the default RMI port 1099 which can easily conflict with CiscoWorks 2000. To work around this problem, if you see errors regarding RMI port conflict, change RMIRegistryPort=1099 to another port that is not being used (such as RMIRegistryPort=1234) in the following files: `/opt/nGeniusRTM/1.3.0/bin/serverprivate.properties /opt/nGeniusRTM/1.3.0/html/client.properties`
CSCdx06011 (3)	You cannot SPAN the same interface to two analyzer ports.	This is a known limitation.
CSCdx03097 (3)	Processes not starting if only the administrator has full control on the hard-disk nGenius is installed on.	Make sure the root directory has permission set to Everyone Full Control before you install RTM. The correct permissions will propagate down the RTM directory structure.
CSCdx25484 (3)	Adding a Catalyst 6513 switch displays an error when you select Cat_6513 as the switch type.	To work around this problem, when you add a Catalyst 6513 switch running Catalyst OS software, select Cat_6509 as the switch type.
CSCdt37031 (3)	RTM does not have a command line installation for UNIX platforms.	This is a known limitation. UNIX platforms must have an X display with at least 256 colors.
CSCdx56265 (3)	NL/AL Hosts and NL/AL Conversations are disabled after upgrading.	NL/AL Hosts and NL/AL Conversations are disabled for SwitchProbe interfaces after upgrading RTM from 1.2 or 1.3 to 1.4. To work around this problem, if you don't have many SwitchProbes in your RTM server, you may relearn the probes from Device Details Windows. You can also update the stealth database: 1. Change the directory to $RTMHOME/rtm/bin. 2. On Windows platforms, execute the following commands. a. nGeniusSQL.bat sqlscripts\ AddNLALCapabilityCode.sql list.out -H b. nGeniusSQL.bat list.out On Solaris platforms, execute the following commands. a. ./nGeniusSQL.sh sqlscripts/ AddNLALCapabilityCode.sql list.out b. Edit the list.out file by removing the first two lines (header). c. ./nGeniusSQL.sh list.out 3. Restart RTM server
CSCdx56322 (3)	Time Triggers Data Capture does not work with Catalyst 6500 and 6000 Series NAMs.	This is a known issue.
CSCdx56482 (3)	RTM failed to start Data Capture for Catalyst 5000 NAM.	This is a known issue.
CSCdx56220 (3)	nGenius RTM does not support NIS+ for Solaris platforms.	If RTM is installed on a Solaris server with NIS+, there may be difficulties in creating an ngenius account, which will cause RTM to not install correctly. This is because the ngenius user account has to be authenticated on the NIS+ server and some NIS+ policies may not allowed such an account to be created. To work around this problem, create the ngenius user account and ngenius group on the following local machines: /etc/passwd /etc/shadow /etc/group
CSCdx36825 (3)	RTM does not properly learn a Catalyst 3548XL switch.	To work around this problem, when adding a Catalyst 3548XL switch, add the switch in Learn Only mode.
CSCdx40454 (3)	RTM indicates warnings when trying to add numerous switch types.	Since the trapDestTable is not supported on XL switches, RTM should not do SNMP SET on trapDestTable for XL switches. A warning message is displayed indicating a protocol write error when in fact, this should be considered normal for the XL switches. This message can be safely ignored.
CSCdx50068 (3)	Traffic Monitor does not display data in NL and AL views if a VLAN is spanned first.	To work around this problem, after you add a Catalyst 6000 switch to RTM, span a port (or ports) first. You can then remove the span session, and span VLANs.
CSCdw23024 (3)	RTM runs slow if accessed over a VPN network.	To work around this problem, you must add a Java Runtime parameter to your java Plug-in Control Panel. 1. Select Start>Settings>Control Panel. 2. Double-click the Java Plug-in. 3. In the Java Runtime Parameters text field enter: `-Djava.rmi.server.hostname=client_addr` Where client_addr is the client ip address assigned by your VPN client connection software.
CSCdx25995 (3)	RTM displays errors messages in the Windows Event Viewer.	These messages can be safely ignored.
CSCdv75516 (3)	Importing Cisco IOS switches from CiscoWorks 2000 failed.	The nGeniusciscoimport batch file proceeds without error messages even though the required dat files do not exist. To import Cisco IOS switches, use a text editor to edit the hwreport file. Replace the SysDescription string from "Cisco Internetwork Operating System" with the four numbers of the switch model you want to add. If you want to add a Catalyst 1900 switch, the string will read: `10.1.2.103,16 Oct 2001 14:01:28 CDT,,WS` 1900`,0x19,,8388608,32768,3927...`
CSCdx47037 (3)	RTM 1.3 does not have a way to export the inventory file.	RTM cannot export the inventory file to a CSV file for import to another RTM server or a newer version of RTM.
CSCdw05944 (3)	RTM does not support RSPAN for Catalyst 6000 and 6500 switches.	RTM cannot make use of the RSPN feature of Catalyst 6000 and 6500 switches.
CSCdu33990 (3)	Cannot open multiple nGenius applets with Management Connection.	To work around this problem, if you are using Internet Explorer 5.5, go to Tools>Internet Options>General>Settings, and click the Every visit to the page radio button. If you are using Internet Explorer 6.0, there is an additional step. Go to Tools>Internet>Options> Privacy>Advanced and click Override automatic cookies handling in the Cookies option. Make sure the browser accepts First-Party Cookies and Thrird Party Cookies.
CSCdu62782 (3)	nGenius Server Admin does not allow you to edit a switch type.	To change the switch type, delete the switch and add it again.
CSCdt61007 (3)	nGenius event viewer is not applicable for Catalyst switches.	Events sent by Catalyst switches do not contain a description field. Because the nGenius event viewer uses the description field, it cannot determine if the switch event was a rising or falling threshold.
CSCdu88839 (3)	Only one port can be spanned to a Catalyst 6000 and 6500 Series NAM in Cisco IOS switches.	You can only span to one port in a Catalyst 6000 and 6500 Series NAM in switches running Cisco IOS software.
CSCdu40080 (3)	There is no tool to recover or fix the nGenius database if it is corrupted.	If the database is corrupted you can recover the data by creating a new database and adding the old configuration data using dbunload and dbreload. 1. Navigate to the $RTMHOME/rtm/bin folder. 2. Run dbunload. This program copies your device configuration table information into the file unloadFiles located in the $RTMHOME/rtm/database directory. 3. Run dbreload. Only the configuration data is saved. All statistics data will be lost.
CSCdx11845 (3)	RTM cannot set different short and long term history parameters for SwitchProbe devices.	This is a known limitation.
CSCdx14660 (3)	Adding a switch to RTM displays an error when selecting automatic as the switch type.	Adding a switch using automatic switch type will display a "Device not recognized" error. When adding a switch, select the matching switch type.
CSCdx15811 (3)	RTM does not learn VLANs for a Catalyst 4006 switch with a Supervisor 3.	RTM does not support the Catalyst 4006 switch with a Supervisor 3 with this release.
CSCdx15887 (3)	Adding a Catalyst 6509 and 6513 switch running Cisco IOS 12.1 generates a protocol write error.	RTM does not support Cisco IOS 12.1 with this release.
CSCdx15897 (3)	Using different read/write community strings between the switch and the NAM does not work.	If you use different read/write community strings between the switch and the NAM, the nGenius Server will display an error message. The read/write community strings must match.
CSCdx19043 (3)	You cannot view total or in/out information from the short-term/long-term usage category.	This is a known limitation.
CSCdx30822 (3)	The New Folder button in Server>File>Table Export has no functionality.	This is a known issue.
CSCdx30877 (3)	Scroll bar in the Packet Analyzer>Decode window does not work.	This works as designed. You can use the arrow buttons to scroll through the window.
CSCdx30881 (3)	RTM initial window displays a "Server not found" error.	This occurs when you launch RTM with Internet Explorer. This message can safely be ignored.
CSCdx36951 (3)	After upgrading to RTM 1.4, RTM 1.3 Packet Analyzer must be removed using the Add/Remove Programs window.	This is a known limitation.
CSCdx40502 (3)	An error message is displayed when adding a switch with two NetFlow enabled NAMs.	RTM does not support two NetFlow enabled NAMs in the same switch. RTM can only use one NAM as a NetFlow source.
CSCdx40518 (3)	RTM does now allow full device table export through the GUI.	You can export the device table in xSV or HTML formal, however the file does not contain any community strings. To export the full device table: Navigate to the $RTMHOME/rtm/bin folder. Run nGeniusSQL.sh. This creates a devicelist.txt file.
CSCdw13264 (3)	Cannot log into nGenius due to filesystem permissions.	If the filesystem permissions for the RTM install directory are not set correctly, RTM will install successfully but you will not be able to log into the RTM server. To work around this problem, the filesystem permissions must be set to 755 (rwxr-xr-x). If this is a mounted partition, make sure the permission is set to 755 before mounting.
CSCdt69162 (3)	Traffic Monitor and Packet Analyzer do not show all VLANs on a switch.	VLANs that do not have at least one access switchport configured will not show up as managed elements in Traffic Monitor or Packet Analyzer. To work around this problem, either place at least one access switchport on the VLAN you want to monitor, or configure a span session for the VLAN.
CSCdw24020 (3)	RTM 1.3 installation will not work if IP address is provided.	If the /etc/hosts directory does not have a hostname in fully qualified domain name (FQDN) format, it will ask for an IP address. An IP address will cause the installation to fail. To work around this problem, add a FQDN hostname in /etc/hosts. If prompted for an IP address during the install, enter the hostname instead.
CSCdv11230 (3)	nGenius does not support multiple NICs on the same server.	To work around this problem, do the following prior to installing RTM: On UNIX platforms, edit the hosts file so that a qualified IPA is at the top of the list. This binds RTM to the first IPA on the server. On Windows NT and 2000 platforms, RTM will bind to the first LAN card shown in the network control applet.
CSCdx07013 (3)	RTM will not install on Win servers with Active Directory.	If you are using Active Directory, make sure the RTM database password meets the password requirements of the domain policy of Active Directory. For example, if the domain policy requires that the password must be eight characters in length, then the RTM database password must also be eight characters in length.
CSCdw84455 (3)	Traffic Monitor does not show application layer traffic for Catalyst 5000 NAMs.	This is caused by the Catalyst 5000 NAM bug CSCdx49381. After running for a few days, the control entries for protocolDir will disappear. To work around this problem, reboot the NAM and relearn the Catalyst 5000 switch from the nGenius server.
CSCdv73033 (3)	RTM 1.3 templates create incorrect RMON event and alarm indexes for Catalyst 2900XL switches.	To work around this problem, you must log into the switch and manually change the rmon alarm values.
CSCdx05808 (3)	nGenius only writes to the running configuration of Catalyst 3500XL switches.	If the switch is rebooted, all configurations made by nGenius will be lost.
CSCdw29439 (3)	RTM database import from TrafficDirector can take numerous hours.	The import status log might only show the import has started but does not show when it is completed.
CSCdu67612 (3)	RTM limits the characters that can be used for the database password.	A number cannot be used as the first character of the database password. The password must consist of alphanumerics only. To work around this issue, you can edit the createUser.sql file and place single quotes (') around the password. This will allow you to use other characters for the password.
CSCdw31885 (3)	RTM does not work across an NAT firewall.	The workaround is in Appendix B of the NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide.
CSCdw23394 (3)	RTM Link Usage, Short Term Usage, and Long Term Usage may not match templates.	The Long Term and Short Term usage does not work with Multilayer Switching Feature Card (MSFC) interfaces. This is a known limitation.
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.
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 and follow the instructions in the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.
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.
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.
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.
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
CSCdw60516 (3)	After upgrading from RTM 1.2 to 1.3, you cannot log into the nGenius Server.	None.
CSCdv52775 (3)	RTM does not have SNMP and other protocols in pre-capture filters.	None.
CSCdv52018 (3)	There is no way to monitor and collect data on all VLANs at one time.	None.
CSCdt18389 (3)	Unable to add a Catalyst 6000 NAM to nGenius.	None.
CSCdx07033 (3)	RTM 1.3 Apache 1.3.6 web server is vulnerable to denial of service attacks.	None.
CSCdw50592 (3)	Reset counters button is not available for NAM devices.	None.
CSCdx22888 (3)	RTM does not display traffic in a table format.	None.
CSCdu79679 (3)	RTM does not learn uplink ports on Catalyst 5000 switches with Supervisor 1.	None.
CSCdt51117 (3)	Packets are counted twice when a VLAN is roved to a NAM or SwitchProbe device.	None.
CSCdv17614 (3)	Server Message log filter does not recognize Japanese date.	None.
CSCdv35177 (3)	(UNIX systems only.) RTM installation fails if there is not enough space in /tmp.	`None.`
CSCdp82231 (3)	Cannot add two Catalyst 6000 NAMs in the same switch if the switch uses RTM.	None.
CSCdv28150 (3)	Traffic Monitor does not save Scene/Show customization.	None.
CSCdv24838 (3)	nGenius Packet Analyzer does not decode RTP protocols.	None.
CSCdv23530 (3)	nGenius Alarm Viewer does not show DLCI or PVC info for DLCI trap.	None.
CSCdv24821 (3)	RTM cannot recover a user-defined configuration.	None.
CSCdv84629 (2)	RTM 1.2 and 1.3 do not support Catalyst OS 5.5.9, 5.5.10, 5.5.1.	None.
CSCdv81613 (2)	RTM 1.3 does not show all connected Catalyst 4000 ports.	None.
CSCdv47252 (2)	RTM does not support Catalyst switches running Catalyst OS 6.3.	None.
CSCdv85877 (2)	Verisign certificate had expired.	None.
CSCdw09239 (2)	The Link Usage option under Data Link Layer in Traffic Monitor only shows data for two days.	None.
CSCdv86976 (2)	RTM 1.2 and 1.3 Java security files are missing.	None.
CSCdv39896 (2)	RTM 1.2 only learns 257 out of 440 DCLIs on SwitchProbe devices running 5.1.	None.
CSCdw52531 (2)	Traffic Monitor reports the wrong ATM PVC speeds.	None.
CSCdw05458 (2)	Error message displays in nGenius Message Log Window.	None.
CSCdw30423 (2)	nGenius does not allow a null password for default users.	None.
CSCdw43454 (2)	nGenius does not show port names for the Catalyst 2948G switch.	None.
CSCdw43649 (2)	Error message is displayed when adding a 2948G switch to nGenius.	None.
CSCdv22909 (3)	Save As feature does not work for Sniffer Pro 4.5.	None.
CSCdw10876 (3)	RTM 1.3 Traffic Monitor displays wrong byte count for groups of ports.	None.
CSCdw03222 (3)	Restarting nGenius causes a Java null pointer exception error.	None.
CSCdt88076 (2)	Importing devices from CiscoWorks 2000 to RTM fails intermittently.	None.

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.

This document is to be used in conjunction with the documents listed in the "Documentation Roadmap" section.

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

CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study 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, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, 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. (0203R)

Table of Contents

Enabling DSMON on a Catalyst 6000 and 6500 Series NAM

Configuring the Cisco Catalyst 6000 and 6500Series NAM

Enabling DSMON on a Catalyst 6000 and 6500
Series NAM

Configuring the Cisco Catalyst 6000 and 6500
Series NAM