Release Notes for TrafficDirector Release 5.8.0a on Windows NT
and Solaris

These release notes are for use with TrafficDirector Release 5.8.0a running on Windows NT and Solaris platforms. The supported Windows NT version is 4.0; the supported Solaris versions are 2.6 and 2.7.

They contain:

New Feature

TrafficDirector Release 5.8.0a contains the new feature extended internal roving. With the introduction of the Catalyst 6000 Network Analysis Module (NAM), the internal roving capabilities supported in Catalyst 5000 family of switches now also apply to the Cisco Catalyst 6000 family of switches that support internal roving.

Note 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 the TrafficDirector application is running are successful.

If you have not already configured the NAM, follow the instructions in the Catalyst 6000 Network Analysis Module Installation and Configuration Note.

: For configuration instructions, see the sections, "Adding a Switch to the TrafficDirector Configuration Manager Application" and "Adding an Agent to the TrafficDirector Configuration Manager Application."

Note You do not need to configure the switch to include a roving agent or analyzer port because you can use the built-in roving features of the switch.

For more information, see these sections:

Adding a Switch to the TrafficDirector Configuration Manager Application

You can now monitor network applications in the Catalyst 6000 family of LAN switches by installing a Network Analysis Module (NAM). The NAM is an internal device---similar in function to an external Cisco SwitchProbe device---that extends (for Ethernet VLANs) the Remote Monitoring (RMON) support provided by the Cisco Catalyst 6000 family of switches.This support is an extension of the RMON support provided by the Catalyst supervisor engine.

The NAM provides a fully integrated RMON, RMON2, NetFlow, VLAN, and Fast EtherChannel (FEC) monitoring solution for the Catalyst 6000 family of LAN switches.

The Catalyst switched port analyzer (SPAN) selects network traffic and directs it to the NAM. Using the TrafficDirector application, you can analyze link characteristics, packet layers for capacity planning or departmental accounting, differentiated service deployment and policies, and filter/capture packets for debugging.

The primary TrafficDirector application function is to manage the RMON and RMON2 agents embedded in certain devices. You can add the Catalyst 6000 NAM as an agent or switch in the TrafficDirector Configuration Manager application. However, if you add the NAM as a switch, the application cannot communicate with the switch in which the NAM is installed until you add specific information about it using the TrafficDirector Configuration Manager application.

Before the TrafficDirector console can communicate with a switch in which the NAM is installed, you must enter (in Configuration Manager) the switch IP address, type of switch, read and write community strings established on the switch, and, if applicable, the names of the agents attached to the switch.

After you add a switch definition in Configuration Manager, the TrafficDirector application automatically learns and displays the ports associated with that switch and learns the VLANs and FECs configured on the switch.

To add a new switch definition:

Step 1 Start the TrafficDirector application.

Step 2 Click the Admin radio button in the upper-right corner of the TrafficDirector main window.

Step 3 Click the Config Manager icon in the Admin level window.

Step 4 In the Configuration Manager window, click the Switch radio button.

Step 5 Click Add.

The Add Switch dialog box is displayed.

Step 6 In the Switch Name text box, enter a name for the switch you are defining.

The name can be up to 15 alphanumeric characters and is case-sensitive. 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 7 In the IP Address text box, 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).

Note If you are using the NAM installed in a Catalyst 6000 switch, all other functions of the Configuration Manager application will use the IP address of
the NAM.

Step 8 In the Switch Type text box, select the type of switch you are adding.

If you have the NAM installed in a Catalyst 6000 switch with software version 5.5 or above, select Cat_6000_v5.5+.
If you have the NAM installed in a Catalyst 6000 switch with software version 5.4 or lower, select Cat_6000.
If you have the NAM installed in a Catalyst 6509 switch with software version 5.5 or above, select Cat_6509_v5.5+.
If you have the NAM installed in a Catalyst 6509 switch with software version 5.4 or lower, select Cat_6509.

Tips On a Microsoft Windows NT platform, click the drop-down list box to select a switch type.

On a Solaris platform, click the window button (...) next to the Switch Type text box.

Step 9 In the community names text boxes, 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 section "Identifying Community Strings on the NAM."

Step 10 In the Retries and Timeout text boxes, do the following:

a. Retries---Enter the number of times (between 1 and 1000) that the TrafficDirector console should try to reach the switch if there is no response.

b. Timeout---Enter the length of time in seconds (between 1 and 1000) that the TrafficDirector console should wait between each retry.

If you are using the NAM installed in a Catalyst 6000 switch to support internal roving, skip to Step 15. The remaining text boxes are automatically populated by Configuration Manager.

Step 11 Identify a roving SwitchProbe device that is physically connected to the switch:

a. To display the Agent List dialog box, click the window button (...) to the right of the Roving
text box.

b. Select the agent name (assigned to the roving SwitchProbe device) from the Agent List dialog box.

c. Click OK.

Note The TrafficDirector application identifies the port names on a switch (in the Interface list box in the lower left pane of the window) after you add the switch definition to Configuration Manager.

Step 12 Specify one or more dedicated agents (SwitchProbe devices) attached to a trunk or server link:

a. To display the Agent List dialog box, click the window button (...) to the right of the Agent1
text box.

b. Select the agent name (assigned to the SwitchProbe device) from the Agent List dialog box.

c. Click OK.

d. If the dedicated SwitchProbe device is monitoring a trunk link (traffic between two switches), select Trunk from the Server drop-down list box.

If the dedicated SwitchProbe device is monitoring a server link (traffic seen for the server connected to a switch port), select Server from the Server drop-down list box.

e. Repeat Step a. through Step d. for each dedicated SwitchProbe device attached to the switch.

Note You can define up to four dedicated agents (SwitchProbe devices) for each switch definition.

Step 13 Identify the RMON level supported in a switch with the properties file. You can also use the properties file to define logging and trap information for individual switch interfaces.

In the Properties File text box, do one of the following:

: For example, if you named the switch Joe (in Step 1) the name Joe is assigned to the properties file.

Enter the name of an existing switch properties file applicable to the switch you are defining.

Step 14

Note When both the SQL Server and the TrafficDirector software exist on the same system, the default name local is displayed.

Step 15 To add the switch to Configuration Manager, do one of the following:

To add the switch and return to the Configuration Manager window, click OK.

: The TrafficDirector application queries the switch and displays the interfaces associated with a switch in the Interface list box in the lower Configuration Manager window.
: Click the appropriate interface radio buttons (port, VLAN, or FEC) to view the list of interfaces associated with a switch or the network traffic associated with a switch interface.

To add the switch to Configuration Manager without closing the Add Switch dialog box, click Apply.

: The TrafficDirector application queries the switch and displays the interfaces associated with a switch in the Interface list box in the lower left Configuration Manager window.
: Click the appropriate interface radio buttons (port, VLAN, or FEC) to view the list of interfaces associated with a switch or the network traffic associated with a switch interface.

To discard the information and close the Add Switch dialog box, click Cancel.

Adding an Agent to the TrafficDirector Configuration Manager Application

When using the NAM installed in a Catalyst 6000 switch you must add a new agent in Configuration Manager for every slot/port, VLAN, or FEC from which you wish to gather RMON/RMON2 statistical information. The agent mode of the NAM is used to do logging for historical trend reporting.

Step 1 Start the TrafficDirector application.

Step 2 Click the Admin radio button in the upper-right corner of the TrafficDirector main window.

Step 3 Click the Config Manager icon in the Admin level window.

Step 4 In the Configuration Manager window, click the Agent radio button.

Step 5 Click Add.

The Add Agent dialog box is displayed.

Step 6 In the Agent Name text box, enter a name for the agent you are defining.

The name you select can be up to 15 alphanumeric characters and is case-sensitive. 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 agent.

Step 7 In the IP Address text box, enter a valid agent IP address.

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

Step 8 In the Interface text box, enter the interface number for every for every VLAN or FEC that is configured on the agent to manage the activity on a network segment.

For example, if VLAN2 is interface number 5, and you wish to gather statistics for this VLAN, you would enter 5 in the Interface text box.

For each slot/port that is configured on the agent to manage the activity on the network segment, enter 1.

Step 9 In the Network drop-down box, select the network topology supported on this agent.

Step 10 Optional. In the Description text box, enter a description (up to 30 characters) about this agent configuration.

Step 11 In the community names text boxes, do the following.

a. Read Community---Enter the read community name established on the agent.

b. Write Community---Enter the write community name established on the agent.

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

Step 12 In the Retries and Timeout text boxes, do the following:

a. Retries---Enter the number of times (between 1 and 1000) that the TrafficDirector console should try to reach the switch if there is no response.

b. Timeout---Enter the length of time in seconds, (between 1 and 1000) that the TrafficDirector console should wait between each retry.

In the Startup File text box, the name of the default startup script is displayed.

Step 13 A properties file identifies the RMON level supported in an agent. You can also use the properties file to define logging and trap information for individual agent interfaces.

In the Properties File text box, do the following:

a. To display the Properties File List dialog box, click the window button (...) to the right of the Properties File text box.

b. Select the properties file for the agent you are adding. If you are using the NAM as an agent, select nam6kprop.

Note If the properties file nam6kprop does not exist, select the properties file name containing the text 6k.

Step 14

Note When both the SQL Server and the TrafficDirector software exist on the same system, the default name of "local" is displayed.

Step 15 To add the agent to Configuration Manager, do one of the following:

To add the agent and return to the Configuration Manager window, click OK.

: The agent name you assigned to this configuration is displayed in the Configuration Manager Agent list box.

To add the agent to Configuration Manager without closing the Add Agent dialog box, click Apply.

: The Apply button is a convenient way to consecutively add more agent definitions.

To discard the information and close the Add Agent dialog box, click Cancel.

Note If you are using the NAM installed in the Catalyst 6000 switch, you must still configure a SPAN through the NAM command-line interface even though you added the NAM as an agent. You must configure a SPAN to direct traffic from a port, trunk, VLAN, or FEC to the slot/port on the NAM. After the SPAN is enabled, RMON/RMON2 statistical data is gathered. For more information on configuring a SPAN, see Catalyst 6000 Network Analysis Module Installation and Configuration Note.

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 displayed information:

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

Roving Switch Interfaces

Roving is a mechanism in Configuration Manager used for monitoring individual interfaces supported by a switch. These interfaces can include physical switch ports (including trunks), VLANs, and FECs.

Note Roving with Configuration Manager is done primarily in switch mode. Roving is not available in agent mode.

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

Step 2 Click the switch name.

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

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

Step 3 In the bottom left pane of the window, select the port, VLAN, or FEC to rove.

Note A port list is displayed by default. However, you can view VLANs or FECs by clicking the appropriate radio button.

Step 4 After you select the object to rove, click Rove On.

The Internal Agent property window is displayed from which you can select a properties file to install.

Step 5 Select the nam6kprop properties file.

Step 6 Click OK.

Step 7 After the nam6kprop file is installed on the NAM, close the Configuration Manager window.

You can now analyze TopN Talkers, All Talkers, Protocol Monitor, and Protocol Zoom by default for each port, VLAN, or FEC that you roved in Configuration Manager.

Using Trend Reporter with the Catalyst 6000 NAM

The Trend Reporter application helps you establish an overall picture of your organization's network usage and health. You can use trend reports to troubleshoot congestion, monitor usage, and plan for future capacity requirements.

To collect data with the Catalyst 6000 NAM for use in Trend Reporter:

Step 1 Add the NAM as a switch, following all steps in the section "Adding a Switch to the TrafficDirector Configuration Manager Application."

Step 2 Rove the interfaces on the switch from which you with to collect data, following all steps in the section "Roving Switch Interfaces."

Step 3 Add the NAM as an agent, following all steps in the section "Adding an Agent to the TrafficDirector Configuration Manager Application."

Step 4 Click the Trend Reporter icon.

You can now generate reports using Trend Reporter for the interfaces roved.
For more information about Trend Reporter, see Using the TrafficDirector Application.

Testing the Operational Status of a Switch with a NAM Installed

You might need to determine if a switch is operational, or if the TrafficDirector application can read and write to the MIB content on the switch with an installed NAM.

Step 1 Start the TrafficDirector application.

Step 2 Click the Admin radio button in upper-right corner of the TrafficDirector main window.

Step 3 Click the Config Manager icon in the Admin level window.

Step 4 Click the Switch radio button.

Step 5 Select the name of the switch to test from the Agent list box.

Step 6 Click Test.

The TrafficDirector application queries the switch and displays the results:

If the switch is operational, the message identifies general, system, and roving information about the switch.
If the switch is not operational, the message identifies whether ping is supported, including whether the read and write community strings passed or failed.

Viewing RMON/RMON2 Data on the NAM

After you install properties on the NAM, you can review which protocols are installed. You can do this in either switch mode or agent mode.

Step 1 To view RMON/RMON2 data on a switch, click the Switch radio button.

To view RMON/RMON2 data on an agent, click the Agent radio button.

Step 2 Select the name of the switch or agent from which to view RMON/RMON2 data.

Step 3 Click the Protocol radio button.

The protocol-level applications are displayed.

Step 4 Click All Conv to retrieve data for all IP-level conversations between two IP addresses.

The Domain Discovery window is displayed.

Note The protocol properties file includes IP protocol and the C (conversations), which is enabled. If conversations is not enabled, an error message shows that the feature is not enabled.

Known Limitations

The limitations described in the following sections are known to exist in TrafficDirector Release 5.8.0a:

Multiport Roving for Ports in Different VLANs

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 that data in the agent counters is not lost.

DLCI Name Restrictions

Only the first eight characters of the DLCI name display in the list box in the TrafficDirector main window.

TrafficDirector Application Loses Contact

If you use a Fast Ethernet SwitchProbe device with 8 MB 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 causes the device to hang, and the TrafficDirector application to lose contact with it.

To prevent this from happening:

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.

Landscape Printing

Landscape printing from Trend Reporter is not supported.

Alert Monitor

Alert community strings displayed in Alert Monitor might have extra characters.

Domain Discovery Display

When roving an FEC, Domain Discovery displays incorrect statistic information for the ports which are not roved. The RMON statistics are correct but the data for all other domains displayed are inaccurate.

Report Editor User Interface

The Report Editor user interface cannot handle changes related to selecting host(s) for reports. You must modify an existing report template (.rt) file or create a new template.

TopN Sorted Summary Graphs Display Inverted

Some non-inverted summary graphs sorted by TopN show the graph bar lowest value on the left and the highest value on the right. The display should show the highest value on the left and the lowest value on the right.

TopN Conversations Application

Some host names are not displayed in the ALLAL TopN conversations application.
The wrong year is reported and displayed in the ALLAL and ALLNL TopN Conversations application window. Dates may be displayed showing the year as 1969.

Reinstalling the TrafficDirector Software

To reinstall the TrafficDirector software, you must kill the resolver process before starting the reinstallation.

Solaris Platforms

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:43  pts/1    0:00
grep resolver

The first number displayed (in this example, 20144) is the resolver process ID.

Step 2 To kill the resolver process, enter 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.8 Installation Guide for Windows NT and Solaris.

Windows NT Platforms

Step 1 From the Windows NT Task Manager, click the Processes tab.

Step 2 Select the dbchk.exe image.

Step 3 Click End Process.

Step 4 Select the dbsnpres.exe image.

Step 5 Click End Process.

Step 6 Select the dvtrapd.exe image.

Step 7 Click End Process.

Step 8 Close the Task Manager window.

VLAN Monitor Application Display

The VLAN Monitor application does not display the VLAN ID zero even though this VLAN ID might be displayed in the Configuration Manager window. The VLAN Monitor application display begins at VLAN ID 1and can display more than 4000 VLAN IDs.

However, the default VLAN display can contain up to 32 VLANs. To see more than 32 VLANs on the display, use a text editor to change the max-trafmon-agents parameter in the default.dvp file in the $NSHOME/usr directory.

Graphical Applications on Solaris Platforms

On Solaris platforms, some 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:

For .cshrc:

setenv HTML /data/netscape/netscape -install
setenv RMONBROWSER ${HTMLBIN}

For .sh:

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.

Note You cannot edit or delete traps set using the Set Trap Destinations dialog box. To edit trap destination information or delete existing traps, you must use the dvadmin command-line utility.

Report/Logging Interval Time Mismatch

Trend Reporter day range settings work properly when the report uses an interval that matches the logging interval for the domain used to generate the report. However, if you set time ranges on reports at different intervals, the data may mismatch.

For example, if logging was off between 1 and 5 p.m and the reporter interval is between 1 and 5 p.m. on the same day, the message no data found is displayed. However, a report with an interval set to 11 a.m. to 8 p.m. also shows data points between 1 p.m. and 5 p.m.

Short- and Long-Term History Utilization

The utilization shown in Short- and Long-Term History is 180%. All other graphs and charts correctly show utilization at 90%.

Known Problems

Known problems are unexpected behaviors or defects in TrafficDirector software releases. They are graded according to severity level. These release notes contain information for severity levels 1 and 2 only.

You can search for known problems with the Cisco bug tracking system tool, called Bug Navigator II. To access Bug Navigator II, do one of the following:

Enter http://www.cisco.com/support/bugtools in your web browser.
Log in to CCO and select Service & Support>Technical Assistance Center>Tools>Software Bug Toolkit>Bug Navigator II.

Table 1 describes the severity level 1 and 2 problems known to exist in this release.

Table 1: TrafficDirector Known Problems

Bug ID Summary Explanation

None

ping
(Windows NT platforms only)

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. To perform pings successfully when you are running any other TCP/IP stack, you must 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-control-index in the $NSHOME\usr\default.dvp file from no to yes.

None

Catalyst 1900 and 2800 switch support

If you encounter errors when installing a properties file to a Cisco Catalyst 1900 or 2800 switch, run the dvclean utility and perform the installation again.

None

TrafficDirector as trap receiver

On all switches (except the Catalyst 4000-, 5000-, and 6000-family 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).

CSCdp82231

Support of two NAMs in one switch

If you add a NAM in a Catalyst 6000-family switch using the Configuration Manger application, the first NAM added will be assigned a static Analyzer Port interface number which cannot be edited. Because of this you cannot add a second NAM for roving.

CSCdp90085

Alarm configuration with Catalyst 6000 NAM

If you create a property file with an alarm configured and install it onto a Catalyst 6000 NAM in agent mode, the alarm configuration definition will not display in Domain Discovery. However, the alarm configured will work accordingly.

CSCdp97693

Support for HCRMON

If you click Test Agent after adding a Catalyst 6000 NAM as an agent, the following message is displayed:

High-Capacity Monitoring: Disabled or Not Supported

However, HCRMON is supported on the Catalyst 6000 NAM and you can safely ignore this message.

CSCdr82064

VLAN Monitor compatibility

The VLAN Monitor application is not compatible with the Catalyst 6000 NAM. TrafficDirector does not recognize the SMON OID implemented in the NAM.

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 does not recognize these changes.

CSCdm57988

Interface indices for FECs and VLANs are not available in Trend Reporter for reports against roved virtual interfaces

Because the Catalyst 5000 NAM is an "invisible" RMON agent associated with the switch, there is no way to select the NAM to generate reports using Trend Reporter. It is generally not advised that you depend on roving for data logging. However, you can log data on a port roved by a NAM. To do so, follow these steps:

1. Use Property Editor to create or modify the agent properties file for logging.

2. If roving a VLAN or FEC, you must manually edit the switch.swp file (where switch is the name associated with the Network Analysis Module).

CSCdm57988
(continued)

3. Add the VLAN or FEC interface indices using the same format as shown in the switch.swp file.

: The VLANs and FECs are displayed in the port listing in the Configuration Manager main screen.

Note If you reconfigure and relearn the switch, the switch.swp file is overwritten and your changes are lost.

4. From the Internal Agent Property File dialog box, select the property file you created in
Step 3.

5. Install the properties file.

: A switch.slg file is created.

6. Wait at least one logging interval (as defined in the properties file) so that data is available.

7. From Trend Reporter, select the switch and the port and interface index that was roved.

: Data should be logged for that port and interface index against which you can generate reports.

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com
Telnet: cco.cisco.com
Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
- From North America, call 408 526-8070
- From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language	E-mail Address
English	tac@cisco.com
Hanzi (Chinese)	chinese-tac@cisco.com
Kanji (Japanese)	japan-tac@cisco.com
Hangul (Korean)	korea-tac@cisco.com
Spanish	tac@cisco.com
Thai	thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.

Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)

Table of Contents

Release Notes for TrafficDirector Release 5.8.0a on Windows NTand Solaris

Release Notes for TrafficDirector Release 5.8.0a on Windows NTand Solaris

Release Notes for TrafficDirector Release 5.8.0a on Windows NT
and Solaris

Release Notes for TrafficDirector Release 5.8.0a on Windows NT
and Solaris