netscout ngenius real-time monitor™ 1.4 release...

NetScout® Systems, Inc.Westford, MA 01886Telephone: 978.614.4000Fax: 978.614.4004

Web: http://www.netscout.com

NetScout nGenius Real-Time

Monitor™ 1.4 Release Notes

78-14180-01

Contents

iii

Use of this product is subject to the Terms and Conditions of the NetScout Systems, Inc. Software License Agreement, which accompanies the product at the time of shipment.

Notice of Restricted Rights:

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR §52.227-19 and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS §252.227-7013. The information in this manual is subject to change without notice.

NetScout� is a registered trademark and the NetScout logo, “Because the Network is the Business”, NetScout Manager Plus, WebCast, and the nGenius family of products are trademarks of NetScout Systems, Inc.

UNIX� is a registered trademark in the United States and other countries licensed exclusively by X/Open Company Limited. Microsoft�, Microsoft� Windows NT� Server, Microsoft� Windows�95, Microsoft� SQL Server, and Microsoft� Internet Explorer are registered trademarks and trademarks of Microsoft� Corporation. Sun is a trademark of Sun Microsystems, Inc. SPARCstation is a trademark of SPARC International, Inc. Solaris� is a registered trademark of Sun Microsystems, Inc. Netscape� is a registered trademark of Netscape Communications Corporation. Intel�, is a registered trademark of Intel Corporation. HP, HP-UX�, HP Openview�, are trademarks and registered trademarks of Hewlett Packard Company. IBM NetView� is a registered trademark of International Business Machines Corporation. Fast EtherChannel� is a registered trademark of Cisco Systems, Inc. in the U.S. and certain other countries. All other brand names, company identifiers, trademarks, service trademarks, registered trademarks and registered service marks mentioned in this document or NetScout’s license agreement are properties of their respective owners, and protected as such against unlawful use or distribution.

NetScout nGenius Real-Time Monitor™ 1.4 Release Notes78-14180-01Copyright 2002 NetScout Systems, Inc. Printed in the USA.All rights reserved.

v

ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Java Plug-in Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Recommended Limits for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Setting the NSM-in-Use Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Solaris Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Using nGenius Real-Time Monitor with Third-Party Products . . . . . . . . . . . . . . 3

Avoiding Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Using Port 8080 for Client HTTP Connections . . . . . . . . . . . . . . . . . . . . . . . 4

Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Summary of New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

nGenius Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Packet Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Voice Over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Documentation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Cisco Website Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

vi

Corrected Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Packet Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12nGenius Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Known Issues and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Packet Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16nGenius Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Upgrading Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Synchronizing Passwords After Reinitializing Database . . . . . . . . . . . . . . . . . 30Server Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Accessing the nGenius Server Across a Firewall . . . . . . . . . . . . . . . . . . . . . . 32

Forcing HTTP Tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Special Considerations When Using NAT . . . . . . . . . . . . . . . . . . . . . . . . . 32Special Considerations When Using VPN . . . . . . . . . . . . . . . . . . . . . . . . . 34

Viewing VLAN Data Link Layer Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Relative Time Property for Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 35Displaying Total Usage Versus In and Out Usage . . . . . . . . . . . . . . . . . . . . . 35Roving with NAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Using the Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Understanding nGeniusCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Using dvTools With nGeniusCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Enabling DSMON on the Cisco Catalyst6000 NAM . . . . . . . . . . . . . . . . . . . . . 41

-1

nGenius Real-Time Monitor v1.4Release Notes

IntroductionThis document describes the new functionality and enhancements in nGenius Real-Time Monitor™ v1.4.

Before You Begin

Java Plug-in SupportThe nGenius Real-Time Monitor and CiscoWorks2000 applications support Java Plug-in version 1.3.1_00. Java Plug-in version 1.4.0 is not supported.

CiscoWorks2000 does not support Java Plug-in versions 1.3.1_01 and 1.3.1_02.

Note: The nGenius products are designed and tested on dedicated servers. Third-partynetwork management software and database agents installed on the same server maycompromise the behavior and overall performance of the nGenius products. Therefore,we recommend that you provide a dedicated server for this product.

Note: If the appropriate plug-in is not detected on your client system the firsttime you launch nGenius Real-Time Monitor, the launch program connectsyou to the Sun Microsystems website. To obtain the correct Java Plug-inversion, close the Sun website and visit the Cisco Systems website at:http://www.cisco.com/pcgi-bin/tablebuild.pl/java

-2 Before You Begin

Recommended Limits for MonitoringFor optimal performance, the following limits are recommended:

• 50 physical probe interfaces

• 10,000 active switch ports

Setting the NSM-in-Use Flag

When installed on your network, nGenius Real-Time Monitor assumes control of configuration settings, whether TrafficDirector is installed on this machine or another one.

To maintain TrafficDirector control of configuration settings, you must add the following line to the serverprivate.properties file on the machine that contains the Real-Time Monitor Server:

stealth.nsminuse=true

Firmware RequirementsThe Voice over Internet Protocol (VoIP) component of nGenius Real-Time Monitor 1.4 requires NetScout Probe (NSP) v5.2 firmware. Voice over IP is not supported in NSP v4.7, 5.0, or 5.1.

Monitoring DSMON using nGenius Real-Time Monitor 1.4 requires NSP v5.2 firmware and 2.1(x) of NAM firmware.

NSP v5.2 is available from NetScout Systems. Visit www.netscout.com or call 800-357-7666 for the NetScout sales office nearest your location.

Solaris PatchesThe list of Solaris patches provided in the nGenius Real-Time Monitor Installation Guide is current at the time the guide is printed. However, it is recommended that you visit the Sun Microsystems web site (www.sun.com) to see if newer patches are available.

Caution: Do not install nGenius Real-Time Monitor on a machine that isalready running Cisco TrafficDirector.

-3

Using nGenius Real-Time Monitor with Third-Party Products

Review the information in this section to avoid port conflicts when using nGenius Real-Time Monitor.

Avoiding Port Conflicts

• If nGenius Real-Time Monitor is installed on a system where no other applications are using RMI port 1099, port 1099 will be used by Real-Time Monitor.

• If another application attempts to bind to port 1099 while nGenius Real-Time Monitor is using this port, that application fails to bind to port 1099 and the nGenius Server continues functioning properly.

• If the nGenius Server is not running when another application binds to port 1099, that application continues functioning and the nGenius Server cannot start.

In addition, you should also avoid conflicts with the following nGenius Real-Time Monitor default ports:

1961-1978

2639

395

162

If these port assignments conflict with other applications, change the port assignments manually by editing the following files:

/rtm/html/client.properties

/rtm/bin/admin/serverpublic.properties

For example, you can change the RMIRegistryPort=1099 to 1100 (or the next available TCP port).

Note: Real-Time Monitor must be installed on a dedicated system with astatic IP address.

-4 Before You Begin

Using Port 8080 for Client HTTP Connections

By default, nGenius Real-Time Monitor uses port 8080 for client HTTP connections. Make sure no third-party management applications conflict with this port.

• If another management application uses port 8080, conflicts will arise and the other application will not function properly.

• When changing the port number after the RTM installation, use a port lower than 1024. (During installation, you can use any port number.)

To change the port number after installation:

Windows platforms

1 Stop nGenius Real-Time Monitor.

2 Modify the variables listed in Table 1 to the new port number.

3 Save and close each file in turn.

4 Restart nGenius Real-Time Monitor.

Note:• Open the files in a text editor, such as Wordpad or vi.• Create a backup copy of each file before you edit it.

Table 1 Changing the Port Number on Windows Platforms

Directory File Variable

\rtm\bin directory

webstart.bat

serverprivate.properties

NSAPACHEPORT

webserverport

\apache\conf

httpd.conf Port

Real-Time Monitor install directory>\tomcat\conf

prof-server.xml Each occurrence of

-5

UNIX platforms

1 Stop nGenius Real-Time Monitor.

2 Modify the variables listed in Table 2 to the new port number.

3 Save and close each file in turn.

4 Restart nGenius Real-Time Monitor.

After you change the port number, specify the new number in the URL when you launch nGenius Real-Time Monitor.

Table 2 Changing the Port Number on UNIX Platforms

Directory File Variable

/rtm/bin

start1

serverprivate.properties

NSAPACHEPORT

webserverport

/rtm/bin

webstart1 NSAPACHEPORT

/apache/conf

httpd.conf Port

/tomcat/conf

prof-server.xml Each occurrence of

-6 Compatibilities

CompatibilitiesThe nGenius Real-Time Monitor software are compatible with the following products (must be installed in different machines):

TrafficDirector

CiscoWorks2000

HP OpenView

If you install both nGenius Real-Time Monitor and TrafficDirector on your network, you must ensure that only one product is in charge of device configuration and receipt of trap information.

Summary of New FeaturesThe following new features have been implemented in Real-Time Monitor v1.4.

nGenius ServerSupport for Differentiated Services — DSMON allows different classes of traffic to be accorded prioritized Quality of Service (QoS) treatment while flowing through the network. DSMON data is displayed in Traffic Monitor. By default the DSMON MIB is disabled. To collect DSMON data from your network, you must enable this setting on the SwitchProbe device or NAM. For more information on enabling DSMON on a NAM, see the Cisco Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4.

Asynchronous Device Configuration — This feature provides the ability to perform concurrent device processing; for example, adding, deleting, or configuring devices. When you initiate a task, a Task Progress Report provides asynchronous device status feedback such as warnings and errors.

Server Load Detection — nGenius Real-Time Monitor proactively monitors the nGenius Server to prevent poor performance or abnormal shutdowns. If disk space, memory usage, or server overload thresholds are exceeded, an alarm is triggered and the nGenius Server executes a script to notify you by e-mail.

Bulk Device Add — Allows you to add multiple devices via a comma separated values (.csv) file.

-7

Traffic MonitorSegment Detail View — Provides refreshable cumulative statistics on the probe interface and switch port, such as short-term history and long-term history. Data is shown as raw counters (not deltas), and includes, among others, the following statistics:

• Utilization

• Bytes and Octets

• Packets

• Broadcasts, Multicasts, and Unicasts

• Cyclic Redundancy Codes (CRCs)

• Jabbers

CSV/TSV/Pipe/HTML Support for Table Views — You can now export all tables in Traffic Monitor to comma separated (CSV), tab separated (TSV), pipe (|), and HTML formats. You can save the files on the client machine, or import them into other applications (for example, spreadsheet applications).

Vital Signs in Data Link Layer View — Displays Utilization, Broadcast, Multicast, and Error percentages side by side. For Ethernet, WAN and FDDI, the Vital Signs view also displays Collisions.

Host/Conversation/Protocol Search — Allows you to search for a host, conversation, or protocol across the enterprise. Displays a table of raw bytes/packets and delta bytes/packets.

Favorite Views — Configure and display favorite views in the same manner as launching default views.

Packet AnalyzerAuto Data Capture Based on Events and Time — You can now configure automatic data capture based on either a rising or falling threshold, or for a specific date and time (time trigger).

Filter Editor — In addition to the many filters nGenius Real-Time Monitor provides by default, you can create your own custom filters using the Filter Editor. You can add, edit, delete, and print filters.

Post-Capture Filter — Packet Analyzer provides new post capture filters. For example, you can specify a Boolean expression of a data pattern on which to filter and save the sub-trace files.

-8 Summary of New Features

ReportingStacked Bar Utilization Charts Segmented by Application — Stacked bar charts now display utilization. Bars are segmented by the application traffic that makes up the utilization total.

Top Hosts Charts — The drill downs from the probe reports display top hosts, in addition to the other charts currently available.

Voice Over IPVoice over IP is available for systems that have installed legacy SwitchProbe devices running NSP v5.2.

Enterprise view — Shows statistics on all VoIP-capable probes, such as the number of active, successful, and incomplete calls; IP, RTP, RTCP, and signaling protocol utilization percentage; and status.

This view can help you understand the relationship between total traffic, voice media traffic (RTP), and aggregated voice signalling traffic (H323, SCCP, MGCP).

Phone Users view — Display statistics relating to activity, phone numbers, usernames, IP addresses, talk time, average call duration, valid calls, incomplete calls, RTP data, and RTCP data.

Quality Details view — Statistics relating to call quality, including activity; sender and receiver phones; sender packet loss, jitter, and DSCP; and receiver packet loss, jitter, and DSCP.

Client-Based Alarms — VoIP now allows you to set thresholds for Enterprise and Conversation Level variables. When a threshold is exceeded, the client highlights the session and the variable that exceeded the threshold.

Data Captures — VoIP has been integrated to support packet capture. The integration allows users to automatically create filters for phone users or even a specific session by selecting a phone user and launching data capture from VoIP.

Note: To collect VoIP data, you must first enable the VoIP MIB on a probethat has the NSP 5.2 firmware installed and that contains a minimum of 32MB of memory.

-9

Related DocumentationThe following documentation is provided to support nGenius Real-Time Monitor software and related hardware.

Refer to the appropriate manual or the online Help for detailed information on specific features and functions.

User documentation is also available in PDF format on the Cisco Systems website at www.cisco.com.

Document Describes

NetScout nGenius Real-Time Monitor 1.4 Installation Guide

Installing nGenius Real-Time Monitor.

NetScout nGenius Real-Time Monitor 1.4 Getting Started Guide

How to quickly initiate data monitoring, collection, and viewing using the nGenius Server, nGenius Traffic Monitor, nGenius Packet Analyzer, and Voice over IP Monitor.

Online Help Configuring and using nGenius Real-Time Monitor software, including advanced features.

Network Analysis Module documentation

Installing, configuring, and using NAMs. Refer to the Cisco Systems website at www.cisco.com for the most current documentation

Note: You must have Adobe Acrobat on your system to view PDF files.

-10 Documentation Issues

Documentation IssuesNote the following documentation issues in nGenius Real-Time Monitor v1.4:

NetScout nGenius Real-Time Monitor Getting Started Guide — Page 2-1 of the text specifies that, as a prerequisite to launching nGenius Real-Time Monitor, you must install NetScout probes as appropriate throughout your network. Installing probes is not a prerequisite to launching nGenius Real-Time Monitor. You can also use other monitoring devices, such as mini-RMON enabled switches or NAMs.

Online Help — When viewing the online Help using Netscape 4.7 versions, white space displays above tables. As a result, it may appear that the topic is empty. Scroll down to view the information in the Help topic.

Cisco Website SupportCisco 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) website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website.

-11

Corrected ProblemsThe tables in this section list the bugs resolved since the last release of nGenius Real-Time Monitor (nGenius Real-Time Monitor v1.3).

Packet AnalyzerTable 3 lists the corrected problems for Packet Analyzer.

Table 3 Corrected Problems for Packet Analyzer

Defect Problem Solution

4319 Absolute time is incorrect in data capture sniffer format

The time-stamp bits were not being written correctly to the trace file. Consequently, the reading of the time stamps during the decode was incorrect.

4619 Up/down scrolling in the Decoder Summary window is very sluggish

Use the arrows to scroll through the Decoder Summary window. The scroll bar is disabled by design.

5194 After re-learning Cisco Catalyst5000 NAM switch and Cisco Catalyst6000 NAM switch, accessing spanned VLAN or FEC generates exceptions

Modify navigation tree code so that a media type check no longer returns a value of null for FECs and VLAN.

5352 Packet Analyzer does not decode RTP packets when the version of RTP is zero

RTP decode logic has been modified to check for version zero and proceed with decoding.

5776 Unable to perform Sniffer format captures on VCs

The user can select the capture to be saved in Sniffer format on a PVC.

5788 It takes a long time to upload captured data across a slow network

Send multiple requests to upload the data from the probe. Upload time is significantly reduced.

-12 Corrected Problems

Traffic MonitorTable 4 lists the corrected problems for Traffic Monitor.

5790 Cannot create a filter of multiple source and destination addresses in pre-capture and post-capture modes

Can now create a filter of up to four source/destination pairs.

5793 Cannot do a string search in Decode file

Searching on strings is now supported.

Table 4 Corrected Problems for Traffic Monitor


5199 The Alarm GUI does not display the Detail section for the DLCI Down Time Alarm

Trap information is now included in the Alarm GUI.

5248 nGenius Real-Time Monitor sets trap port to 395 for all switch and probe devices

Modify code to set RMON trap destination port to 162 for all switch and probe devices.

5197 Changing DLCI speeds in the Server Administration client fails to reflect in ifSpeed of DLCI

The code is modified to sum the DTE and DCE speeds and update the ifSpeed of the DLCI in the database and on the Traffic Monitor monitored element tree. The correct ifSpeed displays on mouse-over, and utilization calculations are correct.

5569 Historical views do not display correct date range

A fixed number of container vectors were used regardless of the number of data sets to be plotted under certain conditions. This is now corrected.

Table 3 Corrected Problems for Packet Analyzer (Continued)


-13

nGenius ServerTable 5 lists the corrected problems for nGenius Server.

Table 5 Corrected Problems for nGenius Server


4510 Launching a second application by URL (via CiscoWorks2000) causes nGenius Real-Time Monitor to log out and request a new login

Modify the servlet code to track client logon sessions and maintain a persistent login session even when launching another application via URL. Communication between the servlet and the client is maintained via RMI.

5411 Users with the System Administrator role cannot change a user password without using the old password

Added a Clear Password button to the User Accounts dialog box to allow the System Administrator to clear the password for any user. Once the old password is cleared, the System Administrator can click Modify to change any field, including setting a new password.

5513 The number of protocols viewed when performing Protocol Discovery decreases over time and protocols displayed in Protocol Discovery do not match either Global Settings or the PDIR on the probe

Force deletion of unknown protocols from the probe. If there is only read access to the device and there are duplicate protocols with the same name, they appear in protocol discovery with _1, _2, etc. Fixed problems where device cache was getting out of sync.

5601 The Alarm Viewer only displays alarms in the database from the most recent 7 days

If the user allows active alarms to exist for more than 7 days, the alarms cannot be deleted from the database

Modify the stored procedure, which performs aging on the alarm database table so that it does not filter on inactive alarms. To improve efficiency, the user may want to modify the serverpublic.properties file to change Aging.traps from 31 to 7.

-14 Corrected Problems

5707 The server learns unknown FEC interfaces on switches with CatOS 6.3(2)

When a Cisco switch with CatOS 6.3(2) is learned, multiple FEC interfaces are found, although the switch is not configured with FECs. This results from a change in the CatOS firmware, where the groupIndex now contains its own ifIndex instead of 0.

5898 The Verisign certificate has expired, and clients encounter an exception when they log in

All jars have been resigned with an updated Verisign certificate.

6254 Attempting to add Cisco 6506 switch with NAM results in null pointer exception containing the line "at com.netscout.frameworks.servicex.me.MERepository.get (MERepository.java:225)"

No orphaned interfaces remain when you delete or add the Cisco Catalyst6000 series switches with NAMs.

6543 Traffic Monitor history menu selections may not match switch port template settings

The client contains an out-of-date cache of the history capabilities and sends them to the server when the template association changes. Changed server to refetch the old capabilities from a more accurate server-side cache.

Table 5 Corrected Problems for nGenius Server (Continued)


-15

Known Issues and WorkaroundsThe tables in this section list the known problems and workarounds for nGenius Real-Time Monitor v1.4. For additional information, visit the NetScout technical support knowledge base which contains related documents, tips, FAQs, and suggested workarounds.

Packet AnalyzerTable 6 lists known issues and workarounds for Packet Analyzer.

Table 6 Known Issues and Workarounds for Packet Analyzer

Defect Problem Workaround

6989 If you attempt to overwrite a data capture that is already in process (for example, if you configured an alarm-based capture for an interface, and then launch a manual capture on the same interface), a warning displays.

However, relearning or activating/deactivating a device results in no warning being given.

This is a known limitation.

7681 Protocol filter is not available for Cisco Catalyst 5000 NAM in Data Capture window.

This is a known Cisco device limitation. The Cisco Catalyst5000 NAM supports Custom Filters (based on Addresses), but does not support Protocol Filter.

7773 Fatal error messages are logged to /rtm/log/dengine####.out when decoding data capture files.

The messages are harmless and can be ignored.

-16 Known Issues and Workarounds

Traffic MonitorTable 7 lists known issues and workarounds for Traffic Monitor.

8137 Packet Analyzer does not capture data on a VoFR interface.

By default, Packet Analyzer captures IP-based traffic.

To capture traffic based on the MAC address, in the Addresses field of the Data Capture dialog box, select MAC.

Not available

In the Decode window of Packet Analyzer, the Summary window (top window) scroll bar is not operable.

The scroll bar is disabled by design. Use the arrows to scroll through the window.

Table 7 Known Issues and Workarounds for Traffic Monitor


6772 Short-Term and Long-Term History on the following switches display incorrect utilization on ports configured to Full-Duplex:

• Cisco Catalyst4000 v5.4(1)

• Cisco Catalyst6000 v6.3(3)

Ports configured to Half-Duplex display correct statistics.

This is a known Cisco device problem.

6985 The full-duplex trunks on the Cisco Catalyst6000 NAM switch display as half-duplex interfaces. The In and Out radio buttons do not display.

This is a known issue.

7489 When changing from a finite number of protocols to zero protocols in Traffic Monitor, it takes a long time to see the update.

If you make changes, relaunch protocol discovery.

Table 6 Known Issues and Workarounds for Packet Analyzer (Continued)


-17

7560 &7559

There are known issues with certain dialogs on Solaris clients:

• If you click outside a modal dialog box, it disappears behind the main MDI.

• Clicking outside of the Alarm Viewer dialog box causes it to disappear.

• If a dialog box disappears behind the main MDI, drag the MDI out of the way using the title bar.

• If the Alarm Viewer dialog disappears, bring up Preferences. The Alarm Viewer should also appear.

• Alternatively, close Traffic Monitor and relaunch.

7698 On Paradyne CSU/DSU, All NL Hosts does not display when launched from a non-bar section of the Network Layer view.

To launch All NL Hosts, right-click directly on a bar in the chart.

Table 7 Known Issues and Workarounds for Traffic Monitor (Continued)



8375 After upgrading the database from nGenius Real-Time Monitor v1.2 or 1.3, drill downs for Top N NL/AL Hosts and All NL/AL Hosts are inactive.

After upgrading the database, manually relearn the device.

If manually relearning the device is not practical, modify files according the following procedure:

1 Upgrade the database and start the server.

2 Execute the following command from the rtm/bin directory:

./nGeniusSQL.sh(.bat)

./sqlscripts/AddNLALCapabilityCode.sql -H

AddNLALCapabilityCode.sql is a query which obtains the MEL_IDs of probes and probe interfaces from the capability_assoc table and formats the OUTPUT.txt file.

3 Execute the following command:

./nGeniusSQL.sh(.bat)

This command ensures that the capability_assoc table inserts the NL&ALHost capability into the MEL_IDs.

4 Stop and restart the server.



-19

nGenius ServerTable 8 lists known issues and workarounds for nGenius Server.

Not available

Application Layer graphs do not display all traffic.

If traffic does not fall into one of the predefined groups, no graph will display.

For a table view of all Application Layer traffic, right-click the graph and select All Traffic.

Not available

The numbers in Traffic Monitor default Network Layer and Application Layer utilization views are hard to read.

Resize the window.

Table 8 Known Issues and Workarounds for nGenius Server


0712 Get exception and error messages when adding Cisco Catalyst4000 or Cisco Catalyst1900 switches to the Server with limited memory and resources.

Click Enable learn only when adding the switch.

4089 In HPUX, error messages display when executing ./dbinit.sh from the /bin directory.

Delete stealth.db, then execute dbinit.sh.

4689 Switch VLAN shows incorrect port membership.

Relearn switch.

4704 The speed of an external rove probe does not add up to the sum of all roved switch ports.

There is no known solution available at this time.




5057 If you have an RSM module on the switch, it is learned and displayed in the nGenius Server, but does not display in Traffic Monitor.

An RSM module displays in nGenius Server switch details, but not in Traffic Monitor, because the module does not have the capability to display statistics.

5099 Stopping and starting the nGenius Server does not always stop or start all processes.

After stopping the nGenius Server, wait briefly to allow the stop or start services to fully complete.

5135 On the Cisco Catalyst5000 NAM switch, you cannot span a giga-bit switch port.

This is a known Cisco switch limitation.

6310 The following login/splash screen issues can occur:

• Invalid login errors display when the server is restarted.

• If you log out from the splash screen and close it, and then refresh the original browser window, the splash screen redisplays. When you log in again, there is no connection to the server. No devices display in the Device Configuration window, and you cannot launch Traffic Monitor or Packet Analyzer.

• If you unintentionally close the splash screen, or if you click another html file, the other file takes over the session and you lose your session with the nGenius Server.

If you log out of nGenius Real-Time Monitor and intend to log back in, do not close the splash screen.

If you unintentionally close the splash screen after you log out, you must close all browser windows completely and then relaunch to access the application.

Table 8 Known Issues and Workarounds for nGenius Server (Continued)


-21

6577 If the appropriate plug-in is not detected on your client system the first time you launch nGenius Real-Time Monitor, the launch program connects you to the Sun Microsystems website.

To obtain the correct Java Plug-in version, close the Sun website and visit the Cisco Systems website at:

http://www.cisco.com/pcgi-bin/tablebuild.pl/java

6732 Online help for dvTool commands is accessed from the CLI.

To access the online Help for dvTool commands, at the command line enter:

:\rtm\bin\nGeniusCLI dvTool -help

The parameters for dvtool Help will be displayed.

6750 On Windows platforms, the CTL3D32.dll file is required to successfully start the nGenius server. If the file is not on your system, you receive the following error message: "dbisql.exe unable to locate CTL3D32.dll".

Obtain the .dll file from another source, and copy it to your \Winnt\system32 folder.

7214 If you access nGenius Real-Time Monitor 1.4 from CiscoWorks2000, after an extended idle period, the CiscoWorks2000 shuts down the nGenius Real-Time Monitor client with all its running applications. Once nGenius Real-Time Monitor is shut down or if you log out of CiscoWorks2000, you cannot log in to any nGenius Real-Time Monitor applications.

Close all browser instances before attempting to log in again.




7340 When upgrading nGenius Real-Time Monitor v1.3 to nGenius Real-Time Monitor v1.4, installation to the original home directory results in an upgrade path that is too long.

If you want to install nGenius Real-Time Monitor v1.4 in the same directory as nGenius Real-Time Monitor v1.3 rather than in the default directory, do so at the root level. Installing to a branch can result in pathnames that are too long.

Not Available

An error message may display in the Task Progress Report when adding a device that has interface 1 configured as manage only.

If an error message displays when adding a manage-only interface, it can be safely ignored. (NSP v5.2 recognizes when if1 is manage only and does not display the error.)

7511 Unable to span Cisco Catalyst3550XL.

If adding the switch fails, you can delete the switch and add it again using the Generic switch option. However, when you add a switch using the Generic option, spanning is not supported.

7580 By default, the DSMON MIB is disabled.

To collect DSMON data from your network, you must enable this setting on the probe or switch and then reboot the nGenius Server.

Refer to the following topics in the online Help to enable DSMON collection:

Enabling DSMON on the Cisco Catalyst6000 NAM

Enabling DSMON on the Probe

7587 All RMON and TopN RMON Hosts and Conversations display for If49 Aggregate Gigachannel interface even though no data is available.

This is a harmless error. The menu items are available will do not contain data.



-23

7703 nGeniusCLI report and dvTools do not work when the device name contains a colon.

Use of the -ms tag for either report or dvTool requires the following format:

DeviceName:ifNumber:virtualifName or DeviceIP:ifNumber:virtualifName

If DeviceName contains a colon (:), replace DeviceName with the IP address. For example, replace the the command:

./nGeniusCLI.sh dvTool -ms6010:LAB:3 -dv admin list

with

./nGeniusCLI.sh dvTool -ms10.10.10.10:30 -dv admin list

7711 & 7621

If RMON & RMON2 traps are installed on NAM Version 2.1(1a) as well as 2.1(2) on Cisco Catalyst6000 switch (10.20.150.6) and (10.20.150.5), the Trap Destination MIB, Alarm MIB, and Event Table MIB indicate the events have been generated. However, the Log MIB under Event does not show the alarm being sent to nGenius Server.

This issue is resolved with the latest NAM maintenance image. You can download the latest maintenance image from the Cisco Systems website at:

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

7721 On a minimally-configured system, the nGeniusCLI script can take a long time to finish.

If you encounter this problem:

• Meet system requirements

• Re-execute the script, or wait until other server processes complete




7788 Unable to span the same interface to 2 different analyzer ports.

In the spanning dialog, you can have two or more analyzer ports. If you attempt to span the same interface (port, VLAN, FEC) to more than one analyzer port, the server displays an error: "Source is already spanned to a different analyzer port., Details: default, Severity: 3, Code: 16134"

This is a known issue, and will be fixed in a future release.

7794 & 7795

When adding certain switches with IOS firmware, Switch Detail shows no ports or interfaces.

If adding the switch fails when using IOS firmware, delete them and add them again as Generic.

Not available

Adding certain switches (3524XL, 2924XL, 2950, 490G-L3, 2948G-L3 (IOS firmware), 3200 (CatOS firmware) can result in Protocol write errors or No such object errors.

The trap destination address has not been set by the client software. You can:

• Manually set the trap destination address in the switch command line interface (CLI).

or

• Click Enable learn only when you add the switch. Learn only mode prevents nGenius Real-Time Monitor from attempting to configure statistics, history, traps, and trap destinations.



-25

7854 On Solaris platforms, the international language license agreement may display incorrectly by replacing certain text with question marks (?).

You can display the text properly by changing your operating environment to English.

You can eliminate the question marks by changing your operating environment to English.

If you prefer not to change the operating environment to English, and if the license agreement is unclear, you can resolve any questions you have by referring to the printed license agreement that is included in your software package.

To change the operating environment to English:

1 From the login screen, select Options > Language.

2 Select one of the following options:

C

en_US.ISO8859 -1 -- U.S.A.

7925 When using the nGeniusCLI on UNIX systems, if you try to log a csv output file to a location outside the nGenius Real-Time Monitor home directory, the log file may not display.

NetScout Systems recommends you place your output logs in the nGenius Real-Time Monitor home directory.

If you must place them outside the home directory, change the user for the new directory to nGenius after the directory is created. (nGenius must have write permission to the new directory.)

8082 On Windows platforms, the international language license agreement may display incorrect characters.

This is a known issue. If the license agreement is unclear, refer to the printed license agreement that is included in your software package.




8083 nGenius Real-Time Monitor cannot be launched where HP OpenView is running. The application must be launched remotely.

NetScout Systems does not support running HP OpenView on the Solaris or HP machine where HP OpenView software is installed. Access the HP OpenView server from a client machine.

8183 If you log in to the terminal console as root and run the dbreload.sh utilities, you cannot start the nGenius Server.

You must run dvreload.sh as a secure user. When you log in to the terminal console as root and run dbreload.sh, reload.sql, stealth.db, and stealth.log are owned by root instead of ngenius.

You must log in as ngenius.

8249 On Solaris platforms, nGeniusImport.sh can hang after importing devices.

Press Ctrl+C to exit, then restart the nGenius Server.

8380 When adding a Cisco Catalyst6513, either manually as CAT6513 or using Automatic, you receive the error "Device type not recognized," and the switch is not added.

Add the switch as CAT6000. Do not use Automatic.

8383 In Global Settings, if you deselect or select App. Auto-Discovery and click OK, the change is not saved.

Make any other change in the Global Settings dialog box, in addition to changing the App. Auto-Discovery setting. For example, you can select and deselect any check box (so there is no net change), and click OK. The Task Progress Report displays, indicating the change is saved.

Not available

Unable to create data capture session in device. Receive "No Channels Available" error message.

Clear the data capture buffer by selecting Capture > Buffer, or by clicking the Clear buffer icon.



-27

Not available

A No such object error may display when installing RMON2 Global Settings to Cisco Catalyst5000 NAM.

The protocol directory control entry is missing in the switch, and cannot be recreated. The workaround is to reboot the switch.

Not available

When upgrading from nGenius Real-Time Monitor v1.3 to nGenius Real-Time Monitor v1.4 on Windows platforms, Packet Analyzer (v1.3) is not removed from Control Panel > Add/Remove Programs.

This is a known issue.

Not available

CiscoWorks2000 supports multi-homed servers but nGenius Real-Time Monitor does not support multiple NICs on the same server. This can result in an error during the installation.

If you have multiple NICs, the installation program may not detect the correct IP address.

If the installation program does not detect the hostname or IP address, or if the program displays localhost as the Host Name and 127.0.0.1 as the Host IP, you must exit the installation and edit the following file:

Windows platforms — \system32\drivers\hosts

UNIX platforms — /etc/hosts

Ensure that the correct Host Name and Host IP are at the top of the list, and restart the installation from the beginning.

Not available

Previously used secured user names should not be used with nGenius Real-Time Monitor v1.4.

Installing nGenius Real-Time Monitor automatically creates a secured user, with the default user name ngenius (group ngenius in UNIX). If the secured user ngenius already exists, it will be reused and assumed to be secure. Do not reuse any secured user name.




Not available

Resetting counters is not available on NAM.

Resetting counters on NAM is not supported in this release.

Not available

nGenius Real-Time Monitor does not support Terminal Services Manager.

Terminal Services Manager and nGenius Real-Time Monitor use a port in common. If a port conflict arises, refer to "Using nGenius Real-Time Monitor with Third-Party Products," earlier in this document.

Not available

SMON Monitor does not poll VLAN data from Cisco Catalyst6000 NAM.

This is a known Cisco issue on 2.1(x) NAM firmware.

Obtain the NAM 2.1(x) patch from Cisco Connection Online.

Not available

When using the NSM Convert utility, you may encounter the following error message:

error creating zipfile:java.util.zip.zipException:ZIP file must have atleast one entry

The database will not contain any entries.

Not available

Some nGenius Server > File dialog boxes have unusable icons. For example, in nGenius Server File, the Table Export icon is inoperable. The same issue is observed in Packet Analyzer > Decode > Export.

The File menu dialog boxes are provided by the Java Developer’s Kit (JDK). The New Folder, List, and Details icons for these dialog boxes are non-functional. This is a known JDK issue.



-29

Not available

Need a procedure to recover a user-defined configuration.

To recover a user-defined configuration (for example, if your database is corrupted):

1 Open a UNIX shell or DOS command window and navigate to the following directory:

/rtm/bin

2 Execute dbunload. Device configuration table information is copied to the following location:

/rtm/database/unloadFiles

3 Execute dbreload. This program creates a new database and imports the configuration data from unloadFiles.

For further information, refer to "Recovering Data from the Database" in the online Help.



-30 Special Considerations

Special Considerations

Upgrading Your DatabaseBefore upgrading from nGenius Real-Time Monitor v1.2 or 1.3, back up your database.

nGenius Real-Time Monitor v1.2 — Be sure you have sufficient disk space before you begin the upgrade. The size of the database increases by approximately 15 percent. It takes approximately one hour per GB to upgrade the database.

nGenius Real-Time Monitor v1.3 — Be sure you have sufficient disk space before you begin the upgrade. There will be a slight increase in the size of the database.

For complete instructions on upgrading your database, refer to the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.

Synchronizing Passwords After Reinitializing Database

If you change the database password, the new password is recorded in the db.properties file. When this occurs, the database password in the db.properties file does not match the old password in the dbinit file.

In nGenius Real-Time Monitor v1.3, you had to manually synchronize the passwords to reinitialize your database, then change your database password again after reinitializing.

In nGenius Real-Time Monitor v1.4, you do not need to manually synchronize the passwords. Database reinitialization automatically uses the old password found in the dbinit file.

Caution: Do not interrupt the upgrade process. Doing so may result indatabase corruption.

-31

Server ProcessesTable 9 lists the nGenius Real-Time Monitor processes.

Table 9 Server Processes

Windows Platforms UNIX Platforms

Apache.exe

Apache.exe

dbsrv7.exe

dengine.exe

dengine.exe

NGeniusNativeService

NGeniusService

NSnGeniusNative.exe

NSRmiregistry.exe

NSServer.exe

NSTomcat.exe

NSWatchdog.exe

dbsrv7

dengine

dengine

Several libhttpd processes (minimum of two)

NSServer

NSnGeniusNative

NSRmiregistry

NSTomcat

NSWatchdog

Note: The number of libhttpd processes started by the Apache Webserver is based on the number of clients currently accessing the Webserver.


Accessing the nGenius Server Across a Firewall To access the nGenius Real-Time Monitor Server from outside a firewall, you can use the well-known port HTTP 80. The Web server must be running on port 80, and the firewall should be configured to allow incoming connections on port 80 and outgoing connections on TCP port 1963. All nGenius Real-Time Monitor client requests to the server are tunneled into an HTTP request over port 80.

Forcing HTTP Tunnelling

If a client cannot log in to the nGenius Server after you have configured the ports, you can force the client to use HTTP tunneling by setting the following property in the /rtm/html/client.properties file:

applicationx.applicationmanager.forceHttpTunneling=true

Special Considerations When Using NAT

When using Network Address Translation (NAT) in a monitored environment, nGenius Real-Time Monitor clients that reside outside a firewall cannot connect to an nGenius Server installed and running within the firewall.

To allow clients on either side of a firewall to properly connect to the nGenius Server, you must modify the server client.properties and serverprivate.properties files as described in this section. In addition, you must configure the client by adding a Java Runtime parameter to the Java Plug-in Control Panel.

In the following example, 10.24.1.2 is the IP address of the system where nGenius Real-Time Monitor is installed inside the firewall. The hostname of this system is MyHostName. The translated IP address of the nGenius Server, viewed from outside the firewall, is 38.24.1.2.

Note: The default setting is false. Changing this property to true will affect theway all clients log in to the server.

Note:• Create a backup copy of each file before you edit it.• Open the files in a text editor, such as Wordpad or vi.

-33

Configuring the nGenius Server

1 Modify properties files as follows:

• In the /rtm/html/client.properties file, change the serveraddress to the hostname instead of the internal IP address.

For example, change serveraddress=10.24.1.2 to serveraddress=MyHostName.

• In the /rtm/bin/serverprivate.properties file:

– Change the serveraddress to the hostname.

For example, change serveraddress=10.24.1.2 to serveraddress=MyHostName.

– Change the java.rmi.server.hostname so that it uses the hostname instead of the internal IP Address.

For example, change java.rmi.server.hostname=10.24.1.2 to java.rmi.server.hostname=MyHostName.

2 Modify /rtm/html/WEB-INF/web.xml by adding the nGenius Server hostname between and .

java.rmi.server.hostnameMyHostName

Configuring the Client

To configure the client:

1 For all client systems, modify the host table to associate the translated server IP address, viewed from outside the firewall, with the server hostname.

For example:

Windows platforms — Add 38.24.1.2 MyHostName to the Winnt\System32\Drivers\etc\hosts file.

UNIX platforms — Add 38.24.1.2 MyHostName to the /etc/hosts file.

2 Add the Java Runtime parameter to the Java Plug-in Control Panel:

a From Start > Settings > Control Panel, double-click Java Plug-in.

b In the Java Runtime Parameters text field, enter: -Djava.rmi.server.hostname=


Special Considerations When Using VPN

Client users wanting to connect to an nGenius Server using a VPN connection, must add a Java Runtime parameter to their Java Plug-in Control Panel:

1 From Start > Settings > Control Panel, double-click Java Plug-in.

2 In the Java Runtime Parameters text field, enter: -Djava.rmi.server.hostname=

For example, for a Cisco VPN client, you can view the client IP address in the Cisco Systems VPN Client Connection Status dialog box.

Viewing VLAN Data Link Layer StatisticsThe nGenius Real-Time Monitor software derives data link layer statistics for VLANs from their member ports. Therefore, the displayed VLAN statistics pertain to only the selected switch. The statistics include only those packets passed within the switch and those passed in or out of the switch through the trunk. The statistics do not reflect the whole trunk.

For example, consider two switches each containing three user ports. Switch A has user ports C, D, E, and Switch B has user ports X, Y, Z. All six ports are members of VLAN 1.

In this case, when you select VLAN 1 under Switch A and launch the data link layer statistics, nGenius Real-Time Monitor aggregates the data link layer statistics in the following way:

Packets sent from C to D: counted 2 times

Packets sent from C to Z: counted once

Packets sent from X to Z: not counted

-35

Relative Time Property for Traffic MonitorYou can now set an option in the client.properties file to display data for a relative month (previous 31 days) or week (previous 7 days). The GUI menu displays Last Month and Last Week, and your selection provides the following data, depending on how you set the condition tag (default is true).

The data in Table 10 reflects a date of December 18.

The reason for adding the relative time property is that with current aging the only proper time to use an absolute time (false) is when a report is published or scheduled on the first of a month. In cases where a report is generated with an absolute time after the first of the month, you would not be able to get a complete month of data.

Displaying Total Usage Versus In and Out UsageOn full-duplex interfaces, all usage views in nGenius Real-Time Monitor v1.3 display Total, In, and Out. In nGenius Performance Manager v1.4, you can display the following usage values:

• Total, In, and Out

• In and Out only (default, condition=false)

To display Total, In, and Out usage values, set the option in the client.properties file to true:

trafficmonitor.showTotalValueForFullDuplex=true;

Table 10 Relative Time Conditions for Traffic Monitor

Set Condition Displays Data For

history.relativeMonth=true November 17 - December 17

history.relativeMonth=false November 17 - November 30

history.relativeWeek=true December 11 - December 17

history.relativeWeek=false December 9 (Sunday) - December 15 (Saturday)


Roving with NAMsWhen two ports are roved to one external probe or to a Cisco Catalyst6000 Network Analysis Module (NAM), the collected data for both ports displays as aggregated data. The collected data is not separated by port. With roving or spanning, if you attempt to rove two ports to one external probe or Cisco Catalyst6000 NAM, the probe or NAM aggregates the data from both ports.

For example, consider spanning port A and port B to an external probe. To begin, port A counts 100 packets of data while port B counts 400 packets of data. If you then click on port A in Traffic Monitor, you will see a total of 500 packets of data (labeled multiple) to indicate its origin (aggregated data from both ports).

Using the Command Line UtilityThe information in this section supplements and corrects information provided in Appendix C, "Using the Command-line Utility" in the nGenius Real-Time Monitor Getting Started Guide.

Understanding nGeniusCLI

The nGenius Command Line Interface (nGeniusCLI) utility is designed to work as a wrapper for dvTools to extract logged data from the nGenius database without invoking the Real-Time Monitor application. The nGeniusCLI program resides in the /rtm/bin directory.

The nGeniusCLI command, used with dvTools, can perform the following functions:

• Embed nGeniusCLI commands in a script file that can be executed by other network management applications.

• Identify the read and write community strings and the retries and timeout values set on a probe (based on the probe name or IP address), eliminating the need for entering this information manually.

• Obtain the Protocol Directory information from the nGenius Server and write this information to the following file:

/rtm/tools/usr/domain.lst

You can also use the dvTools commands without the nGeniusCLI. The dvTool commands are located in the /rtm/tools directory.

Note: The dvTools that allow domain filters require the domain.lst file in orderto run properly.

-37

Using dvTools With nGeniusCLI

When using dvTools with the nGeniusCLI, you must enter your username, password, nGenius Server IP address, and appropriate tag parameter at the beginning of each command.

Alternatively, you can define this information, and other information that you enter often, in the /rtm/bin/nGeniusCLI.properties file. Doing so eliminates the need to supply this information each time you enter a command.

To use dvTools:

1 Navigate to the /rtm/tools directory.

2 Enter the command using the appropriate syntax, as specified in the following section.

dvTools Command Syntax

If you define the hostname or IP address of the remote nGenius Server, username, and password in the nGeniusCLI.properties file as discussed in "Using dvTools With nGeniusCLI," you do not need to enter the tags and values for these parameters.

Using dvTools With the nGeniusCLI Wrapper

Windows platforms

ngeniuscli dvtool -dv "IPaddress interface_number read_community write_community timeouts retries"

For example:

ngeniuscli dvtool -sn 123.456.789 -ur administrator -pw hello-dv dvadmin "123.45.6778.90 3 public public 3 60" list

Note: To access nGeniusCLI help information for the dvTools function, enterone of the following (bin directory):Windows platforms — nGeniusCLI dvTool -helpUNIX platforms — ./nGeniusCLI.sh dvTool -help

Note: To view the correct syntax and arguments associated with a specificcommand, enter the command and press Return.


UNIX platforms

./nGeniusCLI.sh dvtool -dv "IPaddress interface_number read_community write_community timeouts retries"

For example:

./nGeniusCLI.sh dvtool -sn 123.456.789 -ur administrator -pwhello -dv dvadmin "123.45.6778.90 3 public public 3 60" list

Using dvTools Without the nGeniusCLI Wrapper

"IPaddress interface_number read_community write_community timeouts retries"

For example:

dvadmin "123.45.678.90 3 public public 3 60" list

Tools That Cannot Be Used With nGeniusCLI

You cannot use the dvlogin command using the nGeniusCLI wrapper (logs you in to a specified probe).

-39

Tools Requiring the CLI Wrapper

Table 11 lists dvTool commands that must be run using the nGeniusCLI wrapper. You can use the -ms tag with these commands.

Table 11 Tools Requiring CLI Wrapper

Command Description

dvatmsnap Provides a snapshot of segment, host, or conversation statistic groups (of the ATMRMON MIB) for the specified Port Select Group of an ATM probe or switch port.

dvcl Lists the full or partial conversation table contents for a protocol installed on the specified device or Frame Relay DLCI.

dvevlog Retrieves the agent event logs for a protocol installed on the specified device, switch port, or Frame Relay DLCI.

dvhl Lists the full or partial host table contents for a protocol installed on the specified device, switch port, or Frame Relay DLCI.

dvlist Lists the protocols that are installed on the specified device.

dvsnap Provides a snapshot of segment, host, or conversation statistics for the specified device, switch port, or Frame Relay DLCI.


Tools Recommended for Use With CLI Wrapper

It is recommended that you run the dvTool commands listed in Table 12 using the nGeniusCLI wrapper. You can use the -ms tag with these commands.

Tools Not Recommended for Use With CLI Wrapper

It is recommended that you do not run the dvTool commands listed in Table 13 using the nGeniusCLI wrapper.

Table 12 Tools Recommended With CLI Wrapper

Command Description

dvadmin Adds or deletes hosts to receive SNMP traps from the specified probe, port, or DLCI.

dvatmdump Provides an ASCII text dump of control entries related to ATMRMON MIB tables found in ATM probes or switches.

dvclean Deletes some or all MIB tables from the specified probe.

dvdump Provides an ASCII text dump of control entries related to MIB2, RMON1, enterprise RMON, and RMON2 tables found in probes, switches, and Frame Relay agents.

dvsercfg Configures or displays the serial configurations of a probe.

Table 13 Tools Not Recommended for CLI Wrapper

Command Description

dvget Displays the specified SNMP variable.

dvnext Displays the next SNMP variable after the found object identifier (OID).

dvset Sets the OID type and value of the specified SNMP variable.

dvwalk Displays all the SNMP variables defined in a MIB table.

-41

Enabling DSMON on the Cisco Catalyst6000 NAMBy default, the DSMON MIB is disabled. To collect DSMON data from your network, you must first enable the MIB on the NAM. Once the DSMON MIB is enabled, you can view DSMON data using Traffic Monitor.

To enable DSMON on the Cisco Catalyst6000 NAM:

1 From the nGenius Server system, navigate to /rtm/bin/admin.

2 Using a text editor, open the serverpublic.properties file.

3 Set the dsmon.enabled parameter to true. For example:

dsmon.enabled=true

4 Save and close the file.

5 Stop and restart the nGenius Server.

For additional information, refer to the following topics in the online Help:

• DSMON Overview

• Enabling DSMON on the Cisco Catalyst6000 NAM

• Configuring DSMON in the Cisco Catalyst6000 NAM

netscout ngenius real-time monitor™ 1.4 release...

Documents