|
|
These release notes describe the new features and known problems in TrafficDirector Release 5.7.2.
This document contains the following sections:
Use these publications to learn how to install and use the TrafficDirector application:
Note the following cautions about the TrafficDirector installation:
 | Caution Cisco Systems strongly recommends that you use the default installation path of C:\TD. If you wish to override the default and install the software in a preexisting location, you should install the software in a directory subordinate to that location (for example, C:\alternate_location\TD). |
| Caution Cisco Systems strongly recommends that you use the default installation path of /opt/CSCOtd5. If you wish to override the default and install the software in a preexisting location, you should install the software in a directory subordinate to that location (for example, /alternate_location/CSCOtd5). |
The following sections describe the system requirements for the successful use of the TrafficDirector application:
The hardware listed in Table 1 is required to use the TrafficDirector application effectively.
The software listed in Table 2 is required to use the TrafficDirector application effectively.
| Platform | Requirements |
|---|---|
Windows NT |
|
Solaris |
|
The following sections list the Cisco devices supported by the TrafficDirector application:
The following Cisco switches are supported:
Catalyst 1200, 1800, 1900, 1912, 1924, 2800, 2820, 2822, 2828, 2901, 2902, 2908XL, 2916XL, 2924XL, 2926, 2926G, 2948G, 3000, 3100, 3200, 3500XL, 3900, 3920, 4000, 5000, 5002, 5500, 5505, 5509, 6000, and 8510/8540CSR.
The following Cisco routers are supported:
800 series (except 805), 1000 series, 1600 series, 1700 series, 2500 series, 2600 series (except 2613), 3600 series, 4000 series, 4500 series, 4700 series, 7000 series, 7200 series, and 7500 series.
The following types of SwitchProbe devices are supported:
The following sections describe the new features introduced in this release:
This release supports the new Cisco DS-3 ATM and Gigabit Ethernet SwitchProbe devices.
The naming scheme for conversation data and addressing has changed as shown in the following list. These changes allow you to clearly identify which host is sending the data and which host is receiving the data. (See Figure 1.)
Two new reports---fdsh.rt and fdss.rt---allow you to generate a report for the Data Terminal Equipment (DTE, outgoing) and Data Communications Equipment (DCE, incoming) sides for any full-duplex agent (Fast Ethernet, Gigabit Ethernet, OC-3 ATM, DS-3 ATM).
The sum of the bandwidth for the full-duplex agent is broken down into DTE utilization versus DCE utilization. These reports help you to differentiate the bandwidth for each component. In previous releases, you were required to edit the .rr configuration file and modify the agent name syntax to create independent DTE or DCE reports.
You can disable the daemon shutdown message that is displayed (Do you want to shut down all daemons?) when you shut down the TrafficDirector application. To disable the message, follow these steps:
Step 1 Change directory to $NSHOME\usr.
Step 2 Using a text editor, open the default.dvp file for editing.
Step 3 Locate the text string ok-to-shutdown-msg.
Step 4 Disable the display of the confirmation message by replacing the default value of yes with no.
Step 5 Save the change.
The number of child protocols allowed in the domain tree file (domtree.inf) for use in the Protocol Distribution report has been increased from 15 children to 40.
Available for use at any installation, the domtree.inf file lists the domain names of the parent-child relationships that display when you run the Protocol Zoom application
You can enhance and edit the domtree.inf file using an ASCII text editor. If you add a domain name to this file, no activity is reported unless the domain has been defined using the Domain Editor application and installed on an agent using Configuration Manager.
Edit the domtree.inf file to add the "children" to the parent. Verify that logging has been enabled for these children before running the Protocol Distribution Report; the report will list all children for the parent, even if there is no data available.
Figure 2 illustrates the domain group parent-child relationship.
A new statistics group has been added in the Report Editor Report Template Details screen for the Host Outbound Summary Report and the Host Verbose Summary report.
The following sections describe usability and functional improvements to the Trend Reporter:
The Trend Reporter GUI has been improved to streamline the report generation process.
You can now select one or more address ranges for hosts in Trend Reporter. This feature lets you report on those addresses you are most interested in.
You can add the ability to select one or more ranges of hosts and/or one or more specific to any Trend Reporter report using address data. This functionality is for IP (addresses) only, but will cover host, conversation, TopN Conversation and ART data.
The host/host range selection feature lets you specify those IP addresses you wish to capture for a particular report.
For example:
To run a Host/Host Range report, follow these steps:
Step 1 Use Trend Reporter to select an agent.
Step 2 Select a host, conversation, TopN Conversation, or ART data report.
Step 3 Save the report. (It is saved as a *.rr file.)
Step 4 To specify a single range, edit *.rr file and add as the last line:host host_IP
Step 5 To specify multiple ranges, edit *.rr file and add as the last lines:
host host_IP_1 host_IP_2
host host_IP_1
host host _IP_2
Step 6 Save the .rr file.
Step 7 Start Report Editor.
The Report Editor window is displayed.
Step 8 To select a predefined report type, follow these steps:
(a) Click the window button (...) to the right of the Type field to display the Select Report Type list box.
(b) Select the report type you want from those displayed in the Select Report Type list box.
(c) Click OK.
(d) To change the title displayed in the Title field (optional), highlight the text.
(e) Press Delete to clear the field.
(f) Enter a new title.
(g) Enter descriptive text (optional), such as Company Name, Department Name, or Customer Name in the Header1, Header2, and Footer fields.
Step 9 To select the report format, follow these steps:
(a) Click the button to the right of the Report Format field to display the Select Report Format Type list box.
(b) Highlight the report format type you want.
(c) Click OK.
The list of available formats may vary between three sets---Graphical (bar, stacked-bar, plot, and pie), ASCII (tabular, CSV, and TSV), and All (both Graphical and ASCII).
Step 10 To specify a configuration file (.rr), enter the file name directly, or click the button to the right of the Config File field.
Step 11 Select the file you want from those displayed in the Config File Template File Selection Box (FSB).
Step 12 Highlight the file you want.
Step 13 Click OK.
Configuration files include any files that contain report parameters. When specified, the additional configuration file parameters override the previously defined parameters. The order of parsing parameters is important---the last parameter definition is used.
Step 14 To control specific report details, click Details.
Step 15 When finished with report details, click OK.
Step 16 To save the file, do one of the following:
Step 17 To continue, follow these steps:
(a) Enter the file name in the File Name field of the file selection box. You may use hyphens or underscores in the file name, but no spaces.
(b) Click Save.
The report template (*.rt) is saved. You can now use this template to generate Host reports in Trend Reporter.
Step 18 To cancel the Save operation, click Cancel.
Several real-time monitoring applications have been enhanced to increase ease of use and provide extensions for other new features.
The Data Capture feature now lets you save ATM, Ethernet, Token Ring, and FDDI packets in Sniffer 5.0 format. You can also filter traffic based on protocol definitions in addition to filters defined in the Filter Editor.
To support a greater number of industry-standard and most widely used protocols, definitions for the following decodes have been added:
Viewing data is now easier through:
Both users and administrators can view all currently configured domains and existing alarms in the enhanced Domain/Alarm Discovery application.
The following functionality is no longer available.
Table 3 lists the problems known to exist in TrafficDirector Release 5.7.2.
| Bud ID | Summary | Explanation |
|---|---|---|
None | ping | The TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the Windows NT or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete the $NSHOME\usr\pingoff file. |
None | Generic indexing scheme | To enable the TrafficDirector application to use the generic index on switches, you must change the flag enable-generic- |
None | Catalyst 1900 and 2800 switch support | If you receive errors when installing a properties file to the Catalyst 1900 and 2800 switch, run dvclean and perform the installation again. |
None | Network Analysis Module Release 4.3(1a) | The Network Analysis Module supports the roving of only one port; therefore, adding a port to a list of roved ports is not supported. Running Domain Discovery against a switch port, VLAN, or FEC that is roved to a Network Analysis Module results in an error retrieving alarm entries. |
CSCdk29881 | Learning VLANs and FECs | VLANs and FECs are learned only on Catalyst 5000- and 6000- series and 2984G and 2926G devices. |
CSCdk44815 | Support for switch roving | If you make any changes to a roved port, FEC, or VLAN without using the TrafficDirector application (for example, using the switch command-line interface), the TrafficDirector application will not recognize these changes. |
None | TrafficDirector as trap receiver | On all switches (except the Catalyst 4000-, 5000-, and 6000- series and the Catalyst 2926G and 2948G switches), the TrafficDirector application does not autoconfigure itself as a trap receiver. You must manually set the trap destination from the switch command-line interface (CLI). |
CSCdm10165 | No script file launched | When an alert is received in the TrafficDirector application, the script associated with that threshold is not always launched. |
CSCdm57988 | Cannot generate report using roved VLAN or FEC to Network Analysis Module | You cannot generate reports from data collected on the Network Analysis Module using Trend Reporter. |
CSCdm87953 | HCRMON 64-bit counter variable shows only 32-bit value | The dvwalk utility is not currently compatible with HCRMON. As a result, when you use dvwalk to display 64-bit counters, you will receive meaningless information when counters exceed a 32-bit value. |
CSCdp15544 | Data capture slice size | The documentation for data capture incorrectly states that setting the slice size to zero captures an entire packet. Setting the slice size to zero captures only 128 bytes of a packet. To get the largest slice size possible, you must set the slice size to 1518 bytes. |
CSCdm60856 | Cannot launch TrafficDirector with a Catalyst 8510 link | For a Catalyst 8510 link, the Catalyst 8510 package should be installed to start TrafficDirector from the CWSI Topology map. |
The limitations described in the following sections are known to exist in TrafficDirector Release 5.7.2.
To reinstall the TrafficDirector software on Solaris or Windows NT platforms, you must kill the resolver process before starting the reinstallation.
To kill the resolver process on Solaris platforms, follow these steps:
Step 1 Determine the resolver process ID by entering the following command at the UNIX prompt:
ps -ef | grep resolver
Information similar to the following is displayed:
smith 20144 22608 1 14:49:43pts/1 0:00 grep resolver
The first number displayed (in this example, 20144) is the resolver process ID.
Step 2 Kill the resolver process by entering the following command at the UNIX prompt:
kill 20144
After killing the resolver process, complete the installation by following the procedures in TrafficDirector Release 5.7.2 Installation Guide for Windows NT and Solaris.
To kill the resolver process on Windows NT platforms, follow these steps:
Step 1 From the Windows NT Task Manager, click the Processes tab.
Step 2 Select each perl.exe image.
Step 3 Click End Process.
Roving multiple ports from different VLANs is not supported for Catalyst 5000 switches. However, if you try to rove on ports from multiple VLANs, no error message is displayed to warn you that that action is not permitted. When you are prompted to reinitialize the counters, respond NO so data in the agent counters is not lost.
If you use a Fast Ethernet SwitchProbe device with 8MB of RAM, interface 1 set to manage + monitor mode, interface 3 set to monitor mode, and the ART MIB enabled, the default value for the art_report_size parameter will cause the device to hang, and the TrafficDirector application to lose contact with it.
To prevent this from happening, follow these steps:
Step 1 From Configuration Manager, select Remote Login.
Step 2 Go to the Change ARTMIB parameters screen.
Step 3 Change the default value of the art_report_size parameter to a value less than or equal to 800.
The following sections contain updates to Using the Campus TrafficDirector Application.
On Solaris platforms, some of the TrafficDirector graphical applications do not start properly because of the inability to allocate color map entries. For example, the following message might be displayed:
Warning: Cannot allocate colormap entry for "Cadet Blue."
To correct this problem, edit the .traffdir.cshrc or .traffdir.sh file in the $NSHOME directory to change the path to the environment variable for RMONBROWSER to read as follows:
setenv HTML /data/netscape/netscape -install
setenv RMONBROWSER ${HTMLBIN}
HTMLBIN = /data/netscape/netscape -install RMONBROWSER = $HTMLBIN
Or, if you are using the default path to the browser, edit the command as follows:
setenv RMONBROWSER "/opt/netscape/netscape -install"
Source the .traffdir.cshrc or .traffdir.sh file before starting the TrafficDirector application. All color map entries will run properly.
If you want to add a generic domain to a properties file for a Frame Relay agent using the second properties file installation option ("Replace agent properties, but maintain existing counters") or the third properties file installation option ("Reset all counters and replace agent properties"), you must run the dvclean command-line utility.
Run dvclean against the Frame Relay agent before adding the domain to the properties file and installing the properties file.
For example:
dvclean -f <frame_relay_agent_name> filter
dvclean -f <frame_relay_agent_name> channel
or:
dvclean -f <frame_relay_agent_name>
Frame Relay agents can now be members of agent groups.
On page 7-6, the following information should be noted at Step 7, in the description of the DLCI Name field.
Traps can now return DLCI numbers; therefore, you can use one script to handle all DLCIs associated with a trunk.
On page 9-28, the following information should be noted in the section "Using the Set Trap Destination to Send Alerts to TrafficDirector Hosts."
The Traffic Monitor application can now distinguish CIR utilization on traffic displays that show DLCIs. For example, you can now differentiate 50% of 56 kbps traffic from 50% of 128 kbps traffic to evaluate CIR compliance.
When you start the All Talkers application for the RMON domain from anywhere within the TrafficDirector application, no RMON entries will be displayed in the host list. Because the method of Ethernet-to-ATM frame conversion creates pseudo-MAC addresses that do not exist in the MAC layer, valid data displays cannot be generated.
The All Conversations application displays different values in the error count column, depending on the type of domain being reported.
The Protocol Monitor application displays all DLCIs associated with a trunk and can show up to 32 DLCIs simultaneously.
Packets captured on one interface might include packets seen on other interfaces. If you run a data capture for a selected interface on a SwitchProbe device or Network Analysis Module and wish to perform a second data capture for a different interface on the same device, you must clear the agent buffer before performing the second data capture to ensure the integrity of the data capture.
This release supports both Version 6.5 and Version 7.0 of the Microsoft SQL Server. To make any changes to the type of database you use with the TrafficDirector application, see Table 4.
5.5.1a, MSQL 6.5 MSQL 6.5 You do not have to do anything additional. Data collected and saved on the server can be used by TrafficDirector Release 5.7.x. MSQL 6.5 MSQL 7.0 Refer to the Microsoft documentation to upgrade the MSQL Server from Version 6.5 to 7.0. Data collected and saved on the server can be used by TrafficDirector Release 5.7.x. (if the Microsoft upgrade completes successfully). MSQL 6.5 Embedded This is not recommended or supported by Cisco Systems. Data collected and saved with the MSQL Server cannot be used with the embedded SQL server. You will need to modify agent, switch, and Frame Relay agent definitions to reflect the embedded SQL server (listed as local). 5.5.1a, Embedded Embedded You do not need to do anything additional. Data collected and saved on the server can be used by TrafficDirector Release 5.7.x. Embedded MSQL 6.5 This is not recommended or supported by Cisco Systems. Data collected and saved with the MSQL Server cannot be used with the embedded SQL server. You will need to modify agent, switch, and Frame Relay agent definitions to reflect the embedded SQL server (listed as local). Embedded MSQL 7.0 This is not recommended or supported by Cisco Systems. Data collected and saved with the MSQL Server cannot be used with the embedded SQL server. You will need to modify agent, switch, and Frame Relay agent definitions to reflect the embedded SQL server (listed as local).
Table 4: TrafficDirector Database Upgrade Scenarios
If you are running
this release of the TrafficDirector application...
And are
currently
using this
database...
And you want
to use/preserve this database...
Then
5,6, or
5.7.x
5.6,
or 5.7.x
(continued)
If you use the logging -off command to disable logging, you will not be able to generate reports. You must use the logging -on command to generate reports.
If you are using the embedded SQL server and disable logging, then enable logging, an error message similar to the following might be displayed, suggesting that logging has not been enabled:
An instance of the service is already running. Error number: 1056 in StartServiceC:\TD\bin\logging: failed to properly start logging daemons, at C:\TD\bin\logging line 66
You can ignore this message because logging has been successfully enabled.
Graphical displays might not be displayed accurately on Token Ring topologies; however, text displays are accurate.
The following reports are no longer available (listed in Table 31-2):
For a Frame Relay agent's DLCIs, you can display the DLCI Link Status History and DLCI Link Status Summary reports as a percentage of up time instead of a percentage of down time.
To display these reports as up time, follow these steps:
Step 1 Change directory to $NSHOME\usr.
Step 2 Using any text editor, open the default.dvp file for editing.
Step 3 Locate the switch-to-linkup-rpt field.
Step 4 Change the value from zero (0) to one (1).
After you make the change and you run the DLCI Link Status History and DLCI Link Status Summary reports, the report label DLCI Up appears within the graph in the top left corner of the report above the scale.
The following information pertains to the Trend Reporter application:
The event logging subsystem allows you to customize the types of informational messages you wish to retain and how long you wish to retain them for TrafficDirector applications and background daemons.
To properly use the dvwalk, dvset, and dvget utilities on Windows NT platforms, you must specify the IP address---not the agent name---when executing the command.
Integration of the TrafficDirector application with SunNet Manager is no longer supported. Therefore, all references to this product should be disregarded.
The online help information for the TopN Conversation application does not work properly.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Posted: Fri Oct 29 17:13:00 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.