Guest

Cisco TrafficDirector

Release Note (No title available)

 Feedback

Table of Contents

System Requirements
New Features
Documentation Roadmap
Special Installation Caution
Additional Information Online
Known Limitations
SIPP-AH and SIPP-ESP Protocols are Shown as AH and ESP
Multiport Roving for Ports in Different VLANs
Installing the SwitchProbe 5.1 Properties File
Trend Reporter Shows the Same Information for Different Reports
dbsnapd Daemons Halt if Logging the NFS Domain
DLCI Name Restrictions
Landscape Printing
TrafficDirector Loses Contact
Alert Monitor
Domain Discovery Display
Report Editor User Interface
TopN Talkers Displays Only One-Way Traffic Between
Two Hosts

TopN Sorted Summary Graphs Inverted
TopN Conversations Application
VLAN Monitor Application Display
Short- and Long-Term History Utilization
Trend Reporter Reports Appear in the Background
Reinstalling TrafficDirector
Graphical Applications on Solaris Platforms
Report/Logging Interval Time Mismatch
Protocol Usage Report View Options
Report Editor Changes on Trend Reporter
TrafficDirector Upgrades Display Previous Version Numbers
Documentation Updates
Special Installation Caution
Additional Information Online
Known Problems
Obtaining Documentation
Obtaining Technical Assistance

These release notes are for use with TrafficDirector Release 5.8.2 running on
AIX 4.3.3, and HP-UX 11.0 platforms.

These release notes provide:

System Requirements

Table 1 describes the minimum hardware and software requirements for running TrafficDirector.


Table 1: Minimum Hardware and Software Requirements
Hardware
Platform
Operating
System
Requirements for Real-Time Monitoring Requirements
for Reporting

IBM RS/6000

AIX 4.3

48 MB RAM
120 MB free disk space

256 MB RAM
663 MB free disk space

HP 9000 Series
700/800

HP-UX 10.20 or
11.0

48 MB RAM
120 MB free disk space

256 MB RAM
663 MB free disk space



New Features

TrafficDirector Release 5.8.2 contains the following new features:

Voice and VPN Communications Support

TrafficDirector Release 5.8.2 supports several new features in Cisco SwitchProbe devices and the Catalyst 6000 Network Analysis Module (NAM), most notably monitoring Voice Over IP (VoIP) protocols and VPNs.

With TrafficDirector Release 5.8.2 and SwitchProbe Release 5.1, users can monitor VPNs, GRE, IPSec domains and other relevant VoIP and Voice Over Frame Relay (VoFR) domains. The entries available in the domain.lst file are:

  • VPN—AH, ESP, GRE

  • Voice—RTP, RTPAUDIO, RTPVIDEO, VoFR, Q931


    Note   For the GRE and VoFR domains, only the stats group is supported.

Improved Catalyst 6000 NAM Support

The following sections describe the new features and enhancements to the TrafficDirector support of Catalyst 6000 family of switches configured with a Network Analysis Module (NAM).

Application Response Time (ART) Monitor

The ART Monitor application displays data from the Catalyst 6000 NAM when ART is properly configured on the NAM.

New Catalyst 6000 NAM Properties Files

Three new Catalyst 6000 NAM properties files have been added to configure a Catalyst 6000 NAM.

  • nam6kart11.asd—Use this properties file when adding or roving to a Catalyst 6000 NAM running software Release 1.1.(1a).

  • nam6kart.asd—Use this properties file when adding or roving to a Catalyst 6000 NAM running software Release 1.2.(x) and the ART Monitor software option turned on.

  • nam6kprop.asd—Use this properties file when adding or roving to a Catalyst 6000 NAM running software Release 1.2 and the ART Monitor software option turned off.


    Note   The Catalyst 6000 NAM is operational only with a Catalyst 6000 or 6509 switch running Supervisor card software release 5.5 or above. If you are using a Supervisor card running software release 5.4 or earlier, select the nam5kprop.asd properties file.

For more information, see "Adding a Catalyst 6000 NAM As an Agent to the TrafficDirector Configuration Manager Application" section and "Roving Switch Interfaces With the Catalyst 6000 NAM" section.

Additional Domains

Table 2 shows the 48 domains previously available only on the Catalyst 6000 NAM that have been added to the TrafficDirector Release 5.8.2 domain.lst file.


Note   These domains only support Catalyst 6000 NAM devices and not SwitchProbe devices.


Table 2: Additional Catalyst 6000 NAM Protocols

AARP

DISL

NLSP

RSVP1

ATMP

DRP

NOTES1

RTCP

BRIDGE

ESMP

NOTES2

RTP

CATALYST

GARP

NOTES4

SMB1

CCMAIL

IDRP

NOTES6

SMB2

CCMAIL1

ISO-IP

NOV-DIAG

SMB3

CCMAIL3

ISO-TP4

NOV-NETB

SMB4

CCMAIL4

L3SW

NOV-PEP

SSTB

CCMAIL5

MOBILE

NOV-SPX

STP

CDP

MSCP

NSP

TAGSWITC

CGMP

NETBEUI

PAGP

VSI

CSTB

NHRP

RARP_NAM

VTP

CGMP

NETBEUI

PAGP

VSI

CSTB

NHRP

RARP_NAM

VTP



To ensure the domains are only installed on Catalyst 6000 devices, a new file, domain.ext, now recognizes the device type per protocol based on a field value in
the file. These values are mapped to each protocol domain listed in the domain.lst file.

  • If the value is 0, the domain can be installed on a SwitchProbe device or a Catalyst 6000 NAM.

  • If the value is 1, the domain can be installed only on a SwitchProbe device.

  • If the value is 2, the domain can be installed only on a Catalyst 6000 NAM.

Updated Catalyst 6000 NAM Domains

The following Catalyst 6000 domains have been added to the TrafficDirector domain.lst, nam6kprop.asd, and nam6kart.asd files:

  • SUNRPC_T

  • SUNRPC

  • XWINDOW

  • XWIN-UDP

  • NFS_T1

  • NFS_U1

  • NETB_NAM

As a result, the Catalyst 6000 NAM no longer supports these domains in the domain.lst, nam6kprop.asd, and nam6kart.asd files:

  • SUNRPC1

  • SUNRPC2

  • XWIN1

  • XWIN2

  • NBT-NA1

Extended Support for ATM SwitchProbe Device

TrafficDirector Release 5.8.2, with SwitchProbe Releases 5.0 and 5.1, includes these changes on ATM SwitchProbe devices:

  • The number of PVCs supported for each ATM agent is now 120.

  • The ifspeed on ATM devices is now specified in kilobytes per second (Kbps).

  • Wildcard VCIs (a VP bundle or a group of PVCs that have the same VPI, but different VCIs) are displayed in TrafficDirector.

  • Non-AAL-based traffic (AAL1, 2 and 3/4) is displayed in TrafficDirector applications.

For more information, see Release Notes for SwitchProbe Release 5.1.

Multiprotocol Per IP Host Address Report

This new Trend Reporter report defines a single IP address to show IP-based protocol- or application-level traffic per user over a specified time. You can generate the report as a graph or a text-based ASCII report.

Interface 49 Link Aggregation Support

TrafficDirector Release 5.8.2 with SwitchProbe Release 5.1 can track multiple redundant or load-balanced links on interface 49 for multiport WAN devices. TrafficDirector can also track Application Response Time (ART MIB) data generated as a result of the ART MIB device software option on interface 49.

Improved Virtual Interface Support for Frame Relay Devices

TrafficDirector Release 5.8.2 with SwitchProbe Release 5.1 can display up to 440 virtual interfaces from Frame Relay SwitchProbe devices during configuration and data collection.

Access to Updated Default Properties Files

TrafficDirector Release 5.8.2 now supports completely updated default properties files based on SwitchProbe Release 5.1 protocols.

  • fw51prop.asd

  • fw51prop.ast

  • fw51prop.fsd

  • fw51prop.fst

The following domains have been removed from the properties files to support the SwitchProbe Release 5.1 firmware:

  • SIPP-AH

  • SIPP-ESP


    Note   You must use the fw51prop.xxx properties files when using TrafficDirector Release 5.8.2 with SwitchProbe devices running Release 5.1. If you are using TrafficDirector Release 5.8.2 with SwitchProbe devices running Release 4.7 or 5.0, continue to use the fw45prop.xxx properties files.

RMON2 Domain Support

A new domain, RMON2, has been added to the domain.lst file so that you can determine the port for TCP and UDP traffic for each SwitchProbe device. This traffic was previously counted in the TCP~ and UDP~ domains. The RMON2 domain is found at the protocol level of TrafficDirector. Statistics and host data per port are supported. For each device (regardless of the number of interfaces), port-level information is displayed in this format:

aa-bb-cc-dd-ee-ff

where:

  • aa is the MAC header indicating special encoding in the MAC address.

  • bb is the MAC header indicating special encoding in the MAC address.

  • cc is 01 if UPD or 02 if TCP.

  • dd is the high byte of the port number.

  • ee is the low byte of the port number.

  • ff is 00 and has no meaning.

For example, the RMON2 traffic may be shown as 7F-F9-01-08-01-00. In this case, it is UDP traffic on port 2049 (08-01 represents 0801 in hexidecimal format which is equal to 2049 in decimal format).

Protocol Decode Printing Support

The print settings defined in the default.dvp file on UNIX platforms also apply to the print capabilities in the Protocol Decode application. No additional configuration is required.

Updated SMON and HCRMON Standardization

TrafficDirector Release 5.8.2 now displays device data based on the most recent SMON standard (RFC 2613) for VLAN Monitor. TrafficDirector Release 5.8.2 also supports the HCRMON standard (Draft 6) whenever high-capacity devices such as the Gigabit Ethernet SwitchProbe device are used to collect TrafficDirector data.

Automatic Daemon Restart After Rebooting

This new feature automatically restarts daemons upon reboot; you no longer need to start the S83rmonmgr process manually.

To enable this feature:

For AIX Systems

Add the following entry to the /etc/inittab file:

S83rmonmgr:2:wait:$NSHOME/S83rmonmgr start

For HP-UX Systems

Copy the file S83rmonmgr from $NSHOME to /sbin/rc3.d/S83rmonmgr.

Substitute the $NSHOME variable in the S83rmonmgr file with the absolute path of your TrafficDirector Release 5.8.2 installation.

Enhanced Switch Support

The Cisco Systems devices now supported are:

  • Catalyst 4006

  • Catalyst 6000

  • Catalyst 6509


    Note   When using a Catalyst 6000 or Catalyst 6509 switch running software
    version 5.5 or later, select Cat_6000_v5.5+ or Cat_6509_v5.5+ from the switch.def file.

DTE/DCE Reports on Protocol Usage

Two new templates are available for the Protocol Usage report:

  • Protocol Usage Data Termination Equipment (_pudte.rt)

  • Protocol Usage Data Communication Equipment (_pudce.rt)

Use the new templates to generate reports that display utilization, octets, or packets for the data terminal equipment (DTE, outgoing) and data communications equipment (DCE, incoming) sides for a maximum of 20 application or protocols domains over time on a segment. By default, the reports are displayed as three-dimensional bar charts.

The sum of traffic can be broken down into DTE versus DCE utilization. You can directly compare and analyze changes in usage patterns for multiple applications or protocols on a segment.

The reports also provide a method for determining the volume of traffic associated with an application relative to the total traffic volume on the segment. They also help you determine the volume of traffic associated with an application, relative to the volume of traffic associated with a network-layer protocol.

Documentation Roadmap

The following documents are provided in PDF on your product CD:

  • Using the TrafficDirector Application

  • Installing and Setting up TrafficDirector on AIX and HP-UX


    Note   Adobe Acrobat Reader 4.0 is required.

The following documentation is available:

Paper Documentation

  • Installing and Setting up TrafficDirector on AIX and HP-UX (DOC-7812871=)—Describes how to install the TrafficDirector application on AIX and HP-UX systems.

  • Using the TrafficDirector Application (DOC-7810562=)—Describes all features and applications of the TrafficDirector application. You can obtain this document by:

    • Ordering a bound hardcopy from Cisco Systems.

    • Viewing it on the Cisco Documentation CD-ROM, a member of the Cisco Connection Family.

    • Viewing it on Cisco Connection Online (Cisco.com).

  • Catalyst 6000 Network Analysis Module Installation and Configuration Note (DOC-7810406=)—Describes the Catalyst 6000 Network Analysis Module and includes hardware installation and configuration procedures.

Online Documentation

  • Context-sensitive help

To access help you can either:

  • Select an option from the navigation tree, then click Help.

or

  • Click the Help button in the dialog box.

  • PDF

All TrafficDirector documentation is shipped in this format on your
product CD.

Special Installation Caution

Note the following caution about the TrafficDirector installation:


Caution   It is strongly recommended that you use the default installation path of /usr/CSCOtd on AIX systems, or /opt/CSCOtd5 on HP-UX systems. 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).

Additional Information Online

For information about CiscoWorks2000-supported devices, see this URL:

/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
sup_dev/index.htm.

Known Limitations

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

SIPP-AH and SIPP-ESP Protocols are Shown as AH and ESP

Although TrafficDirector allows you to install SIPP-AH and SIPP-ESP protocols, they are considered to be AH and ESP when learning the domains on the agent. If you launch against SIPP-AH or SIPP-ESP an error results; instead, launch applications only against AH and ESP.

Multiport Roving for Ports in Different VLANs

Roving multiple ports from different VLANs is not supported for all Catalyst 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 you do not lose data in the agent counters.

Installing the SwitchProbe 5.1 Properties File

If you have TFTP installed, and you upgrade from SwitchProbe Release 4.7 to 5.1, you cannot install the properties file using the Add or Replace option. You must completely reinstall the fw51prop file using the Reset All Counters option.

Trend Reporter Shows the Same Information for Different Reports

The Protocol Usage History Report and the DCE/DTE Reports show the same information as the Protocol Usage Report.

dbsnapd Daemons Halt if Logging the NFS Domain

If you use a properties file that logs for the NFS domain, dbsnapd (hosts and conversations) daemons halt at each logging interval. No logging occurs for any domain on that agent. Do not log for NFS hosts or conversations.

DLCI Name Restrictions

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

Landscape Printing

Landscape printing from Trend Reporter is not supported.

TrafficDirector 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 TrafficDirector to lose contact with it.

To prevent this from happening:


Step 1   Select Remote Login.from Configuration Manager.

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.


Alert Monitor

Extra characters might be displayed in Alert Monitor alert community strings.

Domain Discovery Display

When roving an FEC, Domain Discovery application displays incorrect statistics information for the ports that 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 process changes related to selecting host(s) for reports. You must modify an existing report template (.rt) file or create a new template.

TopN Talkers Displays Only One-Way Traffic Between
Two Hosts

When you click the Traffic radio button and click TopN Talkers, the graph shows two-way traffic for each DLCI.

If you click the Protocol radio button and click TopN Talkers, the graph shows only one-way traffic.

TopN Sorted Summary Graphs Inverted

Some non-inverted summary graphs sorted by TopN show the lowest value on the left and the highest value on the right of the bar graph. 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 windows. Dates might be displayed showing the year as 1969.

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.

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%.

Trend Reporter Reports Appear in the Background

When you start an application on Windows 2000 platforms, it becomes the active application and it is launched in the foreground. However, when you run a report from Trend Reporter, it is launched in the background. This behavior is controlled by the Windows desktop. Click the report to display it in the foreground.

Reinstalling TrafficDirector

AIX and HP-UX Platforms

Before you reinstall TrafficDirector on AIX and HP-UX systems, you must stop the resolver process.


Step 1   Determine the resolver process ID by entering this command:

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 stop the resolver process, enter this command at the UNIX prompt:

kill 20144

After stopping the resolver process, complete the installation by following the procedures in Installing and Setting up TrafficDirector on AIX and HP-UX.


Graphical Applications on Solaris Platforms

On Solaris platforms, some graphical TrafficDirector applications do not start properly because color map entries are not allocated correctly. 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

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 TrafficDirector. 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 might mismatch.

For example, if logging was off between 1 and 5 p.m and the reporting interval is between 1 and 5 p.m. on the same day, the message Warning: Cannot allocate colormap entry for "Cadet Blue."
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.

Protocol Usage Report View Options

When you run the Protocol Usage report, you can select pie chart as the format from the View menu. This will create a report that reflects a 24-hour period in a single pie chart. However, if you try to edit the Protocol Usage report template to set pie chart as the default view, pie chart is not listed as one of the options.

Report Editor Changes on Trend Reporter

Changes to Segment History reports made using the Report Editor are not written to the Trend Reporter report preview fields. However, Segment History reports will run according to the parameters established within Report Editor.

TrafficDirector Upgrades Display Previous Version Numbers

On Windows NT platforms, when upgrading to TrafficDirector Release 5.8.2 from a previous release (later than 5.5), references to the previous release is displayed in the Programs Menu even if the upgrade to Release 5.8.2 is successful.

To remove the reference to the older release, delete it from C:\Winnt\Profiles\
All Users\Start Menu\Programs.

Documentation Updates

The following sections contain updates to Using the TrafficDirector Application.

Chapter 3—Using Configuration Manager

Adding a Catalyst 6000 NAM As a Switch to the TrafficDirector Configuration Manager Application


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 NAM IP address.

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

  • If the NAM is installed in a Catalyst 6000 switch with software version 5.5 or above, select Cat_6000_v5.5+.

  • If the NAM is installed in a Catalyst 6000 switch with software version 5.4 or earlier, select Cat_6000.

  • If the NAM is installed in a Catalyst 6509 switch with software version 5.5 or above, select Cat_6509_v5.5+.

  • If the NAM is installed in a Catalyst 6509 switch with software version 5.4 or earlier, select Cat_6509.


Tips 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 "Identifying Community Strings On the NAM" section.

Step 10   In the Retries and Timeout text boxes:

   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.

   d.


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 Steps a. through 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 a Catalyst 6000 NAM As an Agent to the TrafficDirector Configuration Manager Application

When using the Catalyst 6000 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 perform 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 not spaces in the name, and 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 VLAN or FEC 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, 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 "Identifying Community Strings On the NAM" section.

Step 12   In the Retries and Timeout text boxes:

   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.

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 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 in TrafficDirector.
    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, see the 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 With the Catalyst 6000 NAM


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.

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, 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.


Chapter 31—Configuring and Generating Reports

Using Trend Reporter With the Catalyst 6000 NAM

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 "Adding a Catalyst 6000 NAM As a Switch to the TrafficDirector Configuration Manager Application" section.

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

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

Step 4   Click the Trend Reporter icon.

You can now generate reports using Trend Reporter for the interfaces roved.


Special Installation Caution

Note the following caution about the TrafficDirector installation:


Caution   It is strongly recommended that you use the default installation path of /usr/CSCOtd on AIX systems, or /opt/CSCOtd5 on HP-UX systems. 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).

Additional Information Online

For information about CiscoWorks2000-supported devices, see this URL:

/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
sup_dev/index.htm.

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 through 3.

You can search for problems using the Cisco bug tracking tool, Bug Navigator II. To access Bug Navigator II, log into Cisco.com and select Service & Support> Technical Support Help—Cisco TAC>Tools>Software Bug Toolkit>
Bug Navigator II
, or enter the following URL in your web browser: http://www.cisco.com/support/bugtools.

Table 3 lists the problems known to exist in TrafficDirector Release 5.8.2.


Table 3: TrafficDirector Known Problems
Bug ID Summary Explanation

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).

CDCdt51074

TrendReporter does not work with the Catalyst 6000 NAM if the timefilter mode is on

TrendReporter will only work on the Catalyst 6000 NAM if the timefilter mode is turned off in the NAM. To turn off the time filter in the NAM, run the timefilteroff script located in the $NSHOME/bin directory.

  • For Solaris platforms enter the following command at the UNIX prompt:

    %timefilteroff.csh NAM_ip_address 
    NAM_write_community_string
  • For Windows NT platforms enter the following command at the DOS prompt:

    >timefilteroff NAM_ip_address 
    NAM_write_community_string

CSCdk44815

Support for switch roving

The TrafficDirector application cannot recognize changes to a roved port, FEC, or VLAN that are made without using the TrafficDirector application (for example, using the switch command-line interface).

CSCdm57988

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

Since 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 recommended that you do not depend on roving for data logging. However, you can log data on a port roved by a NAM:

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

2. If roving a VLAN or FEC, manually edit the switch.swp file (where switch is the name associated with the NAM).

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 window.

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 properties file you created in Step 3.

5. Install the properties file.

6. A switch.slg file is created.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.

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 is assigned a static Analyzer Port interface number that cannot be edited. This means you cannot add a second NAM for roving.

CSCdp90085

Alarm configuration with Catalyst 6000 NAM

If you create a properties file, configure it with an alarm, and install it on a Catalyst 6000 NAM in agent mode, the alarm definition is not displayed in Domain Discovery. However, the alarm will work as configured.

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

You can ignore this message because HCRMON is supported on this device.

CSCdr45562

Configuration Manager port property limitation

When you select the port properties file in Configuration Manager, an unscrollable window opens that limits viewing to 42 items.

CSCdr64495

Port properties file configurations reset

If you add a new module to a Catalyst switch and learn all ports, all previous port properties file configurations are reset to their defaults.

CSCdr82064

VLAN Monitor compatibility

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

CSCdr84537

Timestamp packet capture in Sniffer format

Timestamps for captured packets saved in Sniffer formats are different than those saved in TrafficDirector formats.

CSCdr90792

Scope and Run Script support

The Scope and Run Script menu items in the Tools menu in Configuration Manager are not supported.

CSCdr97781

Port names on Catalyst 2900XL and 3500 XL switches

The TrafficDirector application cannot learn port names on Catalyst 2900XL and Catalyst 3500XL switches.

CSCds20171

Script not executed for trap variables

If you use Property Editor to set a trap variable for rising and falling thresholds on IP traffic utilization, the required script is not executed.

CSCdt4696

Ten character limit on port names for analyzer ports

Although Catalyst switches support port names up to 20 characters in length, TrafficDirector can only recognize 10 characters for the analyzer port on a switch in Configuration Manager.

CSCdt51094

Duplicate packets when roving a VLAN

TrafficDirector configures the rove (span) session with the direction set to BOTH (Tx and Rx; transmit and receive) while roving a VLAN to a Catalyst 6000 NAM or SwitchProbe device. For most Catalyst supervisor modules (except sub-models F6020 and F6020A), the span feature sends two copies of each packet to the destination port, thereby resulting in double the actual statistics.

Workaround:

Manually reconfigure the span direction to either transmit or receive.

For example, if the rove is VLAN 10 to a NAM or SwitchProbe device on port 4/1, you must:

1. Telnet to the switch.

2. To ensure that only one copy of the packet is
sent, enter one of these commands from the switch CLI:

    set span 10 4/1 tx
    
    set span 10 4/1 rx
    
     
    


Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Ordering Documentation

Cisco documentation is available in the following ways:

  • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/public/ordsum.html

  • Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

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

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 your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com 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.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

  • P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

  • P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

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

P1 and P2 level problems are defined as follows:

  • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

  • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

This document is to be used in conjunction with the documents listed in the "Documentation Roadmap" section.

AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other brands, names, or 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. (0104R)

Copyright © 2001, Cisco Systems, Inc.
All rights reserved.

   c.