|
|
This preface describes who should read Using TrafficDirector, how it is organized, and its document conventions.
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, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
This publication is designed for network managers who are responsible for monitoring traffic and diagnosing emerging problems on network segments. Network managers should be familiar with the following topics:
The major sections of this guide are as follows:
Part 1: Getting Started
|
Background information about TrafficDirector and its concepts. Instructions for launching TrafficDirector. |
Part 2: Performing Administrative Tasks
|
Setting up configuration properties, agents, switches, domains, and filters. Describes tasks you need to perform before you can monitor traffic or protocol data, generate reports, and set traps. |
Part 3: Monitoring Traffic
|
How to use Traffic Monitor, view segment and history information, capture and decode packets, view talker, host, and conversation statistics, work with domains, resource monitor, and alert monitor. |
Part 4: Monitoring Protocol Data
|
How to use Protocol Monitor, Protocol Zoom, and Protocol History. |
Part 5: Monitoring Applications
|
How to use Application Monitor and Application History. |
Part 6: Setting Traps for Alarms
|
Configuring alarms and using traps to execute UNIX script files. |
Part 7: Creating Reports
|
Configuring SQL servers, generating and viewing reports, and understanding report information. |
Command descriptions use the following conventions:
| boldface font | Commands and keywords are in boldface. |
| italic font | Arguments for which you supply values are in italics. |
| [ ] | Elements in square brackets are optional. |
| { x | y | z } | Alternative keywords are grouped in braces and separated by vertical bars. |
Screen displays use the following convention:
| ^ | The symbol ^ represents the key labeled Control--for example, the key combination ^D in a screen display means hold down the Control key while you press the D key. |
Examples use the following conventions:
screen font
| Terminal sessions and information the system displays are in screen font.
|
| boldface screen font | Information you must enter is in boldface screen font. |
| < > | Nonprinting characters, such as passwords are in angle brackets. |
| [ ] | Default responses to system prompts are in square brackets. |
Network management interfaces use the following conventions:
Notes use the following conventions:
Cautions use the following conventions:
| Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. |
|
|