Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6
This document contains Cisco-specific product, feature, and release note information to supplement the NetScout Systems nGenius Real-Time Monitor (RTM) documentation.
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 NetScoutnGenius 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 3 with a Pentium III or IV machine (English and Japanese)
Windows XP Professional (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.
RTM Browser Requirements
Windows platforms—Internet Explorer 6.0, 6.0.2, and 6.0.28, Netscape 4.78, and 4.79. Internet Explorer 5.5 is not supported.
Solaris platforms—Netscape 4.76.
Upgrading the Apache Server
It is strongly recommended that if you are running an Apache server version 1.3.26 or earlier, that you upgrade to version 1.3.27. The upgrade can be copied from the RTM Service Pack 6 CD. The file names are apache_1.3.27-win32-x86-no_src.exe (for Windows systems) and apache-1.3.27.sun.tar (for Solaris systems).
For Solaris Systems
Step 1 Stop the nGenius Server and wait for all of the processes to shut down.
/<RTM ROOT>/rtm/bin/stop
Step 2 Rename the <RTM ROOT>/apache directory to <RTM ROOT>/apache_old.
Step 3 Untar the patch and install the new Apache version 1.3.27 on your local disk drive by entering tar -xvf apache-1.3.27-sun.tar.
Note Do not use the RTM install directory.
Step 4 Copy the new /apache directory to the <RTM ROOT> directory.
Step 5 Copy the httpd.conf file from the <RTM ROOT>/apache_old/conf directory to the new <RTM ROOT>/apache/conf directory.
Step 6 Copy the mod_jk.so file from the <RTM ROOT>/apache_old/libexec directory to the new <RTMROOT>/apache/libexec directory.
Step 7 Change the ownership of the new /apache folder to ngenius:ngenius.
Step 8 Change the permissions of the new /apache folder to 750.
chmod -R 750 <RTM ROOT>/apache
Step 9 Manually change the Apache version to 1.3.27 in the nGeniusReg.properties file in the /usr/local/bin and /var/adm/Netscout folders.
Step 10 Uninstall the Apache application installed in Step 3 by removing the original directory created during the installation.
For example, /home/Apache-1.3.27/Apache.
Step 11 Start the nGenius server.
For Windows Systems
Step 1 Select Start>Programs>NetScout nGenius Server>Stop nGenius Server and wait for all of the processes to shut down.
Step 2 Rename the <RTM install directory>\apache directory to <RTM install directory>\apache_old.
Step 3 Install the new Apache version 1.3.27 on your local disk drive by running apache-1.3.27-win32-x86-no_src.exe.
D:\Apache-1.3.27
Step 4 On the Server Information panel, select Run When Started Manually.
Note If you do not select this option, the Apache server will automatically start
when the installation is complete and you will have to access System
Services to stop the server before you can complete the upgrade.
Step 5 Copy the new Apache directory from your local disk drive to the <RTM install directory> directory.
Step 6 Copy the httpd.conf file from the <RTM install directory>\apache_old\conf directory to the new <RTM install directory>\apache\conf directory.
Step 7 Copy the mod_jk.dll file from the <RTM install directory>\apache_old\modules directory to the <RTM install directory>\apache\modules directory.
Step 8 Manually change the Apache version to 1.3.27 in the nGeniusReg.properties file located in the %systemroot%system32 directory.
Step 9 Select Settings>Control Panel>Add/Remove Programs and remove the Apache application installed in Step 3.
Note You can also run the apache_1.3.27-win32-x8-no_src.exe file and select
the Remove option from the panel.
Step 10 Start the nGenius server.
Installing RTM with Device Fault Manager
It is recommended that you install RTM on a dedicated server. If you install RTM and Device Fault Manager (DFM) on the same server, there might be a port conflict. RTM uses ports 162 and 395 to listen for traps and events. If you are using RTM with DFM on the same server, you must configure DFM to forward traps to port 395. RTM will only accept traps forwarded from DFM. If RTM is installed first, there is no port conflict. For more information, see the Installation Guide for Device Fault Manger and the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.
Installing Service Pack 6
Service Pack 6 build 421 is a cumulative patch.You do not need to install builds 289 through 421 before installing build 421. You can apply build 421 on an RTM 1.4 system to which none, one, or more of the earlier patches have been applied.
Installing from the CD
UNIX Platforms
Step 1 Login as root.
Step 2 Stop the nGenius Server by navigating to the <RTM ROOT>/rtm/bin directory and entering ./stop.
Step 3 Change to a directory where root has write permission.
For example, change to /tmp.
Step 4 Execute the rtm140-sp6-unix.sh script, using the full path to the script on the CD.
For example, enter:
/cdrom/cdrom0/rtm140-sp6-unix.sh
Step 5 Start the nGenius Server by navigating to the <RTM ROOT>/rtm/bin directory and entering ./start.
Windows Platforms
Step 1 Stop the nGenius Server.
Step 2 Check the Task Manager to verify that the dengine.exe process is stopped.
Note If the dengine.exe is not stopped, locate the nGeniusNative,
nGeniusServer, and NSApache services from the Control Panel>Services
(on Windows NT) or Control Panel>Administrative Tools>Services (on
Windows 2000). Change the Startup Type to Manual, and then reboot.
Step 3 From the CD, execute the following file:
rtm140-sp6-win-exe
Step 4 Start the nGenius Server by selecting Start>Programs>NetScout nGenius Server>Start nGenius Server.
Downloading and Installing the Service Pack
You can download and install the Service Pack from the CCO website.
Solaris Platforms
Step 1 FTP the rtm140-sp6-unix.sh file to the local machine.
Note Be sure to FTP the file in binary mode.
Step 2 Login as root.
Step 3 Stop the nGenius Server by navigating to the <RTM ROOT>/rtm/bin directory and entering ./stop.
Step 4 Execute the following command:
chmod 777 rtm140-sp6-unix.sh
Step 5 Execute the following script:
./rtm140-sp6-unix.sh
Step 6 Start the nGenius Server by navigating to the <RTM ROOT>/rtn/bin directory and entering ./start.
Windows Platforms
Step 1 Stop the nGenius Server.
Step 2 Check the Task Manager to verify that the dengine.exe process is stopped.
Note If the dengine.exe is not stopped, locate the nGeniusNative,
nGeniusServer, and NSApache services from the Control Panel>Services
(on Windows NT) or Control Panel>Administrative Tools>Services (on
Windows 2000). Change the Startup Type to Manual, and then reboot.
Step 3 FTP the rtm140-sp6-win.exe file to the local machine.
Note Be sure to FTP the file in binary mode.
Step 4 Execute the following file:
rtm140-sp6-win-exe
Step 5 Start the nGenius Server by selecting Start>Programs>NetScout nGenius Server>Start nGenius Server.
Port Numbers Used for RTM
Table 2 shows the RTM port numbers and their usages.
Table 2 Ports Used for RTM
Port Number
Usage
162
SNMP standard port
395
NetScout proprietary port
395
Server monitor
1099
RMI registry
1961
Service manager for server
1962
Service for server
1963
Application for client
1964
Application manager for client
1965
Monitor
1971
Trap and alarms listener
1972
Trap and alarms listener
1974
Shutdown listener for RMI registry
1975
Shutdown listener for Performance Monitor server
1976
Shutdown listener for Watchdog
1977
Shutdown listener for nGeniusNative
2639
Sybase database connection
8007
Tomcat
8009
Tomcat
8080
Web server
8081
Tomcat
Supported Cisco Devices
Although other vendors' devices are listed in the NetScout documentation, Cisco Systems supports only those devices shown in Table 3.
Table 3 shows the devices supported by Cisco Systems.
Note For information about support for other devices, contact NetScout Systems.
The number of parameters that can be passed to nsscript has increased. More trap-related information is now available to the customer.
When the nGenius Server receives any RMON1 (unitization, broadcast, multicast, CRC) or protocol (IP, HTTP, etc.) unitization traps, it executes nsscript. The server passes various parameters to nsscript as command line arguments.
The nsscript file that is supplied with RTM is blank. You can add scripting commands to the file as desired. For example, you can use nsscript to start a program that configures an email notification to include the specific parameters.
The following new parameters are passed to the script:
Element (monitored element full name)
IP address
Time stamp
Severity
Trap Type
Trap Variable (the variable on which the alarm was set)
Trap Value (the actual value of the variable)
Trap Threshold (the threshold that was applied when the trap was configured)
Trap Desc
Trap Interval in seconds (the time interval at which the device checks the value against the threshold and determines if a trap needs to be fired)
When nsscript is launched by the server, the following trap information is echoed to the /rtm/log/traplog.log file:
The nGenius Server now operates in two modes—Probe and Server.
In probe mode, speeds are learned from the device. Probe is the default mode and is recommended for LMI/PVC discovery.
In Server mode, speeds are managed by the nGenius Server and are not learned from the probe. This mode is recommended for Annex_D/Annex_A/PVC discovery. To use the Server mode, you must add a parameter to the serverpublic.properties and client.properties files.
Setting the nGenius Server to Learn DLCI Speeds
Step 1 On the nGenius Server system, navigate to the <Performance Manager install directory>/rtm/bin/admin directory.
Step 2 Using a text editor, open the serverpubliv.properties file.
Step 3 Add the following parameter to the serverpublic.properties file:
FrameRelay.dlcispeed.manager=Server
Note To revert back to Probe mode, set the parameter to Probe, or comment the
line out.
Step 4 When in Server mode, the probe is automatically rebooted after the server sends the DLCI speeds to the probe. To stop the probe reboot, add the following parameter and set it to true.
FrameRelay.dlcispeed.reboot.disable=true
Step 5 Save the file, then close it.
Step 6 Change the directory to <Performance Manager install directory>/rtm/html.
Step 7 Open the client.properties file.
Step 8 Add the same parameters and settings that you added to the serverpublic.properties file in steps 3 and 4.
Step 9 Stop and restart the nGenius Server.
If you want certain interfaces to operate in a different mode than what is set in the serverpublic.properties and client.properties files, you can create a file called dlcimode.dat in the <Performance Monitor install directory>/rtm/bin directory.
You can then add the IP address and interface number(s) that you want to exclude from operating in Server mode using the following format:
ipaddress:interface_number
Enabling SMON on a Catalyst 6000 and 6500 Series NAM
The SMON 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 SMON statistics with a Catalyst 6000 and 6500 series NAM, you must
be running NAM software release 2.1(x) or later.
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 completely terminated.
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 4 shows the options for each aggregation profile.
Table 4 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
Enabling SMON Monitoring with Catalyst 6000 and 6500 Series NAMs
You must be running Catalyst 6000 and 6500 series NAM software release 2.1(x) 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) or later. The patch can
be downloaded from the following url:
Step 3 Run the following commands from the NAM CLI:
autostart vlanstats enable
autostart priostats enable
Step 4 Reboot the NAM.
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.
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.
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 modulemod_num
Step 2 Establish a console session with the NAM by entering:
Console> (enable) sessionmod_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 gatewaydefault-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 SNMPsyslocation 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 SNMPsysName 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 communitycommunity-stringrw
Step 16 Set the SNMP agent community string parameter password for read-only access by entering:
root@localhost# snmp communitycommunity-stringro
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.
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 Automatic or 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 can 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.
You can now use Traffic Monitor and Packet Analyzer with the NAM.
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.
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:
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.
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.
Changing the IP Address on the RTM Server
If you change the IP address of the RTM 1.4 Server, you must update all RTM files that are affected by this change.
Change the serveraddress entry in the client.properties file found in the <RTM ROOT>/rtm/html directory.
Change the serveraddress and java.rmi.server.hostname entries in the serverprivate.properties file found in the <RTM ROOT>/rtm/bin directory.
After the changes have been made, stop and restart the nGenius Server. If you integrate RTM with CiscoWorks Management Connection, you must also modify the IP address for SERVER="http://<IP-Address>:<port>" and HREF="http://<IP-Address>:<port>" in the following files:
nGeniusS.lf—For nGenius Server
nGeniusT.lf—For Traffic Monitor
nGeniusK.lf—For Packet Analyzer
nGeniusV.lf—For Voice Monitor
On Windows systems, the files are in the <RTM ROOT>\htdocs\xml\public\maintree directory.
On Solaris systems, the files are in the <RTM ROOT>/htdocs/XML/Public/maintree directory.
Changing the Hostname on the RTM Server
If you change the hostname on you RTM 1.4 Server, you must update all RTM files that are affected by this change in order for RTM to function properly.
Manually modify the following files with the new hostname:
The RTM 1.4 installation creates Cisco Management Connection (CMC) files for each available application. These files initially reside in the <RTM ROOT>\rtm\bin directory.
Before starting the RTM installation, you must manually create the NMSROOT environment variable and reference the root directory where the CiscoWorks software is installed. If CiscoWorks and RTM are installed on the same system, the files are copied automatically to this CiscoWorks folder.
On Windows systems—$NMSROOT\htdocs\xml\public\maintree
On Solaris systems—$NMSROOT/htdocs/XML/Public/maintree
CiscoWorks uses these files to create menus to launch nGenius Server, Traffic Monitor, Packet Analyzer and Voice Monitor.
If CiscoWorks and RTM are installed on different systems, or if nGenius was installed before CiscoWorks, you must manually copy the CMC files to the location specified in the CiscoWorks installation. After the CMC files are in place, you must reboot the system for the changes to take effect. Then, when you select nGenius Server, Traffic Monitor, Packet Analyzer, or Voice Monitor, an nGenius graphic is displayed in the main CiscoWorks window (Management Connection) and the selected application starts. The nGenius system administrator can create the same users and apply the same privileges from CiscoWorks to the nGenius system.
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:
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
CSCdy61315 (3)
RTM cannot set one direction for port or VLAN SPAN.
RTM sets SPAN sessions in with both transmit and receive directions.
To work around this problem, use the RTM GUI to set the SPAN, then log into the switch and manually change the SPAN direction with the switch CLI.
set span <source> <destination> <direction>
CSCdz58406 (3)
nGenius does not print stats properly when over 4 ports selected.
You cannot print stats with more than 4 ports.
CSCdw25289 (3)
RTM 1.3 does not support or coexist with Microsoft Terminal Server.
There is no known workaround.
CSCdy56175 (3)
RTM generates licence errors with the correct licence.properties file.
This is a known issue.
CSCdw29362 (3)
Traffic Monitor does not support trunk-only VLANs.
This is a known issue.
CSCdz04650 (3)
RTM only shows up to 30 minutes of short term history.
This is a known limitation.
CSCdy78490 (3)
RTM fails to run if the install root path contains more than 15 characters.
If you install RTM in a path with more than 15 characters, the application will not run.
To work around this problem, make sure the name of the root installation directory is no longer than 15 characters.
CSCdz85472 (3)
When RTM is used to set alarms, all the alarms in the device are overwritten.
This is a known issue.
CSCea01609 (3)
SMON Monitor does not show data for a WS-X6380-NAM running software release 1.2(3).
This is a known issue.
To work around this problem, upgrade the WS-Z-X6380-NAM to software release 2.1(2).
CSCdy22612 (3)
nGenius RTM 1.4 upgrade should not need user to login as ngenius user.
The NetScout nGenius Real-Time Monitor Release 1.4 Installation Guide says the user must be logged in as ngenius user before performing an upgrade. This is not correct. The user can be logged in as root to perform the upgrade.
CSCdw13264 (3)
User cannot log into RTM because of filesystem permissions.
RTM should be installed in a directory uder /opt. If it is installed on a file system such as /opt/nGeniusRTM, the filesystem permissions must be set to 755 (rwxr-xr-x). If the permissions are not set correctly, you cannot log into the RTM server.
CSCdz39016 (3)
RTM does not have a script to automatically change the RTM server IP/Hostname.
You must manually change the RTM server IP/Hostname.
This is a known issue.
CSCdz58046 (3)
RTM does not print stats properly when over 4 ports are selected.
This is a known limitation.
CSCdz30943 (3)
RTM Server and Traffic Monitor windows will not open.
If you log into the RTM server and log out, when you log back in the Server and Traffic Monitor windows might not open when you click on the icons.
To work around this problem, log out of RTM and restart the browser.
CSCdy22980 (3)
RTM 1.4 Data Link Layer graph truncates the port names in graphs and print outs.
The RTM 1.4 Data Link Layer graph truncates long switch port names in the vertical column and in the print outs.
To work around this problem, modify the max_graph_label_length in the $RTMROOT/html/client.properties file. The default value is 15. To see all the characters, set the value to 0.
CSCea01441 (2)
RTM is unable to SPAN multiple interfaces or VLANs to an analyzer port for Catalyst 4000 Supervisor 3.
This is a known issue.
To work around this problem, SPAN the multiple interfaces or VLANs using the switch CLI.
CSCdy37038 (2)
RTM fails to start if the fully qualified hostname exceeds 31 characters.
If a hostname exceeds 31 characters on Solaris, the RTM database server will not start.
To work around this problem, change all occurrences of the hostname to the short hostname in the $NSHOME/rtm/bin scripts.
start1
dbinit1.sh
stop1
nGeniusSQL.sh
Delete the $NSHOME/rtm/database/stealth.* file and restart RTM.
If the short hostname is longer than 31 characters, you must pick anther unique name for the database engine and replace all instances of the old hostname with the new name.
CSCea00968 (2)
RTM does not learn VLANs for Catalyst 2900, 2950, 3500 and 3550 switches.
This is a known issue.
CSCdz90403 (3)
The Segment Details View is not enabled for FastEthernet Channels or Gigabit Ethernet Channels on Catalyst 6000 switches running Cisco IOS.
This is a known issue.
CSCdz83717 (3)
The Alarm Triggered Data Capture feature does not work for NAM-1 and NAM-2 devices.
RTM creates entries in the bufferControlTable and channelTable, but the captureBufferTable is empty.
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:
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.
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.
CSCdx56220 (3)
nGenius RTM does not support NIS+ for Solaris platforms.
If RTM is installed on a Solaris server with NIS+, there might 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 might not allow 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
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.
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.
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.
Cisco IOS supports 1 spanning session in both directions or 1 session in transmit only and up to 64 in receiving only. RTM only supports the spanning in both directions and will only show that session. The RTM Server does not show the sessions that are spanned in transmit only and receive only.
This is a known limitation.
CSCdx11845 (3)
RTM cannot set different short and long term history parameters for SwitchProbe devices.
This is a known limitation.
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.
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.
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.
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.
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.
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).
CSCdy40159 (6)
The RTM licence.properties file is not always installed properly.
If you remotely install RTM, the licence.properties file might not install for the RTM server.
To work around this problem, install RTM 1.4 from the server console.
CSC61872 (6)
RTM import from CiscoWorks2000 only works with a new RTM database.
If you still have an old steath.db, the import from CiscoWorks2000 using the ngeniusciscoimport.bat/sh script will not work.
To work around this problem, shut down the RTM daemons and delete the old RTM database steath.db file before restarting the RTM server. Then run the ngeniusciscoimport.bat/sh script to import the CiscoWorks2000 switch inventory.
CSCdw28845 (6)
RTM does not deactivate rmon agent when switch is deleted or deactivated.
This is a known issue.
CSCdx61889 (6)
RTM import from CiscoWorks does not work for devices with DNS names.
RTM only imports devices with IP addresses.
To work around this problem, use the nslookup device_name command to find the device IP addresses. Then modify the hwreport.dat file so that all devices will be using IP addresses instead of DNS resolvable names.
CSCdy73525 (6)
RTM cannot select multiple ports for deactivation.
This is a known limitation.
CSCdw28412 (5)
ALL Application layer conversations should show graphs.
Traffic Monitor only displays a table with percentages for all applications in the ALL Application layer conversations screen.
CSCdy31793 (6)
Adding a switch to RTM removes all existing SNMP trap receivers.
RTM wipes out the trapDestTable in the RMON agent when you add a Catalyst switch to the server.
Table 6 nGenius RTM Resolved Problems
Bug ID (Severity)
Summary
Additional Information
CSCdx15811 (3)
RTM does not learn VLANs for a Catalyst 4006 switch with a Supervisor 3.
None.
CSCdx40454 (3)
RTM indicates warnings when trying to add numerous switch types.
None.
CSCdx36825 (3)
RTM does not properly learn a Catalyst 3548XL switch.
None.
CSCdx25484 (3)
Adding a Catalyst 6513 switch displays an error when you select Cat_6513 as the switch type.
None.
CSCdx56322 (3)
Time Triggers Data Capture does not work with Catalyst 6500 and 6000 Series NAMs.
None.
CSCdx50068 (3)
Traffic Monitor does not display data in NL and AL views if a VLAN is spanned first.
None.
CSCdx14660 (3)
Adding a switch to RTM displays an error when selecting automatic as the switch type.
None.
CSCdx56265 (3)
NL/AL Hosts and NL/AL Conversations are disabled after upgrading.
None.
CSCdx40532 (2)
RTM Task Progress Report does not always work.
None.
CSCdx56721 (2)
RMI cannot be tunneled across HTTP.
None.
CSCdz83733 (3)
Sometimes the menu option for Views/Utilization for the Application Layer View is missing.
None.
CSCdz83723 (2)
Data capture does not work properly for NAM-1 and NAM-2 devices on a Catalyst 6500 switch running Cisco IOS.
None.
CSCdz89706 (2)
Time-Triggered Data Capture does not work on Catalyst 6000 switches running Cisco IOS.
None.
CSCdx8457 (2)
Apply Alarm template to a Catalyst 6000 NAM generates a protocol write error.
None.
CSCdx25995 (3)
RTM displays errors messages in the Windows Event Viewer.
None.
CSCdu33990 (3)
Cannot open multiple nGenius applets with Management Connection.
None.
CSCdu40080 (3)
There is no tool to recover or fix the nGenius database if it is corrupted.
None.
CSCdx15887 (3)
Adding a Catalyst 6509 and 6513 switch running Cisco IOS 12.1 generates a protocol write error.
None.
CSCdx30881 (3)
RTM initial window displays a "Server not found" error.
None.
CSCdx07013 (3)
RTM will not install on Win servers with Active Directory.
None.
CSCdw84455 (3)
Traffic Monitor does not show application layer traffic for Catalyst 5000 NAMs.
None.
CSCdw29439 (3)
RTM database import from TrafficDirector can take numerous hours.
None.
CSCdw31885 (3)
RTM does not work across an NAT firewall.
None.
CSCdw23394 (3)
RTM Link Usage, Short Term Usage, and Long Term Usage might not match templates.
None.
CSCdt34319 (3)
RTM displays an error message if Java plug-in is not installed when using Netscape browser.
None.
CSCdy29073 (3)
Documentation for integrating RTM with CiscoWorks is not complete.
RTM 1.3 templates create incorrect RMON event and alarm indexes for Catalyst 2900XL switches.
None.
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
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
To obtain customized information and service, you can self-register on Cisco.com at this URL:
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: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.
Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.
Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Cisco TAC Website
The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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 this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:
iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:
Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
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, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, 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, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, 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. (0304R)
