|
|
You can use the TrafficDirector application to display and review agent history information.
The following sections provide information about displaying history information:
You can use Short-Term History to display snapshots of the various RMON 1 statistical counters stored in the memory of roving agent. The snapshots are displayed in a graphical format over a period of time. This display lets you look at spikes in utilization to determine areas of concern. You can zoom in on an area of concern to get a better view by clicking on two points of the graph.
The following sections contain more information about using Short-Term History:
To enable short-term history, follow these steps:
Step 1 Edit the properties file.
Step 2 From Property Editor, select the RMON domain.
Step 3 Click Edit.
Step 4 Check the Short-Term History box.
Step 5 Install properties on the agent.
The default values used to display the history information (samples and buckets) are established in the roving agent. The default sample period is 30 seconds, and the default number of buckets is 50. You can increase and decrease these values depending on your needs.
To start Short-Term History, follow these steps:
Step 1 Click Traffic from the TrafficDirector main window.
Step 2 Click the Agent, Agent Group, Switch, or Frame Relay radio button.
Step 3 Do one of the following:
Step 4 Select the RMON domain.
Step 5 Click the Short-Term History icon.
The Short-Term History window for the selection you made opens (Figure 19-1).
The different view options let you tailor the Short-Term History display for your specific needs.
Table 19-1 describes the information that is displayed on the Short-Term History window when you select a specific View option.
| Select This View Option | To Display |
|---|---|
Utilization | Utilization as a percentage of available bandwidth. |
Packets | Number of packets per second. |
Bytes | Number of bytes per second. |
Vital Signs | Five most important RMON1 statistics---Broadcast%, Multicast%, Utilization%, Error%, and Collision%. |
Packet Destinations | Packets per second for Broadcast, Multicasts, and Unicasts destinations. |
Errors | As a percentage, errors for CRCAligns, Undersize, Oversize, Fragments, and Jabbers. |
To zoom in on a section of a graph and get a more focused view, follow these steps:
Step 1 Move the cursor to the first point on the graph.
Step 2 Click the left mouse button.
The actual numerical value of the highlighted point is displayed in the status line of the Short-Term History window.
Step 3 Move the cursor to the second point on the graph.
Step 4 Click the left mouse button.
An exploded view of the graph between the two selected points is displayed.
Step 5 Click the right mouse button to return to the normal display.
You can use Long-Term History to display snapshots of the various RMON 1 statistical counters stored in the memory of a roving agent. The snapshots are displayed in a graphical format over a period of time. This display lets you look at spikes in utilization to determine areas of concern. You can zoom an area of concern to get a better view by clicking on two points of the graph.
The following sections contain more information about using Long-Term History:
To enable long-term history, follow these steps:
Step 1 Edit the properties file.
Step 2 From Property Editor, select the RMON domain.
Step 3 Click Edit.
Step 4 Check the Long-Term History box.
Step 5 Install properties on the agent.
The default values used to display the history information (samples and buckets) are established in the roving agent. The default sample period is 30 minutes, and the default number of buckets is 50. You can increase or decrease these values depending on your needs.
To start Long-Term History, follow these steps:
Step 1 Click Traffic from the TrafficDirector main window.
Step 2 Click the Agent, Agent Group, Switch, or Frame Relay radio button.
Step 3 Do one of the following:
Step 4 Select the RMON domain.
Step 5 Click the Long-Term History icon.
The Long-Term History window for the selection you made opens (Figure 19-2).
The different view options let you tailor the Long-Term History display for your specific needs.
Table 19-2 describes the information that is displayed in the Long-Term History window after you select a specific View option.
| Select This View Option | To Display |
|---|---|
Utilization | Utilization as a percentage of available bandwidth. |
Packets | Number of packets per second. |
Bytes | Number of bytes per second. |
Vital Signs | Five most important RMON1 statistics---Broadcast%, Multicast%, Utilization%, Error%, and Collision%. |
Packet Destinations | Packets per second for Broadcast, Multicasts, and Unicasts destinations. |
Errors | As a percentage, errors for CRCAligns, Undersize, Oversize, Fragments, and Jabbers. |
To zoom in on a section of a graph and get a more focused view, follow these steps:
Step 1 Move the cursor to the first point on the graph.
Step 2 Click the left mouse button.
The actual numerical value of the point highlighted displays in the status line of the Long-Term History window.
Step 3 Move the cursor to the second point on the graph.
Step 4 Click the left mouse button.
An exploded view of the graph between the two selected points is displayed.
Step 5 Click the right mouse button to return to the normal display.
You can use Domain History to display real-time statistics for an agent, Frame Relay Agent, DLCI, or a switch port and domain in various graphical formats. The graphic formats depend on the short- and long-term history interval values you specified in the default.dvp file.
The following sections contain more information about using Domain History:
To start Domain History, follow these steps:
Step 1 Click Traffic from the TrafficDirector main window.
Step 2 Click the Agent, Switch, or Frame Relay radio button.
Step 3 Do one of the following:
Step 4 Select a Domain name from the Domain Name list box.
Step 5 Click the Domain History icon.
The Domain History window opens for the selected domain (Figure 19-3).
By default, the Domain History display is set to Utilization. To see a different view, select View from the Menu bar and then select a different view from the list.
To display the numerical value that a point or bar in a graph represents, click on the point or bar. The value appears in the status bar at the bottom of the window (Figure 19-4).
You can use Host History to display a graph of statistics (utilization, packets, bytes, destinations, and errors) about a specific host for a selected agent and domain.
To start Host History, follow these steps:
Step 1 Click Traffic, Protocol, or Application from the TrafficDirector main window.
Step 2 Click the Agent or Frame Relay radio button.
Step 3 Do one of the following:
Step 4 Select the domain you want from the ones listed under the Domain Name heading.
Step 5 Click the All Talkers icon.
Step 6 The All Talkers window opens (Figure 19-5).
Step 7 Select a host name from the list displayed.
Step 8 Select Applications>Host History from the menu bar.
The Host History window opens (Figure 19-6).
Use the Custom History application to create custom user-defined history files (.udh) that contain specific history MIB variables for which you want to obtain statistics. By specifying individual MIB variables within a .udh file, you can define exactly what to display as history information, including counters or gauges.
For example, to display a comparison of the activity of IP packets versus IPX packets, you would create a .udh file that contains the MIB variables for IP packets and IPX packets.
If desired, you can change the default display (line graph) to a 2-D or 3-D bar graph.
You can also display statistics from other installed .udh files (up to 16 different .udh files are supported simultaneously) or zoom in on a section of a displayed graph to get a closer view of a specific section of the graph.
Before you start Custom History you must do the following:
The following sections contain more information about Custom History:
To verify configuration of the agent or Frame Relay agent, follow these steps:
Step 1 Change to the NSHOME/BIN directory.
Step 2 At the command-line prompt, enter the following command:
dvuhist <agent> NN
where <agent> is the name of the device from which you want to do the polling, and NN indicates a table ID number between 1 and 16.
If the device has not been configured for polling user-defined MIB variables, a message similar to this is displayed:
Error reading user history control
You must create and install .udh files. For more information, see "Creating .udh Files" and "Installing .udh Files."
If the device has already been configured for polling user-defined MIB variables, configuration information is displayed. For more information, see "Starting Custom History."
User-Defined History (.udh) files contain the specific user-defined MIB variables that will display information. You can define multiple user-defined MIB variables within each .udh file. However, only 32 variables display at one time. Each MIB variable consists of five components. Table 19-3 provides a detailed description of the contents of each component.
| This Part... | Contains This Information |
|---|---|
Label | User-defined description of the MIB variable. The information that displays in the legend at the bottom of the Custom History Display. For best display results, limit the label description to twenty characters |
OID String | The OID string that defines the MIB variable that you want to access for counter information. Use the dvwalk command-line utility, if necessary, to get OID strings |
Variable Instance | Variable that maps the .udh file to the correct probe interface number.
|
Index Number | The index number of the counter for which you want to get information. If necessary, use the dvdomid command-line utility to obtain the value. |
Sample Type | Delta (DEL) or Absolute (ABS). |
The following sample MIB variable breaks down as follows:
IP:pkts |1.3.6.1.2.1.16.12.2.1.1|@DLCI|327681|DEL
There is a sample .udh file in the NSHOME/usr directory that you can use as a template when creating .udh files. You can create an unlimited number of .udh files; however, only up to sixteen are displayed simultaneously within the History List box in the Custom History window.
To create custom .udh files for installation on an agent or Frame Relay agent DLCI, follow these steps:
Step 1 Change to the NSHOME/usr directory.
Step 2 Locate the sample .udh file.
Step 3 Copy the sample.udh file to a new .udh file, assigning the new file a name of up to fifteen characters.
The name you assign to a new .udh file affects the labels that display in the legend at the bottom of the Custom History display. Using any name you select for the .udh file displays the complete name of the object identifier for each MIB variable in the legend at the bottom of the Custom History display. However, if you use the name of an agent from the list box for the .udh file you are creating, the descriptive text entered as a label for each MIB variable in the .udh file displays at the bottom of the Custom History display.
For example, if you are using a PC, and want to create a new .udh file that displays the complete name of the object identifier for each MIB variable at the bottom of the Custom History display, you would enter the following command:
copy sample.udh justinexample.udh.
If you are using a PC and want to create a file that displays the descriptive text you entered as a label for the MIB variable, you would enter the following command:
copy sample.udh ET601013.udh
Step 4 Using a text editor, edit the .udh file just created to meet your needs by changing the following elements:
To identify the OID string, refer to the appropriate MIB document or a MIB browser that shows both the OID name and value.
For example, to indicate ifInOctets, you would specify 1.3.6.1.2.1.2.2.1.10.
To identify which variable instance to use, you must specify the interface on the SwitchProbe device for which you want to track the OID you specified. You can identify this using either the IFINDEX, DLCI#, or CONTROL INDEX of that interface.
For example, to track ifInOctets for interface 3, you would specify 1.3.6.1.2.1.2.2.1.10@IFN.3; to track ifInOctets for DLCI 57, you would specify 1.3.6.1.2.1.2.2.1.10@DLCI.57.
Figure 19-7 shows a sample .udh file:
# user defined history variables # # User Defined History Variables # Label Variable Sampletype # sampletype is ABS<1> or DEL<2> - default is DEL #---------------------------------------------------------------------- # eg. # myPkts "1.3.6.1.2.1.16.12.2.1.1.1.327681" Sampletype #---------------------------------------------------------------------- # replacement tags: # @DLCI = DLCI number for frame relay agents # @IFN = Physical interface number of agent # @INDEX = Control Index # IP:pkts "1.3.6.1.2.1.16.12.2.1.1.@INDEX.327681" DEL IP:octets "1.3.6.1.2.1.16.12.2.1.2.@INDEX.327681" DEL IPX:pkts "1.3.6.1.2.1.16.12.2.1.1.@INDEX.458755" DEL IPX:octets "1.3.6.1.2.1.16.12.2.1.2.@INDEX.458755" DEL DECNET:pkts "1.3.6.1.2.1.16.12.2.1.1.@INDEX.589829" DEL
To install customized .udh files, follow these steps:
Step 1 Change to the NSHOME/bin directory.
Step 2 At the command line prompt, enter the following command:
dvuhist agent TYPE config buckets interval filename.udh
where:
-f agent dlci_no is used for Frame Relay agents.
-s switch ifn is used for switches.
-v agent vlan_no is used for VLAN agents.
-c agent vc_no is used for VC agents.
config is the argument.
Step 3 Press Enter.
Step 4 Repeat Step 2 for other .udh files you want to install.
You start Custom History from the Traffic level of the main window.
To start Custom History, follow these steps:
Step 1 Click the Traffic radio button.
Step 2 Within the Traffic window, click the Agent, Switch, or Frame Relay radio button.
Step 3 Do one of the following:
Step 4 Click the Custom History icon.
The Custom History window displays information from the .udh file that corresponds to the first entry listed in the History List box.
Figure 19-8 illustrates the Custom History window when a random name was assigned to the .udh file.
Figure 19-9 illustrates the Custom History window when the agent name was assigned to a .udh file.
The default Custom History display shows a line graph for each MIB variable within the selected .udh file that has activity. Each of the individual MIB variables that make up a .udh file are shown in the legend at the bottom of the display. To change the default display, select Format>2-D Bar or Format>3-D Bar.
To use a different .udh file to display different MIB variable statistics, follow these steps:
Step 1 Select View>History List from the menu bar.
The History List box opens (Figure 19-10):
Step 2 Select the History List number you want to display.
Each number displayed (which was automatically assigned by the system) corresponds to the order that custom .udh files were installed on the agent. For example, the first .udh file installed is assigned UserHistory1, the second .udh file installed is assigned UserHistory2, and so on.
Step 3 Click OK.
The new MIB variable information defined in the selected .udh file is displayed.
To improve the view of the MIB variables displayed on the Custom History window for a selected .udh file, you can change the number of MIB variables displayed. To do so, follow these steps:
Step 1 Select View>Object List from the menu bar.
A list of the MIB variables within the .udh file currently displayed appears in the Select Custom History Objects window (Figure 19-11).
Step 2 Select only the MIB variable(s) for which you want to display history information.
Step 3 Click OK.
The Custom History window displays the selected MIB variables.
To zoom in on a portion of a graph displayed on the Custom History window to get a closer look at the activity between two points on a graph, follow these steps:
Step 1 Highlight a point on the graph that you want to focus in on.
Step 2 Click the left mouse button (time and value for the point display in the legend at the bottom of the display).
Step 3 Highlight a second point on the graph.
Step 4 Click the left mouse button again.
An expanded view of the data between point 1 and point 2 displays.
Step 5 When you have completed examining a portion of the graph, click the left mouse button a third time to zoom out.
Posted: Mon Apr 5 13:09:40 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.