|
|
April 6, 1998
This release note and update document describes the new features and caveats for Release 5.2 of the TrafficDirector component of CiscoWorks for Switched Internetworks (CWSI). The information in this release note and update document only applies to TrafficDirector applications running in Windows NT and Solaris environments.
This document contains the following sections:
In addition to this release note and update document, the TrafficDirector documentation includes the Using TrafficDirector publication.
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 up to date 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 on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The TrafficDirector application includes the following new major features and enhancements:
The following table shows the release level requirements and dependencies for the TrafficDirector Release 5.2 application and the supported platforms.
| Platform | TrafficDirector Release | SwitchProbe Agent Release |
|---|---|---|
| Solaris | 5.2 | 4.1 |
| Windows NT | 5.2 | 4.1 |
You can only install the TrafficDirector 5.2 upgrade patch to CWSI 2.1 (for Windows NT) or CWSI 2.1.1 (for Solaris).
To upgrade the TrafficDirector application on a Windows NT platform, follow these steps:
Step 1 Quit the TrafficDirector application, and close all other applications.
Step 2 From the DOS window, run dbshutdn from the cwsiroot\bin directory.
Step 3 Download the TD5.2-nt-smu.tar.Z file from Cisco Connection Online (CCO) and extract install.exe and smu.tar.
Step 4 Run install.exe on the directory where CWSI 2.1 is installed.
For example, if CWSI 2.1 is installed on c:\cwsi21 you would enter the following command:
The install program copies all the new release 5.2 files to the appropriate directories, and the 5.2 upgrade installation for Windows NT completes.
To upgrade the TrafficDirector application on a Solaris platform, follow these steps:
Step 1 Close all TrafficDirector applications.
Step 2 Log in as a root user.
Step 3 Shut down all the TrafficDirector daemons running on your machine by running dbshutdn from the cwsiroot/bin directory.
If you want to confirm that the daemons are shut down, check the dbshutdn.log file.
Step 4 Download the tar file from CCO, and untar it by running
tar xvf TD5.2-sol-smu.tar.
You will see two files: install and smu.tar.
Step 5 Run the install program as root:
You will receive the following prompt:
Please enter the CWSI base directory:
Step 6 Enter the location where you have installed CWSI 2.1.
The install program asks if you want to enable the TrafficDirector data logging for reporting feature.
To enable or disable the TrafficDirector logging feature at any time after the installation, enter:
The install completes and the following message appears:
The TD5.2 Patch is installed. Thank you for choosing Cisco Systems!
You will need to determine if you need to use any user-configurable files that were created during previous installations instead of the new default files supplied with the 5.2 release.
If you have altered any of the following files and want to retain their contents, copy them from the backup directory into the NSHOME\usr directory:
You will need specific TrafficDirector 5.2 files to launch the 5.2 release successfully, even if you previously customized the contents of the earlier files as well. In this case, if you want to use your earlier configurations, you will need to merge (line level) the contents of the earlier releases with the 5.2 release. The 5.2 files include the following:
To merge the contents of any required files, you can use a text editor such as Edit. Open multiple windows containing the two file versions, and cut and paste the necessary configuration information into the file located in NSHOME\usr.
This section provides notes and caveats about the TrafficDirector application.
The new 5.2 properties file (fw42prop) is shipped with logging parameters enabled for 10 standard domains. If you do not plan to use the TrafficDirector reporting features, you do not need to log data. During the TrafficDirector product installation process, you are prompted whether you want to enable data logging for reporting. If you respond No, no data will be logged to the SQL database and no data will be available for Trend Reporter.
The TrafficDirector 5.2 upgrade process will not impact you if you have well-established domains and custom logging intervals. The properties file named default is not modified and is no longer used as the default properties filename when you create new agents.
If you use the new properties file (fw42prop) and initialize the Property File field in the Configuration Manager Add Agent dialog box, only the newly created agents are configured with logging enabled on the 10 standard domains. To create new agents that do not have logging enabled, select an alternative properties file.
You also can copy and create your own properties file definition and establish it as the default. To initialize the Properties File field in the Configuration Manager Add Agent dialog box with the new properties file definition filename, modify the cm-prop-file-default: fw42prop setting (in default.dvp).
Ports on a Token Ring module should be operational before you can install property files to it. [CSCdj81149]
After capturing and decoding data, an inaccurate protocol decode time stamp may be received. [CSCdj77699]
The default trap port in the "About Trap Integration" section on page D-9 of Using TrafficDirector should be list as port 395 and port 162. [CSCdj83179]
The differences between dvadmin and the TrafficDirector shell need to clarified in the documentation. [CSCdj74762]
The TrafficDirector Main Window shown in Figure 2-1 of Using TrafficDirector needs to be updated. The Netscout Shell button has been replaced with the TrafficDirector Shell button. [CSCdj74769]
The information in the sections that follow is an update to the Using TrafficDirector publication. This information will be added to Using TrafficDirector in a future release.
The TrafficDirector software supports the new ATM SwitchProbe device, where ATM counters are mapped to Etherstats group counters to generate ATM-specific, real-time data. This allows standard TrafficDirector applications, including Segment Details, Segment Zoom, Traffic Monitor, and Trend Reporter, to display ATM statistics.
No physical addresses are displayed in the remote monitoring (RMON) MIB tables for the ATM SwitchProbe device because the syntax of these MIB objects does not permit the representation of the 20-byte ATM Network Service Access Point (NSAP) address. This problem will be fixed in future releases with the support of the ATM RMON MIB by the ATM Forum.
For more information on these features, see the publications Cisco ATM SwitchProbe Configuration Note and Release Notes for SwitchProbe Release 4.2.1 and 4.1.
For any switch in the Cisco Catalyst 5000 family of switches, you can rove the VLANs configured in the switch. The roving VLANs operation feature is similar to the roving switch ports operation application feature--the packets on the VLAN are copied to an analyzer port where an attached SwitchProbe device examines them.
If you are the administrator, you can switch the display listing between ports and VLANs within the Configuration Manager to track the status of a particular Catalyst-based VLAN. To support the roving capability between VLANs and capture up-to-date statistics from a selected entity, you also can reinitialize the counters on demand.
To rove a VLAN, follow these steps:
Step 1 In the Configuration Manager main window, select the Switch radio button and select the switch containing the VLANs you want to rove.
Step 2 Click the VLAN radio button under the switch list to display all the VLANs configured in the selected switch.
Step 3 Select the VLAN you want to rove from the VLAN list.
Step 4 Select the switch port you want to rove.
Step 5 Click the Rove button to the right of the switch port list box.
A dialog box displays the VLAN that is currently roved (if any).
Step 6 Click Yes in the confirmation box.
Another dialog box prompts you to reinitialize the counters in the roving agent.
Step 7 Select Yes to reset the statistical counters of the roving agent to zero, or select No to continue tracking statistics at the point where the counters concluded from the last roved VLAN.
The agent roves to the selected VLAN.
When you set up alarms on Windows platforms, you can specify a batch file to run when the alarm occurs. Using batch files, you can run any TrafficDirector dvtool utility or any application such as Data Capture or TopN Hosts to get more information about the alarm condition.
# # Sample shell script to be executed upon trap reception # # This records the top hosts & conversations and Launches Data # Capture. # echo High utilization trap received from agent %1, priority %2 echo Top 10 hosts: dvsnap %1 RMON HOST 30 10 >> hostcon.out echo Top 10 conversations: dvsnap %1 RMON CONV 30 10 >> hostcon.out run c:\NSHOME\bin\nsdcap %1 -START
The TrafficDirector application invokes a TrafficDirector shell to run the batch file. In your batch file, enter the command string as you would in the TrafficDirector shell environment. For example, you can enter any TrafficDirector dvtool utility command as follows:
dvtool_name arguments output.filename
To execute TrafficDirector applications, use the following syntax:
run path\app_name arguments
where path\app_name is the path and application filename, and arguments are the application arguments, if any.
To add a batch file to a TrafficDirector alarm definition, follow these steps:
Step 1 Write the batch file and save it to the $TRAFFDIR\usr directory.
You can specify both the agent name and severity level (these are passed on to the program to run) from the trap you want to use to execute the DOS batch file.
Step 2 Create the alarm in the Property Editor.
Step 3 Enter the name and path of the script in the appropriate Program to Run field (the entire path can not exceed 15 characters).
You can specify two separate batch files: one for a rising threshold and one for a falling threshold.
Step 4 Add the alarm.
The information in the Program to Run field is sent as part of the SNMP trap each time the corresponding rising or falling alarm condition occurs and the specified batch file is executed.
By default, no security parameters are established for an agent. Through the remote Login utility, Admin (read and write) and User (read only) security levels can be set for an agent.
By establishing an Admin level of security, you can do the following:
To set any of the security parameters listed in the TrafficDirector Remote Login window, follow these steps:
Step 1 At the Selection# prompt, enter 31 (Go to Next Page).
Step 2 At the Selection# prompt, enter 25 (Security Options).
The Secure Access Menu window appears. From this window you can create or change an Admin level password, create or change a User level password, change the data capture slice size, or turn off the data capture capability.
To create or change an Admin level password, follow these steps:
(a) At the Selection# prompt, enter 1.
The Enter New Admin Password prompt appears.
(b) Enter the new or changed password (maximum six alpha or numeric characters).
The Confirm New Admin Password prompt appears.
(c) Reenter the password.
To create or change a User level password, follow these steps:
(a) At the Selection# prompt, enter 2.
The Enter New User Password prompt appears.
(b) Enter the new or changed password (maximum six alpha or numeric characters).
The Confirm New User Password prompt appears.
(c) Reenter the password.
To change the data capture slice size, follow these steps:
(a) At the Selection# prompt, enter 3.
The Enter New Slice Size prompt appears.
(b) Enter the new slice size.
To turn off the data capture capability, follow these steps:
(a) At the Selection# prompt, enter 4.
Another Selection# prompt appears.
(b) At the Selection# prompt, enter 5.
Another Selection# prompt appears.
(c) At the Selection# prompt, enter 26.
The Enter User or Admin Password prompt appears.
(d) Enter the User or Admin password you used to log in with.
The Selection# prompt appears.
(e) At the Selection# prompt, enter 32.
The Selection# prompt appears on the first page of the Agent Configuration Utility window.
Step 3 To reset the probe, follow these steps:
(a) At the Selection# prompt, enter 12 (Reset Agent).
The following message appears:
WARNING: Agent will be reset, confirm (n)
(b) Enter Y.
Step 4 To exit the Remote Login window, press Enter.
The TrafficDirector Main Window appears.
Step 5 To log out of the Remote Login utility, enter 26 at the Selection# prompt.
If you specify UDPAPP or TCPAPP in the Domain Type field, you can create new protocol domains to monitor known UDP and TCP ports. For example, the Internet Relay Chat (IRC) protocol uses port 194, and the Hypertext Transfer Protocol (HTTP) typically uses port 80.
The following examples of predefined protocol domains in the TrafficDirector application are based on port numbers:
To create new port-specific protocol domains, follow these steps:
Step 1 Select UDPAPP or TCPAPP from the Domain Type pulldown menu.
If you select UDPAPP, you can create protocol domains based on known UDP ports. If you select TCPAPP, you can create protocol domains based on known TCP ports.
Step 2 Select Tools/New Domain, or click the New button on the tool bar.
The New UDP Domain window or the New TCP Domain window appears (depending on your earlier selection).
Step 3 Enter the domain name in the Name field.
Step 4 Enter the UDP or TCP port number in the Port field.
Step 5 Click OK to save the domain.
Figure 7-4, "New Generic Domain Window," has been updated with a new PORT button. This new button enables traffic to be displayed for each port address in a generic domain.
The following ATM information was added to Table 18-1:
| Device | Display |
|---|---|
| Agent on an ATM segment | Utilization percentage for both DTE and DCE, Packet Size, Packet Destination, Short and Long-Term Segment History for both DTE and DCE. |
The following ATM information was added to Table 18-2:
| Data Display | Variables |
|---|---|
| DTE Utilization Percentage | For ATM, the average percentage of bandwidth utilization on the DTE network during the sample interval. |
| DCE Utilization Percentage | For ATM, the average percentage of bandwidth utilization on the DCE network during the sample interval. |
| Packet Size (ATM) | Percentages of different packet sizes within the last sampled interval displayed in a pie chart. |
| Packet Destination (ATM) | Percentages of unicast, multicast, and broadcast packets displayed in a pie chart. |
| Short-Term DTE Segment History
Short-Term DCE Segment History Long-Term DTE Segment History Long-Term DCE Segment History | Utilization and error percentage for the specified history section displayed in a line chart. |
Figure 21-1, "TrafficDirector Ring Station List Window (FDDI Network)," has been updated with a new Topology State field. This new field indicates if a node is connected correctly on the ring.
Figure 21-1, "TrafficDirector Ring Station List Window (FDDI Network)," also includes a new lower list box display that contains the following information:
| Station Address | Indicates the name and address of the highlighted station. |
| Nearest Upstream Neighbor Address | Indicates the address of the nearest active upstream neighbor (NAUN) of the highlighted station. |
| Node Class | Indicates the node type. Can be any one of the following types:
Single Attachment STATION (SAS) |
| Topology State | Indicates if the node is connected to the ring correctly. These states are indicated as follows:
Normal The following information is also displayed to indicate how the node is connected to the FDDI ring: Rooted Station/Station not Rooted |
| Synchronous Service | Indicates if synchronous traffic is supported. |
| Duplicate MAC Address Test | Indicates if a duplicate MAC address condition exists. |
The FDDI nodes can be classified into stations and concentrators. The primary purpose of a station is to transmit and receive information. Concentrators are similar to hubs: they provide facilities to connect additional nodes. Some node types can have zero, one, or two MAC addresses. For example, a dual attachment node with two MAC addresses can simultaneously receive and transmit frames on both the logical rings. This operation is not possible with a dual attachment node that has only one MAC.
The A-port of one dual attachment node needs to be connected to the B-port of its upstream neighbor, and the B-port needs to be connected to the A-port of its downstream neighbor (unless Dual Homing is used). In Twisted Ring A-A topology, the A-port of one dual attachment node is attached to the A-port of another dual attachment node. In Twisted Ring B-B topology, the B-port of one dual attachment node is attached to the B-port of another dual attachment node.
Redundant topology networks are defined by FDDI. If a fault occurs on the trunk ring, the dual attachment nodes on either side of the faulty link wrap around and bypass the fault link. These nodes are in a Wrap state.
A Peer Wrap state occurs when a fault in a node causes the node to wrap within itself.
Additional information is displayed to indicate how the node is connected to the FDDI ring. A node that is a station is rooted if it does not have an active A, B, or S port in tree mode. If a station is connected through a concentrator as part of a tree topology, it is unrooted (Station not Rooted).
If a node is a concentrator, its status is displayed as either Attached Concentrator or Unattached Concentrator. A concentrator can only be unattached if it does not have an active A, B, or S port. In an FDDI dual-ring topology or a dual-ring with trees topology, all concentrators are normally attached. However, in an FDDI tree topology the concentrators are arranged in a hierarchy, with a number of stations attached to each concentrator. In this topology, the one concentrator that is the root of the tree is unattached and all others are attached (under normal conditions).
An FDDI ring allows two different types of traffic: synchronous and asynchronous. Synchronous traffic consists of delay-sensitive traffic such as voice packets, which need to be transmitted within a specific time interval. Asynchronous traffic consists of data traffic produced by various communication applications, such as file transfer and mail. These data packets can sustain some delays.
If the node supports synchronous traffic, the following message is displayed:
Synchronous Service: Supported
If the node does not support synchronous traffic, then the following message is displayed:
Synchronous Service: Not Supported
On an operational FDDI ring, each node periodically checks to see if any other nodes exist with the same MAC address as its own. If a duplicate MAC address condition does not exist, the following message is displayed:
Duplicate MAC Address test: Passed
If a duplicate MAC address condition exists, one of the following messages is displayed:
Duplicate MAC Address test: Failed (My duplicate exists)
Duplicate MAC Address test: Failed (My Upstream is duplicate)
Figure 24-3, "TrafficDirector Protocol Decode Window (With Captured Data)," has been updated with a new Information field. This new field displays the source and destination port numbers for TCP and UDP protocols.
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.
|
|