|
|
July 23, 1999
This document contains updates to Using the Campus TrafficDirector Application.
The following sections contain updates to Using the Campus TrafficDirector Application.
The following sections contain information not specific to a particular chapter or appendix in Using the Campus TrafficDirector Application.
The TOS Monitor feature included with this release depends on a future SwitchProbe firmware release (not yet available from Cisco Systems) and is therefore not yet supported.
The Tools>Run Script feature, visible on the TrafficDirector main window, is not yet supported by Cisco Systems.
The Tools>Scope feature, visible on the TrafficDirector main window, is not yet supported by Cisco Systems.
The VPI/VCI Logging and VPI/VCI Naming features included with this release depend on a future SwitchProbe firmware release (not yet available from Cisco Systems) and are therefore not yet supported.
On some UNIX 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, make the following edits:
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>
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, indicating that logging has not been enabled:
An instance of the service is already running. Error number: 1056 in StartService
C:\NSHOME57\bin\logging: failed to properly start logging daemons, at
C:\NSHOME57\bin\logging line 66
You can ignore this message because logging has been successfully enabled.
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. If you wish to make any changes to the type of database you use with the TrafficDirector application, see Table 1.
5.3 MSQL 6.5 MSQL 6.5 You do not need to do anything additional. Data collected and saved on the server can be used by TrafficDirector Release 5.7. 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 (if the Microsoft upgrade completes successfully). 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. 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 (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. 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 1: 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
or
5.6
or
5.6 (continued)
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):
You can now display Frame Relay agent data in the DLCI Link Status History and DLCI Link Status Summary reports as a percentage of uptime instead of downtime.
To display these reports as uptime, follow these steps:
Step 1 Change directory to $NSHOME\usr.
Step 2 Using a text editor, open the default.dvp file.
Step 3 Locate the switch-to-linkup-rpt field.
Step 4 Change the value from 0 to 1.
After you make this change and run these reports, the words "DLCI Up" display in 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.
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: Thu Sep 30 12:51:31 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
